Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

[Andres Salomon]

On 1/5/22 13:14, Mattia Rizzolo wrote:

On Wed, Jan 05, 2022 at 01:52:33PM +0100, Mattia Rizzolo wrote:

I suppose I'll see how it goes in the coming few days.

So it's not crashing but it's being unbearably slow in gmail, to the
point that I just wasn't able to type a mail there, while throwing one
CPU core to 100%.
Also it was kind go generally slow in several other sites, compared to
v93.  Always compared to v93, it takes far longer (and by far much much
more CPU) to reopen the whole session (I keep ~50 tabs in 3 windows open
all the time, trusting the browser to reopen them where I left when I
close it).

I didn't mesure anything and I don't have any numbers to share, but
that's what I see.


At least, it looks like it has not been leaking as much memory as v93
was (that in this regard was buggier than v90).



If you want to try with chromium 97; it now builds as an official build, 
so those DCHECKs shouldn't even be compiled in. It also supports wayland 
automatically, in case that's related to your slowdowns.


https://salsa.debian.org/dilinger/chromium/-/tree/v97

Bug#1002132: A patch from upstream

[handsome_feng]

Hi,


I saw this bug older than 7 days and no maintainer activity, but it
fixed upstream: 

https://github.com/canonical/lightdm/commit/270b3bfcf84939ab2d71db3f3470cffd36816852

So I prepared a debdiff,  and I hope this will help.


Cheers,

handsome_feng
diff -Nru lightdm-1.26.0/debian/changelog lightdm-1.26.0/debian/changelog
--- lightdm-1.26.0/debian/changelog 2020-02-04 03:13:13.0 +0800
+++ lightdm-1.26.0/debian/changelog 2022-01-06 14:49:08.0 +0800
@@ -1,3 +1,12 @@
+lightdm (1.26.0-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches:
+- 10_fix-build-glibc-2.33 added, fix FTBFS with glibc 2.33.
+  (Closes: #1002132)
+
+ -- handsome_feng   Thu, 06 Jan 2022 14:49:08 +0800
+
 lightdm (1.26.0-7) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru lightdm-1.26.0/debian/patches/10_fix-build-glibc-2.33.patch 
lightdm-1.26.0/debian/patches/10_fix-build-glibc-2.33.patch
--- lightdm-1.26.0/debian/patches/10_fix-build-glibc-2.33.patch 1970-01-01 
08:00:00.0 +0800
+++ lightdm-1.26.0/debian/patches/10_fix-build-glibc-2.33.patch 2022-01-06 
14:49:08.0 +0800
@@ -0,0 +1,22 @@
+--- a/tests/src/libsystem.c
 b/tests/src/libsystem.c
+@@ -329,6 +329,10 @@ stat64 (const char *path, struct stat64
+ return _stat64 (new_path, buf);
+ }
+ 
++// glibc 2.33 and newer does not declare these functions in a header file
++#pragma GCC diagnostic push
++#pragma GCC diagnostic ignored "-Wmissing-prototypes"
++
+ int
+ __xstat (int version, const char *path, struct stat *buf)
+ {
+@@ -365,6 +369,8 @@ __fxstatat64(int ver, int dirfd, const c
+ return ___fxstatat64 (ver, dirfd, new_path, buf, flags);
+ }
+ 
++#pragma GCC diagnostic pop
++
+ DIR *
+ opendir (const char *name)
+ {
diff -Nru lightdm-1.26.0/debian/patches/series 
lightdm-1.26.0/debian/patches/series
--- lightdm-1.26.0/debian/patches/series2020-02-04 03:13:13.0 
+0800
+++ lightdm-1.26.0/debian/patches/series2022-01-06 14:49:08.0 
+0800
@@ -5,3 +5,4 @@
 06_change-user-dirs.patch
 08_reset-SIGPIPE-before-exec.patch
 09_hide_systemd_nologin.patch
+10_fix-build-glibc-2.33.patch

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

[Debian Bug Tracking System]

Your message dated Thu, 06 Jan 2022 07:03:31 +
with message-id 
and subject line Bug#965791: fixed in pscan 1.2-9.1
has caused the Debian Bug report #965791,
regarding pscan: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: pscan
Source-Version: 1.2-9.1
Done: Paul Wise 

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

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated pscan package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Jan 2022 14:47:32 +0800
Source: pscan
Architecture: source
Version: 1.2-9.1
Distribution: unstable
Urgency: medium
Maintainer: Uwe Hermann 
Changed-By: Paul Wise 
Closes: 965791
Changes:
 pscan (1.2-9.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump debhelper compat level to 7 (Closes: #965791)
 There are no changes to the binary package from this.
Checksums-Sha1:
 16382ea8459ceff44dd6182fec4087aee74991cd 1649 pscan_1.2-9.1.dsc
 b49b26a638a02f848007e3e756871621cea1c6b5 6053 pscan_1.2-9.1.diff.gz
Checksums-Sha256:
 e1086b219d7b5eec500fd2558ae6d9024648091a10e6cd671e12c078a86c3db2 1649 
pscan_1.2-9.1.dsc
 c36b097af64eb0300775af19d0ed9a5411e0b4365fc539257ce443859564a7aa 6053 
pscan_1.2-9.1.diff.gz
Files:
 cbb4ad935b5f0f6a1b19543ac186cf3a 1649 misc optional pscan_1.2-9.1.dsc
 fffcc8a1a272fa1323046b4b55bb3900 6053 misc optional pscan_1.2-9.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAmHWkc8ACgkQMRa6Xp/6
aaM1pxAAnQyRJnfYCJdfrh0sd0+WuZDTAiL9P/IIvB7Zf5OvnnVqUjWlJmI3Jq/8
N+A4Rp+SWISApvRMluJYnNBiohlxlmc37F304FxHJf5j60heZDHgEK0ZjyD33DMI
eBBF4DxJr2w1OfQxzh28LdnJ5FtHtLQMne1PYQRn7A57D5ozgPECKi2JQ+UM74lO
5hF+6D5zFOSRIXuDyEEA3LvCef2P5EelYKn+9PnN7mdTtUIPhAEGL0XUhi05eJ/z
trdzB6mThjnUWEUdi8+RAgzUKLNpxK1LG7f2Awju14Zeo8hnLyj4YBbxanb72Uum
8PU9eXfLk3JeqYC0RqRrxG7HjqhMk5KDYejG5eeseTdsOmhvDlGXDFP3LCa5WdMt
rhGqX8wUEl7GPBy6p+755/JdKvX3IGY6Ts94K9iNPSK86w1p0YxScxKXmatGEYmA
BUs7S3qe9G2M+sr6jF9A2rqIlAtDtFX83SfCUNo90tsk3k3uZNoECtK4N4nAKvOc
pZlYFkqpHa3Vdbby9Wol6END74pVRFjnk+0V8MBDKQ1ithm/oDa60DhlbgIb4bfS
6Mtjv22vS0rDscbCoknBIm8CpJJW0DGtEPbCYNkC+ZPUUuK7o/jXA8P8WTFrf+58
+9n5waR0URytrWAv7HnYRiuTdBUQZYjXlqH+W9ugdiBPaL7SJSk=
=fWts
-END PGP SIGNATURE End Message ---

Bug#965651: marked as done (libjmac-java: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Thu, 06 Jan 2022 05:33:29 +
with message-id 
and subject line Bug#965651: fixed in libjmac-java 1.74-7
has caused the Debian Bug report #965651,
regarding libjmac-java: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: libjmac-java
Source-Version: 1.74-7
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated libjmac-java package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Jan 2022 21:22:27 -0800
Source: libjmac-java
Architecture: source
Version: 1.74-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 965651
Changes:
 libjmac-java (1.74-7) unstable; urgency=medium
 .
   * Team upload
   * Update debian/compat to 9 (Closes: #965651)
   * Update Vcs URLs to point to Salsa
Checksums-Sha1:
 9a5cc124fd251a04300aeb5f4ff26cbfb83ec339 2035 libjmac-java_1.74-7.dsc
 29e560bb837d32fa964f8bb18482dc0fd07821e9 3752 libjmac-java_1.74-7.diff.gz
 45252c35b86834bce00d3ad0ef09833ea069962a 8288 
libjmac-java_1.74-7_amd64.buildinfo
Checksums-Sha256:
 52872aa7b0ef94a08dff16e4067f9bb5724009f22d8c5f1eeb0a62a0e478668c 2035 
libjmac-java_1.74-7.dsc
 73158cf3255438f034eb34436489a6c990f4fe2b9ff95d096d1dfaa6c8846c65 3752 
libjmac-java_1.74-7.diff.gz
 b699e3558aab553b9fe22527639ee71bcd7e5cbedd5c5412d7d6a673848612d3 8288 
libjmac-java_1.74-7_amd64.buildinfo
Files:
 adacd01c3ed01081139ecb9971d828c0 2035 java optional libjmac-java_1.74-7.dsc
 138ad62a69f83e027469353f6fa761a8 3752 java optional libjmac-java_1.74-7.diff.gz
 682a020da1c879be567897a9102d4be5 8288 java optional 
libjmac-java_1.74-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmHWfRAUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpa62hAAwYagiX7mFdmQug9sFLjENoJkDgTc
ZOKUf5Mro7MhbKYcWeOr5jdjWKZ0u5THXChEtqNhUwASEZSxLHPD94uhV220k/OM
1UNFikv1g9RBwDAWbZPjml6Zq7IaIx4OMY/Mp5s614qQxBt5uvLV5rkymbv3qqo7
eYNPVihw7Y2vIaPtPTQ7l37hOKGia2M/mkEHEtfN8rzBn/L0gyCKrub9dOk+9ADf
slTT4/n7Lf7bTTU1LojifUqIyr+Zyjp2Und9zXHeKVX5ss+3yK2AWupTBgZ2bXkm
tw19vX9EP/2csn37PA3MjTWNQxTZJ0+MKdtJIR8ELSM8hOvfTvbORVuQs41qEtac
ber848896MjvF/ul13Zlv5dsf5xMThXoKoyu8biU6sByGJqPkzz06b3gNrCBIrFX
ZhO96Qeql8b9TTriIx8EgVI0ASKQWBLnuS78xNLSpu9b7nTL1CriFThc8rpOJuQl
vpqo2nyYdqR6P+tE/JcB+lQg05yyfU0U8fNDmjyPVScBBnBxtFWNayGfA1lTB0J2
wFYIMvnpl8i3yz/UAgcuAxlej96XzsRhbDiiNaA/Jb7zqimLIXbVDGgt+bKzEVnl
mcpLErdJDO5Q2HSTVupmiTSIFaTlRli6rzyg5K9lr0C+NQtD01GAmE2O/IAVBk6k
u2PHzpomn5jKWw4=
=6Zc1
-END PGP SIGNATURE End Message ---

Bug#996066: marked as done (gnome-shell-extension-multi-monitors: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Thu, 06 Jan 2022 04:33:22 +
with message-id 
and subject line Bug#1003166: Removed package(s) from unstable
has caused the Debian Bug report #996066,
regarding gnome-shell-extension-multi-monitors: does not declare compatibility 
with GNOME Shell 41
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.)


-- 
996066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-multi-monitors
Version: 23-1
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

The metadata.json for this extension doesn't declare compatibility with
GNOME 41. I don't know whether the actual code will need changes or not:
the conservative assumption is that it probably will (so please test).
gnome-shell 41 should be available in experimental soon.

In versions of GNOME Shell up to 3.38, metadata.json didn't matter much,
because validation of extensions' metadata against the installed Shell
version was disabled by default; but since GNOME 40 the default has changed
back to enabling the version check by default, in an effort to avoid
issues caused by outdated extensions remaining enabled. As a result,
GNOME Shell extensions in bookworm should probably have a dependency like:

Depends: gnome-shell (>= x), gnome-shell (<< y~)

where x and y are set according to metadata.json.
gnome-shell-extension-caffeine is a good example of this technique.

When we do the GNOME Shell 41 transition, hopefully soon, we will have
to either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 23-1+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1002084: marked as done (smlsharp: FTBFS: configure: error: Specify --with-incompatible-llvm if you really want to build SML# with it.)

[Debian Bug Tracking System]

Your message dated Thu, 06 Jan 2022 01:33:30 +
with message-id 
and subject line Bug#1002084: fixed in smlsharp 4.0.0+git20211227.5af5945b-1
has caused the Debian Bug report #1002084,
regarding smlsharp: FTBFS: configure: error: Specify --with-incompatible-llvm 
if you really want to build SML# with it.
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.)


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

Hi,

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


Relevant part (hopefully):
> checking for opt... /usr/lib/llvm-13/bin/opt
> checking for llvm-dis... /usr/lib/llvm-13/bin/llvm-dis
> checking for llvm-as... /usr/lib/llvm-13/bin/llvm-as
> checking for LLVM compatibility... no
> configure: WARNING: SML# does not support LLVM 13.0. Build may fail due to 
> incompatibility.
> configure: error: Specify --with-incompatible-llvm if you really want to 
> build SML# with it.
> make[1]: *** [debian/rules:14: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/smlsharp_4.0.0-3_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: smlsharp
Source-Version: 4.0.0+git20211227.5af5945b-1
Done: Nobuhiro Iwamatsu 

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

Debian distribution maintenance software
pp.
Nobuhiro Iwamatsu  (supplier of updated smlsharp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 06 Jan 2022 09:26:36 +0900
Source: smlsharp
Architecture: source
Version: 4.0.0+git20211227.5af5945b-1
Distribution: unstable
Urgency: medium
Maintainer: Nobuhiro Iwamatsu 
Changed-By: Nobuhiro Iwamatsu 
Closes: 1002084
Changes:
 smlsharp (4.0.0+git20211227.5af5945b-1) unstable; urgency=medium
 .
   * Snapshot, taken from the master (20220106). (Closes: #1002084)
Checksums-Sha1:
 ed4af23b114ef83c3bc471eabb419ffd3520a61e 2019 
smlsharp_4.0.0+git20211227.5af5945b-1.dsc
 5b8156f44ea5236d584e08e336fbe8b871e2e92b 6224008 
smlsharp_4.0.0+git20211227.5af5945b.orig.tar.xz
 2dbeb55cec62693d7fe3a688422f74f90a4a1e2e 5872 
smlsharp_4.0.0+git20211227.5af5945b-1.debian.tar.xz
 ffb0d2ab432fe6178c57681950c04fe7a88e 7578 
smlsharp_4.0.0+git20211227.5af5945b-1_amd64.buildinfo
Checksums-Sha256:
 cc574b7d3c5b30546c608ee32dcc03440130dbc0ec28d3d2061375086f208f2f 2019 
smlsharp_4.0.0+git20211227.5af5945b-1.dsc
 bc67e6ec103da8debc79ff8e300393f5016f162f789e71ca63ced6321c44c6bd 6224008 
smlsharp_4.0.0+git20211227.5af5945b.orig.tar.xz
 dd7887e9aa644731890296f87aaae96d2c0f2f7159473ac736fb41ad7c29f259 5872 
smlsharp_4.0.0+git20211227.5af5945b-1.debian.tar.xz
 2f6050907fa5b7b4bc425f9398b2d6ae1cb05511e7582d26b68e1e810ebfc069 7578 
smlsharp_4.0.0+git20211227.5af5945b-1_amd64.buildinfo
Files:
 dd79c43fe13f01c73a6905c88cb7139a 2019 devel optional 
smlsharp_4.0.0+git20211227.5af5945b-1.dsc
 ff99e9cf53016e80e7fa961667975cc4 6224008 devel optional 
smlsharp_4.0.0+git20211227.5af5945b.orig.tar.xz
 cc946f8b2bde3f428834c66bc4e8d896 5872 devel optional 
smlsharp_4.0.0+git20211227.5af5945b-1.debian.tar.xz
 a16106f841e1ba982bcf8c8a1ccc4164 7578 devel optional 
smlsharp_4.0.0+git20211227.5af5945b-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXmKe5SMhlzV7hM9DMiR/u0CtH6YFAmHWQ4oACgkQMiR/u0Ct

Bug#1000619: marked as done (tcpdf: Failing testsuite with PHP 8.1)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 23:18:40 +
with message-id 
and subject line Bug#1000619: fixed in tcpdf 6.4.4+dfsg1-1
has caused the Debian Bug report #1000619,
regarding tcpdf: Failing testsuite with PHP 8.1
to be marked as done.

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

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


-- 
1000619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000619
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-tcpdf
Version: 6.4.2+dfsg1-1
Severity: normal
Control: block 976811 by -1

Hi,

Now that PHP 8.1 is default in experimental (soon in unstable), we
noticed the testsuite is currently failing due to deprecation notices.

https://release.debian.org/britney/pseudo-excuses-experimental.html#php-defaults
https://ci.debian.net/data/autopkgtest/unstable/amd64/t/tcpdf/16973890/log.gz
[…]
Deprecated: Implicit conversion from float 16.912810673130803 to int loses 
precision in /usr/share/php/tcpdf/tcpdf.php on line 7360

Deprecated: Implicit conversion from float 5.388921932205105 to int loses 
precision in /usr/share/php/tcpdf/tcpdf.php on line 7360

Deprecated: Implicit conversion from float 0.20696933481202212 to int loses 
precision in /usr/share/php/tcpdf/tcpdf.php on line 7360

Deprecated: Implicit conversion from float 0.006000286595066149 to int loses 
precision in /usr/share/php/tcpdf/tcpdf.php on line 7360

Warning: Cannot modify header information - headers already sent by (output 
started at /usr/share/php/tcpdf/tcpdf.php:7360) in 
/usr/share/php/tcpdf/tcpdf.php on line 7709
TCPDF ERROR: Some data has already been output to browser, 
can't send PDF file
---
[…]

A quick look upstream makes me think a patch is already available.

PHP 8.1: Fix implicit conversion from float to int #387 
https://github.com/tecnickcom/TCPDF/pull/387

Thanks in advance for fixing this issue.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: tcpdf
Source-Version: 6.4.4+dfsg1-1
Done: William Desportes 

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

Debian distribution maintenance software
pp.
William Desportes  (supplier of updated tcpdf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Jan 2022 23:54:01 +0100
Source: tcpdf
Built-For-Profiles: noudeb
Architecture: source
Version: 6.4.4+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: phpMyAdmin Team 
Changed-By: William Desportes 
Closes: 1000619
Changes:
 tcpdf (6.4.4+dfsg1-1) unstable; urgency=medium
 .
   * New upstream version 6.4.4 (Closes: #1000619)
   * Update tcpdf test.php from upstream
   * Update d/copyright
   * Add d/s/lintian-overrides
   * Update d/copyright years
   * Update test.sh to use the debian include path for tests
   * Depend on dh-sequence-phpcomposer and remove dh --with phpcomposer
   * Remove Felipe from Uploaders (no upload needed since 2020)
   * Install /u/s/p/autoloaders file
   * Use the debian autoload and not the class file directly in example 066
Checksums-Sha1:
 54de21cc9b2744a73825a8705d5f8dd23ee1d886 2084 tcpdf_6.4.4+dfsg1-1.dsc
 9b5aae662a35d055b6deef38889c24d97bbb3a55 8004516 tcpdf_6.4.4+dfsg1.orig.tar.xz
 60997c6a292c8d0fbf4fb439d728a32854b5b505 9416 tcpdf_6.4.4+dfsg1-1.debian.tar.xz
 625b15aa5d155c11850a1cb840459f5ba53d0b9c 9551 
tcpdf_6.4.4+dfsg1-1_source.buildinfo
Checksums-Sha256:
 e58d255fb702625d7ffe30318d5bfe145355fb434b2255dea1f01bc7c373cb23 2084 
tcpdf_6.4.4+dfsg1-1.dsc
 4d29c2fe6e3bc566592ecb41beed4a7e6f889666a2da247c83f682621e80 8004516 
tcpdf_6.4.4+dfsg1.orig.tar.xz
 b814e3f603331e1317e5129b05aee9cca393955bfc08550540d8738e7d17de82 9416 
tcpdf_6.4.4+dfsg1-1.debian.tar.xz
 ea170092503695813586748201e2d6c80fe00c478f2514e9e6b091bb7b4e17e8 9551 
tcpdf_6.4.4+dfsg1-1_source.buildinfo
Files:
 6ba64de4d0906ea7616fc8f95e937e04 2084 php optional tcpdf_6.4.4+dfsg1-1.dsc
 6f2a8365b1e69a7bfbe1ed9b96a20ebd 8004516 php optional 
tcpdf_6.4.4+dfsg1.orig.tar.xz
 ec5aaac2dc8f22a0ecac08e69409551e 9416 php optional 
tcpdf_6.4.4+dfsg1-1.debian.tar.xz
 

Processed: Working on gkrellkam

[Debian Bug Tracking System]

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

> tags 350166 pending
Bug #350166 [gkrellkam] typos in gkrellkam-list.5 resulting in missing words
Added tag(s) pending.
> tags 848375 pending
Bug #848375 [gkrellkam] gkrellkam: Retrieves image from external server. 
Potential privacy violation, dead link
Added tag(s) pending.
> tags 939882 pending
Bug #939882 [src:gkrellkam] gkrellkam FTCBFS: does not pass cross tools to make
Added tag(s) pending.
> tags 999084 pending
Bug #999084 [src:gkrellkam] gkrellkam: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.
> tags 1001969 pending
Bug #1001969 [src:gkrellkam] ITS: gkrellkam
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#965507: marked as done (edac-utils: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 22:19:01 +
with message-id 
and subject line Bug#965507: fixed in edac-utils 0.18+git12-gd98769e-1
has caused the Debian Bug report #965507,
regarding edac-utils: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: edac-utils
Source-Version: 0.18+git12-gd98769e-1
Done: Yaroslav Halchenko 

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

Debian distribution maintenance software
pp.
Yaroslav Halchenko  (supplier of updated edac-utils 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 05 Jan 2022 11:35:31 -0500
Source: edac-utils
Architecture: source
Version: 0.18+git12-gd98769e-1
Distribution: unstable
Urgency: medium
Maintainer: Yaroslav Halchenko 
Changed-By: Yaroslav Halchenko 
Closes: 965507
Changes:
 edac-utils (0.18+git12-gd98769e-1) unstable; urgency=medium
 .
   [ Stephen Kitt ]
   * Non-maintainer upload.
   * Bump to debhelper compatibility level 10. Closes: #965507. Level 10
 is the last level usable with cdbs in packages installing init
 scripts; see #885407 for details.
 .
   [ Yaroslav Halchenko ]
   * Incorporate changes from upstream git for 0.18-12-gd98769e
   * Add a patch to produce fake ChangeLog to satisfy autotools
Checksums-Sha1:
 d8746c8264268b5ac7bf3b77ab7ab91b9014ad6f 2172 
edac-utils_0.18+git12-gd98769e-1.dsc
 53aa65c2fb384aaa110d245fec575c4470347f69 284189 
edac-utils_0.18+git12-gd98769e.orig.tar.gz
 4a658a26309866469c46711b778531fa8f03473d 5248 
edac-utils_0.18+git12-gd98769e-1.debian.tar.xz
 ba0880e4a8af72503a2c00ef71272d5f11a0a65c 6030 
edac-utils_0.18+git12-gd98769e-1_source.buildinfo
Checksums-Sha256:
 626ac9cba67cc10052c26f609e46745241ca692b9ae6daed59021a705089731f 2172 
edac-utils_0.18+git12-gd98769e-1.dsc
 a75fc837fa0a9e94100ad610638fcd2761cedf78ff846219758226861a058a18 284189 
edac-utils_0.18+git12-gd98769e.orig.tar.gz
 87d7ef1b9d34096fe44134913836a8163560f63fff0307f7cbb2c37d72a500c2 5248 
edac-utils_0.18+git12-gd98769e-1.debian.tar.xz
 0723da45148c36948237066397df06e66ffd2d80bd8b0c60a4190992bb60a1f8 6030 
edac-utils_0.18+git12-gd98769e-1_source.buildinfo
Files:
 0cd0fe56d94051e46520697c385ac8b9 2172 admin extra 
edac-utils_0.18+git12-gd98769e-1.dsc
 27f7b0043826ece129ae6b3a1a7e144d 284189 admin extra 
edac-utils_0.18+git12-gd98769e.orig.tar.gz
 3686a0a0bfcbffe96a4eda114f943f90 5248 admin extra 
edac-utils_0.18+git12-gd98769e-1.debian.tar.xz
 c2aaf6a4d60b129c70549510e26353ae 6030 admin extra 
edac-utils_0.18+git12-gd98769e-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExbkF8OjZ/ZZo/zZvot4jUGLaM/oFAmHWAqIACgkQot4jUGLa

Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive

[Joseph Carter]

On Sun, 02 Jan 2022 23:28:32 +0100 Hilko Bengen  wrote:
> * Laurent Bigonville:
> 
> > It looks like libguestfs-tools version 1:1.46.2-1 in depending on
> > guestfs-tools that is not in the archive making the package uninstalable
> >
> > guestfs-tools is currently stuck in the new queue
> 
> Right. Let's  just wait. (Or do you know of a way to speed this up?)

Cold beverages of the FTP maintainer's choice?  Hopefully it'll be in the 
archive soon, but looking at https://ftp-master.debian.org/new.html there are 
packages that have been sitting in NEW for almost a year now. It might be a 
case of squeaky wheels—or that some of those packages having a hold-up for a 
particular reason. Probably a bit of both.

Joseph

Processed: bug 1003191 is forwarded to https://gitlab.mister-muffin.de/josch/mmdebstrap/issues/21

[Debian Bug Tracking System]

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

> forwarded 1003191 https://gitlab.mister-muffin.de/josch/mmdebstrap/issues/21
Bug #1003191 [mmdebstrap] mmdebstrap fails when identifying suite by codename
Set Bug forwarded-to-address to 
'https://gitlab.mister-muffin.de/josch/mmdebstrap/issues/21'.
> thanks
Stopping processing here.

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

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

[Mattia Rizzolo]

On Wed, Jan 05, 2022 at 01:52:33PM +0100, Mattia Rizzolo wrote:
> I suppose I'll see how it goes in the coming few days.

So it's not crashing but it's being unbearably slow in gmail, to the
point that I just wasn't able to type a mail there, while throwing one
CPU core to 100%.
Also it was kind go generally slow in several other sites, compared to
v93.  Always compared to v93, it takes far longer (and by far much much
more CPU) to reopen the whole session (I keep ~50 tabs in 3 windows open
all the time, trusting the browser to reopen them where I left when I
close it).

I didn't mesure anything and I don't have any numbers to share, but
that's what I see.


At least, it looks like it has not been leaking as much memory as v93
was (that in this regard was buggier than v90).

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#1003191: mmdebstrap fails when identifying suite by codename

[Johannes Schauer Marin Rodrigues]

Package: mmdebstrap
Severity: serious
Version: 0.8.2-1

Hi,

Quoting Benjamin Drung (2022-01-05 20:59:37)
> I saw that the autopkgtests for bdebstrap fails for mmdebstrap 0.8.2-1
> on Ubuntu jammy:
> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
> 
> amd64 log:
> https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/b/bdebstrap/20220101_132038_11625@/log.gz
> 
> E: nothing got downloaded
> W: listening on child socket failed: Undefined subroutine
> ::Cover::get_coverage called at /usr/bin/mmdebstrap line 105.
> 
> I haven't investigated further.

this is a problem introduced with 0.8.2 and fixing it properly requires a new
apt release with this commit in it:

https://salsa.debian.org/apt-team/apt/-/commit/c6bd75f906c9c782e739ec99f2983407500811bf

On Debian you can work around this by using 'stable', 'unstable', 'testing'
instead of 'bullseye' or 'sid'.

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1003190: tcpslice: CVE-2021-41043: use-after-free in extract_slice()

[Salvatore Bonaccorso]

Source: tcpslice
Version: 1.3-2
Severity: grave
Tags: security upstream
Forwarded: https://github.com/the-tcpdump-group/tcpslice/issues/11
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for tcpslice.

CVE-2021-41043[0]:
| Use after free in tcpslice triggers AddressSanitizer, no other
| confirmed impact.

The impact is not confirmed to be exploitable TTBOMK so far, but the
severity is choosen as better safe than sorry afterwards. Can you
update tcpslice first in unstable? Possibly ideally directly to 1.5
containing other fixes.


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-2021-41043
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41043
[1] https://github.com/the-tcpdump-group/tcpslice/issues/11
[2] 
https://github.com/the-tcpdump-group/tcpslice/commit/030859fce9c77417de657b9bb29c0f78c2d68f4a

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: mark 1003003 as forwarded upstream

[Debian Bug Tracking System]

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

> forwarded 1003003 https://github.com/Qalculate/libqalculate/issues/378
Bug #1003003 [src:libqalculate] libqalculate FTBFS on architectures where char 
is unsigned
Set Bug forwarded-to-address to 
'https://github.com/Qalculate/libqalculate/issues/378'.
> thanks
Stopping processing here.

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

Processed: reopen

[Debian Bug Tracking System]

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

> reopen 1002569
Bug #1002569 {Done: Thomas Dreibholz } [src:rsplib] 
rsplib: FTBFS on mipsel
'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 rsplib/3.4.0-1.
> notfixed 1002569 rsplib/3.4.0-1
Bug #1002569 [src:rsplib] rsplib: FTBFS on mipsel
Ignoring request to alter fixed versions of bug #1002569 to the same values 
previously set
> found 1002569 rsplib/3.4.0-1
Bug #1002569 [src:rsplib] rsplib: FTBFS on mipsel
Marked as found in versions rsplib/3.4.0-1.
>
End of message, stopping processing here.

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

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

[Andres Salomon]

On 1/5/22 13:14, Mattia Rizzolo wrote:

On Wed, Jan 05, 2022 at 01:52:33PM +0100, Mattia Rizzolo wrote:

I suppose I'll see how it goes in the coming few days.

So it's not crashing but it's being unbearably slow in gmail, to the
point that I just wasn't able to type a mail there, while throwing one
CPU core to 100%.
Also it was kind go generally slow in several other sites, compared to
v93.  Always compared to v93, it takes far longer (and by far much much
more CPU) to reopen the whole session (I keep ~50 tabs in 3 windows open
all the time, trusting the browser to reopen them where I left when I
close it).

I didn't mesure anything and I don't have any numbers to share, but
that's what I see.


At least, it looks like it has not been leaking as much memory as v93
was (that in this regard was buggier than v90).



I've been testing on x11 (under xfce). Are you using wayland, by chance?

Bug#1003180: votca-xtp: virtual memory exhausted: Cannot allocate memory

[Sebastian Ramacher]

Source: votca-xtp
Version: 2021.2-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

| [  7%] Building CXX object 
src/libxtp/CMakeFiles/votca_xtp.dir/calculators/eanalyze.cc.o
| cd /<>/obj-mipsel-linux-gnu/src/libxtp && /usr/bin/c++ 
-DBOOST_ALL_NO_LIB -DBOOST_CHRONO_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK 
-DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_TIMER_DYN_LINK 
-Dvotca_xtp_EXPORTS -I/<>/obj-mipsel-linux-gnu/src/libxtp 
-I/<>/src/libxtp -I/<>/include 
-I/usr/include/hdf5/serial -I/<>/obj-mipsel-linux-gnu/include 
-I/<>/obj-mipsel-linux-gnu/include/votca/xtp -isystem 
/usr/include/eigen3 -isystem /usr/include/libint2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O1 -g1 -DNDEBUG -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fopenmp -std=c++14 -MD -MT 
src/libxtp/CMakeFiles/votca_xtp.dir/calculators/eanalyze.cc.o -MF 
CMakeFiles/votca_xtp.dir/calculators/eanalyze.cc.o.d -o 
CMakeFiles/votca_xtp.dir/calculators/eanalyze.cc.o -c 
/<>/src/libxtp/calculators/eanalyze.cc
| virtual memory exhausted: Cannot allocate memory
| make[3]: *** [src/libxtp/CMakeFiles/votca_xtp.dir/build.make:163: 
src/libxtp/CMakeFiles/votca_xtp.dir/aomatrices/aomatrix.cc.o] Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=votca-xtp=mipsel=2021.2-1%2Bb1=1641244404=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

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

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 17:33:34 +
with message-id 
and subject line Bug#999185: fixed in atmel-firmware 1.3-4.2
has caused the Debian Bug report #999185,
regarding atmel-firmware: missing required debian/rules targets build-arch 
and/or build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: atmel-firmware
Source-Version: 1.3-4.2
Done: Ryan Finnie 

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

Debian distribution maintenance software
pp.
Ryan Finnie  (supplier of updated atmel-firmware 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, 28 Dec 2021 22:06:04 -0800
Source: atmel-firmware
Architecture: source
Version: 1.3-4.2
Distribution: unstable
Urgency: medium
Maintainer: Simon Kelley 
Changed-By: Ryan Finnie 
Closes: 999185
Changes:
 atmel-firmware (1.3-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Convert package to debhelper (Closes: #999185)
   * Convert debian/copyright to DEP-5
   * Clean lintian (except for pedantic whitespace)
Checksums-Sha1:
 c83bcf9ba9462c6152c54ca940b44b063874eedf 1763 atmel-firmware_1.3-4.2.dsc
 6f5ba0522ed58f9d0b4963c2a2b3753ff1f4faa2 3720 
atmel-firmware_1.3-4.2.debian.tar.xz
 9a47e5b189e58d77b2cfeee010103949c7489b72 6568 
atmel-firmware_1.3-4.2_amd64.buildinfo
Checksums-Sha256:
 571257b1c2696369fe42ca86ef32ad4d954fbeefb04ea1e5d5d66cd659503e81 1763 
atmel-firmware_1.3-4.2.dsc
 bdb83a442edfca698c7af5eb74ed70f690fc71ff196d6bb5eb9257f9d6863cab 3720 
atmel-firmware_1.3-4.2.debian.tar.xz
 763562b32908ddef19634a3250fc122f9178c748c3650738219cf1b5fff16603 6568 
atmel-firmware_1.3-4.2_amd64.buildinfo
Files:
 b13b3bae91f83fc101be0856a19042b1 1763 non-free/net optional 
atmel-firmware_1.3-4.2.dsc
 c35bef902e4e373f331cc4aab1f1a357 3720 non-free/net optional 
atmel-firmware_1.3-4.2.debian.tar.xz
 e32048e05a180f3804ca0816c3d163d2 6568 non-free/net optional 
atmel-firmware_1.3-4.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE1urL1u5GuDQkjRESFc3aauGRNaIFAmHV0acACgkQFc3aauGR
NaJwSQ/8CPlZzyEiNQ6+cTHqNPKG8gGXKe7ybkBunbxZqSpfDwCo3we/PcSiZFpV
QYxUgGKU928W0nzIuQtV+UZe07lYdAkR1wnpCCT2MD8zGtlzfxZpZ34hZkik/1qM
z/USMAEelxyKV8aslCvTM5Zac/i5Y6gufSWvrDKMeLDDkQi5TDzE3BXkCejcLnR+
yq3MNs5KI9h7nWk8CW1Sc7mlM92tOc4C9rccQB4Z6UaKqKrSuja4CarIfQYqzscq
DXf1P3SxzX13mVK3Khj0hSu7mO+kAU0kctJfBVKlrSIVssFVhOLh8vURKz3+8U17
YVbnDAzGoybPii5hFITmLHmsZYxf2odnoHa8P+yE3rFW8zWLDNJf4E1AUSKXkEd/
dwK1UfwzQISddkfbGTkgcyAkXqaVEChKmrbgAAw6lSGpuLjc+agAPt8LMmsAZRov
TWqXxGKyuA6v35LcSI8zt16JL0U9/BVnq7rQ8s63uVgZlKzXOB81Dl6jffpBxm1S
7+1gIvDyhfqGmXM9dWEt/7Eg3dTO723DpAKJ18/Itw2/EauCQ1uhcjZhlxBEdmBc
G2CgbXtI6IGai9xoVlgBOlsG7TKcpmZl13XcuM7UrSAoc2VAqiyw8coA252D4TVO
R7hkhAJc7AwCIkG1FxvszRFm69JKqW3bi4VemJ0P64FC7Yd4wuU=
=oiBS
-END PGP SIGNATURE End Message ---

Processed: transition: perl 5.34

[Debian Bug Tracking System]

Processing control commands:

> block -1 with 1002093 997267 997189
Bug #1003176 [release.debian.org] transition: perl 5.34
1003176 was not blocked by any bugs.
1003176 was not blocking any bugs.
Added blocking bug(s) of 1003176: 1002093, 997189, and 997267

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

Processed: Re: djangorestframework: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1002396 {Done: Sandro Tosi } [src:djangorestframework] 
djangorestframework: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.10 3.9" returned exit code 13
Added tag(s) patch.

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

Bug#1002396: djangorestframework: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13

[Lukas Märdian]

Package: djangorestframework
Followup-For: Bug #1002396
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
X-Debbugs-Cc: sl...@ubuntu.com
Control: tags -1 patch

Hello Sandro,

you disabled the test_markdown test in your recent upload of
djangorestframework 3.12.4-2 in order to handle the failure described in
https://github.com/encode/django-rest-framework/issues/8160

The same test suite is run as an autopkgtest and I'd like to proposed disabling
this very test in the same way there, too.

In Ubuntu, the attached patch was applied to achieve the following:

  * d/tests/control
- skip test_markdown, which is currently failing; see issue #8160 upstream
  for followups (LP: #1955134)


Thanks for considering the patch.

Cheers,
  Lukas


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

Kernel: Linux 5.13.0-23-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE:en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru djangorestframework-3.12.4/debian/tests/control 
djangorestframework-3.12.4/debian/tests/control
--- djangorestframework-3.12.4/debian/tests/control 2021-12-31 
08:05:52.0 +0100
+++ djangorestframework-3.12.4/debian/tests/control 2022-01-05 
17:47:08.0 +0100
@@ -1,4 +1,7 @@
-Test-Command: cp -r tests $AUTOPKGTEST_TMP && cd $AUTOPKGTEST_TMP && pytest-3
+# Disable test_markdown until the upstream issue is resolved:
+# https://github.com/encode/django-rest-framework/issues/8160
+# Disable it the same way as done in dh_auto_test (debian/rules) at build time
+Test-Command: cp -r tests $AUTOPKGTEST_TMP && cd $AUTOPKGTEST_TMP && pytest-3 
-k 'not test_markdown'
 Depends:
  python3-pygments,
  python3-pytest,

Bug#998553: RC bug in libdbi-drivers

[GCS]

Hi Thorsten,

On Wed, Jan 5, 2022 at 1:09 PM Thorsten Alteholz  wrote:
> are you already working on an upload of libdbi-drivers? Or do you need some 
> help?
 Did a quick check back then, but couldn't find the root cause. I
couldn't devote more time to this issue since then. Maybe tomorrow I
can check it. But of course, any help is appreciated.

Regards,
Laszlo/GCS

Processed: Re: Bug#1003171: calibre: Calibre version used in debian stable does not start

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #1003171 [calibre] calibre: Calibre version used in debian stable does not 
start
Added tag(s) moreinfo.
> severity -1 normal
Bug #1003171 [calibre] calibre: Calibre version used in debian stable does not 
start
Severity set to 'normal' from 'grave'

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

Bug#1003171: calibre: Calibre version used in debian stable does not start

[Julien Cristau]

Control: tag -1 moreinfo
Control: severity -1 normal

On Wed, Jan 05, 2022 at 04:34:34PM +0100, Georges Gouriten wrote:
>   File "/usr/lib/calibre/calibre/devices/smart_device_app/driver.py", line 
> 2044, in 
> from zeroconf import (BadTypeInNameException, _HAS_A_TO_Z,
> ImportError: cannot import name '_HAS_A_TO_Z' from 'zeroconf' 
> (/usr/local/lib/python3.9/dist-packages/zeroconf/__init__.py)
> 
You've got a zeroconf python package installed in /usr/local, outside
the Debian package management, overriding the packaged version, and
breaking things.

Cheers,
Julien

Bug#1003171: calibre: Calibre version used in debian stable does not start

[Georges Gouriten]

Package: calibre
Version: 5.12.0+dfsg-1+deb11u1
Severity: grave
Tags: a11y patch
Justification: renders package unusable

Dear Maintainer,

The version used in debian stable for Calibre does not seem to work.

It creates the following problem:

Traceback (most recent call last):
  File "/usr/bin/calibre", line 20, in 
sys.exit(calibre())
  File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre
main(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 516, in main
run_main(app, opts, args, gui_debug, si)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 523, in run_main
return run_gui(opts, args, app, gui_debug=gui_debug)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 388, in run_gui
run_gui_(opts, args, app, gui_debug)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 398, in run_gui_
from calibre.gui2.ui import Main
  File "/usr/lib/calibre/calibre/gui2/ui.py", line 32, in 
from calibre.customize.ui import available_store_plugins, interface_actions
  File "/usr/lib/calibre/calibre/customize/ui.py", line 18, in 
from calibre.customize.builtins import plugins as builtin_plugins
  File "/usr/lib/calibre/calibre/customize/builtins.py", line 752, in 
from calibre.devices.smart_device_app.driver import SMART_DEVICE_APP
  File "/usr/lib/calibre/calibre/devices/smart_device_app/driver.py", line 
2044, in 
from zeroconf import (BadTypeInNameException, _HAS_A_TO_Z,
ImportError: cannot import name '_HAS_A_TO_Z' from 'zeroconf' 
(/usr/local/lib/python3.9/dist-packages/zeroconf/__init__.py)

I found a patch from gentoo to fix the problem:

--- driver.ori.py   2022-01-05 16:22:28.978735392 +0100
+++ driver.py   2022-01-05 16:23:00.627144736 +0100
@@ -2041,12 +2041,6 @@
 # Copied from https://github.com/jstasiak/python-zeroconf version 0.28.1
 
 
-from zeroconf import (BadTypeInNameException, _HAS_A_TO_Z,
-  _HAS_ONLY_A_TO_Z_NUM_HYPHEN_UNDERSCORE,
-  _HAS_ASCII_CONTROL_CHARS,
-  _HAS_ONLY_A_TO_Z_NUM_HYPHEN)
-
-
 def service_type_name(type_: str, *, allow_underscores: bool = False) -> str:
 """
 Validate a fully qualified service name, instance or subtype. [rfc6763]
@@ -2087,6 +2081,10 @@
 :param type_: Type, SubType or service name to validate
 :return: fully qualified service name (eg: _http._tcp.local.)
 """
+from zeroconf import (BadTypeInNameException, _HAS_A_TO_Z,
+  _HAS_ONLY_A_TO_Z_NUM_HYPHEN_UNDERSCORE,
+  _HAS_ASCII_CONTROL_CHARS,
+  _HAS_ONLY_A_TO_Z_NUM_HYPHEN)
 if not (type_.endswith('._tcp.local.') or type_.endswith('._udp.local.')):
 raise BadTypeInNameException("Type '%s' must end with '._tcp.local.' 
or '._udp.local.'" % type_)

Best regards

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

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

Versions of packages calibre depends on:
ii  calibre-bin  5.12.0+dfsg-1+deb11u1
ii  dpkg 1.20.9
ii  fonts-liberation22.1.3-1
ii  imagemagick  8:6.9.11.60+dfsg-1.3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.3
ii  libjpeg-turbo-progs  1:2.0.6-4
ii  libjxr-tools 1.1-6+b1
ii  optipng  0.7.7-1+b1
ii  poppler-utils20.09.0-3.1
ii  python3  3.9.2-3
ii  python3-apsw 3.34.0-r1-1
ii  python3-bs4  4.9.3-1
ii  python3-chardet  4.0.0-1
ii  python3-chm  0.8.6-2+b3
ii  python3-css-parser   1.0.6-1
ii  python3-cssselect1.1.0+ds-1
ii  python3-cssutils 1.0.2-3
ii  python3-dateutil 2.8.1-6
ii  python3-dbus 1.2.16-5
ii  python3-feedparser   5.2.1-3
ii  python3-html2text2020.1.16-1
ii  python3-html5-parser 0.4.9-3+b3
ii  python3-html5lib 1.1-3
ii  python3-lxml 4.6.3+dfsg-0.1
ii  python3-markdown 3.3.4-1
ii  python3-mechanize1:0.4.5-2
ii  python3-msgpack  1.0.0-6+b1
ii  python3-netifaces0.10.9-0.2+b3
ii  python3-pil  8.1.2+dfsg-0.3
ii  python3-pkg-resources52.0.0-4
ii  python3-py7zr0.11.3+dfsg-1
ii  python3-pygments 2.7.1+dfsg-2.1
ii  python3-pyparsing2.4.7-1
ii  python3-pyqt55.15.2+dfsg-3
ii  python3-pyqt5.qtsvg  5.15.2+dfsg-3
ii  

Bug#992097: marked as done (mlton-compiler is not installable)

[Debian Bug Tracking System]

Your message dated Wed, 5 Jan 2022 10:27:04 -0500
with message-id <20220105152703.6oiflfhgvsbo3...@asteria.rak.ac>
and subject line done
has caused the Debian Bug report #992097,
regarding mlton-compiler is not installable
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.)


-- 
992097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992097
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mlton-compiler
Version: 20180207-1
Severity: grave

mlton-compiler is not installable

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

The following packages have unmet dependencies:
a mlton-compiler : Depends: mlton-basis (= 20180207-1) but 20130715-3 is to be 
installed
E: Unable to correct problems, you have held broken packages.
rak@zeta:~$ apt-cache show mlton-compiler
Package: mlton-compiler
Source: mlton
Version: 20180207-1
Installed-Size: 19501
Maintainer: Wesley W. Terpstra 
Architecture: amd64
Replaces: mlton (<< 20100608-3)
Depends: libc6 (>= 2.27), libgmp10, gcc, libc6-dev, libgmp-dev, mlton-basis (= 
20180207-1), mlton-runtime-native (= 20180207-1) | mlton-runtime
Breaks: mlton (<< 20100608-3)
Description-en: Optimizing compiler for Standard ML - compiler
 MLton is a whole-program optimizing compiler
 for Standard ML.  MLton generates standalone
 executables with excellent runtime performance,
 is SML 97 compliant, and has a complete basis
 library.  MLton has source-level profiling,
 a fast C FFI, an interface to the GNU
 multiprecision library, and lots of useful
 libraries.
 .
 This package includes the compiler itself.
Description-md5: 4d2747f6a7ae5685bdb914296a9ee48a
Multi-Arch: foreign
Homepage: http://mlton.org/
Section: devel
Priority: optional
Filename: pool/main/m/mlton/mlton-compiler_20180207-1_amd64.deb
Size: 3070708
MD5sum: f3e1ee979627decb83d0ed45a2d71eb0
SHA256: 8c9bc43cb7f8304edee95857c1ec914e0605604b2b1864f8096776b70dfe3b40

Package: mlton-compiler
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 17750
Maintainer: Wesley W. Terpstra 
Architecture: amd64
Multi-Arch: foreign
Source: mlton
Version: 20130715-3
Replaces: mlton (<< 20100608-3)
Depends: libc6 (>= 2.14), libgmp10, gcc, libc6-dev, libgmp-dev, mlton-basis (= 
20130715-3), mlton-runtime-native (= 20130715-3) | mlton-runtime
Breaks: mlton (<< 20100608-3)
Description-en: Optimizing compiler for Standard ML - compiler
 MLton is a whole-program optimizing compiler
 for Standard ML.  MLton generates standalone
 executables with excellent runtime performance,
 is SML 97 compliant, and has a complete basis
 library.  MLton has source-level profiling,
 a fast C FFI, an interface to the GNU
 multiprecision library, and lots of useful
 libraries.
 .
 This package includes the compiler itself.
Description-md5: 4d2747f6a7ae5685bdb914296a9ee48a
Homepage: http://mlton.org/

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

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

Versions of packages mlton-compiler depends on:
ii  gcc 4:10.2.1-1
ii  libc6   2.31-13
ii  libc6-dev   2.31-13
ii  libgmp-dev  2:6.2.1+dfsg-1
ii  libgmp102:6.2.1+dfsg-1
ii  mlton-basis 20130715-3
ii  mlton-runtime-native20130715-3
ii  mlton-runtime-x86-64-linux-gnu [mlton-runtime]  20130715-3

mlton-compiler recommends no packages.

mlton-compiler suggests no packages.

-- no debconf information

-- 
|)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature
--- End 

Bug#999517: marked as done (qutip cannot build against numpy >= 1.20)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 15:21:02 +
with message-id 
and subject line Bug#999517: fixed in qutip 4.6.2-3
has caused the Debian Bug report #999517,
regarding qutip cannot build against numpy >= 1.20
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.)


-- 
999517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qutip
Version: 4.6.2-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-numpy121

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64, using numpy 1.21 currently in experimental. This version
will soon be uploaded to unstable.

If you have questions about this, please contact Sandro Tosi
.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean 
> Compiling qutip/cy/brtools_checks.pyx because it changed.
> Compiling qutip/cy/stochastic.pyx because it changed.
> Compiling qutip/cy/sparse_utils.pyx because it changed.
> Compiling qutip/cy/interpolate.pyx because it changed.
> Compiling qutip/cy/mcsolve.pyx because it changed.
> Compiling qutip/cy/cqobjevo.pyx because it changed.
> Compiling qutip/cy/checks.pyx because it changed.
> Compiling qutip/cy/math.pyx because it changed.
> Compiling qutip/cy/inter.pyx because it changed.
> Compiling qutip/cy/ptrace.pyx because it changed.
> Compiling qutip/cy/piqs.pyx because it changed.
> Compiling qutip/cy/cqobjevo_factor.pyx because it changed.
> Compiling qutip/control/cy_grape.pyx because it changed.
> Compiling qutip/cy/spconvert.pyx because it changed.
> Compiling qutip/cy/spmath.pyx because it changed.
> Compiling qutip/cy/brtools.pyx because it changed.
> Compiling qutip/cy/br_tensor.pyx because it changed.
> Compiling qutip/cy/spmatfuncs.pyx because it changed.
> Compiling qutip/cy/graph_utils.pyx because it changed.
> Compiling qutip/cy/heom.pyx because it changed.
> [ 1/20] Cythonizing qutip/control/cy_grape.pyx
> [ 2/20] Cythonizing qutip/cy/br_tensor.pyx
> [ 3/20] Cythonizing qutip/cy/brtools.pyx
> [ 4/20] Cythonizing qutip/cy/brtools_checks.pyx
> [ 5/20] Cythonizing qutip/cy/checks.pyx
> [ 6/20] Cythonizing qutip/cy/cqobjevo.pyx
> [ 7/20] Cythonizing qutip/cy/cqobjevo_factor.pyx
> [ 8/20] Cythonizing qutip/cy/graph_utils.pyx
> [ 9/20] Cythonizing qutip/cy/heom.pyx
> [10/20] Cythonizing qutip/cy/inter.pyx
> [11/20] Cythonizing qutip/cy/interpolate.pyx
> [12/20] Cythonizing qutip/cy/math.pyx
> [13/20] Cythonizing qutip/cy/mcsolve.pyx
> [14/20] Cythonizing qutip/cy/piqs.pyx
> [15/20] Cythonizing qutip/cy/ptrace.pyx
> [16/20] Cythonizing qutip/cy/sparse_utils.pyx
> [17/20] Cythonizing qutip/cy/spconvert.pyx
> [18/20] Cythonizing qutip/cy/spmatfuncs.pyx
> [19/20] Cythonizing qutip/cy/spmath.pyx
> [20/20] Cythonizing qutip/cy/stochastic.pyx
> WARNING: The wheel package is not available.
> /usr/bin/python3.9: No module named pip
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 75, in 
> fetch_build_egg
> subprocess.check_call(cmd)
>   File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
> raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['/usr/bin/python3.9', '-m', 'pip', 
> '--disable-pip-version-check', 'wheel', '--no-deps', '-w', 
> '/tmp/tmpo4aol4ev', '--quiet', 'numpy<1.20,>=1.16.6']' returned non-zero exit 
> status 1.
> 
> The above exception was the direct cause of the following exception:
> 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 239, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 152, in 
> setup
> _install_setup_requires(attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 147, in 
> _install_setup_requires
> dist.fetch_build_eggs(dist.setup_requires)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 806, in 
> fetch_build_eggs
> resolved_dists = pkg_resources.working_set.resolve(
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 766, 
> in resolve
> dist = best[req.key] = env.best_match(
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1051, 
> in best_match
> return self.obtain(req, installer)
>   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1063, 
> in obtain
> return installer(requirement)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 877, in 
> 

Bug#996061: marked as done (gnome-shell-extension-hide-activities: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 14:48:44 +
with message-id 
and subject line Bug#996061: fixed in gnome-shell-extension-hide-activities 41-1
has caused the Debian Bug report #996061,
regarding gnome-shell-extension-hide-activities: does not declare compatibility 
with GNOME Shell 41
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.)


-- 
996061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-hide-activities
Version: 0.00~git20131024.1.6574986-2
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

The metadata.json for this extension doesn't declare compatibility with
GNOME 41. I don't know whether the actual code will need changes or not:
the conservative assumption is that it probably will (so please test).
gnome-shell 41 should be available in experimental soon.

In versions of GNOME Shell up to 3.38, metadata.json didn't matter much,
because validation of extensions' metadata against the installed Shell
version was disabled by default; but since GNOME 40 the default has changed
back to enabling the version check by default, in an effort to avoid
issues caused by outdated extensions remaining enabled. As a result,
GNOME Shell extensions in bookworm should probably have a dependency like:

Depends: gnome-shell (>= x), gnome-shell (<< y~)

where x and y are set according to metadata.json.
gnome-shell-extension-caffeine is a good example of this technique.

When we do the GNOME Shell 41 transition, hopefully soon, we will have
to either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-hide-activities
Source-Version: 41-1
Done: Jonathan Carter 

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-hide-activities package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Jan 2022 16:05:38 +0200
Source: gnome-shell-extension-hide-activities
Architecture: source
Version: 41-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Jonathan Carter 
Closes: 993188 996061
Changes:
 gnome-shell-extension-hide-activities (41-1) unstable; urgency=medium
 .
   * New upstream fork (Closes: #996061, #993188)
   * Upgrade to debhelper-compat (=13)
   * Update standards version to 4.6.0
Checksums-Sha1:
 c426fef56f2d1e9bae313281d35fa4062756075d 2188 
gnome-shell-extension-hide-activities_41-1.dsc
 d8b49d64c19c62dc870cfa6817906f21736a3ae5 2005 
gnome-shell-extension-hide-activities_41.orig.tar.gz
 d606b1e7b102d35fe5b9ca04581221a447c3be2c 1968 
gnome-shell-extension-hide-activities_41-1.debian.tar.xz
 acf09cf78a18f506119270f2e769bdde5ee35535 5804 
gnome-shell-extension-hide-activities_41-1_source.buildinfo
Checksums-Sha256:
 5f4e92b6d308b31b0a2c045b7c625d77ded83e04f94f75b578b0692489d186cd 2188 
gnome-shell-extension-hide-activities_41-1.dsc
 405bb7ae702116871c01b3fe6ba55fd6454cdfbddeffe28dd3fa2a80d69226ef 2005 
gnome-shell-extension-hide-activities_41.orig.tar.gz
 a99599f0dd223949adb3a87a4b38c7a48d58dfc8f0d7332bfe7151ec81e41e1f 1968 
gnome-shell-extension-hide-activities_41-1.debian.tar.xz
 cbe7e34eecfe1fe777c3fae24dafc3ccfa868562eccdc086862807720a485d77 5804 
gnome-shell-extension-hide-activities_41-1_source.buildinfo
Files:
 0e2bc7a4dc075d576e1e0bffa2a5c788 2188 gnome optional 
gnome-shell-extension-hide-activities_41-1.dsc
 806b91ea3d5241666c678607de6d21ae 2005 gnome optional 
gnome-shell-extension-hide-activities_41.orig.tar.gz
 bd08d0499b0571fb10a0d9574161f5f2 1968 gnome optional 
gnome-shell-extension-hide-activities_41-1.debian.tar.xz
 2d5f56f75a127b59a348ea28864d7ca0 5804 gnome optional 
gnome-shell-extension-hide-activities_41-1_source.buildinfo

-BEGIN PGP 

Processed: meshzoo blocks

[Debian Bug Tracking System]

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

> block 997756  by 1000311
Bug #997756 [src:python-meshplex] python-meshplex: FTBFS: sed: no input files
997756 was not blocked by any bugs.
997756 was blocking: 997532
Added blocking bug(s) of 997756: 1000311
> block 998577 by 1000311
Bug #998577 [src:python-meshplex] python-dmsh: FTBFS: build-dependency not 
installable: python3-meshio (< 5)
998577 was not blocked by any bugs.
998577 was not blocking any bugs.
Added blocking bug(s) of 998577: 1000311
> thanks
Stopping processing here.

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

Bug#1001429: marked as done (python-qtpy: (autopkgtest) needs update for python3.10: deprecation warning on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 14:40:15 +
with message-id 
and subject line Bug#1001429: fixed in python-qtpy 2.0.0-1
has caused the Debian Bug report #1001429,
regarding python-qtpy: (autopkgtest) needs update for python3.10: deprecation 
warning on stderr
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.)


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

Source: python-qtpy
Version: 1.9.0-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.10
Control: affects -1 src:python3-defaults

Dear maintainer(s),

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


   passfail
python3-defaults   from testing3.9.8-1
python-qtpyfrom testing1.9.0-3
all others from testingfrom testing

I copied some of the output at the bottom of this report. As the test 
passes otherwise, either suppress deprecation warnings, fix the issue 
and/or use the allow-stderr restriction in autopkgtest to avoid having 
autopkgtest fail on warnings.


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


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

Paul

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

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

Testing with python3.10:
/usr/lib/python3/dist-packages/qtpy/__init__.py:65: DeprecationWarning: 
The distutils package is deprecated and slated for removal in Python 
3.12. Use setuptools or check PEP 632 for potential alternatives

  from distutils.version import LooseVersion



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-qtpy
Source-Version: 2.0.0-1
Done: Picca Frédéric-Emmanuel 

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated python-qtpy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Jan 2022 14:33:31 +0100
Source: python-qtpy
Architecture: source
Version: 2.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Picca Frédéric-Emmanuel 
Closes: 1001429
Changes:
 python-qtpy (2.0.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * Bump debhelper from old 12 to 13.
 .
   [ Håvard Flaget Aasen ]
   * autopkgtest: Add allow-stderr as restriction. Tests fails because of
 a deprecation warning. Closes: #1001429
   * Document Rules-Requires-Root.
 .
   [ Picca Frédéric-Emmanuel ]
   * New upstream version 2.0.0
Checksums-Sha1:
 417cd362ed82020e86f70ef4086ac432d3cea143 2857 python-qtpy_2.0.0-1.dsc
 74a744584c541d31815d3a7bf12876c3d4f7475a 39628 python-qtpy_2.0.0.orig.tar.gz
 ea4b9c41e9a510cc406d9e655564f76f122f9b7f 4624 python-qtpy_2.0.0-1.debian.tar.xz
Checksums-Sha256:
 13eacb52a3dd3c81e4a31bfa2b412070b9785918ffbd687333f9ae7c6c046476 2857 
python-qtpy_2.0.0-1.dsc
 777e333df4d711b2ec9743117ab319dadfbd743a5a0eee35923855ca3d35cd9d 39628 
python-qtpy_2.0.0.orig.tar.gz
 

Processed: 1003165 update found version

[Debian Bug Tracking System]

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

> notfound 1003165 0.23.2-5
Bug #1003165 [src:scikit-learn] scikit-learn in unstable FTBFS on arm64, armel, 
armhf, i386, ppc64el and s390x
No longer marked as found in versions scikit-learn/0.23.2-5.
> thanks
Stopping processing here.

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

Processed: 1003165 affects 1.0.1-1

[Debian Bug Tracking System]

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

> found 1003165 1.0.1-1
Bug #1003165 [src:scikit-learn] scikit-learn in unstable FTBFS on arm64, armel, 
armhf, i386, ppc64el and s390x
Marked as found in versions scikit-learn/1.0.1-1.
> thanks
Stopping processing here.

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

Processed: 1003165 affects opentsne

[Debian Bug Tracking System]

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

> affects 1003165 + opentsne
Bug #1003165 [src:scikit-learn] scikit-learn in unstable FTBFS on arm64, armel, 
armhf, i386, ppc64el and s390x
Added indication that 1003165 affects opentsne
> thanks
Stopping processing here.

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

Bug#1003165: scikit-learn in unstable FTBFS on arm64, armel, armhf, i386, ppc64el and s390x

[Neil Williams]

Source: scikit-learn
Version: 0.23.2-5
Severity: serious
Tags: ftbfs
Justification: Fails to build from source
X-Debbugs-Cc: codeh...@debian.org

The new version of scikit-learn has not migrated to testing because it
has not built on all required architectures. This is now affecting other
packages as the version of scikit-learn in testing is too old to allow
reverse dependencies to build. e.g. opentsne

https://buildd.debian.org/status/package.php?p=scikit-learn

This error crops up in the in-build tests:

=== FAILURES ===
[31m[1m [doctest] sklearn.ensemble._weight_boosting.AdaBoostRegressor 
_[0m
1004 Examples
1005 
1006 >>> from sklearn.ensemble import AdaBoostRegressor
1007 >>> from sklearn.datasets import make_regression
1008 >>> X, y = make_regression(n_features=4, n_informative=2,
1009 ...random_state=0, shuffle=False)
1010 >>> regr = AdaBoostRegressor(random_state=0, n_estimators=100)
1011 >>> regr.fit(X, y)
1012 AdaBoostRegressor(n_estimators=100, random_state=0)
1013 >>> regr.predict([[0, 0, 0, 0]])
Expected:
array([4.7972...])
Got:
array([5.74049295])




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

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

Bug#999155: RC bug in mm and zlib

[Mark Brown]

On Wed, Jan 05, 2022 at 12:57:47PM +0100, Thorsten Alteholz wrote:

> are you already working on an update of mm and zlib? Or do you need some
> help?

They're utterly trivial, I'll get round to them at some point when I do
a batch run through all my packages.  It'd be more effort to integrate
something.


signature.asc
Description: PGP signature

Bug#998446: marked as done (ippsample-data: ships /usr/share/cups/ipptool/* already in cups-ipp-utils)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 13:18:29 +
with message-id 
and subject line Bug#998446: fixed in ippsample 0.0~git20211022.c75af30-2
has caused the Debian Bug report #998446,
regarding ippsample-data: ships /usr/share/cups/ipptool/* already in 
cups-ipp-utils
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.)


-- 
998446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998446
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ippsample-data
Version: 0.0~git20211022.c75af30-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../ippsample-data_0.0~git20211022.c75af30-1_all.deb ...
  Unpacking ippsample-data (0.0~git20211022.c75af30-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ippsample-data_0.0~git20211022.c75af30-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/cups/ipptool/cancel-current-job.test', which 
is also in package cups-ipp-utils 2.3.3op2-7
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ippsample-data_0.0~git20211022.c75af30-1_all.deb

The following files are already shipped in cups-ipp-utils:

usr/share/cups/ipptool/cancel-current-job.test
usr/share/cups/ipptool/create-job-format.test
usr/share/cups/ipptool/create-job-sheets.test
usr/share/cups/ipptool/create-job-timeout.test
usr/share/cups/ipptool/create-job.test
usr/share/cups/ipptool/create-printer-subscription.test
usr/share/cups/ipptool/get-completed-jobs.test
usr/share/cups/ipptool/get-job-attributes.test
usr/share/cups/ipptool/get-job-template-attributes.test
usr/share/cups/ipptool/get-jobs.test
usr/share/cups/ipptool/get-notifications.test
usr/share/cups/ipptool/get-printer-attributes.test
usr/share/cups/ipptool/get-printer-description-attributes.test
usr/share/cups/ipptool/get-printers.test
usr/share/cups/ipptool/get-subscriptions.test
usr/share/cups/ipptool/identify-printer-display.test
usr/share/cups/ipptool/identify-printer-multiple.test
usr/share/cups/ipptool/identify-printer.test
usr/share/cups/ipptool/ipp-1.1.test
usr/share/cups/ipptool/ipp-2.0.test
usr/share/cups/ipptool/ipp-2.1.test
usr/share/cups/ipptool/ipp-2.2.test
usr/share/cups/ipptool/ipp-everywhere.test
usr/share/cups/ipptool/print-job-and-wait.test
usr/share/cups/ipptool/print-job-deflate.test
usr/share/cups/ipptool/print-job-gzip.test
usr/share/cups/ipptool/print-job-hold.test
usr/share/cups/ipptool/print-job-media-col.test
usr/share/cups/ipptool/print-job-password.test
usr/share/cups/ipptool/print-job.test
usr/share/cups/ipptool/print-uri.test
usr/share/cups/ipptool/set-attrs-hold.test
usr/share/cups/ipptool/validate-job.test
usr/share/man/man1/ippeveprinter.1.gz
usr/share/man/man1/ippfind.1.gz
usr/share/man/man1/ipptool.1.gz
usr/share/man/man5/ipptoolfile.5.gz


cheers,

Andreas


cups-ipp-utils=2.3.3op2-7_ippsample-data=0.0~git20211022.c75af30-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ippsample
Source-Version: 0.0~git20211022.c75af30-2
Done: Thorsten Alteholz 

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated ippsample package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Jan 2022 12:59:12 +0100
Source: ippsample
Architecture: source
Version: 0.0~git20211022.c75af30-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Thorsten Alteholz 
Closes: 998446
Changes:
 ippsample (0.0~git20211022.c75af30-2) unstable; urgency=medium
 .
   * debian/control: add Conflicts: with cups-ipp-utils
 (Closes: #998446)
Checksums-Sha1:
 d3ac5e7c5df3799af4eba3cef4b5b59991ab0ea4 2440 
ippsample_0.0~git20211022.c75af30-2.dsc
 

Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)

[Mattia Rizzolo]

On Tue, Jan 04, 2022 at 06:46:46PM -0500, Andres Salomon wrote:
> On 1/4/22 15:15, Mattia Rizzolo wrote:
> > On Tue, Jan 04, 2022 at 02:50:20PM -0500, Andres Salomon wrote:
> > > I pushed a commit to the skip-a11y-checks branch, please give that a try. 
> > > I
> > > need to take a look at other distributions that are shipping chromium to 
> > > see
> > > if they're just disabling DCHECKs outright, or what.
> 
> Just took a look at fedora, arch, and ungoogle-chromium debian packaging.
> They're all setting is_official_build=true, which completely disables those
> DCHECKs. We should probably set it like that as well, although the
> dcheck_is_configurable=true thing that I added to the skip-a11y-checks
> branch should at least allow the DCHECKs to not be fatal - so there's no
> need to restart your build.


So, this one at least didn't crash on me as soon as I started.
Also, it looks like the saved passwords that went away came back, so I
reckon perhaps the local storage format changed in the upgrade, so v93
wasn't able to see them anymore, or something similar.

I suppose I'll see how it goes in the coming few days.


Thank you for your work!

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Bug#965507: marked as done (edac-utils: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 12:33:39 +
with message-id 
and subject line Bug#965507: fixed in edac-utils 0.18-1.1
has caused the Debian Bug report #965507,
regarding edac-utils: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: edac-utils
Source-Version: 0.18-1.1
Done: Stephen Kitt 

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated edac-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Jan 2022 13:18:58 +0100
Source: edac-utils
Architecture: source
Version: 0.18-1.1
Distribution: unstable
Urgency: medium
Maintainer: Yaroslav Halchenko 
Changed-By: Stephen Kitt 
Closes: 965507
Changes:
 edac-utils (0.18-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump to debhelper compatibility level 10. Closes: #965507. Level 10
 is the last level usable with cdbs in packages installing init
 scripts; see #885407 for details.
Checksums-Sha1:
 aeaf97f8e62ae90d3c4dc706f6f6f883e314d0f4 2075 edac-utils_0.18-1.1.dsc
 e18ba5eb899398bf31f75dde0cd5fff1f41e177f 5368 edac-utils_0.18-1.1.debian.tar.xz
 8a40bfd89b0d1b63c0aca98656fc0427d49a5f54 6479 
edac-utils_0.18-1.1_source.buildinfo
Checksums-Sha256:
 f9419adc81dad7973ddf880c0405d04390a66fc6b9001236f28406cbf7fc 2075 
edac-utils_0.18-1.1.dsc
 d274d99b5613271ace54e6daa10b99f5854b67b37779e3f0f42e53591b1f815e 5368 
edac-utils_0.18-1.1.debian.tar.xz
 654cf3c04c4516b86ae0f08609f222686dcdc358314d7214bff71153df74eadf 6479 
edac-utils_0.18-1.1_source.buildinfo
Files:
 a1f9771860fb01a898a4a1316021e0ec 2075 admin extra edac-utils_0.18-1.1.dsc
 5935e6aec1c493a08aea262ea8c14331 5368 admin extra 
edac-utils_0.18-1.1.debian.tar.xz
 fd2448ab706afc5a981188616037090c 6479 admin extra 
edac-utils_0.18-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmHVjQcACgkQgNMC9Yht
g5wCYA//cH4drrJqyOd47UD1Q5RJklH1pRr6IjiORuzyLis8tdsRg5Oaguz6UtLx
qkUFwa2eGJCanajnNGxxNRpz9GJG2iXBYd3SXvnvvVhSS2QsYWEb4/5T1KyXrvPj
A9zqL0v4qwXj5B9cFP8jozH/A/+vUg+HYgCQj275mRO+yLIGS7KgWzbQ9MYV1u89
+cmR110jqMCPZbBHHSMTqk34yDy7w5/mhR26Lg3uvL7heeKr8+2fiUztD7fOEenp
g5aEEAJ4bQOM13k8bfgD8sfOWHf68d+MWu8pmTkIGnoqjM0gKPUav+RmXJWn0Hy5
iwe/rST0ABip2wp79+ZuIGdKmAX6gzrF1pi+gos0bWMpeoV0mhNSuLMLO79tnvjq
OPZO7QFPww/Y55XJPCzJPzbexTxET2ePNwx3C/AH11bYhfNDcUtEd/pvI/gsTDW4
U3nJgZMInZgP8wY/ZO/HPYMtvVTywQzHpVbdOAKm1+Q6YfVwERLbEd5u2QDbcZCY
7VpkBkg6VkSjbf2Tu+ZTPArfZRq+XlTI5ynrYgGglNVfzvCpW1ryqU1h0ESZgsXJ
P67bvpc1OSul2SSabGlxeA5b2DORGieohbak3Whi0PQOolSZoywNBa81GL106XWh

Bug#998553: RC bug in libdbi-drivers

[Thorsten Alteholz]

Hi Laszlo,

are you already working on an upload of libdbi-drivers? Or do you need 
some help?


Best regards
Thorsten

Bug#999155: RC bug in mm and zlib

[Thorsten Alteholz]

Hi Mark,

are you already working on an update of mm and zlib? Or do you need some 
help?


Best regards
Thorsten

Bug#1003045: New information : problem seems to be xorg/wayland conflict.

[Vincent Lefevre]

On 2022-01-03 15:24:47 +0100, copropriete27ruemo...@gmail.com wrote:
> After this update, somme applications such as LibreOffice, but also
> Firefox, do not "work" in an xorg session but do in a Wayland session.

I don't have such issues in xorg (no GNOME on my machine), and
up-to-date sid packages.

> More precisely, these applications run (I can see them in `ps augwx`,
> their icons are marked with a white dot in the Activities panel), but
> do not display anything.

FYI, windows appear partly off-screen here (but this is not new).
Just in case, you should check that windows do not appear completely
off-screen (this has already happened to me in the past): this could
explain why you can see that these applications run, but nothing is
displayed.

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

Bug#984131: flmsg: ftbfs with GCC-11

[Christoph Berg]

> flmsg.cxx: In function ‘void rotate_log(std::string)’:
> flmsg.cxx:2848:24: error: ‘streampos’ is not a member of ‘std::ostringstream’ 
> {aka ‘std::__cxx11::basic_ostringstream’}
>  2848 | ostringstream::streampos p;
>   |^

For the record, the new upstream version 4.0.19 which I just pushed to
git probably works better with gcc-11, but has problems with xmlrpc:

g++ -DHAVE_CONFIG_H -I.  -I. -I./include -I/usr/include/flxmlrpc -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16  -I. 
-I./include   -pipe -Wall -fexceptions -O2 -ffast-math -finline-functions 
-fomit-frame-pointer   -DNDEBUG -I/usr/include/flxmlrpc -g -O2 
-ffile-prefix-map=/srv/projects/afu/flmsg/flmsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -c -o blank-dnd/flmsg-dnd_tab.o `test -f 
'blank-dnd/dnd_tab.cxx' || echo './'`blank-dnd/dnd_tab.cxx
flmsg.cxx: In function ‘int main(int, char**)’:
flmsg.cxx:1927:17: error: ‘set_pname’ is not a member of ‘XmlRpc’
 1927 | XmlRpc::set_pname(pname);
  | ^

(I have no plans to fix this since I don't use flmsg.)

Christoph

Bug#1003003: libqalculate FTBFS on architectures where char is unsigned

[Rik Mills]

Reported here: https://github.com/Qalculate/libqalculate/issues/378

I note that these tests are entirely new in 3.22.0, so there is no
history of them previously passing.

Bug#1000460: marked as done (tf does not trap errors from make)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 09:21:13 +
with message-id 
and subject line Bug#1000460: fixed in tf 1:4.0s1-21.1
has caused the Debian Bug report #1000460,
regarding tf does not trap errors from make
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.)


-- 
1000460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tf
Version: 1:4.0s1-21
Severity: serious
Justification: policy 4.6

When building tf fails, the failure is not propagated and debian/rules
proceeds with dh_auto_install after a failed dh_auto_build. Such
behaviour violates policy section 4.6 and thus this issue deserves
rc-severity.

At least one cause is unix/Makefile line 25.
https://sources.debian.org/src/tf/1:4.0s1-21/unix/Makefile/#L25

There, the result of the sub-make is ignored.

Helmut
--- End Message ---
--- Begin Message ---
Source: tf
Source-Version: 1:4.0s1-21.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated tf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 23 Dec 2021 07:50:06 +0200
Source: tf
Architecture: source
Version: 1:4.0s1-21.1
Distribution: unstable
Urgency: medium
Maintainer: Jan Niehusmann 
Changed-By: Adrian Bunk 
Closes: 1000460
Changes:
 tf (1:4.0s1-21.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * unix/Makefile: Trap errors from make. (Closes: #1000460)
Checksums-Sha1:
 561e546c49004d41b2969135d3543e9a5d7485f6 1674 tf_4.0s1-21.1.dsc
 3c2889282ad178320480fe9a3a8b91ea742c590d 13048 tf_4.0s1-21.1.debian.tar.xz
Checksums-Sha256:
 1cfa588e179cb3c4fcbefbfcbca1c49d71df14560768463c6e817d87a68acae3 1674 
tf_4.0s1-21.1.dsc
 aef6be16bd4a7975c7b28c0ef451387dd12c825a698c98f12d9cfe8211639388 13048 
tf_4.0s1-21.1.debian.tar.xz
Files:
 f8eac8f8144c7c17c78fedc0c8174129 1674 games optional tf_4.0s1-21.1.dsc
 821fbb26fc6d890c5e3a290c63fecef1 13048 games optional 
tf_4.0s1-21.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHEDzsACgkQiNJCh6LY
mLHvEw/9H1YxwRuwJFSXk7ZEkNyJWSZGJBxpWUxjtIt8nlr6Cobt3xNbv9Sy3p3P
F/3xjc4p7cr9cFl/xfzX8bLi3lEBegP+LOZDwm4HtPcu3sK7randBEcE3J2TaVr+
eJyQomNQrjOKLqyAWDvmXQlACQ6psHcEfwbPcUM4Xklemr5jYP7nMXmrvzXI7TBR
puIMrSlHfVS81iZ4JBTS2vntdluteqhBoNfLP6uC7XlUJt1uN1VyEQGqaSfU6LUk
4+7CQKKaokjCSIRU/gNLmsZSALzB7baOVbKtd8VC9mt7GKX3oGmZvPxoVzSFvtfQ
Mm0eMHxpPLTMd8TLDlRqx2kxkgN5RXxJxFQKHNoTgEmAgGxLai6cXUxrUb6cZDIE
NwSTIshrP9Wr02YkZGdAzp0CNZbHYjydGHhRyg2Ueco6yNZzs09BPkTYfS52wBMB
5YNpuGctd69RWlnAOpYiuZKx+yiHytCnWKtrT3kb3LGDUx8EAvpO9qZImJkNJIVp
Ka6OnP3ojH0knwhiZOfVcsk0y5zauw/iBa6hQHlp/GNkqwmjisbJM3wN2zp4v/+8
1HpNld5Ch7jGc1qhnQ6xlrsfnReo3oQfTSsDy2aQoHkHA2fC5GTrm0FrEFIDoACm
L1XjC70Yu3IumrtGM7Qy1L/zATS0bI/E8fqjNTKCUUJ497+dJZE=
=1ZEh
-END PGP SIGNATURE End Message ---

Bug#1002098: marked as done (ruby-gon: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 08:39:18 +
with message-id 
and subject line Bug#1002098: fixed in ruby-gon 6.4.0-2
has caused the Debian Bug report #1002098,
regarding ruby-gon: FTBFS: ERROR: Test "ruby2.7" failed:   ArgumentError
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.)


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

Hi,

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


Relevant part (hopefully):
>   ArgumentError:
> wrong number of arguments (given 0, expected 3)
>   # 
> /usr/share/rubygems-integration/all/gems/actionview-6.1.4.1/lib/action_view/base.rb:230:in
>  `initialize'
>   # ./spec/gon/global_spec.rb:36:in `new'
>   # ./spec/gon/global_spec.rb:36:in `block (3 levels) in '
> 
> Finished in 0.12069 seconds (files took 0.38329 seconds to load)
> 72 examples, 31 failures
> 
> Failed examples:
> 
> rspec ./spec/gon/basic_spec.rb:96 # Gon#include_gon outputs correct js with 
> an integer
> rspec ./spec/gon/basic_spec.rb:103 # Gon#include_gon outputs correct js with 
> a string
> rspec ./spec/gon/basic_spec.rb:111 # Gon#include_gon outputs correct js with 
> a script string
> rspec ./spec/gon/basic_spec.rb:124 # Gon#include_gon outputs correct js with 
> an integer and type
> rspec ./spec/gon/basic_spec.rb:134 # Gon#include_gon outputs correct js with 
> an integer, camel-case and namespace
> rspec ./spec/gon/basic_spec.rb:142 # Gon#include_gon outputs correct js with 
> camel_depth = :recursive
> rspec ./spec/gon/basic_spec.rb:150 # Gon#include_gon outputs correct js with 
> camel_depth = 2
> rspec ./spec/gon/basic_spec.rb:158 # Gon#include_gon outputs correct js for 
> an array with camel_depth = :recursive
> rspec ./spec/gon/basic_spec.rb:166 # Gon#include_gon outputs correct key with 
> camel_case option set alternately 
> rspec ./spec/gon/basic_spec.rb:176 # Gon#include_gon outputs correct js with 
> an integer and without tag
> rspec ./spec/gon/basic_spec.rb:184 # Gon#include_gon outputs correct js 
> without variables, without tag and gon init if before there was data
> rspec ./spec/gon/basic_spec.rb:193 # Gon#include_gon outputs correct js 
> without variables, without tag and gon init
> rspec ./spec/gon/basic_spec.rb:199 # Gon#include_gon outputs correct js 
> without variables, without tag, gon init and an integer
> rspec ./spec/gon/basic_spec.rb:207 # Gon#include_gon outputs correct js 
> without cdata, without type, gon init and an integer
> rspec ./spec/gon/basic_spec.rb:218 # Gon#include_gon outputs correct js with 
> type text/javascript
> rspec ./spec/gon/basic_spec.rb:222 # Gon#include_gon outputs correct js with 
> namespace check
> rspec ./spec/gon/basic_spec.rb:226 # Gon#include_gon outputs correct js 
> without namespace check
> rspec ./spec/gon/basic_spec.rb:237 # Gon#include_gon without a current_gon 
> instance does not raise an exception
> rspec ./spec/gon/basic_spec.rb:241 # Gon#include_gon without a current_gon 
> instance outputs correct js
> rspec ./spec/gon/basic_spec.rb:245 # Gon#include_gon without a current_gon 
> instance outputs correct js with init
> rspec ./spec/gon/basic_spec.rb:262 # Gon#include_gon_amd is included in 
> ActionView::Base as a helper
> rspec ./spec/gon/basic_spec.rb:266 # Gon#include_gon_amd outputs correct js 
> without variables
> rspec ./spec/gon/basic_spec.rb:274 # Gon#include_gon_amd outputs correct js 
> with an integer
> rspec ./spec/gon/basic_spec.rb:284 # Gon#include_gon_amd outputs correct 
> module name when given a namespace
> rspec ./spec/gon/global_spec.rb:40 # Gon::Global#include_gon outputs correct 
> js with an integer
> rspec ./spec/gon/global_spec.rb:50 # Gon::Global#include_gon outputs correct 
> js with an integer and integer in Gon
> rspec ./spec/gon/global_spec.rb:62 # Gon::Global#include_gon outputs correct 
> js with a string
> rspec ./spec/gon/global_spec.rb:72 # Gon::Global#include_gon outputs correct 
> js with a script string
> rspec ./spec/gon/global_spec.rb:87 # Gon::Global#include_gon outputs correct 
> js with a unicode line separator
> rspec ./spec/gon/global_spec.rb:97 # Gon::Global#include_gon outputs locally 
> overridden value
> rspec ./spec/gon/global_spec.rb:108 # Gon::Global#include_gon includes the 
> tag attributes in the script tag
> 
> /usr/bin/ruby2.7 
> 

Processed: tagging 984373

[Debian Bug Tracking System]

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

> tags 984373 + fixed-upstream
Bug #984373 [src:ucommon] ucommon: ftbfs with GCC-11
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1003114: marked as done (python3-ccdproc: ships /usr/lib/python3/dist-packages/benchmarks/*.py)

[Debian Bug Tracking System]

Your message dated Wed, 05 Jan 2022 08:34:21 +
with message-id 
and subject line Bug#1003114: fixed in ccdproc 2.3.0-2
has caused the Debian Bug report #1003114,
regarding python3-ccdproc: ships /usr/lib/python3/dist-packages/benchmarks/*.py
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.)


-- 
1003114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-ccdproc
Version: 2.3.0-1
Severity: serious

Hi,

python3-ccdproc started to ship /usr/lib/python3/dist-packages/benchmarks/*.py
causing file conflicts with packages doing the same mistake.

These should probably not be shipped in the package at all or moved to a
package specific subdirectory.


Andreas
--- End Message ---
--- Begin Message ---
Source: ccdproc
Source-Version: 2.3.0-2
Done: Ole Streicher 

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

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

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated ccdproc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 05 Jan 2022 08:50:08 +0100
Source: ccdproc
Architecture: source
Version: 2.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Closes: 1003114
Changes:
 ccdproc (2.3.0-2) unstable; urgency=medium
 .
   * Remove benchmarks subdir (Closes: #1003114)
   * Remove obsolete special test data handling
Checksums-Sha1:
 f3bb1c239eafba7774895d2729edce1bc47287a6 2215 ccdproc_2.3.0-2.dsc
 c0339f7b0925e01d6f5149ddb54528bf8db5a563 3948 ccdproc_2.3.0-2.debian.tar.xz
Checksums-Sha256:
 d89dc2c1b0989391451de80b104a995575375da030607c51ab74588c07a084b4 2215 
ccdproc_2.3.0-2.dsc
 9f175ee4e4bd17061fa1c06f87918ec8852be396f0854023db2ce09596ccaba0 3948 
ccdproc_2.3.0-2.debian.tar.xz
Files:
 fe3457cd251c503bfe6708310caf4b8a 2215 python optional ccdproc_2.3.0-2.dsc
 013653c1822cf050756425ce039fee31 3948 python optional 
ccdproc_2.3.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmHVUZ4ACgkQcRWv0HcQ
3Pd33BAAllgaf+P0XsjLB8nI4Trnv5Z2U5UE8e1wMla/9Bfx/9IYMTJ5Lk0xYqDN
knYsYXZDyhcetev9Yxg6U00kcuv8DddM3DtH+OUz7ph0KTDfO0fgJ+WI+Xvifq25
SzYwrJDGecp9+zZPkq4Qdqg/kxrqGavKkqM4BhChT6sWmUR/F2vhz6flhBq0w+gL
Xob/WFfgXVH/TQ5nOTOtkS9hXfj1EayP7YdERLtWLpVE9xcigkOoIoNHS565XHH0
fGhMQdj/+JJGIegtUOc2JJnoh38RSYCUhcMAQWcWA8YafYV0krkZ2yjad+LSTG/q
J+qSL5BoIUlbVu8JHD+Z1VndNh6oxUlhbuYB8Xmoct8yCsgRe/EZ5oru5it7xFYD
yPnLVu5BCcsQxwrb93pFdEPgAd+7tX4SGsx2V4+QOBmEl22O4wSrDRQqG40Krcnb
GlMkd63klrXR+TEYh2kuqL+d82PEIFbt04X5VgGhtrWQULlsEexkRzShRoy6weKo
DVbkTdDr+tdnqTC521DLDU2OURk6L263vAd4lCLpyXklcpku/dSpSwPbrGm03/mq
D7s4OaD353+af4ZkbHhpNG4XGQkiWtvsVDws75gwlPH0H3Os8EEzg5ExmwZxkhFs
l/Wi33YmPEz12lOElijMD+UCs0hbRGow8img9Lq0nCnzQiY4QAI=
=diKf
-END PGP SIGNATURE End Message ---

Bug#1002098: marked as pending in ruby-gon

[Cédric Boutillier]

Control: tag -1 pending

Hello,

Bug #1002098 in ruby-gon 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/ruby-team/ruby-gon/-/commit/bebf7e5a6e9ac73446e7cafa1bc3d525b609b7c0


Import upstream patch to fix test suite with ruby3.0 (Closes: #1002098)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002098

Processed: Bug#1002098 marked as pending in ruby-gon

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002098 [src:ruby-gon] ruby-gon: FTBFS: ERROR: Test "ruby2.7" failed:  
 ArgumentError
Added tag(s) pending.

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