Processed: src:genimage: fails to migrate to testing for too long: FTBFS (testsuite fails) on 32 bits systems

[Debian Bug Tracking System]

Processing control commands:

> close -1 16-1
Bug #1025732 [src:genimage] src:genimage: fails to migrate to testing for too 
long: FTBFS (testsuite fails) on 32 bits systems
Marked as fixed in versions genimage/16-1.
Bug #1025732 [src:genimage] src:genimage: fails to migrate to testing for too 
long: FTBFS (testsuite fails) on 32 bits systems
Marked Bug as done

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

Bug#1025732: src:genimage: fails to migrate to testing for too long: FTBFS (testsuite fails) on 32 bits systems

[Paul Gevers]

Source: genimage
Version: 15-3
Severity: serious
Control: close -1 16-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:genimage has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package failed to build from 
source on the 32 bit architectures where it built successfully in the past.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and bookworm, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=genimage



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024163: marked as done (src:freefem++: unsatisfied build dependency in testing: libgmm++-dev)

[Debian Bug Tracking System]

Your message dated Thu, 8 Dec 2022 08:46:27 +0100
with message-id <0fbed3d5-dce3-45cc-7128-3c984fc50...@debian.org>
and subject line Re: src:freefem++: unsatisfied build dependency in testing: 
libgmm++-dev
has caused the Debian Bug report #1024163,
regarding src:freefem++: unsatisfied build dependency in testing: libgmm++-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.)


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

Source: freefem++
Version: 4.11+dfsg1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Control: block -1 by 1023788

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

In this case, src:getfem took over from src:getfem++ but it is blocked 
because if fails to build from source on s390x, see bug #1023788.


Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

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



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

Hi,

On Tue, 15 Nov 2022 20:22:08 +0100 Paul Gevers  wrote:
In this case, src:getfem took over from src:getfem++ but it is blocked 
because if fails to build from source on s390x, see bug #1023788.


It migrated.

Paul


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

Bug#1024164: marked as done (src:gmsh: unsatisfied build dependency in testing: libgmm++-dev)

[Debian Bug Tracking System]

Your message dated Thu, 8 Dec 2022 08:44:33 +0100
with message-id 
and subject line Re: src:gmsh: unsatisfied build dependency in testing: 
libgmm++-dev
has caused the Debian Bug report #1024164,
regarding src:gmsh: unsatisfied build dependency in testing: libgmm++-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.)


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

Source: gmsh
Version: 4.8.4+ds2-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Control: block -1 by 1023788

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

In this case, src:getfem took over from src:getfem++ but it is blocked 
because if fails to build from source on s390x, see bug #1023788.


Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

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



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

Hi,

On Tue, 15 Nov 2022 20:22:58 +0100 Paul Gevers  wrote:
In this case, src:getfem took over from src:getfem++ but it is blocked 
because if fails to build from source on s390x, see bug #1023788.


libgmm++-dev migrated.

Paul


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

Bug#1025731: libghc-pcre-light-doc: depends on non-existing haddock-interface-35

[Ralf Treinen]

Package: libghc-pcre-light-doc
Version: 0.4.1.0-1
Severity: serious

libghc-pcre-light-doc cannot be installed since it depends on
haddock-interface-35 which does not exist in sid.

-Ralf.

Bug#1024439: marked as done (numpy: autopkgtest regression: transtional package libopenblas-base dropped)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2022 07:19:35 +
with message-id 
and subject line Bug#1024439: fixed in numpy 1:1.23.5-1
has caused the Debian Bug report #1024439,
regarding numpy: autopkgtest regression: transtional package libopenblas-base 
dropped
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.)


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

Source: numpy
Version: 1:1.21.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it recently started
to fail in testing. This seems to be a result of openblas no longer 
building the transitional package libopenblas-base that the test depends 
upon [1].


Paul

[1] Line 7 in:
https://sources.debian.org/src/numpy/1%3A1.21.5-2/debian/tests/control/



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: numpy
Source-Version: 1:1.23.5-1
Done: Sandro Tosi 

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated numpy 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: Thu, 08 Dec 2022 01:57:30 -0500
Source: numpy
Architecture: source
Version: 1:1.23.5-1
Distribution: experimental
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 1024439
Changes:
 numpy (1:1.23.5-1) experimental; urgency=medium
 .
   * New upstream release
   * debian/watch
 - track releases via GitHub APIs
   * debian/patches
 - refresh/disable patches
   * debian/tests/control
 - replace libopenblas-base (transitional pkg, now removed) with
   libopenblas0; Closes: #1024439
   * debian/edit_console_scripts.py, debian/rules
 - add a new helper script to edit console_scripts section of
   entry_points.txt
Checksums-Sha1:
 f401d85fe321f98a0a42e8faebdbcc32fc5a5a07 3032 numpy_1.23.5-1.dsc
 ca1842cb5e574b4c6fa7b232b5f298eec00d5eb0 8119216 numpy_1.23.5.orig.tar.xz
 816e9954eec02dacf3398c4d6ecc0b2f4cf9d8d3 31888 numpy_1.23.5-1.debian.tar.xz
 45f83c922805568eb09cda49cbcbdef54d213043 13728 numpy_1.23.5-1_source.buildinfo
Checksums-Sha256:
 e30d3d2c006f04e8ba06778b429b571411dd6d8bbeda986b84292c192efd7d04 3032 
numpy_1.23.5-1.dsc
 8aae4b7fb7dbdec7a43d89c0adf98a04be1cbd15831e8a6988a71a20b4b24728 8119216 
numpy_1.23.5.orig.tar.xz
 becd66353cfa09d197451bea3633d7dcf874872de1e916c644b2d326c9853c09 31888 
numpy_1.23.5-1.debian.tar.xz
 ee89d19273a909ff720f86c1b1c1e37a1e1879074387e14f2affd5819fb52a43 13728 
numpy_1.23.5-1_source.buildinfo
Files:
 c2c5a8f58a516e4d034f3faf914e8360 3032 python optional numpy_1.23.5-1.dsc
 0211bf4ab7199a339ec13d1edc610af9 8119216 python optional 
numpy_1.23.5.orig.tar.xz
 9d5443d6cc6195755fe734a89813508a 31888 python optional 
numpy_1.23.5-1.debian.tar.xz
 16c8ea734d1b1cff25250062bd3718c2 13728 python optional 
numpy_1.23.5-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmORiwoACgkQh588mTgB
qU+o9w/9EYLp/pIEPGz3tdvNcjM0Ks07GEgo1lNZNVIrsvfPIAgKLQ2kvM+2rQIb
IMHfjChjov0u40tXIWLhTHr29CKM5yGDylWh/1rkjuMjw3v63W4F1//zrTgBQfoL
n1VRzEaw4CIFb7TNpqgCmCE6ri7I8nkIjjq3Bxbat9N1wK6VKbh5IRwokAIgaxcD
SnSchRom9GXdoe+Zi6JK/VgzZGJmnclLi5gqYj+8iU7EF5qzLbncH/r4sSsGPnRv
mAIfAMmS2L0kWEsmwoUWXkiI6bX+Gjd7bfZsENrpEhP/e3rmtjsahAtRK56Z1H25
d3c7CATV1RsjNHZSB2i7HyXPEobUnLZEtx/X83X7Q6zdLsEb/6SC4Aocu2PQ4/c0
lwno5T4cWtdKAnmofP1POEsZYZIUbj+LpTIlc3uDRt5Z+DPJyp3O8JlNnmjWY00b
lvgLz81eiIT/IejmOTHLMVU5U8aIvwPdWsnuMPW01KbPK0PFNiKSYZ9FziHoGClF
Q/9SD8ett8HyEEw4y70JpydMTWxNsN5qOyaR7T9fatdJF3BbkbEqV2ik0dtdwSo3
AqYHZ8zJtU0b83cJ2l29wcBniOllqehR0c61hFhBwXaygAO4laeK5W5VEwedaaJt
Q7GVphH0HCp3zqY1jPMQqsFRH63qq2R57pCphLxUGMCDvmpTg7w=
=s5xx
-END PGP SIGNATURE End Message ---

Bug#1025408: marked as done (python-certbot-dns-standalone: FTBFS (Depending on old python3-acme-abi-1))

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2022 04:04:19 +
with message-id 
and subject line Bug#1025408: fixed in python-certbot-dns-standalone 1.0.3-3
has caused the Debian Bug report #1025408,
regarding python-certbot-dns-standalone: FTBFS (Depending on old 
python3-acme-abi-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.)


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

Source: python-certbot-dns-standalone
Version: 1.0.3-2
Severity: serious

Hello, your package FTBFS now that newer python3-acme abi is in sid.

dpkg-source: warning: cannot verify inline signature for 
./python-certbot-dns-standalone_1.0.3-2.dsc: no acceptable signature found
dpkg-source: info: extracting python-certbot-dns-standalone in 
python-certbot-dns-standalone-1.0.3
dpkg-source: info: unpacking python-certbot-dns-standalone_1.0.3.orig.tar.gz
dpkg-source: info: unpacking python-certbot-dns-standalone_1.0.3-2.debian.tar.xz
I: Not using root during the build.
I: Installing the build-deps
 -> Attempting to parse the build-deps
 -> Considering build-depdebhelper-compat (= 13)
   -> Trying to add debhelper-compat=13
 -> Considering build-dep dh-python
   -> Trying to add dh-python
 -> Considering build-dep python3
   -> Trying to add python3
 -> Considering build-dep python3-setuptools
   -> Trying to add python3-setuptools
 -> Considering build-dep python3-acme-abi-1
   -> Trying to add python3-acme-abi-1
   -> Loop detected, last APT error was: ==
Reading package lists...
Building dependency tree...
Reading state information...
Package python3-acme-abi-1 is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'python3-acme-abi-1' has no installation candidate
   -> =
   -> (not adding  to python3-acme-abi-1)
   -> Cannot install python3-acme-abi-1; apt errors follow:
Reading package lists...
Building dependency tree...
Reading state information...
Package python3-acme-abi-1 is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'python3-acme-abi-1' has no installation candidate


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-certbot-dns-standalone
Source-Version: 1.0.3-3
Done: Harlan Lieberman-Berg 

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

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated 
python-certbot-dns-standalone package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Dec 2022 22:42:28 -0500
Source: python-certbot-dns-standalone
Architecture: source
Version: 1.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Let's Encrypt 
Changed-By: Harlan Lieberman-Berg 
Closes: 1025408
Changes:
 python-certbot-dns-standalone (1.0.3-3) unstable; urgency=medium
 .
   * Team upload.
   * Bump dependency requirements (Closes: #1025408)
   * Run wrap-and-sort
Checksums-Sha1:
 dcf59ddd1c1a5aa1b95c94711800604397478f2a 2401 
python-certbot-dns-standalone_1.0.3-3.dsc
 86ef30e52b7af854c4b49fae4e2f2fc85daafece 2116 
python-certbot-dns-standalone_1.0.3-3.debian.tar.xz
 aebcd98213d067293c9192869f7f7fff8c2d1605 7682 
python-certbot-dns-standalone_1.0.3-3_amd64.buildinfo
Checksums-Sha256:
 be0a911afb8966dcf2ee79a4f704257f3db867b57a96cd8bb3268dc5c25bbce2 2401 
python-certbot-dns-standalone_1.0.3-3.dsc
 7835f30651dbe6e43061abbe509a5310818a5312d7b87e021e9da71183b66a5d 2116 
python-certbot-dns-standalone_1.0.3-3.debian.tar.xz
 95484fb5812a68b28412539f09c84367d34dc2280628939528771fa3c7035260 7682 
python-certbot-dns-standalone_1.0.3-3_amd64.buildinfo
Files:
 d957b488d27a49bf6ce8a0d555fce690 2401 python optional 
python-certbot-dns-standalone_1.0.3-3.dsc
 

Bug#1017234: marked as done (golang-github-zenazn-goji: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/zenazn/goji github.com/zenazn/goji/bind github.com/ze

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2022 02:38:38 +
with message-id 
and subject line Bug#1017234: fixed in golang-github-zenazn-goji 1.0.1-2
has caused the Debian Bug report #1017234,
regarding golang-github-zenazn-goji: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/zenazn/goji 
github.com/zenazn/goji/bind github.com/zenazn/goji/graceful 
github.com/zenazn/goji/graceful/listener github.com/zenazn/goji/web 
github.com/zenazn/goji/web/middleware github.com/zenazn/goji/web/mutil 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
> github.com/zenazn/goji github.com/zenazn/goji/bind 
> github.com/zenazn/goji/graceful github.com/zenazn/goji/graceful/listener 
> github.com/zenazn/goji/web github.com/zenazn/goji/web/middleware 
> github.com/zenazn/goji/web/mutil
> internal/unsafeheader
> internal/goarch
> internal/goos
> internal/goexperiment
> internal/cpu
> internal/race
> runtime/internal/syscall
> runtime/internal/atomic
> internal/abi
> runtime/internal/math
> sync/atomic
> unicode
> runtime/internal/sys
> unicode/utf8
> container/list
> internal/itoa
> math/bits
> crypto/internal/subtle
> crypto/subtle
> internal/bytealg
> crypto/internal/boring/sig
> unicode/utf16
> vendor/golang.org/x/crypto/cryptobyte/asn1
> internal/nettrace
> vendor/golang.org/x/crypto/internal/subtle
> encoding
> math
> runtime
> internal/reflectlite
> sync
> internal/testlog
> math/rand
> internal/singleflight
> runtime/cgo
> errors
> sort
> io
> internal/oserror
> path
> vendor/golang.org/x/net/dns/dnsmessage
> strconv
> crypto/internal/nistec/fiat
> syscall
> hash
> strings
> bytes
> crypto/internal/randutil
> hash/crc32
> crypto
> reflect
> crypto/rc4
> vendor/golang.org/x/text/transform
> bufio
> net/http/internal/ascii
> regexp/syntax
> internal/syscall/execenv
> internal/syscall/unix
> time
> regexp
> io/fs
> context
> internal/poll
> embed
> os
> internal/fmtsort
> encoding/binary
> crypto/cipher
> crypto/internal/nistec
> crypto/internal/edwards25519/field
> crypto/md5
> encoding/base64
> vendor/golang.org/x/crypto/internal/poly1305
> vendor/golang.org/x/crypto/curve25519/internal/field
> fmt
> encoding/pem
> crypto/internal/edwards25519
> internal/godebug
> path/filepath
> io/ioutil
> crypto/internal/boring
> crypto/des
> internal/intern
> vendor/golang.org/x/crypto/chacha20
> crypto/aes
> crypto/sha512
> crypto/hmac
> crypto/sha1
> crypto/sha256
> net/netip
> vendor/golang.org/x/sys/cpu
> vendor/golang.org/x/crypto/hkdf
> os/signal
> encoding/hex
> net/url
> vendor/golang.org/x/crypto/curve25519
> math/big
> vendor/golang.org/x/crypto/chacha20poly1305
> flag
> log
> vendor/golang.org/x/text/unicode/norm
> compress/flate
> vendor/golang.org/x/text/unicode/bidi
> net
> vendor/golang.org/x/net/http2/hpack
> mime
> mime/quotedprintable
> compress/gzip
> net/http/internal
> runtime/debug
> vendor/golang.org/x/text/secure/bidirule
> vendor/golang.org/x/net/idna
> crypto/elliptic
> crypto/internal/boring/bbig
> encoding/asn1
> crypto/rand
> crypto/dsa
> crypto/ed25519
> crypto/rsa
> crypto/x509/pkix
> vendor/golang.org/x/crypto/cryptobyte
> crypto/ecdsa
> github.com/zenazn/goji/graceful/listener
> vendor/golang.org/x/net/http/httpproxy
> github.com/zenazn/goji/bind
> net/textproto
> crypto/x509
> mime/multipart
> vendor/golang.org/x/net/http/httpguts
> crypto/tls
> net/http/httptrace
> net/http
> github.com/zenazn/goji/graceful
> github.com/zenazn/goji/web/mutil
> github.com/zenazn/goji/web
> github.com/zenazn/goji/web/middleware
> github.com/zenazn/goji
>dh_auto_test -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
> github.com/zenazn/goji github.com/zenazn/goji/bind 
> github.com/zenazn/goji/graceful github.com/zenazn/goji/graceful/listener 
> github.com/zenazn/goji/web 

Bug#1023804: marked as done (git-remote-hg: autopkgtest needs update for new version of git: transport 'file' not allowed)

[Debian Bug Tracking System]

Your message dated Thu, 08 Dec 2022 02:38:28 +
with message-id 
and subject line Bug#1023804: fixed in git-remote-hg 1.0.4~ds-1
has caused the Debian Bug report #1023804,
regarding git-remote-hg: autopkgtest needs update for new version of git: 
transport 'file' not allowed
to be marked as done.

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

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


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

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

Dear maintainer(s),

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


   passfail
gitfrom testing1:2.38.1-1
git-remote-hg  from testing1.0.3.2~ds-2
all others from testingfrom testing

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

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

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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-remote-hg/28079228/log.gz

Initialized empty Git repository in 
/tmp/autopkgtest-lxc.4ir0bv3l/downtmp/build.jzc/src/test/trash 
directory.main-push/tmp/sub/.git/

[master (root-commit) be983cd] init
 Author: A U Thor 
 1 file changed, 0 insertions(+), 0 deletions(-)
 create mode 100644 empty
Initialized empty Git repository in 
/tmp/autopkgtest-lxc.4ir0bv3l/downtmp/build.jzc/src/test/trash 
directory.main-push/tmp/gitrepo/.git/
Cloning into 
'/tmp/autopkgtest-lxc.4ir0bv3l/downtmp/build.jzc/src/test/trash 
directory.main-push/tmp/gitrepo/sub'...

fatal: transport 'file' not allowed
fatal: clone of 
'/tmp/autopkgtest-lxc.4ir0bv3l/downtmp/build.jzc/src/test/trash 
directory.main-push/tmp/sub' into submodule path 
'/tmp/autopkgtest-lxc.4ir0bv3l/downtmp/build.jzc/src/test/trash 
directory.main-push/tmp/gitrepo/sub' failed

not ok 52 - push with submodule


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: git-remote-hg
Source-Version: 1.0.4~ds-1
Done: Paul Wise 

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

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

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

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated git-remote-hg 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, 08 Dec 2022 10:00:03 +0800
Source: git-remote-hg
Architecture: source
Version: 1.0.4~ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Paul Wise 
Closes: 1023804
Changes:
 git-remote-hg (1.0.4~ds-1) unstable; urgency=medium
 .
   * QA upload.
   * New 

Processed: Bug#1017234 marked as pending in golang-github-zenazn-goji

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1017234 [src:golang-github-zenazn-goji] golang-github-zenazn-goji: FTBFS: 
dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/zenazn/goji github.com/zenazn/goji/bind 
github.com/zenazn/goji/graceful github.com/zenazn/goji/graceful/listener 
github.com/zenazn/goji/web github.com/zenazn/goji/web/middleware 
github.com/zenazn/goji/web/mutil returned exit code 1
Added tag(s) pending.

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

Bug#1017234: marked as pending in golang-github-zenazn-goji

[Thorsten Alteholz]

Control: tag -1 pending

Hello,

Bug #1017234 in golang-github-zenazn-goji 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/go-team/packages/golang-github-zenazn-goji/-/commit/b1b8ea06fa8140e857adeba2c20689db43011043


Import Debian changes 1.0.1-2

golang-github-zenazn-goji (1.0.1-2) unstable; urgency=medium
.
  [ Debian Janitor ]
  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
  * Update standards version to 4.5.1, no changes needed.
.
  [ Thorsten Alteholz ]
  * Update standards version to 4.6.1, no changes needed.
  * deactivate race test (Closes: #1017234)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1017234

Bug#1025722: duck fails with 'Can't close(GLOB(0x558bebc05958)) filehandle: 'Is a directory' at /usr/share/duck/lib/checks/patch_files.pm line 101'

[gregor herrmann]

Package: duck
Version: 0.14.0
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: p...@packages.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As of today, duck (called in any source package directory) fails with

Can't close(GLOB(0x558bebc05958)) filehandle: 'Is a directory' at 
/usr/share/duck/lib/checks/patch_files.pm line 101'

92  # iterate over all patchdirs, process all files found
93  foreach my $patchdir (@patchdirs) {
94  my $dirhandle = dir($patchdir)->open;
95  
96  while (my $patchfile = $dirhandle->read) {
97  open my $pf, "<", $patchdir . "/" . $patchfile;
98  
99  my @pf_raw = <$pf>;
   100  
   101  close($pf);

This may or may not be caused by a recent change in src:perl [0], hence
cc'in the perl maintainers


Cheers,
gregor

[0]

perl (5.36.0-5) unstable; urgency=medium

  * Backported upstream changes:
+ only clear the stream error state in readline() for glob()
  (Closes: #1016369)
…

 -- Niko Tyni   Tue, 06 Dec 2022 11:43:06 +0200


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

Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages duck depends on:
ii  devscripts   2.22.2
ii  dpkg-dev 1.21.12
ii  libconfig-inifiles-perl  3.03-1
ii  libconfig-simple-perl4.59-6.1
ii  libdomain-publicsuffix-perl  0.19-2
ii  libfile-which-perl   1.27-2
ii  libmailtools-perl2.21-2
ii  libnet-dns-perl  1.35-1
ii  libparallel-forkmanager-perl 2.02-1
ii  libparse-debcontrol-perl 2.005-6
ii  libpath-class-perl   0.37-4
ii  libregexp-common-email-address-perl  1.01-6
ii  libregexp-common-perl2017060201-3
ii  libstring-similarity-perl1.04-3+b1
ii  libwww-curl-perl 4.17-8+b1
ii  libxml-xpath-perl1.48-1
ii  libyaml-libyaml-perl 0.84+ds-1+b1
ii  lynx 2.9.0dev.10-1+b1
ii  perl 5.36.0-5
ii  publicsuffix 20220811.1734-1

duck recommends no packages.

Versions of packages duck suggests:
ii  brz [bzr]   3.3.1-1
ii  git 1:2.38.1-1
ii  mercurial   6.3.1-2
ii  subversion  1.14.2-4+b1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmORJZlfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaZtw//QqED5auXM1gfiGMwnS/OjU6jPnHjZ6kKu8QM12jH35Pgv8+TMvOePliR
6cLLHA4+GooqUBLrBLIJSw49YzSuxV2SxesjD9RsKHRsLkeqOaAU4kAS1CnW1POp
qNZP7/qNjmOl0B7xeQEljehseILWgFmGEe3selRI0maHHwSLnMr0YmPN36kg3s0X
/8qPh0xOUrbrooeAH76rcOqapnA2RKoGq7SvuY4cmLvIz/SwHq18CADaMNFvW1u3
RRq8orKf7DXWkAoBIRfFg1HYBppYGWA4yn3k5GwRxS9/YYdDTOoYrDFbGQTFhnpZ
T+KSx1DaTPum6A3MkXgdSB+OFUlxzbvrt7y+ULz6+ZHe3kaqjPHMe6i1cjPnhD+s
nLZ7n5f67f0oZq7zHRTANIASCEWs+Xp2fuwGzs910A80LUUwe9vvNkEx6WEf7QdS
yAbChHZhkIfFI1B5Bh/dYdxklfmkj5KrfFCKaLChLKbEr3EgC3LdwI5sNvOuWu+7
EgyzntYCPg1BvmFE1cZYzcCmAfvF9OOEd7Om16j1Z1e/ydHycWJcm0OrROcZDroK
e2ZIcxE9B4lpSCVVyE0PeDjgqlEFLalI5EyJhktFz14kWOj6wdJ1ekufWRtw+N8R
sw87whJFSxgKZ4m4NtWWTVwpTCIxl36GyasLKv7/sNqZUSh2+1Q=
=P4E5
-END PGP SIGNATURE-

Bug#1025713: marked as done (isenkram FTBFS: error: version numbers in d/changelog and isenkram/__init__.py do not match)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 23:20:09 +
with message-id 
and subject line Bug#1025713: fixed in isenkram 0.48+nmu2
has caused the Debian Bug report #1025713,
regarding isenkram FTBFS: error: version numbers in d/changelog and 
isenkram/__init__.py do not match
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.)


-- 
1025713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: isenkram
Version: 0.48+nmu1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Bastian Germann 

https://buildd.debian.org/status/fetch.php?pkg=isenkram=all=0.48%2Bnmu1=1669982912=0

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'

error: version numbers in d/changelog and isenkram/__init__.py do not match

make[1]: *** [debian/rules:6: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: isenkram
Source-Version: 0.48+nmu2
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated isenkram package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Dec 2022 23:46:30 +0100
Source: isenkram
Architecture: source
Version: 0.48+nmu2
Distribution: unstable
Urgency: medium
Maintainer: Petter Reinholdtsen 
Changed-By: Bastian Germann 
Closes: 1025713
Changes:
 isenkram (0.48+nmu2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Correct version to satisfy version check (Closes: #1025713).
Checksums-Sha1:
 6771aad40bff7eef38f1f3d7d17aeef5f38aefa4 1701 isenkram_0.48+nmu2.dsc
 83b54663797d52a9c5ffe32d229ed944fe21b07a 52472 isenkram_0.48+nmu2.tar.xz
 cc249bf84c0cd13269f2335c89b94189715bc8a0 5542 
isenkram_0.48+nmu2_source.buildinfo
Checksums-Sha256:
 daa1fc8c6a4cd3434f652ef91879409d9861f93ac4b8a4648d89af6677b1f5cd 1701 
isenkram_0.48+nmu2.dsc
 d8d738593a7f58fb10454f88b9b082c429ce58dd7802eb78add42eb87915b355 52472 
isenkram_0.48+nmu2.tar.xz
 33c13e62643e9824a83ed46c9a21419ffa4d25f5b0d7bb17ffe391474ec4d5f2 5542 
isenkram_0.48+nmu2_source.buildinfo
Files:
 094188f7bb8a80e2ad0e6bc997150022 1701 misc optional isenkram_0.48+nmu2.dsc
 9c4a4cb2bc2fcb553b8d7404cc3c37b4 52472 misc optional isenkram_0.48+nmu2.tar.xz
 0daf81ede60e6514d025097960c35951 5542 misc optional 
isenkram_0.48+nmu2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmORGK4QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFD7yC/48XAKi8X/RYhsSRgOXDGs5ey1Y9Pp71x9f
lkEP+ICqBizjrCKU/PcdWQGGTsZWCOAv6z/bQL2w0M2JnurBMD8wxScdv71ILtqf
bvNeEFXBnEqs6CJrvYYa9QelJpMBLcx2WzEBnar5AHM/Zc6mDCt/szP7Kbmdyj83
kPcfFF7CwO8jKohRZ2MoNIVWj0nhF8AvnlPnwyQYu5DXlzLZlDkTr/ysxf2d420E
zgFtB7Q91hGbK8SmDCq7dnfYRiX1PuHhuMloGLdMXEBSj8yh8GNA6tudgkMl7GEG
ixd0dobsPL06J0G+N6raisXa+IMmJgisRMQ9X5e75JPiHyC+KJosAmH/ZCisN8B9
S76n+42oRbWep+dh4/4wu1gwgpxnszyhwfn6KiGT7IWerMgXp26AAPquCp0XQBTi
DJIedSAQLTAKAGtFuD3Hpyb4KdJyB20FyQ3Ao733kWSovTKLceKG9ILq1c7XF4Zd
NxmrHxVhB6IAuzSBJGMGwYddIRVuH9I=
=Ku25
-END PGP SIGNATURE End Message ---

Processed: bug 1020617 is forwarded to https://salsa.debian.org/julia-team/openlibm/-/merge_requests/2

[Debian Bug Tracking System]

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

> forwarded 1020617 
> https://salsa.debian.org/julia-team/openlibm/-/merge_requests/2
Bug #1020617 {Done: Paul Gevers } [src:openlibm] 
src:openlibm: fails to migrate to testing for too long: FTBFS on armhf and 
mips64el
Set Bug forwarded-to-address to 
'https://salsa.debian.org/julia-team/openlibm/-/merge_requests/2'.
> thanks
Stopping processing here.

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

Bug#1025311: solvespace: missing builds on mipsel and mips64el

[Ryan Pavlik]

Thanks for this advice on how to fix it better and unblock migration!

I've pushed an updated revision to both mentors and salsa. I'll reach
out to the science team for review and sponsorship.

On Fri, Dec 2, 2022 at 6:15 AM Graham Inggs  wrote:
>
> Source: solvespace
> Version: 3.1+ds1-2
> Severity: serious
> Tags: ftbfs
>
> Hi Maintainer
>
> The upload of solvespace 3.1+ds1-2 includes the change 'Drop s390x
> architecture due to test failures' [1], however the way this was done
> didn't only drop s390x, but also mipsel, mips64el, riscv64 and several
> other ports.  The missing builds on mipsel and mips64el now prevent
> migration of solvespace to testing.
>
> Seeing that solvespace builds fine on s390x, if the failing tests
> cannot be fixed, you could skip them on s390x only.  See my proposed
> debian/tests/control file below.  You could also try asking on
> debian-s...@lists.debian.org for help.
>
> Regards
> Graham
>
>
> [1] 
> https://salsa.debian.org/science-team/solvespace/-/commit/660e95c1d4583e078e31c5f91e7cd57f1aa1c7d1
>
>
> Tests: htmlmesh stlmesh surfaces
> Restrictions: allow-stderr
> Depends: solvespace, findutils, grep
> Architecture: !s390x
>
> Tests: thumbnail view wireframe
> Restrictions: allow-stderr
> Depends: solvespace, findutils, grep
>

Processed: found 1024998 in 0.3.3-2, fixed 1024998 in 0.3.3-2+deb10u1

[Debian Bug Tracking System]

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

> found 1024998 0.3.3-2
Bug #1024998 {Done: Stephen Kitt } [g810-led] g810-led: 
Security risk: Leaves /dev/input/event* with read and write permissions for all 
users (CVE-2022-46338)
Marked as found in versions g810-led/0.3.3-2.
> fixed 1024998 0.3.3-2+deb10u1
Bug #1024998 {Done: Stephen Kitt } [g810-led] g810-led: 
Security risk: Leaves /dev/input/event* with read and write permissions for all 
users (CVE-2022-46338)
There is no source info for the package 'g810-led' at version '0.3.3-2+deb10u1' 
with architecture ''
Unable to make a source version for version '0.3.3-2+deb10u1'
Marked as fixed in versions 0.3.3-2+deb10u1.
> thanks
Stopping processing here.

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

Bug#1025717: cross-toolchain-base-mipsen FTBFS: install: cannot change owner and permissions

[Adrian Bunk]

Source: cross-toolchain-base-mipsen
Version: 22
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=cross-toolchain-base-mipsen=all=22=1670437077=0

...
dh_installdirs -plinux-libc-dev-mips-cross \
  usr/share/doc/linux-libc-dev-mips-cross \
  usr/share/lintian/overrides \
  usr/mips-linux-gnu
install: cannot change owner and permissions of 
‘debian/linux-libc-dev-mips-cross/usr/share/doc/linux-libc-dev-mips-cross’: 
Operation not permitted
install: cannot change owner and permissions of 
‘debian/linux-libc-dev-mips-cross/usr/share/lintian/overrides’: Operation not 
permitted
install: cannot change owner and permissions of 
‘debian/linux-libc-dev-mips-cross/usr/mips-linux-gnu’: Operation not permitted
dh_installdirs: error: install -m0755 -o 0 -g 0 -d 
debian/linux-libc-dev-mips-cross/usr/share/doc/linux-libc-dev-mips-cross 
debian/linux-libc-dev-mips-cross/usr/share/lintian/overrides 
debian/linux-libc-dev-mips-cross/usr/mips-linux-gnu returned exit code 1
make: *** [debian/rules:162: stamp-dir/install-linux.mips] Error 25

Bug#1025713: isenkram FTBFS: error: version numbers in d/changelog and isenkram/__init__.py do not match

[Adrian Bunk]

Source: isenkram
Version: 0.48+nmu1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Bastian Germann 

https://buildd.debian.org/status/fetch.php?pkg=isenkram=all=0.48%2Bnmu1=1669982912=0

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'

error: version numbers in d/changelog and isenkram/__init__.py do not match

make[1]: *** [debian/rules:6: override_dh_auto_build] Error 1

Processed: retitle 1025711 to marble: qtwebengine5-dev build dependency restriction does not work

[Debian Bug Tracking System]

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

> retitle 1025711 marble: qtwebengine5-dev build dependency restriction does 
> not work
Bug #1025711 [src:marble] marble:
Changed Bug title to 'marble: qtwebengine5-dev build dependency restriction 
does not work' from 'marble:'.
> thanks
Stopping processing here.

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

Bug#1025712: marble: autopkgtest regression in 22.08.3-{1,2}

[Adrian Bunk]

Source: marble
Version: 4:22.08.3-2
Severity: serious
X-Debbugs-Cc: Sandro Knauß 

https://ci.debian.net/packages/m/marble/testing/amd64/

...
autopkgtest [22:10:52]: test acc: [---
cc1: warning: command-line option ‘-std=c++11’ is valid for C++/ObjC++ but not 
for C
cc1: warning: command-line option ‘-std=c++11’ is valid for C++/ObjC++ but not 
for C
Can't "next" outside a loop block at /usr/bin/abi-compliance-checker line 10171.
dh_acc: error: abi-compliance-checker -q -l libmarble-dev -v1 4:22.08.3-1 -dump 
debian/libmarble-dev.acc -dump-path 
debian/libmarble-dev/usr/lib/x86_64-linux-gnu/dh-acc/libmarble-dev_4:22.08.3-1.abi.tar.gz
 returned exit code 5
autopkgtest [22:11:17]: test acc: ---]
autopkgtest [22:11:17]: test acc:  - - - - - - - - - - results - - - - - - - - 
- -
acc  FAIL non-zero exit status 25
...

Bug#1025711: marble:

[Adrian Bunk]

Source: marble
Version: 4:22.08.3-2
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Sandro Knauß 

https://buildd.debian.org/status/package.php?p=marble=sid

Build-Depends: qtwebengine5-dev (>= 5.14.0~) [all amd64 arm64 armhf i386 
mips64el mipsel]

I suspect "all" might be interpreted as "binary-all" by some tools,
but as "all architectures" by other tools.

It might work better to write this as (untested):
Build-Depends: qtwebengine5-dev (>= 5.14.0~) [amd64 arm64 armhf i386 mips64el 
mipsel]
Build-Depends-Indep: qtwebengine5-dev (>= 5.14.0~)

Bug#1023684: marked as done (odb build depends on gcc-10 that should not be in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 21:05:49 +
with message-id 
and subject line Bug#1023684: fixed in odb 2.4.0-16
has caused the Debian Bug report #1023684,
regarding odb build depends on gcc-10 that should not be 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.)


-- 
1023684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: odb
Version: 2.4.0-15
Severity: serious
Control: block 1023666 by -1

Please switch to gcc-12 that is default in bookworm.
--- End Message ---
--- Begin Message ---
Source: odb
Source-Version: 2.4.0-16
Done: Laszlo Boszormenyi (GCS) 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Dec 2022 20:42:49 +0100
Source: odb
Architecture: source
Version: 2.4.0-16
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1023684
Changes:
 odb (2.4.0-16) unstable; urgency=medium
 .
   * Backport upstream patches to build with GCC 12 (closes: #1023684).
   * Update Standards-Version to 4.6.1 .
Checksums-Sha1:
 658a7615060ecc3028c098dcec32abfb8c2b6224 1753 odb_2.4.0-16.dsc
 f5884877adfa91035ac4f8fdf8e3c663252f74fd 15432 odb_2.4.0-16.debian.tar.xz
Checksums-Sha256:
 a212f01e0aa74c90a1fad602a01dd7253397f00a6117dc02cf53f3bed855dd02 1753 
odb_2.4.0-16.dsc
 b245f8ab6c6ae0f0ab8f56197f6da8ffb3c2b8c97ec07681bbaaa2d6fb0748e3 15432 
odb_2.4.0-16.debian.tar.xz
Files:
 7a778eefbbb06db9c15441f0f4d57b0d 1753 devel optional odb_2.4.0-16.dsc
 cb095d773dfad4d8d60cfcbb567759da 15432 devel optional 
odb_2.4.0-16.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmOQ+MUACgkQ3OMQ54ZM
yL/LUQ//YB9E7EjwlEJ524WGKG4mEM6EAfOTIFpFhuIFOVj6G7KvHgPx8kRalqh8
ODh1T2XAjJ6QYyBdE11Q2a0R7DnKJwJOZLWwr8aO/bycYvDI9i0z4Dc5eGdpsuS7
oF3clNBrcfXVwApLhX3QPFwFp3yDKa3G+YuHMt3Md0MCykoUFhi9GrqkzqUil3V3
hlzMJpVpa6kgWZF5nE5d/2ffadJ6kN8zSAd83wfv0XrV+cgamIci64JIta9ui88o
7G/eubieSROF/2RdE64Me+O6lya2nZ+tyaZ4KKuBzRAaPK8B1EmNgOFw5ebvTkOt
NB9DV+tDPY+S2tILGt7EoHU8ZJksHndnvDEJ7CQOQj4nzvnpHb3BgkcPmR/hQVyg
ZpK4qQQj/ylZOf+kkj+uDLqftHjoTrbIUlDxRu9rzr1BNq+mXy61OvjZsuY2yqd9
DwAdrIoJPITpXgoYyG2uDG3RF6YCeXyXHkTVJG1qBNueb9g7WizF13JnmambkazA
Dr98pj33tEO4n0jAN5ZXzMzmkSo0sNeROGfPHdnjDUN8SdkxhnI5WpcfCk5dhWcq
0AG0F0zURkBgtSZw9XznwDAiIPhZuXCnsYuCHNYNiVHOa9SDKxsxI/NazEnyLCzo
NhKY1JefPRVedZmoUJLtEB7PAE3c3+eoj8Rd7mLSVWp0x7Wvs8M=
=IXHp
-END PGP SIGNATURE End Message ---

Bug#1025648: marked as done (cacti: CVE-2022-46169: Unauthenticated Command Injection)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 21:04:23 +
with message-id 
and subject line Bug#1025648: fixed in cacti 1.2.22+ds1-3
has caused the Debian Bug report #1025648,
regarding cacti: CVE-2022-46169: Unauthenticated Command Injection
to be marked as done.

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

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


-- 
1025648: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025648
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cacti
Version: 1.2.22+ds1-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for cacti.

CVE-2022-46169[0]:
| Cacti is an open source platform which provides a robust and
| extensible operational monitoring and fault management framework for
| users. In affected versions a command injection vulnerability allows
| an unauthenticated user to execute arbitrary code on a server running
| Cacti, if a specific data source was selected for any monitored
| device. The vulnerability resides in the `remote_agent.php` file. This
| file can be accessed without authentication. This function retrieves
| the IP address of the client via `get_client_addr` and resolves this
| IP address to the corresponding hostname via `gethostbyaddr`. After
| this, it is verified that an entry within the `poller` table exists,
| where the hostname corresponds to the resolved hostname. If such an
| entry was found, the function returns `true` and the client is
| authorized. This authorization can be bypassed due to the
| implementation of the `get_client_addr` function. The function is
| defined in the file `lib/functions.php` and checks serval `$_SERVER`
| variables to determine the IP address of the client. The variables
| beginning with `HTTP_` can be arbitrarily set by an attacker. Since
| there is a default entry in the `poller` table with the hostname of
| the server running Cacti, an attacker can bypass the authentication
| e.g. by providing the header `Forwarded-For: TARGETIP`. This
| way the function `get_client_addr` returns the IP address of the
| server running Cacti. The following call to `gethostbyaddr` will
| resolve this IP address to the hostname of the server, which will pass
| the `poller` hostname check because of the default entry. After the
| authorization of the `remote_agent.php` file is bypassed, an attacker
| can trigger different actions. One of these actions is called
| `polldata`. The called function `poll_for_data` retrieves a few
| request parameters and loads the corresponding `poller_item` entries
| from the database. If the `action` of a `poller_item` equals
| `POLLER_ACTION_SCRIPT_PHP`, the function `proc_open` is used to
| execute a PHP script. The attacker-controlled parameter `$poller_id`
| is retrieved via the function `get_nfilter_request_var`, which allows
| arbitrary strings. This variable is later inserted into the string
| passed to `proc_open`, which leads to a command injection
| vulnerability. By e.g. providing the `poller_id=;id` the `id` command
| is executed. In order to reach the vulnerable call, the attacker must
| provide a `host_id` and `local_data_id`, where the `action` of the
| corresponding `poller_item` is set to `POLLER_ACTION_SCRIPT_PHP`. Both
| of these ids (`host_id` and `local_data_id`) can easily be
| bruteforced. The only requirement is that a `poller_item` with an
| `POLLER_ACTION_SCRIPT_PHP` action exists. This is very likely on a
| productive instance because this action is added by some predefined
| templates like `Device - Uptime` or `Device - Polling Time`. This
| command injection vulnerability allows an unauthenticated user to
| execute arbitrary commands if a `poller_item` with the `action` type
| `POLLER_ACTION_SCRIPT_PHP` (`2`) is configured. The authorization
| bypass should be prevented by not allowing an attacker to make
| `get_client_addr` (file `lib/functions.php`) return an arbitrary IP
| address. This could be done by not honoring the `HTTP_...` `$_SERVER`
| variables. If these should be kept for compatibility reasons it should
| at least be prevented to fake the IP address of the server running
| Cacti. This vulnerability has been addressed in both the 1.2.x and
| 1.3.x release branches with `1.2.23` being the first release
| containing the patch.


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-46169

Bug#1025118: marked as done (python-pytest-subtests: (autopkgtest) needs update for python3.11: AssertionError)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 20:40:25 +
with message-id 
and subject line Bug#1025118: fixed in python-pytest-subtests 0.9.0-1
has caused the Debian Bug report #1025118,
regarding python-pytest-subtests: (autopkgtest) needs update for python3.11: 
AssertionError
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.)


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

Source: python-pytest-subtests
Version: 0.8.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
python-pytest-subtests fails in testing when that autopkgtest is run 
with the binary packages of python3-defaults from unstable. It passes 
when run with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
python-pytest-subtests from testing0.8.0-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pytest-subtests/28750729/log.gz

=== FAILURES 
===
__ TestSubTest.test_simple_terminal_normal[unittest] 
___


self = 
simple_script = 
local('/tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2/test_simple_terminal_normal.py')
testdir = local('/tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2')>

runner = 'unittest'

@pytest.mark.parametrize("runner", ["unittest", "pytest-normal", 
"pytest-xdist"])

def test_simple_terminal_normal(self, simple_script, testdir, runner):
if runner == "unittest":
result = testdir.run(sys.executable, simple_script)

  result.stderr.fnmatch_lines(

[
"FAIL: test_foo (__main__.T) [custom] (i=1)",
"AssertionError: 1 != 0",
"FAIL: test_foo (__main__.T) [custom] (i=3)",
"AssertionError: 1 != 0",
"Ran 1 test in *",
"FAILED (failures=2)",
]
)
E   Failed: nomatch: 'FAIL: test_foo (__main__.T) [custom] (i=1)'
E   and: 'FF'
E   and: 
'=='

E   and: 'FAIL: test_foo (__main__.T.test_foo) [custom] (i=1)'
E   and: 
'--'

E   and: 'Traceback (most recent call last):'
E   and: '  File 
"/tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2/test_simple_terminal_normal.py", 
line 8, in test_foo'

E   and: 'self.assertEqual(i % 2, 0)'
E   and: 'AssertionError: 1 != 0'
E   and: ''
E   and: 
'=='

E   and: 'FAIL: test_foo (__main__.T.test_foo) [custom] (i=3)'
E   and: 
'--'

E   and: 'Traceback (most recent call last):'
E   and: '  File 
"/tmp/pytest-of-debci/pytest-0/test_simple_terminal_normal2/test_simple_terminal_normal.py", 
line 8, in test_foo'

E   and: 'self.assertEqual(i % 2, 0)'
E   and: 'AssertionError: 1 != 0'
E   and: ''
E   and: 
'--'

E   and: 'Ran 1 test in 0.001s'
E   and: ''
E   and: 'FAILED (failures=2)'
E   remains unmatched: 'FAIL: test_foo (__main__.T) [custom] (i=1)'

Bug#1025709: src:ruby-grape: unsatisfied build dependency in testing: ruby-grape-entity

[Paul Gevers]

Source: ruby-grape
Version: 1.6.2-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024162: closing 1024162

[Paul Gevers]

Hi,

On 07-12-2022 16:02, IOhannes m zmölnig (Debian/GNU) wrote:

libgmm++-dev has entered testing on 2022-12-04.

shouldn't this bug have been closed automatically, as soon as the missing B-Ds
were available again?


There is nothing automatic yet; there's a lot of shoulds in Debian :). 
Feel free to be the one making the automation. Or even better, help 
improve the existing tools to *prevent* the situation.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024856: marked as done (azure-cli: (autopkgtest) needs update for python3.11: conflicting subparser: configure)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 19:36:37 +
with message-id 
and subject line Bug#1024856: fixed in azure-cli 2.43.0-1
has caused the Debian Bug report #1024856,
regarding azure-cli: (autopkgtest) needs update for python3.11: conflicting 
subparser: configure
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.)


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

Source: azure-cli
Version: 2.42.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
azure-cli fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
azure-cli  from testing2.42.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/a/azure-cli/28706375/log.gz

_ ERROR at teardown of 
ConfigureGlobalDefaultsTest.test_configure_global_defaults _


self = testMethod=test_configure_global_defaults>


def tearDown(self):

  self.cmd('configure --defaults global="" global2=""')


tests_core/test_configure.py:33: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/azure/cli/testsdk/base.py:170: in cmd
return execute(self.cli_ctx, command, 
expect_failure=expect_failure).assert_with_checks(checks)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

self = 
cli_ctx = 
command = 'configure --defaults global="" global2=""', expect_failure = 
False


def __init__(self, cli_ctx, command, expect_failure=False):
self.output = ''
self.applog = ''
self.command_coverage = {}
cli_ctx.data['_cache'] = None
if os.environ.get(ENV_COMMAND_COVERAGE, None):
with open(COVERAGE_FILE, 'a') as coverage_file:
if command.startswith('az '):
command = command[3:]
coverage_file.write(command + '\n')
self._in_process_execute(cli_ctx, command, 
expect_failure=expect_failure)

log_val = ('Logging ' + self.applog) if self.applog else ''
if expect_failure and self.exit_code == 0:
logger.error('Command "%s" => %d. (It did not fail as 
expected). %s\n', command,

 self.exit_code, log_val)
raise AssertionError('The command did not fail as it was 
expected.')

if not expect_failure and self.exit_code != 0:
logger.error('Command "%s" => %d. %s\n', command, 
self.exit_code, log_val)

  raise AssertionError('The command failed. Exit code: 
{}'.format(self.exit_code))

E   AssertionError: The command failed. Exit code: 1

/usr/lib/python3/dist-packages/azure/cli/testsdk/base.py:253: AssertionError
- Captured stderr call 
-
To check existing issues, please visit: 
https://github.com/Azure/azure-cli/issues

To open a new issue, please run `az feedback`
To check existing issues, please visit: 
https://github.com/Azure/azure-cli/issues

To open a new issue, please run `az feedback`
-- Captured log call 
---
INFO az_command_data_logger:azlogging.py:128 command args: configure 
--defaults {}
ERRORcli.azure.cli.core.azclierror:azlogging.py:212 The command 
failed with an unexpected error. Here is the traceback:
ERRORaz_command_data_logger:azlogging.py:213 The command failed with 
an unexpected error. Here is the traceback:
ERROR

Bug#1023684: odb build depends on gcc-10 that should not be in bookworm

[Adrian Bunk]

Control: tags -1 patch

On Tue, Nov 08, 2022 at 08:50:12PM +0200, Adrian Bunk wrote:
> Source: odb
> Version: 2.4.0-15
> Severity: serious
> Control: block 1023666 by -1
> 
> Please switch to gcc-12 that is default in bookworm.

The following commits make odb build with gcc-12:
https://git.codesynthesis.com/cgit/odb/odb/commit/?id=61d80f051293a7449a09081f60f48b8377bfbbad
https://git.codesynthesis.com/cgit/odb/odb/commit/?id=47035c0f72efd99a2210cd45db6e42423fb74533

cu
Adrian

Processed: Re: Bug#1023684: odb build depends on gcc-10 that should not be in bookworm

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1023684 [src:odb] odb build depends on gcc-10 that should not be in 
bookworm
Added tag(s) patch.

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

Bug#1024724: closing 1024724

[Fabian Gruenbichler]

close 1024724 0.63.1-3
thanks

worked-around by temporarily skipping the two failing test cases - the
cause is actually in rustc, and should be fixed with rustc >= 1.63 which
in turn requires cargo >= 0.60 and is already waiting in experimental.

Processed: closing 1024724

[Debian Bug Tracking System]

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

> close 1024724 0.63.1-3
Bug #1024724 [src:cargo] cargo: FTBFS on armel
Marked as fixed in versions cargo/0.63.1-3.
Bug #1024724 [src:cargo] cargo: FTBFS on armel
Marked Bug as done
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 19:02:38 +
with message-id 
and subject line Bug#1023732: fixed in xfce4-settings 4.16.0-1+deb11u1
has caused the Debian Bug report #1023732,
regarding xfce4-settings: CVE-2022-45062: argument injection vulnerability in 
xfce4-mime-helper
to be marked as done.

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

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


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

Hi,

The following vulnerability was published for xfce4-settings.

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


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-45062
https://www.cve.org/CVERecord?id=CVE-2022-45062
[1] https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/390 (not public)
[2] 
https://gitlab.xfce.org/xfce/xfce4-settings/-/commit/55e3c5fb667e96ad1412cf249879262b369d28d7
 (xfce4-settings-4.16.4)
[3] 
https://gitlab.xfce.org/xfce/xfce4-settings/-/commit/f34a92a84f96268ad24a7a13fd5edc9f1d526110
 (xfce4-settings-4.17.1)

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: xfce4-settings
Source-Version: 4.16.0-1+deb11u1
Done: Yves-Alexis Perez 

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

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

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated xfce4-settings 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Dec 2022 13:50:21 +0100
Source: xfce4-settings
Architecture: source
Version: 4.16.0-1+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Closes: 1023732
Changes:
 xfce4-settings (4.16.0-1+deb11u1) bullseye-security; urgency=medium
 .
   * d/gbp.conf: follow bullseye-security branch.
 Gbp-dch: ignore
   * d/patches: 0002-mime-settings-Properly-quote-command-parameters added.
 Fix argument injection in xfce4-mime-helper (CVE-2022-45062)
 (Closes: #1023732)
Checksums-Sha1:
 1f351e4336d45aa134fadef809918ce714b7b28f 2084 
xfce4-settings_4.16.0-1+deb11u1.dsc
 3ae863cc28a74ea5847cb5a9be1261171eb8328f 1492754 
xfce4-settings_4.16.0.orig.tar.bz2
 6b5b66968fb1e8676bf7c2623c3f025478183e21 9668 
xfce4-settings_4.16.0-1+deb11u1.debian.tar.xz
 f49db60ece44ae94aaecfd8e4629646fdb7f6ae2 16485 
xfce4-settings_4.16.0-1+deb11u1_amd64.buildinfo
Checksums-Sha256:
 226fdddf12965466f7808a6b835e0051ef87c2dd3eb82c14097938b7361eb1a4 2084 
xfce4-settings_4.16.0-1+deb11u1.dsc
 67a1404fc754c675c6431e22a8fe0e5d79644fdfadbfe25a4523d68e1442ddc2 1492754 
xfce4-settings_4.16.0.orig.tar.bz2
 f68138a8fc704e44224f5771aaf68a6e81dbc18a55c431d770de86cba2d69b29 9668 
xfce4-settings_4.16.0-1+deb11u1.debian.tar.xz
 ed38a969fdc5c1af77b83bc4fc8676266675addb04cf1f5db7218797888d6f73 16485 
xfce4-settings_4.16.0-1+deb11u1_amd64.buildinfo
Files:
 b8c2d4edf9b54465933d0b04788c2cf8 2084 xfce optional 
xfce4-settings_4.16.0-1+deb11u1.dsc
 3aa1f4edb1190f5c164d5760688f247a 1492754 xfce optional 
xfce4-settings_4.16.0.orig.tar.bz2
 2c5f29960631db3d4677c3d9ffd711db 9668 xfce optional 
xfce4-settings_4.16.0-1+deb11u1.debian.tar.xz
 26090e0472450d7cecf76116feb1dac8 16485 xfce optional 
xfce4-settings_4.16.0-1+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmOMeKsACgkQ3rYcyPpX
RFujtAf+K0RZlsA67Z6/9C6Qp33GquJXmc29q0SRFoLzW6OjyMwhQDxD6llkPtsG
D8RLuPS9uPyV6NE32eTJRTc1Ihpp3BOQ3PF5D2bZHoQXWuIaNaJ8gfFTX6i9wban
tpbBUaThdS796fGb2Oum3/oIdTz0/2yB4GRYq/yIKKxNKO6qG8R2KIlFIJFOWEak
Q9Xvs3S4K2udRBJabOPmCT8V54WbH4kVa9L20yZMq+YCOxHg3cCoQ7B43wFOZYvL

Bug#1023303: marked as done (jhead 1:3.06.0.1-3 deletes EXIF data)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 19:02:08 +
with message-id 
and subject line Bug#1023303: fixed in jhead 1:3.04-6+deb11u1
has caused the Debian Bug report #1023303,
regarding jhead 1:3.06.0.1-3 deletes EXIF data
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.)


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

Package: jhead
Version: 1:3.06.0.1-3
Severity: grave


jhead version 1:3.06.0.1-3 deletes EXIF data when rotating images:

$ exiftool IMG_20221102_000230.jpg | wc -l

77



$ jhead -autorot IMG_20221102_000230.jpg



Nonfatal Error : 'IMG_20221102_000230.jpg' Command has invalid characters.



$ exiftool IMG_20221102_000230.jpg | wc -l

23





jhead 1:3.06.0.1-2 is not affected.
--- End Message ---
--- Begin Message ---
Source: jhead
Source-Version: 1:3.04-6+deb11u1
Done: Joachim Reichel 

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

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

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

Debian distribution maintenance software
pp.
Joachim Reichel  (supplier of updated jhead package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 04 Dec 2022 10:35:31 +0100
Source: jhead
Architecture: source
Version: 1:3.04-6+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Joachim Reichel 
Changed-By: Joachim Reichel 
Closes: 1022028 1023303 1024272
Changes:
 jhead (1:3.04-6+deb11u1) bullseye-security; urgency=medium
 .
   * New maintainer.
   * Add patch fix_cve_2021_34055 to fix CVE-2021-34055 (Closes: #1024272).
   * Add patch fix_cve_2022_41751 to fix CVE-2022-41751 (Closes: #1022028,
 #1023303).
Checksums-Sha1:
 87c69dd80ec046ecef8dab1d58154a25233879e8 1823 jhead_3.04-6+deb11u1.dsc
 914ee3944d582bf3b3df8b208fffba6b8b07d2f3 67754 jhead_3.04.orig.tar.gz
 46fac10c9ba21015420b1d1792decea842157998 9992 
jhead_3.04-6+deb11u1.debian.tar.xz
 f8020316dabe0a7b99b53799c1c8e1783f538f57 6349 
jhead_3.04-6+deb11u1_amd64.buildinfo
Checksums-Sha256:
 7626622680cba489882a163a7eddebabbf079a16c37b917e526923a9a27581fa 1823 
jhead_3.04-6+deb11u1.dsc
 ef89bbcf4f6c25ed88088cf242a47a6aedfff4f08cc7dc205bf3e2c0f10a03c9 67754 
jhead_3.04.orig.tar.gz
 62ebd80ce4e3ef78f9e9b33705c8d4458db6c72681608a4176cc076697a611b2 9992 
jhead_3.04-6+deb11u1.debian.tar.xz
 346db35f5201e2804baa0f8f479c38c90d5ef17826d0779fb9dd29c19e4239ed 6349 
jhead_3.04-6+deb11u1_amd64.buildinfo
Files:
 f35e57a78cb1bbbcebae965b43ac7d32 1823 graphics optional 
jhead_3.04-6+deb11u1.dsc
 9c046e75a07c6e6e94945e8455c503c2 67754 graphics optional jhead_3.04.orig.tar.gz
 7c1e60fa759cf55a99d04ac067f051c7 9992 graphics optional 
jhead_3.04-6+deb11u1.debian.tar.xz
 62f995077781ff0adbfa8f55148c047e 6349 graphics optional 
jhead_3.04-6+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErX6NzLwwsr4xjsEVuPr/HEOIZ3EFAmOMawYACgkQuPr/HEOI
Z3HlBBAAp+2TEYJW1gu6y89B/rIcdxI4gQQjE22vt6kx/aIVpH96P5A/gnoObgAn
oZFwvnnzlufptxm0LZZYepQ9QScO3fXvfZ6+fIZT7NkzL5x2XRCOFJgCKE8vL2u1
IMDZJlOrPz6DDVuymGNxie50RQLsoFbREARI5uMiG5o4IhRlGPxD5eJBEaccXTZM
AZOs98lsHaE9Ju1bcehCxwseE1N2VaSFD4qJK+T3y/ENfmyyt7X9D9sSO21dGC6E
A51O80idFhZ+9v5Q3CbcIPChZ4e6HhYf7zwRNqcVMQs536n3m7yF0UKMy9Pny6eA
NxoTIP7ZqsvX16S70jZLtxPT9xHPjF6g5T2AKKRjiZakVkEzmnzPAtH1ohJxdjjn
2MpR2EfXpQXN6vynO1vWED5SoMC08xccdSZiswmYr6hNuTgniWR+UZP2vuWKVHgq
vE0JZVfSb4bCyjOTKXs639BHNi9Yrh7wF+sjUetTBkVGaUTYurV+b5HSt0xdl5I4
eA5+hnCWJU7zf32tjZRZ0Jbhx+3BnV4D3/jYaP+VkHvYVtTIx8Wlr4/wEx/uYnZi
CqRP69qs+w5dLRLZ3y9/j/hJbnTlwNe7qhYCjSSV1+h2IlfJYMATuoSjPPfXwrzS
BFcvKCucBHJE/D+FbjnAB+c0v/vGho3jH0dCUgglsLd+LI7AZQw=
=CvKM
-END PGP SIGNATURE End Message ---

Bug#1022028: marked as done (jhead: CVE-2022-41751)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 19:02:08 +
with message-id 
and subject line Bug#1022028: fixed in jhead 1:3.04-6+deb11u1
has caused the Debian Bug report #1022028,
regarding jhead: CVE-2022-41751
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.)


-- 
1022028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jhead
Version: 1:3.06.0.1-2
Severity: grave
Tags: security upstream
Forwarded: https://github.com/Matthias-Wandel/jhead/pull/57
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for jhead.

CVE-2022-41751[0]:
| Jhead 3.06.0.1 allows attackers to execute arbitrary OS commands by
| placing them in a JPEG filename and then using the regeneration -rgt50
| option.

>From context I'm not yet really conviced we need a DSA for it, as a
user needs to be tricked into processing a specially crafted filename.
keeping RC severity though to make sure the fix land in bookworm.

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-41751
https://www.cve.org/CVERecord?id=CVE-2022-41751
[1] https://github.com/Matthias-Wandel/jhead/pull/57

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: jhead
Source-Version: 1:3.04-6+deb11u1
Done: Joachim Reichel 

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

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

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

Debian distribution maintenance software
pp.
Joachim Reichel  (supplier of updated jhead package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 04 Dec 2022 10:35:31 +0100
Source: jhead
Architecture: source
Version: 1:3.04-6+deb11u1
Distribution: bullseye-security
Urgency: medium
Maintainer: Joachim Reichel 
Changed-By: Joachim Reichel 
Closes: 1022028 1023303 1024272
Changes:
 jhead (1:3.04-6+deb11u1) bullseye-security; urgency=medium
 .
   * New maintainer.
   * Add patch fix_cve_2021_34055 to fix CVE-2021-34055 (Closes: #1024272).
   * Add patch fix_cve_2022_41751 to fix CVE-2022-41751 (Closes: #1022028,
 #1023303).
Checksums-Sha1:
 87c69dd80ec046ecef8dab1d58154a25233879e8 1823 jhead_3.04-6+deb11u1.dsc
 914ee3944d582bf3b3df8b208fffba6b8b07d2f3 67754 jhead_3.04.orig.tar.gz
 46fac10c9ba21015420b1d1792decea842157998 9992 
jhead_3.04-6+deb11u1.debian.tar.xz
 f8020316dabe0a7b99b53799c1c8e1783f538f57 6349 
jhead_3.04-6+deb11u1_amd64.buildinfo
Checksums-Sha256:
 7626622680cba489882a163a7eddebabbf079a16c37b917e526923a9a27581fa 1823 
jhead_3.04-6+deb11u1.dsc
 ef89bbcf4f6c25ed88088cf242a47a6aedfff4f08cc7dc205bf3e2c0f10a03c9 67754 
jhead_3.04.orig.tar.gz
 62ebd80ce4e3ef78f9e9b33705c8d4458db6c72681608a4176cc076697a611b2 9992 
jhead_3.04-6+deb11u1.debian.tar.xz
 346db35f5201e2804baa0f8f479c38c90d5ef17826d0779fb9dd29c19e4239ed 6349 
jhead_3.04-6+deb11u1_amd64.buildinfo
Files:
 f35e57a78cb1bbbcebae965b43ac7d32 1823 graphics optional 
jhead_3.04-6+deb11u1.dsc
 9c046e75a07c6e6e94945e8455c503c2 67754 graphics optional jhead_3.04.orig.tar.gz
 7c1e60fa759cf55a99d04ac067f051c7 9992 graphics optional 
jhead_3.04-6+deb11u1.debian.tar.xz
 62f995077781ff0adbfa8f55148c047e 6349 graphics optional 
jhead_3.04-6+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErX6NzLwwsr4xjsEVuPr/HEOIZ3EFAmOMawYACgkQuPr/HEOI
Z3HlBBAAp+2TEYJW1gu6y89B/rIcdxI4gQQjE22vt6kx/aIVpH96P5A/gnoObgAn
oZFwvnnzlufptxm0LZZYepQ9QScO3fXvfZ6+fIZT7NkzL5x2XRCOFJgCKE8vL2u1
IMDZJlOrPz6DDVuymGNxie50RQLsoFbREARI5uMiG5o4IhRlGPxD5eJBEaccXTZM
AZOs98lsHaE9Ju1bcehCxwseE1N2VaSFD4qJK+T3y/ENfmyyt7X9D9sSO21dGC6E
A51O80idFhZ+9v5Q3CbcIPChZ4e6HhYf7zwRNqcVMQs536n3m7yF0UKMy9Pny6eA
NxoTIP7ZqsvX16S70jZLtxPT9xHPjF6g5T2AKKRjiZakVkEzmnzPAtH1ohJxdjjn
2MpR2EfXpQXN6vynO1vWED5SoMC08xccdSZiswmYr6hNuTgniWR+UZP2vuWKVHgq
vE0JZVfSb4bCyjOTKXs639BHNi9Yrh7wF+sjUetTBkVGaUTYurV+b5HSt0xdl5I4

Bug#1013662: marked as done (core-async-clojure: FTBFS randomly in bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 19:02:08 +
with message-id 
and subject line Bug#1013662: fixed in core-async-clojure 1.3.610-5+deb11u1
has caused the Debian Bug report #1013662,
regarding core-async-clojure: FTBFS randomly in 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.)


-- 
1013662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: core-async-clojure
Version: 1.3.610-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 '/<>'
> lein test
> 
> lein test clojure.core.async-test
> 
> lein test :only clojure.core.async-test/ops-tests
> 
> FAIL in (ops-tests) (async_test.clj:303)
> mult
> expected: (= 1 (a/poll! t-1))
>   actual: (not (= 1 nil))
> 
> lein test :only clojure.core.async-test/ops-tests
> 
> FAIL in (ops-tests) (async_test.clj:304)
> mult
> expected: (= nil (a/poll! t-1))
>   actual: (not (= nil 1))
> 
> lein test clojure.core.async.buffers-test
> 
> lein test clojure.core.async.concurrent-test
> 
> lein test clojure.core.async.exceptions-test
> 
> lein test clojure.core.async.ioc-macros-test
> Exception in thread "async-dispatch-9" java.lang.AssertionError: Assert 
> failed: This exception is expected
> false
>   at 
> clojure.core.async.ioc_macros_test$fn__12939$fn__12999$state_machine__6955__auto13004$fn__13006.invoke(ioc_macros_test.clj:465)
>   at 
> clojure.core.async.ioc_macros_test$fn__12939$fn__12999$state_machine__6955__auto13004.invoke(ioc_macros_test.clj:464)
>   at 
> clojure.core.async.impl.ioc_macros$run_state_machine.invokeStatic(ioc_macros.clj:978)
>   at 
> clojure.core.async.impl.ioc_macros$run_state_machine.invoke(ioc_macros.clj:977)
>   at 
> clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invokeStatic(ioc_macros.clj:982)
>   at 
> clojure.core.async.impl.ioc_macros$run_state_machine_wrapped.invoke(ioc_macros.clj:980)
>   at 
> clojure.core.async.ioc_macros_test$fn__12939$fn__12999.invoke(ioc_macros_test.clj:464)
>   at clojure.lang.AFn.run(AFn.java:22)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>   at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>   at 
> clojure.core.async.impl.concurrent$counted_thread_factory$reify__720$fn__721.invoke(concurrent.clj:29)
>   at clojure.lang.AFn.run(AFn.java:22)
>   at java.base/java.lang.Thread.run(Thread.java:829)
> 
> lein test clojure.core.async.lab-test
> 
> lein test clojure.core.async.timers-test
> 
> lein test clojure.core.pipeline-test
> 
> Ran 51 tests containing 346 assertions.
> 2 failures, 0 errors.
> Tests failed.
> make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/core-async-clojure_1.3.610-5_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: core-async-clojure
Source-Version: 1.3.610-5+deb11u1
Done: Jérôme Charaoui 

We believe that the bug you reported is fixed in the latest version of
core-async-clojure, 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.
Jérôme Charaoui  (supplier of updated core-async-clojure 
package)

(This message was generated automatically at their request; if you
believe that there is a problem 

Bug#931002: Removed package(s) from unstable

[Blair Noctis]

On Sun, 8 Sep 2019 13:58:06 +0200 (CEST) Santiago Vila  wrote:>
This was automatically closed by ftpmaster because the package was
> removed from unstable, but this still does not fix the FTBFS problem
> in stable.

It's now only in oldstable, nothing depends on it, and it requires a nightly
rustc which we currently don't have. Is it safe to close this?

-- 
Sdrager,
Blair Noctis


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1025187: marked as done (golang-github-crewjam-saml: CVE-2022-41912: Signature bypass via multiple Assertion elements)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 17:49:32 +
with message-id 
and subject line Bug#1025187: fixed in golang-github-crewjam-saml 0.4.10-1
has caused the Debian Bug report #1025187,
regarding golang-github-crewjam-saml: CVE-2022-41912: Signature bypass via 
multiple Assertion elements
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.)


-- 
1025187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-crewjam-saml
Version: 0.4.6-3
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-github-crewjam-saml.

CVE-2022-41912[0]:
| The crewjam/saml go library prior to version 0.4.9 is vulnerable to an
| authentication bypass when processing SAML responses containing
| multiple Assertion elements. This issue has been corrected in version
| 0.4.9. There are no workarounds other than upgrading to a fixed
| version.


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-41912
https://www.cve.org/CVERecord?id=CVE-2022-41912
[1] https://github.com/crewjam/saml/security/advisories/GHSA-j2jp-wvqg-wc2g

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: golang-github-crewjam-saml
Source-Version: 0.4.10-1
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated 
golang-github-crewjam-saml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Dec 2022 12:19:49 +0100
Source: golang-github-crewjam-saml
Architecture: source
Version: 0.4.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Thorsten Alteholz 
Closes: 1025187
Changes:
 golang-github-crewjam-saml (0.4.10-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #1025187)
 Fix for CVE-2022-41912
   * according to ratt nothing needs to be rebuild
Checksums-Sha1:
 9edcb66ec7e61ea8044b35bb863c1157dbc12f36 2804 
golang-github-crewjam-saml_0.4.10-1.dsc
 f4edcac26ba0d871de30bd7874bbad9ab59f515a 305542 
golang-github-crewjam-saml_0.4.10.orig.tar.gz
 4adc0a8dc05aff1ac387e8f451bc79ba7f0f59ff 2840 
golang-github-crewjam-saml_0.4.10-1.debian.tar.xz
 0b921b1a1943d8288ba7d04e769a8120cd16cce4 8036 
golang-github-crewjam-saml_0.4.10-1_amd64.buildinfo
Checksums-Sha256:
 20d7c12e9b80eb6d24889eddbd14bcdc4166ab3ac668d20347ed676390470a82 2804 
golang-github-crewjam-saml_0.4.10-1.dsc
 439e9afabf4bf4792eea28ea6f59413cb29f855df3b1d77afc03f78e5fddbde6 305542 
golang-github-crewjam-saml_0.4.10.orig.tar.gz
 530865e1f379bc0f4402a867b217aab96cd4b762f07a30fd2fb3d36972276e87 2840 
golang-github-crewjam-saml_0.4.10-1.debian.tar.xz
 e8546fdc70005e921cf9b2ce80481f5bd5878df814f80694be106958a1418257 8036 
golang-github-crewjam-saml_0.4.10-1_amd64.buildinfo
Files:
 f2b3d40a5138410fed3fa9e0dc60525e 2804 devel optional 
golang-github-crewjam-saml_0.4.10-1.dsc
 aaecef2f93ecd774152e937a599c8a32 305542 devel optional 
golang-github-crewjam-saml_0.4.10.orig.tar.gz
 147caf14886b6aca952a69e0a9d3c94a 2840 devel optional 
golang-github-crewjam-saml_0.4.10-1.debian.tar.xz
 95715d139d3bd44b6bbfbfcef8385e02 8036 devel optional 
golang-github-crewjam-saml_0.4.10-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmOQzn9fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy
MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh
bHRlaG9sei5kZQAKCRCW/KwNOHtYR/yHEACuXjSuRS3yX7sIOGfvcJkHsUGoNLcg
T8w8CKETYoVB5nrqCKNKh8J4wNLNA0pftAmuSSPlWs7Jnu1mBdfK0STGgmv1K/mU
ydpDQrNvbilExvh0SZGYnMpxXxE0FwpIohI++bPKOanKUEkKO0WPgp85qovjiJf2
uqOw8klGmq5vH5X8GOvplVdMTMVPHpZf/iIgH9zdRUi3orOywfnufoNjKarnellt

Processed: Bug#1024856 marked as pending in azure-cli

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1024856 [src:azure-cli] azure-cli: (autopkgtest) needs update for 
python3.11: conflicting subparser: configure
Added tag(s) pending.

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

Bug#1024856: marked as pending in azure-cli

[Luca Boccassi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/azure-cli/-/commit/140f1848074139754e4562cf608a6f383f0b30e8


Add patch to fix build with Python 3.11

Closes: #1024856


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1024856

Processed (with 1 error): archiving 946942, archiving 949954, archiving 1009073

[Debian Bug Tracking System]

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

> archive 946942
Bug #946942 {Done: Gert Wollny } [src:virglrenderer] 
virglrenderer: CVE-2019-18389 CVE-2019-18391
archived 946942 to archive/42 (from 946942)
> archive 949954
Bug #949954 {Done: Debian FTP Masters } 
[src:virglrenderer] virglrenderer: CVE-2020-8002 CVE-2020-8003
archived 949954 to archive/54 (from 949954)
> archive 1009073
Bug #1009073 {Done: Gert Wollny } [src:virglrenderer] 
virglrenderer: CVE-2022-0135: out-of-bounds write in read_transfer_data()
Bug 1009073 cannot be archived
> thanks
Stopping processing here.

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

Processed: fixed 946942 in virglrenderer/0.7.0-2+deb10u1, fixed 949954 in virglrenderer/0.7.0-2+deb10u1 ...

[Debian Bug Tracking System]

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

> fixed 946942 virglrenderer/0.7.0-2+deb10u1
Bug #946942 {Done: Gert Wollny } [src:virglrenderer] 
virglrenderer: CVE-2019-18389 CVE-2019-18391
The source virglrenderer and version 0.7.0-2+deb10u1 do not appear to match any 
binary packages
Marked as fixed in versions virglrenderer/0.7.0-2+deb10u1.
> fixed 949954 virglrenderer/0.7.0-2+deb10u1
Bug #949954 {Done: Debian FTP Masters } 
[src:virglrenderer] virglrenderer: CVE-2020-8002 CVE-2020-8003
The source virglrenderer and version 0.7.0-2+deb10u1 do not appear to match any 
binary packages
Marked as fixed in versions virglrenderer/0.7.0-2+deb10u1.
> fixed 1009073 virglrenderer/0.7.0-2+deb10u1
Bug #1009073 {Done: Gert Wollny } [src:virglrenderer] 
virglrenderer: CVE-2022-0135: out-of-bounds write in read_transfer_data()
The source virglrenderer and version 0.7.0-2+deb10u1 do not appear to match any 
binary packages
Marked as fixed in versions virglrenderer/0.7.0-2+deb10u1; no longer marked as 
fixed in versions virglrenderer/0.7.0-2+deb10u1.
> thanks
Stopping processing here.

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

Processed (with 1 error): unarchiving 946942, unarchiving 949954, unarchiving 1009073

[Debian Bug Tracking System]

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

> unarchive 946942
Bug #946942 {Done: Gert Wollny } [src:virglrenderer] 
virglrenderer: CVE-2019-18389 CVE-2019-18391
Unarchived Bug 946942
> unarchive 949954
Bug #949954 {Done: Debian FTP Masters } 
[src:virglrenderer] virglrenderer: CVE-2020-8002 CVE-2020-8003
Unarchived Bug 949954
> unarchive 1009073
> thanks
Stopping processing here.

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

Processed (with 2 errors): fixed 946942 in virglrenderer/0.7.0-2+deb10u1, fixed 949954 in virglrenderer/0.7.0-2+deb10u1 ...

[Debian Bug Tracking System]

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

> fixed 946942 virglrenderer/0.7.0-2+deb10u1
Failed to add fixed on 946942: Not altering archived bugs; see unarchive.

> fixed 949954 virglrenderer/0.7.0-2+deb10u1
Failed to add fixed on 949954: Not altering archived bugs; see unarchive.

> fixed 1009073 virglrenderer/0.7.0-2+deb10u1
Bug #1009073 {Done: Gert Wollny } [src:virglrenderer] 
virglrenderer: CVE-2022-0135: out-of-bounds write in read_transfer_data()
The source virglrenderer and version 0.7.0-2+deb10u1 do not appear to match any 
binary packages
Marked as fixed in versions virglrenderer/0.7.0-2+deb10u1.
> thanks
Stopping processing here.

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

Processed: autopkgtest fails on armel against atlas 3.10.3-13

[Debian Bug Tracking System]

Processing control commands:

> affects -1 atlas
Bug #1025699 [src:scipy] autopkgtest fails on armel against atlas 3.10.3-13
Added indication that 1025699 affects atlas

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

Bug#1025699: autopkgtest fails on armel against atlas 3.10.3-13

[Sébastien Villemot]

Source: scipy
Version: 1.8.1-14
Severity: serious
Control: affects -1 atlas

Dear Maintainer,

Since the upload of atlas 3.10.3-13 to unstable, the autopkgtest of scipy fails
on armel. See:
https://ci.debian.net/data/autopkgtest/testing/armel/s/scipy/29064436/log.gz

More precisely, a test in sparse/linalg/_eigen/tests/test_svds.py fails because
the error is now slightly above tolerance. Simply increasing the tolerance
should fix the problem.

Note that the only numerically significant change in 3.10.3-13 was the rebuild
against lapack 3.11, hence the latter is probably the real cause of the problem
(though it may also be a change in the toolchain). In particular, note that
this issue transitively prevents lapack 3.11 from migrating to
testing/bookworm.

Incidentally, you should be aware that atlas has not seen a stable major
upstream since 2016; it has also been superseded by better alternatives like
OpenBLAS and BLIS; I’m therefore considering its possible removal during the
trixie development cycle.

Thanks for your work,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org

Bug#1024162: closing 1024162

[Debian/GNU]

close 1024162 
thanks

libgmm++-dev has entered testing on 2022-12-04.

shouldn't this bug have been closed automatically, as soon as the missing B-Ds
were available again?

cheers

Processed: closing 1024162

[Debian Bug Tracking System]

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

> close 1024162
Bug #1024162 [src:csound-plugins] src:csound-plugins: unsatisfied build 
dependency in testing: libgmm++-dev
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1023764: Bug 1023764

[Brian Haley]

This change has merged:

https://review.opendev.org/c/x/networking-l2gw/+/866620

If you want to try and build again.

Bug#1024783:

[Riccardo Pittau]

Hi,

this patch should fix the issue
https://review.opendev.org/c/openstack/ironic/+/866861

Thanks
Riccardo

Bug#1025621: marked as done (mercurial: FTBFS on 32-bit (test-revset.t: output changed))

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 13:50:57 +
with message-id 
and subject line Bug#1025621: fixed in mercurial 6.3.1-2
has caused the Debian Bug report #1025621,
regarding mercurial: FTBFS on 32-bit (test-revset.t: output changed)
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.)


-- 
1025621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mercurial
Version: 6.3.1-1
Severity: serious
Tags: upstream patch ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: jcris...@debian.org
Forwarded: https://bz.mercurial-scm.org/show_bug.cgi?id=6770

mercurial 6.3 fails its testsuite on 32-bit.  More info and proposed
patch in the bugzilla ticket.

Cheers,
Julien
--- End Message ---
--- Begin Message ---
Source: mercurial
Source-Version: 6.3.1-2
Done: Julien Cristau 

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated mercurial package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Dec 2022 13:59:55 +0100
Source: mercurial
Architecture: source
Version: 6.3.1-2
Distribution: sid
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julien Cristau 
Closes: 1025621
Changes:
 mercurial (6.3.1-2) sid; urgency=medium
 .
   * Fix FTBFS on 32-bit (closes: #1025621)
Checksums-Sha1:
 6b1495326783a7f4eb0ad203949b9da81d590f0a 2848 mercurial_6.3.1-2.dsc
 b5ac98e4f4ea0f18f53e25409bd27f1173a0a17b 70616 mercurial_6.3.1-2.debian.tar.xz
Checksums-Sha256:
 b50ccd69eedabc7eb2c88fdf185065628f68d95965ac36be708d1feb9755cdbd 2848 
mercurial_6.3.1-2.dsc
 75ec52a259c6c7bdc39ffdd1b0953684226a97aad9a1710dc25221f5b9f576ab 70616 
mercurial_6.3.1-2.debian.tar.xz
Files:
 990e7ee999af084e928a52b36ed212aa 2848 vcs optional mercurial_6.3.1-2.dsc
 c99e3cfdc7f9722cbf770937c4dc74c8 70616 vcs optional 
mercurial_6.3.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEVXgdqzTmGgnvuIvhnbAjVVb4z60FAmOQjpgUHGpjcmlzdGF1
QGRlYmlhbi5vcmcACgkQnbAjVVb4z607og//Tq9VM4LG/DzuVN7fSTc487rqcGYV
A+EgoXwSwJYLL2SpQLVs8+RzfCXIr4fN9M2z5RPGntPHi7Miumkeob89lXd7ifUE
FrcegYpnQeUaPxaxM4dQASfJ3OoVRw5uZm2DBcR6pWsOoR36oe6iONS8MZafO/91
LzuPEMnMmb9VRMa6bgbwH6ryQ4FGGcDD2Yeor8a38wht/zcji67C8XyAaQRMumnm
Y5fq2ErGpppdc+njnGb0Z2fS/MUZ1gDfPMXQo3l8Wccu03kAPIp751Iphke/IHCv
qwoAbVgy4QF0llixOX7WFHFyczUIEg1HKeqC2zO+v0YrVfH4baTRQ+hjBYJm5lOr
heb1eNFzynk7/ARAtufZxgfm+bgizhO+QznQY03riQaaKI/cN0EgtsijOQqgAulo
4rthhqUPDTBbfhnL13OFOVmsXBTn0y66lCTyxlBche0nALDN6Y3xd8K4cQ4m4VBG
SVUgOKuFcH/2+Jd/ZhV8TU27ogmbdcBYEpMJFEBT3+prtZY0MbSjxg1o37QQ5daI
qwthe4QkOjoYmpsQyafu+NRQG8/0l70dvIRJhZ1Q7F+2etnofbvh1xAkpVKVBofN
LwU9LAlb4BmcFkUmeVn12M9PzJm+Nf21i8nRA77OGj6U6rXCjf4HCP52UEAk2t8f
jUktvgTGht8+834=
=1c84
-END PGP SIGNATURE End Message ---

Bug#1024952:

[Riccardo Pittau]

Hi,

I'm looking into this issue and after a couple of tests I still can't
reproduce it.

I'm using python 3.11.0

This is the output of pip freeze

alembic==1.8.1
amqp==5.1.1
appdirs==1.4.4
async-timeout==4.0.2
attrs==22.1.0
automaton==3.0.1
autopage==0.5.1
bandit==1.7.4
bcrypt==4.0.0
cachetools==5.2.0
certifi==2022.9.24
cffi==1.15.1
charset-normalizer==2.1.1
click==8.1.3
cliff==4.0.0
cmd2==2.4.2
construct==2.10.68
coverage==6.4.4
cryptography==36.0.2
debtcollector==2.5.0
decorator==5.1.1
dnspython==2.2.1
dogpile.cache==1.1.8
eventlet==0.33.1
extras==1.0.0
fasteners==0.17.3
fixtures==4.0.1
Flask==2.2.2
future==0.18.2
futurist==2.4.1
gitdb==4.0.9
GitPython==3.1.27
greenlet==1.1.3
idna==3.3
ifaddr==0.2.0
importlib-metadata==4.12.0
-e git+
https://opendev.org/openstack/ironic-inspector.git@c2e4d64b605b5ca22c5135b2ba3d94f1da90f1a1#egg=ironic_inspector
ironic-lib==5.3.0
iso8601==1.0.2
itsdangerous==2.1.2
Jinja2==3.1.2
jmespath==1.0.1
jsonpatch==1.32
jsonpath-rw==1.4.0
jsonpointer==2.3
jsonschema==4.14.0
keystoneauth1==5.0.0
keystonemiddleware==10.1.0
kombu==5.2.4
Mako==1.2.2
MarkupSafe==2.1.1
msgpack==1.0.4
munch==2.5.0
netaddr==0.8.0
netifaces==0.11.0
openstacksdk==0.101.0
os-service-types==1.7.0
oslo.cache==3.2.0
oslo.concurrency==5.0.1
oslo.config==9.0.0
oslo.context==5.0.0
oslo.db==12.1.0
oslo.i18n==5.1.0
oslo.log==5.0.0
oslo.messaging==14.0.0
oslo.metrics==0.5.0
oslo.middleware==5.0.0
oslo.policy==4.0.0
oslo.rootwrap==6.3.1
oslo.serialization==5.0.0
oslo.service==3.0.0
oslo.upgradecheck==2.0.0
oslo.utils==6.0.1
oslotest==4.5.0
packaging==21.3
Paste==3.5.2
PasteDeploy==2.1.1
pbr==5.10.0
ply==3.11
prettytable==3.4.1
prometheus-client==0.14.1
pycadf==3.1.1
pycparser==2.21
pyinotify==0.9.6
pymemcache==3.5.2
pyparsing==3.0.9
pyperclip==1.8.2
pyrsistent==0.18.1
python-dateutil==2.8.2
python-keystoneclient==5.0.1
python-subunit==1.4.0
pytz==2022.2.1
PyYAML==6.0
repoze.lru==0.7
requests==2.28.1
requestsexceptions==1.4.0
rfc3986==1.5.0
Routes==2.5.1
six==1.16.0
smmap==5.0.0
SQLAlchemy==1.4.40
sqlalchemy-migrate==0.13.0
sqlparse==0.4.2
statsd==3.3.0
stestr==3.2.1
stevedore==4.0.2
Tempita==0.5.2
tenacity==6.3.1
testresources==2.0.1
testscenarios==0.5.0
testtools==2.5.0
tooz==3.1.0
urllib3==1.26.12
vine==5.0.0
voluptuous==0.13.1
wcwidth==0.2.5
WebOb==1.8.7
Werkzeug==2.2.2
wrapt==1.14.1
yappi==1.4.0
zeroconf==0.39.0
zipp==3.8.1

The tests are executed using tox in a clean virtual environment.

Thanks
Riccardo

Processed: severity 1024932 important

[Debian Bug Tracking System]

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

> severity 1024932 important
Bug #1024932 {Done: Thomas Goirand } [ceph-base] ceph-base: 
ceph to root privilege escalation via ceph-crash.service CVE-2022-3650
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Bug#1022018: marked as done (ganeti: Uses deprecated yaml.load)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 13:04:22 +
with message-id 
and subject line Bug#1023299: fixed in ganeti 3.0.2-2
has caused the Debian Bug report #1023299,
regarding ganeti: Uses deprecated yaml.load
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.)


-- 
1023299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ganeti
Version: 3.0.2-1
Severity: normal
X-Debbugs-Cc: gor...@chronitis.net

We hope to upgrade python3-yaml (aka pyyaml) to version 6 before the
freeze, per #1008262

Your package appears to use `yaml.load()` without specifying a `Loader=`
argument, which will become an error in pyyaml version 6. This should
have emitted a warning message since version 5.1 (from 2019).

In most cases this can be fixed by replacing `yaml.load` with
`yaml.safe_load`, unless the ability for yaml to create arbitrary python
objects is desirable.


This is used in the tests: test/py/ganeti.cli_unittest.py; this causes
autopkgtest failure against the version of pyyaml in experimental. I
don't think it breaks anything outside the test suite however.

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

Kernel: Linux 6.0.0-1-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 3.0.2-2
Done: Apollon Oikonomopoulos 

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

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

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated ganeti 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: Wed, 07 Dec 2022 12:31:59 +0200
Source: ganeti
Architecture: source
Version: 3.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Apollon Oikonomopoulos 
Closes: 1021753 1022018 1023299
Changes:
 ganeti (3.0.2-2) unstable; urgency=medium
 .
   * Fix compatibility with PyYAML 6.0 (Closes: #1023299, #1022018)
   * Drop the explicit libcurl4-openssl-dev dependency (Closes: #1021753)
   * Fix detection of C.UTF-8 (renamed to C.utf8 in glibc 2.34-1)
   * Relax deps to allow Haskell LTS-19 versions
   * Adapt to Template Haskell 2.17.0 changes (GHC 9)
   * Work around a build failure with GHC 9 / Lens 5 by letting the compiler
 infer the (correct) signatures of Ganeti.Network.poolLens,
 Ganeti.Network.poolArrayLens, Ganeti.Utils.MultiMap.multiMapL.
Checksums-Sha1:
 5bf76b783bd45c1c91c1d5473af48b23f05a35d7 3317 ganeti_3.0.2-2.dsc
 adbb72bfa4f71d1a1cc87569da8f93d27831a745 49228 ganeti_3.0.2-2.debian.tar.xz
 432374f54dd8fbcae9e288c0d18042de11d820d1 16575 ganeti_3.0.2-2_amd64.buildinfo
Checksums-Sha256:
 f2a3c911c7379ee1acd4f7faa5451380b34c15003461e4859fef4c61082c4723 3317 
ganeti_3.0.2-2.dsc
 9aa11b0151b63cb3943a7f864113009fe21d53a9c9583f7ce650105ba30e69d2 49228 
ganeti_3.0.2-2.debian.tar.xz
 3d043f6277b44936d6d151658dbd59680ed1b3afb55083ed7ed6ad5ef13cb3d6 16575 
ganeti_3.0.2-2_amd64.buildinfo
Files:
 067c90402ae9ea0ec6106a21918df19a 3317 admin optional ganeti_3.0.2-2.dsc
 4d68d675a36d7ed99aef6bd4c2f229c6 49228 admin optional 
ganeti_3.0.2-2.debian.tar.xz
 ce442b150a23cf9e4144dcfe3e2f2a97 16575 admin optional 
ganeti_3.0.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAmOQdoIACgkQ9RsYxyAk
giSC6hAArS0YBhAJ8+ombGDNBEmEvO0I1HYR+9i6ZLz/pj43p2xfmLfXdbMGuBSM
2H/qxJWAg99Ww+ffj5vmdsY5H11obUPah4XLvEr+19Baf2ymU85yVSg8IliVcrT2
0fvRyDfRuEupwgHDs+POiS7TBRiFYs0yIGiFVlQrJ1EYYQwnivkAwLfsZq4vPzE/
bM7HAAirHxUr51+yNmmqjjupDXnSwNwnexy6AnwXSUyG2SsUzV1ijHSgqenpY6dv
RUdlbSoYhs6pKr5Jj7jye1lHPCUTJWzwlFl19g7Kowu5IzpUJFKpqqJx+z5+pxUp
V7Ii81pKEYaFmxnmSV5ABWJIqyNAPt/M3yZntgjmrT22xJ3xf7IivDrWCHzqO1d8
pnFW4KX7YrePIQHS4y/3d5MkgXQkS3pLmoOulRnD0JoOU6Dxu+BXP66D2fY6XKLC

Bug#1023299: marked as done (ganeti-testsuite: yaml.load in testsuite needs to specify loader)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 13:04:22 +
with message-id 
and subject line Bug#1023299: fixed in ganeti 3.0.2-2
has caused the Debian Bug report #1023299,
regarding ganeti-testsuite: yaml.load in testsuite needs to specify loader
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.)


-- 
1023299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ganeti-testsuite
Version: 3.0.2-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
X-Debbugs-Cc: debian-pyt...@lists.debian.org

Previously yaml.load did not require a loader to be specified:

load(stream, Loader=None)

Now it does (starting in pyyaml 6.0):

load(stream, Loader)

Ganeti-testsuit uses yaml.load without specifying a loader, which now
causes a test failure in unstable.  Due to ganeti not being buildable
currently, it's not possible to fix this at the moment.

Note: Using FTBFS as a tag since that's the closest thing we have to a
test failure that would prevent migration.

Scott K
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 3.0.2-2
Done: Apollon Oikonomopoulos 

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

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

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated ganeti 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: Wed, 07 Dec 2022 12:31:59 +0200
Source: ganeti
Architecture: source
Version: 3.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Apollon Oikonomopoulos 
Closes: 1021753 1022018 1023299
Changes:
 ganeti (3.0.2-2) unstable; urgency=medium
 .
   * Fix compatibility with PyYAML 6.0 (Closes: #1023299, #1022018)
   * Drop the explicit libcurl4-openssl-dev dependency (Closes: #1021753)
   * Fix detection of C.UTF-8 (renamed to C.utf8 in glibc 2.34-1)
   * Relax deps to allow Haskell LTS-19 versions
   * Adapt to Template Haskell 2.17.0 changes (GHC 9)
   * Work around a build failure with GHC 9 / Lens 5 by letting the compiler
 infer the (correct) signatures of Ganeti.Network.poolLens,
 Ganeti.Network.poolArrayLens, Ganeti.Utils.MultiMap.multiMapL.
Checksums-Sha1:
 5bf76b783bd45c1c91c1d5473af48b23f05a35d7 3317 ganeti_3.0.2-2.dsc
 adbb72bfa4f71d1a1cc87569da8f93d27831a745 49228 ganeti_3.0.2-2.debian.tar.xz
 432374f54dd8fbcae9e288c0d18042de11d820d1 16575 ganeti_3.0.2-2_amd64.buildinfo
Checksums-Sha256:
 f2a3c911c7379ee1acd4f7faa5451380b34c15003461e4859fef4c61082c4723 3317 
ganeti_3.0.2-2.dsc
 9aa11b0151b63cb3943a7f864113009fe21d53a9c9583f7ce650105ba30e69d2 49228 
ganeti_3.0.2-2.debian.tar.xz
 3d043f6277b44936d6d151658dbd59680ed1b3afb55083ed7ed6ad5ef13cb3d6 16575 
ganeti_3.0.2-2_amd64.buildinfo
Files:
 067c90402ae9ea0ec6106a21918df19a 3317 admin optional ganeti_3.0.2-2.dsc
 4d68d675a36d7ed99aef6bd4c2f229c6 49228 admin optional 
ganeti_3.0.2-2.debian.tar.xz
 ce442b150a23cf9e4144dcfe3e2f2a97 16575 admin optional 
ganeti_3.0.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAmOQdoIACgkQ9RsYxyAk
giSC6hAArS0YBhAJ8+ombGDNBEmEvO0I1HYR+9i6ZLz/pj43p2xfmLfXdbMGuBSM
2H/qxJWAg99Ww+ffj5vmdsY5H11obUPah4XLvEr+19Baf2ymU85yVSg8IliVcrT2
0fvRyDfRuEupwgHDs+POiS7TBRiFYs0yIGiFVlQrJ1EYYQwnivkAwLfsZq4vPzE/
bM7HAAirHxUr51+yNmmqjjupDXnSwNwnexy6AnwXSUyG2SsUzV1ijHSgqenpY6dv
RUdlbSoYhs6pKr5Jj7jye1lHPCUTJWzwlFl19g7Kowu5IzpUJFKpqqJx+z5+pxUp
V7Ii81pKEYaFmxnmSV5ABWJIqyNAPt/M3yZntgjmrT22xJ3xf7IivDrWCHzqO1d8
pnFW4KX7YrePIQHS4y/3d5MkgXQkS3pLmoOulRnD0JoOU6Dxu+BXP66D2fY6XKLC
4EGsrJzq5Kp+CIAIHwKXs5T1HLp+zdRKx6PlpiacHf3ew1+TBGn05iKs1YofS2Km
HSKxFVtr8Wj2t3lD4VaX9V36Eqd8svUyHcJDATLjvdUU7HBCt0qw1zd+73CKDDAB
a/bZUrsFSfh/Uga9kIm743nqXPVf50mYmKlMWVWA7PmnVk7EsGvtLyeBjxUuM4PU
Psv4pKBEmPWitw96K865UtvgP1CzIovv6MczIEajZSzNveBduGc=
=6LLP
-END PGP SIGNATURE End Message ---

Bug#1023299: marked as done (ganeti-testsuite: yaml.load in testsuite needs to specify loader)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 13:04:22 +
with message-id 
and subject line Bug#1022018: fixed in ganeti 3.0.2-2
has caused the Debian Bug report #1022018,
regarding ganeti-testsuite: yaml.load in testsuite needs to specify loader
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.)


-- 
1022018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ganeti-testsuite
Version: 3.0.2-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
X-Debbugs-Cc: debian-pyt...@lists.debian.org

Previously yaml.load did not require a loader to be specified:

load(stream, Loader=None)

Now it does (starting in pyyaml 6.0):

load(stream, Loader)

Ganeti-testsuit uses yaml.load without specifying a loader, which now
causes a test failure in unstable.  Due to ganeti not being buildable
currently, it's not possible to fix this at the moment.

Note: Using FTBFS as a tag since that's the closest thing we have to a
test failure that would prevent migration.

Scott K
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 3.0.2-2
Done: Apollon Oikonomopoulos 

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

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

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated ganeti 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: Wed, 07 Dec 2022 12:31:59 +0200
Source: ganeti
Architecture: source
Version: 3.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Apollon Oikonomopoulos 
Closes: 1021753 1022018 1023299
Changes:
 ganeti (3.0.2-2) unstable; urgency=medium
 .
   * Fix compatibility with PyYAML 6.0 (Closes: #1023299, #1022018)
   * Drop the explicit libcurl4-openssl-dev dependency (Closes: #1021753)
   * Fix detection of C.UTF-8 (renamed to C.utf8 in glibc 2.34-1)
   * Relax deps to allow Haskell LTS-19 versions
   * Adapt to Template Haskell 2.17.0 changes (GHC 9)
   * Work around a build failure with GHC 9 / Lens 5 by letting the compiler
 infer the (correct) signatures of Ganeti.Network.poolLens,
 Ganeti.Network.poolArrayLens, Ganeti.Utils.MultiMap.multiMapL.
Checksums-Sha1:
 5bf76b783bd45c1c91c1d5473af48b23f05a35d7 3317 ganeti_3.0.2-2.dsc
 adbb72bfa4f71d1a1cc87569da8f93d27831a745 49228 ganeti_3.0.2-2.debian.tar.xz
 432374f54dd8fbcae9e288c0d18042de11d820d1 16575 ganeti_3.0.2-2_amd64.buildinfo
Checksums-Sha256:
 f2a3c911c7379ee1acd4f7faa5451380b34c15003461e4859fef4c61082c4723 3317 
ganeti_3.0.2-2.dsc
 9aa11b0151b63cb3943a7f864113009fe21d53a9c9583f7ce650105ba30e69d2 49228 
ganeti_3.0.2-2.debian.tar.xz
 3d043f6277b44936d6d151658dbd59680ed1b3afb55083ed7ed6ad5ef13cb3d6 16575 
ganeti_3.0.2-2_amd64.buildinfo
Files:
 067c90402ae9ea0ec6106a21918df19a 3317 admin optional ganeti_3.0.2-2.dsc
 4d68d675a36d7ed99aef6bd4c2f229c6 49228 admin optional 
ganeti_3.0.2-2.debian.tar.xz
 ce442b150a23cf9e4144dcfe3e2f2a97 16575 admin optional 
ganeti_3.0.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAmOQdoIACgkQ9RsYxyAk
giSC6hAArS0YBhAJ8+ombGDNBEmEvO0I1HYR+9i6ZLz/pj43p2xfmLfXdbMGuBSM
2H/qxJWAg99Ww+ffj5vmdsY5H11obUPah4XLvEr+19Baf2ymU85yVSg8IliVcrT2
0fvRyDfRuEupwgHDs+POiS7TBRiFYs0yIGiFVlQrJ1EYYQwnivkAwLfsZq4vPzE/
bM7HAAirHxUr51+yNmmqjjupDXnSwNwnexy6AnwXSUyG2SsUzV1ijHSgqenpY6dv
RUdlbSoYhs6pKr5Jj7jye1lHPCUTJWzwlFl19g7Kowu5IzpUJFKpqqJx+z5+pxUp
V7Ii81pKEYaFmxnmSV5ABWJIqyNAPt/M3yZntgjmrT22xJ3xf7IivDrWCHzqO1d8
pnFW4KX7YrePIQHS4y/3d5MkgXQkS3pLmoOulRnD0JoOU6Dxu+BXP66D2fY6XKLC
4EGsrJzq5Kp+CIAIHwKXs5T1HLp+zdRKx6PlpiacHf3ew1+TBGn05iKs1YofS2Km
HSKxFVtr8Wj2t3lD4VaX9V36Eqd8svUyHcJDATLjvdUU7HBCt0qw1zd+73CKDDAB
a/bZUrsFSfh/Uga9kIm743nqXPVf50mYmKlMWVWA7PmnVk7EsGvtLyeBjxUuM4PU
Psv4pKBEmPWitw96K865UtvgP1CzIovv6MczIEajZSzNveBduGc=
=6LLP
-END PGP SIGNATURE End Message ---

Bug#1022018: marked as done (ganeti: Uses deprecated yaml.load)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 13:04:22 +
with message-id 
and subject line Bug#1022018: fixed in ganeti 3.0.2-2
has caused the Debian Bug report #1022018,
regarding ganeti: Uses deprecated yaml.load
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.)


-- 
1022018: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022018
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ganeti
Version: 3.0.2-1
Severity: normal
X-Debbugs-Cc: gor...@chronitis.net

We hope to upgrade python3-yaml (aka pyyaml) to version 6 before the
freeze, per #1008262

Your package appears to use `yaml.load()` without specifying a `Loader=`
argument, which will become an error in pyyaml version 6. This should
have emitted a warning message since version 5.1 (from 2019).

In most cases this can be fixed by replacing `yaml.load` with
`yaml.safe_load`, unless the ability for yaml to create arbitrary python
objects is desirable.


This is used in the tests: test/py/ganeti.cli_unittest.py; this causes
autopkgtest failure against the version of pyyaml in experimental. I
don't think it breaks anything outside the test suite however.

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

Kernel: Linux 6.0.0-1-amd64 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 3.0.2-2
Done: Apollon Oikonomopoulos 

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

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

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated ganeti 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: Wed, 07 Dec 2022 12:31:59 +0200
Source: ganeti
Architecture: source
Version: 3.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Apollon Oikonomopoulos 
Closes: 1021753 1022018 1023299
Changes:
 ganeti (3.0.2-2) unstable; urgency=medium
 .
   * Fix compatibility with PyYAML 6.0 (Closes: #1023299, #1022018)
   * Drop the explicit libcurl4-openssl-dev dependency (Closes: #1021753)
   * Fix detection of C.UTF-8 (renamed to C.utf8 in glibc 2.34-1)
   * Relax deps to allow Haskell LTS-19 versions
   * Adapt to Template Haskell 2.17.0 changes (GHC 9)
   * Work around a build failure with GHC 9 / Lens 5 by letting the compiler
 infer the (correct) signatures of Ganeti.Network.poolLens,
 Ganeti.Network.poolArrayLens, Ganeti.Utils.MultiMap.multiMapL.
Checksums-Sha1:
 5bf76b783bd45c1c91c1d5473af48b23f05a35d7 3317 ganeti_3.0.2-2.dsc
 adbb72bfa4f71d1a1cc87569da8f93d27831a745 49228 ganeti_3.0.2-2.debian.tar.xz
 432374f54dd8fbcae9e288c0d18042de11d820d1 16575 ganeti_3.0.2-2_amd64.buildinfo
Checksums-Sha256:
 f2a3c911c7379ee1acd4f7faa5451380b34c15003461e4859fef4c61082c4723 3317 
ganeti_3.0.2-2.dsc
 9aa11b0151b63cb3943a7f864113009fe21d53a9c9583f7ce650105ba30e69d2 49228 
ganeti_3.0.2-2.debian.tar.xz
 3d043f6277b44936d6d151658dbd59680ed1b3afb55083ed7ed6ad5ef13cb3d6 16575 
ganeti_3.0.2-2_amd64.buildinfo
Files:
 067c90402ae9ea0ec6106a21918df19a 3317 admin optional ganeti_3.0.2-2.dsc
 4d68d675a36d7ed99aef6bd4c2f229c6 49228 admin optional 
ganeti_3.0.2-2.debian.tar.xz
 ce442b150a23cf9e4144dcfe3e2f2a97 16575 admin optional 
ganeti_3.0.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAmOQdoIACgkQ9RsYxyAk
giSC6hAArS0YBhAJ8+ombGDNBEmEvO0I1HYR+9i6ZLz/pj43p2xfmLfXdbMGuBSM
2H/qxJWAg99Ww+ffj5vmdsY5H11obUPah4XLvEr+19Baf2ymU85yVSg8IliVcrT2
0fvRyDfRuEupwgHDs+POiS7TBRiFYs0yIGiFVlQrJ1EYYQwnivkAwLfsZq4vPzE/
bM7HAAirHxUr51+yNmmqjjupDXnSwNwnexy6AnwXSUyG2SsUzV1ijHSgqenpY6dv
RUdlbSoYhs6pKr5Jj7jye1lHPCUTJWzwlFl19g7Kowu5IzpUJFKpqqJx+z5+pxUp
V7Ii81pKEYaFmxnmSV5ABWJIqyNAPt/M3yZntgjmrT22xJ3xf7IivDrWCHzqO1d8
pnFW4KX7YrePIQHS4y/3d5MkgXQkS3pLmoOulRnD0JoOU6Dxu+BXP66D2fY6XKLC

Bug#1021753: marked as done (ganeti: conflicting curl build-depends)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 13:04:22 +
with message-id 
and subject line Bug#1021753: fixed in ganeti 3.0.2-2
has caused the Debian Bug report #1021753,
regarding ganeti: conflicting curl build-depends
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.)


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

Package: ganeti
Version: 3.0.2-1
Tags: bookworm, sid

ganeti build-depends on both libcurl4-openssl-dev and libghc-curl-dev,
the current version of libghc-curl-dev build-depends on libcurl4-gnutls-dev
and libcurl4-gnutls-dev conflicts with libcurl4-openssl-dev.

Therefore your packages build-dependencies are unsatisfiable.
--- End Message ---
--- Begin Message ---
Source: ganeti
Source-Version: 3.0.2-2
Done: Apollon Oikonomopoulos 

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

Debian distribution maintenance software
pp.
Apollon Oikonomopoulos  (supplier of updated ganeti 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: Wed, 07 Dec 2022 12:31:59 +0200
Source: ganeti
Architecture: source
Version: 3.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ganeti Team 
Changed-By: Apollon Oikonomopoulos 
Closes: 1021753 1022018 1023299
Changes:
 ganeti (3.0.2-2) unstable; urgency=medium
 .
   * Fix compatibility with PyYAML 6.0 (Closes: #1023299, #1022018)
   * Drop the explicit libcurl4-openssl-dev dependency (Closes: #1021753)
   * Fix detection of C.UTF-8 (renamed to C.utf8 in glibc 2.34-1)
   * Relax deps to allow Haskell LTS-19 versions
   * Adapt to Template Haskell 2.17.0 changes (GHC 9)
   * Work around a build failure with GHC 9 / Lens 5 by letting the compiler
 infer the (correct) signatures of Ganeti.Network.poolLens,
 Ganeti.Network.poolArrayLens, Ganeti.Utils.MultiMap.multiMapL.
Checksums-Sha1:
 5bf76b783bd45c1c91c1d5473af48b23f05a35d7 3317 ganeti_3.0.2-2.dsc
 adbb72bfa4f71d1a1cc87569da8f93d27831a745 49228 ganeti_3.0.2-2.debian.tar.xz
 432374f54dd8fbcae9e288c0d18042de11d820d1 16575 ganeti_3.0.2-2_amd64.buildinfo
Checksums-Sha256:
 f2a3c911c7379ee1acd4f7faa5451380b34c15003461e4859fef4c61082c4723 3317 
ganeti_3.0.2-2.dsc
 9aa11b0151b63cb3943a7f864113009fe21d53a9c9583f7ce650105ba30e69d2 49228 
ganeti_3.0.2-2.debian.tar.xz
 3d043f6277b44936d6d151658dbd59680ed1b3afb55083ed7ed6ad5ef13cb3d6 16575 
ganeti_3.0.2-2_amd64.buildinfo
Files:
 067c90402ae9ea0ec6106a21918df19a 3317 admin optional ganeti_3.0.2-2.dsc
 4d68d675a36d7ed99aef6bd4c2f229c6 49228 admin optional 
ganeti_3.0.2-2.debian.tar.xz
 ce442b150a23cf9e4144dcfe3e2f2a97 16575 admin optional 
ganeti_3.0.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEPgL9ZlYpWVIRC6uZ9RsYxyAkgiQFAmOQdoIACgkQ9RsYxyAk
giSC6hAArS0YBhAJ8+ombGDNBEmEvO0I1HYR+9i6ZLz/pj43p2xfmLfXdbMGuBSM
2H/qxJWAg99Ww+ffj5vmdsY5H11obUPah4XLvEr+19Baf2ymU85yVSg8IliVcrT2
0fvRyDfRuEupwgHDs+POiS7TBRiFYs0yIGiFVlQrJ1EYYQwnivkAwLfsZq4vPzE/
bM7HAAirHxUr51+yNmmqjjupDXnSwNwnexy6AnwXSUyG2SsUzV1ijHSgqenpY6dv
RUdlbSoYhs6pKr5Jj7jye1lHPCUTJWzwlFl19g7Kowu5IzpUJFKpqqJx+z5+pxUp
V7Ii81pKEYaFmxnmSV5ABWJIqyNAPt/M3yZntgjmrT22xJ3xf7IivDrWCHzqO1d8
pnFW4KX7YrePIQHS4y/3d5MkgXQkS3pLmoOulRnD0JoOU6Dxu+BXP66D2fY6XKLC
4EGsrJzq5Kp+CIAIHwKXs5T1HLp+zdRKx6PlpiacHf3ew1+TBGn05iKs1YofS2Km
HSKxFVtr8Wj2t3lD4VaX9V36Eqd8svUyHcJDATLjvdUU7HBCt0qw1zd+73CKDDAB
a/bZUrsFSfh/Uga9kIm743nqXPVf50mYmKlMWVWA7PmnVk7EsGvtLyeBjxUuM4PU
Psv4pKBEmPWitw96K865UtvgP1CzIovv6MczIEajZSzNveBduGc=
=6LLP
-END PGP SIGNATURE End Message ---

Bug#1019677: marked as done (ruby-webpacker: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 12:50:15 +
with message-id 
and subject line Bug#1019677: fixed in ruby-webpacker 5.4.3-2
has caused the Debian Bug report #1019677,
regarding ruby-webpacker: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
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.)


-- 
1019677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-webpacker
Version: 5.4.3-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-webpacker with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-webpacker/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"webpacker\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-webpacker/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> mv Gemfile.lock ./.gem2deb.Gemfile.lock
> /usr/bin/ruby3.1 -w -I"test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "test/command_test.rb" "test/compiler_test.rb" "test/configuration_test.rb" 
> "test/dev_server_test.rb" "test/env_test.rb" "test/helper_test.rb" 
> "test/manifest_test.rb" "test/rake_tasks_test.rb" "test/webpacker_test.rb" -v
> /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/nokogiri-1.13.7/lib/nokogiri/version/info.rb:85:
>  warning: possibly useless use of a variable in void context
> /usr/share/rubygems-integration/all/gems/activesupport-6.1.6.1/lib/active_support/core_ext/class/subclasses.rb:30:
>  warning: method redefined; discarding old subclasses
> The resolved_paths option has been deprecated. Use additional_paths instead.
> The resolved_paths option has been deprecated. Use additional_paths instead.
> The resolved_paths option has been deprecated. Use additional_paths instead.
> Run options: -v --seed 30762
> 
> # Running:
> 
> DevServerTest#test_host = 0.00 s = .
> DevServerTest#test_protocol = 0.00 s = .
> DevServerTest#test_pretty? = 0.00 s = .
> DevServerTest#test_running? = 0.00 s = .
> DevServerTest#test_host_with_port = 0.00 s = .
> DevServerTest#test_port = 0.00 s = .
> DevServerTest#test_default_env_prefix = 0.00 s = .
> DevServerTest#test_https? = 0.00 s = .
> CompilerTest#test_compilation_digest_path = 0.00 s = .
> CompilerTest#test_custom_environment_variables = 0.00 s = .
> CompilerTest#test_freshness = 0.00 s = .
> The resolved_paths option has been deprecated. Use additional_paths instead.
> CompilerTest#test_compile = 0.10 s = .
> CompilerTest#test_external_env_variables = 0.00 s = .
> The resolved_paths option has been deprecated. Use additional_paths instead.
> The resolved_paths option has been deprecated. Use additional_paths instead.
> The resolved_paths option has been deprecated. Use additional_paths instead.
> The resolved_paths option has been deprecated. Use additional_paths instead.
> CompilerTest#test_freshness_on_compile_success = 0.00 s = .
> The resolved_paths option has been deprecated. Use additional_paths instead.
> CompilerTest#test_default_watched_paths = 0.00 s = .
> The resolved_paths option has been deprecated. Use additional_paths instead.
> The resolved_paths option has been deprecated. Use additional_paths instead.
> The 

Bug#1025659:

[Martin]

I am also affected by this bug on a 2020 Lenovo laptop, same as OP
reported. After an upgrade on my unstable debian system it booted only
to a blinking cursor. Going into a terminal and checking logs I also
saw the segmentation fault.

It made my laptop unusable as of now. :( Hope that the driver can be
brought back or the hardware supported otherwise.
This was also reported in #1025389

I'm happy to support you with information as much as I can.

Xorg.0.log  https://paste.debian.net/1263176/
Hardware info  https://paste.debian.net/1263178/

Bug#1025686: Plugin cannot be loaded, not linked against hdf5

[Enrico Zini]

Package: hdf5-filter-plugin
Version: 0.0~git2022.49e3b65-2
Severity: serious
Tags: patch

Hello,

hdf5 cannot load the plugin dynamically:

   >>> import h5py
   >>> h5py.h5z.filter_avail(32004)
   False

This is because the library cannot be loaded due to missing HDF5 symbols:

   $ python3
   Python 3.10.8 (main, Nov  4 2022, 09:21:25) [GCC 12.2.0] on linux
   Type "help", "copyright", "credits" or "license" for more information.
   >>> import ctypes
   >>> lib = 
ctypes.CDLL("/usr/lib/x86_64-linux-gnu/hdf5/serial/plugins/libh5lz4.so")
   Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python3.10/ctypes/__init__.py", line 374, in __init__
   self._handle = _dlopen(self._name, mode)
   OSError: /usr/lib/x86_64-linux-gnu/hdf5/serial/plugins/libh5lz4.so: 
undefined symbol: H5E_PLINE_g

I filed a PR upstream that fixes the problem:
https://github.com/nexusformat/HDF5-External-Filter-Plugins/pull/27

I'm attaching the corresponding patch.


Thanks,

Enrico


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

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

Versions of packages hdf5-filter-plugin depends on:
ii  libbz2-1.0 1.0.8-5+b1
ii  libc6  2.36-6
ii  libhdf5-103-1  1.10.8+repack-4
ii  liblz4-1   1.9.4-1

hdf5-filter-plugin recommends no packages.

hdf5-filter-plugin suggests no packages.
commit 3d93e1821dd10962f4477d8b3615024cf10f4cc6
Author: Enrico Zini 
Date:   Wed Dec 7 12:19:17 2022 +0100

Added missing libraries

diff --git a/LZ4/src/CMakeLists.txt b/LZ4/src/CMakeLists.txt
index b5bf34b..1823eff 100644
--- a/LZ4/src/CMakeLists.txt
+++ b/LZ4/src/CMakeLists.txt
@@ -1,7 +1,7 @@
 set(SOURCES H5Zlz4.c lz4_h5plugin.c)
 
 set(INCLUDE_DIRS ${HDF5_INCLUDE_DIRS} ${LZ4_INCLUDE_DIRS})
-set(LINK_LIBS ${LZ4_LIBRARIES})
+set(LINK_LIBS ${LZ4_LIBRARIES} ${HDF5_LIBRARIES})
 
 if(CMAKE_SYSTEM_NAME MATCHES Windows)
 #

Processed: pyfai: autopkgtest regression on armel and i386

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1018811 [src:pyfai] pyfai: autopkgtest regression on armel and i386
Severity set to 'serious' from 'important'

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

Bug#1025124:

[Riccardo Pittau]

hi,

this patch should fix the issue
https://review.opendev.org/c/openstack/sushy/+/866782

thanks
Riccardo

Bug#1025678: marked as done (coreboot-utils-doc: Uninstallable in sid because of ${sphinxdoc:Built-Using} dependency)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 11:05:33 +
with message-id 
and subject line Bug#1025678: fixed in coreboot 4.15~dfsg-3
has caused the Debian Bug report #1025678,
regarding coreboot-utils-doc: Uninstallable in sid because of 
${sphinxdoc:Built-Using} dependency
to be marked as done.

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

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


-- 
1025678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: coreboot-utils-doc
Version: 4.15~dfsg-2
Severity: serious

Dear Maintainer,

In a clean sid chroot, coreboot-utils-doc is not installable:

  # apt install coreboot-utils-doc
  Reading package lists... Done
  Building dependency tree... Done
  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:
   coreboot-utils-doc : Depends: sphinx (= 4.5.0-4)
  E: Unable to correct problems, you have held broken packages.

This is because that package has ${sphinxdoc:Built-Using} among its
dependencies.

That substitution variable is intended to be used in Built-Using field of
architecture-dependent packages, NOT in Depends field. For "Architecture: all"
packages it is not needed at all. Please remove it.

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: coreboot
Source-Version: 4.15~dfsg-3
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated coreboot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Dec 2022 11:42:50 +0100
Source: coreboot
Architecture: source
Version: 4.15~dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Bastian Germann 
Changed-By: Bastian Germann 
Closes: 1025678
Changes:
 coreboot (4.15~dfsg-3) unstable; urgency=medium
 .
   * Get rid of Built-Using in Depends (Closes: #1025678)
Checksums-Sha1:
 5006f25ce08099fae6cf1081893b9db97107120b 2030 coreboot_4.15~dfsg-3.dsc
 a19d789ab535669921e5e27f0b59aad84d8bcf8e 29492 
coreboot_4.15~dfsg-3.debian.tar.xz
 166daa67beeed5d64f6e74be9eb3aa57bd09714f 7579 
coreboot_4.15~dfsg-3_source.buildinfo
Checksums-Sha256:
 63b135f58b231665139ec80a9b2f1569a9b5313c4c2a51c0991a73a67d2750b4 2030 
coreboot_4.15~dfsg-3.dsc
 1a71208c2d824d5aace156bf9033bf747003425675ba105008318f67f46fc262 29492 
coreboot_4.15~dfsg-3.debian.tar.xz
 80941a465dcae4cb9e2459701ebfad500c9f52b901b8b998ab5eb8a66beb 7579 
coreboot_4.15~dfsg-3_source.buildinfo
Files:
 197f8b661717df01f162bec649c48200 2030 utils optional coreboot_4.15~dfsg-3.dsc
 ad339727bb183cf3e0437506911f2dd3 29492 utils optional 
coreboot_4.15~dfsg-3.debian.tar.xz
 f43ac2c3c99a206577933f786b26c90b 7579 utils optional 
coreboot_4.15~dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmOQcDIQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFNNZDACQKHMRv0jP5maLBqXr2zIaU9fjqcpUxMWg
vs5ElVwVev92Tl3jZINoeh68lAp009CmAauGJ3catQWIQE42t004km5zMbIy5xJo
aRQD5LRl5/q/X2jt4TK2NDIx+wio0CA21KixqqPGtRwT6GI2OdJ9x0nsvtXTq0T7
m8Ji/hG8xjxTRSpf3Tt6kr/SvgNzYCA/SbXPeYHqqpchWc/TYPrekqWquiTbklF6
euYUhCDDbJsllCNBoF0Fq2vhRmQ62KhtQH+Nz5a/Z6wVnH6YOF2gdawu8WW3NUPW
UGjxuEhgbglZnTAcBcnbB88zu1eA5+mlZk5f9kMpeTP1ZXhn3RFpKKssK9nvsAJg
JVWOfnnoR0nkOzgNzoms479d6bAK2j1x4YbdWcuJ2D6bwQsmr+soCqIdjShuOzjD
ljzEkxUzfV6bXuIfe7WxbXsQ0EJcn2DZWwuZ/Xvvq91R/LFPsGIMMISxNsC/sgSB
tfw1eECYxcHYUYva3vjxmm1UFaEMm3g=
=/sOd
-END PGP SIGNATURE End Message ---

Processed: Re: Processed: Re: Bug#1024327: gv hangs on any file

[Debian Bug Tracking System]

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

> tags 1023330 - experimental
Bug #1023330 {Done: Sebastian Ramacher } [ghostscript] 
ghostscript 10.0.0~dfsg-6: x11 support missing, thus 'gv 1:3.7.4-2+b1' is 
failing
Bug #1024318 {Done: Sebastian Ramacher } [ghostscript] 
gv: x11 output driver not found
Bug #1024327 {Done: Sebastian Ramacher } [ghostscript] gv 
hangs on any file
Removed tag(s) experimental.
Removed tag(s) experimental.
Removed tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#1025678: coreboot-utils-doc: Uninstallable in sid because of ${sphinxdoc:Built-Using} dependency

[Dmitry Shachnev]

Package: coreboot-utils-doc
Version: 4.15~dfsg-2
Severity: serious

Dear Maintainer,

In a clean sid chroot, coreboot-utils-doc is not installable:

  # apt install coreboot-utils-doc
  Reading package lists... Done
  Building dependency tree... Done
  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:
   coreboot-utils-doc : Depends: sphinx (= 4.5.0-4)
  E: Unable to correct problems, you have held broken packages.

This is because that package has ${sphinxdoc:Built-Using} among its
dependencies.

That substitution variable is intended to be used in Built-Using field of
architecture-dependent packages, NOT in Depends field. For "Architecture: all"
packages it is not needed at all. Please remove it.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1025659: libgl1-mesa-dri: mesa causes xorg segfault; regression against 22.2.0-1

[Bernhard Übelacker]

After updating mesa from 22.2.0-1 to 22.3.0-2 (according to dpkg.log)
earlier today U.S. time as part of a routine upgrade to up-to-date sid,
the greeter stopped appearing, and over the course of the last two hours
we chased it down to that upgrade, which made X.org die with
  iris_dri.so (nouveau_drm_screen_create+[three addresses])
  iris_dri.so (?+0x0)
  iris_dri.so (__driDriverGetExtensions_d3d12+[three addresses])
in the backtrace of a segfault at 0x20.

This may be tangentially related to other d3d12 fuckups in 22.3.0,
like #1025312, given the timeline and d3d12ness.



00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 
[8086:591b] (rev 04)



Dear Maintainer,
I tried to reconstruct a better backtrace with the
help of the dbgsym packages.

What I find strange is the system has a Intel GPU, but
is calling in some nouveau functions?

Kind regards,
Bernhard


...ebc in nouveau_pushbuf_destroy at 
../src/gallium/drivers/nouveau/nouveau_screen.c:244  
(nouveau_drm_screen_create+0x4406c)
...319 in nvc0_screen_destroy at 
../src/gallium/drivers/nouveau/nvc0/nvc0_screen.c:740
(nouveau_drm_screen_create+0x1e4c9)
...0b6 in nouveau_drm_screen_create at 
../src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c:133 
(nouveau_drm_screen_create+0x266)
...df6 in pipe_nouveau_create_screen at 
../src/gallium/auxiliary/target-helpers/drm_helper.h:144  (0x7f205d0a9df6)
...0c4 in pipe_loader_create_screen_vk at 
../src/gallium/auxiliary/pipe-loader/pipe_loader.c:175  
(__driDriverGetExtensions_d3d12+0x60ad84)
...dd3 in dri2_init_screen at ../src/gallium/frontends/dri/dri2.c:2265  
  (__driDriverGetExtensions_d3d12+0x1a93)
...4b5 in driCreateNewScreen2 at ../src/gallium/frontends/dri/dri_util.c:143
  (__driDriverGetExtensions_d3d12+0xa175)
...eae in dri_screen_create_dri2 at ../src/gbm/backends/dri/gbm_dri.c:434   
  (gbm_format_get_name+0xf2e)
...678 in dri_screen_create at ../src/gbm/backends/dri/gbm_dri.c:511
  (gbm_format_get_name+0x16f8)
...74c in backend_create_device at ../src/gbm/main/backend.c:101
  (0x7f205edc274c)
...884 in gbm_create_device at ../src/gbm/main/gbm.c:138
  (gbm_create_device+0x44)
...3c1 in glamor_egl_init at ../../../../../../glamor/glamor_egl.c:947  
  (glamor_egl_init+0x61)
...733 in try_enable_glamor at 
../../../../../../../hw/xfree86/drivers/modesetting/driver.c:945   
(0x7f205f118733)
...56a in InitOutput at ../../../../../../hw/xfree86/common/xf86Init.c:490  
  (InitOutput+0xa2a)
...


The crashing instruction:  (the 0x20 offset matches, maybe NULL given to 
nouveau_pushbuf_destroy?)

   0x75f56ebc : mov0x20(%rax),%rdi


https://sources.debian.org/src/mesa/22.3.0-2/src/gallium/drivers/nouveau/nouveau_screen.c/#L244
241 void
242 nouveau_pushbuf_destroy(struct nouveau_pushbuf **push)
243 {
244FREE((*push)->user_priv);
245nouveau_pushbuf_del(push);
246 }

Processed: Re: Bug#1024327: gv hangs on any file

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ghostscript
Bug #1024327 [gv] gv hangs on any file
Bug reassigned from package 'gv' to 'ghostscript'.
No longer marked as found in versions gv/1:3.7.4-2.
Ignoring request to alter fixed versions of bug #1024327 to the same values 
previously set
> forcemerge 1023330 -1
Bug #1023330 {Done: Sebastian Ramacher } [ghostscript] 
ghostscript 10.0.0~dfsg-6: x11 support missing, thus 'gv 1:3.7.4-2+b1' is 
failing
Bug #1024318 {Done: Sebastian Ramacher } [ghostscript] 
gv: x11 output driver not found
Bug #1024318 {Done: Sebastian Ramacher } [ghostscript] 
gv: x11 output driver not found
Added tag(s) experimental.
Added tag(s) experimental.
Bug #1024327 [ghostscript] gv hangs on any file
Marked Bug as done
Marked as fixed in versions ghostscript/10.0.0~dfsg-8.
Marked as found in versions ghostscript/10.0.0~dfsg-6.
Merged 1023330 1024318 1024327
> affects -1 gv
Bug #1024327 {Done: Sebastian Ramacher } [ghostscript] gv 
hangs on any file
Bug #1023330 {Done: Sebastian Ramacher } [ghostscript] 
ghostscript 10.0.0~dfsg-6: x11 support missing, thus 'gv 1:3.7.4-2+b1' is 
failing
Bug #1024318 {Done: Sebastian Ramacher } [ghostscript] 
gv: x11 output driver not found
Added indication that 1024327 affects gv
Added indication that 1023330 affects gv
Added indication that 1024318 affects gv

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

Bug#1024327: gv hangs on any file

[Vincent Lefevre]

Control: reassign -1 ghostscript
Control: forcemerge 1023330 -1
Control: affects -1 gv

On 2022-12-07 09:35:19 +0100, jerjer...@online.de wrote:
> Could be the same as
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023330
> 
> which is fixed in testing now.

Thanks for the information. Indeed, the upgrade to ghostscript from
10.0.0~dfsg-7 to 10.0.0~dfsg-8 fixed the issue.

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

Bug#1024327: gv hangs on any file

[jerjer194]

Could be the same as

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023330

which is fixed in testing now.

Bug#1025017: marked as done (pymca: (autopkgtest) needs update for python3.11: 'TestPlotWidget' object has no attribute '_feedErrorsToResult')

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 09:38:54 +0100
with message-id <5807a8e3382bc6a8bbdedabfc0716...@debian.org>
and subject line pymca: (autopkgtest) needs update for python3.11: 
'TestPlotWidget'  object has no attribute '_feedErrorsToResult'
has caused the Debian Bug report #1025017,
regarding pymca: (autopkgtest) needs update for python3.11: 'TestPlotWidget' 
object has no attribute '_feedErrorsToResult'
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.)


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

Source: pymca
Version: 5.7.2+dfsg-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
pymca fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
pymca  from testing5.7.2+dfsg-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pymca/28728876/log.gz


==
ERROR: testShow (WidgetsInstantiationTest.TestPlotWidget.testShow)
--
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/PyMca5/PyMcaGui/misc/testutils.py", line 
254, in tearDown

if self._currentTestSucceeded():
   
  File 
"/usr/lib/python3/dist-packages/PyMca5/PyMcaGui/misc/testutils.py", line 
207, in _currentTestSucceeded

self._feedErrorsToResult(result, self._outcome.errors)

AttributeError: 'TestPlotWidget' object has no attribute 
'_feedErrorsToResult'


==
ERROR: testShow (WidgetsInstantiationTest.TestPlotWindow.testShow)
--
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/PyMca5/PyMcaGui/misc/testutils.py", line 
254, in tearDown

if self._currentTestSucceeded():
   
  File 
"/usr/lib/python3/dist-packages/PyMca5/PyMcaGui/misc/testutils.py", line 
207, in _currentTestSucceeded

self._feedErrorsToResult(result, self._outcome.errors)

AttributeError: 'TestPlotWindow' object has no attribute 
'_feedErrorsToResult'


==
ERROR: testShow (WidgetsInstantiationTest.TestRGBCorrelatorGraph.testShow)
--
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/PyMca5/PyMcaGui/misc/testutils.py", line 
254, in tearDown

if self._currentTestSucceeded():
   
  File 
"/usr/lib/python3/dist-packages/PyMca5/PyMcaGui/misc/testutils.py", line 
207, in _currentTestSucceeded

self._feedErrorsToResult(result, self._outcome.errors)

AttributeError: 'TestRGBCorrelatorGraph' object has no attribute 
'_feedErrorsToResult'


==
ERROR: testShow (WidgetsInstantiationTest.TestRGBCorrelatorWidget.testShow)
--
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/PyMca5/PyMcaGui/misc/testutils.py", line 
254, in tearDown

if self._currentTestSucceeded():
   
  File 

Bug#1019806: marked as done (sooperlooper: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 08:38:16 +
with message-id 
and subject line Bug#1019806: fixed in sooperlooper 1.7.8~dfsg0-2
has caused the Debian Bug report #1019806,
regarding sooperlooper: Please transition to wxwidgets3.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.)


-- 
1019806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sooperlooper
Severity: normal
Control: block 1019416 by -1

Hi,

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

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: sooperlooper
Source-Version: 1.7.8~dfsg0-2
Done: Dennis Braun 

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

Debian distribution maintenance software
pp.
Dennis Braun  (supplier of updated sooperlooper package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 07 Dec 2022 08:59:38 +0100
Source: sooperlooper
Architecture: source
Version: 1.7.8~dfsg0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Dennis Braun 
Closes: 1019806
Changes:
 sooperlooper (1.7.8~dfsg0-2) unstable; urgency=medium
 .
   [ Scott Talbert ]
   * Transition to wxWidgets 3.2 (Closes: #1019806)
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster (oldstable)
   * Use secure URI in Homepage field.
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Dennis Braun ]
   * Add salsa ci config
   * Update my email address
   * d/copyright, d/patches/*, d/watch: http --> https
   * Bump my d/copyright year
   * Reformat patches with gbp pq
   * debian/patches/*: Remove double Forward entries
Checksums-Sha1:
 2d0fb164bcd5b174245926ba1a1e96115ba9c82c 2354 sooperlooper_1.7.8~dfsg0-2.dsc
 a2fd0724067f6d9ead415f2bd5a15b49563a 13644 
sooperlooper_1.7.8~dfsg0-2.debian.tar.xz
 6a58ad81e5d1093de853e741022b0b7321416bcc 6311 
sooperlooper_1.7.8~dfsg0-2_source.buildinfo
Checksums-Sha256:
 a7fd78129309821503e92a7b47a796ae9873a7180b6c41fa9d48253a9eca900f 2354 
sooperlooper_1.7.8~dfsg0-2.dsc
 0a4b74f62b8e98bb138c17fbe877aec1931fba695381bd3d9bcac29c65538471 13644 
sooperlooper_1.7.8~dfsg0-2.debian.tar.xz
 8ecfc9d297f4dc214f00390e6bc497e91c6453a60248db0b0a00d6f87b39c633 6311 
sooperlooper_1.7.8~dfsg0-2_source.buildinfo
Files:
 036a74fd24841f57938e8540979bf2f8 2354 sound optional 
sooperlooper_1.7.8~dfsg0-2.dsc
 71ee6b480b7806e4848e374eb541407d 13644 sound optional 
sooperlooper_1.7.8~dfsg0-2.debian.tar.xz
 9f189f9dc08d274e8dd45e24becabc8d 6311 sound optional 
sooperlooper_1.7.8~dfsg0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEPLfDAq+1fmGoxhfdY06lXZArmDYFAmOQSCsPHHNuZEBkZWJp
YW4ub3JnAAoJEGNOpV2QK5g2OikQAKZysVL4zdEVZ504oO9dNvlHml3IXjIp1V7A
uLaSx+p4xEh0eMkOR9YdqhLsC1x33BojhsF414fG9xEKRPXYiMeeEga/UtguK7I0
sM3EiJf9vjEQVkshsUfojJmk05THDjgM2pB5XjRGSyVZtWHHxWFmakN9IRobdZT6
LYq1LzsMnO4pzlpXiWZ2mLefosbG3BsEe5N1eXz2LoI2DkMZU2gdOznwYROlb4M7
XztfdOH8lkxWELz37GItnrv/Uht1OrLwrdHqrf8lut5tBkh1chfA4o4JeZgnp6x8
km0jBtiy4VSTw/HomGBJkWidU2kuyvOIrCrOzyvckd51AISd8lwjsPGMeLUqNMfL
G+Y1YfeFIc+Cx6s5JB+PNXtsKDt4CcqyoAUQ8d2B8j4BZosXh9IBS8k5sYAutA8S
6Mr/9ylTu5ztte0JtwL8SXd8mW8017drFhRh5utALfMqB6IEN5+u2Vtm3V4IAoYZ
+CVaXOaOGChufH5u3onlAIcY3uK/IAqD3HyyCfORsyKIYhQ/veV5m7JeayEJzxiK
3H+J+SfoAPd9694ovGKNLqW70YiHgAhmhlKiGhlCoO4B3KEpq8meRzHZmIfsJX80

Bug#1022255: fixed in python-xarray 2022.11.0-2

[Antonio Valentino]

Dear Alastair,

On Mon, 21 Nov 2022 15:12:02 + Debian FTP Masters 
 wrote:

Source: python-xarray
Source-Version: 2022.11.0-2
Done: Alastair McKinstry 

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated python-xarray 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 Nov 2022 14:37:38 +
Source: python-xarray
Architecture: source
Version: 2022.11.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Alastair McKinstry 
Closes: 1004869 1022255 1023222
Changes:
 python-xarray (2022.11.0-2) unstable; urgency=medium
 .
   * Ack bogs fixed in this and previous releases:
 Closes: #1022255, #1004869, #1023222
Checksums-Sha1:
 25bfc4ad68c46f9f7428c7a008736478f3bd2fa7 3395 python-xarray_2022.11.0-2.dsc
 9d5fa48523ea38b6684f9b18e3d3a10a8aee2875 14092 
python-xarray_2022.11.0-2.debian.tar.xz
Checksums-Sha256:
 2921fcf4d7b5b82ed54813180ceacb2261264e99eb22e1b9bcf11e8660755e6e 3395 
python-xarray_2022.11.0-2.dsc
 c480af287094772516773b559ac385d6eed33001e1ded8aa1ddab4db721fc91b 14092 
python-xarray_2022.11.0-2.debian.tar.xz
Files:
 16ee7843761bf700d78213b6a8061f38 3395 python optional 
python-xarray_2022.11.0-2.dsc
 b483b08efbb572a27c4af434d3df17d1 14092 python optional 
python-xarray_2022.11.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmN7jiUACgkQy+a7Tl2a
06Vb0Q//YmFju6NG15oqqygNRQiiGIGPXS+qvtwPbXKGJDq6g3rX24KdF2tP77i6
Aw9LjfskclEe7TRQCwaS/49qh+6CE+Tndv47nMGb3jnBGL0vYa9YqOn3XeBAHCcw
aYCvbkks5HxDWizJ6Kh2Ohef0okEl2Q/pHDKMDfF+Q8DEvGh7iFtedVF6ARquPSW
95u3V6QhCCQPws26cYPz1L2a+QJuEf49lohoVDC8u4EtaJHbv1NKXtQP1srEqf10
zqbSd6KDqT3mn4dONtF7etxzQGxSHRySEPJpXQ+2kkdmcueLUT5UAEazC6SCdCUB
GMCqMFbwi4kY7CaaK5646XxCm3QQUg3UeZAMHqsBI9gYModfKG8twRhlyA4N9mam



Unfortunately version 2022.11.2 and 2022.12.0 of xarray still causes 
test failures in satpy.
According to the satpy upstream developers [1] (also reported in one of 
the previous messages [2]), the problem should be related to some kind 
of incompatibility between new versions of xarray and the version of 
dask currently in Debian (2022.02.0).


I can confirm that updating dask to 2022.11.1 fixes the issues and satpy 
tests pass with dask 2022.11.1 and xarray 2022.12.0.


I have started preparing a Merge Request [3] to update the dask package.
Unfortunately, while the Python package itself builds and works well, it 
is currently not possible to build the -doc package because of outdated 
build dependencies or new build dependencies still not in debian.


In addition, there are some other test failures in satpy that are not 
related to xarray/dask and could be fixed with an update to the latest 
upstream version of satpy (0.38.0).
I have the packaging work done (locally), but I cannot upload until the 
problem with xarray/dask is solved.


In conclusion the satpy version currently in testing works perfectly 
with xarray 2022.06.0, but the migration of xarray 2022.12.0 would break 
satpy and make it unbuildable both in testing and unstable.


Honestly I'm not sure about what is the best way to proceed.
In principle I think that this issue should be re-open and xarray 
2022.12.0 should not migrate, for the moment at least.


But then the way forward is not clear to me.
Waiting for an update of dask could take some time.
Of course I would be more that happy to help to prepare a new version of 
the dask package.


What is your idea about how to proceed?

[1] https://github.com/pytroll/satpy/issues/2248#issuecomment-1296325915
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022255#16
[3] https://salsa.debian.org/python-team/packages/dask/-/merge_requests/1


kind regards
--
Antonio Valentino

Bug#1025661: marked as done (rust-plotters: invalid Uploaders field: missing comma between Jelmer Vernooij and Blair Noctis)

[Debian Bug Tracking System]

Your message dated Wed, 07 Dec 2022 08:37:28 +
with message-id 
and subject line Bug#1025661: fixed in rust-plotters 0.3.4-2
has caused the Debian Bug report #1025661,
regarding rust-plotters: invalid Uploaders field: missing comma between Jelmer 
Vernooij and Blair Noctis
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.)


-- 
1025661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-plotters
Version: 0.3.4-1
Severity: serious

rust-plotters 0.3.4-1 introduced an invalid Uploaders field, that is
missing a comma between Jelmer Vernooij and Blair Noctis.

   $ apt-cache showsrc rust-plotters | grep -E '^$|^Version|^Uploaders'
   Version: 0.3.4-1
   Uploaders: Jelmer Vernooij  Blair Noctis 
   
According to Debian policy 5.6.3 the Uploaders field must separate
individual uploaders using commas:

   List of the names and email addresses of co-maintainers of the
   package, if any.
   ...
   The format of each entry is the same as that of the Maintainer
   field, and multiple entries must be comma separated.
  
https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders

This is causing the DDPO and BLS cron jobs to send error mails,
please fix it as soon as possible.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: rust-plotters
Source-Version: 0.3.4-2
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated rust-plotters 
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: Wed, 07 Dec 2022 09:10:41 +0100
Source: rust-plotters
Architecture: source
Version: 0.3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Sylvestre Ledru 
Closes: 1025661
Changes:
 rust-plotters (0.3.4-2) unstable; urgency=medium
 .
   [ Blair Noctis ]
   * Fix the author list (Closes: #1025661)
Checksums-Sha1:
 0e3000c742af767e67a1cae6a2b5b4f64649e23b 3151 rust-plotters_0.3.4-2.dsc
 b8b437f039ab7ea2b40aca5c290025cad2540b59 4640 
rust-plotters_0.3.4-2.debian.tar.xz
 30e2d7eb122fb018b3353f7e116d2eefe16fa37d 7961 
rust-plotters_0.3.4-2_source.buildinfo
Checksums-Sha256:
 ccabeadb039caff0583a2ddafe961f23e7e9ae8af3da87b6327cc13fe7b97c8b 3151 
rust-plotters_0.3.4-2.dsc
 f833954a4bb3dc5e5535fa0f849445390d8fc811d46217750dbdbdff6728ab52 4640 
rust-plotters_0.3.4-2.debian.tar.xz
 f6c07d487bf9a0aa7d9552c2aa3d7873aa2163525196c2a52f5655af9317bd48 7961 
rust-plotters_0.3.4-2_source.buildinfo
Files:
 a81cdc4de4e8d17a22114ba9ebd6da12 3151 rust optional rust-plotters_0.3.4-2.dsc
 f498d6c635814b9fbe27676fda423dc4 4640 rust optional 
rust-plotters_0.3.4-2.debian.tar.xz
 bf302ac6a55038e8de6b5c38dbdf6163 7961 rust optional 
rust-plotters_0.3.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmOQSogACgkQfmUo2nUv
G+GYVQ/9FbvNIopSnt4UeGAc06+wKHWZ7NXbZmuSBa628VlASOHxrya4IAT8nJOj
UpZhY27CM0RIM3FB1yVLC/EbDNd/0oGqhdrA+xXgnO2SlhZuVhfbjU9b6SsLLqje
rj3IeXIW1GmkDaeXJF8FcsFUHc3FdpeAVjnf/SEU+nYPtYpVQ6v40kZzGZiDwfgx
ybCFmqIq+1rMJci3B/t4IbLZT8xQndc5GK2QbOnTaBkTI3egWqXQ0EbuqYLjBLZi
WEtev2JCSxmBnHJPEN/QrqnR6bYJ8/MDEDh0yeNXCUgGnztW6kajKza/p73/Agn8
SY5lkqoKv3S2plUYbWHwpfPLQfLv9Lgu/FJ2D+fj8L+1HRo7JR2REyCU3DoawznX
NBCKL9QbmTHEUquNoDRHKMz/1w91nyDejeGCUR9YHzKjyc7Ah0tlNDq2XgRgXKXr
wTQwZO1W3BHDtNComAU4w8f70DseAEEhEGoZe1PaY5AJYgfsYxEpXDqbA9q3HTiT
PTAzazowrfIbmZuU0lUTbu4MPdPBhXwZ+3qYP4kZwjuQaIhNHkNrnHY7ODunPQlQ
shuHuGsoXITIKVOmqv/MWU2p0BKiuP7kCNugkqcKH8Ggohcis8vA/oFMEbPLOXF4
ke8GFkW2s/MIHvc2QwFESwtTeJpti1oLXeps91SMU1T0BBb+MbU=
=Z24Y
-END PGP SIGNATURE End Message ---

Processed: Prusa-Slicer and wxwidget3.2 (Transition: wxwidgets3.2)

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1023365
Bug #1019416 [release.debian.org] transition: wxwidgets3.2
1019416 was blocked by: 1019823 1019775 1019802 1019768 1019811 1019812 1019798 
1019780 1019801 1019774 1019786 1019767 1019822 1019803 1019835 1019769 1019834 
1019821 1019799 1019813 1019797 1019827 1019808 1019830 1019762 1019829 1019791 
1019818 1019792 1019776 1019809 1019763 1019770 1019807 1019784 1019828 1019785 
1019819 1019836 1019840 1019793 1019817 1019804 1019842 1019766 1019787 1019771 
1019789 1019814 1019833 1019805 1019796 1019841 1019772 1019790 1019831 1019824 
1019788 1019832 1019825 1019773 1019783 1019806 1019795 1019764 1019820 1019839 
1019765 1019794 1019837 1019778 1019826 1019810 1019782 1019838 1019781 1019777 
1019779 1019800
1019416 was not blocking any bugs.
Added blocking bug(s) of 1019416: 1023365

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