Bug#1011902: marked as done (libvirt-python: FTBFS: make: *** [debian/rules:12: build] Error 25)

[Debian Bug Tracking System]

Your message dated Sat, 25 Jun 2022 05:34:02 +
with message-id 
and subject line Bug#1011902: fixed in libvirt-python 8.4.0-0.1
has caused the Debian Bug report #1011902,
regarding libvirt-python: FTBFS: make: *** [debian/rules:12: build] Error 25
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:239: python3.9 setup.py config 
> running config
> I: pybuild base:239: python3.10 setup.py config 
> /<>/setup.py:3: 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.core import setup, Extension, Command
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3.9 setup.py build 
> running build
> /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
> /usr/bin/python3.9 generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
> Found 493 functions in /usr/share/libvirt/api/libvirt-api.xml
> Found 0 functions in libvirt-override-api.xml
> Generated 404 wrapper functions
> /usr/bin/python3.9 generator.py libvirt-qemu 
> /usr/share/libvirt/api/libvirt-qemu-api.xml
> Found 6 functions in /usr/share/libvirt/api/libvirt-qemu-api.xml
> Found 0 functions in libvirt-qemu-override-api.xml
> Generated 3 wrapper functions
> Missing type converters: 
> int *:1 
> ERROR: failed virDomainQemuMonitorCommandWithFiles
> error: command '/usr/bin/python3.9' failed with exit code 1
> E: pybuild pybuild:369: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3.9 setup.py build 
> I: pybuild base:239: /usr/bin/python3 setup.py build 
> /<>/setup.py:3: 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.core import setup, Extension, Command
> running build
> /usr/bin/pkg-config --print-errors --atleast-version=0.9.11 libvirt
> /usr/bin/python3 generator.py libvirt /usr/share/libvirt/api/libvirt-api.xml
> Found 493 functions in /usr/share/libvirt/api/libvirt-api.xml
> Found 0 functions in libvirt-override-api.xml
> Generated 404 wrapper functions
> /usr/bin/python3 generator.py libvirt-qemu 
> /usr/share/libvirt/api/libvirt-qemu-api.xml
> Found 6 functions in /usr/share/libvirt/api/libvirt-qemu-api.xml
> Found 0 functions in libvirt-qemu-override-api.xml
> Generated 3 wrapper functions
> Missing type converters: 
> int *:1 
> ERROR: failed virDomainQemuMonitorCommandWithFiles
> error: command '/usr/bin/python3' failed with exit code 1
> E: pybuild pybuild:369: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p "3.9 3.10" 
> returned exit code 13
> make: *** [debian/rules:12: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/libvirt-python_8.0.0-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: libvirt-python
Source-Version: 8.4.0-0.1
Done: Pino Toscano 

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

A summary of the changes between 

Bug#948632: marked as done (rust-bcder: Build-depends on older rust-smallvec than is in unstable)

[Debian Bug Tracking System]

Your message dated Sat, 25 Jun 2022 04:03:52 +
with message-id 
and subject line Bug#948632: fixed in rust-bcder 0.6.1-1
has caused the Debian Bug report #948632,
regarding rust-bcder: Build-depends on older rust-smallvec than is in unstable
to be marked as done.

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

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


-- 
948632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-bcder
Version: 0.4.1-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal

rust-bcder build-depends on librust-smallvec-0.6+default-dev, but
rust-smallvec is now at version 1.1 in unstable:

$ sudo apt build-dep rust-bcder
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:rust-bcder : Depends: librust-smallvec-0.6+default-dev (>= 
0.6.10-~~) but it is not installable
E: Unable to correct problems, you have held broken packages.
$

Please update rust-bcder for compatibility with the current
rust-smallvec.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: rust-bcder
Source-Version: 0.6.1-1
Done: James McCoy 

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated rust-bcder 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, 24 Jun 2022 23:45:49 -0400
Source: rust-bcder
Architecture: source
Version: 0.6.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: James McCoy 
Closes: 948632
Changes:
 rust-bcder (0.6.1-1) unstable; urgency=medium
 .
   * Package bcder 0.6.1 from crates.io using debcargo 2.5.0
 + Updates smallvec dependency to 1.x (Closes: #948632)
 .
   [ Sylvestre Ledru ]
   * Team upload.
   * Source upload
   * Package bcder 0.4.1 from crates.io using debcargo 2.4.4-alpha.0
Checksums-Sha1:
 26bc485cf6e4952f9447086ab1d81abaa65c2e91 2383 rust-bcder_0.6.1-1.dsc
 c635457451f0c84153ddde8f578caf001f1d4fbb 58648 rust-bcder_0.6.1.orig.tar.gz
 310e2098688bf523bfa68d967c4c854fc1e7fcb4 3204 rust-bcder_0.6.1-1.debian.tar.xz
 9c2fae7fc352d2bf5402f72bb7d3c96d8b452c1e 7577 
rust-bcder_0.6.1-1_source.buildinfo
Checksums-Sha256:
 0a076394c312cbfb09c8b042cde3c3c9dc05da2f0d4732696cb788ff365e085b 2383 
rust-bcder_0.6.1-1.dsc
 52e7c3bae57b01ec5b1b028af1f77b7d41dd2bd97a41bab7968739b5329c0e39 58648 
rust-bcder_0.6.1.orig.tar.gz
 94727e5823f463185695fe164f97c0e0dd84b6eea158139b3025eb0c4d98420f 3204 
rust-bcder_0.6.1-1.debian.tar.xz
 0fbc7ec3f4d118e1de50ad244923f335eafd72c20d8b3142c283be87c31ee312 7577 
rust-bcder_0.6.1-1_source.buildinfo
Files:
 6fd8bbaf37e02e2b27d7963002bd71be 2383 rust optional rust-bcder_0.6.1-1.dsc
 e6624d9dc5d33b2c53de0ab5d7c18c9c 58648 rust optional 
rust-bcder_0.6.1.orig.tar.gz
 f9f9df982d076fee9b8cdb9ee9791be9 3204 rust optional 
rust-bcder_0.6.1-1.debian.tar.xz
 87290f6cce8609aa72d6b8cf2fe5d472 7577 rust optional 
rust-bcder_0.6.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmK2hO9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIACgkQ3+aRrjMb
o9v1hw//agvOe8BJMHn2vF8Y7DqKxu41I/wpwARikRtCQCdPBjkCiC9zp4OFYnJ7

Bug#1012883: marked as done (rust-copypasta: (build-)dependencies unsatisfiable.)

[Debian Bug Tracking System]

Your message dated Sat, 25 Jun 2022 03:21:02 +
with message-id 
and subject line Bug#1012883: fixed in rust-copypasta 0.8.1-1
has caused the Debian Bug report #1012883,
regarding rust-copypasta: (build-)dependencies unsatisfiable.
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.)


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

Package: rust-copypasta
Version: 0.7.1-2
Severity: serious

The dependencies and build-dependencies of rust-copypasta are unsatisfiable.

The first issue is that "disable-smithay-clipboard.diff" removes the
smithay-clipboard feature from the default set, but does not remove the
smithay-clipboard feature itself. Since the package uses collapse_features
and copypasta is not in Debian, this renders the package uninstallable.
I tweaked the patch to remove the feature completely (it can of course be
reinsated if/when someone packages smithay-clipboard)

The second issue is that x11-clipboard was recently updated to 0.6, in
addition to bumping the dependency, a small tweak to one of the use statements
was needed to make the code build with the new version.

However given that copypasta appears to have a grand total of zero tests, i'm
not comfortable uploading said patch without someone having done some real-world
testing of it (though looking at upstream git, I notice that they just made
the same change I did).

Anyway, I've committed the changes to debcargo-conf, I'll leave it up to
those packaging software that depends on copypasta to decide whether to
upload my changes as-is or make further changes.
--- End Message ---
--- Begin Message ---
Source: rust-copypasta
Source-Version: 0.8.1-1
Done: James McCoy 

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

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

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated rust-copypasta 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, 24 Jun 2022 23:09:15 -0400
Source: rust-copypasta
Architecture: source
Version: 0.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: James McCoy 
Closes: 1012883
Changes:
 rust-copypasta (0.8.1-1) unstable; urgency=medium
 .
   * Package copypasta 0.8.1 from crates.io using debcargo 2.5.0
 .
   [ Peter Michael Green ]
   * Team upload.
   * Package copypasta 0.7.1 from crates.io using debcargo 2.5.0
   * Disable smithay-clipboard feature (Sylvestre already removed it from the
 default features).  (Closes: #1012883)
Checksums-Sha1:
 3bbf27b0cb91b1b2b0a4216aa77b99bf88aa8968 2323 rust-copypasta_0.8.1-1.dsc
 b943a0e5b9768de145f726c64d1753680bae78b1 12872 rust-copypasta_0.8.1.orig.tar.gz
 7047f12379788dc27e78e9ad5ff7879be52239d1 3424 
rust-copypasta_0.8.1-1.debian.tar.xz
 8a44f8b682aaef938a72b106d9766ecc5c8954dd 7593 
rust-copypasta_0.8.1-1_source.buildinfo
Checksums-Sha256:
 99a99e7071dc551569b452c0c9ab48b528058886b779900018d2d85864c6b9c1 2323 
rust-copypasta_0.8.1-1.dsc
 d7216b5c1e9ad3867252505995b02d01c6fa7e6db0d8abd42634352ef37e 12872 
rust-copypasta_0.8.1.orig.tar.gz
 5cf748aca49e136db992d4c76f36cad2f6b8c3c009da85ab2bcb05ecb4a2d57d 3424 
rust-copypasta_0.8.1-1.debian.tar.xz
 3c165c87b6adf2466412bf242e2d56ad9f544a0588eb538004d8f7f82f7ff93b 7593 
rust-copypasta_0.8.1-1_source.buildinfo
Files:
 d95c627723866aee248809113eb65390 2323 rust optional rust-copypasta_0.8.1-1.dsc
 848862752f38a795149ef80a99c34185 12872 rust optional 
rust-copypasta_0.8.1.orig.tar.gz
 a3ad315ca31d9c727940348a4355f7c2 3424 rust optional 
rust-copypasta_0.8.1-1.debian.tar.xz
 80d5405cad5dfe89275921859d8f37ed 7593 rust optional 
rust-copypasta_0.8.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmK2fF9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIACgkQ3+aRrjMb
o9su+A//T9QWizZ20TuHkGsECZXCRJyALxRnwv/5ZmA6xOEgCDQaUAM6AxXbpCjd

Bug#1013730: FTBFS: S/MIME test fails with OpenSSL 3.0

[Andrew Ruthven]

Package: request-tracker4
Version: 4.4.5+dfsg-1
Severity: serious
Tags: ftbfs upstream
Justification: fails to build from source

To preempt other people reporting this.

The unit test t/mail/smime/realmail.t fails with OpenSSL 3.0.x due to DES
being deprecated and the sample emails used by the test use DES.

I have a fix for this, but I want to hear from upstream first as I'm not
convinced that enabling DES is the correct approach.

This issue is also in 5.0-trunk.

Cheers,
Andrew

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

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

Versions of packages request-tracker4 depends on:
ii  dbconfig-common  2.0.21
ii  debconf [debconf-2.0]1.5.79
ii  fonts-droid-fallback 1:6.0.1r16-1.1
ii  fonts-noto-hinted20201225-1
ii  libapache-session-perl   1.94-1
ii  libbusiness-hours-perl   0.13-1
ii  libcgi-emulate-psgi-perl 0.23-2
ii  libcgi-pm-perl   4.54-1
ii  libcgi-psgi-perl 0.15-3
ii  libclass-accessor-perl   0.51-1
ii  libclone-perl0.45-1+b2
ii  libconvert-color-perl0.12-1
ii  libcpanel-json-xs-perl   4.29-1
ii  libcrypt-eksblowfish-perl0.009-3
ii  libcrypt-x509-perl   0.54-1
ii  libcss-minifier-xs-perl  0.13-1+b1
ii  libcss-squish-perl   0.10-1
ii  libdata-guid-perl0.050-1
ii  libdata-ical-perl0.24+dfsg-1
ii  libdata-page-pageset-perl1.02-2
ii  libdate-extract-perl 0.06-2
ii  libdate-manip-perl   6.88-1
ii  libdatetime-format-natural-perl  1.13-1
ii  libdatetime-locale-perl  1:1.35-1
ii  libdatetime-perl 2:1.57-1
ii  libdbi-perl  1.643-3+b2
ii  libdbix-searchbuilder-perl   1.71-2
ii  libdevel-globaldestruction-perl  0.14-2
ii  libemail-address-list-perl   0.06-1
ii  libemail-address-perl1.912-1
ii  libencode-perl   3.17-1
ii  libfile-sharedir-perl1.118-1
ii  libfile-which-perl   1.27-1
ii  libgd-graph-perl 1.54~ds-3
ii  libgd-text-perl  0.86-10
ii  libgnupg-interface-perl  1.02-1
ii  libgraphviz-perl 2.24-1
ii  libhtml-formattext-withlinks-andtables-perl  0.07-2
ii  libhtml-formattext-withlinks-perl0.15-2
ii  libhtml-gumbo-perl   0.18-2+b4
ii  libhtml-mason-perl   1:1.59-1
ii  libhtml-mason-psgihandler-perl   0.53-2
ii  libhtml-quoted-perl  0.04-2
ii  libhtml-rewriteattributes-perl   0.05-2
ii  libhtml-scrubber-perl0.19-1
ii  libhttp-message-perl 6.37-1
ii  libipc-run-perl  20200505.0-1
ii  libipc-run3-perl 0.048-2
ii  libjavascript-minifier-xs-perl   0.15-1+b1
ii  libjson-perl 4.06000-1
ii  liblist-moreutils-perl   0.430-2
ii  liblocale-maketext-fuzzy-perl0.11-2
ii  liblocale-maketext-lexicon-perl  1.00-2
ii  liblog-dispatch-perl 2.70-1
ii  libmailtools-perl2.21-1
ii  libmime-tools-perl   5.509-2
ii  libmime-types-perl   2.22-1
ii  libmodule-refresh-perl   0.18-1
ii  libmodule-versions-report-perl   1.06-3
ii  libnet-cidr-perl 0.21-1
ii  libnet-ip-perl   1.26-2
ii  libnet-ldap-perl 1:0.6800+dfsg-1
ii  libnet-ssleay-perl   1.92-2
ii  libperlio-eol-perl   0.17-2
ii  libplack-perl1.0048-1
ii  libregexp-common-net-cidr-perl   0.03-1
ii  libregexp-common-perl2017060201-2
ii  libregexp-ipv6-perl  0.03-3
ii  librole-basic-perl   0.13-3
ii  

Bug#1003904: marked as done (lsp-plugins 1.1.31-1 FTBFS on armhf)

[Debian Bug Tracking System]

Your message dated Sat, 25 Jun 2022 01:03:51 +
with message-id 
and subject line Bug#1003904: fixed in lsp-plugins 1.1.31-2
has caused the Debian Bug report #1003904,
regarding lsp-plugins 1.1.31-1 FTBFS on armhf
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.)


-- 
1003904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lsp-plugins
Version: 1.1.31-1
Severity: serious
Justification: Policy 5.6.8

Dear Maintainer,

lsp-plugins 1.1.31 FTBFS on armhf and therefore cannot migrate from proposed to 
release on ubuntu Jammy (future 20.04). 
Please specify architectures to build for in debian/control.

Thanks,
Erich Eickmeyer
Ubuntu MOTU

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

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

Versions of packages lsp-plugins depends on:
ii  lsp-plugins-jack1.1.31-1
ii  lsp-plugins-ladspa  1.1.31-1
ii  lsp-plugins-lv2 1.1.31-1
ii  lsp-plugins-vst 1.1.31-1

lsp-plugins recommends no packages.

Versions of packages lsp-plugins suggests:
ii  dgedit  0.10.0-1build1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lsp-plugins
Source-Version: 1.1.31-2
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated lsp-plugins 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, 24 Jun 2022 20:41:33 -0400
Source: lsp-plugins
Architecture: source
Version: 1.1.31-2
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Maintainers 
Changed-By: Boyuan Yang 
Closes: 1003904
Changes:
 lsp-plugins (1.1.31-2) unstable; urgency=high
 .
   * Team upload.
   * Apply patch from Ubuntu:
 .
   [ Steve Langasek ]
   * export VERBOSE=1 in debian/rules; opaque build systems in build logs
 are evil.
   * debian/patches/use-fp-for-arm.patch: use the correct machine target
 for armhf builds.  Closes: #1003904.
Checksums-Sha1:
 7bb9d907942fa475e48b04c89feefb56ca1ba1c2 2442 lsp-plugins_1.1.31-2.dsc
 9f20a5785998fb3196c0952b6453ed7aaa745b0e 55132876 
lsp-plugins_1.1.31.orig.tar.gz
 8d3e8eba2c251b63d72c3ae7e0df951b05726aaf 7836 
lsp-plugins_1.1.31-2.debian.tar.xz
 92367f4956f92eb3e773a706f4273fb1bf51907e 13456 
lsp-plugins_1.1.31-2_amd64.buildinfo
Checksums-Sha256:
 32ff1d5427b45da865ea8a614fc0fd126d002ddced9cc014d000eefdc30d077e 2442 
lsp-plugins_1.1.31-2.dsc
 540252f747fa1253e0cec6d6b2804200929efcb5a69098d0487672877c84feb0 55132876 
lsp-plugins_1.1.31.orig.tar.gz
 40a2bb08b91e1bf6f516bb5b62f89cf0be3bd780fd37f67a02daef81b46f6aec 7836 
lsp-plugins_1.1.31-2.debian.tar.xz
 1d3886794d2abe957d4afb816118f132cf7093302060f2e449e50f6a8779d599 13456 
lsp-plugins_1.1.31-2_amd64.buildinfo
Files:
 c7e8a0404d1ec9a9dc8e8d177b6906c1 2442 sound optional lsp-plugins_1.1.31-2.dsc
 429337bff7079e5ea8b04f28c66c1ed1 55132876 sound optional 
lsp-plugins_1.1.31.orig.tar.gz
 aa29589332bbb5bc67209030d20695e8 7836 sound optional 
lsp-plugins_1.1.31-2.debian.tar.xz
 6f88136c35132429634ac57b95238165 13456 sound optional 
lsp-plugins_1.1.31-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmK2WsYACgkQwpPntGGC
Ws51Og/5ARn12JwwlwB+mqX9vyde8FNLvSidgD8Hcqg7cHMOIi3403833MT7Ly2D
DLF3NVrdrhZf6biJPWpwLx7SbU0Cj+1CAoFluP4HGX5ldk4T0w1/9fbLE8b61ZQB
QPys0qSWB3QpO4dIIaUuClwLNBA6ontNReWkTOYkamyd7nKFt/iDlBbDQq5wIbSn
LvJK2ETNebe3zUtt8HifpQA0kZ7Qw8ZF50OkooF/lve/lqkyHLUW/J/h6CDCVa+V

Bug#988729: marked as done (CVE-2021-21299)

[Debian Bug Tracking System]

Your message dated Sat, 25 Jun 2022 00:03:53 +
with message-id 
and subject line Bug#988729: fixed in rust-hyper 0.14.19-1
has caused the Debian Bug report #988729,
regarding CVE-2021-21299
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.)


-- 
988729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-hyper
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

CVE-2021-21299:
https://github.com/hyperium/hyper/security/advisories/GHSA-6hfq-h8hq-87mf
https://rustsec.org/advisories/RUSTSEC-2021-0020.html

Cheers,
 Moritz
--- End Message ---
--- Begin Message ---
Source: rust-hyper
Source-Version: 0.14.19-1
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated rust-hyper 
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, 24 Jun 2022 23:44:18 +
Source: rust-hyper
Architecture: source
Version: 0.14.19-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 988729
Changes:
 rust-hyper (0.14.19-1) unstable; urgency=medium
 .
   * Package hyper 0.14.19 from crates.io using debcargo 2.5.0
   * Set collapse_features = true
 .
   [ Fabian Gruenbichler ]
   * Team upload.
   * Package hyper 0.14.18 from crates.io using debcargo 2.5.0
 .
   * closes: #988729
Checksums-Sha1:
 718e776f20eca3660c75253ea5037edc83979bbc 3619 rust-hyper_0.14.19-1.dsc
 a96b4575c525e8cc4671a55842ea5436306ad6d5 182288 rust-hyper_0.14.19.orig.tar.gz
 b4c7a51d3c7ec517b34de46d12dc76b1a47b8d7e 3548 
rust-hyper_0.14.19-1.debian.tar.xz
 f17d52191c304af892a0d555f4d13a9f73210c6a 11283 
rust-hyper_0.14.19-1_source.buildinfo
Checksums-Sha256:
 4d437f56d358bc938a20fb258cf260ae9ca64a386aec8cfae3fd15ef5d51e441 3619 
rust-hyper_0.14.19-1.dsc
 42dc3c131584288d375f2d07f822b0cb012d8c6fb899a5b9fdb3cb7eb9b6004f 182288 
rust-hyper_0.14.19.orig.tar.gz
 d72c1631f068cb12ea0a8c8cc8ae6240d4684f4b0e900e36484fa8f354263c29 3548 
rust-hyper_0.14.19-1.debian.tar.xz
 801915229f90318dcd1085e6484a2ad54b646e88923ff95b82f08e6e142a9a6b 11283 
rust-hyper_0.14.19-1_source.buildinfo
Files:
 3eaf9d0f7a1244d98b42d92efdc178c2 3619 rust optional rust-hyper_0.14.19-1.dsc
 74837c8570567d6b63e9c217a73a96a7 182288 rust optional 
rust-hyper_0.14.19.orig.tar.gz
 1a381936b2874231f3c1ef550951a32a 3548 rust optional 
rust-hyper_0.14.19-1.debian.tar.xz
 9b20e77bd41253dbec1ef3d796c46990 11283 rust optional 
rust-hyper_0.14.19-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmK2TGYUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvWGw//WyiBe7rR4JBDA5WBmtoTni945Yb7
qtMlMia/Rv9XqVoKrPLNzomvs+iIOOLnosOTCAdi8/dtmUVadDaW3WOyIZH7zuuS
2xQeC9zVv6Ee3PSCZDXQ82uq0YyjfwUY5VpYiQw23JneHrqckF+LmQo3d6ObQUeu
7M6HUr5JdvtaOVtGMIEyQlPl/0e8cl74scg7FzXJSFwOVwsyvL0UofM4Sv+ysf+V
iNYIsMxUX0DzQ0RD9tFw3eDXnYvmo/dK0Eb1F+IGBPlQAu6YcXp/mrzMYF6zTKtM
6YqNQnLMSY+GFjFRRs6yNprJtUH+yQDT8A4iA0wDUP437jM8H3Pppv/4UmCKqbxo
mWVpWA7nRKyHb3sCrNeDElCl2VVeJmAjywtkVW2yJfcIzsYsTVrYcwrOULpI6ClD
H4rL66lz3VvDohvzOpthp2yAy9eDzDdWfVEFd1wgchP2wQfbNuPA7IYbBC1vMeXz
S4q1uuGbR6fkl89eLvqPGDScHo17Wm4s8vPFEoCklgG7lJcCJj4yHKo56tng3Wvc
IHV63y1kZbhpQCGpq5Z3bfvLG9x+xCMG3Nb8r1d211FDXWGaParqSgF4coB+8PAw
avHsNjweibanjM/kePf7lI1hNlMKd1ieg5gZkpu2ArijGCUwKK1qmiDjRZoPeyAT
kx1qEScUdMCpm5g=
=FNWO
-END PGP SIGNATURE End Message ---

Bug#1013726: python-astor: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Tianon Gravi]

On Fri, 24 Jun 2022 at 15:57, Louis-Philippe Véronneau  wrote:
> I had a closer look at the error log and identified the regression as:
> 'deprecated pytest feature: -k-'. Hopefully, that's helpful!

Thanks!  I've updated Git with a fix now (`-k 'not ...'`), but I'm not
sure when I'll have a chance to upload it.

(If someone reading this wants/needs it, please feel free to do the
upload dance!)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Bug#1011875: golang-github-opencontainers-runtime-tools: FTBFS unreproducible

[Sven Mueller]

Hi there.

Just a side note: The test fails on my test builds (with the same error as
in the original report. Because it relies on having a working network
connection. Which it shouldn't do. (my test builds are on a connection that
only allows access to a Debian mirror).

Cheers,
Sven

Bug#1013727: openlp: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: openlp
Version: 2.9.4-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/openlp_2.9.4-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013726: python-astor: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: python-astor
Version: 0.8.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-astor_0.8.1-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013725: python-aws-xray-sdk: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: python-aws-xray-sdk
Version: 0.95-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-aws-xray-sdk_0.95-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013724: python-b2sdk: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: python-b2sdk
Version: 1.3.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-b2sdk_1.3.0-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013723: python-easydev: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: python-easydev
Version: 0.12.0+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-easydev_0.12.0+dfsg-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013722: python-h11: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: python-h11
Version: 0.13.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-h11_0.13.0-1_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013721: python-jose: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: python-jose
Version: 3.3.0+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-jose_3.3.0+dfsg-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013720: python-matrix-nio: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: python-matrix-nio
Version: 0.19.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-matrix-nio_0.19.0-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013719: python-twitter: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: python-twitter
Version: 3.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-twitter_3.3-3_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012224: marked as done (python-tornado: autopkgtest regression in testing)

[Debian Bug Tracking System]

Your message dated Sat, 25 Jun 2022 00:52:18 +0200
with message-id 

and subject line python-tornado: autopkgtest regression in testing
has caused the Debian Bug report #1012224,
regarding python-tornado: autopkgtest regression in testing
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.)


-- 
1012224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-tornado
Version: 6.1.0-3
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime around 2022-05-08, python-tornado's autopkgtests regressed in
testing [1].
I've copied what I hope is the relevant part below.

The package also now FTBFS on reproducible builds [2] with the same error.

Regards
Graham


[1] https://ci.debian.net/packages/p/python-tornado/testing/amd64/
[2] https://tests.reproducible-builds.org/debian/rb-pkg/python-tornado.html


==
ERROR: test_multi_line_headers
(tornado.test.curl_httpclient_test.CurlHTTPClientCommonTestCase)
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/tornado/testing.py", line 98, in __call__
result = self.orig_method(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/tornado/test/httpclient_test.py",
line 534, in test_multi_line_headers
resp = self.fetch("http://127.0.0.1:%d/; % port)
  File "/usr/lib/python3/dist-packages/tornado/testing.py", line 443, in fetch
return self.io_loop.run_sync(
  File "/usr/lib/python3/dist-packages/tornado/ioloop.py", line 530, in run_sync
return future_cell[0].result()
tornado.curl_httpclient.CurlError: HTTP 599: Header without colon

--
Ran 1167 tests in 16.585s

FAILED (errors=1, skipped=6)
Some tests were skipped because: Prevent internet access during build,
needs fix, no testable future imports, pycares module not present
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 35633--- End Message ---

Bug#1013718: sphinx-gallery: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: sphinx-gallery
Version: 0.10.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/sphinx-gallery_0.10.1-1_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013717: spyne: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: spyne
Version: 2.14.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/spyne_2.14.0-1_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013716: flask: FTBFS: pytest7 regression, deprecated pytest feature: pytest.warnsNone

[Louis-Philippe Véronneau]

Source: flask
Version: 2.0.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/flask_2.0.1-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: pytest.warnsNone'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013715: photutils: FTBFS: pytest7 regression, deprecated pytest feature: pytest.warnsNone

[Louis-Philippe Véronneau]

Source: photutils
Version: 1.4.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/photutils_1.4.0-3_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: pytest.warnsNone'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013714: python-ase: FTBFS: pytest7 regression, deprecated pytest feature: pytest.warnsNone

[Louis-Philippe Véronneau]

Source: python-ase
Version: 3.22.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-ase_3.22.1-1_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: pytest.warnsNone'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013713: python-biom-format: FTBFS: pytest7 regression, not sure what the problem is

[Louis-Philippe Véronneau]

Source: python-biom-format
Version: 2.1.10-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-biom-format_2.1.10-4_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'not sure what the problem is'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013712: python-httplib2: FTBFS: pytest7 regression, not sure what the problem is

[Louis-Philippe Véronneau]

Source: python-httplib2
Version: 0.20.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-httplib2_0.20.2-3_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'not sure what the problem is'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013711: python-pytest-subtests: FTBFS: pytest7 regression, not sure what the problem is

[Louis-Philippe Véronneau]

Source: python-pytest-subtests
Version: 0.6.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-pytest-subtests_0.6.0-1_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'not sure what the problem is'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013710: python-can: FTBFS: pytest7 regression, AttributeError: pytest.approx is not supported in a boolean context

[Louis-Philippe Véronneau]

Source: python-can
Version: 3.3.2.final~github-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-can_3.3.2.final~github-3_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'AttributeError: pytest.approx is not supported in a boolean context'.
Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013709: python-protobix: FTBFS: pytest7 regression, plugin distutils failed with: exit code=5

[Louis-Philippe Véronneau]

Source: python-protobix
Version: 1.0.2-11
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-protobix_1.0.2-11_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'plugin distutils failed with: exit code=5'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1011712: olm: FTBFS: unsatisfiable build-dependency: binaryen (< 105+) but 106-1 is to be installed

[Evangelos Ribeiro Tzaras]

Hi,

On Thu, 23 Jun 2022 13:33:55 +0200 Markus Koschany  wrote:
> Hi,
> 
> I didn't know that there was some coordination required between binaryen and
> emscripten. Nobody talked about that in the past. Sorry to ditch your request
> but I don't plan to maintain emscripten. 

Thanks for your reply and good to know.

> The only reason why I introduced
> binaryen and wabt to Debian was to compile web assembly code from source in
> ublock-origin. Apart from that I am not really involved in the Javascript
> ecosystem either. I think it is best if someone takes over emscripten and
> binaryen and maintains them together.
> 

Having looked a bit into olm and emscripten I can imagine a few possible
solutions:

- binaryen is a build dep for emscripten "only" for running the tests
(). This suggest to me, that it should be possible to get a build
going without the tests. 
I've tried running building with DEB_BUILD_OPTIONS=nocheck and dropping the
build dep on binaryen, but this alone didn't stop the build from failing.
d/rules is rather complex beast and I haven't managed to rip everything
"unneeded" out. Maybe someone more knowledgeable will have more success..
Although I'm not sure how good of an idea it would be to simply skip the tests.

- Drop the javascript bindings for olm (libjs-olm). The only reverse dependency
of libjs-olm is libjs-matrix-sdk which itself has no reverse dependencies.

- Have someone maintain binaryen and emscripten and always upgrade in lockstep,
as the sources [0] suggest, that the actual and "expected" binaryen version at
most differ by one version number.

Maybe there are other ideas of how to resolve this.

If no other solution presents itself I'm inclined to drop libjs-olm in a NMU
with DELAYED/7.

[0]
https://salsa.debian.org/js-team/emscripten/-/blob/debian/latest/tools/building.py#L1475

Cheers
-- 
Evangelos
PGP: B938 6554 B7DD 266B CB8E 29A9 90F0 C9B1 8A6B 4A19





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

Bug#1013708: python-pykka: FTBFS: pytest7 regression, AttributeError: module pytest has no attribute collect

[Louis-Philippe Véronneau]

Source: python-pykka
Version: 2.0.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-pykka_2.0.3-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'AttributeError: module pytest has no attribute collect'. Hopefully,
that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013707: python-ratelimiter: FTBFS: pytest7 regression, AttributeError: module pytest has no attribute collect

[Louis-Philippe Véronneau]

Source: python-ratelimiter
Version: 1.2.0.post0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-ratelimiter_1.2.0.post0-1_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'AttributeError: module pytest has no attribute collect'. Hopefully,
that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013706: python-pytest-xprocess: FTBFS: pytest7 regression, pytest.PytestUnraisableExceptionWarning: Exception ignored

[Louis-Philippe Véronneau]

Source: python-pytest-xprocess
Version: 0.18.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-pytest-xprocess_0.18.1-3_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'pytest.PytestUnraisableExceptionWarning: Exception ignored'. Hopefully,
that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013702: pytest-pylint: FTBFS: pytest7 regression, AssertionError

[Louis-Philippe Véronneau]

Source: pytest-pylint
Version: 0.18.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/pytest-pylint_0.18.0-3_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'AssertionError'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013705: humanfriendly: FTBFS: pytest7 regression, upstream doesn't actually use pytest?

[Louis-Philippe Véronneau]

Source: humanfriendly
Version: 10.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/humanfriendly_10.0-1_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'upstream doesn't actually use pytest?'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013704: pyglet: FTBFS: pytest7 regression, py3.9 OK; py3.10 fails

[Louis-Philippe Véronneau]

Source: pyglet
Version: 1.5.14-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/pyglet_1.5.14-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'py3.9 OK; py3.10 fails'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013703: pyranges: FTBFS: pytest7 regression, py3.9 OK; py3.10 fails with Fatal Python error: Bus error

[Louis-Philippe Véronneau]

Source: pyranges
Version: 0.0.111+ds-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/pyranges_0.0.111+ds-1_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'py3.9 OK; py3.10 fails with Fatal Python error: Bus error'. Hopefully,
that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013701: junitparser: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: junitparser
Version: 2.5.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/junitparser_2.5.0-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013700: python-qtpy: FTBFS: pytest7 regression, TypeError: the 'package' argument is required to perform a relative import

[Louis-Philippe Véronneau]

Source: python-qtpy
Version: 2.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-qtpy_2.1.0-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'TypeError: the 'package' argument is required to perform a relative
import'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013699: asyncpg: FTBFS: pytest7 regression, deprecated pytest feature: -k-

[Louis-Philippe Véronneau]

Source: asyncpg
Version: 0.25.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/asyncpg_0.25.0-1_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

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

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

If you fail to reproduce this, please provide a build log and diff it
with the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013622: marked as done (mailscripts: FTBFS: /bin/sh: 1: register-python-argcomplete3: not found)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 22:04:02 +
with message-id 
and subject line Bug#1013622: fixed in mailscripts 27-1
has caused the Debian Bug report #1013622,
regarding mailscripts: FTBFS: /bin/sh: 1: register-python-argcomplete3: not 
found
to be marked as done.

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

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


-- 
1013622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mailscripts
Version: 26-1
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):
> make[1]: Entering directory '/<>'
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=mdmv \
>   mdmv.1.pod mdmv.1
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=mbox2maildir \
>   mbox2maildir.1.pod mbox2maildir.1
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=notmuch-slurp-debbug \
>   notmuch-slurp-debbug.1.pod notmuch-slurp-debbug.1
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=notmuch-extract-patch \
>   notmuch-extract-patch.1.pod notmuch-extract-patch.1
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=maildir-import-patch \
>   maildir-import-patch.1.pod maildir-import-patch.1
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=mbox-extract-patch \
>   mbox-extract-patch.1.pod mbox-extract-patch.1
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=imap-dl \
>   imap-dl.1.pod imap-dl.1
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=email-extract-openpgp-certs \
>   email-extract-openpgp-certs.1.pod email-extract-openpgp-certs.1
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=email-print-mime-structure \
>   email-print-mime-structure.1.pod email-print-mime-structure.1
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=notmuch-import-patch \
>   notmuch-import-patch.1.pod notmuch-import-patch.1
> pod2man --section=1 --date="Debian Project" --center="User Commands" \
>   --utf8 \
>   --name=gmi2email \
>   gmi2email.1.pod gmi2email.1
> mkdir -p completions/bash
> register-python-argcomplete3 email-print-mime-structure 
> >completions/bash/email-print-mime-structure.tmp
> /bin/sh: 1: register-python-argcomplete3: not found
> make[1]: *** [Makefile:30: completions/bash/email-print-mime-structure] Error 
> 127


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/mailscripts_26-1_unstable.log

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

We believe that the bug you reported is fixed in the latest version of
mailscripts, 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 pleas

Bug#1013542: marked as done (rust-tre-command: FTBFS: build-dependency not installable: librust-lscolors-0.8+default-dev)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 21:06:44 +
with message-id 
and subject line Bug#1013542: fixed in rust-tre-command 0.4.0-1
has caused the Debian Bug report #1013542,
regarding rust-tre-command: FTBFS: build-dependency not installable: 
librust-lscolors-0.8+default-dev
to be marked as done.

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

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


-- 
1013542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-tre-command
Version: 0.3.6-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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-atty-0.2+default-dev, 
> librust-getopts-0.2+default-dev, librust-lscolors-0.8+default-dev, 
> librust-serde-1+default-dev, librust-serde-1+derive-dev, 
> librust-serde-json-1+default-dev, librust-slab-0.4+default-dev (>= 0.4.1-~~), 
> librust-termcolor-1+default-dev, librust-walkdir-2+default-dev, help2man, 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-atty-0.2+default-dev, 
> librust-getopts-0.2+default-dev, librust-lscolors-0.8+default-dev, 
> librust-serde-1+default-dev, librust-serde-1+derive-dev, 
> librust-serde-json-1+default-dev, librust-slab-0.4+default-dev (>= 0.4.1-~~), 
> librust-termcolor-1+default-dev, librust-walkdir-2+default-dev, help2man, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [485 B]
> Get:5 copy:/<>/apt_archive ./ Packages [570 B]
> Fetched 2012 B in 0s (160 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librust-lscolors-0.8+default-dev 
> but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/rust-tre-command_0.3.6-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=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: rust-tre-command
Source-Version: 0.4.0-1
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-tre-command, 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

Processed: tagging 1013526

[Debian Bug Tracking System]

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

> # emollier _can_ reproduce it
> tags 1013526 - unreproducible
Bug #1013526 [src:libtickit-widget-scrollbox-perl] 
libtickit-widget-scrollbox-perl: FTBFS: dh_auto_test: error: /usr/bin/perl 
Build test --verbose 1 returned exit code 255
Removed tag(s) unreproducible.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1013526: libtickit-widget-scrollbox-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed
Bug #1013526 [src:libtickit-widget-scrollbox-perl] 
libtickit-widget-scrollbox-perl: FTBFS: dh_auto_test: error: /usr/bin/perl 
Build test --verbose 1 returned exit code 255
Added tag(s) confirmed.

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

Bug#1013674: haskell-wl-pprint-text_1.2.0.1-1+b2_mips64el-buildd.changes REJECTED

[Aurelien Jarno]

Source: haskell-wl-pprint-text
Version: 1.2.0.1-1
Severity: serious

On 2022-06-22 16:08, Debian FTP Masters wrote:
> libghc-wl-pprint-text-dev_1.2.0.1-1+b2_mips64el.deb: has 1 file(s) with a 
> timestamp too far in the past:
>   usr/share/doc/libghc-wl-pprint-text-dev/changelog.gz (Thu Jan  1 00:00:00 
> 1970)
> 
> 
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 

Bug#999162: marked as done (oroborus: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:37:51 +
with message-id 
and subject line Bug#1012435: Removed package(s) from unstable
has caused the Debian Bug report #999162,
regarding oroborus: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oroborus
Version: 2.0.20+nmu1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 2.0.20+nmu1+rm

Dear submitter,

as the package oroborus has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1012435

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#999135: marked as done (keylaunch: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:37:16 +
with message-id 
and subject line Bug#1012434: Removed package(s) from unstable
has caused the Debian Bug report #999135,
regarding keylaunch: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: keylaunch
Version: 1.3.9
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 1.3.9+rm

Dear submitter,

as the package keylaunch has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1012434

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#999043: marked as done (sbrsh: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:36:46 +
with message-id 
and subject line Bug#1012594: Removed package(s) from unstable
has caused the Debian Bug report #999043,
regarding sbrsh: missing required debian/rules targets build-arch and/or 
build-indep
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.)


-- 
999043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sbrsh
Version: 7.6.1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 7.6.1+rm

Dear submitter,

as the package sbrsh has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1012594

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#965809: marked as done (sbrsh: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:36:46 +
with message-id 
and subject line Bug#1012594: Removed package(s) from unstable
has caused the Debian Bug report #965809,
regarding sbrsh: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965809
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sbrsh
Version: 7.6.1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package sbrsh uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 7.6.1+rm

Dear submitter,

as the package sbrsh has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1012594

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Processed: forcibly merging 1012535 1013552

[Debian Bug Tracking System]

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

> forcemerge 1012535 1013552
Bug #1012535 {Done: Pino Toscano } [src:cantor] cantor: fails 
to build from source
Bug #1012535 {Done: Pino Toscano } [src:cantor] cantor: fails 
to build from source
Added tag(s) sid and bookworm.
Bug #1013552 [src:cantor] cantor: FTBFS: pythonkeywords.cpp:11:10: fatal error: 
repository.h: No such file or directory
Marked Bug as done
Marked as fixed in versions cantor/4:22.04.1-1.
Merged 1012535 1013552
> thanks
Stopping processing here.

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

Bug#1008415: marked as done (libnih: FTBFS: dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:35:51 +
with message-id 
and subject line Bug#1013225: Removed package(s) from unstable
has caused the Debian Bug report #1008415,
regarding libnih: FTBFS: dh_auto_test: error: make -j8 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.)


-- 
1008415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnih
Version: 1.0.3-12
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/nih-dbus'
> PASS: test_dbus_error
> ../test-driver: line 112: 3855884 Aborted "$@" >> "$log_file" 
> 2>&1
> FAIL: test_dbus_connection
> PASS: test_dbus_pending_data
> PASS: test_dbus_util
> PASS: test_dbus_message
> PASS: test_dbus_object
> PASS: test_dbus_proxy
> ===
>libnih 1.0.3: nih-dbus/test-suite.log
> ===
> 
> # TOTAL: 7
> # PASS:  6
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test_dbus_connection
> ==
> 
> Testing nih_dbus_connect()
> ...with listening server
> ...with disconnection from server
> ...with disconnection signal from wrong path
> FAIL test_dbus_connection (exit status: 134)
> 
> 
> Testsuite summary for libnih 1.0.3
> 
> # TOTAL: 7
> # PASS:  6
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See nih-dbus/test-suite.log
> Please report to http://bugs.launchpad.net/libnih/
> 
> make[4]: *** [Makefile:1125: test-suite.log] Error 1
> make[4]: Leaving directory '/<>/nih-dbus'
> make[3]: *** [Makefile:1233: check-TESTS] Error 2
> make[3]: Leaving directory '/<>/nih-dbus'
> make[2]: *** [Makefile:1348: check-am] Error 2
> make[2]: Leaving directory '/<>/nih-dbus'
> make[1]: *** [Makefile:474: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 check VERBOSE=1 returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/03/26/libnih_1.0.3-12_unstable.log

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

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

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

Dear submitter,

as the package libnih has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1013225

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#997339: marked as done (nvtv: FTBFS: configure: error: cannot find required auxiliary files: compile missing)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:33:31 +
with message-id 
and subject line Bug#1013278: Removed package(s) from unstable
has caused the Debian Bug report #997339,
regarding nvtv: FTBFS: configure: error: cannot find required auxiliary files: 
compile missing
to be marked as done.

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

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


-- 
997339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvtv
Version: 0.4.7-8.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> touch debian/stamp-autotools-files
> chmod a+x /<>/./configure
> mkdir -p .
> cd . && CFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
> LDFLAGS="-Wl,-z,relro -Wl,-dy,--as-needed" /<>/./configure 
> --build=x86_64-linux-gnu --prefix=/usr --includedir="\${prefix}/include" 
> --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info" 
> --sysconfdir=/etc --localstatedir=/var --libexecdir="\${prefix}/lib/nvtv" 
> --srcdir=. --disable-maintainer-mode --disable-dependency-tracking 
> --disable-silent-rules
> configure: WARNING: unrecognized options: --disable-maintainer-mode
> configure: error: cannot find required auxiliary files: compile missing


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/nvtv_0.4.7-8.1_unstable.log

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

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

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

Dear submitter,

as the package nvtv has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1013278

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1012255: marked as done (hatari: FTBFS for RISC-V due to RISC-V system header)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:34:24 +
with message-id 
and subject line Bug#1012255: fixed in hatari 2.3.1+dfsg-2
has caused the Debian Bug report #1012255,
regarding hatari: FTBFS for RISC-V due to RISC-V system header
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.)


-- 
1012255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hatari
Version: 2.3.1+dfsg
Severity: serious
Tags: ftbfs patch upstream
Justification: fails to build from source
X-Debbugs-Cc: tienhock@starfivetech.com

Dear Maintainer,

hatari is FTBFS due to a header conflict with REG_A0 that is already
defined in RISC-V's header.

Patch to fix the build is attached. Build test run on StarFive's
VisionFive board.

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: riscv64

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

Versions of packages hatari depends on:
ii  gir1.2-gtk-3.0  3.24.24-4+deb11u2
ii  libc6   2.31-13+deb11u3
ii  libpng16-16 1.6.37-3
pn  libportaudio2   
ii  libreadline88.1-1
ii  libsdl2-2.0-0   2.0.14+dfsg2-3
ii  libudev1247.3-7
ii  libx11-62:1.7.2-1
ii  python3 3.9.2-3
ii  python3-gi  3.38.0-2
ii  zlib1g  1:1.2.11.dfsg-2+deb11u1

Versions of packages hatari recommends:
ii  binfmt-support  2.2.1-1

Versions of packages hatari suggests:
ii  dosfstools  4.2-1
pn  mtools  
ii  unzip   6.0-26
01-fix-conftypes-py-build-path.diff  fix-rega0-for-riscv.patch
07-fix-python-ui-doc-install.patch   series
09-fix-hconsole-doc-install.patch
root@v5:~/hatari/hatari-2.3.1+dfsg# cat debian/patches/fix-rega0-for-riscv.patch
Fix issue where REG_A0 is already defined by riscv64 platform
Index: hatari-2.3.1+dfsg/src/includes/m68000.h
===
--- hatari-2.3.1+dfsg.orig/src/includes/m68000.h2020-12-26 
21:50:12.0 +
+++ hatari-2.3.1+dfsg/src/includes/m68000.h 2022-05-26 01:37:55.028838540 
+
@@ -26,6 +26,9 @@
 #include "cycInt.h"
 #include "log.h"

+#ifdef REG_A0
+#undef REG_A0
+#endif

 /* 68000 Register defines */
 enum {

--- End Message ---
--- Begin Message ---
Source: hatari
Source-Version: 2.3.1+dfsg-2
Done: Teemu Hukkanen 

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

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

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

Debian distribution maintenance software
pp.
Teemu Hukkanen  (supplier of updated hatari 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, 24 Jun 2022 22:01:17 +0300
Source: hatari
Architecture: source
Version: 2.3.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Teemu Hukkanen 
Changed-By: Teemu Hukkanen 
Closes: 1012255
Changes:
 hatari (2.3.1+dfsg-2) unstable; urgency=medium
 .
   * Add patch fixing FTBFS on RISC-V (Closes: #1012255)
 Thanks to Tien Hock Loh 
Checksums-Sha1:
 a89932f409e55a07d9bb04065184848d7c60e1ee 1854 hatari_2.3.1+dfsg-2.dsc
 b84ea7bcf863d31333dfafb07ea9c037f4868f1e 9608 hatari_2.3.1+dfsg-2.debian.tar.xz
 75ca8de9b91e9b838e4e8c87ba1d3fdeaa6274a5 12020 
hatari_2.3.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 41810109caad99b1d93e28a22667b0ac3126097097d66139bf57380f6a9f3911 1854 
hatari_2.3.1+dfsg-2.dsc
 348cfcafb44e242d73d13a0b07252f620047452734512d110a14a9f4255b1100 9608 
hatari_2.3.1+dfsg-2.debian.tar.xz
 c0cb68e2cbc2fbe8b2580a938210e4d2a9b67b19b2cbc68c7a194f890ab2d1fd 12020 
hatari_2.3.1+dfsg-2_source.buildinfo
Files:
 8d79e86bc66ae92710c37207755ed41d 1854 otherosfs optional 
hatari_2.3.1+dfsg-2.dsc
 87f6eb04d79d8f39e5eb700cf446346f 9608 otherosfs optional 
hatari_2.3.1+dfsg-2.debian.tar.xz
 

Bug#1005247: marked as done (Object::Pad::SlotAttr::Trigger is replaced by Object::Pad::FieldAttr::Trigger)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:30:54 +
with message-id 
and subject line Bug#1013446: Removed package(s) from unstable
has caused the Debian Bug report #1005247,
regarding Object::Pad::SlotAttr::Trigger is replaced by 
Object::Pad::FieldAttr::Trigger
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.)


-- 
1005247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libobject-pad-slotattr-final-perl
Version: 0.04-2
Severity: normal
X-Debbugs-Cc: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I noticed that libobject-pad-slotattr-final-perl fails its
autopkgtests because of a deprecation warning:

autopkgtest [15:14:29]: test autodep8-perl: 
/usr/share/pkg-perl-autopkgtest/runner runtime-deps
autopkgtest [15:14:29]: test autodep8-perl: [---

#   Failed test ' /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 
produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Object::Pad::SlotAttr::Final" -e 1 2>&1 produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.
# Looks like you failed 2 tests of 4.
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 
1..4
# register_slot_attribute() is now deprecated; use register_field_attribute() 
instead at /usr/lib/x86_64-linux-gnu/perl-base/XSLoader.pm line 111.
ok 1 -  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 exited 
successfully
not ok 2 -  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 
produced no (non-whitelisted) output
# register_slot_attribute() is now deprecated; use register_field_attribute() 
instead at /usr/lib/x86_64-linux-gnu/perl-base/XSLoader.pm line 111.
ok 3 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" 
-e 1 2>&1 exited successfully
not ok 4 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Object::Pad::SlotAttr::Final" -e 1 2>&1 produced no (non-whitelisted) output
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/4 subtests 

Test Summary Report
- ---
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 512 Tests: 4 
Failed: 2)
  Failed tests:  2, 4
  Non-zero exit status: 2
Files=1, Tests=4,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.09 cusr  0.02 
csys =  0.13 CPU)
Result: FAIL
autopkgtest [15:14:29]: test autodep8-perl: ---]
autopkgtest [15:14:30]: test autodep8-perl:  - - - - - - - - - - results - - - 
- - - - - - -


This warning comes from Object::Pad 0.60 which renamed 'slots' to
'fields'.

Now in libobject-pad-slotattr-final-perl we could silence the
autopkgtest warnings or we could patch the code but still the module
and the package would be called *slot* …

So I looked at the MetaCPAN, and indeed, there is a renamed
distribution available: https://metacpan.org/dist/Object-Pad-FieldAttr-Final

I guess we should replace libobject-pad-slotattr-final-perl with
libobject-pad-fieldattr-final-perl …


Well, and this is not the only package with 'slot':

% apt-cache --names-only search libobject-pad-slot | grep -v dbgsym
libobject-pad-slotattr-final-perl - declare Object::Pad slots readonly after 
construction
libobject-pad-slotattr-isa-perl - apply class type constraints to Object::Pad 
slots
libobject-pad-slotattr-lazyinit-perl - lazily initialise Object::Pad slots at 
first read
libobject-pad-slotattr-trigger-perl - invoke an instance method after a :writer 
accessor

 
Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmH+iWJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbCnA/8C/FumDm2bljlUNhzbbrj00nUSB1BMjE254opiGGF+jqHVvoPjbcRoIbg
APPkugDOgyDOa+3MeEnwPN1jpxROiJHDrKgrtY0mLmP14BDk+SbMO6S9MDzq8QV3
xNuQs0Gvmy+ZF7rJLkt3jkE31SDKl16UytHG/1KmNMieaKJj44zhaptv1mACHr4E
Bvy/avAS/vzrnqY+2g7KGno0pdxNj8tFMFdqf0FviXuUFcEqM5fgbJN/wBMDgKr5
qpmZnlXXVcgOPMRH/QF85byrll5FPcGf67Uy6t44cU9DLVM6JSsRtlctU8mzE6Ry
I3iloE2ly2Mb8dUYPRPs1dvAUlfs6N814kQrHEZ3f0AQLw1vPMRXYXFRS6Qzg6iD
CMtQt/7ql5wKfnJ5Cl2Ja5v6LOSmC+3GyPCIVkuRknXdZw0xFuF39f+nsjuRCvLp
ZBjp2/ANFI5iCYCqlS3xkOEH/f2hHA+UCnKoIAmQLQthOqByOaWFiMibT8t+8G/5
uLi1CTdRTqO+v5zyGlrWsnx8CtNlxuLkt0aZbi3glpWSbdpUYgVtumAqYtVMRUDe
aN4l0GI1qIvG6n4BnXk+caczR7jkxqP78+DwiT9utMOxsd1jJKqedQSwh9mISoPy
ttyVJuXZrvtS4gom5rZOMfmL4yEqtkAmEIE8CIk9p4vT+QU9Q2g=
=eSHN
-END PGP SIGNATURE-
--- End 

Bug#1005016: marked as done (libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is replaced by Object::Pad::FieldAttr::Final)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:29:45 +
with message-id 
and subject line Bug#1013443: Removed package(s) from unstable
has caused the Debian Bug report #1005016,
regarding libobject-pad-slotattr-final-perl: Object::Pad::SlotAttr::Final is 
replaced by Object::Pad::FieldAttr::Final
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.)


-- 
1005016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libobject-pad-slotattr-final-perl
Version: 0.04-2
Severity: normal
X-Debbugs-Cc: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I noticed that libobject-pad-slotattr-final-perl fails its
autopkgtests because of a deprecation warning:

autopkgtest [15:14:29]: test autodep8-perl: 
/usr/share/pkg-perl-autopkgtest/runner runtime-deps
autopkgtest [15:14:29]: test autodep8-perl: [---

#   Failed test ' /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 
produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Object::Pad::SlotAttr::Final" -e 1 2>&1 produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.
# Looks like you failed 2 tests of 4.
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 
1..4
# register_slot_attribute() is now deprecated; use register_field_attribute() 
instead at /usr/lib/x86_64-linux-gnu/perl-base/XSLoader.pm line 111.
ok 1 -  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 exited 
successfully
not ok 2 -  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 
produced no (non-whitelisted) output
# register_slot_attribute() is now deprecated; use register_field_attribute() 
instead at /usr/lib/x86_64-linux-gnu/perl-base/XSLoader.pm line 111.
ok 3 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" 
-e 1 2>&1 exited successfully
not ok 4 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Object::Pad::SlotAttr::Final" -e 1 2>&1 produced no (non-whitelisted) output
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/4 subtests 

Test Summary Report
- ---
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 512 Tests: 4 
Failed: 2)
  Failed tests:  2, 4
  Non-zero exit status: 2
Files=1, Tests=4,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.09 cusr  0.02 
csys =  0.13 CPU)
Result: FAIL
autopkgtest [15:14:29]: test autodep8-perl: ---]
autopkgtest [15:14:30]: test autodep8-perl:  - - - - - - - - - - results - - - 
- - - - - - -


This warning comes from Object::Pad 0.60 which renamed 'slots' to
'fields'.

Now in libobject-pad-slotattr-final-perl we could silence the
autopkgtest warnings or we could patch the code but still the module
and the package would be called *slot* …

So I looked at the MetaCPAN, and indeed, there is a renamed
distribution available: https://metacpan.org/dist/Object-Pad-FieldAttr-Final

I guess we should replace libobject-pad-slotattr-final-perl with
libobject-pad-fieldattr-final-perl …


Well, and this is not the only package with 'slot':

% apt-cache --names-only search libobject-pad-slot | grep -v dbgsym
libobject-pad-slotattr-final-perl - declare Object::Pad slots readonly after 
construction
libobject-pad-slotattr-isa-perl - apply class type constraints to Object::Pad 
slots
libobject-pad-slotattr-lazyinit-perl - lazily initialise Object::Pad slots at 
first read
libobject-pad-slotattr-trigger-perl - invoke an instance method after a :writer 
accessor

 
Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmH+iWJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbCnA/8C/FumDm2bljlUNhzbbrj00nUSB1BMjE254opiGGF+jqHVvoPjbcRoIbg
APPkugDOgyDOa+3MeEnwPN1jpxROiJHDrKgrtY0mLmP14BDk+SbMO6S9MDzq8QV3
xNuQs0Gvmy+ZF7rJLkt3jkE31SDKl16UytHG/1KmNMieaKJj44zhaptv1mACHr4E
Bvy/avAS/vzrnqY+2g7KGno0pdxNj8tFMFdqf0FviXuUFcEqM5fgbJN/wBMDgKr5
qpmZnlXXVcgOPMRH/QF85byrll5FPcGf67Uy6t44cU9DLVM6JSsRtlctU8mzE6Ry
I3iloE2ly2Mb8dUYPRPs1dvAUlfs6N814kQrHEZ3f0AQLw1vPMRXYXFRS6Qzg6iD
CMtQt/7ql5wKfnJ5Cl2Ja5v6LOSmC+3GyPCIVkuRknXdZw0xFuF39f+nsjuRCvLp
ZBjp2/ANFI5iCYCqlS3xkOEH/f2hHA+UCnKoIAmQLQthOqByOaWFiMibT8t+8G/5
uLi1CTdRTqO+v5zyGlrWsnx8CtNlxuLkt0aZbi3glpWSbdpUYgVtumAqYtVMRUDe
aN4l0GI1qIvG6n4BnXk+caczR7jkxqP78+DwiT9utMOxsd1jJKqedQSwh9mISoPy
ttyVJuXZrvtS4gom5rZOMfmL4yEqtkAmEIE8CIk9p4vT+QU9Q2g=
=eSHN
-END 

Bug#1005245: marked as done (Object::Pad::SlotAttr::Isa is replaced by Object::Pad::FieldAttr::Isa)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:30:21 +
with message-id 
and subject line Bug#1013444: Removed package(s) from unstable
has caused the Debian Bug report #1005245,
regarding Object::Pad::SlotAttr::Isa is replaced by Object::Pad::FieldAttr::Isa
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.)


-- 
1005245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005245
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libobject-pad-slotattr-final-perl
Version: 0.04-2
Severity: normal
X-Debbugs-Cc: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I noticed that libobject-pad-slotattr-final-perl fails its
autopkgtests because of a deprecation warning:

autopkgtest [15:14:29]: test autodep8-perl: 
/usr/share/pkg-perl-autopkgtest/runner runtime-deps
autopkgtest [15:14:29]: test autodep8-perl: [---

#   Failed test ' /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 
produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Object::Pad::SlotAttr::Final" -e 1 2>&1 produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.
# Looks like you failed 2 tests of 4.
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 
1..4
# register_slot_attribute() is now deprecated; use register_field_attribute() 
instead at /usr/lib/x86_64-linux-gnu/perl-base/XSLoader.pm line 111.
ok 1 -  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 exited 
successfully
not ok 2 -  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 
produced no (non-whitelisted) output
# register_slot_attribute() is now deprecated; use register_field_attribute() 
instead at /usr/lib/x86_64-linux-gnu/perl-base/XSLoader.pm line 111.
ok 3 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" 
-e 1 2>&1 exited successfully
not ok 4 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Object::Pad::SlotAttr::Final" -e 1 2>&1 produced no (non-whitelisted) output
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/4 subtests 

Test Summary Report
- ---
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 512 Tests: 4 
Failed: 2)
  Failed tests:  2, 4
  Non-zero exit status: 2
Files=1, Tests=4,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.09 cusr  0.02 
csys =  0.13 CPU)
Result: FAIL
autopkgtest [15:14:29]: test autodep8-perl: ---]
autopkgtest [15:14:30]: test autodep8-perl:  - - - - - - - - - - results - - - 
- - - - - - -


This warning comes from Object::Pad 0.60 which renamed 'slots' to
'fields'.

Now in libobject-pad-slotattr-final-perl we could silence the
autopkgtest warnings or we could patch the code but still the module
and the package would be called *slot* …

So I looked at the MetaCPAN, and indeed, there is a renamed
distribution available: https://metacpan.org/dist/Object-Pad-FieldAttr-Final

I guess we should replace libobject-pad-slotattr-final-perl with
libobject-pad-fieldattr-final-perl …


Well, and this is not the only package with 'slot':

% apt-cache --names-only search libobject-pad-slot | grep -v dbgsym
libobject-pad-slotattr-final-perl - declare Object::Pad slots readonly after 
construction
libobject-pad-slotattr-isa-perl - apply class type constraints to Object::Pad 
slots
libobject-pad-slotattr-lazyinit-perl - lazily initialise Object::Pad slots at 
first read
libobject-pad-slotattr-trigger-perl - invoke an instance method after a :writer 
accessor

 
Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmH+iWJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbCnA/8C/FumDm2bljlUNhzbbrj00nUSB1BMjE254opiGGF+jqHVvoPjbcRoIbg
APPkugDOgyDOa+3MeEnwPN1jpxROiJHDrKgrtY0mLmP14BDk+SbMO6S9MDzq8QV3
xNuQs0Gvmy+ZF7rJLkt3jkE31SDKl16UytHG/1KmNMieaKJj44zhaptv1mACHr4E
Bvy/avAS/vzrnqY+2g7KGno0pdxNj8tFMFdqf0FviXuUFcEqM5fgbJN/wBMDgKr5
qpmZnlXXVcgOPMRH/QF85byrll5FPcGf67Uy6t44cU9DLVM6JSsRtlctU8mzE6Ry
I3iloE2ly2Mb8dUYPRPs1dvAUlfs6N814kQrHEZ3f0AQLw1vPMRXYXFRS6Qzg6iD
CMtQt/7ql5wKfnJ5Cl2Ja5v6LOSmC+3GyPCIVkuRknXdZw0xFuF39f+nsjuRCvLp
ZBjp2/ANFI5iCYCqlS3xkOEH/f2hHA+UCnKoIAmQLQthOqByOaWFiMibT8t+8G/5
uLi1CTdRTqO+v5zyGlrWsnx8CtNlxuLkt0aZbi3glpWSbdpUYgVtumAqYtVMRUDe
aN4l0GI1qIvG6n4BnXk+caczR7jkxqP78+DwiT9utMOxsd1jJKqedQSwh9mISoPy
ttyVJuXZrvtS4gom5rZOMfmL4yEqtkAmEIE8CIk9p4vT+QU9Q2g=
=eSHN
-END PGP SIGNATURE-
--- End Message ---

Bug#1005246: marked as done (Object::Pad::SlotAttr::LazyInit is replaced by Object::Pad::FieldAttr::LazyInit)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:31:47 +
with message-id 
and subject line Bug#1013445: Removed package(s) from unstable
has caused the Debian Bug report #1005246,
regarding Object::Pad::SlotAttr::LazyInit is replaced by 
Object::Pad::FieldAttr::LazyInit
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.)


-- 
1005246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libobject-pad-slotattr-final-perl
Version: 0.04-2
Severity: normal
X-Debbugs-Cc: Jonas Smedegaard 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I noticed that libobject-pad-slotattr-final-perl fails its
autopkgtests because of a deprecation warning:

autopkgtest [15:14:29]: test autodep8-perl: 
/usr/share/pkg-perl-autopkgtest/runner runtime-deps
autopkgtest [15:14:29]: test autodep8-perl: [---

#   Failed test ' /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 
produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Object::Pad::SlotAttr::Final" -e 1 2>&1 produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 107.
# Looks like you failed 2 tests of 4.
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 
1..4
# register_slot_attribute() is now deprecated; use register_field_attribute() 
instead at /usr/lib/x86_64-linux-gnu/perl-base/XSLoader.pm line 111.
ok 1 -  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 exited 
successfully
not ok 2 -  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" -e 1 2>&1 
produced no (non-whitelisted) output
# register_slot_attribute() is now deprecated; use register_field_attribute() 
instead at /usr/lib/x86_64-linux-gnu/perl-base/XSLoader.pm line 111.
ok 3 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w -M"Object::Pad::SlotAttr::Final" 
-e 1 2>&1 exited successfully
not ok 4 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"Object::Pad::SlotAttr::Final" -e 1 2>&1 produced no (non-whitelisted) output
Dubious, test returned 2 (wstat 512, 0x200)
Failed 2/4 subtests 

Test Summary Report
- ---
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 512 Tests: 4 
Failed: 2)
  Failed tests:  2, 4
  Non-zero exit status: 2
Files=1, Tests=4,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.09 cusr  0.02 
csys =  0.13 CPU)
Result: FAIL
autopkgtest [15:14:29]: test autodep8-perl: ---]
autopkgtest [15:14:30]: test autodep8-perl:  - - - - - - - - - - results - - - 
- - - - - - -


This warning comes from Object::Pad 0.60 which renamed 'slots' to
'fields'.

Now in libobject-pad-slotattr-final-perl we could silence the
autopkgtest warnings or we could patch the code but still the module
and the package would be called *slot* …

So I looked at the MetaCPAN, and indeed, there is a renamed
distribution available: https://metacpan.org/dist/Object-Pad-FieldAttr-Final

I guess we should replace libobject-pad-slotattr-final-perl with
libobject-pad-fieldattr-final-perl …


Well, and this is not the only package with 'slot':

% apt-cache --names-only search libobject-pad-slot | grep -v dbgsym
libobject-pad-slotattr-final-perl - declare Object::Pad slots readonly after 
construction
libobject-pad-slotattr-isa-perl - apply class type constraints to Object::Pad 
slots
libobject-pad-slotattr-lazyinit-perl - lazily initialise Object::Pad slots at 
first read
libobject-pad-slotattr-trigger-perl - invoke an instance method after a :writer 
accessor

 
Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmH+iWJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbCnA/8C/FumDm2bljlUNhzbbrj00nUSB1BMjE254opiGGF+jqHVvoPjbcRoIbg
APPkugDOgyDOa+3MeEnwPN1jpxROiJHDrKgrtY0mLmP14BDk+SbMO6S9MDzq8QV3
xNuQs0Gvmy+ZF7rJLkt3jkE31SDKl16UytHG/1KmNMieaKJj44zhaptv1mACHr4E
Bvy/avAS/vzrnqY+2g7KGno0pdxNj8tFMFdqf0FviXuUFcEqM5fgbJN/wBMDgKr5
qpmZnlXXVcgOPMRH/QF85byrll5FPcGf67Uy6t44cU9DLVM6JSsRtlctU8mzE6Ry
I3iloE2ly2Mb8dUYPRPs1dvAUlfs6N814kQrHEZ3f0AQLw1vPMRXYXFRS6Qzg6iD
CMtQt/7ql5wKfnJ5Cl2Ja5v6LOSmC+3GyPCIVkuRknXdZw0xFuF39f+nsjuRCvLp
ZBjp2/ANFI5iCYCqlS3xkOEH/f2hHA+UCnKoIAmQLQthOqByOaWFiMibT8t+8G/5
uLi1CTdRTqO+v5zyGlrWsnx8CtNlxuLkt0aZbi3glpWSbdpUYgVtumAqYtVMRUDe
aN4l0GI1qIvG6n4BnXk+caczR7jkxqP78+DwiT9utMOxsd1jJKqedQSwh9mISoPy
ttyVJuXZrvtS4gom5rZOMfmL4yEqtkAmEIE8CIk9p4vT+QU9Q2g=
=eSHN
-END PGP SIGNATURE-
--- End 

Processed: merge groovy RC bugs

[Debian Bug Tracking System]

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

> reassign 1013522 groovy
Bug #1013522 [src:groovy] groovy: FTBFS: IO.java:22: error: cannot find symbol
Bug reassigned from package 'src:groovy' to 'groovy'.
No longer marked as found in versions groovy/2.4.21-1.
Ignoring request to alter fixed versions of bug #1013522 to the same values 
previously set
> forcemerge 1013355 1013522
Bug #1013355 [groovy] groovy: FTBFS with jansi 2.4.0-1
Bug #1013355 [groovy] groovy: FTBFS with jansi 2.4.0-1
Added tag(s) bookworm, sid, and ftbfs.
Bug #1013522 [groovy] groovy: FTBFS: IO.java:22: error: cannot find symbol
Marked as found in versions groovy/2.4.21-1.
Merged 1013355 1013522
> thanks
Stopping processing here.

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

Bug#1013611: marked as done (surefire: FTBFS: [ERROR] /<>/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/DefaultReporterFactory.java:[476,36] error: cannot fi

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 19:19:19 +
with message-id 
and subject line Bug#1013611: fixed in surefire 2.22.3-2
has caused the Debian Bug report #1013611,
regarding surefire: FTBFS: [ERROR] 
/<>/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/DefaultReporterFactory.java:[476,36]
 error: cannot find symbol
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.)


-- 
1013611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: surefire
Version: 2.22.3-1
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):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibsurefire-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.surefire:surefire-api:jar:2.22.3
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: com.google.code.findbugs:jsr305:jar -> version (?) vs debian @ 
> line 56, column 15
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.surefire:surefire-junit47:jar:2.22.3
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 120, column 
> 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.22.3
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-plugin-plugin is missing. @ line 55, column 12
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.maven.plugins:maven-surefire-report-plugin:maven-plugin:2.22.3
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-plugin-plugin is missing. @ line 112, column 12
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING] 
> [WARNING] The project org.apache.maven.surefire:surefire-grouper:jar:2.22.3 
> uses prerequisites which is only intended for maven-plugin projects but not 
> for non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [WARNING] The project 
> org.apache.maven.surefire:maven-surefire-common:jar:2.22.3 uses prerequisites 
> which is only intended for maven-plugin projects but not for non maven-plugin 
> projects. For such purposes you should use the maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [WARNING] The project 
> org.apache.maven.surefire:surefire-report-parser:jar:2.22.3 uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Apache Maven Surefire  
> [pom]
> [INFO] SureFire Logger API

Processed (with 1 error): merge groovy RC bugs

[Debian Bug Tracking System]

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

> forcemerge 1013355 1013522
Bug #1013355 [groovy] groovy: FTBFS with jansi 2.4.0-1
Unable to merge bugs because:
package of #1013522 is 'src:groovy' not 'groovy'
Failed to forcibly merge 1013355: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: Bug#1013611 marked as pending in surefire

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013611 [src:surefire] surefire: FTBFS: [ERROR] 
/<>/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/DefaultReporterFactory.java:[476,36]
 error: cannot find symbol
Added tag(s) pending.

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

Bug#1013611: marked as pending in surefire

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #1013611 in surefire 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/java-team/surefire/-/commit/838414d435c757e312271279c1e184167a8e5daa


Fix FTBFS with maven-shared-utils 3.3.4.

Closes: #1013611


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013611

Bug#1013526: libtickit-widget-scrollbox-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255

[gregor herrmann]

Control: tag -1 + unreproducible

On Fri, 24 Jun 2022 12:07:04 +0200, Lucas Nussbaum wrote:

> Source: libtickit-widget-scrollbox-perl
> Version: 0.11-1
> 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.

> > malloc_consolidate(): unaligned fastbin chunk detected
> > t/02input-key.t . 
> > ok 1 - start is 0 initially
> > ok 2 - hextent start is 0 initially
> > ok 3 - start moves down +1 after 
> > ok 4 - start moves down +12 after 
> > ok 5 - start moves up -1 after 
> > ok 6 - start moves up -12 after 
> > ok 7 - start moves to 76 after 
> > ok 8 - start moves to 0 after 
> > ok 9 - start moves right +1 after 
> > ok 10 - start moves right +39 after 
> > ok 11 - start moves up -1 after 
> > ok 12 - start moves up -39 after 
> > ok 13 - start moves to 121 after 
> > ok 14 - start moves to 0 after 
> > 1..14
> > All 14 subtests passed 

I can't reproduce this failure; log attached.

Any ideas, anyone?


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
   `-   
dh clean
   dh_clean
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building libtickit-widget-scrollbox-perl using existing 
./libtickit-widget-scrollbox-perl_0.11.orig.tar.gz
dpkg-source: info: building libtickit-widget-scrollbox-perl in 
libtickit-widget-scrollbox-perl_0.11-1.debian.tar.xz
dpkg-source: info: building libtickit-widget-scrollbox-perl in 
libtickit-widget-scrollbox-perl_0.11-1.dsc
I: Generated dsc will be overwritten by build result; not generating 
changes file
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.72275
I: forking: cp -al /var/cache/pbuilder/base.cow 
/var/cache/pbuilder/build/cow.72275
I: removed stale ilistfile /var/cache/pbuilder/build/cow.72275/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.72275 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace 
/var/cache/pbuilder/build/cow.72275 --buildresult 
/home/gregoa/src/git-pkg-perl/meta/packages/build-area --mirror 
http://ftp.ch.debian.org/debian --distribution sid --extrapackages ' eatmydata' 
--no-targz --internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.72275 
cow-shell' 
/home/gregoa/src/git-pkg-perl/meta/packages/build-area/libtickit-widget-scrollbox-perl_0.11-1.dsc
I: Running in no-targz mode
W: pbuilder: network will not be disabled during build!
I: Current time: Fri Jun 24 20:58:38 CEST 2022
I: pbuilder-time-stamp: 1656097118
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage 
for details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: Mounting /var/cache/pbuilder/ccache
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Setting up ccache
I: Copying source file
I: copying 
[/home/gregoa/src/git-pkg-perl/meta/packages/build-area/libtickit-widget-scrollbox-perl_0.11-1.dsc]
I: copying 
[/home/gregoa/src/git-pkg-perl/meta/packages/build-area/libtickit-widget-scrollbox-perl_0.11.orig.tar.gz]
I: copying 
[/home/gregoa/src/git-pkg-perl/meta/packages/build-area/libtickit-widget-scrollbox-perl_0.11-1.debian.tar.xz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package 
(libtickit-widget-scrollbox-perl_0.11-1.dsc)
dpkg-source: info: extracting libtickit-widget-scrollbox-perl in 
libtickit-widget-scrollbox-perl-0.11
dpkg-source: info: unpacking libtickit-widget-scrollbox-perl_0.11.orig.tar.gz
dpkg-source: info: unpacking 
libtickit-widget-scrollbox-perl_0.11-1.debian.tar.xz
I: Not using root during the build.
I: Installing the build-deps
I: user script /var/cache/pbuilder/build/cow.72275/tmp/hooks/D10-man-db 
starting
I: Preseed man-db/auto-update to false
I: user script /var/cache/pbuilder/build/cow.72275/tmp/hooks/D10-man-db 
f

Processed: Re: Bug#1013526: libtickit-widget-scrollbox-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 255

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + unreproducible
Bug #1013526 [src:libtickit-widget-scrollbox-perl] 
libtickit-widget-scrollbox-perl: FTBFS: dh_auto_test: error: /usr/bin/perl 
Build test --verbose 1 returned exit code 255
Added tag(s) unreproducible.

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

Bug#1011978: marked as done (kakoune FTBFS on big endian)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 17:49:04 +
with message-id 
and subject line Bug#1011978: fixed in kakoune 2021.11.08-2
has caused the Debian Bug report #1011978,
regarding kakoune FTBFS on big endian
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.)


-- 
1011978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kakoune
Version: 2021.11.08-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: debian-s...@lists.debian.org
Control: block 1010335 by -1

https://buildd.debian.org/status/logs.php?pkg=kakoune=2021.11.08-1

...
Fatal error: assert failed "hash_data(data, strlen(data)) == 0xf816f95b" at 
hash.cc:76
...


debian-s390 list is Cc'ed on this bug.
--- End Message ---
--- Begin Message ---
Source: kakoune
Source-Version: 2021.11.08-2
Done: Peter Pentchev 

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

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

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

Debian distribution maintenance software
pp.
Peter Pentchev  (supplier of updated kakoune 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, 24 Jun 2022 20:23:47 +0300
Source: kakoune
Architecture: source
Version: 2021.11.08-2
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Closes: 1011978 1012956
Changes:
 kakoune (2021.11.08-2) unstable; urgency=medium
 .
   * Add the murmurhash-endian patch to fix the build on s390x.
 Closes: #1011978
   * Add the iterator and validate-alpha patches to fix the build with GCC 12.
 Closes: #1012956
   * Declare compliance with Policy 4.6.1 with no changes.
Checksums-Sha1:
 f5e211279e0b746be2ccc436e766068ce4a5ab0e 2174 kakoune_2021.11.08-2.dsc
 9f92ce72d8778ca5e27f112661de286ca5b6d615 13416 
kakoune_2021.11.08-2.debian.tar.xz
Checksums-Sha256:
 0f7fce8e446b75ffb8490641106bf8f8349e76d75e7e706dccb733bd62d7e46e 2174 
kakoune_2021.11.08-2.dsc
 f6a53147e2ed09ba45e8fdeba5cdcbfb4ff727a295616697d2ac0e58dcc58873 13416 
kakoune_2021.11.08-2.debian.tar.xz
Files:
 42568e3a414bb6a202c2d3f548843ff6 2174 editors optional kakoune_2021.11.08-2.dsc
 6d4c3b21ec7a2b174ac266882f0a6813 13416 editors optional 
kakoune_2021.11.08-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmK18+sQHHJvYW1AZGVi
aWFuLm9yZwAKCRBlHu+wJSffEx9wEADONwFbUSOdglYXXKMLfI7+nlSe2gJ7hKpt
kTrKKVmlePwvHP5QgolZJkHMh+uVa9vkuA7v3yVzsnL2QuspKaMgNZQ/dQD1FdqZ
LBNyKX2DK8KJnuT6nexWTJvPr8QvD0PGpbh+j79LJ0k9ZLC+eZUeIjv4+ZxZ6xfu
wmjAb5yPMPVHMUcYiyz2YfFjh/YYpaAMl+lvWPbYgiCbwYR3Gg0iLXuYICC1y74x
2f2I5Hajyy1UyxMBdJpSgWNNkUpoA2ff71pp76BswjbX398i7P9M7Q2z7c/yOTiS
IGBmm7nY8YfdB+TpVyPHGTXJ9nTveKFnozrw4oLOuLHMYHYeUimHaS+/l4VKYdsc
Gz/YQs49n8w1pVm27Sn44edqi42WFhIymkgQ6KqKqAZP/znlQQHAXkvyjI8rj0bB
iZTFZlTVZwEYH2V5sKt7nkBkABIvRUi/yeilq49AaSYXTSkyZmvFAGwa8qqdCEw4
Hk9V9cYEZ0JVxLGYv6w8yAN3bxT2AWh7JTMxuM0m4fZNRD2MTap3/F25NniwaN/Z
3xQU49+7lpKdAhqbGVv+XtOG3t4dHQwvaPnxsq9NV87VuNy7bqcDN2NF8N1KrvOP
cx5dKlZFGsRqLW1lKUVCCagBQwyxb4Cw6hLaL9FFaegfeY2A+LjwLcoXIEt8nPg0
e7TKMYKdeg==
=g80n
-END PGP SIGNATURE End Message ---

Bug#1013451: openssh-client: double free or corruption

[Antonio]

GNU gdb (Debian 12.1-2) 12.1
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 


This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ssh...
Reading symbols from 
/usr/lib/debug/.build-id/2a/f97f1bdaee7cdffdc6275b9e837796ba8c0d30.debug...

(gdb) r
Starting program: /usr/bin/ssh-p7386 localhost
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
double free or corruption (!prev)

Program received signal SIGABRT, Aborted.
__GI_raise(sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
49  ../sysdeps/unix/sysv/linux/raise.c: File o directory non esistente.
(gdb) br
Breakpoint 1 at 0x7785f8a1: file ../sysdeps/unix/sysv/linux/raise.c, 
line 49.

(gdb) bt
#0 __GI_raise(sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#1 0x77849546in __GI_abort() at abort.c:79
#2 0x778a0eb8in __libc_message(action=action@entry=do_abort,
fmt=fmt@entry=0x779bea78 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#3 0x778a891ain malloc_printerr(
str=str@entry=0x779c0fa0 "double free or corruption (!prev)") at 
malloc.c:5628
#4 0x778aa1acin _int_free(av=0x779f5ba0 , 
p=0x556b8350,

have_lock=) at malloc.c:4550
#5 0x778ad9b4in __GI___libc_free(mem=) at 
malloc.c:3309

#6 0x77b2bd2cin ??() from /usr/lib/x86_64-linux-gnu/libcrypto.so.3
#7 0x77b1858ein BN_mod_exp_mont_consttime_x2() from 
/usr/lib/x86_64-linux-gnu/libcrypto.so.3

#8 0x77c77b6din ??() from /usr/lib/x86_64-linux-gnu/libcrypto.so.3
#9 0x77c79010in ??() from /usr/lib/x86_64-linux-gnu/libcrypto.so.3
#10 0x77c7d0d1in RSA_sign() from 
/usr/lib/x86_64-linux-gnu/libcrypto.so.3
#11 0x555d6ee0in ssh_rsa_sign(key=key@entry=0x556c89e0, 
sigp=sigp@entry=0x7fffc3c0,
lenp=lenp@entry=0x7fffc3c8, data=data@entry=0x556b6e70 "", 
datalen=,
alg_ident=alg_ident@entry=0x556b2da0 "rsa-sha2-512") at 
../../ssh-rsa.c:206
#12 0x5559a65ein sshkey_sign(key=key@entry=0x556c89e0, 
sigp=sigp@entry=0x7fffc3c0,
lenp=lenp@entry=0x7fffc3c8, data=data@entry=0x556b6e70 "", 
datalen=datalen@entry=542,
alg=alg@entry=0x556b2da0 "rsa-sha2-512", sk_provider=0x556a7770 
"internal", sk_pin=0x0,

compat=67108864) at ../../sshkey.c:2787
#13 0x555806acin identity_sign(alg=0x556b2da0 
"rsa-sha2-512", compat=67108864,
datalen=542, data=0x556b6e70 "", lenp=0x7fffc3c8, 
sigp=0x7fffc3c0, id=0x556bb450)

   at ../../sshconnect2.c:1432
#14 sign_and_send_pubkey(ssh=ssh@entry=0x556a4ad0, 
id=id@entry=0x556bb450)

   at ../../sshconnect2.c:1602
#15 0x55583752in input_userauth_pk_ok(type=, 
seq=,

ssh=0x556a4ad0) at ../../sshconnect2.c:830
#16 0x555c95c6in ssh_dispatch_run(ssh=ssh@entry=0x556a4ad0, 
mode=mode@entry=0,

done=done@entry=0x7fffc578) at ../../dispatch.c:113
#17 0x555c9719in 
ssh_dispatch_run_fatal(ssh=ssh@entry=0x556a4ad0, mode=mode@entry=0,

done=done@entry=0x7fffc578) at ../../dispatch.c:133
--Type  for more, q to quit, c to continue without paging--
#18 0x55582906in ssh_userauth2(ssh=ssh@entry=0x556a4ad0,
local_user=local_user@entry=0x556a8850 "root",
server_user=server_user@entry=0x556a8890 "root", 
host=host@entry=0x556b2390 "localhost",
sensitive=sensitive@entry=0x5565c390 ) at 
../../sshconnect2.c:557

#19 0x5557c267in ssh_login(ssh=0x556a4ad0,
sensitive=sensitive@entry=0x5565c390 , 
orighost=,
hostaddr=hostaddr@entry=0x5565c3a0 , port=, 
pw=,

timeout_ms=-1000, cinfo=0x556ac190) at ../../sshconnect.c:1573
#20 0x55561dfain main(ac=, av=) at 
../../ssh.c:1661

Bug#1013523: marked as done (libredis-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 1)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 16:50:06 +
with message-id 
and subject line Bug#1013523: fixed in libredis-perl 2:1.9990-2
has caused the Debian Bug report #1013523,
regarding libredis-perl: FTBFS: dh_auto_test: error: /usr/bin/perl Build test 
--verbose 1 returned exit code 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.)


-- 
1013523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libredis-perl
Version: 2:1.9990-1
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):
> make[1]: Entering directory '/<>'
> # make the default explicit
> USE_SSL=0 dh_auto_test
>   /usr/bin/perl Build test --verbose 1
> t/00-compile.t ... 
> 1..4
> ok 1 - Redis.pm loaded ok
> ok 2 - Redis/Hash.pm loaded ok
> ok 3 - Redis/List.pm loaded ok
> ok 4 - Redis/Sentinel.pm loaded ok
> ok
> t/01-basic.t . 
> ok 1 - Got an unconnected object
> ok 2 - ping doesn't work yet
> ok 3 - ping works after connection
> ok 4 - connected to our test redis-server
> ok 5 - ping
> ok 6 - set foo => bar
> ok 7 - setnx foo => bar fails
> ok 8 - get foo = bar
> ok 9 - set foo => ""
> ok 10 - get foo = ""
> ok 11 - set foo => baz
> ok 12 - get foo = baz
> ok 13 - assume $eur is wide character
> ok 14 - accepts only binary data, thus crashes on strings with characters > 
> 255
> ok 15 - .. and crashes on syswrite call
> ok 16 - .. and does not write actual data
> ok 17 - set test-undef
> ok 18 - exists undef
> ok 19 - set with value size 1 ok
> ok 20 - ... and get was ok to
> ok 21 - set with value size 10 ok
> ok 22 - ... and get was ok to
> ok 23 - set with value size 50 ok
> ok 24 - ... and get was ok to
> ok 25 - set with value size 100 ok
> ok 26 - ... and get was ok to
> ok 27 - set with value size 250 ok
> ok 28 - ... and get was ok to
> ok 29 - exists non-existant
> ok 30 - get non-existant
> ok 31 - key-next = 0
> ok 32 - key-left
> ok 33 - mget
> ok 34 - set key-0
> ok 35 - exists key-0
> ok 36 - get key-0
> ok 37 - incr
> ok 38 - decr
> ok 39 - set key-1
> ok 40 - exists key-1
> ok 41 - get key-1
> ok 42 - incr
> ok 43 - decr
> ok 44 - set key-2
> ok 45 - exists key-2
> ok 46 - get key-2
> ok 47 - incr
> ok 48 - decr
> ok 49 - set key-3
> ok 50 - exists key-3
> ok 51 - get key-3
> ok 52 - incr
> ok 53 - decr
> ok 54 - key-next
> ok 55 - test-incrby
> ok 56 - test-decry
> ok 57 - incrby 3
> ok 58 - decrby 7
> ok 59 - incrby 3
> ok 60 - decrby 7
> ok 61 - incrby 3
> ok 62 - decrby 7
> ok 63 - del key-next
> ok 64 - del key-left
> ok 65 - del non-existing
> ok 66 - type
> ok 67 - key-*
> ok 68 - keys
> ok 69 - randomkey
> ok 70 - rename
> ok 71 - exists test-renamed
> ok 72 - rename to existing key
> ok 73 - dbsize
> ok 74 - Error responses throw exception
> ok 75 - rpush
> ok 76 - rpush
> ok 77 - rpush
> ok 78 - lpush
> ok 79 - lpush
> ok 80 - type
> ok 81 - llen
> ok 82 - lrange
> ok 83 - ltrim
> ok 84 - llen after ltrim
> ok 85 - lindex
> ok 86 - lindex
> ok 87 - lset
> ok 88 - verified
> ok 89 - lrem
> ok 90 - llen after lrem
> ok 91 - lpop
> ok 92 - rpop
> ok 93 - sadd
> ok 94 - sadd
> ok 95 - scard
> ok 96 - sismember
> ok 97 - type is set
> ok 98 - srem
> ok 99 - srem again
> ok 100 - scard
> ok 101 - sinter
> ok 102 - sinterstore
> ok 103 - cardinality of intersection
> ok 104 - sdiff
> ok 105 - sdiffstore
> ok 106 - cardinality of diff
> ok 107 - sunion
> ok 108 - sunionstore
> ok 109 - cardinality of union
> ok 110 - srandmember result is defined
> ok 111
> ok 112 - spop result is defined
> ok 113
> ok 114 - new cardinality of union
> ok 115 - smembers
> ok 116 - repeated smove depleted source
> ok 117 - repeated smove populated destination
> ok 118 - smembers
> ok 119
> ok 120
> ok 121
> ok 122
> ok 123
> ok 124
> ok 125
> ok 126
> ok 127
> ok 128
> ok 129
> ok 130
> ok 131
> ok 132
> ok 133
> ok 134
> ok 135
> ok 136
> ok 137
> o

Bug#1013546: marked as done (starjava-vo: FTBFS: [javac] /<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:1286: error: cannot find symbol)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 16:33:01 +
with message-id 
and subject line Bug#1013546: fixed in starjava-vo 0.2+2022.01.20-2
has caused the Debian Bug report #1013546,
regarding starjava-vo: FTBFS: [javac] 
/<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:1286: error: 
cannot find symbol
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.)


-- 
1013546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: starjava-vo
Version: 0.2+2022.01.20-1
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):
> make[1]: Entering directory '/<>'
> ant jars
> Buildfile: /<>/build.xml
> 
> prepare:
>[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been 
> set to 1643641869
> 
> check_packages:
> 
> build:
> [mkdir] Created dir: /<>/build/classes
> [javac] Compiling 112 source files to /<>/build/classes
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/DoubleValueField.java:101: 
> warning: [deprecation] Double(double) in Double has been deprecated
> [javac] val = new Double( getValue() );
> [javac]   ^
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/DoubleValueField.java:168: 
> warning: [deprecation] Double(double) in Double has been deprecated
> [javac] getEntryField().setText( vc.unconvertValue( new 
> Double( value ) ) );
> [javac] ^
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:108: warning: 
> [deprecation] Event in java.awt has been deprecated
> [javac] KeyStroke.getKeyStroke( KeyEvent.VK_Z, Event.CTRL_MASK ),
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:109: warning: 
> [deprecation] Event in java.awt has been deprecated
> [javac] KeyStroke.getKeyStroke( KeyEvent.VK_Z, Event.META_MASK ),
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:112: warning: 
> [deprecation] Event in java.awt has been deprecated
> [javac] KeyStroke.getKeyStroke( KeyEvent.VK_Z, Event.CTRL_MASK
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:113: warning: 
> [deprecation] Event in java.awt has been deprecated
> [javac]  | Event.SHIFT_MASK ),
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:114: warning: 
> [deprecation] Event in java.awt has been deprecated
> [javac] KeyStroke.getKeyStroke( KeyEvent.VK_Z, Event.META_MASK
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:115: warning: 
> [deprecation] Event in java.awt has been deprecated
> [javac]  | Event.SHIFT_MASK ),
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:116: warning: 
> [deprecation] Event in java.awt has been deprecated
> [javac] KeyStroke.getKeyStroke( KeyEvent.VK_Y, Event.CTRL_MASK ),
> [javac]^
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:1286: error: 
> cannot find symbol
> [javac] int iline = tmerr.getErrorLine();
> [javac]  ^
> [javac]   symbol:   method getErrorLine()
> [javac]   location: variable tmerr of type TokenMgrError
> [javac] 
> /<>/src/main/uk/ac/starlink/vo/TapQueryPanel.java:1287: error: 
> cannot find symbol
> [javac] int icol = tmerr.getErrorColumn();
> [javac] ^
> [javac]   symbol:   method getErrorColumn()
> [javac]   location: variable tmerr of type TokenMgrError
> [javac] 
>

Bug#1013602: marked as done (libauthen-sasl-cyrus-perl: FTBFS: /bin/sh: 1: cannot create Cyrus.pod: Permission denied)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 16:20:36 +
with message-id 
and subject line Bug#1013602: fixed in libauthen-sasl-cyrus-perl 0.13-server-13
has caused the Debian Bug report #1013602,
regarding libauthen-sasl-cyrus-perl: FTBFS: /bin/sh: 1: cannot create 
Cyrus.pod: Permission denied
to be marked as done.

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

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


-- 
1013602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013602
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libauthen-sasl-cyrus-perl
Version: 0.13-server-12
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):
> make[1]: Entering directory '/<>'
> !!! Developers: Do not edit the Cyrus.pod, edit the Cyrus.xs instead. !!!
> Make will overwrite Cyrus.pod.
> podselect Cyrus.xs > Cyrus.pod
> Running Mkbootstrap for Cyrus ()
> /bin/sh: 1: cannot create Cyrus.pod: Permission denied
> make[1]: *** [Makefile:515: Cyrus.pod] Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/libauthen-sasl-cyrus-perl_0.13-server-12_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=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: libauthen-sasl-cyrus-perl
Source-Version: 0.13-server-13
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libauthen-sasl-cyrus-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, 24 Jun 2022 17:48:26 +0200
Source: libauthen-sasl-cyrus-perl
Architecture: source
Version: 0.13-server-13
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1013602
Changes:
 libauthen-sasl-cyrus-perl (0.13-server-13) unstable; urgency=medium
 .
   * Team upload.
   * Remove Cyrus.pod during clean, it's generated during build.
 This not only fixes the permission problem at build time but also enables
 building-twice-in-a-row. (Closes: #1013602)
   * Refresh lintian override.
   * debian/rules: remove override_dh_auto_test which was just running
 dh_auto_test after a previous change.
   * Declare compliance with Debian Policy 4.6.1.
Checksums-Sha1:
 f1a35cf7dd9a8df12628288d45eafa660d8a6406 2633 
libauthen-sasl-cyrus-perl_0.13-server-13.dsc
 6694ba7b11386dab03ff9ed3391d46b00e9115e4 9204 
libauthen-sasl-cyrus-perl_0.13-server-13.debian.tar.xz
Checksums-Sha256:
 4b4cbeb4f56ab37d9096b4df4cf5214c62cb75c4fa756220b8e47a41b574e3b0 2633 
libauthen-sasl-cyrus-perl_0.13-server-13.dsc
 abbbfe2509729e0e531d3aaf4098c0f43ff59fb03cd09899fdee57c72c83bd25 9204 
libauthen-sasl-cyrus-perl_0.13-server-13.debian.tar.xz
Files:
 c3d4eaab8de07b5c4437450b7c44630b 2633 perl optional 
libauthen-sasl-cyrus-perl_0.13-server-13.dsc
 e27235c82078f83ac9fe28395b63f9aa 9204 perl optional 
libauthen-sasl-cyrus-perl_0.13-server-13.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmK13SpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYexA//eXwfmoeRIs+Z/Fu5Su/o9uNgmP

Bug#1013608: marked as done (ncbi-entrez-direct: FTBFS: cannot find package "github.com/shirou/gopsutil/mem")

[Aaron M. Ucko]

"Debian Bug Tracking System"  writes:

>* d/rules: Pass right location of gopsutil/mem (Closes: #1013608)

Thanks for looking into this report!  FWIW, I reckon it should be
possible to do away with this dependency altogether by retiring the shim
that used it in favor of system golang-github-pbnjay-memory-dev now that
the latter exists.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#1008022: marked as done (keepass2: CVE-2022-0725 information disclosure)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 17:48:55 +0200
with message-id <20220624154855.z3obc6nuvov5i...@enricozini.org>
and subject line Unreproducible
has caused the Debian Bug report #1008022,
regarding keepass2: CVE-2022-0725 information disclosure
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.)


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

Hi,

The following vulnerability was published for keepass2.

CVE-2022-0725[0]:
| A flaw was found in KeePass. The vulnerability occurs due to logging
| the plain text passwords in the system log and leads to an Information
| Exposure vulnerability. This flaw allows an attacker to interact and
| read sensitive passwords and logs.


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-0725
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0725

Please adjust the affected versions in the BTS as needed.

Steps to reproduce the problem (according
to https://bugzilla.redhat.com/show_bug.cgi?id=2052696)


Step 1: Run "journalctl -f" in a terminal window.
Step 2: Double click a password in KeePass.
Step 3: Wait for the clear timeout to trigger.

Actual results:
See your plain text password logged in the terminal window

Expected results:
Never see your plain text password logged anywhere


Only users in the systemd-journal group can use journalctl. At the moment I
can't reproduce the problem on a custom XFCE system but I have not tried GNOME
or other desktop environments yet and I suspect this problem is not limited to
RedHat or Fedora.


Regards,

Markus



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

not having been able to find a way to reproduce this on various
combinations of systems, I suppose it's time to close this as
unreproducible.


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 


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

Processed: tagging 1008022

[Debian Bug Tracking System]

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

> tags 1008022 + unreproducible
Bug #1008022 [keepass2] keepass2: CVE-2022-0725 information disclosure
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#1013602: marked as pending in libauthen-sasl-cyrus-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #1013602 in libauthen-sasl-cyrus-perl 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/perl-team/modules/packages/libauthen-sasl-cyrus-perl/-/commit/ef19622f1cc87c83a056a7f288b426990b81dc46


Remove Cyrus.pod during clean, it's generated during build.

This not only fixes the permission problem at build time but also enables
building-twice-in-a-row.

Closes: #1013602


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013602

Processed: Bug#1013602 marked as pending in libauthen-sasl-cyrus-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013602 [src:libauthen-sasl-cyrus-perl] libauthen-sasl-cyrus-perl: FTBFS: 
/bin/sh: 1: cannot create Cyrus.pod: Permission denied
Added tag(s) pending.

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

Bug#1008022: keepass2: CVE-2022-0725 information disclosure

[Enrico Zini]

On Fri, Jun 24, 2022 at 05:16:41PM +0200, Enrico Zini wrote:

> I failed to reproduce this on Gnome on a freshly installed buster
> system.
> 
> I failed to reproduce this on Gnome on a freshly installed bullseye
> system with wayland.

I also failed to reproduce this on a freshly installed stretch system,
both on an X11 and on a Wayland session


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 


signature.asc
Description: PGP signature

Bug#1013617: marked as done (starlink-pal: FTBFS: ! Undefined control sequence.)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 15:34:07 +
with message-id 
and subject line Bug#1013617: fixed in starlink-pal 0.9.8-2
has caused the Debian Bug report #1013617,
regarding starlink-pal: FTBFS: ! Undefined control sequence.
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.)


-- 
1013617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013617
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: starlink-pal
Version: 0.9.8-1
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):
> make[2]: Entering directory '/<>'
> pdflatex sun267.tex && pdflatex sun267.tex
> This is pdfTeX, Version 3.141592653-2.6-1.40.24 (TeX Live 2022/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> (./sun267.tex
> LaTeX2e <2021-11-15> patch level 1
> L3 programming layer <2022-02-24> (./starlink.cls
> Document Class: starlink 
> passing options to article..
> (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
> Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
> (/usr/share/texlive/texmf-dist/tex/latex/base/size11.clo))
> ..Article!..
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/ifpdf.sty
> (/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/base/fontenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/base/inputenc.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/microtype/microtype.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/microtype/microtype-pdftex.def)
> (/usr/share/texlive/texmf-dist/tex/latex/microtype/microtype.cfg))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
> For additional information on amsmath, use the `?' option.
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/psnfss/mathpazo.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/siunitx/siunitx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/translations/translations.sty
> (/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty
> (/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty)))
> (/usr/share/texlive/texmf-dist/tex/latex/l3packages/l3keys2e/l3keys2e.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty
> (/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def)))
> (/usr/share/texlive/texmf-dist/tex/latex/tools/array.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/titlesec/titlesec.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-def/pdftex.def)))
> (/usr/share/texlive/texmf-dist/tex/latex/multirow/multirow.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/enumitem/enumitem.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
> (/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)
> (/usr/share/texlive/texmf-dist/tex/latex/colortbl/colortbl.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/graphics/dvipsnam.def)
> (/usr/share/texlive/texmf-dist/tex/latex/xcolor/svgnam.def))
> (/usr/share/texlive/texmf-dist/tex/latex/mdframed/mdframed.sty
> (/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty
> (/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty))
> (/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)
> (/usr/share/texlive/texmf-dist/tex/latex/zref/zref-abspage.sty
> (/usr/share/texlive/texmf-dist/tex/latex/zref/zref-base.sty
> (/usr/share/texlive/texmf-dist/tex/generic/kvdefinekeys/kvdefinekeys.sty)
> (/usr/share/texlive/texmf-dist/tex/generic/etexcmds/ete

Bug#1013086: marked as done (python-bayespy: tests fail using deprecated scipy.optimize.optimize)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 15:22:53 +
with message-id 
and subject line Bug#1013086: fixed in python-bayespy 0.5.22-2
has caused the Debian Bug report #1013086,
regarding python-bayespy: tests fail using deprecated scipy.optimize.optimize
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.)


-- 
1013086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-bayespy
Version: 0.5.22-1
Severity: serious
Tags: upstream
Justification: debci

bayespy tests use scipy.optimize.optimize which is deprecated and no
longer has attribute _epsilon.

Hence bayespy tests fail with scipy 1.8.1
--- End Message ---
--- Begin Message ---
Source: python-bayespy
Source-Version: 0.5.22-2
Done: Håvard F. Aasen 

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

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

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

Debian distribution maintenance software
pp.
Håvard F. Aasen  (supplier of updated python-bayespy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 23 Jun 2022 22:52:57 +0200
Source: python-bayespy
Architecture: source
Version: 0.5.22-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Håvard F. Aasen 
Closes: 1013086
Changes:
 python-bayespy (0.5.22-2) unstable; urgency=medium
 .
   * QA upload.
   * Change patch to gbp-pq.
   * Add change-from-scipy-to-locally-defined-epsilon.patch
 - Upstream patch to fix compatibility with scipy >= 1.8.1 Closes: #1013086
   * autopkgtest:
 - Move test script to a separate file.
 - Change from py3versions -r -> py3versions --supported
   * Update Standards-Version to 4.6.1
Checksums-Sha1:
 85a19e2e9e348019c4f6ae4484d573602cb0da1f 2201 python-bayespy_0.5.22-2.dsc
 1ef4b4fb6e18e80397c6143010f5ac2160434b43 7052 
python-bayespy_0.5.22-2.debian.tar.xz
 a3cd8a5dac72c10087e6a45a845e67b5873aaf8d 7775 
python-bayespy_0.5.22-2_source.buildinfo
Checksums-Sha256:
 50d1b501ef715895321307e72a3d6af4f1b6065c9613f0260fc6f7b2801ae250 2201 
python-bayespy_0.5.22-2.dsc
 988ab87a6ceec91c29494096d560a7e0a495a3263ed6e3b38088f8df9c7172a7 7052 
python-bayespy_0.5.22-2.debian.tar.xz
 176812ac1d0be5993d8d5ed2b62d6c95a6b22345b09fcc6f3ac17f06273972e3 7775 
python-bayespy_0.5.22-2_source.buildinfo
Files:
 7f9e3500e2cc8bddde21de90759b1215 2201 python optional 
python-bayespy_0.5.22-2.dsc
 dc40429da005ec989e1105ccfe175668 7052 python optional 
python-bayespy_0.5.22-2.debian.tar.xz
 b0bc299a1c0f139995cbf9bc6c4b2469 7775 python optional 
python-bayespy_0.5.22-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmK1zIAQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFJPlDADdYNxC8i6FYfIvIXMXCFRxeQqUI3LchtEU
Gl/CyOf0ZteBPKgySejrUPwEJiVozasdLbhIijBh/Iu1E9DZsVJZ7rApPW6tr5Ve
NsKZiuSZUUkVSOgT/JxU4EOmB+w9BKhi4sCcA7MRdre/aI5YiFbro5Ofq+SEfYjO
MVqInrYq/PXk9dv9omfxG8gUNBaeGoXKrRQY0lCuFJ5+U63J7VFUc1ZIgRXeQypR
9DsnvENm+aNsxZI0BPnPGKEMfmdQHYadbdyDJw/4Cn3/nza1ekSEpuxilO9uaKJ3
L5dA2bBly/a2yU1IF37k0XWJOnabYVwzNczPu0j0aU1Ut+yq/vBQeu/x/UphZedV
m6K6kBBdMZ7fF4NhAf/2l4nkHrbKRczkkChWZ/aweOLSCsgcfEwTo2kD5zVEpgsO
eWLD6RhhayQXiKWfbPikYYcg/EBKHyMb5mfIpi9brhP/gKvYGMA20B1QowvhdSW1
PFQXJy5ntQZRSHVGsbv+Fwb3O5l+eJs=
=RF5g
-END PGP SIGNATURE End Message ---

Bug#1008022: keepass2: CVE-2022-0725 information disclosure

[Enrico Zini]

On Sun, Mar 20, 2022 at 06:16:41PM +0100, Markus Koschany wrote:

> Steps to reproduce the problem (according
> to https://bugzilla.redhat.com/show_bug.cgi?id=2052696)
> 
> Step 1: Run "journalctl -f" in a terminal window.
> Step 2: Double click a password in KeePass.
> Step 3: Wait for the clear timeout to trigger.
> 
> Actual results:
> See your plain text password logged in the terminal window
> 
> Expected results:
> Never see your plain text password logged anywhere
> 
> Only users in the systemd-journal group can use journalctl. At the moment I
> can't reproduce the problem on a custom XFCE system but I have not tried GNOME
> or other desktop environments yet and I suspect this problem is not limited to
> RedHat or Fedora.

I failed to reproduce this on Gnome on a freshly installed buster
system.

I failed to reproduce this on Gnome on a freshly installed bullseye
system with wayland.

Also on bullseye:

 - I tried to install all the clipboard managers I could find in apt
   (clipit clipman copyq diodon gnome-shell-extension-gpaste parcellite
   qlipper xsel) and I still couldn't reproduce.

 - I ran keepass2 in a terminal, and it did not produce output.

 - I ran keepass2 from Gnome Shell, and I keep seeing nothing in logs.

In RedHat's bugzilla at https://bugzilla.redhat.com/show_bug.cgi?id=2053688
they also failed to reproduce it. At this point, the only reproducers
are in the two threads in the keepass discussion forum.

In https://sourceforge.net/p/keepass/discussion/329220/thread/da7546b7e1/
Paul tried to reproduce it, too, and also failed.

At this point I would suspect that something else was at play in the
users' systems, independent from keepass2.


Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 


signature.asc
Description: PGP signature

Bug#1013538: marked as done (node-rollup-plugin-sourcemaps: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 15:20:00 +
with message-id 
and subject line Bug#1013538: fixed in node-rollup-plugin-sourcemaps 0.6.3-7
has caused the Debian Bug report #1013538,
regarding node-rollup-plugin-sourcemaps: FTBFS: dh_auto_test: error: /bin/sh 
-ex debian/tests/pkg-js/test returned exit code 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.)


-- 
1013538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-rollup-plugin-sourcemaps
Version: 0.6.3-6
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):
> make[1]: Entering directory '/<>'
> rollup -c
> 
> src/index.ts → dist, dist...
> (!) Plugin typescript: @rollup/plugin-typescript TS2345: Argument of 
> type '({ sourceMap, inlineSourceMap, inlineSources, }: { sourceMap: boolean; 
> inlineSourceMap: boolean; inlineSources: boolean; }) => Promise' is not 
> assignable to parameter of type '(arg: Record) => void | 
> TestReturnValuePromise | TestReturnValueGenerator | undefined'.
>   Types of parameters '__0' and 'arg' are incompatible.
> Type 'Record' is missing the following properties from 
> type '{ sourceMap: boolean; inlineSourceMap: boolean; inlineSources: boolean; 
> }': sourceMap, inlineSourceMap, inlineSources
> src/__tests__/index.ts: (98:5)
> 
>  98 async ({
>     
>  99   sourceMap,
>     
> ... 
> 105   inlineSources: boolean;
>     ~
> 106 }) => {
>     ~~~
> 
> created dist, dist in 4.8s
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs
>   ln -s ../. node_modules/rollup-plugin-sourcemaps
>   /bin/sh -ex debian/tests/pkg-js/test
> + jest --ci
> FAIL src/__tests__/index.ts
>   ● Test suite failed to run
> 
> src/__tests__/index.ts:98:5 - 
> error TS2345: Argument of type '({ sourceMap, 
> inlineSourceMap, inlineSources, }: { sourceMap: boolean; inlineSourceMap: 
> boolean; inlineSources: boolean; }) => Promise' is not assignable to 
> parameter of type '(arg: Record) => void | 
> TestReturnValuePromise | TestReturnValueGenerator | undefined'.
>   Types of parameters '__0' and 'arg' are incompatible.
> Type 'Record' is missing the following properties 
> from type '{ sourceMap: boolean; inlineSourceMap: boolean; inlineSources: 
> boolean; }': sourceMap, inlineSourceMap, inlineSources
> 
>  98 async ({
>     
>  99   sourceMap,
>     
> ... 
> 105   inlineSources: boolean;
>     ~
> 106 }) => {
>     ~~~
> 
> Test Suites: 1 failed, 1 total
> Tests:   0 total
> Snapshots:   0 total
> Time:6.154 s
> Ran all test suites.
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/node-rollup-plugin-sourcemaps_0.6.3-6_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=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: node-rollup-plugin-sourcemaps
Source-Version: 0.6.3-7
Done: Yadd 

We believe th

Bug#1013608: marked as done (ncbi-entrez-direct: FTBFS: cannot find package "github.com/shirou/gopsutil/mem")

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 15:19:54 +
with message-id 
and subject line Bug#1013608: fixed in ncbi-entrez-direct 14.6.20210224+dfsg-6
has caused the Debian Bug report #1013608,
regarding ncbi-entrez-direct: FTBFS: cannot find package 
"github.com/shirou/gopsutil/mem"
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.)


-- 
1013608: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ncbi-entrez-direct
Version: 14.6.20210224+dfsg-5
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):
> make[1]: Entering directory '/<>'
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' edirect.pl > bin/edirect
> chmod +x bin/edirect
> echo '#!/bin/sh' > bin/eaddress
> echo 'exec /usr/bin/edirect -address "$@"' >> bin/eaddress
> chmod +x bin/eaddress
> echo '#!/bin/sh' > bin/eblast
> echo 'exec /usr/bin/edirect -blast "$@"' >> bin/eblast
> chmod +x bin/eblast
> echo '#!/bin/sh' > bin/ecitmatch
> echo 'exec /usr/bin/edirect -citmatch "$@"' >> bin/ecitmatch
> chmod +x bin/ecitmatch
> echo '#!/bin/sh' > bin/econtact
> echo 'exec /usr/bin/edirect -contact "$@"' >> bin/econtact
> chmod +x bin/econtact
> echo '#!/bin/sh' > bin/enotify
> echo 'exec /usr/bin/edirect -notify "$@"' >> bin/enotify
> chmod +x bin/enotify
> echo '#!/bin/sh' > bin/eproxy
> echo 'exec /usr/bin/edirect -proxy "$@"' >> bin/eproxy
> chmod +x bin/eproxy
> echo '#!/bin/sh' > bin/espell
> echo 'exec /usr/bin/edirect -spell "$@"' >> bin/espell
> chmod +x bin/espell
> echo '#!/bin/sh' > bin/ftp-cp
> echo 'exec /usr/bin/edirect -ftpcp "$@"' >> bin/ftp-cp
> chmod +x bin/ftp-cp
> echo '#!/bin/sh' > bin/ftp-ls
> echo 'exec /usr/bin/edirect -ftpls "$@"' >> bin/ftp-ls
> chmod +x bin/ftp-ls
> sed -e 's,xml2json,/usr/lib/ncbi-entrez-direct/&,; s/python/&3/; /to 
> precompiled/q' \
> transmute > bin/transmute.sh
> echo 'exec /usr/lib/ncbi-entrez-direct/transmute "$@"' >> bin/transmute.sh
> chmod +x bin/transmute.sh
> sed -e 's,xml2json,/usr/lib/ncbi-entrez-direct/&,; s/python/&3/; /to 
> precompiled/q' \
> xtract > bin/xtract.sh
> echo 'exec /usr/lib/ncbi-entrez-direct/xtract "$@"' >> bin/xtract.sh
> chmod +x bin/xtract.sh
> mkdir -p bin
> sed -e '1s,^#!/bin/sh,#!/bin/bash,' index-extras > bin/index-extras
> chmod +x bin/index-extras
> mkdir -p bin
> sed -e 's/`has-asp`/false # &/' download-ncbi-data > bin/download-ncbi-data
> chmod +x bin/download-ncbi-data
> mkdir -p bin
> sed -e 's/`has-asp`/false # &/' download-pubmed > bin/download-pubmed
> chmod +x bin/download-pubmed
> mkdir -p bin
> sed -e 's/`has-asp`/false # &/' download-sequence > bin/download-sequence
> chmod +x bin/download-sequence
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' edirutil > bin/edirutil
> chmod +x bin/edirutil
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' run-ncbi-converter > 
> bin/run-ncbi-converter
> chmod +x bin/run-ncbi-converter
> mkdir -p bin
> sed -e '1s,^#!/usr/bin/env perl$,#!/usr/bin/perl,' xml2json > bin/xml2json
> chmod +x bin/xml2json
> mkdir -p bin
> sed -e 's/edirect\.pl/edirect/g; 
> s,"$pth"/ec,/usr/lib/ncbi-entrez-direct/ec,g' efetch > bin/efetch
> chmod +x bin/efetch
> mkdir -p bin
> sed -e 's/edirect\.pl/edirect/g; 
> s,"$pth"/ec,/usr/lib/ncbi-entrez-direct/ec,g' efilter > bin/efilter
> chmod +x bin/efilter
> mkdir -p bin
> sed -e 's/edirect\.pl/edirect/g; 
> s,"$pth"/ec,/usr/lib/ncbi-entrez-direct/ec,g' einfo > bin/einfo
> chmod +x bin/einfo
> mkdir -p bin
> sed -e 's/edirect\.pl/edirect/g; 
> s,"$pth"/ec,/usr/lib/ncbi-entrez-direct/ec,g' elink > bin/elink
> chmod +x bin/elink
> mkdir -p bin
> sed -e 's/edirect\.pl/edirect/g; 
> s,"$pth"/ec,/usr/lib/ncbi-entrez-direct/ec,g' epost > bin/epost
> chmod +x bin/epost
> mkdir -p bin
> sed -e 's/edirect\.

Bug#1002227: golang-github-templexxx-xor: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/templexxx/xor returned exit code 1

[Lucas Nussbaum]

Hi,

On 24/06/22 at 22:48 +0800, Shengjing Zhu wrote:
> On Wed, Dec 22, 2021 at 12:42 AM Lucas Nussbaum  wrote:
> >
> > Source: golang-github-templexxx-xor
> > Version: 0.1.2-5
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20211220 ftbfs-bookworm
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> >
> > Relevant part (hopefully):
> > >  debian/rules build
> > > dh build --buildsystem=golang --with=golang
> > >dh_update_autotools_config -O--buildsystem=golang
> > >dh_autoreconf -O--buildsystem=golang
> > >dh_auto_configure -O--buildsystem=golang
> > >dh_auto_build -O--buildsystem=golang
> > >   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
> > > github.com/templexxx/xor
> > > internal/goexperiment
> > > internal/abi
> > > github.com/templexxx/cpufeat
> > > internal/cpu
> > > runtime/internal/atomic
> > > runtime/internal/sys
> > > runtime/internal/math
> > > internal/bytealg
> > > runtime
> > > github.com/templexxx/xor
> > >dh_auto_test -O--buildsystem=golang
> > >   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
> > > github.com/templexxx/xor
> > > === RUN   TestVerifyBytesNoSIMD
> > > --- PASS: TestVerifyBytesNoSIMD (1.13s)
> > > === RUN   TestVerifyBytes
> > > --- PASS: TestVerifyBytes (1.13s)
> > > === RUN   TestVerifyBytesSrc1
> > > unexpected fault address 0x0
> > > fatal error: fault
> > > [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0x4e7234]
> > >
> > > goroutine 10 [running]:
> > > runtime.throw({0x511356, 0xc1a2d0})
> > >   /usr/lib/go-1.17/src/runtime/panic.go:1198 +0x71 fp=0xc33638 
> > > sp=0xc33608 pc=0x433f11
> > > runtime.sigpanic()
> > >   /usr/lib/go-1.17/src/runtime/signal_unix.go:742 +0x2f6 
> > > fp=0xc33688 sp=0xc33638 pc=0x448696
> > > github.com/templexxx/xor.xorSrc0({0xc1a288, 0x11, 0x11}, 
> > > {0xc1a2a0, 0x11, 0x11}, {0xc1a2b8, 0x11, 0x11})
> > >   
> > > /<>/obj-x86_64-linux-gnu/src/github.com/templexxx/xor/sse2_amd64.s:43
> > >  +0x34 fp=0xc33690 sp=0xc33688 pc=0x4e7234
> 
> This test "sse2_amd64.s“ suggests it's related to SIMD, but I haven't
> checked if it just calls sse2 or more. I'm also not sure if the
> package is broken without SIMD, or just the test is broken.

The CPU used for 
http://qa-logs.debian.net/2022/06/24/golang-github-templexxx-xor_0.1.2-5_unstable.log
was Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz, so it's fairly
recent.

Lucas

Processed: affects 1010344

[Debian Bug Tracking System]

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

> affects 1010344 node-espree
Bug #1010344 {Done: Yadd } [node-acorn] FTBFS: some test fails 
with "An export name cannot include a lone surrogate"
Added indication that 1010344 affects node-espree
> thanks
Stopping processing here.

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

Processed: Re: Bug#1013657: node-espree: FTBFS: make[1]: *** [debian/rules:31: override_dh_auto_test] Error 9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1013657 [src:node-espree] node-espree: FTBFS: make[1]: *** 
[debian/rules:31: override_dh_auto_test] Error 9
Added tag(s) moreinfo.

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

Bug#1013657: node-espree: FTBFS: make[1]: *** [debian/rules:31: override_dh_auto_test] Error 9

[Yadd]

Control: tags -1 + moreinfo

On 24/06/2022 16:36, Lucas Nussbaum wrote:

Source: node-espree
Version: 9.3.1~dfsg-1
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.


Hi,

I just fixed acorn and all seems OK for node-espree. Let's wait to see 
if this bug is fixed with #1010344


Cheers,
Yadd

Bug#1013538: marked as pending in node-rollup-plugin-sourcemaps

[Yadd]

Control: tag -1 pending

Hello,

Bug #1013538 in node-rollup-plugin-sourcemaps 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/js-team/node-rollup-plugin-sourcemaps/-/commit/5ca4c3ae2c1b2d831e2cf228e1a0539fe05e7d8f


Fix TypeScript for test

Closes: #1013538


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013538

Processed: Bug#1013538 marked as pending in node-rollup-plugin-sourcemaps

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013538 [src:node-rollup-plugin-sourcemaps] node-rollup-plugin-sourcemaps: 
FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit 
code 1
Added tag(s) pending.

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

Bug#1013451: openssh-client: double free or corruption

[Andreas Tille]

Hi,

I confirm the very same issue here.  I've found another "solution" (if
exchanging your ssh-keys is an option for you):  Just create new keys
with ssh-keygen and push them with ssh-copy-id to your target hosts.
This works for me (but is for sure a nuisance when you have lots of
hosts to feed the key with.

I've got a hint that the linked libssl3 might have caused the issue.
In my case the switch from

  2022-06-16 08:37:01 status installed libssl3:amd64 3.0.3-8

(which works) to

  2022-06-23 10:54:50 status installed libssl3:amd64 3.0.4-1

which produces the error seems to be responsible.

Hope this shades some light into this issue

 Andreas.

-- 
http://fam-tille.de

Bug#997116: marked as done (anjuta-extras: FTBFS: gatomic.h:113:19: error: argument 2 of ‘__atomic_load’ must not be a pointer to a ‘volatile’ type)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 14:53:16 +
with message-id 
and subject line Bug#1011353: Removed package(s) from unstable
has caused the Debian Bug report #997116,
regarding anjuta-extras: FTBFS: gatomic.h:113:19: error: argument 2 of 
‘__atomic_load’ must not be a pointer to a ‘volatile’ type
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.)


-- 
997116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: anjuta-extras
Version: 3.26.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /bin/bash ../../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H 
> -I. -I../../..  -I./include -I./src -I./lexlib -pthread 
> -I/usr/include/libanjuta-3.0 -I/usr/include/libgdl-3.0 -I/usr/include/libxml2 
> -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi 
> -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGTK 
> -DSCI_LEXER -DUSE_XIM -Wdate-time -D_FORTIFY_SOURCE=2 -DGTK -DSCI_LEXER 
> -DUSE_XIM -std=c++11 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> ScintillaGTK.lo `test -f 'gtk/ScintillaGTK.cxx' || echo 
> './'`gtk/ScintillaGTK.cxx
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../.. -I./include -I./src 
> -I./lexlib -pthread -I/usr/include/libanjuta-3.0 -I/usr/include/libgdl-3.0 
> -I/usr/include/libxml2 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi 
> -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGTK 
> -DSCI_LEXER -DUSE_XIM -Wdate-time -D_FORTIFY_SOURCE=2 -DGTK -DSCI_LEXER 
> -DUSE_XIM -std=c++11 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -c 
> gtk/ScintillaGTKAccessible.cxx  -fPIC -DPIC -o .libs/ScintillaGTKAccessible.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../.. -I./include -I./src 
> -I./lexlib -pthread -I/usr/include/libanjuta-3.0 -I/usr/include/libgdl-3.0 
> -I/usr/include/libxml2 -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 
> -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi 
> -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo 
> -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DGTK 
> -DSCI_LEXER -DUSE_XIM -Wdate-time -D_FORTIFY_SOURCE=2 -DGTK -DSCI_LEXER 
> -DUSE_XIM -std=c++11 -g -O2 

Processed: Re: python-bids-validator: autopkgtest regression in testing

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.9.4-1
Bug #1012771 [src:python-bids-validator] python-bids-validator: autopkgtest 
regression in testing
The source 'python-bids-validator' and version '1.9.4-1' do not appear to match 
any binary packages
Marked as fixed in versions python-bids-validator/1.9.4-1.
> close -1
Bug #1012771 [src:python-bids-validator] python-bids-validator: autopkgtest 
regression in testing
Marked Bug as done

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

Bug#1012771: python-bids-validator: autopkgtest regression in testing

[Nilesh Patra]

Control: fixed -1 1.9.4-1
Control: close -1

fixed in latest upatream.

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Processed (with 3 errors): fix remaining bugs

[Debian Bug Tracking System]

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

> Hello, please find as an attachment a patch to fix #1012190 and #981703
Unknown command or malformed arguments to command.
> and close them.
Unknown command or malformed arguments to command.
> Best regards, Georges.
Unknown command or malformed arguments to command.
> tags 1012190 + patch
Bug #1012190 {Done: Paul Gevers } [src:slop] src:slop: fails 
to migrate to testing for too long: unresolved RC bug
Added tag(s) patch.
> thank you
Stopping processing here.

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

Bug#1009010: fix remaining bugs

[Georges Khaznadar]

Hello, please find as an attachment a patch to fix #1012190 and #981703
and close them.

Best regards,   Georges.

tags 1012190 + patch
thank you

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70

diff --git a/debian/changelog b/debian/changelog
index f5795bd..2c59b7e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,18 @@
+slop (7.6-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * added a file d/libslop7.6.shlibs; #closes: #1012190
+  * modified d/control
++ now libslop7.6 conflicts with libslop7.5 and replaces it
++ added a strict dependency libdevel =>
+  libslopy7.6(>= ${source:Version}), libslopy7.6(<= ${source:Version}.1~)
+  * applied GSR's patch; closes: #981703
+  * modified d/rules to clean out bin/slop
+  * checked that the last release of maim can be built with this release of
+libslop7.6 and run seamlessly
+
+ -- Georges Khaznadar   Fri, 24 Jun 2022 15:38:33 +0200
+
 slop (7.6-2) experimental; urgency=medium
 
   * split out shared library in new binary packages (Closes: #1009010)
diff --git a/debian/control b/debian/control
index 42c61ce..8e6487b 100644
--- a/debian/control
+++ b/debian/control
@@ -51,6 +51,8 @@ Description: queries for a selection from the user and prints the region to stdo
   * Supports a magnifying glass.
 
 Package: libslopy7.6
+Conflicts:  libslopy7.5
+Replaces: libslopy7.5
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: queries for a selection from the user and prints the region to stdout
@@ -65,7 +67,8 @@ Description: queries for a selection from the user and prints the region to stdo
 Package: libslopy-dev
 Section: libdevel
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends: ${misc:Depends},
+ libslopy7.6(>= ${source:Version}), libslopy7.6(<= ${source:Version}.1~)
 Description: queries for a selection from the user and prints the region to stdout
  slop (Select Operation) is an application that queries for a
  selection from the user and prints the region to stdout. It grabs the
diff --git a/debian/libslopy7.6.shlibs b/debian/libslopy7.6.shlibs
new file mode 100644
index 000..05db7f3
--- /dev/null
+++ b/debian/libslopy7.6.shlibs
@@ -0,0 +1 @@
+libslopy 7.6 libslopy7.6
diff --git a/debian/patches/fix981703.patch b/debian/patches/fix981703.patch
new file mode 100644
index 000..c18e853
--- /dev/null
+++ b/debian/patches/fix981703.patch
@@ -0,0 +1,16 @@
+fix 981703: slop: Improve man page for better apropos results
+Index: slop/slop.1
+===
+--- slop.orig/slop.1
 slop/slop.1
+@@ -1,8 +1,8 @@
+ .\" Manpage for slop.
+ .\" Contact naelst...@gmail.com to correct errors or typos.
+-.TH SLOP 1 2017-03-21 Linux "slop man page"
++.TH SLOP 1 2021-02-03 Linux "slop man page"
+ .SH NAME
+-slop \- select operation
++slop \- select operation, either mark screen region or pick window
+ .SH SYNOPSIS
+ slop [-klqn] [OPTIONS]
+ .SH DESCRIPTION
diff --git a/debian/patches/series b/debian/patches/series
index 8c97052..fef7054 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,2 @@
 fix994824.patch
+fix981703.patch
diff --git a/debian/rules b/debian/rules
index bb2a2a9..61fae45 100755
--- a/debian/rules
+++ b/debian/rules
@@ -20,3 +20,8 @@ export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
 # main packaging script based on dh7 syntax
 %:
 	dh $@
+
+override_dh_auto_clean:
+	dh_auto_clean
+	# remove a binary file not cleaned by the Makefile
+	rm -f bin/slop


signature.asc
Description: PGP signature

Bug#1013615: hiredis: FTBFS: 2 TESTS FAILED ***

[Chris Lamb]

>> #54 Does not return a reply when the command times out: FAILED

I suspect that the root cause here is that Redis 7.x is now in
unstable (vs. 6.x).


// Chris

Bug#966112: marked as done (fsl: FTBFS with GCC 10: undefined reference to `int fslsurface_name::readGIFTI(...))

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 14:48:37 +
with message-id 
and subject line Bug#1009276: Removed package(s) from unstable
has caused the Debian Bug report #966112,
regarding fsl: FTBFS with GCC 10: undefined reference to `int 
fslsurface_name::readGIFTI(...)
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.)


-- 
966112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fsl
Version: 5.0.8-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Hi,

fsl started to FTBFS when GCC 10 was made the default compiler:

g++ -g -O2 -fdebug-prefix-map=/build/fsl-5.0.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-DHAVE_LIBFREETYPE -fPIC -I/usr/include/nifti -I/usr/include/gifti 
-I/usr/include/newmat -I/build/fsl-5.0.8/extras/src/libprob 
-I/build/fsl-5.0.8/extras/src/libcprob -I/build/fsl-5.0.8/src
-I/usr/include/newmat -I/build/fsl-5.0.8/extras/include/libprob -I/usr/include 
-I/build/fsl-5.0.8/include/niftiio  -I. -I/build/fsl-5.0.8/include 
-I/build/fsl-5.0.8/include -Wl,-z,relro -Wl,--no-undefined -L/usr/lib/fsl/lib 
-L/usr/lib  -L/build/fsl-5.0.8/extras/lib -L/usr/lib -L. -L/build/fsl-5.0.8/lib 
-L/build/fsl-5.0.8/lib -o fslsurfacemaths fslsurfacemaths.o fslsurfaceio.o 
fslsurfacefns.o fslsurface_first.o fslsurface.o -lgiftiio -lexpat -lfirst_lib 
-lmeshclass -lshapeModel -lfslvtkio -lmeshclass -lnewimage -lmiscmaths  -lfslio 
-lniftiio -lznz -lnewmat -lutils -lprob -lz -lGL -lGLU
/usr/bin/ld: fslsurfacemaths.o: in function `main':
./src/fslsurface/fslsurfacemaths.cpp:184: undefined reference to `int 
fslsurface_name::readGIFTI(fslsurface_name::fslSurface&, 
std::__cxx11::basic_string, std::allocator > 
const&)'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:61: fslsurfacemaths] Error 1
make[1]: Leaving directory '/build/fsl-5.0.8/src/fslsurface'
make: *** [debian/rules:114: biproj-fslsurface] Error 2

Te full buildlog is attached.


Andreas


fsl_5.0.8-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 5.0.8-6+rm

Dear submitter,

as the package fsl has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1009276

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#966800: marked as done (vmtk: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 14:48:03 +
with message-id 
and subject line Bug#1008792: Removed package(s) from unstable
has caused the Debian Bug report #938795,
regarding vmtk: Unversioned Python removal in sid/bullseye
to be marked as done.

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

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


-- 
938795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vmtk
Version: 1.3+dfsg-2.3
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 1.3+dfsg-2.3+rm

Dear submitter,

as the package vmtk has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1008792

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#939594: marked as done (vmtk build-depends on cruft package)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 14:48:03 +
with message-id 
and subject line Bug#1008792: Removed package(s) from unstable
has caused the Debian Bug report #938795,
regarding vmtk build-depends on cruft 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.)


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

package: vmtk
severity: serious
version: 1.3+dfsg-2.3

vmtk build-depends on libvtk6-java which is no longer built by the vtk6 
source package.
--- End Message ---
--- Begin Message ---
Version: 1.3+dfsg-2.3+rm

Dear submitter,

as the package vmtk has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1008792

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#936954: marked as done (live-wrapper: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 14:49:51 +
with message-id 
and subject line Bug#1009282: Removed package(s) from unstable
has caused the Debian Bug report #936954,
regarding live-wrapper: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:live-wrapper
Version: 0.10
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:live-wrapper

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.10+rm

Dear submitter,

as the package live-wrapper has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1009282

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#966732: marked as done (fsl: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 14:48:37 +
with message-id 
and subject line Bug#1009276: Removed package(s) from unstable
has caused the Debian Bug report #936564,
regarding fsl: Unversioned Python removal in sid/bullseye
to be marked as done.

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

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


-- 
936564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fsl
Version: 5.0.8-6
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 5.0.8-6+rm

Dear submitter,

as the package fsl has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1009276

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#938795: marked as done (vmtk: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 14:48:03 +
with message-id 
and subject line Bug#1008792: Removed package(s) from unstable
has caused the Debian Bug report #938795,
regarding vmtk: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
938795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vmtk
Version: 1.3+dfsg-2.3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:vmtk

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 1.3+dfsg-2.3+rm

Dear submitter,

as the package vmtk has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1008792

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#936564: marked as done (fsl: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 14:48:37 +
with message-id 
and subject line Bug#1009276: Removed package(s) from unstable
has caused the Debian Bug report #936564,
regarding fsl: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fsl
Version: 5.0.8-6
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:fsl

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 5.0.8-6+rm

Dear submitter,

as the package fsl has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1009276

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#916716: marked as done (live-wrapper: Replace vmdebootstrap usage with alternative)

[Debian Bug Tracking System]

Your message dated Fri, 24 Jun 2022 14:49:51 +
with message-id 
and subject line Bug#1009282: Removed package(s) from unstable
has caused the Debian Bug report #916716,
regarding live-wrapper: Replace vmdebootstrap usage with alternative
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.)


-- 
916716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: live-wrapper
Version: 0.7
Severity: important

The vmdebootstrap maintainer has a strong preference for the package to be
removed from Debian [1].  live-wrapper is the only remaining user.  Pleae
port it to use something else.

Scott K

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907751
--- End Message ---
--- Begin Message ---
Version: 0.10+rm

Dear submitter,

as the package live-wrapper has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1009282

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---