Bug#1030175: marked as done (libgetdata: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Wed, 15 Feb 2023 07:50:00 +
with message-id 
and subject line Bug#1030175: fixed in libgetdata 0.11.0-6
has caused the Debian Bug report #1030175,
regarding libgetdata: FTBFS: dh_install: error: missing files, aborting
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.)


-- 
1030175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgetdata
Version: 0.11.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=libgetdata=amd64=0.11.0-5%2Bb1=1675112061=0

   dh_install -a
install -m0755 -d debian/libgetdata-dev//usr/include
cp --reflink=auto -a debian/tmp/usr/include/getdata 
debian/tmp/usr/include/getdata.f debian/tmp/usr/include/getdata.h 
debian/libgetdata-dev//usr/include/
install -m0755 -d debian/libgetdata-dev//usr/lib/x86_64-linux-gnu
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.a 
debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so 
debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.a 
debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.a 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.a 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so 
debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/
install -m0755 -d 
debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/getdata
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2-0.11.0.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2.a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac-0.11.0.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac.a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip-0.11.0.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip.a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma-0.11.0.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma.a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip-0.11.0.so 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip.a 
debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip.so 
debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/getdata/
install -m0755 -d 
debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/pkgconfig
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/getdata.pc 
debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/pkgconfig/
install -m0755 -d debian/libgetdata8//usr/lib/x86_64-linux-gnu
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so.8 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so.8.1.0 
debian/libgetdata8//usr/lib/x86_64-linux-gnu/
install -m0755 -d debian/libgetdata\+\+7//usr/lib/x86_64-linux-gnu
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so.7 
debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so.7.1.0 
debian/libgetdata\+\+7//usr/lib/x86_64-linux-gnu/
install -m0755 -d debian/libfgetdata6//usr/lib/x86_64-linux-gnu
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so.6 
debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so.6.1.0 
debian/libfgetdata6//usr/lib/x86_64-linux-gnu/
install -m0755 -d debian/libf95getdata7//usr/lib/x86_64-linux-gnu
cp --reflink=auto -a 
debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so.7 
debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so.7.1.0 
debian/libf95getdata7//usr/lib/x86_64-linux-gnu/
install -m0755 -d debian/libgetdata-tools//usr/bin
cp --reflink=auto -a debian/tmp/usr/bin/checkdirfile 
debian/tmp/usr/bin/dirfile2ascii debian/libgetdata-tools//usr/bin/
install -m0755 -d debian/libgetdata-tools//usr/share/man/man1
cp --reflink=auto -a debian/tmp/usr/share/man/man1/checkdirfile.1 
debian/tmp/usr/share/man/man1/dirfile2ascii.1 
debian/libgetdata-tools//usr/share/man/man1/
dh_install: warning: Cannot find (any matches for) 
"usr/local/lib/python3.10/dist-packages/*" (tried in ., debian/tmp)

dh_install: warning: python3-pygetdata missing files: 
usr/local/lib/python3.10/dist-packages/*
dh_install: error: missing 

Bug#1030455: schedule: FTBFS: AssertionError: ScheduleValueError not raised by until

[Étienne Mollier]

Control: tags -1 confirmed

Good Morning,

Étienne Mollier, on 2023-02-14:
> However, looking at the nature of the test, and the hour at
> which it ran (build log starts at 03:05:50 +), I'm under the
> impression that the build time test failure could occur every
> day in a window between 0:00 and 5:00 am local hour.  I
> scheduled an sbuild attempt `at 3am`, we may see the result
> tomorrow and whether the bug is confirmed or unreproducible.

So, the test ran at 02:00 + and failed with same symptom.
My guess is upstream never intended to run the test out of
office hours.  It might be worth skipping the test as flaky, or
patching it to reduce the ftbfs time window to, say, 00:00 to
00:01 local hour.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/tty1, please excuse my verbosity.


signature.asc
Description: PGP signature

Processed: Re: Bug#1030455: schedule: FTBFS: AssertionError: ScheduleValueError not raised by until

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed
Bug #1030455 [src:schedule] schedule: FTBFS: AssertionError: ScheduleValueError 
not raised by until
Added tag(s) confirmed.

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

Bug#1030298: pyopencl: FTBFS on i386: = 1 failed, 304 passed, 7 skipped, 1 deselected, 2 xfailed, 31 warnings in 736.25s (0:12:16) =

[Andreas Beckmann]

Followup-For: Bug #1030298

minimized reproducer (needs only python3-pyopencl):

=
import math
import numpy as np

import pyopencl.array as cl_array
import pyopencl as cl
import pyopencl.clmath as clmath

context = cl.Context()
queue = cl.CommandQueue(context)

for s in [10]:
a = cl_array.arange(queue, s, dtype=np.float32)/10
a2 = cl_array.arange(queue, s, dtype=np.float32)/45.2 + 0.1
b = clmath.fmod(a, a2)

a = a.get()
a2 = a2.get()
b = b.get()

for i in range(s):
f=math.fmod(a[i], a2[i])
d=b[i] - f # should be zero
print("i=", i, " a[i]=", a[i], " a2[i]=", a2[i], " b[i]=clmath.fmod(a, 
a2)[i]=", b[i],
  " fmod(a[i], a2[i])=", f, " diff=", d);
#assert math.fmod(a[i], a2[i]) == b[i]
=

output on testing/i386:
# python3 test_1030298.py
i= 0  a[i]= 0.0  a2[i]= 0.1  b[i]=clmath.fmod(a, a2)[i]= 0.0  fmod(a[i], 
a2[i])= 0.0  diff= 0.0
i= 1  a[i]= 0.1  a2[i]= 0.1221239  b[i]=clmath.fmod(a, a2)[i]= 0.1  fmod(a[i], 
a2[i])= 0.1000149011612  diff= 0.0
i= 2  a[i]= 0.2  a2[i]= 0.14424779  b[i]=clmath.fmod(a, a2)[i]= 0.055752218  
fmod(a[i], a2[i])= 0.0557522177696228  diff= 0.0
i= 3  a[i]= 0.3  a2[i]= 0.16637167  b[i]=clmath.fmod(a, a2)[i]= 0.13362834  
fmod(a[i], a2[i])= 0.13362833857536316  diff= 0.0
i= 4  a[i]= 0.4  a2[i]= 0.18849558  b[i]=clmath.fmod(a, a2)[i]= 0.023008853  
fmod(a[i], a2[i])= 0.02300885319709778  diff= 0.0
i= 5  a[i]= 0.5  a2[i]= 0.21061948  b[i]=clmath.fmod(a, a2)[i]= 0.07876104  
fmod(a[i], a2[i])= 0.0787610411643982  diff= 0.0
i= 6  a[i]= 0.6  a2[i]= 0.23274335  b[i]=clmath.fmod(a, a2)[i]= 0.13451332  
fmod(a[i], a2[i])= 0.13451331853866577  diff= 0.0
i= 7  a[i]= 0.7  a2[i]= 0.25486726  b[i]=clmath.fmod(a, a2)[i]= 0.19026548  
fmod(a[i], a2[i])= 0.1902654767036438  diff= 0.0
i= 8  a[i]= 0.8  a2[i]= 0.27699116  b[i]=clmath.fmod(a, a2)[i]= 0.2460177  
fmod(a[i], a2[i])= 0.2460176944732666  diff= 0.0
i= 9  a[i]= 0.9  a2[i]= 0.29911503  b[i]=clmath.fmod(a, a2)[i]= 0.0026548803  
fmod(a[i], a2[i])= 0.0026548802852630615  diff= 0.0

output on sid/i386:
# python3 test_1030298.py
i= 0  a[i]= 0.0  a2[i]= 0.1  b[i]=clmath.fmod(a, a2)[i]= 0.0  fmod(a[i], 
a2[i])= 0.0  diff= 0.0
i= 1  a[i]= 0.1  a2[i]= 0.1221239  b[i]=clmath.fmod(a, a2)[i]= 0.1  fmod(a[i], 
a2[i])= 0.1000149011612  diff= 0.0
i= 2  a[i]= 0.2  a2[i]= 0.14424779  b[i]=clmath.fmod(a, a2)[i]= 0.055752218  
fmod(a[i], a2[i])= 0.0557522177696228  diff= 0.0
i= 3  a[i]= 0.3  a2[i]= 0.16637167  b[i]=clmath.fmod(a, a2)[i]= 0.13362834  
fmod(a[i], a2[i])= 0.13362833857536316  diff= 0.0
i= 4  a[i]= 0.4  a2[i]= 0.18849558  b[i]=clmath.fmod(a, a2)[i]= 0.023008853  
fmod(a[i], a2[i])= 0.02300885319709778  diff= 0.0
i= 5  a[i]= 0.5  a2[i]= 0.21061948  b[i]=clmath.fmod(a, a2)[i]= 0.07876104  
fmod(a[i], a2[i])= 0.0787610411643982  diff= 0.0
i= 6  a[i]= 0.6  a2[i]= 0.23274335  b[i]=clmath.fmod(a, a2)[i]= 0.13451329  
fmod(a[i], a2[i])= 0.13451331853866577  diff= -2.9802322387695312e-08
i= 7  a[i]= 0.7  a2[i]= 0.25486726  b[i]=clmath.fmod(a, a2)[i]= 0.19026548  
fmod(a[i], a2[i])= 0.1902654767036438  diff= 0.0
i= 8  a[i]= 0.8  a2[i]= 0.27699116  b[i]=clmath.fmod(a, a2)[i]= 0.24601772  
fmod(a[i], a2[i])= 0.2460176944732666  diff= 2.9802322387695312e-08
i= 9  a[i]= 0.9  a2[i]= 0.29911503  b[i]=clmath.fmod(a, a2)[i]= 0.0026548505  
fmod(a[i], a2[i])= 0.0026548802852630615  diff= -2.9802322387695312e-08

output on sid/amd64:
# python3 test_1030298.py
i= 0  a[i]= 0.0  a2[i]= 0.1  b[i]=clmath.fmod(a, a2)[i]= 0.0  fmod(a[i], 
a2[i])= 0.0  diff= 0.0
i= 1  a[i]= 0.1  a2[i]= 0.1221239  b[i]=clmath.fmod(a, a2)[i]= 0.1  fmod(a[i], 
a2[i])= 0.1000149011612  diff= 0.0
i= 2  a[i]= 0.2  a2[i]= 0.14424779  b[i]=clmath.fmod(a, a2)[i]= 0.055752218  
fmod(a[i], a2[i])= 0.0557522177696228  diff= 0.0
i= 3  a[i]= 0.3  a2[i]= 0.16637167  b[i]=clmath.fmod(a, a2)[i]= 0.13362834  
fmod(a[i], a2[i])= 0.13362833857536316  diff= 0.0
i= 4  a[i]= 0.4  a2[i]= 0.18849558  b[i]=clmath.fmod(a, a2)[i]= 0.023008853  
fmod(a[i], a2[i])= 0.02300885319709778  diff= 0.0
i= 5  a[i]= 0.5  a2[i]= 0.21061948  b[i]=clmath.fmod(a, a2)[i]= 0.07876104  
fmod(a[i], a2[i])= 0.0787610411643982  diff= 0.0
i= 6  a[i]= 0.6  a2[i]= 0.23274335  b[i]=clmath.fmod(a, a2)[i]= 0.13451332  
fmod(a[i], a2[i])= 0.13451331853866577  diff= 0.0
i= 7  a[i]= 0.7  a2[i]= 0.25486726  b[i]=clmath.fmod(a, a2)[i]= 0.19026548  
fmod(a[i], a2[i])= 0.1902654767036438  diff= 0.0
i= 8  a[i]= 0.8  a2[i]= 0.27699116  b[i]=clmath.fmod(a, a2)[i]= 0.2460177  
fmod(a[i], a2[i])= 0.2460176944732666  diff= 0.0
i= 9  a[i]= 0.9  a2[i]= 0.29911503  b[i]=clmath.fmod(a, a2)[i]= 0.0026548803  
fmod(a[i], a2[i])= 0.0026548802852630615  diff= 0.0

Andreas

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Theodore Ts'o]

There is more about this in the referenced bugs, but I dispute
Daniel's characterization of the issue.

I will draw the analogy of building a program which links against
glibc for Bookworm resulting in a binary that will not run on Buster.
We expect that, and we tell people to use build chroots.  This is not
something which is actionable, and we don't hold back glibc updates
just because you can no longer build on Debian 10.0 something that
won't work on Debian 9.0, or 8.0.

The same is true for file system featuers.  We add new features to
improve the user experience.  This is true for all file systems: ext4,
xfs, btrfs.  For example, in Bookworm, the version of xfsprogs is
going to enable the incompat "bigtime" feature for the first time.
This fixes XFS's 2038 problem.  A file system has the bigtime feature
enabled won't boot on Grub versions older than 2.06.  That is just the
way of the world.

As it truns out, for e2fsprogs, users (or distributions) can very
easily change the default file system features by editing the
configuration file /etc/mke2fs.conf.  So if a user wants to ask mke2fs
to disable certain features by default, and "dumb down" the
capabilities of the file system, they can to do that --- on the
command line, by tuning the file system after the fact, or by editing
the /etc/mke2fs.conf file.  They can even set the MKE2FS_CONFIG
environment variable to point at their own custom config file if they
would like.

We can change the default for mke2fs.conf file for Debian.  I don't
think it's warranted, and I'm not aware of any other distribution
doing this.  The fact that file system featuers that fix certain
problems (such as the 2038 bug) will cause older versions the
distribution to fail to accept that file system is always going to be
the case.  So how long do we hold back some new feature?  A year?  Two
years?  Five years?  Ten years?  Again, we don't do this with shared
library linkages; we just tell people to use a build chroot.

I would gently suggest that the most general solution to this problem
is to do the same for building VM images, if people won't want to be
bothered to learn how to configure the mfks program.  After all,
according to popcon, there are 960 times as many people who have use
gcc-10 recently (7685) as vmdb2 (8).

So if we are to hold e2fsprogs and xfsprogs to the standard that a
file system created by default must work on all older Debian and
Ubuntu distributions to some arbitrary point in history, should we
1000 times as much hold gcc-10 and clang to the same standard?

Obviously, that is a ridiculous thing to do.

Best regards,

- Ted

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 16:53 -0500 schrieb Theodore Ts'o:

[snip]

Your arrogant and ignorant attitude is frustrating, to say the least.
You don't care about the mess you create, for a feature, that probably
only a handful of people will ever need (I did a quick search and
didn't find anything regarding this feature - so why turn it on by
default then?). But yet you have to make it the default and break
running toolchains and methods. Talking to you is pointless. You cost
me hours of useless work yesterday and today because you ignore the
rules we have set out as a project to not frustrate each other.

I have reported this to the release team now.

Daniel

Bug#1021798: marked as done (crowdsec: FTBFS: FAIL: TestCreateMachineWithForwardedFor)

[Debian Bug Tracking System]

Your message dated Wed, 15 Feb 2023 00:06:25 +0100
with message-id <20230214230625.foeekrlq4y3w3...@debamax.com>
and subject line Re: Bug#1021798: crowdsec: FTBFS: FAIL: 
TestCreateMachineWithForwardedFor
has caused the Debian Bug report #1021798,
regarding crowdsec: FTBFS: FAIL: TestCreateMachineWithForwardedFor
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.)


-- 
1021798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: crowdsec
Version: 1.0.9-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

crowdsec in sid (and experimental) recently started to FTBFS:

=== RUN   TestCreateMachineWithForwardedFor
time="2022-10-14T20:21:20Z" level=info msg="Creating new API server"
 - [Fri, 14 Oct 2022 20:21:20 UTC] "POST /v1/watchers HTTP/1.1 201 56.31ms 
"crowdsec-test/" "
machines_test.go:81:
Error Trace:
/build/crowdsec-1.0.9/_build/src/github.com/crowdsecurity/crowdsec/pkg/apiserver/machines_test.go:81
Error:  Not equal:
expected: "1.1.1.1"
actual  : ""

Diff:
--- Expected
+++ Actual
@@ -1 +1 @@
-1.1.1.1
+
Test:   TestCreateMachineWithForwardedFor
--- FAIL: TestCreateMachineWithForwardedFor (0.06s)

Full log attached.


Andreas


crowdsec.sid.build.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1.4.2-1

Cyril Brulebois  (2022-10-14):
> This should be fixed in the upcoming 1.4.x versions, the test suite
> doesn't fail there. There are a bunch of dependencies that need to go in
> before that can be uploaded though:
>   https://lists.debian.org/debian-go/2022/10/msg00018.html

Closing this bug report as addressed in the just-uploaded version (even
if a Closes statement was forgotten there).


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


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

Bug#1031325: e2fsprogs 1.47.0 introduces a breaking change into Bookworm, breaking grub and making installations of Ubuntu and Debian releases via debootstrap impossible

[Daniel Leidert]

Package: release.debian.org
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

A week ago, Theodore Ts'o uploaded e2fsprogs 1.47.0 into Debian unstable. This
version contains a unannounced change that basically breaks grub2 (and
grub-install). This issue has been reported as #1030939 [1] and #1030846 [2].
To "fix" the issue, instead of turning the feature off, a patch to grub2 in Sid
has been committed recently. Unfortunately, that only fixes grub in Sid. Grub
in Bullseye or any current Ubuntu release *cannot* deal with a filesystem
created by this version of e2fsprogs. This basically breaks the debootstrap
method of installing a Debian or Ubuntu. If e2fsprogs 1.47.0 is allowed into
Testing, we can no longer use the debootstrap method to install a Debian
Bullseye (or older) or any Ubuntu release. It requires to manually change the
filesystem features before it can be used again. It also makes e.g. vmdb2 in
Sid unusable to create images of Bullseye or older Debian releases, or Ubuntu
releases.

The gain of enabling the metadata_csum_seed feature by default is not
noteworthy. It is a feature that hardly anybody needs. I have not seen one
use-case nor even relevant search hits. But the loss is heavy. User's can no
longer simply follow [3] to install any Debian or Ubuntu system if the
filesystem has been created with e2fsprogs 1.47.0. It also breaks software in
the midst of the freeze.

I hereby ask the release team to step in and either make sure that the
metadata_csum_seed feature is not turned on by default in e2fsprogs in Bookworm
or that version 1.47.0 is not shipped as part of Bookworm.

Reasons:

- - this breaks existing tools for no apparant reason

- - introducing this breaking change is too late in the release cycle to deal
  with it properly

- - the metadata_csum_seed feature is hardly useful or requested; it can be
  turned on if necessary; no need to make it the default in Bookworm

- - there is no grub upstream release with support for it; only patched grub
  versions can cope with it

- - the change makes it impossible to create filesystems with this version of
  e2fsprogs and then run a grub-install from a target system that does not cope
  with that feature; basically breaking the debootstrap method of installing
  Debian or Ubuntu onto a server (violating #4 of the Debian social contract)

- - to cope with the former issues, users will have to know about that
  incompatibility and ways to deal with it; none of that is prepared; the
  package maintainer even refuses a NEWS entry

- - it breaks vmdb2, only allowing to make images of Debian Bookworm and Sid (if
  grub is involved)

- - pushing this metadata_csum_seed feature violates #4 of the Debian social
  contract

Instead, turning on this feature should be postponed for the next release cycle
where a proper transition can be done.

[1] https://bugs.debian.org/1030939
[2] https://bugs.debian.org/1030846
[3] https://www.debian.org/releases/stable/amd64/apds03

Daniel Leidert

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmPsE8UACgkQS80FZ8KW
0F0Aug/+Kb6xrQcILq+VYpKk/161UXgQA47ccydz78uT3r1eRBVJIPReULZPdjvk
W4PDDOYypScsx4+EahdOVViAMiOyzI0eroivZmDItxY1HR6LpKdeQFPLET6FdbfM
pDHezFKXqsulYQWLu5M6yPCtMWGCmAtiH9NeppzUY7+dnBr2yzZGitH4pPSh7MmS
9jxRIKG0xGa3wF+a1yEgHE0nPvqD5a97GlwL5+MTg580k/e1VRpaQaYrTRr3CHyK
EJbVOu70K+qXgP837x6B5eyYmihJWiNBMxm9JqF1TrwTKXwk26zpZ2+T1uKVgVKj
Y5AlZX8Gypdxq0Q3uFPSlzBhetd2wvrUt9hKEb52fdzw3L4AsY2Ken98sAhqy7Xi
PGVdihiUSAT5gslthm3qB3fGQQMIEXI3UdHqSx7ARgZJ6Gkf/zIjk5sKl/xiGe+t
jJExPdCR7H8+tPNZhJEhx6BLtLs8tLm+zhOAr3rZVekEn3PJJAHOKPs1KPBWinYr
FsVBsWBWzOgKNARu31u/o4s5BFV99M45gZqHLs3Mp5TvJqIxkbwS0FDoCa/TausP
vojuW4kDPM7Jjw568W4O8csXBiI/qEcEPXZGPrgGVs3Yo1hV/KkJUOkQ9y/VvRps
POx+RwF400ov8zOxGPqETkqDjl/2JQ47OOvogJMi6FDRQk+YE2w=
=bKh7
-END PGP SIGNATURE-

Bug#1030545: qemu: qemu-img and qemu-system-s390x hang on s390x

[James Addison]

Source: qemu
Followup-For: Bug #1030545

> In the build logs for libguestfs, I see last successful builds were done
> on 5.10.0-20-s390x kernel, and on 5.10.0-21-s390x, all builds fails.
> 5.10.0-21-s390x is the one running on zelenka too.

Sorry for what I now worry may have been distractions in my previous comments.

There is at least one failed build where the cause seem unrelated to qemu-img:

https://buildd.debian.org/status/fetch.php?pkg=libguestfs=s390x=1%3A1.48.6-1%2Bb3=1675540466=1

That build (libguestfs 1:1.48.6-1+b3, kernel 5.10.0-21-s390x) passes qemu-img
steps, but later fails to find the 'getenforce' binary (from selinux-utils):

> SELinux: sh: 1: getenforce: not found

Could that mean there's a missing build-dep on selinux-utils? (and perhaps the
kernel version upgrade has introduced/exposed that?)

Bug#1031315: libjpeg9: libjpeg.so.9* missing

[Roy Clark (kralcyor)]

Package: libjpeg9
Version: 1:9d-1.1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

/usr/lib/*/{libjpeg.so.9,libjpeg.so.9.4.0} are missing in the package, making 
it completely unusable:
$ dpkg -L libjpeg9 
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/libjpeg9
/usr/share/doc/libjpeg9/README.gz
/usr/share/doc/libjpeg9/changelog.Debian.gz
/usr/share/doc/libjpeg9/changelog.gz
/usr/share/doc/libjpeg9/copyright

This issue may related to changes in the build system. While libjpeg.so.9* 
appear in the old version 1:9d-1, a rebuilt package of version 1:9d-1 on a 
latest unstable Debian system also lacks libjpeg.so.9*.

The following lines appeared in the latest build log on buildd[1]:
   checking whether the x86_64-linux-gnu-gcc linker (/usr/bin/ld -m elf_x86_64) 
supports shared libraries... ./configure: line 11202: : supported targets:.* 
elf: command not found
   no
which corresponds to the following lines in the regenerated `configure':
   if $LD --help 2>&1 | $EGREP ': supported targets:.* elf' > /dev/null \
&& test no = "$tmp_diet"

It can be found from `config.status' that $EGREP is empty, which may cause this 
issue:
EGREP=''

I didn't figure out why $EGREP is empty, but adding the following line into 
debian/rules will generate a normal package with libjpeg.so.9* included:

diff -Nru libjpeg9-9d/debian/rules libjpeg9-9d/debian/rules
--- libjpeg9-9d/debian/rules2023-02-15 03:52:51.0 +0800
+++ libjpeg9-9d/debian/rules2022-11-04 03:14:38.0 +0800
@@ -18,8 +18,6 @@
 CFLAGS += -O2
 endif
  
-export EGREP = grep -E
-
 export AUTOMAKE = automake-1.16
 export ACLOCAL = aclocal-1.16
 export AUTOHEADER = true

[1] 
https://buildd.debian.org/status/fetch.php?pkg=libjpeg9=amd64=1%3A9d-1.1=1667678775=0

Regards,
Roy Clark

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

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

-- debconf-show failed

Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Theodore Ts'o]

On Tue, Feb 14, 2023 at 07:35:51PM +0100, Daniel Leidert wrote:
> 
> As soon as this version hits testing, you have successfully disabled
> the last working environment to use vmdb2 to create images of Ubuntu
> and Debian. As soon as this version hits Testing, one then can no
> longer build images for either any Ubuntu release nor Debian Bullseye
> or older. I can then only build images for Bookworm and Sid. Please
> think about that.

The number of users who use vmdb2 are quite small; for those users who
do, there is a simple fix.  You can either diable the feature using
tune2fs, or you can just make an edit to your /etc/mke2fs.conf file to
not enable the feature.  A one line change to /etc/mke2fs.conf is
hardly what I'd call "impossible".

> You *seriously* break the debootstrap method of installing Debian or
> Ubuntu.

As you have pointed out, this is not a debootstrap issue, since it
doesn't create the file system.  The uestion is in how the file system
is created, and this is not hard to fix.  You can just run "mke2fs -O
^metadata_csum_seed _file_or_block_device_"; you can run "tune2fs -O
^metadata_csum_seed _file_or_block_device"; you can make a one-line
change to /etc/mke2fs.conf.

> You haven't documented how to disable that
> breaking change when creating filesystems for distributions where grub
> does not support this (there is not even a NEWS entry). You haven't
> even announced that breaking change. And yet you are going to break one
> of our two standard methods of installing Debian or Ubuntu. How is any
> of what you have been saying so far addressing any of these issues?

Sorry, as far as I'm concerned, vmdb2 is not that important.  We don't
document in a NEWS entry or anywhere else, how to build a binary that
links against a newer version of glibc so it will work on an older
system.  And I would consider the compiler toolchain to be far more
common a usecase than vmdb2.  Indeed, your use of "toolchain" for file
system utilities is a new one for me.  I've never heard the term
"toolchain" used in such a way before.

> I do not understand why you are pushing 1.47.0 over 1.46.6, which you
> had uploaded just five days before the former. You haven't even
> presented a reason yet.

It has anumber of new features that will improve ext4's performance on
highly parallel workloads; it makes it possible for cloud VM's to be
able to safely update the root file systems's UUID while it is
mounted, among other changes.

- Ted

Bug#1031303: marked as done (silver-platter: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 21:39:37 +
with message-id 
and subject line Bug#1031303: fixed in silver-platter 0.5.6-2
has caused the Debian Bug report #1031303,
regarding silver-platter: autopkgtest regression
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.)


-- 
1031303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: silver-platter
Version: 0.5.6-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/s/silver-platter/31340548/log.gz

...
==
ERROR: tests (unittest.loader._FailedTest.tests)
--
ImportError: Failed to import test module: tests
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 154, in loadTestsFromName
module = __import__(module_name)
 ^^^
ModuleNotFoundError: No module named 'silver_platter.tests'


--
Ran 1 test in 0.000s

FAILED (errors=1)
autopkgtest [07:13:29]: test testsuite: ---]
autopkgtest [07:13:30]: test testsuite:  - - - - - - - - - - results - - - - - 
- - - - -
testsuiteFAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: silver-platter
Source-Version: 0.5.6-2
Done: Jelmer Vernooij 

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated silver-platter 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: Tue, 14 Feb 2023 19:42:23 +
Source: silver-platter
Architecture: source
Version: 0.5.6-2
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij 
Changed-By: Jelmer Vernooij 
Closes: 1031303
Changes:
 silver-platter (0.5.6-2) unstable; urgency=medium
 .
   * Fix test suite invocation in debian/tests/control. Closes: #1031303
Checksums-Sha1:
 fbe2b01b36597bb0c3bbf212d8574968a37b1a0f 1914 silver-platter_0.5.6-2.dsc
 d200ac3225e519d6c7872fa6454fe292d11b4f3a 47244 
silver-platter_0.5.6-2.debian.tar.xz
 08658219eb9da8df5295160e11481108aef7bc25 17305 
silver-platter_0.5.6-2_source.buildinfo
Checksums-Sha256:
 df50aafed28e581457909bfefe86701257cdc8e1db2c1e00d743e202d9c6ddd4 1914 
silver-platter_0.5.6-2.dsc
 ab19ef30b08ee3a51e4207efeb4c995ff3809c9e0568195a70540eda9243f832 47244 
silver-platter_0.5.6-2.debian.tar.xz
 0819d9aae2b827e3a8badde0f443f4ad3beb199ef660f6f2cf911295ea43 17305 
silver-platter_0.5.6-2_source.buildinfo
Files:
 50c1edaa6f824ab775141d7b7381615d 1914 vcs optional silver-platter_0.5.6-2.dsc
 b71874e208296c0610405cc8d5e9f785 47244 vcs optional 
silver-platter_0.5.6-2.debian.tar.xz
 efc304b74a51ce416f41bbf738ddca42 17305 vcs optional 
silver-platter_0.5.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEgIoEfJX3ae+y722SMG8hYYBCUGYFAmPr/AsACgkQMG8hYYBC
UGZ2GwgAqhzJFkDIb3WUADNaCf6AC+dtTiHpH4XPX3+hNi3ipTroMnjIs7Zdkt1E
OiN8YmpyWuN9tQrmKCL3ScniRNBv/RVHfiIthyLGFbg7nqGHNTsMEbR/YHHrnn+8
DMZoZiyn1MUVIMIzEpYC2G5+ZapHPCO3RObBl2FvorDwPLvONMluyNySrnlxQzCA
a9+C5xcXQEh+REf6WFResm3VE8EhCBvL7zBsF8ht+v5p2qEqWKqpDlc4Q5FyTZHJ
YKjSMOc5F9jSrqfkgVblItC2648UbskhgwLe8WfQKuScgtOJLT7h3s453l/oiT0s
jIU4LDxXwXzwuT/WlSFeb+JjcpoDXQ==
=5o+2
-END PGP SIGNATURE End Message ---

Bug#1031247: marked as done (systemd-cron: trying to overwrite '/etc/cron.yearly/.placeholder', which is also in package systemd-cron)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 21:39:45 +
with message-id 
and subject line Bug#1031247: fixed in systemd-cron 1.15.19-5
has caused the Debian Bug report #1031247,
regarding systemd-cron: trying to overwrite '/etc/cron.yearly/.placeholder', 
which is also in package systemd-cron
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.)


-- 
1031247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-cron
Version: 1.15.19-4
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Unpacking cron-daemon-common (3.0pl1-160) over (3.0pl1-156) ...
dpkg: error processing archive 
/var/cache/apt/archives/cron-daemon-common_3.0pl1-160_all.deb (--unpack):
 trying to overwrite '/etc/cron.yearly/.placeholder', which is also in package 
systemd-cron 1.15.19-4
Errors were encountered while processing:
 /var/cache/apt/archives/cron-daemon-common_3.0pl1-160_all.deb

It appears that cron-daemon-common has gotten around shipping 
/etc/cron.yearly/.placeholder, so systemd-cron can probably stop shipping it.

- -- Package-specific info:
- -- output of systemd-delta

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

Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages systemd-cron depends on:
ii  cron-daemon-common  3.0pl1-156
ii  libc6   2.36-8
ii  python3 3.11.1-3
ii  systemd [systemd-sysusers]  252.5-2
ii  systemd-sysv252.5-2

systemd-cron recommends no packages.

Versions of packages systemd-cron suggests:
ii  nullmailer [mail-transport-agent]  1:2.2-4

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmPqqAUACgkQrh+Cd8S0
17auyg/9Eiyyo8/NwuKVdM2L3pwiYqvEjgu2BYo60cFak8K6v/vZyvFM75LDl/gm
4uHW/txgUPJ61Wi8iDOdzMWM1k+6yk237+snmByJ1etUeA38VE9KY+xIKcQMBfsG
sa7gMP6Lav0ZFqV3UlfejC81UoXQ6VCJ0V0BglVhcuXWs6P0P5SCYUxftbHRFd+o
PFQBLC1+U174oGTGx4Bi9ukaJ0yUFADrxzDfx6GYUXgoKuyTy1IXgn4Vr40FaIjM
91tvvYY5iY/zEQUEtxoS37j7H8LGMDCVGucLbS2KVm3zFsNn8UvE/xIJ4sZNihbm
DTQO6v7rmjLZxIjDJgkjfZs3i5NW/BFjN1OA/igoPhT6C6bTDf40uXXLpRmS4ZFp
BXBzzBZk5t3JwsNxEl5caidoOaqoGVfp0nLCe2w+InnLXIW+n+gmLD2Ksg4v9t4u
BIUD4rHGRpN1VnYnGx7vTzAvzuNYgFArxPasRoeebntdAusx79zraaZtvON3PhS5
P5OHsFQtR4avB+6O8yZXZl16R5QMKwGwuzix05pU2DEYL0rEsMr5J5v+SL5IFpLT
WX7GVPvmOAuMSAzpdLtPIt48uv9oFPigYA74Eyn/Gj0eCvFxNIij3g/kVTye3lUL
lcbbDtGqWcfOCnwmwJzl7o6vgKafODt4BGzKnLqDIwH5FAghS/Y=
=A4oz
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: systemd-cron
Source-Version: 1.15.19-5
Done: Alexandre Detiste 

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

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated 
systemd-cron 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: Tue, 14 Feb 2023 22:23:19 +0100
Source: systemd-cron
Architecture: source
Version: 1.15.19-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Systemd Maintainers 

Changed-By: Alexandre Detiste 
Closes: 1031247
Changes:
 systemd-cron (1.15.19-5) unstable; urgency=medium
 .
   * /etc/cron.yearly/.placeholder is now owned by
 "cron-daemon-common" (Closes: #1031247)
Checksums-Sha1:
 2663102318d96e4757bda32c9dbb06e11f59d200 2064 systemd-cron_1.15.19-5.dsc
 55dd4e58366aeb51f314dea586822d05cdad36e5 7392 
systemd-cron_1.15.19-5.debian.tar.xz
 45d08e1bc8131590529b9f4916e577f99b347f79 6789 
systemd-cron_1.15.19-5_source.buildinfo
Checksums-Sha256:
 785a8686454ace6f173c056e00a216a610ce814485dc8077d17ab6d21e7eac66 2064 
systemd-cron_1.15.19-5.dsc
 27743aff5cf4d48797e88133ea09a9c2787b989d0a4cc805413c8eb51608e8d0 7392 
systemd-cron_1.15.19-5.debian.tar.xz
 9016393855c28c69e01889c417b3c650e393846d249952534c7a0efd4a1a0d42 6789 

Bug#1031231: tries to overwrite /etc/cron.yearly/.placeholder from systemd-cron

[Alexandre Detiste]

To be explicit: on your side you'd need yet another upload with a

   Conflicts: systemd-cron (<<1.15.19-5~)

(and/or a Breaks?)

Bug#995156: easy-rsa: vars Autodetection

[Lee Garrett]

I'm bumping the bug severity because currently it will ignore 
security-relevant settings like keysize and algo, and the defaults are 
pretty weak.

Bug#1029588: bts: Changes in libio-socket-ssl-perl 2.078 make bts fail to send mail to mail-server via SSL/TLS - hostname verification failed

[Lee Garrett]

Bumped severity as this makes bts currently unusable, and probably 
breaks for quite a few DDs their workflow.

Bug#1031231: tries to overwrite /etc/cron.yearly/.placeholder from systemd-cron

[Alexandre Detiste]

Hi,

I uploaded systemd-cron_1.15.19-5 , without the file.

I'm not sure if the handover of this non-file
is done correctly, you can NMU if you know better.

[lament placeholder]

Alexandre

Processed: severity of 995156 is grave

[Debian Bug Tracking System]

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

> severity 995156 grave
Bug #995156 [easy-rsa] easy-rsa: vars Autodetection
Ignoring request to change severity of Bug 995156 to the same value.
> thanks
Stopping processing here.

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

Processed: severity of 1029588 is grave

[Debian Bug Tracking System]

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

> severity 1029588 grave
Bug #1029588 [devscripts] bts: Changes in libio-socket-ssl-perl 2.078 make bts 
fail to send mail to mail-server via SSL/TLS - hostname verification failed
Ignoring request to change severity of Bug 1029588 to the same value.
> thanks
Stopping processing here.

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

Processed: severity of 995156 is grave

[Debian Bug Tracking System]

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

> severity 995156 grave
Bug #995156 [easy-rsa] easy-rsa: vars Autodetection
Ignoring request to change severity of Bug 995156 to the same value.
> thanks
Stopping processing here.

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

Processed: severity of 995156 is grave

[Debian Bug Tracking System]

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

> severity 995156 grave
Bug #995156 [easy-rsa] easy-rsa: vars Autodetection
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.

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

Processed: change bug severity

[Debian Bug Tracking System]

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

> severity 1029588 grave
Bug #1029588 [devscripts] bts: Changes in libio-socket-ssl-perl 2.078 make bts 
fail to send mail to mail-server via SSL/TLS - hostname verification failed
Severity set to 'grave' from 'important'
> kthxbye
Stopping processing here.

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

Bug#1030455: schedule: FTBFS: AssertionError: ScheduleValueError not raised by until

[Étienne Mollier]

Hello,

Jumping in because this bug is causing autoremoval of a reverse
depency in my radar.  The test failure below did not appear when
I ran the build time tests a dozen of times in a row:
> > test_until_time (test_schedule.SchedulerTests.test_until_time) ... FAIL
> > test_weekday_at_todady 
> > (test_schedule.SchedulerTests.test_weekday_at_todady) ... ok
> > 
> > ==
> > FAIL: test_until_time (test_schedule.SchedulerTests.test_until_time)
> > --
> > Traceback (most recent call last):
> >   File 
> > "/<>/.pybuild/cpython3_3.11_schedule/build/test_schedule.py", 
> > line 317, in test_until_time
> > self.assertRaises(ScheduleValueError, every().day.until, 
> > datetime.time(hour=5))
> > AssertionError: ScheduleValueError not raised by until

However, looking at the nature of the test, and the hour at
which it ran (build log starts at 03:05:50 +), I'm under the
impression that the build time test failure could occur every
day in a window between 0:00 and 5:00 am local hour.  I
scheduled an sbuild attempt `at 3am`, we may see the result
tomorrow and whether the bug is confirmed or unreproducible.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent at ftbfs o'clock.


signature.asc
Description: PGP signature

Bug#1031305: marked as done (libhttp-daemon-ssl-perl: autopkgtest regression with libio-socket-ssl-perl_2.081-2)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 21:04:22 +
with message-id 
and subject line Bug#1031305: fixed in libhttp-daemon-ssl-perl 1.05-01-5
has caused the Debian Bug report #1031305,
regarding libhttp-daemon-ssl-perl: autopkgtest regression with 
libio-socket-ssl-perl_2.081-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.)


-- 
1031305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhttp-daemon-ssl-perl
Version: 1.05-01-4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/libh/libhttp-daemon-ssl-perl/31328850/log.gz

...
t/testmodule.t .. 
1..14
ok #authority certificate generated 1
ok #server certificate generated 2
ok #authority certificate saved 3
ok #server certificate saved 4
ok #server key saved 5
ok #server init port=43389 6
ok #server fileno 7
ok #server url test 8
ok #client bad connection test 7
ok #bad request handled 9
Use of uninitialized value $2 in concatenation (.) or string at 
/usr/share/perl5/IO/Socket/SSL.pm line 792.
ok #client good connection test 8
ok #valid request handled 10
ok #server method processing 11
ok #client permission test 9
ok
All tests successful.
Files=3, Tests=37,  2 wallclock secs ( 0.01 usr  0.00 sys +  1.41 cusr  0.05 
csys =  1.47 CPU)
Result: PASS
autopkgtest [00:12:47]: test autodep8-perl-build-deps: ---]
autopkgtest [00:12:47]: test autodep8-perl-build-deps:  - - - - - - - - - - 
results - - - - - - - - - -
autodep8-perl-build-deps FAIL stderr: Use of uninitialized value $2 in 
concatenation (.) or string at /usr/share/perl5/IO/Socket/SSL.pm line 792.
...
autopkgtest [00:13:17]:  summary
autodep8-perl-build-deps FAIL stderr: Use of uninitialized value $2 in 
concatenation (.) or string at /usr/share/perl5/IO/Socket/SSL.pm line 792.
autodep8-perlPASS (superficial)
autodep8-perl-recommends PASS (superficial)
--- End Message ---
--- Begin Message ---
Source: libhttp-daemon-ssl-perl
Source-Version: 1.05-01-5
Done: gregor herrmann 

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated 
libhttp-daemon-ssl-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 14 Feb 2023 21:43:21 +0100
Source: libhttp-daemon-ssl-perl
Architecture: source
Version: 1.05-01-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1031305
Changes:
 libhttp-daemon-ssl-perl (1.05-01-5) unstable; urgency=medium
 .
   * Team upload.
   * Add patch to make test compatible with IO::Socket::SSL >= 2.079.
 Thanks to Adrian Bunk for the bug report. (Closes: #1031305)
   * Lowercase short description.
Checksums-Sha1:
 1388d2ab140c9058bc3c5b8a250d90b5b5c8935a 2552 
libhttp-daemon-ssl-perl_1.05-01-5.dsc
 326ed243010dee492d12af7f398c93021d14297d 6112 
libhttp-daemon-ssl-perl_1.05-01-5.debian.tar.xz
Checksums-Sha256:
 340737b5221cbe431d0eba4f23eb9c70a87642e0a2bf2021f9ec3f6d913c58e8 2552 
libhttp-daemon-ssl-perl_1.05-01-5.dsc
 3a3ab9a4c99f1509729a3ee01af5593f8d3bf34f76b591ea2af7547cd7051ace 6112 
libhttp-daemon-ssl-perl_1.05-01-5.debian.tar.xz
Files:
 6d30f803ef541cd712304e05dfa835c0 2552 perl optional 
libhttp-daemon-ssl-perl_1.05-01-5.dsc
 19eb8ffe6ce90a4193fef945dfdda4f4 6112 perl optional 
libhttp-daemon-ssl-perl_1.05-01-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmPr8xpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgYxjw//Uz91wq+h/bECZr51UX3GQEOJIIPASGYB0qHlZ3RGnnhbnvYkRi0ZAVfq
BrHCBkC/iFOsi1PVqo0I2ExVsDJRsZ84UQi5HlnoWGniH8QHAk0rbr7UzJChD4HR
rL2iz4RQaSM2BApRCn2f0zvxuMivdWG6tcTAXYJSXS5Bq2xm3heUArDCMwbQeO0u
IWJ3iWZApiOU0gqSK3PxHu3nUCgGcmwQRnu1GHToJp4a2nnHjUumbROysXOhJZyc
X8ssfxQKs8AnaKv/bqYb4/pjP9058EpJnqis3nbVJ0I6/zJQqo0Ir74SSPAdEAcj

Processed: tagging 1031258, tagging 1031253, tagging 1031187

[Debian Bug Tracking System]

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

> tags 1031258 + sid bookworm
Bug #1031258 [python-instagram] python-instagram: Missing active upstream 
should not be in Bookworm
Added tag(s) sid and bookworm.
> tags 1031253 + sid bookworm
Bug #1031253 [src:jthread] jthread: FTBFS (dh_install: error: missing files, 
aborting)
Added tag(s) sid and bookworm.
> tags 1031187 + sid bookworm
Bug #1031187 [src:dnscrypt-proxy] dnscrypt-proxy: FTBFS: Can't exec "go": No 
such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 518.
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Processed: severity of 1012232 is serious, severity of 1031247 is serious, tagging 1031080

[Debian Bug Tracking System]

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

> severity 1012232 serious
Bug #1012232 [autoconf] freespace2: FTBFS: ./configure: line 17040: syntax 
error near unexpected token `ax_cxx_compile_cxx11_required=falsednl'
Bug #1016728 [autoconf] autoconf: _AC_PROG_CXX_STDCXX_EDITION_TRY test is 
broken due to typo
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> severity 1031247 serious
Bug #1031247 [systemd-cron] systemd-cron: trying to overwrite 
'/etc/cron.yearly/.placeholder', which is also in package systemd-cron
Severity set to 'serious' from 'normal'
> tags 1031080 + pending
Bug #1031080 [nvidia-driver] nvidia-driver: OpenCL compiler dorsn't wok since 
version 520
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1028356: procmail: Variable set with stdin pipe action fails leaving empty variable

[Santiago Vila]

Hello.

This is what I did today. Maybe someone can follow my steps
and arrive at something.

I'm using this $HOME/.procmailrc file:

-
LOGFILE=$HOME/.cache/procmail.log
VERBOSE=yes

:0 h
SUBJECT=|formail -cXSubject:|cat

MYVAR=$SUBJECT

:0
/dev/null
-

and this command to test it:

echo "Subject: thesubject" | formail | procmail

A non-buggy procmail (for example, the one in bullseye) will
produce a $HOME/.cache/procmail.log file like this:

procmail: [2236560] Tue Feb 14 20:27:41 2023
procmail: Assigning "SUBJECT="
procmail: [2236560] Tue Feb 14 20:27:41 2023
procmail: Executing "formail -cXSubject:|cat"
procmail: Assigning "MYVAR=Subject: thesubject"
procmail: Assigning "LASTFOLDER=/dev/null"
procmail: Opening "/dev/null"
procmail: Notified comsat: "bluser@0:/dev/null"
From foo@bar  Tue Feb 14 20:27:41 2023
 Subject: thesubject
  Folder: /dev/null  60


However, a buggy procmail (for example, procmail_3.24-1) will
produce a $HOME/.cache/procmail.log file like this:

procmail: [2236823] Tue Feb 14 20:30:28 2023
procmail: Assigning "SUBJECT="
procmail: [2236823] Tue Feb 14 20:30:28 2023
procmail: Executing "formail -cXSubject:|cat"
procmail: Assigning "MYVAR="
procmail: Assigning "LASTFOLDER=/dev/null"
procmail: Opening "/dev/null"
procmail: Notified comsat: "bluser@0:/dev/null"
From foo@bar  Tue Feb 14 20:30:28 2023
 Subject: thesubject
  Folder: /dev/null  60

The relevant thing here is that MYVAR is empty.


Now, to do a git-bisect (or something which resembles it),
I'm doing this:

git checkout some-git-id --force

To avoid putting the debian/* files on top of this,
I'm using this simple script "make-procmail" to compile:

#!/bin/sh
set -e
make CC=gcc CFLAGS0="" LDFLAGS0="" SEARCHLIBS="-lm" LOCKINGTEST=100
cat src/procmail > /usr/bin/procmail

where I've previously made /usr/bin/procmail mode 777 for that to work.
(This is naturally in a test machine).

It is possible that the above fails with "text file busy", then
I execute this other script as root:

#!/bin/sh
set -e
cd /usr/bin
rm -f procmail
touch procmail
chmod 777 procmail


If "some-git-id" is too old, the following error may arise:

formisc.h:20:2: error: conflicting types for ‘getline’
   20 |  getline P((void));
  |  ^~~
In file included from includes.h:41,
 from formail.c:16:
/usr/include/stdio.h:616:18: note: previous declaration of ‘getline’ was here
  616 | extern __ssize_t getline (char **__restrict __lineptr,

(This was Bug #549426 fixed in version 3.22-18).

In such case this is enough to get rid of such error:

git show 2df8bdb0d2557d6cdc7632e | patch -p1


Now the bad news:

According to my tests, this commit, tagged v3.23pre, is already buggy:

commit 98ca67898b3f38ea09f1a0d1119d0794c044f9b6 (HEAD, tag: v3.23pre)
Author: Philip Guenther 
Date:   Tue Nov 1 03:15:48 2005 +

Fixed properties

The previous commit is huge and it's already buggy:

commit 5281aac102d92966c5963ea8694d95e4f1103747
Author: Philip Guenther 
Date:   Tue Nov 1 01:44:56 2005 +

Various fixes.

[lots of stuff]


And finally, the commit before that makes this simple command

echo "Subject: thesubject" | formail  | procmail

to take some time to return (locking problems?) and
the log output on procmail.log is like this:

procmail: [2243217] Tue Feb 14 21:04:28 2023
procmail: Assigning "SUBJECT="
procmail: [2243217] Tue Feb 14 21:04:28 2023
procmail: Executing "formail -cXSubject:|cat"
procmail: Out of memory
buffer 0: "formail -cXSubject:|cat"
buffer 1: "formail -cXSubject:|cat"
procmail: Notified comsat: "bluser@:**Bounced**"
From foo@bar  Tue Feb 14 21:04:28 2023
  Folder: **Bounced** 0

Because there is not a MYVAR= line, I'm not even able
to tell if this is also buggy or not.

So, to summarize: I still need help to fix this...

Thanks.

Bug#1031310: git: CVE-2023-22490 CVE-2023-23946

[Salvatore Bonaccorso]

Source: git
Version: 1:2.30.2-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:2.39.1-0.1

Hi,

The following vulnerabilities were published for git.

CVE-2023-22490[0] and CVE-2023-23946[1].

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-22490
https://www.cve.org/CVERecord?id=CVE-2023-22490
[1] https://security-tracker.debian.org/tracker/CVE-2023-23946
https://www.cve.org/CVERecord?id=CVE-2023-23946
[2] https://www.openwall.com/lists/oss-security/2023/02/14/5

Regards,
Salvatore

Processed: git: CVE-2023-22490 CVE-2023-23946

[Debian Bug Tracking System]

Processing control commands:

> found -1 1:2.39.1-0.1
Bug #1031310 [src:git] git: CVE-2023-22490 CVE-2023-23946
Marked as found in versions git/1:2.39.1-0.1.

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

Bug#1031309: accountsservice: accounts-daemon service will prevent system boot if shadowconfig is off

[john amidon]

Package: accountsservice
Version: 22.08.8-5
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: jami...@helixinnovations.io

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I set shadowconfig to 'off' when I edited '/etc/group' and forgot to reset it.
Sometime later, I ran 'apt upgrade', rebooted, and found that the boot did not
complete, complaining about accounts-daemon.service not starting.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
booted into recovery mode, looked at journal and discovered that 'shadowconfig'
was set to 'off' and re-enabled it

   * What was the outcome of this action?
machine successfully rebooted


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

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

Versions of packages accountsservice depends on:
ii  dbus [default-dbus-system-bus]  1.14.6-1
ii  libaccountsservice0 22.08.8-5
ii  libc6   2.36-8
ii  libglib2.0-02.74.5-1
ii  libpolkit-gobject-1-0   122-3

Versions of packages accountsservice recommends:
ii  libpam-systemd [logind]  252.5-2
ii  polkitd  122-3

Versions of packages accountsservice suggests:
ii  gnome-control-center  1:43.2-2

-- no debconf information

Bug#1031308: redmine FTBFS: test failure

[Adrian Bunk]

Source: redmine
Version: 5.0.4-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=redmine=all

...
PARALLEL_WORKERS=2 bin/rake test RAILS_ENV=test
sh: 1: gs: not found
(GhostScript convert not available)
Bazaar test repository NOT FOUND. Skipping functional tests !!!
CVS test repository NOT FOUND. Skipping functional tests !!!
Filesystem test repository NOT FOUND. Skipping functional tests !!!
Git test repository NOT FOUND. Skipping functional tests !!!
Mercurial test repository NOT FOUND. Skipping functional tests !!!
Subversion test repository NOT FOUND. Skipping functional tests !!!
Git test repository NOT FOUND. Skipping integration tests !!!
(Test LDAP server not configured)
Bazaar test repository NOT FOUND. Skipping unit tests !!!
Cvs test repository NOT FOUND. Skipping unit tests !!!
Filesystem test repository NOT FOUND. Skipping unit tests !!! See 
doc/RUNNING_TESTS.
Git test repository NOT FOUND. Skipping unit tests !!!
Mercurial test repository NOT FOUND. Skipping unit tests !!!
Subversion test repository NOT FOUND. Skipping unit tests !!!
Bazaar test repository NOT FOUND. Skipping unit tests !!!
CVS test repository NOT FOUND. Skipping unit tests !!!
Filesystem test repository NOT FOUND. Skipping unit tests !!! See 
doc/RUNNING_TESTS.
Git test repository NOT FOUND. Skipping unit tests !!!
Git UTF-8 test repository NOT FOUND. Skipping unit tests !!!
Mercurial test repository NOT FOUND. Skipping unit tests !!!
Subversion test repository NOT FOUND. Skipping unit tests !!!
Skipping LDAP tests.
Run options: --seed 22796

# Running:

..SSSE

Error:
Redmine::PluginLoaderTest#test_mirror_assets:
RuntimeError: Could not copy 
/<>/test/fixtures/plugins/foo_plugin/assets/stylesheets/foo.css to 
/<>/tmp/public/plugin_assets/foo_plugin/stylesheets/foo.css: No 
such file or directory @ rb_sysopen - 
/<>/tmp/public/plugin_assets/foo_plugin/stylesheets/foo.css
lib/redmine/plugin_loader.rb:71:in `rescue in block in mirror_assets'
lib/redmine/plugin_loader.rb:66:in `block in mirror_assets'
lib/redmine/plugin_loader.rb:65:in `each'
lib/redmine/plugin_loader.rb:65:in `mirror_assets'
lib/redmine/plugin_loader.rb:143:in `each'
lib/redmine/plugin_loader.rb:143:in `mirror_assets'
test/unit/lib/redmine/plugin_loader_test.rb:45:in `test_mirror_assets'

rails test test/unit/lib/redmine/plugin_loader_test.rb:44

(Ghostscript
 not available)

Processed: ruby-oj: buf.h #includes mem.h that is not shipped

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:ruby-oj-introspect
Bug #1031307 [ruby-oj] ruby-oj: buf.h #includes mem.h that is not shipped
Added indication that 1031307 affects src:ruby-oj-introspect

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

Bug#1031307: ruby-oj: buf.h #includes mem.h that is not shipped

[Adrian Bunk]

Package: ruby-oj
Version: 3.14.1-3
Severity: serious
Tags: ftbfs
Control: affects -1 src:ruby-oj-introspect

https://buildd.debian.org/status/fetch.php?pkg=ruby-oj-introspect=armhf=0.7.1-3=1676220273=0

...
In file included from /usr/include/ruby-3.1.0/vendor_ruby/oj/parser.h:10,
 from introspect.c:3:
/usr/include/ruby-3.1.0/vendor_ruby/oj/buf.h:8:10: fatal error: mem.h: No such 
file or directory
8 | #include "mem.h"
  |  ^~~
...

Bug#1026563: marked as done (aioxmlrpc: FTBFS: AttributeError: module 'asyncio' has no attribute 'coroutine'. Did you mean: 'coroutines'?)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 19:49:16 +
with message-id 
and subject line Bug#1026563: fixed in aioxmlrpc 0.6.4-1
has caused the Debian Bug report #1026563,
regarding aioxmlrpc: FTBFS: AttributeError: module 'asyncio' has no attribute 
'coroutine'. Did you mean: 'coroutines'?
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config 
> running config
> I: pybuild base:240: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_aioxmlrpc/build/aioxmlrpc
> copying aioxmlrpc/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_aioxmlrpc/build/aioxmlrpc
> copying aioxmlrpc/client.py -> 
> /<>/.pybuild/cpython3_3.11_aioxmlrpc/build/aioxmlrpc
> creating 
> /<>/.pybuild/cpython3_3.11_aioxmlrpc/build/aioxmlrpc/tests
> copying aioxmlrpc/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_aioxmlrpc/build/aioxmlrpc/tests
> copying aioxmlrpc/tests/test_client.py -> 
> /<>/.pybuild/cpython3_3.11_aioxmlrpc/build/aioxmlrpc/tests
> running egg_info
> writing aioxmlrpc.egg-info/PKG-INFO
> writing dependency_links to aioxmlrpc.egg-info/dependency_links.txt
> writing requirements to aioxmlrpc.egg-info/requires.txt
> writing top-level names to aioxmlrpc.egg-info/top_level.txt
> reading manifest file 'aioxmlrpc.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.pyc' found under directory 
> '.'
> adding license file 'LICENSE'
> writing manifest file 'aioxmlrpc.egg-info/SOURCES.txt'
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_aioxmlrpc/build/aioxmlrpc
> copying aioxmlrpc/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_aioxmlrpc/build/aioxmlrpc
> copying aioxmlrpc/client.py -> 
> /<>/.pybuild/cpython3_3.10_aioxmlrpc/build/aioxmlrpc
> creating 
> /<>/.pybuild/cpython3_3.10_aioxmlrpc/build/aioxmlrpc/tests
> copying aioxmlrpc/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_aioxmlrpc/build/aioxmlrpc/tests
> copying aioxmlrpc/tests/test_client.py -> 
> /<>/.pybuild/cpython3_3.10_aioxmlrpc/build/aioxmlrpc/tests
> running egg_info
> writing aioxmlrpc.egg-info/PKG-INFO
> writing dependency_links to aioxmlrpc.egg-info/dependency_links.txt
> writing requirements to aioxmlrpc.egg-info/requires.txt
> writing top-level names to aioxmlrpc.egg-info/top_level.txt
> reading manifest file 'aioxmlrpc.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.pyc' found under directory 
> '.'
> adding license file 'LICENSE'
> writing manifest file 'aioxmlrpc.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py test 
> running test
> WARNING: Testing via this command is deprecated and will be removed in a 
> future version. Users looking for a generic test entry point independent of 
> test runner are encouraged to use tox.
> running egg_info
> writing aioxmlrpc.egg-info/PKG-INFO
> writing dependency_links to aioxmlrpc.egg-info/dependency_links.txt
> writing requirements to aioxmlrpc.egg-info/requires.txt
> writing top-level names to aioxmlrpc.egg-info/top_level.txt
> reading manifest file 'aioxmlrpc.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no previously-included files matching '*.pyc' found under directory 
> '.'
> adding license file 'LICENSE'
> writing manifest file 'aioxmlrpc.egg-info/SOURCES.txt'
> running build_ext
> Traceback (most recent call last):
>   File "/<>/setup.py", line 28, in 
> setup(name=NAME,
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>^
>   File 

Bug#1031306: rust-criterion: autopkgtest regression

[Adrian Bunk]

Source: rust-criterion
Version: 0.4.0-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-criterion/31329906/log.gz

...
error[E0004]: non-exhaustive patterns: `Some(BytesDecimal(_))` not covered
  --> src/csv_report.rs:36:55
   |
36 | let (throughput_num, throughput_type) = match id.throughput {
   |   ^ 
pattern `Some(BytesDecimal(_))` not covered
   |
note: `std::option::Option` defined here
   = note: the matched value is of type `std::option::Option`
help: ensure that all possible cases are being handled by adding a match arm 
with a wildcard pattern or an explicit pattern as shown
   |
39 ~ None => (None, None),
40 ~ Some(BytesDecimal(_)) => todo!(),
   |

For more information about this error, try `rustc --explain E0004`.
error: could not compile `criterion` due to previous error
...
autopkgtest [01:29:46]:  summary
rust-criterion-0.4:@ FAIL non-zero exit status 101
rust-criterion-0.4:cargo_bench_support PASS
rust-criterion-0.4:csv_output FAIL non-zero exit status 101
rust-criterion-0.4:default PASS
rust-criterion-0.4:html_reports PASS
rust-criterion-0.4:  PASS
rust-criterion-0.4:async_futures PASS
rust-criterion-0.4:async_smol PASS
rust-criterion-0.4:async_std PASS
rust-criterion-0.4:async_tokio PASS
rust-criterion-0.4:stable FAIL non-zero exit status 101

Bug#1031305: libhttp-daemon-ssl-perl: autopkgtest regression with libio-socket-ssl-perl_2.081-2

[Adrian Bunk]

Source: libhttp-daemon-ssl-perl
Version: 1.05-01-4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/libh/libhttp-daemon-ssl-perl/31328850/log.gz

...
t/testmodule.t .. 
1..14
ok #authority certificate generated 1
ok #server certificate generated 2
ok #authority certificate saved 3
ok #server certificate saved 4
ok #server key saved 5
ok #server init port=43389 6
ok #server fileno 7
ok #server url test 8
ok #client bad connection test 7
ok #bad request handled 9
Use of uninitialized value $2 in concatenation (.) or string at 
/usr/share/perl5/IO/Socket/SSL.pm line 792.
ok #client good connection test 8
ok #valid request handled 10
ok #server method processing 11
ok #client permission test 9
ok
All tests successful.
Files=3, Tests=37,  2 wallclock secs ( 0.01 usr  0.00 sys +  1.41 cusr  0.05 
csys =  1.47 CPU)
Result: PASS
autopkgtest [00:12:47]: test autodep8-perl-build-deps: ---]
autopkgtest [00:12:47]: test autodep8-perl-build-deps:  - - - - - - - - - - 
results - - - - - - - - - -
autodep8-perl-build-deps FAIL stderr: Use of uninitialized value $2 in 
concatenation (.) or string at /usr/share/perl5/IO/Socket/SSL.pm line 792.
...
autopkgtest [00:13:17]:  summary
autodep8-perl-build-deps FAIL stderr: Use of uninitialized value $2 in 
concatenation (.) or string at /usr/share/perl5/IO/Socket/SSL.pm line 792.
autodep8-perlPASS (superficial)
autodep8-perl-recommends PASS (superficial)

Processed: found 1031290 in 3:3.2.17-1

[Debian Bug Tracking System]

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

> found 1031290 3:3.2.17-1
Bug #1031290 {Done: Chris Lamb } [python-django] 
python-django: CVE-2023-24580 (denial-of-service vulnerability in file uploads)
There is no source info for the package 'python-django' at version '3:3.2.17-1' 
with architecture ''
Unable to make a source version for version '3:3.2.17-1'
Marked as found in versions 3:3.2.17-1.
> thanks
Stopping processing here.

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

Bug#1031303: silver-platter: autopkgtest regression

[Adrian Bunk]

Source: silver-platter
Version: 0.5.6-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/s/silver-platter/31340548/log.gz

...
==
ERROR: tests (unittest.loader._FailedTest.tests)
--
ImportError: Failed to import test module: tests
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 154, in loadTestsFromName
module = __import__(module_name)
 ^^^
ModuleNotFoundError: No module named 'silver_platter.tests'


--
Ran 1 test in 0.000s

FAILED (errors=1)
autopkgtest [07:13:29]: test testsuite: ---]
autopkgtest [07:13:30]: test testsuite:  - - - - - - - - - - results - - - - - 
- - - - -
testsuiteFAIL non-zero exit status 1

Bug#1031302: devscripts FTBFS with black 23.1.0

[Adrian Bunk]

Source: devscripts
Version: 2.23.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=devscripts=s390x=2.23.1=1676400700=0
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/devscripts.html

...
==
FAIL: test_black (devscripts.test.test_black.BlackTestCase.test_black)
Test: Run black code formatter on Python source code.
--
Traceback (most recent call last):
  File "/build/1st/devscripts-2.23.1/scripts/devscripts/test/test_black.py", 
line 43, in test_black
self.fail(
AssertionError: black found code that needs reformatting:
--- wrap-and-sort   2023-02-04 23:33:58 +
+++ wrap-and-sort   2024-03-19 01:21:02.603765 +
@@ -193,11 +193,10 @@
 return True
 return False
 
 
 class InstallContent:
-
 __slots__ = ("content", "comments")
 
 def __init__(self, content, comments=None):
 self.content = content
 self.comments = comments
--- sadt2023-02-04 23:33:58 +
+++ sadt2024-03-19 01:21:02.593172 +
@@ -129,11 +129,10 @@
 def close(self):
 pass
 
 
 class DefaultProgress(Progress):
-
 _hourglass = r"/-\|"
 
 def __init__(self):
 self._counter = 0
 self._output = False
--- debootsnap  2023-02-04 23:33:58 +
+++ debootsnap  2024-03-19 01:21:02.985582 +
@@ -652,11 +652,10 @@
 for source in sources:
 print(source.deb_line(), end="")
 sys.exit(0)
 
 with tempfile.TemporaryDirectory() as tmpdirname:
-
 download_packages(tmpdirname, sources, pkgs, nativearch, foreignarches)
 
 create_repo(tmpdirname, pkgs)
 
 newpkgs = run_mmdebstrap(

--
Ran 17 tests in 37.834s

FAILED (failures=1)
Test failed: 
error: Test failed: 
make[3]: *** [Makefile:103: test_py] Error 1

Bug#1031299: r-cran-ggalluvial: autopkgtest regression

[Adrian Bunk]

Source: r-cran-ggalluvial
Version: 0.12.4-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-ggalluvial/31321147/log.gz

...
══ Failed tests 
── Error ('test-stat-flow.r:10'): `stat_flow` weights computed variables but 
drops weight ──
Error in `summarise(.tbl, !!!funs)`: Problem while computing `lode = (function 
(x, order_by = NULL, default =
NULL, na_rm = FALSE) ...`.
ℹ The error occurred in group 1: alluvium = 1, x = 1, yneg = FALSE, stratum =
  "B", deposit = 1, fissure = 1, link = 1, flow = from, adj_deposit = 1.1.3,
  adj_fissure = 1.1.1.
Caused by error in `nth()`:
! unused argument (na_rm = na_rm)
Backtrace:
 ▆
  1. ├─base::as.data.frame(StatFlow$compute_panel(data)) at 
test-stat-flow.r:10:2
  2. ├─StatFlow$compute_panel(data)
  3. │ └─ggalluvial (local) compute_panel(..., self = self)
  4. │   └─dplyr::summarize_at(data, "lode", distill)
  5. │ ├─dplyr::summarise(.tbl, !!!funs)
  6. │ └─dplyr:::summarise.grouped_df(.tbl, !!!funs)
  7. │   └─dplyr:::summarise_cols(.data, dplyr_quosures(...), caller_env = 
caller_env())
  8. │ ├─base::withCallingHandlers(...)
  9. │ └─dplyr:::map(quosures, summarise_eval_one, mask = mask)
 10. │   └─base::lapply(.x, .f, ...)
 11. │ └─dplyr (local) FUN(X[[i]], ...)
 12. │   └─mask$eval_all_summarise(quo)
 13. ├─dplyr (local) ``(lode)
 14. └─base::.handleSimpleError(...)
 15.   └─dplyr (local) h(simpleError(msg, call))
 16. └─rlang::abort(bullets, call = error_call, parent = 
skip_internal_condition(e))
── Error ('test-stat-flow.r:28'): `stat_flow` orders flows correctly with 
negative values ──
Error in `summarise(.tbl, !!!funs)`: Problem while computing `lode = (function 
(x, order_by = NULL, default =
NULL, na_rm = FALSE) ...`.
ℹ The error occurred in group 1: alluvium = 1, x = 1, yneg = FALSE, stratum =
  "A", deposit = 2, fissure = 1, link = 1, flow = from, adj_deposit = 1.2.3,
  adj_fissure = 1.1.1.
Caused by error in `nth()`:
! unused argument (na_rm = na_rm)
Backtrace:
 ▆
  1. ├─StatFlow$compute_panel(data) at test-stat-flow.r:28:2
  2. │ └─ggalluvial (local) compute_panel(..., self = self)
  3. │   └─dplyr::summarize_at(data, "lode", distill)
  4. │ ├─dplyr::summarise(.tbl, !!!funs)
  5. │ └─dplyr:::summarise.grouped_df(.tbl, !!!funs)
  6. │   └─dplyr:::summarise_cols(.data, dplyr_quosures(...), caller_env = 
caller_env())
  7. │ ├─base::withCallingHandlers(...)
  8. │ └─dplyr:::map(quosures, summarise_eval_one, mask = mask)
  9. │   └─base::lapply(.x, .f, ...)
 10. │ └─dplyr (local) FUN(X[[i]], ...)
 11. │   └─mask$eval_all_summarise(quo)
 12. ├─dplyr (local) ``(lode)
 13. └─base::.handleSimpleError(...)
 14.   └─dplyr (local) h(simpleError(msg, call))
 15. └─rlang::abort(bullets, call = error_call, parent = 
skip_internal_condition(e))
── Error ('test-stat-flow.r:56'): `stat_flow` orders alluvia correctly 
according to `aes.bind` ──
Error in `summarise(.tbl, !!!funs)`: Problem while computing `lode = (function 
(x, order_by = NULL, default =
NULL, na_rm = FALSE) ...`.
ℹ The error occurred in group 1: alluvium = 1, x = 1, yneg = FALSE, stratum =
  "A", deposit = 2, fissure = -2, link = 1, flow = from, adj_deposit = 1.2.4,
  adj_fissure = 1.-2.-2.
Caused by error in `nth()`:
! unused argument (na_rm = na_rm)
Backtrace:
 ▆
  1. ├─StatFlow$compute_panel(data) at test-stat-flow.r:56:2
  2. │ └─ggalluvial (local) compute_panel(..., self = self)
  3. │   └─dplyr::summarize_at(data, "lode", distill)
  4. │ ├─dplyr::summarise(.tbl, !!!funs)
  5. │ └─dplyr:::summarise.grouped_df(.tbl, !!!funs)
  6. │   └─dplyr:::summarise_cols(.data, dplyr_quosures(...), caller_env = 
caller_env())
  7. │ ├─base::withCallingHandlers(...)
  8. │ └─dplyr:::map(quosures, summarise_eval_one, mask = mask)
  9. │   └─base::lapply(.x, .f, ...)
 10. │ └─dplyr (local) FUN(X[[i]], ...)
 11. │   └─mask$eval_all_summarise(quo)
 12. ├─dplyr (local) ``(lode)
 13. └─base::.handleSimpleError(...)
 14.   └─dplyr (local) h(simpleError(msg, call))
 15. └─rlang::abort(bullets, call = error_call, parent = 
skip_internal_condition(e))
── Error ('test-stat-flow.r:78'): `stat_flow` preserves missingness to position 
flows ──
Error in `summarise(.tbl, !!!funs)`: Problem while computing `lode = (function 
(x, order_by = NULL, default =
NULL, na_rm = FALSE) ...`.
ℹ The error occurred in group 1: alluvium = 1, x = 1, yneg = FALSE, stratum =
  A, deposit = 1, fissure = 1, link = 1, flow = from, adj_deposit = 1.1.3,
  adj_fissure = 1.1.1.
Caused by error in `nth()`:
! unused argument (na_rm = na_rm)
Backtrace:
 ▆
  1. ├─StatFlow$compute_panel(data) at test-stat-flow.r:78:2
  2. │ └─ggalluvial (local) compute_panel(..., self = self)
  3. │   └─dplyr::summarize_at(data, "lode", distill)
  4. │ 

Bug#1031297: diffoscope: autopkgtest regression due to unavailable Recommends on several architectures

[Adrian Bunk]

Source: diffoscope
Version: 235
Severity: serious

Issues preventing migration:
∙ ∙ autopkgtest for diffoscope/235: amd64: Pass, arm64: Pass, armel: Regression 
♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), 
s390x: Regression ♻ (reference ♻)


pytest-with-recommends FAIL badpkg
blame: diffoscope
badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.




aapt   | 1:10.0.0+r36-10 | unstable| amd64, arm64, armel, 
armhf, i386, mips64el, mipsel
dexdump| 11.0.0+r48-5  | unstable | amd64, arm64, armhf, i386

Bug#1018023: Update on this bug?

[Jose Antonio Jimenez Madrid]

Thanks Matthew for the links.

I will test this patch and let you to know whether the bug is fixed.

Sincerely,
Jose

Matthew Vernon wrote:
> Hi,
>
> Do you have plans to fix this before the bookworm freeze, please?
>
> I think netbsd at least have patched eterm to work with the newer
> imlib; at least per the comment here
> https://github.com/mej/Eterm/issues/4
>
> That linked to
> http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/x11/eterm/patches/
>
> Which has a couple of patches that seem like they'd do the trick...
>
> Thanks,
>
> Matthew

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 12:34 -0500 schrieb Theodore Ts'o:
> 
[..]
> In any case, a version of grub that will support the csum_seed feature
> will be landing in Bookworm in just a few days.  So at that point,
> you'll be able to create VM images for Bookworm and Sid that will work
> with the e2fsprogs in sid.  The current plan of record is that it will
> only be at that point that e2fsprogs will be allowed to migrate into
> Bookworm.

As soon as this version hits testing, you have successfully disabled
the last working environment to use vmdb2 to create images of Ubuntu
and Debian. As soon as this version hits Testing, one then can no
longer build images for either any Ubuntu release nor Debian Bullseye
or older. I can then only build images for Bookworm and Sid. Please
think about that.

You *seriously* break the debootstrap method of installing Debian or
Ubuntu. vmdb2 ist just another tool that is broken by now, a tool that
I use very often. I explained the impacts of what you are doing often
enough now. By now the impact should be clear. And you are still not
dealing with the aftermath of your intended action?! You haven't done a
proper transition. You haven't given any affected toolchain the
necessary time to adopt. You haven't documented how to disable that
breaking change when creating filesystems for distributions where grub
does not support this (there is not even a NEWS entry). You haven't
even announced that breaking change. And yet you are going to break one
of our two standard methods of installing Debian or Ubuntu. How is any
of what you have been saying so far addressing any of these issues? 

> [..]
> By the way, in the case of the csum_seed feature, it's pretty
> straightforward to just run "tune2fs -O ^metadata_csum_seed
> /tmp/boot.img".  If the UUID has been changed since the file system
> was created, you'll have to do this while the file system is
> unmounted
> and it will take a few seconds, but that's almost certainly not the
> case with vmdb2.

Well, how do you intend to distribute that information, so people who
have to use the deboostrap method to install a Debian or Ubuntu release
with a grub not supporting csum_seed (basically all existing releases,
except for the upcoming Bookworm) know that?

I do not understand why you are pushing 1.47.0 over 1.46.6, which you
had uploaded just five days before the former. You haven't even
presented a reason yet.

Regards, Daniel

Bug#1031296: sccache FTBFS (on non-i386 32bit?)

[Adrian Bunk]

Source: sccache
Version: 0.4.0~~pre7-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=sccache=0.4.0%7E%7Epre7-1

...
[io-lifetimes 0.7.2] error[E0554]: `#![feature]` may not be used on the stable 
release channel
[io-lifetimes 0.7.2]  --> :1:1
[io-lifetimes 0.7.2]   |
[io-lifetimes 0.7.2] 1 | #![feature(rustc_attrs)]
[io-lifetimes 0.7.2]   | 
[io-lifetimes 0.7.2] 
[io-lifetimes 0.7.2] error: aborting due to previous error
[io-lifetimes 0.7.2] 
[io-lifetimes 0.7.2] For more information about this error, try `rustc 
--explain E0554`.
...

Bug#1031295: pcp fails to install without systemd

[Adrian Bunk]

Package: pcp
Version: 6.0.2-1
Severity: serious

https://piuparts.debian.org/sid/fail/pcp_6.0.2-1.log

...
Setting up pcp (6.0.2-1) ...
  /var/lib/dpkg/info/pcp.postinst: 242: systemctl: not found
  dpkg: error processing package pcp (--configure):
   installed pcp package post-installation script subprocess returned error 
exit status 127
  Processing triggers for libc-bin (2.36-8) ...
  Errors were encountered while processing:
   pcp
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Processed: python3-zstandard 0.19.0-3 supports only libzstd 1.5.2

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:libzstd src:rpmlint
Bug #1031293 [python3-zstandard] python3-zstandard 0.19.0-3 supports only 
libzstd 1.5.2
Added indication that 1031293 affects src:libzstd and src:rpmlint

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

Bug#1031293: python3-zstandard 0.19.0-3 supports only libzstd 1.5.2

[Adrian Bunk]

Package: python3-zstandard
Version: 0.19.0-3
Severity: serious
Control: affects -1 src:libzstd src:rpmlint

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-zstandard/31313975/log.gz

...
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/zstandard/__init__.py", line 39, in 

from .backend_c import *  # type: ignore

ImportError: zstd C API versions mismatch; Python bindings were not 
compiled/linked against expected zstd version (10504 returned by the lib, 10502 
hardcoded in zstd headers, 10502 hardcoded in the cext)
...


Due to
https://sources.debian.org/src/python-zstandard/0.19.0-3/c-ext/backend_c.c/#L155

Please remove this version check, it is not supportable and does not
seem to be necessary in practice:
https://github.com/indygreg/python-zstandard/commit/964141349479070486ea25253bd4cc106929b2fc
https://github.com/indygreg/python-zstandard/commit/a1c567edd15cb735f1ae8b91fd994db2fe39f19b

Bug#1031290: marked as done (python-django: CVE-2023-24580 (denial-of-service vulnerability in file uploads))

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 17:50:53 +
with message-id 
and subject line Bug#1031290: fixed in python-django 3:3.2.18-1
has caused the Debian Bug report #1031290,
regarding python-django: CVE-2023-24580 (denial-of-service vulnerability in 
file uploads)
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.)


-- 
1031290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1:1.11.29-1+deb10u6
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2023-24580[0]:

  Potential denial-of-service vulnerability in file uploads

  Passing certain inputs to multipart forms could result in too many
  open files or memory exhaustion, and provided a potential vector for
  a denial-of-service attack.

  The number of files parts parsed is now limited via the new
  DATA_UPLOAD_MAX_NUMBER_FILES setting.

  

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

For further information see:

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 3:3.2.18-1
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Feb 2023 09:12:57 -0800
Source: python-django
Built-For-Profiles: nocheck
Architecture: source
Version: 3:3.2.18-1
Distribution: unstable
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Chris Lamb 
Closes: 1031290
Changes:
 python-django (3:3.2.18-1) unstable; urgency=high
 .
   * New upstream security release:
 .
 - CVE-2023-24580: Potential denial-of-service vulnerability in file uploads
 .
   Passing certain inputs to multipart forms could result in too many open
   files or memory exhaustion, and provided a potential vector for a
   denial-of-service attack.
 .
   The number of files parts parsed is now limited via the new
   DATA_UPLOAD_MAX_NUMBER_FILES setting.
 .
   Thanks to Jakob Ackermann for the report. (Closes: #1031290)
Checksums-Sha1:
 698d15a21d198aa340fefd2ec158dbb0d17126d5 2807 python-django_3.2.18-1.dsc
 27010f09a149773fe9d19b6ee69c597a428fadc8 9848949 
python-django_3.2.18.orig.tar.gz
 9573bf6b748250469c6fd702dcabae574734fe6b 37760 
python-django_3.2.18-1.debian.tar.xz
 d794cd315ceeb8c2046109134695721dd6940594 7905 
python-django_3.2.18-1_amd64.buildinfo
Checksums-Sha256:
 9f1680ee17b33372ac8b399dd68859f54b96ed8545cb899d0cacc5a57de491f1 2807 
python-django_3.2.18-1.dsc
 08208dfe892eb64fff073ca743b3b952311104f939e7f6dae954fe72dcc533ba 9848949 
python-django_3.2.18.orig.tar.gz
 003420cd5c9f886e9bc2bf6675588e10023612f570ba74a6bba44ecc78a365ab 37760 
python-django_3.2.18-1.debian.tar.xz
 d5973ee8402bde6ca76f953c1290f60569536503154ed5732a449d54bb5c65cd 7905 
python-django_3.2.18-1_amd64.buildinfo
Files:
 c13581162bcd79ba9ff521b6a9dc5302 2807 python optional 
python-django_3.2.18-1.dsc
 03831fdb086d0efb7ba0b4e1c521427e 9848949 python optional 
python-django_3.2.18.orig.tar.gz
 c1f320d1824e8a58d06babfc4a4eab20 37760 python optional 
python-django_3.2.18-1.debian.tar.xz
 a69a8880f5d0510221817c178537 7905 python optional 
python-django_3.2.18-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAmPrwsIACgkQHpU+J9Qx
Hli0NxAAiHVkfBVXaz4hPKYq0McDwn5pX3/Fu5Ehtp/Aaa9Jh0rZeL0fStrq8EvT
ktGwx79qif1/m+OCqA5ktJPt0cSE6+hOLnX1hrl8Zs0lxDH5FsBdXgigund5jS0/

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Theodore Ts'o]

There is another issue with vmdb2 if you are using XFS.  Starting with
xfsprogs 5.15 (which is already in testing), bigtime is enabled by
default, so that newly created XFS file systems won't be subject to
timestamp overflow in 2038.  Grub didn't land support for this feature
until 8b1e5d1936ff ("fs/xfs: Add bigtime incompat feature support") in
May 2021, despite the fact that XFS has had this feature for years and
years and years.

So if you aren't using the latest security fixes, and you are using
XFS as the boot partition --- it won't work on buster and bullseye.
"Fortunately", there were were massive number security vulnerabilities
in grub2 which forced a backport of grub2 2.06 to bullseye and buster,
so if you have the security updates enabled, you'll probably be OK ---
but it was only because of massive number of security problems forced
that backport.


In any case, a version of grub that will support the csum_seed feature
will be landing in Bookworm in just a few days.  So at that point,
you'll be able to create VM images for Bookworm and Sid that will work
with the e2fsprogs in sid.  The current plan of record is that it will
only be at that point that e2fsprogs will be allowed to migrate into
Bookworm.

For slowly moving upstreams like grub2, distributions *have* to take
updates before grub2 finally gets around to doing a release --- to get
security fixes if nothing else!  The support for csum_seed has been in
Fedora and other distributions for a while, since the patches had
landed in grub2 in June 2021.  I probably should have made sure the
feature had landed in Debian's grub2 packaging earlier; that's my bad,
and my apologies for that.

Note that Debian's grub2 has well over 100 patches, nearly all of
which are backports from grub2's git repo.  So the argument that
"there doesn't exist a formally released grub2 release" isn't
particularly compelling, since all the distros are backporting
patches.  The only question is how *many* commits release has an
individual distribution taken.


By the way, in the case of the csum_seed feature, it's pretty
straightforward to just run "tune2fs -O ^metadata_csum_seed
/tmp/boot.img".  If the UUID has been changed since the file system
was created, you'll have to do this while the file system is unmounted
and it will take a few seconds, but that's almost certainly not the
case with vmdb2.

   - Ted

Bug#1031290: python-django: CVE-2023-24580 (denial-of-service vulnerability in file uploads)

[Chris Lamb]

Package: python-django
Version: 1:1.11.29-1+deb10u6
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2023-24580[0]:

  Potential denial-of-service vulnerability in file uploads

  Passing certain inputs to multipart forms could result in too many
  open files or memory exhaustion, and provided a potential vector for
  a denial-of-service attack.

  The number of files parts parsed is now limited via the new
  DATA_UPLOAD_MAX_NUMBER_FILES setting.

  

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

For further information see:

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#1028707: marked as done (python-mrcfile: FTBFS: AssertionError: ValueError not raised)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 16:37:42 +
with message-id 
and subject line Bug#1028707: fixed in python-mrcfile 1.4.3-3
has caused the Debian Bug report #1028707,
regarding python-mrcfile: FTBFS: AssertionError: ValueError not raised
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.)


-- 
1028707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mrcfile
Version: 1.4.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> Running Sphinx v5.3.0
> making output directory... done
> loading intersphinx inventory from https://docs.python.org/3.8/objects.inv...
> loading intersphinx inventory from https://numpy.org/doc/stable/objects.inv...
> building [mo]: targets for 0 po files that are out of date
> building [man]: all manpages
> updating environment: [new config] 4 added, 0 changed, 0 removed
> reading sources... [ 25%] index
> reading sources... [ 50%] readme
> reading sources... [ 75%] source/mrcfile
> reading sources... [100%] usage_guide
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> writing... mrcfile.1 { readme usage_guide source/mrcfile } done
> build succeeded.
> 
> The manual pages are in _build/man.
> Running Sphinx v5.3.0
> making output directory... done
> loading pickled environment... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 4 source files that are out of date
> updating environment: 0 added, 0 changed, 0 removed
> looking for now-outdated files... none found
> preparing documents... done
> writing output... [ 25%] index
> writing output... [ 50%] readme
> writing output... [ 75%] source/mrcfile
> writing output... [100%] usage_guide
> 
> generating indices... genindex py-modindex done
> writing additional pages... search done
> copying static files... done
> copying extra files... done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded.
> 
> The HTML pages are in _build/html.
> make[2]: Leaving directory '/<>/docs'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd 
> /<>/.pybuild/cpython3_3.10_mrcfile/build; tox -c 
> /<>/tox.ini --sitepackages -e py310 
> GLOB sdist-make: /<>/setup.py
> py310 create: /<>/.tox/py310
> py310 inst: /<>/.tox/.tmp/package/1/mrcfile-1.4.3.zip
> WARNING: Discarding $PYTHONPATH from environment, to override specify 
> PYTHONPATH in 'passenv' in your configuration.
> WARNING: Discarding $PYTHONPATH from environment, to override specify 
> PYTHONPATH in 'passenv' in your configuration.
> py310 installed: 
> alabaster==0.7.12,Babel==2.10.3,certifi==2022.9.24,chardet==5.1.0,charset-normalizer==3.0.1,distlib==0.3.6,docutils==0.17.1,filelock==3.9.0,idna==3.3,imagesize==1.4.1,Jinja2==3.0.3,MarkupSafe==2.1.1,mrcfile
>  @ 
> file:///<>/.tox/.tmp/package/1/mrcfile-1.4.3.zip,numpy==1.24.1,packaging==22.0,platformdirs==2.6.0,pluggy==1.0.0+repack,py==1.11.0,Pygments==2.14.0,pytz==2022.7,requests==2.28.1,roman==3.3,six==1.16.0,snowballstemmer==2.2.0,Sphinx==5.3.0,sphinx-rtd-theme==1.2.0rc1,tox==3.28.0,urllib3==1.26.12,virtualenv==20.17.1+ds
> py310 run-test-pre: PYTHONHASHSEED='1646220704'
> py310 run-test: commands[0] | python -m unittest tests
> ..FFFF..F..F.FF...F...
> ==
> FAIL: test_cannot_edit_extended_header_in_read_only_mode 
> (tests.test_bzip2mrcfile.Bzip2MrcFileTest)
> 

Bug#1030810: marked as done (django-sass-processor FTBFS: django.core.exceptions.ImproperlyConfigured)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 15:19:46 +
with message-id 
and subject line Bug#1030810: fixed in django-sass-processor 1.2.2+repack-1
has caused the Debian Bug report #1030810,
regarding django-sass-processor FTBFS: 
django.core.exceptions.ImproperlyConfigured
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.)


-- 
1030810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-sass-processor
Version: 1.2.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=django-sass-processor=all=1.2.2-1=1675788416=0

...
 ERRORS 
__ ERROR at setup of SassProcessorTest.test_management_command_django __

cls = 

@classmethod
def setUpClass(cls):
>   super().setUpClass()

/usr/lib/python3/dist-packages/django/test/testcases.py:1182: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/django/test/testcases.py:183: in setUpClass
cls._add_databases_failures()
/usr/lib/python3/dist-packages/django/test/testcases.py:204: in 
_add_databases_failures
cls.databases = cls._validate_databases()
/usr/lib/python3/dist-packages/django/test/testcases.py:190: in 
_validate_databases
if alias not in connections:
/usr/lib/python3/dist-packages/django/utils/connection.py:73: in __iter__
return iter(self.settings)
/usr/lib/python3/dist-packages/django/utils/functional.py:48: in __get__
res = instance.__dict__[self.name] = self.func(instance)
/usr/lib/python3/dist-packages/django/utils/connection.py:45: in settings
self._settings = self.configure_settings(self._settings)
/usr/lib/python3/dist-packages/django/db/utils.py:144: in configure_settings
databases = super().configure_settings(databases)
/usr/lib/python3/dist-packages/django/utils/connection.py:50: in 
configure_settings
settings = getattr(django_settings, self.settings_name)
/usr/lib/python3/dist-packages/django/conf/__init__.py:82: in __getattr__
self._setup(name)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = , name = 'DATABASES'

def _setup(self, name=None):
"""
Load the settings module pointed to by the environment variable. This
is used the first time settings are needed, if the user hasn't
configured settings manually.
"""
settings_module = os.environ.get(ENVIRONMENT_VARIABLE)
if not settings_module:
desc = ("setting %s" % name) if name else "settings"
>   raise ImproperlyConfigured(
"Requested %s, but settings are not configured. "
"You must either define the environment variable %s "
"or call settings.configure() before accessing settings."
% (desc, ENVIRONMENT_VARIABLE))
E   django.core.exceptions.ImproperlyConfigured: Requested setting 
DATABASES, but settings are not configured. You must either define the 
environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before 
accessing settings.

/usr/lib/python3/dist-packages/django/conf/__init__.py:63: ImproperlyConfigured
...
=== short test summary info 
ERROR 
tests/test_sass_processor.py::SassProcessorTest::test_management_command_django
ERROR 
tests/test_sass_processor.py::SassProcessorTest::test_management_command_jinja2
ERROR 
tests/test_sass_processor.py::SassProcessorTest::test_management_command_multiple
ERROR tests/test_sass_processor.py::SassProcessorTest::test_sass_processor - ...
ERROR tests/test_sass_processor.py::SassProcessorTest::test_sass_src_django
ERROR tests/test_sass_processor.py::SassProcessorTest::test_sass_src_jinja2
ERROR 
tests/test_sass_processor.py::SassProcessorTest::test_sass_src_jinja2_variable
ERROR tests/test_sass_processor.py::SassProcessorTest::test_use_storage_django
ERROR tests/test_sass_processor.py::SassProcessorTest::test_use_storage_jinja2
ERROR tests/test_sass_processor.py::SassProcessorTest::test_use_storage_multiple
 2 warnings, 10 errors in 1.39s 
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.11_django-sass-processor/build; python3.11 
-m pytest tests
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit 
code 13
make: *** [debian/rules:8: build-indep] Error 25
--- End Message ---
--- Begin Message 

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 14:58 + schrieb Steve McIntyre:
> On Tue, Feb 14, 2023 at 12:50:18PM +0100, Daniel Leidert wrote:
> 
> 
[..]
> Breakages happen like this,

This breakage is *unnecessary* and it breaks at the momnent *all*
debootstrap installations except for doing a bookworm/sid installation
themselves. That is just stupid.

Get down from your high horse and ackknowledge the problems your
behavior causes.

> and this has happened before in similar
> circumstances.

No it has not. You are doing a breakage on purpose during a freeze
period while the transition period is over. Do it with a proper
transition during the next release cycle.


> > 
[..]
> > Whe whole handling is completely wrong here. First, grub should have
> > been fixed upstream. And the change in e2fsprogs should have been done
> > only after "fixed" grub versions had settled. If we do it the other way
> > around, we have to patch grub in affected distributions as well. And
> > for Debian that means at least to patch Bullseye and any other release
> > we want to be able to install from Bookworm. I even a lot of companies
> > using Buster still.
> 
> And I know of folks still working on Stretch and Jessie. How far back
> do you want to tie things??

How about staying on topic and explaining, why this transition is
necessary and has to be done the wrong way around, instead of picking
the fact that older systems still exist? You break almost *all*
installation right now. You also broke an Ubuntu 20.04 or 22.04 LTS
installation. Are they new enough?

[..]
> > 
> > I'm critizicing the way of handling that breaking change and the
> > ignorance shown reagarding the impact, not that fact that there is a
> > breaking change. And it breaks a lot! This doesn't affect just a few
> > minor use cases. It affects the basic way of installing a clean Ubuntu
> > or Debian (or derivative) on a remote server using the debootstrap
> > method.
> 
> People using these tools need to be aware of the potential issue. What
> would happen if you ran debootstrap with a filesystem that the target
> distro doesn't know how to mount at all, for example?

That is different from introducing a breaking change for which no grub
upstream release has a fix yet. So basically the only system able to
handle a filesystem created with e2fsprogs 1.47.0 is Sid right now. Can
you please ignore your ego and see the problems you are causing?

You push a breaking change for no reason at all. What is the gain here
compared to the issues you are causing?

> > And again: We are in the middle of a freeze here. And e2fsprogs
> > pushes
> > a breaking change that is not even handled by any existing grub
> > upstream release, and is also not properly handled within Debian?!
> 
> Grub upstream is already known to be problematic in terms of release
> cycles.

That is not enough and it is not a solution for the problem. There is
*no* grub version out there supporting this, except for the patched
version is Sid. Is this the sign for a working transition?

> We now know about this particular issue (thanks Ted!) and
> we've fixed it in unstable (and soon testing).

Which helps exactly nobody, as it still breaks all other Debian or
Ubuntu installation.

I cannot belive that you intentionally break one of the standard
methods to install Debian or Ubuntu for no reason at all and without a
proper transition. Version 1.47.0 of e2fsprogs contains nothing
necessary for Bookworm. I'll bring this to the attention of the release
team. I'm sick of your ignorance. Do a proper transition and don't
start it during a freeze.


Daniel

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Steve McIntyre]

On Tue, Feb 14, 2023 at 12:50:18PM +0100, Daniel Leidert wrote:
>Am Dienstag, dem 14.02.2023 um 10:45 + schrieb Steve McIntyre:
>> On Tue, Feb 14, 2023 at 11:34:13AM +0100, Daniel Leidert wrote:
>> > Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
>> 
>> ...
>> 
>> > > But a generalized requirement that we be able to use debootstrap and
>> > > vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't
>> > > seem to be reasonable.
>> > 
>> > You are completyl wrong. This breaks a standard way of installing any
>> > system supported by deboostrap with a grub without a fix to deal with
>> > this version of e2fsprogs. This isn't just about vmdb2.
>> > 
>> > What you are saying is ignorant.
>> > 
>> > If this isn't cared about, then this version of e2fsprogs shouldn't
>> > make it into Bookworm. We are in the middle of a freeze and this breaks
>> > toolchains and a standard way (see [1]) of installing Debian.
>> 
>> Sorry Daniel, but I have to (mostly!) agree with Ted here. If you're
>> creating an image of an older release using newer tools then you'll
>> need to be aware that sometimes the newer tools will create things
>> that don't work there. If there's a bug here, I would strongly argue
>> that it's in vmdb2. deboostrap (for example) includes some
>> release-specific knowledge to cope with issues like this.
>
>debootstrap does nothing related to grub. So it is a bad example.

That's why I said *like* this, not *exactly* like this. debootstrap
has had knowledge of things like fs layouts etc. that older releases
need (e.g. merged-/usr).

>Again I refer to [1]: If the host system contains the problematic
>e2fsprogs and the target system doesn't contain a grub with the fix
>[2], then this breaks installations. This breaks older systems *and*
>current systems. For example, I neither see the necessary grub patch
>in both Ubuntu 20.04 and 22.04 either. So they also cannot be
>installed using the deboostrap method and the toolchain in Sid (and
>Bookworm if e2fsprogs makes it there).

Breakages happen like this, and this has happened before in similar
circumstances. If you're installing an older system using brand-new
tools, you need to be aware of the potential for things to not
work. In this particular case, all you need to do is tweak the flags
on the ext4 filesystem when you create it. This isn't that hard...

>[1] https://www.debian.org/releases/stable/amd64/apds03
>[2] Even "our" grub only contains a patch and not an upstream version
>with support. So how can you even expect the target system to contain a
>fix and be able to handle the created filesystem?!
>
>Whe whole handling is completely wrong here. First, grub should have
>been fixed upstream. And the change in e2fsprogs should have been done
>only after "fixed" grub versions had settled. If we do it the other way
>around, we have to patch grub in affected distributions as well. And
>for Debian that means at least to patch Bullseye and any other release
>we want to be able to install from Bookworm. I even a lot of companies
>using Buster still.

And I know of folks still working on Stretch and Jessie. How far back
do you want to tie things??

>> If we don't allow for this kind of change, that wouldn't allow us to
>> *ever* make breaking changes in some packages, and that's just not
>> sustainable.
>
>I'm critizicing the way of handling that breaking change and the
>ignorance shown reagarding the impact, not that fact that there is a
>breaking change. And it breaks a lot! This doesn't affect just a few
>minor use cases. It affects the basic way of installing a clean Ubuntu
>or Debian (or derivative) on a remote server using the debootstrap
>method.

People using these tools need to be aware of the potential issue. What
would happen if you ran debootstrap with a filesystem that the target
distro doesn't know how to mount at all, for example?

>And again: We are in the middle of a freeze here. And e2fsprogs pushes
>a breaking change that is not even handled by any existing grub
>upstream release, and is also not properly handled within Debian?!

Grub upstream is already known to be problematic in terms of release
cycles. We now know about this particular issue (thanks Ted!) and
we've fixed it in unstable (and soon testing).

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?

Bug#1031278: buddy: Contains non-source file

[Bastian Germann]

Source: buddy
Version: 2.4-11
Severity: serious

The doc/buddy.ps file contained in the package is not a source file.
Please repack to get rid of it or build it from source if it is available.

Bug#1030269: marked as done (freezer: python3 dependency issues)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 13:50:31 +
with message-id 
and subject line Bug#1030269: fixed in freezer 13.0.0-2
has caused the Debian Bug report #1030269,
regarding freezer: python3 dependency issues
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.)


-- 
1030269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freezer
Version: 13.0.0-1.1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

python3-freezer is an arch: all package that should work with all
versions of the python3 interpreter. Nevertheless, it currently has a
dependency on python3.10 (and rebuilding it produces one on python3.11).

So, freezer needs a sourceful upload for the python3.11-only transition.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: freezer
Source-Version: 13.0.0-2
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated freezer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Feb 2023 14:21:02 +0100
Source: freezer
Architecture: source
Version: 13.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1030269
Changes:
 freezer (13.0.0-2) unstable; urgency=medium
 .
   * Fix python3 shebang (Closes: #1030269).
Checksums-Sha1:
 3aac834db30395b2e0e3c91f75313fc1e522c789 2898 freezer_13.0.0-2.dsc
 9e61dae3898bb1ca501ccd5d63aa9a6f9ef04638 10136 freezer_13.0.0-2.debian.tar.xz
 d65317a53fbdd264a65e9b9e16ace10184e7b124 14242 freezer_13.0.0-2_amd64.buildinfo
Checksums-Sha256:
 700b74747027e3095ec32c6049b20ca94bc6a8cf2a6db6765de609a20c063702 2898 
freezer_13.0.0-2.dsc
 e69e3384b1c95202d119166f822a61923e48427468d8b706870f9a68c5e78360 10136 
freezer_13.0.0-2.debian.tar.xz
 c6e8aef1d0d1c9d7ce14118e625d5bfc770be83120660cc1cf17dd7cf18ca688 14242 
freezer_13.0.0-2_amd64.buildinfo
Files:
 e1b5ff0dfb6e79dcc37053e1cc73394d 2898 net optional freezer_13.0.0-2.dsc
 e85d5538afc3b2301767c81bcbd31d8a 10136 net optional 
freezer_13.0.0-2.debian.tar.xz
 4de430b6a8a7d6659f6565f2885ea7fa 14242 net optional 
freezer_13.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmPri50ACgkQ1BatFaxr
Q/5tGQ//frP7/bh77dT5nw+g1R+/18YraEBsYdMCDCC0rwhQCsst2057SWQ1aQMi
ne+5cUkhvsbdeskL0LKKhusTIin0Jq+QePR04eSx0+EtiYMoQS8xQkI9p3B64oPJ
8rT1n3FUhSBwtRy9IjLx8iV/cR6BknAff2Xy+GLQrOMdYK9KoH2/dsKTaJIek40r
SHoNPQ7me2neYYM9KYzBGDC//8PXc2pTwIawhZwpU02BYY9EWPMFpvxu6L1/mEFa
flKnEkwsve1K1O70cX5XoHmJs/JbL9FrWmJEXZlxjgMuiS/95aHN4MhbBAZjytSM
c06mPDWC7gjJBHZYNk/deDIJYjD1FVK47MXtFxnqWs42KXFXyWYuyHH52I8EAkL7
FCFzwP31SftnjSJDXx9US8KistTwBt8lslAYfpYcsGL5EXIH9IXeicZnn2mN9uSP
fiFFbWkbJu+BPnNW152JO0eS/v8/PZPowS4fN2O0jdtzkgsp8VTTPHHL/be5A1iV
asA/+4h0ILEWuzQmTxFtPUHQyF5X4E2H0jYs3XLytWAUcncUiwqbwj4Ldo28sXkX
07lYgF3kUGvlS/FWHukuU5p3rBoMlJI23UnFhgC3fuu5M8+3XPbWbCrw1gKKquPi
+nZjOIYszqx1e9anUiZgwp8SBUiigx7mV5h/1CUiAizjZX0juNk=
=5k5x
-END PGP SIGNATURE End Message ---

Processed: Bug#1031233: hplip: hp-plugin unable to download plugin

[Debian Bug Tracking System]

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

> Forwarded 1031233 https://bugs.launchpad.net/hplip/+bug/2003739
Bug #1031233 [hplip] hplip: hp-plugin unable to download plugin
Set Bug forwarded-to-address to 'https://bugs.launchpad.net/hplip/+bug/2003739'.
> tags 1031233 upstream
Bug #1031233 [hplip] hplip: hp-plugin unable to download plugin
Ignoring request to alter tags of bug #1031233 to the same tags previously set
> severity 1031233 important
Bug #1031233 [hplip] hplip: hp-plugin unable to download plugin
Severity set to 'important' from 'grave'
> merge 1031233 1029459
Bug #1031233 [hplip] hplip: hp-plugin unable to download plugin
Bug #1029459 [hplip] hp-plugin crashes when trying to download plugin with 
error NameError: name 'get_distro_std_name' is not defined. Did you mean: 
'get_distro_name'?
Merged 1029459 1031233
> thanks
Stopping processing here.

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

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Dienstag, dem 14.02.2023 um 10:45 + schrieb Steve McIntyre:
> On Tue, Feb 14, 2023 at 11:34:13AM +0100, Daniel Leidert wrote:
> > Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
> 
> ...
> 
> > > But a generalized requirement that we be able to use debootstrap and
> > > vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't
> > > seem to be reasonable.
> > 
> > You are completyl wrong. This breaks a standard way of installing any
> > system supported by deboostrap with a grub without a fix to deal with
> > this version of e2fsprogs. This isn't just about vmdb2.
> > 
> > What you are saying is ignorant.
> > 
> > If this isn't cared about, then this version of e2fsprogs shouldn't
> > make it into Bookworm. We are in the middle of a freeze and this breaks
> > toolchains and a standard way (see [1]) of installing Debian.
> 
> Sorry Daniel, but I have to (mostly!) agree with Ted here. If you're
> creating an image of an older release using newer tools then you'll
> need to be aware that sometimes the newer tools will create things
> that don't work there. If there's a bug here, I would strongly argue
> that it's in vmdb2. deboostrap (for example) includes some
> release-specific knowledge to cope with issues like this.

debootstrap does nothing related to grub. So it is a bad example. Again
I refer to [1]: If the host system contains the problematic e2fsprogs
and the target system doesn't contain a grub with the fix [2], then
this breaks installations. This breaks older systems *and* current
systems. For example, I neither see the necessary grub patch in both
Ubuntu 20.04 and 22.04 either. So they also cannot be installed using
the deboostrap method and the toolchain in Sid (and Bookworm if
e2fsprogs makes it there). 

[1] https://www.debian.org/releases/stable/amd64/apds03
[2] Even "our" grub only contains a patch and not an upstream version
with support. So how can you even expect the target system to contain a
fix and be able to handle the created filesystem?!

Whe whole handling is completely wrong here. First, grub should have
been fixed upstream. And the change in e2fsprogs should have been done
only after "fixed" grub versions had settled. If we do it the other way
around, we have to patch grub in affected distributions as well. And
for Debian that means at least to patch Bullseye and any other release
we want to be able to install from Bookworm. I even a lot of companies
using Buster still.

> If we don't allow for this kind of change, that wouldn't allow us to
> *ever* make breaking changes in some packages, and that's just not
> sustainable.

I'm critizicing the way of handling that breaking change and the
ignorance shown reagarding the impact, not that fact that there is a
breaking change. And it breaks a lot! This doesn't affect just a few
minor use cases. It affects the basic way of installing a clean Ubuntu
or Debian (or derivative) on a remote server using the debootstrap
method.


And again: We are in the middle of a freeze here. And e2fsprogs pushes
a breaking change that is not even handled by any existing grub
upstream release, and is also not properly handled within Debian?!

Daniel

Processed: Re: Bug#1029238: imv not found in $PATH

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1029238 [imv] imv not found in $PATH
Severity set to 'normal' from 'grave'

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

Bug#1029238: imv not found in $PATH

[Petter Reinholdtsen]

Control: severity -1 normal

[Andreas Metzler]
> | Starting from upstream version 4.0.0 imv ships two binaries that
> | handle Wayland and X11 natively: imv-wayland and imv-x11. To allow
> | seamless usage to users upstream provides a /usr/bin/imv wrapper that
> | checks whether a Wayland compositor is available before running the
> | appropriate binary.
> 
> | The Debian package does not ship the wrapper script to avoid a file
> | name clash with the renameutils package.
> 
> Invoking either imv-wayland or imv-x11 should work perfectly fine on the
> commandline.

This sound like a normal or wishlist issue, not a grave error.  Reducing
severity accordingly.
-- 
Happy hacking
Petter Reinholdtsen

Bug#1030825: marked as done (less: CVE-2022-46663: -R filtering bypass)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 11:06:35 +
with message-id 
and subject line Bug#1030825: fixed in less 590-1.2
has caused the Debian Bug report #1030825,
regarding less: CVE-2022-46663: -R filtering bypass
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.)


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

Hi,

The following vulnerability was published for less. The severity is
set on purpose to RC level, as I think the issue might ideally be
fixed for the bookworm release in advance.

CVE-2022-46663[0]:
| less -R filtering bypass

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-46663
https://www.cve.org/CVERecord?id=CVE-2022-46663
[1] https://github.com/gwsw/less/commit/a78e1351113cef564d790a730d657a321624d79c
[2] https://www.openwall.com/lists/oss-security/2023/02/07/7

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: less
Source-Version: 590-1.2
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated less package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Feb 2023 11:17:35 +0100
Source: less
Architecture: source
Version: 590-1.2
Distribution: unstable
Urgency: medium
Maintainer: Milan Kupcevic 
Changed-By: Salvatore Bonaccorso 
Closes: 1030825
Changes:
 less (590-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * End OSC8 hyperlink on invalid embedded escape sequence (CVE-2022-46663)
 (Closes: #1030825)
Checksums-Sha1: 
 5904b57d7b395f88909fe15a8f68471df1de77ec 1944 less_590-1.2.dsc
 5b3fc4385707b16d1bc08b0c0748636df72e246e 20456 less_590-1.2.debian.tar.xz
Checksums-Sha256: 
 6290f5e8607fb61719d37a50c627fc25d96f8caf19502d7137ade61a1d56a0ef 1944 
less_590-1.2.dsc
 f4873578bec704987a6f22704453e2d8914c39fbc1d908853f074f5530f4aa3e 20456 
less_590-1.2.debian.tar.xz
Files: 
 523e53806203434c49e2b8e8a8b9ec6a 1944 text important less_590-1.2.dsc
 1cd3b776b36d35cc38427e599a7c0267 20456 text important 
less_590-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmPovS1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EiogP/R/kS/BRbicLM7vQ+ekh8NvSSBr9ztJB
3AKK9RQrXIh6SHojx2YovjDC5jRFYUPzERE5bnuHcY5zWiXkIuUlOsg9H/ahoUU0
Z+dMATiaowxhqfSq26g24X04CHcEIGGBYCXWoaMuhwmQSCOxal8mxBFbARG2tH6H
RD2TVi4Qb3phhx9uKNWX172PPvcX/tUSLoQt92V+GOPiRQ8eyf26hFR/eelLEJbe
Senhcyo13W5kSjwCyvcGJ2pzSGAKO11a45BECKAoiJFGiHhb0mznOTOMd3ePDL+7
mcEsyentenpgjN87DTmImYSBG20ANJW5Qdf0osutK7REF3G0R2zQz52TTFKG7upG
o8bOXudpB/hA/TuO/A24oHzX8TJSTWTuxlDFRY/O/sUWeER4KHglLAzvyoRRaQX5
0M/6aBVj++BIQmwHUpuv9B34Vx5Serp1RCeUUixQhASuup4tuKTHSVlm+RMsh+jf
+EyznTrk1vb1YkPOF/9FFlMQZrcdhIJNar+G44qAamqDU+PAfGq5i8YomN29hwL2
pWuhcfRaYLKrA0EZ3OKcTs2FsptQ/GYnq5fvLs0tV7jSiqc3U9oKejqz6ykc5M3G
3tgHm5gOWCEQSFWIfEbmtrcFubzLD7/oPRtEkosDoWQ4AFfYLc99vvkiAX/cLaCU
jamFeFq8Dhg2
=DKVg
-END PGP SIGNATURE End Message ---

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Steve McIntyre]

On Tue, Feb 14, 2023 at 11:34:13AM +0100, Daniel Leidert wrote:
>Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:

...

>> But a generalized requirement that we be able to use debootstrap and
>> vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't
>> seem to be reasonable.
>
>You are completyl wrong. This breaks a standard way of installing any
>system supported by deboostrap with a grub without a fix to deal with
>this version of e2fsprogs. This isn't just about vmdb2.
>
>What you are saying is ignorant.
>
>If this isn't cared about, then this version of e2fsprogs shouldn't
>make it into Bookworm. We are in the middle of a freeze and this breaks
>toolchains and a standard way (see [1]) of installing Debian.

Sorry Daniel, but I have to (mostly!) agree with Ted here. If you're
creating an image of an older release using newer tools then you'll
need to be aware that sometimes the newer tools will create things
that don't work there. If there's a bug here, I would strongly argue
that it's in vmdb2. deboostrap (for example) includes some
release-specific knowledge to cope with issues like this.

If we don't allow for this kind of change, that wouldn't allow us to
*ever* make breaking changes in some packages, and that's just not
sustainable.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
  Armed with "Valor": "Centurion" represents quality of Discipline,
  Honor, Integrity and Loyalty. Now you don't have to be a Caesar to
  concord the digital world while feeling safe and proud.

Bug#1027542: epl: FTBFS: make: *** [debian/rules:6: build] Error 25

[Adrian Bunk]

On Tue, Feb 14, 2023 at 12:30:59PM +0200, Adrian Bunk wrote:
> On Mon, Jan 02, 2023 at 08:14:55AM -0400, David Bremner wrote:
> > Lucas Nussbaum  writes:
> > 
> > > Source: epl
> > > Version: 0.9-5
> > > Severity: serious
> > > Justification: FTBFS
> > > Tags: bookworm sid ftbfs
> > > User: lu...@debian.org
> > > Usertags: ftbfs-20230101 ftbfs-bookworm
> > >
> > > Hi,
> > >
> > > During a rebuild of all packages in sid, your package failed to build
> > > on amd64.
> > >
> > 
> > This seems tricky to duplicate
> > 
> > - building on bare metal (sid/bookworm): works
> > - building in sbuild chroot by running dpkg-buildpackage: works
> > - building with sbuild: fails.
> > 
> > As a wild guess I tried adding
> > 
> >export EMACS_INHIBIT_AUTOMATIC_NATIVE_COMPILATION=t
> > 
> > to debian/rules, but it did not help.
> 
> FTR, the dates when epl started to FTBFS in sid and bookworm are
> a good match for when emacs 1:28.2+1-9 entered sid and bookworm:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/epl.html

Correct link:
https://tests.reproducible-builds.org/debian/history/epl.html

cu
Adrian

Processed: tagging 1031271

[Debian Bug Tracking System]

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

> tags 1031271 + experimental
Bug #1031271 [src:glib2.0] glib2.0 [experimental]: 2.75.3 FTBFS on big-endian
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#1030849: marked as done (CVE-2022-45142: accidental logic inversion in signature verification in gsskrb5)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 10:35:29 +
with message-id 
and subject line Bug#1030849: fixed in heimdal 7.8.git20221117.28daf24+dfsg-1.1
has caused the Debian Bug report #1030849,
regarding CVE-2022-45142: accidental logic inversion in signature verification 
in gsskrb5
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.)


-- 
1030849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: heimdal
Version: 7.8.git20221117.28daf24+dfsg-1
Severity: grave
Tags: upstream
Forwarded: https://www.openwall.com/lists/oss-security/2023/02/08/1

Hi,

Debian's heimdal is also vulnerable to CVE-2022-45142. Refer to the
openwall publication for details. Note that this vulnerability only
applies to heimdal's maintenance branches and never affected its main
development branch. It can be fixed either by applying the patch or by
moving to the development branch.

Salvatore will be issuing a DSA today. I'll be taking care of older
releases.

Helmut
--- End Message ---
--- Begin Message ---
Source: heimdal
Source-Version: 7.8.git20221117.28daf24+dfsg-1.1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated heimdal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 12 Feb 2023 10:35:50 +0100
Source: heimdal
Architecture: source
Version: 7.8.git20221117.28daf24+dfsg-1.1
Distribution: unstable
Urgency: high
Maintainer: Brian May 
Changed-By: Salvatore Bonaccorso 
Closes: 1030849
Changes:
 heimdal (7.8.git20221117.28daf24+dfsg-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * gsskrb5: fix accidental logic inversions (CVE-2022-45142)
 (Closes: #1030849)
Checksums-Sha1: 
 a2e3386514b1628ff23600cc499bae08a62120ce 3768 
heimdal_7.8.git20221117.28daf24+dfsg-1.1.dsc
 aeef2912fe240ec0e02d94053eebff50c5392a18 128292 
heimdal_7.8.git20221117.28daf24+dfsg-1.1.debian.tar.xz
Checksums-Sha256: 
 16f15d10f2f7d01c1faa7762b78837769a1809bfd9cb2d27209dbdb9f691b590 3768 
heimdal_7.8.git20221117.28daf24+dfsg-1.1.dsc
 1c4c939c8dfd178933c4bfc5cfd74e69ee56426397bbad5be9dd49c8553f56c9 128292 
heimdal_7.8.git20221117.28daf24+dfsg-1.1.debian.tar.xz
Files: 
 6ac87d6db307845b7238bd9c5a2722fc 3768 net optional 
heimdal_7.8.git20221117.28daf24+dfsg-1.1.dsc
 06107962acf0b28c057e4ba97d8603cd 128292 net optional 
heimdal_7.8.git20221117.28daf24+dfsg-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmPotjRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EMP8P/A1l7+4KeW0GifIQDgLSVc5dYXEzA5cN
/Rlrxbbv/eFIeKWO83qam1huN3B20+tsorNsgT0haDSwP8cUpKsYAHq2sOnbaxYs
UD3yRKD3OgXCiSE2kmydTOgUjwSBryivdr9N+42p75LfNaWVcrKamzyDpHs5MyhS
FuSzH8iFBWgS67rbw1ZlnYUwk7/eiGEYFzXiaHJXEgkItUoz7YbGL7nmZNrEiT3A
fo2r1clxe1LwPUUBtWAL4063nqAaiBVXtTr3eq9FZIKSW0NkA71k/tnEr5fSsKbh
CtmHMnrECDH4/jrfDN39+phAIu4uFzLQIqghl6Ib3HLYeOmcZqllv6XYMqo2jcar
Y9wUzABM4VNpx+UiAPuUB9NpriXTch+wBi/8AmRhmkTgYEoKL9/TTXyhK//4FN3d
KDNfPBmhngBzSk0eNit2fENlmTeIGer71dcUaXHObJb+bR+67+fQNpDUcKAWNEb+
mkG05iIFPUY+9xeUb1d6SHvnxu1oLnwFfzw9JEf965s1/LOhIMo2RwE/GqcqnxEr
I4h7PAPBxgxE4H4WIgjIjg1Y3h0z1e4uVvvjEMha9HtVeGMwC3g3VkJxyJc2ymme
acFhAmFjJNvH2Q2v5/qiEiCtv4WYLdZsN6UMjk4xu0w4CLyxivhCyXvBlmdxVq/W
rlTn/+5y7Wl9
=6WVQ
-END PGP SIGNATURE End Message ---

Processed: close

[Debian Bug Tracking System]

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

> close 1021643
Bug #1021643 [libamdhip64-5] libamdhip64-5: libamdhip64.so.5.2.21153- missing 
githash
Bug #1031252 [libamdhip64-5] hipsparse: FTBFS (c++: error: -E or -x required 
when input is from standard input)
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1030846: Bug#1030939: e2fsprogs: generates filesystems that grub-install doesn't recognize

[Daniel Leidert]

Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
> On Tue, Feb 14, 2023 at 01:01:38AM +0100, Daniel Leidert wrote:
> > Hi Steve,
> > 
> > I believe that your fix to grub2 in Sid is not enough to handle
> > #1030939/#1030846.
> > 
> > This problem breaks e.g. vmdb2. I can no longer create a Bullseye
> > system image with vmdb2 on Sid, because the grub-install step in the
> > Bullseye chroot now fails, because the created filesystem (created with
> > e2fsprogs on Sid) cannot be recognized by grub.
> 
> I'm confused, why does using vmdb2 on *sid* involve running
> grub-install on a *bulleye* chroot?

My workstation is running Sid. I want to create an image for Bullseye
(in this case using vmdb2, but I could do it manually as well). First,
one creates the paritioning and the filesystems for the target system
with the tools provided by the host system. This involves running the
unfortunate version of e2fsprogs with the breaking change. Then, one
installs the base system with deboostrap (also from the host system)
into the created partitions/filesystem. Then one (bind-)mounts the
virtual filesystems into the target systems, does a chroot into it, and
then one finishes the installation inside the chroot, including running
grub-install.

This is standard and common behavior. I have never ever seen in my
whole life someone to use grub2 from Sid to make a grub-install for a
Bullseye target. I have not even seen anybody suggest that.

Consider another example: Server providers use GRML or Bookworm with
e2fsprogs 1.47.0 as their rescue system. Now people are no longer able
to create a Bullseye system using the deboostrap method [1]. If the
host system uses e2fsprogs 1.47.0 or above and the target system for
[1] uses a grub without a fix, then this no longer works.

[1] https://www.debian.org/releases/stable/amd64/apds03

> That seems to be extremely ill-advised.

I'm sorry? I think you are completely missing the point.

> If you are trying to install a bullseye system, why
> can't you using vmdb2 on bullseye?

Because I am using Sid and because I use features of vmdb2 which are
not available in the version in Bullseye. And this feature breaks vmdb2
and similar tools. It also breaks a standard way of installing Debian
systems.

> And if you are trying to install a sid or bookworm system using vmdb2,
> why can't you (or vmdb2) use a sid or bookworm chroot for doing the
> grub-install?

What are you talking about? You basically break the toolchains and then
you suggest to do non-standard stuff to handle this or even avoid doing
installations of affected systems?!

> > I guess that the fix applied to grub2 in Sid would have to be applied
> > to grub2 in Bullseye as well (and basically to any grub2 package in any
> > Debian or Ubuntu or Raspbian release supported by debootstrap).
> 
> I can understand why we need to keep things synchronized so that a
> debian installer for Bookworm be able to generate a bootable system
> using the version of grub and e2fsprogs in Bookworm.
> 
> But a generalized requirement that we be able to use debootstrap and
> vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't
> seem to be reasonable.

You are completyl wrong. This breaks a standard way of installing any
system supported by deboostrap with a grub without a fix to deal with
this version of e2fsprogs. This isn't just about vmdb2.

What you are saying is ignorant.

If this isn't cared about, then this version of e2fsprogs shouldn't
make it into Bookworm. We are in the middle of a freeze and this breaks
toolchains and a standard way (see [1]) of installing Debian.

Daniel

Bug#1031271: glib2.0 [experimental]: 2.75.3 FTBFS on big-endian

[Simon McVittie]

Source: glib2.0
Version: 2.75.3-1
Severity: serious
Tags: ftbfs upstream pending
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://gitlab.gnome.org/GNOME/glib/-/issues/2918

See . I'm testing a
solution.

smcv

Processed: Re: Bug#1031252: hipsparse: FTBFS (c++: error: -E or -x required when input is from standard input)

[Debian Bug Tracking System]

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

> reassign 1031252 libamdhip64-5
Bug #1031252 [src:hipsparse] hipsparse: FTBFS (c++: error: -E or -x required 
when input is from standard input)
Bug reassigned from package 'src:hipsparse' to 'libamdhip64-5'.
No longer marked as found in versions hipsparse/5.3.3+dfsg-1.
Ignoring request to alter fixed versions of bug #1031252 to the same values 
previously set
> affects 1031252 + src:hipsparse
Bug #1031252 [libamdhip64-5] hipsparse: FTBFS (c++: error: -E or -x required 
when input is from standard input)
Added indication that 1031252 affects src:hipsparse
> found 1031252 5.2.3-1~0exp1
Bug #1031252 [libamdhip64-5] hipsparse: FTBFS (c++: error: -E or -x required 
when input is from standard input)
Marked as found in versions rocm-hipamd/5.2.3-1~0exp1.
> fixed 1031252 5.2.3-2
Bug #1031252 [libamdhip64-5] hipsparse: FTBFS (c++: error: -E or -x required 
when input is from standard input)
Marked as fixed in versions rocm-hipamd/5.2.3-2.
> forcemerge 1031252 1021643
Bug #1031252 [libamdhip64-5] hipsparse: FTBFS (c++: error: -E or -x required 
when input is from standard input)
Bug #1021643 {Done: Étienne Mollier } [libamdhip64-5] 
libamdhip64-5: libamdhip64.so.5.2.21153- missing githash
Severity set to 'serious' from 'normal'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions rocm-hipamd/5.2.3-2.
Added indication that 1021643 affects src:hipsparse
Added tag(s) ftbfs.
Bug #1021643 [libamdhip64-5] libamdhip64-5: libamdhip64.so.5.2.21153- missing 
githash
Marked as fixed in versions rocm-hipamd/5.2.3-2.
Merged 1021643 1031252
> thanks
Stopping processing here.

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

Bug#1027542: epl: FTBFS: make: *** [debian/rules:6: build] Error 25

[Adrian Bunk]

On Mon, Jan 02, 2023 at 08:14:55AM -0400, David Bremner wrote:
> Lucas Nussbaum  writes:
> 
> > Source: epl
> > Version: 0.9-5
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20230101 ftbfs-bookworm
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> 
> This seems tricky to duplicate
> 
> - building on bare metal (sid/bookworm): works
> - building in sbuild chroot by running dpkg-buildpackage: works
> - building with sbuild: fails.
> 
> As a wild guess I tried adding
> 
>export EMACS_INHIBIT_AUTOMATIC_NATIVE_COMPILATION=t
> 
> to debian/rules, but it did not help.

FTR, the dates when epl started to FTBFS in sid and bookworm are
a good match for when emacs 1:28.2+1-9 entered sid and bookworm:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/epl.html

cu
Adrian

Bug#1031252: hipsparse: FTBFS (c++: error: -E or -x required when input is from standard input)

[Santiago Vila]

reassign 1031252 libamdhip64-5
affects 1031252 + src:hipsparse
found 1031252 5.2.3-1~0exp1
fixed 1031252 5.2.3-2
forcemerge 1031252 1021643
thanks

El 14/2/23 a las 5:15, Cordell Bloor escribió:

This is a bug in libamdhip64-5:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021643

It was fixed in rocm-hipamd 5.2.3-2, but no versions since rocm-hipamd 5.2.3-1 
have migrated to bookworm. This problem will affect all libraries and 
executables that link against libamdhip64-5 using the GCC toolchain.


If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.


I'm still learning how to use these the Debian bug reporting tools. Perhaps 
another maintainer could help set these properties.

Apologies for the incomplete handling, but I hope that this information is 
helpful.


No problem. The information alone is already useful.
I believe the above commands should work (note: I'm using Bcc for 
control@b.d.o).

Thanks.

Bug#1030412: marked as done (python-jenkins: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 10:09:02 +
with message-id 
and subject line Bug#1030412: fixed in python-jenkins 1.4.0-3
has caused the Debian Bug report #1030412,
regarding python-jenkins: FTBFS: tests 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.)


-- 
1030412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030412
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-jenkins
Version: 1.4.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-jenkins
> + echo python-jenkins
> + sed s/python-//
> + PY_MODULE_NAME=jenkins
> + py3versions -vr
> + PYTHON3S=3.11
> + [ no = yes ]
> + TARGET_DIR=python3-jenkins
> + pwd
> + python3.11 setup.py install --install-layout=deb --root 
> /<>/debian/python3-jenkins
> /usr/lib/python3/dist-packages/setuptools/dist.py:775: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:775: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: 
> EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
> and pip and other standards-based tools.
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:775: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:775: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> running install
> [pbr] Generating AUTHORS
> [pbr] AUTHORS complete (0.0s)
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/jenkins
> copying jenkins/__init__.py -> build/lib/jenkins
> copying jenkins/plugins.py -> build/lib/jenkins
> copying jenkins/version.py -> build/lib/jenkins
> running egg_info
> creating python_jenkins.egg-info
> writing python_jenkins.egg-info/PKG-INFO
> writing dependency_links to python_jenkins.egg-info/dependency_links.txt
> writing requirements to python_jenkins.egg-info/requires.txt
> writing top-level names to python_jenkins.egg-info/top_level.txt
> [pbr] Processing SOURCES.txt
> writing manifest file 'python_jenkins.egg-info/SOURCES.txt'
> warning: no files found matching 'AUTHORS'
> warning: no files found matching 'ChangeLog'
> warning: no previously-included files found matching '.gitignore'
> warning: no previously-included files found matching '.gitreview'
> warning: no previously-included files matching '*.pyc' found anywhere in 
> distribution
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'AUTHORS'
> warning: no files found matching 'ChangeLog'
> warning: no previously-included files found matching '.gitignore'
> warning: no previously-included files found matching '.gitreview'
> warning: no previously-included files matching '*.pyc' found anywhere in 
> distribution
> adding license file 'COPYING'
> writing manifest file 'python_jenkins.egg-info/SOURCES.txt'
> running install_lib
> creating /<>/debian/python3-jenkins
> creating /<>/debian/python3-jenkins/usr
> creating /<>/debian/python3-jenkins/usr/lib
> creating /<>/debian/python3-jenkins/usr/lib/python3
> creating /<>/debian/python3-jenkins/usr/lib/python3/dist-packages
> creating 
> /<>/debian/python3-jenkins/usr/lib/python3/dist-packages/jenkins
> copying build/lib/jenkins/__init__.py -> 
> 

Processed: Bug#1030412 marked as pending in python-jenkins

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1030412 [src:python-jenkins] python-jenkins: FTBFS: tests failed
Added tag(s) pending.

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

Bug#1030412: marked as pending in python-jenkins

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1030412 in python-jenkins 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/openstack-team/third-party/python-jenkins/-/commit/23876b6dde05b5a3b76caccc3a46be2951d6a8d4


Add allow-pkg_resources.parse_version-to-fail.patch (Closes: #1030412).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030412

Bug#1030438: marked as done (python-dcos: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 'SNAPSHOT')

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 09:34:17 +
with message-id 
and subject line Bug#1030438: fixed in python-dcos 0.2.0-6
has caused the Debian Bug report #1030438,
regarding python-dcos: FTBFS: 
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'SNAPSHOT'
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.)


-- 
1030438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dcos
Version: 0.2.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-dcos
> + echo python-dcos
> + sed s/python-//
> + PY_MODULE_NAME=dcos
> + py3versions -vr
> + PYTHON3S=3.11
> + [ no = yes ]
> + TARGET_DIR=python3-dcos
> + pwd
> + python3.11 setup.py install --install-layout=deb --root 
> /<>/debian/python3-dcos
> /usr/lib/python3/dist-packages/setuptools/dist.py:548: UserWarning: The 
> version specified ('SNAPSHOT') is an invalid version, this may not work as 
> expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 
> for more details.
>   warnings.warn(
> running install
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/dcos
> copying dcos/__init__.py -> build/lib/dcos
> copying dcos/package.py -> build/lib/dcos
> copying dcos/util.py -> build/lib/dcos
> copying dcos/marathon.py -> build/lib/dcos
> copying dcos/options.py -> build/lib/dcos
> copying dcos/errors.py -> build/lib/dcos
> copying dcos/subcommand.py -> build/lib/dcos
> copying dcos/http.py -> build/lib/dcos
> copying dcos/auth.py -> build/lib/dcos
> copying dcos/emitting.py -> build/lib/dcos
> copying dcos/cmds.py -> build/lib/dcos
> copying dcos/mesos.py -> build/lib/dcos
> copying dcos/config.py -> build/lib/dcos
> copying dcos/constants.py -> build/lib/dcos
> copying dcos/jsonitem.py -> build/lib/dcos
> running install_lib
> creating /<>/debian/python3-dcos
> creating /<>/debian/python3-dcos/usr
> creating /<>/debian/python3-dcos/usr/lib
> creating /<>/debian/python3-dcos/usr/lib/python3
> creating /<>/debian/python3-dcos/usr/lib/python3/dist-packages
> creating 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/__init__.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/package.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/util.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/marathon.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/options.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/errors.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/subcommand.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/http.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/auth.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/emitting.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/cmds.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/mesos.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/config.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/constants.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> copying build/lib/dcos/jsonitem.py -> 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos
> byte-compiling 
> /<>/debian/python3-dcos/usr/lib/python3/dist-packages/dcos/__init__.py
>  to __init__.cpython-311.pyc

Bug#1029439: help fixing this bug

[Thorsten Alteholz]

In case somebody has any idea how to fix this bug, I would be happy to 
apply a patch.


  Thorsten

Bug#1027551: any progress

[Thorsten Alteholz]

Hi,

this is just a ping  ...

  Thorsten

Bug#1030438: marked as pending in python-dcos

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1030438 in python-dcos 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/openstack-team/python/python-dcos/-/commit/ee79b5b2e07e61369ff799a33fd6d39317764bca


Fix package version when building (Closes: #1030438).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030438

Processed: Bug#1030438 marked as pending in python-dcos

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1030438 [src:python-dcos] python-dcos: FTBFS: 
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'SNAPSHOT'
Added tag(s) pending.

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

Bug#1030535: marked as done (python-pycdlib: FTBFS (AttributeError: module 'inspect' has no attribute 'getargspec'))

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2023 09:05:57 +
with message-id 
and subject line Bug#1030535: fixed in python-pycdlib 1.12.0+ds1-4
has caused the Debian Bug report #1030535,
regarding python-pycdlib: FTBFS (AttributeError: module 'inspect' has no 
attribute 'getargspec')
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.)


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

Package: src:python-pycdlib
Version: 1.12.0+ds1-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
=== short test summary info 
===
FAILED tests/integration/test_parse.py::test_parse_write_with_progress - 
AttributeError: module 'inspect' has no attribute 'getargspec'
FAILED 
tests/integration/test_parse.py::test_parse_write_with_progress_three_arg - 
AttributeError: module 'inspect' has no attribute 'getargspec'
= 2 failed, 1702 passed, 17 skipped in 
13.87s =
make[1]: *** [debian/rules:19: override_dh_auto_install] Error 1
make[1]: Leaving directory '/home/sanvila/python-pycdlib-1.12.0+ds1'
make: *** [debian/rules:7: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The above is just how the build ends and I believe it's also the most relevant 
part.

The failure also happens here with similar error message:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pycdlib.html


About the archive rebuild: The build was made using virtual machines
from Hetzner, with enough memory, enough disk, and either one or two
CPUs, using a reduced chroot with only build-essential packages (plus
debhelper).

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: python-pycdlib
Source-Version: 1.12.0+ds1-4
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-pycdlib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 25 Oct 2022 15:46:06 +0200
Source: python-pycdlib
Architecture: source
Version: 1.12.0+ds1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1030535
Changes:
 python-pycdlib (1.12.0+ds1-4) unstable; urgency=medium
 .
   * Add fix-getargspec-removed-from-py3.11.patch (Closes: #1030535).
Checksums-Sha1:
 0eba3894405dabb45f01ef0be4aa154ffb917ede 2148 python-pycdlib_1.12.0+ds1-4.dsc
 0f40ec50f092dfb81b51d8caed15000dca640bd9 3632 
python-pycdlib_1.12.0+ds1-4.debian.tar.xz
 3b04d97fe3aafc079576d2be399f49778f7ef9ed 7216 
python-pycdlib_1.12.0+ds1-4_amd64.buildinfo
Checksums-Sha256:
 d3ec9542d2ec752db6892acaf375263d0c9ec8ecffb3f20fe2ab660c71bf52e2 2148 
python-pycdlib_1.12.0+ds1-4.dsc
 8ed6af66f97f10c2f8a96d3fb7d161818d4785f007ac77824da7355afcc21af5 3632 
python-pycdlib_1.12.0+ds1-4.debian.tar.xz
 d094be8cab42f76677491a8aca89047c4fc74ea3acca94c679b855040997594c 7216 
python-pycdlib_1.12.0+ds1-4_amd64.buildinfo
Files:
 40f498fc9b3cb41f80ff7e49c6fd7b68 2148 python optional 
python-pycdlib_1.12.0+ds1-4.dsc
 c536230a6e27bba521da07c69edc2051 3632 python optional 
python-pycdlib_1.12.0+ds1-4.debian.tar.xz
 cf8657f19ce011c255456aedef3eca0c 7216 python optional 
python-pycdlib_1.12.0+ds1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Processed: Bug#1030469 marked as pending in python-proliantutils

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1030469 [src:python-proliantutils] python-proliantutils: FTBFS: 
AssertionError: Calls not found.
Added tag(s) pending.

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

Bug#1030469: marked as pending in python-proliantutils

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1030469 in python-proliantutils 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/openstack-team/libs/python-proliantutils/-/commit/671906addf26a674a513341452fe2923da35560e


* Blacklist test_update_persistent_boot_uefi_target() that is broken under
Python 3.11 (Closes: #1030469).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030469

Bug#1030416: marked as pending in python-os-api-ref

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1030416 in python-os-api-ref 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/openstack-team/libs/python-os-api-ref/-/commit/21b6dd6945697e7d8d69370bfd2cd690ab31d12b


* Blacklist failing tests (Closes: #1030416):
- TestBasicExample.test_parameters
- TestBasicExample.test_rest_response


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030416

Processed: Bug#1030416 marked as pending in python-os-api-ref

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1030416 [src:python-os-api-ref] python-os-api-ref: FTBFS: make[1]: *** 
[debian/rules:19: override_dh_auto_test] Error 1
Added tag(s) pending.

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

Bug#1030669: Only include in Bookworm with commitment to stable updates

[Moritz Muehlenhoff]

On Tue, Feb 14, 2023 at 02:48:43AM +0100, Marco d'Itri wrote:
> On Feb 02, Moritz Muehlenhoff  wrote:
> 
> > Varnish should only be included in Bookworm with a reliable commitment
> > by the maintainers to backport/test security fixes across the typical
> > three year life cycle (two years of stable-security and one year of
> > oldstable-security).
> I do not think that this will be helpful for Varnish users.

Then someone needs to step up, it's as easy as that.