Bug#1000986: Montage-wrapper does not play well with astropy 5.0

[Ole Streicher]

Package: python3-montage-wrapper
Version: 0.9.9-4
Severity: serious

The package fails in CI test with astropy 5.0. Since it is abandoned 
upstream, I do not intend to fix this, but will remove the package 
(unless someone else is going to take it over).


The "montage" package now comes with its own wrapper, python3-montagepy. 
Please migrate to this package.


Ole

Bug#1000753: marked as done (poliastro FTBFS: plugin flit failed with: Use [project] table for metadata or [tool.flit.metadata], not both)

[Debian Bug Tracking System]

Your message dated Thu, 02 Dec 2021 07:18:39 +
with message-id 
and subject line Bug#1000753: fixed in poliastro 0.15.2-4
has caused the Debian Bug report #1000753,
regarding poliastro FTBFS: plugin flit failed with: Use [project] table for 
metadata or [tool.flit.metadata], not both
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.)


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

Package: python3-poliastro
Version: 0.15.2-3
Severity: serious

Fails to build with the error

E: pybuild pybuild:354: build: plugin flit failed with: Use [project] 
table for metadata or [tool.flit.metadata], not both.
--- End Message ---
--- Begin Message ---
Source: poliastro
Source-Version: 0.15.2-4
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
poliastro, 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.
Ole Streicher  (supplier of updated poliastro 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, 02 Dec 2021 07:55:02 +0100
Source: poliastro
Architecture: source
Version: 0.15.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 1000753
Changes:
 poliastro (0.15.2-4) unstable; urgency=medium
 .
   [ Scott Kitterman ]
   * Drop debian/patches/Revert-the-adoption-PEP-621-metadata.patch
 (Closes: #1000753)
Checksums-Sha1:
 19fbf1d50008cd3b8e6de4c10e3ddf108dbaf498 2371 poliastro_0.15.2-4.dsc
 f8d5fff608d07da690f2e73814569b64badbf85b 5528 poliastro_0.15.2-4.debian.tar.xz
Checksums-Sha256:
 7453c56eff9e1090c42fab5910b36aab30c4a552114316cd2afe380f9ff54ec9 2371 
poliastro_0.15.2-4.dsc
 85789c04cd0e89da8d412fa4bb6923657a5460b0e721e506bf73888331a11836 5528 
poliastro_0.15.2-4.debian.tar.xz
Files:
 20cda9959752227fef8c72e4d17fd82a 2371 python optional poliastro_0.15.2-4.dsc
 0d16db1513d9bb0321898ea5876af6c9 5528 python optional 
poliastro_0.15.2-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmGocIYACgkQcRWv0HcQ
3PfgExAAjINs6q//IwpscypPu9BYhIUp6LI2PfURrCLxSfqk74so2biEA12i5Ju7
FWzlnVMS2VuGVO9P4S7o48VvShaTD1h8eFi2LrxOjHEBU1JIv2TKpNqF4c0WL6ZZ
f+FP+NjUpXK8WeuFvw+MEw/k/89clRagGnlPtZWXqXTI3ROTHB3ydJHYiWhrRSRs
iFjVm0wwoOUZNpmcZbYwazlc4xciufk4LRwqhiwIJVbddKeKFs9L25NE3pM8bHnk
m4WEGGtKeu2bZyQ0+lQ85OOkScmXjelEwqYDgg7NnsxejtKwxgmUs5u2f/wI0KXA
u5LveaSU2rjUxwyEskgRviXhYASJhhblRQA904q6ZrmlsLkOirqgp/VpNtY/d4mw
UhjunXkHL4CUqLBhZA8BMe3YI7i1w0kbMrGgZ6qNnNGNdnUhP7hMi37QfZ/Hz1eR
OQNHUKysAV3IJ3cRKiXmJXk5hlC1Luiyu964+e1e1mBryxhSMLxEo3DEyhx5Xg9f
Do8BsIfMa76x7rxcwErS7KF++6K9ZvqIq2tBczxi83Ny0Ja2VtOSl9+OtBkOyoRO
DCssAhTVgqqel5gUH1lzfs56+tgiX+fZbaU7AUTK3dkLunRffMamp7Z8SeNxqeds
2JvptkjvsMBDW7jzwY5CSJK63N4pCm1baKKFiR8LNGGDOEMvcIQ=
=6trw
-END PGP SIGNATURE End Message ---

Bug#1000339: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'

[Andreas Tille]

Hi Robert,

Am Wed, Dec 01, 2021 at 10:59:45PM -0800 schrieb Robert J. Hijmans:
> On Tue, Nov 30, 2021 at 10:46 PM Andreas Tille  wrote:
> 
> > > raster 3-5.2 depends on terra; but it does not specify which version of
> > > terra. I believe it needs to be terra 1.4-11 to not get this error.
> >
> > Is it *exactly* this version or >= 1.4-11?  We had once packaged terra
> > just for raster startung with 1.4-11 and than moved on upgrading it to
> > the current version 1.4-22.
> 
> Sorry about being not very precise, I should have said >= 1.4-11
> 1.4-22 is even better

OK.
 
> I now wonder whether it is the order of installation. Can you install
> raster *after* installing terra? That might help in getting the namespaces
> work as they should.

The Debian autopkgtest procedure is to install *all* needed dependencies
but in a random order (so there is no way I'm aware of to specify one
package before others are installed).  Could you please be more verbose
in how far you consider the sequence in which the R code is installed is
relevant for the test?  I mean after installing all the R packages the
files and directories are equal in any case since the files in /usr are
identical to the content inside the packages no matter in what sequence
the code was installed.

> If not, I will try to make some dockers to see if I can reproduce this.
 
This would be really helpful. 

Kind regards

 Andreas.
 
> > > From what you sent I cannot see which version of terra is installed, but
> > I
> > > am guessing it is an earlier version. Is that something you can check?
> >
> > There was never any earlier version than 1.4-11 in Debian.  The Debian
> > bug report links to a full log of the test[1] which installs
> >
> > ...
> > Get:117 http://deb.debian.org/debian testing/main amd64 r-cran-terra
> > amd64 1.4-11-2 [2,358 kB]
> > Get:118 http://deb.debian.org/debian unstable/main amd64 r-cran-raster
> > amd64 3.5-2-1 [3,063 kB]
> > ...
> >
> > > I can dig a bit more if needed, please let me know.
> >
> > Your help would be really appreciated
> >
> > Andreas.
> >
> >
> > [1]
> > https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-satellite/16823806/log.gz
> >
> > --
> > http://fam-tille.de
> >

> ___
> R-pkg-team mailing list
> r-pkg-t...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team


-- 
http://fam-tille.de

Bug#1000339: r-cran-raster breaks r-cran-satellite autopkgtest: unable to find an inherited method for function 'extend'

[Robert J. Hijmans]

On Tue, Nov 30, 2021 at 10:46 PM Andreas Tille  wrote:

> Dear Robert,
>
> Am Tue, Nov 30, 2021 at 09:18:18PM -0800 schrieb Robert J. Hijmans:
> > Dear Andreas,
> >
> > raster 3-5.2 depends on terra; but it does not specify which version of
> > terra. I believe it needs to be terra 1.4-11 to not get this error.
>
> Is it *exactly* this version or >= 1.4-11?  We had once packaged terra
> just for raster startung with 1.4-11 and than moved on upgrading it to
> the current version 1.4-22.
>

Sorry about being not very precise, I should have said >= 1.4-11
1.4-22 is even better

I now wonder whether it is the order of installation. Can you install
raster *after* installing terra? That might help in getting the namespaces
work as they should.

If not, I will try to make some dockers to see if I can reproduce this.



> > From what you sent I cannot see which version of terra is installed, but
> I
> > am guessing it is an earlier version. Is that something you can check?
>
> There was never any earlier version than 1.4-11 in Debian.  The Debian
> bug report links to a full log of the test[1] which installs
>
> ...
> Get:117 http://deb.debian.org/debian testing/main amd64 r-cran-terra
> amd64 1.4-11-2 [2,358 kB]
> Get:118 http://deb.debian.org/debian unstable/main amd64 r-cran-raster
> amd64 3.5-2-1 [3,063 kB]
> ...
>
> > I can dig a bit more if needed, please let me know.
>
> Your help would be really appreciated
>
> Andreas.
>
>
> [1]
> https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-satellite/16823806/log.gz
>
> --
> http://fam-tille.de
>

Bug#995353: marked as done (ruby-protocol-http: autopkgtest regression on armhf and i386 (both 32 bits))

[Debian Bug Tracking System]

Your message dated Thu, 02 Dec 2021 07:58:28 +0100
with message-id <91d16169b8e7a83f8c38996328a24ee4bf52867f.ca...@debian.org>
and subject line Fixed
has caused the Debian Bug report #995353,
regarding ruby-protocol-http: autopkgtest regression on armhf and i386 (both 32 
bits)
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.)


-- 
995353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-protocol-http
Version: 0.22.5-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of ruby-protocol-http the autopkgtest of
ruby-protocol-http fails in testing when that autopkgtest is run with
the binary packages of ruby-protocol-http from unstable. It passes when
run with only packages from testing. I noticed that in testing, the test
is actually skipped, so your current test is sort of new. In tabular form:

   passfail
ruby-protocol-http from testing0.22.5-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. I notice that
the test that fails on armhf is about memory. The test *may* be fooled
by the shear amount of memory available on this system: 250 GB. However,
i386 also fails, so I suspect an issue with 32 bits in the test or binary.

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=ruby-protocol-http

https://ci.debian.net/data/autopkgtest/testing/armhf/r/ruby-protocol-http/15629689/log.gz



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-rspec-memory
Source-Version: 1.0.2-3
Done: Daniel Leidert 

Now that the fixed version of ruby-rspec-memory migrated to Testing, the
autopkgtest failures of ruby-protocol-http are gone (I restarted the failed
ones). They were caused by what has been described in #1000835.

Closing this bug report.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert


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

Bug#1000983: ocaml-mm FTBFS on !am64/arm64/riscv64

[Stéphane Glondu]

Le 02/12/2021 à 07:45, Adrian Bunk a écrit :
> Source: ocaml-mm
> Version: 0.7.2-1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/logs.php?pkg=ocaml-mm=0.7.2-1
> 
> ...
> Supported external libraries:
>   - Alsa  : true
>   - AO: true
>   - Mad   : true
>   - OSS   : false
>   - Pulseaudio: true
>   - SDL   : true
>   - Theora: true
> ...
> Error: Library "mm.oss" in _build/default/external is hidden (unsatisfied
> 'enabled_if').
> Hint: try:
>   dune external-lib-deps --missing @@default
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1

There is a similar issue in ocaml-dssi, which I chose to fix by removing
the enabled_if directive altogether:

https://salsa.debian.org/ocaml-team/ocaml-dssi/-/blob/master/debian/patches/0001-Remove-enable_if-directive.patch


Cheers,

-- 
Stéphane

Bug#1000983: ocaml-mm FTBFS on !am64/arm64/riscv64

[Adrian Bunk]

Source: ocaml-mm
Version: 0.7.2-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=ocaml-mm=0.7.2-1

...
Supported external libraries:
  - Alsa  : true
  - AO: true
  - Mad   : true
  - OSS   : false
  - Pulseaudio: true
  - SDL   : true
  - Theora: true
...
Error: Library "mm.oss" in _build/default/external is hidden (unsatisfied
'enabled_if').
Hint: try:
  dune external-lib-deps --missing @@default
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1

Processed: closing 1000359

[Debian Bug Tracking System]

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

> close 1000359
Bug #1000359 [src:python-biopython] FTBFS: test failure: External MBEDTLS 
version mismatch
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1000812: pyrle: import fails on Python 3.10

[Nilesh Patra]

On Mon, 29 Nov 2021 20:35:40 +0100 Andreas Tille  wrote:
> Am Mon, Nov 29, 2021 at 11:36:33PM +0530 schrieb Nilesh Patra:
> > I rebuilt with python3.10, and now error is this.
> > Something wrong with pandas?
> 
> As far as I understood we need to wait for pandas 1.3 to work
> with Python3.10.

I retried autopkgtest now, and it still seems a non-bug with pyrle.
@Rebecca, please re-assign this bug to relevant package.

autopkgtest [11:57:49]: test autodep8-python3: [---
Testing with python3.10:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/pyrle/__init__.py", line 1, in 
from pyrle.rle import Rle
  File "/usr/lib/python3/dist-packages/pyrle/rle.py", line 13, in 
from tabulate import tabulate
  File "/usr/lib/python3/dist-packages/tabulate.py", line 16, in 
from collections import Iterable
ImportError: cannot import name 'Iterable' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)

"""
Minimal example to reproduce:

$ python3.10  
Python 3.10.0+ (default, Nov 17 2021, 06:49:13) [GCC 11.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from tabulate import tabulate
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/tabulate.py", line 16, in 
from collections import Iterable
ImportError: cannot import name 'Iterable' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)
"""

$ apt policy python3.10
python3.10:
  Installed: 3.10.0-5
  Candidate: 3.10.0-5
  Version table:
 *** 3.10.0-5 500
500 http://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status


signature.asc
Description: PGP signature

Bug#999773: marked as done (ksh93u+m: missing Breaks+Replaces: ksh (<< 20210511))

[Debian Bug Tracking System]

Your message dated Thu, 2 Dec 2021 10:30:00 +0530
with message-id 
and subject line Experimental package has been removed
has caused the Debian Bug report #999773,
regarding ksh93u+m: missing Breaks+Replaces: ksh (<< 20210511)
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.)


-- 
999773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ksh93u+m
Version: 1.0.0~beta.1-1
Severity: serious
Tags: patch
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid 'installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../ksh_20210510-93u+m-1.0.0~beta.1-1_amd64.deb ...
  Unpacking ksh (20210510-93u+m-1.0.0~beta.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ksh_20210510-93u+m-1.0.0~beta.1-1_amd64.deb (--unpack):
   trying to overwrite '/bin/ksh93', which is also in package ksh93u+m 
1.0.0~beta.1-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ksh_20210510-93u+m-1.0.0~beta.1-1_amd64.deb

The overwrite error is actually the other way around since ksh93u+m
in sid is newer than ksh in experimental.
Therefore please add 
  Breaks+Replaces: ksh (<< 20210511)
to ksh93u+m to ensure clean upgrades from whatever ksh version
was installed.

You also need to use an increasing version for
'dh_gencontrol -- -v...', otherwise subsequent (binary) uploads that
have a binary package with same version as already in the archive will
be rejected.
See the attached patch for my suggested solution.

You will have to file RM bugs against ftp.debian.org to get the obsolete
src:ksh package removed from sid and experimental.


cheers,

Andreas
diff -Nru ksh93u+m-1.0.0~beta.1/debian/control 
ksh93u+m-1.0.0~beta.1/debian/control
--- ksh93u+m-1.0.0~beta.1/debian/control2021-09-05 15:14:36.0 
+0200
+++ ksh93u+m-1.0.0~beta.1/debian/control2021-11-16 14:00:52.0 
+0100
@@ -11,8 +11,8 @@
 
 Package: ksh93u+m
 Architecture: any
-Replaces: ksh (<= 2020.0.0+really93u+20120801-10)
-Breaks: ksh (<= 2020.0.0+really93u+20120801-10)
+Replaces: ksh (<< 20210511)
+Breaks: ksh (<< 20210511)
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Suggests: binfmt-support
 Description: AT KornShell
diff -Nru ksh93u+m-1.0.0~beta.1/debian/rules ksh93u+m-1.0.0~beta.1/debian/rules
--- ksh93u+m-1.0.0~beta.1/debian/rules  2021-09-05 15:14:36.0 +0200
+++ ksh93u+m-1.0.0~beta.1/debian/rules  2021-11-16 14:00:52.0 +0100
@@ -7,6 +7,7 @@
 export TZ=GMT
 
 include /usr/share/dpkg/buildflags.mk
+include /usr/share/dpkg/pkg-info.mk
 
 export CCFLAGS+=$(shell dpkg-buildflags --get CFLAGS)
 export CCFLAGS+=$(shell dpkg-buildflags --get CPPFLAGS)
@@ -34,8 +35,8 @@
dh_installchangelogs NEWS
 
 override_dh_gencontrol:
-   dh_gencontrol --package=ksh93u+m
-   dh_gencontrol --package=ksh -- -v20210511
+   dh_gencontrol --package=ksh -- 
-v20210511+$(DEB_VERSION_UPSTREAM_REVISION)
+   dh_gencontrol --remaining-packages
 
 clean:
dh_testdir


ksh93u+m=1.0.0~beta.1-1_ksh=20210510-93u+m-1.0.0~beta.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
ksh/experimental package has been removed from the archive [1] to address
this issue.

Anuradha

[1] - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999814--- End Message ---

Processed: fixed 984403 in 4.2.3-2

[Debian Bug Tracking System]

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

> fixed 984403 4.2.3-2
Bug #984403 {Done: Stephen Kitt } [src:warzone2100] 
warzone2100: ftbfs with GCC-11
Marked as fixed in versions warzone2100/4.2.3-2.
> thanks
Stopping processing here.

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

Processed: tagging 996052 ...

[Debian Bug Tracking System]

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

> tags 996052 + patch
Bug #996052 [gnome-shell-extension-disconnect-wifi] 
gnome-shell-extension-disconnect-wifi: does not declare compatibility with 
GNOME Shell 41
Added tag(s) patch.
> forwarded 996052 https://github.com/kgshank/gse-disconnect-wifi/pull/35 
> https://github.com/kgshank/gse-disconnect-wifi/issues/34
Bug #996052 [gnome-shell-extension-disconnect-wifi] 
gnome-shell-extension-disconnect-wifi: does not declare compatibility with 
GNOME Shell 41
Changed Bug forwarded-to-address to 
'https://github.com/kgshank/gse-disconnect-wifi/pull/35 
https://github.com/kgshank/gse-disconnect-wifi/issues/34' from 
'https://github.com/kgshank/gse-disconnect-wifi/pull/35'.
> thanks
Stopping processing here.

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

Processed: tagging 996052

[Debian Bug Tracking System]

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

> tags 996052 + fixed-upstream
Bug #996052 [gnome-shell-extension-disconnect-wifi] 
gnome-shell-extension-disconnect-wifi: does not declare compatibility with 
GNOME Shell 41
Ignoring request to alter tags of bug #996052 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#999507: marked as done (rust-tokio-signal, (build-)dependencies unsatisfiable, abandoned upstream, should this package be removed.)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:21:01 +
with message-id 
and subject line Bug#999736: Removed package(s) from unstable
has caused the Debian Bug report #999507,
regarding rust-tokio-signal, (build-)dependencies unsatisfiable, abandoned 
upstream, should this package be removed.
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.)


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

Package: rust-tokio-signal
Version: 0.2.7-2
Severity: serious

rust-tokio-signal (build-)depends on version 0.1 of rust-futures. Upstream 
seems to
have abandoned the project, there was an alpha release supporting futures 0.2, 
but
the code appears to have been removed from the tokio git repository. So I 
presume
it is abandoned upstream.

There are no reverse dependencies in testing, there is a single reverse 
dependency
in unstable which is rc buggy and also appears to be abandoned upstream.

If there are no objections in a few weeks, I intend to file a removal request.
--- End Message ---
--- Begin Message ---
Version: 0.2.7-2+rm

Dear submitter,

as the package rust-tokio-signal 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/999736

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#974606: marked as done (rust-tokio-process: unsatisfiable build-dependency)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:20:39 +
with message-id 
and subject line Bug#999735: Removed package(s) from unstable
has caused the Debian Bug report #974606,
regarding rust-tokio-process: unsatisfiable build-dependency
to be marked as done.

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

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


-- 
974606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-tokio-process
Version: 0.2.4-1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

rust-tokio-process build-depends on librust-crossbeam-queue-0.1+default-dev.
This package does not exist in sid or in the NEW queue.

-Ralf.
--- End Message ---
--- Begin Message ---
Version: 0.2.4-1+rm

Dear submitter,

as the package rust-tokio-process 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/999735

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#936535: marked as done (flup: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:20:15 +
with message-id 
and subject line Bug#999688: Removed package(s) from unstable
has caused the Debian Bug report #936535,
regarding flup: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:flup

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

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

Dear submitter,

as the package flup 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/999688

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#966797: marked as done (tumgreyspf: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:19:51 +
with message-id 
and subject line Bug#999644: Removed package(s) from unstable
has caused the Debian Bug report #927137,
regarding tumgreyspf: Unversioned Python removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

Please check for dependencies, build dependencies AND autopkg tests.

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

Dear submitter,

as the package tumgreyspf 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/999644

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#938724: marked as done (tumgreyspf: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:19:51 +
with message-id 
and subject line Bug#999644: Removed package(s) from unstable
has caused the Debian Bug report #927137,
regarding tumgreyspf: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:tumgreyspf

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

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

Dear submitter,

as the package tumgreyspf 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/999644

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#927137: marked as done (src:tumgreyspf: Please port to python3 or remove)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:19:51 +
with message-id 
and subject line Bug#999644: Removed package(s) from unstable
has caused the Debian Bug report #927137,
regarding src:tumgreyspf: Please port to python3 or remove
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.)


-- 
927137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tumgreyspf
Version: 1.36-4.1
Severity: important

Python2.7 will go out of upstream security support during the Bullseye
development cycle.  It is not safe to assume it will be included in the
next release, so if you want to be sure tumgreyspf can stay in Debian, please
port it to python3.

Alternately, it's close to 8 years without a new release and there are
certainly alternatives for SPF checking and greylisting.  Removal might be in
order.

Personally, I want to remove some packages I maintain, particularly python-
ipaddr, which tumgreyspf depends on (indirectly via python-spf - which I will
change to python3 only) during the Bullseye cycle, regardless of what
happens to python2.7, so please update (python3 includes the ipaddress module,
which was developed from ipaddr, in the standard library).
--- End Message ---
--- Begin Message ---
Version: 1.36-4.1+rm

Dear submitter,

as the package tumgreyspf 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/999644

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#997570: marked as done (golang-github-marten-seemann-qtls-go1-15: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/marten-seemann/qtls-go1-15 returned exit code 1)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:17:14 +
with message-id 
and subject line Bug#999403: Removed package(s) from unstable
has caused the Debian Bug report #996756,
regarding golang-github-marten-seemann-qtls-go1-15: FTBFS: dh_auto_test: error: 
cd _build && go test -vet=off -v -p 4 github.com/marten-seemann/qtls-go1-15 
returned exit code 1
to be marked as done.

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

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


-- 
996756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-marten-seemann-qtls-go1-15
Version: 0.1.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package 
> golang-github-marten-seemann-qtls-go1-15
> dpkg-buildpackage: info: source version 0.1.1-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Shengjing Zhu 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --builddirectory=_build --buildsystem=golang --with=golang
>dh_auto_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf_clean -O--builddirectory=_build -O--buildsystem=golang
>dh_clean -O--builddirectory=_build -O--buildsystem=golang
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building golang-github-marten-seemann-qtls-go1-15 using 
> existing ./golang-github-marten-seemann-qtls-go1-15_0.1.1.orig.tar.gz
> dpkg-source: info: building golang-github-marten-seemann-qtls-go1-15 in 
> golang-github-marten-seemann-qtls-go1-15_0.1.1-2.debian.tar.xz
> dpkg-source: info: building golang-github-marten-seemann-qtls-go1-15 in 
> golang-github-marten-seemann-qtls-go1-15_0.1.1-2.dsc
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 4 
> github.com/marten-seemann/qtls-go1-15
> internal/goexperiment
> internal/unsafeheader
> internal/cpu
> runtime/internal/atomic
> internal/abi
> runtime/internal/sys
> runtime/internal/math
> internal/race
> sync/atomic
> unicode
> unicode/utf8
> internal/bytealg
> container/list
> internal/itoa
> math/bits
> crypto/internal/subtle
> math
> crypto/subtle
> runtime
> unicode/utf16
> vendor/golang.org/x/crypto/cryptobyte/asn1
> internal/nettrace
> vendor/golang.org/x/crypto/internal/subtle
> golang.org/x/crypto/internal/subtle
> golang.org/x/crypto/cryptobyte/asn1
> internal/reflectlite
> sync
> internal/testlog
> internal/singleflight
> math/rand
> runtime/cgo
> errors
> sort
> io
> internal/oserror
> syscall
> strconv
> bytes
> hash
> crypto/elliptic/internal/fiat
> crypto
> reflect
> path
> strings
> time
> internal/syscall/unix
> internal/syscall/execenv
> crypto/internal/randutil
> bufio
> crypto/hmac
> context
> internal/poll
> io/fs
> crypto/rc4
> vendor/golang.org/x/net/dns/dnsmessage
> encoding/binary
> internal/fmtsort
> os
> vendor/golang.org/x/crypto/hkdf
> golang.org/x/crypto/hkdf
> crypto/sha512
> crypto/cipher
> crypto/aes
> crypto/des
> fmt
> crypto/ed25519/internal/edwards25519/field
> crypto/md5
> crypto/sha1
> crypto/ed25519/internal/edwards25519
> crypto/sha256
> math/big
> encoding/hex
> encoding/base64
> net
> net/url
> encoding/pem
> path/filepath
> vendor/golang.org/x/crypto/chacha20
> vendor/golang.org/x/crypto/poly1305
> io/ioutil
> vendor/golang.org/x/crypto/curve25519
> vendor/golang.org/x/sys/cpu
> vendor/golang.org/x/crypto/chacha20poly1305
> golang.org/x/crypto/chacha20
> golang.org/x/crypto/poly1305
> crypto/elliptic
> encoding/asn1
> crypto/rand
> crypto/ed25519
> crypto/rsa
> vendor/golang.org/x/crypto/cryptobyte
> crypto/dsa
> crypto/x509/pkix
> golang.org/x/sys/cpu
> golang.org/x/crypto/cryptobyte
> crypto/ecdsa
> golang.org/x/crypto/chacha20poly1305
> golang.org/x/crypto/curve25519/internal/field
> golang.org/x/crypto/curve25519
> crypto/x509
> crypto/tls
> github.com/marten-seemann/qtls-go1-15
>dh_auto_test 

Bug#996756: marked as done (golang-github-marten-seemann-qtls-go1-15: FTBFS with golang/1.17: panic: qtls.ClientHelloInfo doesn't match)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:17:14 +
with message-id 
and subject line Bug#999403: Removed package(s) from unstable
has caused the Debian Bug report #996756,
regarding golang-github-marten-seemann-qtls-go1-15: FTBFS with golang/1.17: 
panic: qtls.ClientHelloInfo doesn't match
to be marked as done.

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

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


-- 
996756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-marten-seemann-qtls-go1-15
Version: 0.1.1-2
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: z...@debian.org

dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
cd _build && go test -vet=off -v -p 12 
github.com/marten-seemann/qtls-go1-15
panic: qtls.ClientHelloInfo doesn't match

goroutine 1 [running]:
github.com/marten-seemann/qtls-go1-15.init.0()

/<>/_build/src/github.com/marten-seemann/qtls-go1-15/unsafe.go:20 
+0x132
FAILgithub.com/marten-seemann/qtls-go1-15   0.006s
FAIL
--- End Message ---
--- Begin Message ---
Version: 0.1.1-2+rm

Dear submitter,

as the package golang-github-marten-seemann-qtls-go1-15 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/999403

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#997626: marked as done (django-restricted-resource: FTBFS: TypeError: Abstract models cannot be instantiated.)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:16:07 +
with message-id 
and subject line Bug#998900: Removed package(s) from unstable
has caused the Debian Bug report #995465,
regarding django-restricted-resource: FTBFS: TypeError: Abstract models cannot 
be instantiated.
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.)


-- 
995465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-restricted-resource
Version: 2016.8-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Run the bundled tests (in-memory database) when building the package
> LC_ALL=C python3 ./django_restricted_resource/test_project/manage.py test
> Creating test database for alias 'default'...
> System check identified some issues:
> 
> WARNINGS:
> django_restricted_resource.ExampleRestrictedResource: (models.W042) 
> Auto-created primary key used when not defining a primary key type, by 
> default 'django.db.models.AutoField'.
>   HINT: Configure the DEFAULT_AUTO_FIELD setting or the 
> AppConfig.default_auto_field attribute to point to a subclass of AutoField, 
> e.g. 'django.db.models.BigAutoField'.
> 
> System check identified 1 issue (0 silenced).
> ....
> ==
> ERROR: test_clean_is_okay_when_just_group_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_is_okay_when_just_group_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File 
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
>  line 64, in test_clean_is_okay_when_just_group_set
> resource = RestrictedResource(group=group)
>   File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, 
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract models cannot be instantiated.
> 
> 
> ==
> ERROR: test_clean_is_okay_when_just_user_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_is_okay_when_just_user_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File 
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
>  line 59, in test_clean_is_okay_when_just_user_set
> resource = RestrictedResource(user=user)
>   File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, 
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract models cannot be instantiated.
> 
> 
> ==
> ERROR: test_clean_raises_exception_when_both_user_and_group_is_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_raises_exception_when_both_user_and_group_is_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> --
> testtools.testresult.real._StringException: Traceback (most recent call last):
>   File 
> "/<>/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
>  line 54, in test_clean_raises_exception_when_both_user_and_group_is_set
> resource = RestrictedResource(user=user, group=group)
>   File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, 
> in __init__
> raise TypeError('Abstract models cannot be instantiated.')
> TypeError: Abstract models cannot be instantiated.
> 
> 
> ==
> ERROR: test_clean_raises_exception_when_owner_is_not_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> test_clean_raises_exception_when_owner_is_not_set 
> (django_restricted_resource.tests.ResourceCleanTests)
> 

Bug#995465: marked as done (django-restricted-resource: autopkgtest fails for python-django >= 3)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:16:07 +
with message-id 
and subject line Bug#998900: Removed package(s) from unstable
has caused the Debian Bug report #995465,
regarding django-restricted-resource: autopkgtest fails for python-django >= 3
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.)


-- 
995465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-restricted-resource
Version: 2016.8-3
Severity: serious
Usertags: breaks needs-update
Control: found -1 python-django/2:3.2.7-4
Control: found -1 django-restricted-resource/2016.8-3

Dear Maintainer(s),

the latest upload of python-django is breaking the autopkgtest for
django-restricted-resource but was succeeding previously.

The broken autopkgtest is blocking python-django from migrating to
testing.

The relevant part of the broken testing is this:

==
ERROR: test_clean_is_okay_when_just_group_set 
(django_restricted_resource.tests.ResourceCleanTests)
test_clean_is_okay_when_just_group_set 
(django_restricted_resource.tests.ResourceCleanTests)
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.r7b2wyms/downtmp/build.SBo/src/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
 line 64, in test_clean_is_okay_when_just_group_set
resource = RestrictedResource(group=group)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, in 
__init__
raise TypeError('Abstract models cannot be instantiated.')
TypeError: Abstract models cannot be instantiated.


==
ERROR: test_clean_is_okay_when_just_user_set 
(django_restricted_resource.tests.ResourceCleanTests)
test_clean_is_okay_when_just_user_set 
(django_restricted_resource.tests.ResourceCleanTests)
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.r7b2wyms/downtmp/build.SBo/src/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
 line 59, in test_clean_is_okay_when_just_user_set
resource = RestrictedResource(user=user)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, in 
__init__
raise TypeError('Abstract models cannot be instantiated.')
TypeError: Abstract models cannot be instantiated.


==
ERROR: test_clean_raises_exception_when_both_user_and_group_is_set 
(django_restricted_resource.tests.ResourceCleanTests)
test_clean_raises_exception_when_both_user_and_group_is_set 
(django_restricted_resource.tests.ResourceCleanTests)
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.r7b2wyms/downtmp/build.SBo/src/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
 line 54, in test_clean_raises_exception_when_both_user_and_group_is_set
resource = RestrictedResource(user=user, group=group)
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, in 
__init__
raise TypeError('Abstract models cannot be instantiated.')
TypeError: Abstract models cannot be instantiated.

==
ERROR: test_clean_raises_exception_when_owner_is_not_set 
(django_restricted_resource.tests.ResourceCleanTests)
test_clean_raises_exception_when_owner_is_not_set 
(django_restricted_resource.tests.ResourceCleanTests)
--
testtools.testresult.real._StringException: Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.r7b2wyms/downtmp/build.SBo/src/django_restricted_resource/test_project/../../django_restricted_resource/tests.py",
 line 48, in test_clean_raises_exception_when_owner_is_not_set
resource = RestrictedResource()
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 413, in 
__init__
raise TypeError('Abstract models cannot be instantiated.')
TypeError: Abstract models cannot be instantiated.


--
Ran 172 tests in 2.745s

The full log is visible under

Bug#998723: marked as done (node-whatwg-fetch conflicts libjs-fetch)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:08:11 +
with message-id 
and subject line Bug#998724: Removed package(s) from unstable
has caused the Debian Bug report #998723,
regarding node-whatwg-fetch conflicts libjs-fetch
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.)


-- 
998723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-whatwg-fetch
Severity: serious
Justification: FTBFS

Hi,

node-whatwg-fetch and libjs-fetch both provides node-whatwg-fetch, and
share the same source. One has to be removed.
--- End Message ---
--- Begin Message ---
Version: 3.5.0-2+rm

Dear submitter,

as the package libjs-fetch 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/998724

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#970186: marked as done (rust-rand-core-0.3: Unaligned memory access resulting in undefined behavior)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:08:46 +
with message-id 
and subject line Bug#998735: Removed package(s) from unstable
has caused the Debian Bug report #970186,
regarding rust-rand-core-0.3: Unaligned memory access resulting in undefined 
behavior
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.)


-- 
970186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-rand-core-0.3
Version: 0.3.0-2
Severity: normal
Tags: upstream, security

Dear Maintainer,


Versions under 0.4.2 violated alignment when casting byte slices to integer 
slices, resulting in undefined behavior.

Advisory: https://rustsec.org/advisories/RUSTSEC-2019-0035.html


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

Kernel: Linux 5.6.0-2-amd64 (SMP w/2 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
--- End Message ---
--- Begin Message ---
Version: 0.3.0-2+rm

Dear submitter,

as the package rust-rand-core-0.3 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/998735

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#915069: marked as done (libphp-predis: Useless in Debian, superseded by php-nrk-predis)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:06:47 +
with message-id 
and subject line Bug#998717: Removed package(s) from unstable
has caused the Debian Bug report #915069,
regarding libphp-predis: Useless in Debian, superseded by php-nrk-predis
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.)


-- 
915069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libphp-predis
Version: 0.8.3-1
Severity: serious

libphp-predis was packaged a few years ago, and is not used by any
Debian anymore. The php-nrk-predis is a more recent version of the same
package, so there is a priori little point to ship libphp-predis in a
stable Debian release.

I intend to follow up with an RM request in a few months if nobody
objects (but feel free to beat me to it).

Regards

David
--- End Message ---
--- Begin Message ---
Version: 0.8.3-1+rm

Dear submitter,

as the package libphp-predis 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/998717

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#875184: marked as done ([sofa-framework] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:04:18 +
with message-id 
and subject line Bug#998639: Removed package(s) from unstable
has caused the Debian Bug report #875184,
regarding [sofa-framework] Future Qt4 removal from Buster
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.)


-- 
875184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sofa-framework
Version: 1.0~beta4-12
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Version: 1.0~beta4-12+rm

Dear submitter,

as the package sofa-framework 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/998639

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#997290: marked as done (xfce4-sntray-plugin: FTBFS: client.vala:68.13-68.21: error: syntax error, no expression allowed between array brackets)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:03:57 +
with message-id 
and subject line Bug#997290: fixed in xfce4-sntray-plugin 0.4.13.1-2
has caused the Debian Bug report #997290,
regarding xfce4-sntray-plugin: FTBFS: client.vala:68.13-68.21: error: syntax 
error, no expression allowed between array brackets
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.)


-- 
997290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-sntray-plugin
Version: 0.4.13.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/aa.mo /<>/po/aa.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ab.mo /<>/po/ab.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ae.mo /<>/po/ae.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/af.mo /<>/po/af.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ak.mo /<>/po/ak.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/am.mo /<>/po/am.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/an.mo /<>/po/an.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ar.mo /<>/po/ar.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/as.mo /<>/po/as.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ast.mo /<>/po/ast.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/av.mo /<>/po/av.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ay.mo /<>/po/ay.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/az.mo /<>/po/az.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ba.mo /<>/po/ba.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/be.mo /<>/po/be.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bg.mo /<>/po/bg.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bh.mo /<>/po/bh.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bi.mo /<>/po/bi.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bm.mo /<>/po/bm.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bn.mo /<>/po/bn.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bo.mo /<>/po/bo.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/br.mo /<>/po/br.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/bs.mo /<>/po/bs.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ca.mo /<>/po/ca.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ce.mo /<>/po/ce.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ch.mo /<>/po/ch.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/ckb.mo /<>/po/ckb.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/co.mo /<>/po/co.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/cr.mo /<>/po/cr.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/cs.mo /<>/po/cs.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/cu.mo /<>/po/cu.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/cv.mo /<>/po/cv.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/cy.mo /<>/po/cy.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/da.mo /<>/po/da.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/de.mo /<>/po/de.po
> cd /<>/obj-x86_64-linux-gnu/po && /usr/bin/msgfmt -o 
> /<>/obj-x86_64-linux-gnu/po/dv.mo /<>/po/dv.po
> cd 

Bug#991000: marked as done (bareos-database-common: fails to upgrade from buster: ERROR: invalid value for parameter "client_min_messages": "fatal")

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:01:50 +
with message-id 
and subject line Bug#1000906: Removed package(s) from unstable
has caused the Debian Bug report #991000,
regarding bareos-database-common: fails to upgrade from buster: ERROR: invalid 
value for parameter "client_min_messages": "fatal"
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.)


-- 
991000: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bareos-database-common
Version: 17.2.7-2.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'sid' fails.
(There is no bareos in bullseye, so the buster bareos packages were kept
installed during the upgrade to bullseye. But the postgresql cluster was
upgraded from 11 to 13.)

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

  Setting up bareos-database-common (17.2.7-2.1) ...
  Warning: failed to get "dbname" from config, using default value "bareos", 
see /tmp/bareos-config.9027.log
  Warning: failed to get "dbuser" from config, using default value "bareos", 
see /tmp/bareos-config.9027.log
  (config) dbc_go() bareos-database-common configure 2004.
  dbc_config() bareos-database-common configure 2004.
  dbc_set_dbtype_defaults() .
  dbc_detect_installed_dbtype() pgsql.
  _dbc_detect_installed_dbtype() pgsql.
  dbc_register_debconf() .
  dbc_read_package_config() .
  dbc_preseed_package_debconf() .
  dbc_config() bareos-database-common configure 2004.
  dbc_set_dbtype_defaults() pgsql.
  dbc_detect_installed_dbtype() pgsql.
  _dbc_detect_installed_dbtype() pgsql.
  dbc_register_debconf() .
  dbc_get_app_pass() .
  dbconfig-common: writing config to 
/etc/dbconfig-common/bareos-database-common.conf
  creating database backup in 
/var/cache/dbconfig-common/backups/bareos-database-common_2004.2021-07-12-01.24.18.
  applying upgrade sql for 2004 -> 2171.
  error encountered processing 
/usr/share/dbconfig-common/data/bareos-database-common/upgrade/pgsql/2171:
  NOTICE: table "tmpmergefilenameintofiletable" does not exist, skipping setval 
 (1 row) ERROR: invalid value for parameter "client_min_messages": 
"fatal" HINT: Available values: debug5, debug4, debug3, debug2, debug1, log, 
notice, warning, error.
  dbconfig-common: bareos-database-common configure: aborted.
  dbconfig-common: flushing administrative password
  dpkg: error processing package bareos-database-common (--configure):
   installed bareos-database-common package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.31-13) ...
  Errors were encountered while processing:
   bareos-database-common


cheers,

Andreas


bareos-database-common_17.2.7-2.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 17.2.7-2.1+rm

Dear submitter,

as the package bareos 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/1000906

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#995837: marked as done (Should bareos be removed?)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:01:50 +
with message-id 
and subject line Bug#1000906: Removed package(s) from unstable
has caused the Debian Bug report #995837,
regarding Should bareos be removed?
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.)


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

Your package came up as a candidate for removal from Debian:

Bareos hasn't seen an upload since 2019, missed Bullseye
and has a total of 8 RC bugs at this point.


If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 17.2.7-2.1+rm

Dear submitter,

as the package bareos 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/1000906

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#977708: marked as done (on purge not all files are removed)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:01:50 +
with message-id 
and subject line Bug#1000906: Removed package(s) from unstable
has caused the Debian Bug report #977708,
regarding on purge not all files are removed
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.)


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

Hello,

on sudo apt purge bareos*

I get

[quote]
Purging configuration files for bareos-common (17.2.7-2.1) ...
dpkg: warning: while removing bareos-common, directory '/var/lib/bareos' not
empty so not removed
Purging configuration files for bareos-filedaemon (17.2.7-2.1) ...
[/qoute]

[quote]
$ ls -l /var/lib/bareos
insgesamt 4
-rw-r- 1 root bareos 196 19. Dez 11:16 bareos-fd.9102.state
[/qoute]

CU
Jörg



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

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

Versions of packages bareos depends on:
pn  bareos-client
pn  bareos-director  
pn  bareos-storage   

bareos recommends no packages.

bareos suggests no packages.
--- End Message ---
--- Begin Message ---
Version: 17.2.7-2.1+rm

Dear submitter,

as the package bareos 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/1000906

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#977707: marked as done (Install fails with mysql error 1005)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:01:50 +
with message-id 
and subject line Bug#1000906: Removed package(s) from unstable
has caused the Debian Bug report #977707,
regarding Install fails with mysql error 1005
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.)


-- 
977707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bareos-database-common
Version: 17.2.7-2.1
Severity: grave

Hello,

on a fresh bullseye install I get on install bareos with

$ sudo apt install bareos bareos-database-mysql

[quote]
 mysql said: ERROR 1005 (HY000) at line 31: Can't create table `bareos`.`File`
(errno: 150 "Foreign key constraint is incorrectly formed")
[/quote]


CU
Jörg



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

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

Versions of packages bareos-database-common depends on:
iu  bareos-common  17.2.7-2.1
iu  bareos-database-mysql  17.2.7-2.1
ii  dbconfig-common2.0.17
ii  debconf [debconf-2.0]  1.5.74
ii  libc6  2.31-5
ii  libstdc++6 10.2.1-1
ii  lsb-base   11.1.0

bareos-database-common recommends no packages.

bareos-database-common suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Version: 17.2.7-2.1+rm

Dear submitter,

as the package bareos 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/1000906

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#968957: marked as done (bareos: CVE-2020-11061)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:01:50 +
with message-id 
and subject line Bug#1000906: Removed package(s) from unstable
has caused the Debian Bug report #968957,
regarding bareos: CVE-2020-11061
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.)


-- 
968957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bareos
Severity: grave
Tags: security

CVE-2020-11061:
https://github.com/bareos/bareos/security/advisories/GHSA-mm45-cg35-54j4

CVE-2020-4042
https://github.com/bareos/bareos/security/advisories/GHSA-vqpj-2vhj-h752

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
Version: 17.2.7-2.1+rm

Dear submitter,

as the package bareos 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/1000906

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#965985: marked as done (bareos: CVE-2020-4042)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:01:50 +
with message-id 
and subject line Bug#1000906: Removed package(s) from unstable
has caused the Debian Bug report #965985,
regarding bareos: CVE-2020-4042
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.)


-- 
965985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bareos
Severity: grave
Tags: security

CVE-2020-11061:
https://github.com/bareos/bareos/security/advisories/GHSA-mm45-cg35-54j4

CVE-2020-4042
https://github.com/bareos/bareos/security/advisories/GHSA-vqpj-2vhj-h752

Cheers,
Moritz

--- End Message ---
--- Begin Message ---
Version: 17.2.7-2.1+rm

Dear submitter,

as the package bareos 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/1000906

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#937927: marked as done (python-mode: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:00:38 +
with message-id 
and subject line Bug#1000902: Removed package(s) from unstable
has caused the Debian Bug report #937927,
regarding python-mode: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
937927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-mode
Version: 1:6.2.3-1.3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-mode

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

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

Dear submitter,

as the package python-mode 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/1000902

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#937398: marked as done (pycalendar: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:01:07 +
with message-id 
and subject line Bug#1000904: Removed package(s) from unstable
has caused the Debian Bug report #937398,
regarding pycalendar: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
937398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pycalendar
Version: 1:2.1~git20161130.0.e68e150-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:pycalendar

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

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

Dear submitter,

as the package pycalendar 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/1000904

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#936185: marked as done (bareos: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:01:50 +
with message-id 
and subject line Bug#1000906: Removed package(s) from unstable
has caused the Debian Bug report #936185,
regarding bareos: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:bareos

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

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

Dear submitter,

as the package bareos 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/1000906

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#922344: marked as done (bareos: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:01:50 +
with message-id 
and subject line Bug#1000906: Removed package(s) from unstable
has caused the Debian Bug report #922344,
regarding bareos: autopkgtest regression
to be marked as done.

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

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


-- 
922344: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922344
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bareos
Version: 17.2.7-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of bareos the autopkgtest of bareos fails in
testing when that autopkgtest is run with the binary packages of bareos
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
bareos from testing17.2.7-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? If needed, please
change the bug's severity.

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

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
bareos/17.2.7-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=bareos

https://ci.debian.net/data/autopkgtest/testing/amd64/b/bareos/1927429/log.gz

Feb 14 02:18:17 ci-1550110244 systemd[3507]: Failed to attach 3507 to
compat systemd cgroup /system.slice/bareos-director.service: No such
file or directory
Feb 14 02:18:48 ci-1550110244 bareos-dir[3507]: bareos-dir:
dird.c:1157-0 Could not open Catalog "MyCatalog", database "bareos".
Feb 14 02:18:48 ci-1550110244 bareos-dir[3507]: bareos-dir:
dird.c:1162-0 postgresql.c:253 Unable to connect to PostgreSQL server.
Database=bareos User=bareos
Feb 14 02:18:48 ci-1550110244 bareos-dir[3507]: Possible causes: SQL
server not running; password incorrect; max_connections exceeded.
Feb 14 02:18:48 ci-1550110244 bareos-dir[3507]: 0bareos-dir ERROR
TERMINATION
Feb 14 02:18:48 ci-1550110244 bareos-dir[3507]: Please correct the
configuration in /etc/bareos/bareos-dir.d/*/*.conf
Feb 14 02:18:48 ci-1550110244 systemd[3509]: Failed to attach 3509 to
compat systemd cgroup /system.slice/bareos-director.service: No such
file or directory
Feb 14 02:18:48 ci-1550110244 systemd[1]: bareos-director.service: Can't
open PID file /var/lib/bareos/bareos-dir.9101.pid (yet?) after start: No
such file or directory



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 17.2.7-2.1+rm

Dear submitter,

as the package bareos 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/1000906

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#884234: marked as done (bareos: Stable update fails to configure (no database version defined, FAILED to set Catalog MyCatalog dbdriver = postgresql))

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 23:01:50 +
with message-id 
and subject line Bug#1000906: Removed package(s) from unstable
has caused the Debian Bug report #884234,
regarding bareos: Stable update fails to configure (no database version 
defined, FAILED to set Catalog MyCatalog dbdriver = postgresql)
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.)


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

Package: bareos
Version: 14.2.1+20141017gitc6c5b56-3+deb8u3
Severity: serious
Justification: Policy 10.7.3

I've been happily using the bareos packages on jessie for a bit now (thank
you for maintaining them!)

I attempted to upgrade bareos to 14.2.1+20141017gitc6c5b56-3+deb8u3
(from +deb8u2) this afternoon, and it failed to configure. Here is
trying to configure it again:

root@Bennu:~# dpkg --configure -a
Setting up bareos-database-common (14.2.1+20141017gitc6c5b56-3+deb8u3) ...
Warning: no database version defined for release 14.2.1+20141017gitc6c5b56 
(14.2.1+20141017gitc6c5b56-3+deb8u2). Using default version: 2003
(config) dbc_go() bareos-database-common configure 2003.
dbc_config() bareos-database-common configure 2003.
dbc_set_dbtype_defaults() .
dbc_register_debconf() .
dbc_read_package_config() .
dbc_preseed_package_debconf() .
dbc_detect_supported_dbtype() pgsql.
dbc_detect_installed_dbtype() pgsql.
_dbc_detect_installed_dbtype() pgsql.
dbc_config() bareos-database-common configure 2003.
dbc_set_dbtype_defaults() pgsql.
dbc_get_app_pass() .
Warning: no database version defined for release 14.2.1+20141017gitc6c5b56 
(14.2.1+20141017gitc6c5b56-3+deb8u2). Using default version: 2003
dbconfig-common: writing config to 
/etc/dbconfig-common/bareos-database-common.conf
dbconfig-common: flushing administrative password
FAILED to set Catalog MyCatalog dbdriver = postgresql 
(/etc/bareos/bareos-dir.conf)

... which would make sense because I don't have a catalog called
MyCatalog, except reading /usr/lib/bareos/scripts/bareos-config-lib.sh
it turns out its actually nowhere near that robust; it's just looking
for "dbdriver = ..." and failing to find it. That's broken for at least
three reasons:

   1) The documented parameter name is "DB Driver"; see
  
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirCatalogDB%20Driver
  and bareos of course doesn't care about capitalization or spacing
  (which is why dbdriver also works).

   2) Config files can include other config files, so the db config may
  not even be in that file at all.

   3) It blindly overwrites any configuration changes made by the admin,
  which isn't permitted by Debian Policy §10.7.3. (In my case,
  bareos-dir.conf is actually a generated file — directly editing it
  is broken.)

Thankfully, there is a fairly easy approach that solves all these
problems: put the default Debian database config in its own file
(possibly under /var/lib/bareos/) and then @-include it into the shipped
bareos-dir.conf. Then you don't have to touch the configuration file.


(I fixed my system by commenting out the apply_dbconfig_settings line in
/var/lib/dpkg/info/bareos-database-common.postinst).


 -- System Information:
Debian Release: 8.10
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-0.bpo.4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bareos depends on:
ii  bareos-client14.2.1+20141017gitc6c5b56-3+deb8u3
iu  bareos-director  14.2.1+20141017gitc6c5b56-3+deb8u3
ii  bareos-storage   14.2.1+20141017gitc6c5b56-3+deb8u3

bareos recommends no packages.

bareos suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 17.2.7-2.1+rm

Dear submitter,

as the package bareos 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/1000906

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 

Bug#998206: calendar: cronjob processes all users’ calendars as root, allowing information disclosure

[Thorsten Glaser]

Michael Meskes dixit:

>Hmm, not sure what I'm doing wrong. Using the same entries in my calendar file 
>I get:
>
>michael@feivel:~$ calendar

Right, but do enable the cronjob. “calendar -a” runs as root.
Or try sudo calendar -a which is basically the same then watch
your mail. (You’ll also need to change the dates, of course.)

The patch to remove the setusercontext call is wrong, basically.
Turns out fixing this (I was independently porting a different
BSD calendar codebase) is rather hard and probably involves PAM
magic way out of my experience. I asked at
https://listman.redhat.com/archives/pam-list/2021-November/msg0.html
but that mailing list seems to be mostly dead.

I did manage to cobble together something that at least switches
to users properly… search for USE_CUSTOM_USERSWITCH or userswitch in
http://www.mirbsd.org/cvs.cgi/src/usr.bin/calendar/calendar.c?rev=HEAD
combined with…

/* better than nothing… */
#define userswitch(pw) (\
!!setresgid((pw)->pw_gid, (pw)->pw_gid, (pw)->pw_gid) ||\
/*  \
 * not correct (should switch to user’s supplemental\
 * group vector) but sufficient until someone sends \
 * a workable alternative…  \
 */ \
!!setgroups(0, NULL) || \
!!setresuid((pw)->pw_uid, (pw)->pw_uid, (pw)->pw_uid)   \
)

… in calendar-mirbsd-20211101/debian/port/port.h but it lacks
not only setting the groups vector but also things like limits,
environment variables and the likes.

Unless you happen to have a PAM expert at hand, you might wish
to at least apply something similar. In your package, at least
the cronjob is disabled by default, so it hits less users, but
it’s still risky.

bye,
//mirabilos
-- 
[...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but
what about xfs, and if only i had waited until reiser4 was ready... in the be-
ginning, there was ffs, and in the middle, there was ffs, and at the end, there
was still ffs, and the sys admins knew it was good. :)  -- Ted Unangst über *fs

Bug#1000753: poliastro FTBFS: plugin flit failed with: Use [project] table for metadata or [tool.flit.metadata], not both

[Scott Kitterman]

On Wed, 01 Dec 2021 14:07:52 -0500 Scott Kitterman  
wrote:
> On Sun, 28 Nov 2021 14:17:14 + "Rebecca N. Palmer" 
>  wrote:
> > Package: python3-poliastro
> > Version: 0.15.2-3
> > Severity: serious
> > 
> > Fails to build with the error
> > 
> > E: pybuild pybuild:354: build: plugin flit failed with: Use [project] 
> > table for metadata or [tool.flit.metadata], not both.
> 
> this should be pretty trivially resolved by dropping Revert-the-adoption-
> PEP-621-metadata.patch and bumping the minimum flit version in build-depends 
to 
> 3.2.  Now that we have flit 3.3 in the archive, using the PEP 621 metadata is 
> not a problem.

Confirmed.  NMU diff attached.  I'm not going to upload this now, but I may 
later.  I'd prefer one of the maintainers take care of it.

Scott Kdiff -Nru poliastro-0.15.2/debian/changelog poliastro-0.15.2/debian/changelog
--- poliastro-0.15.2/debian/changelog	2021-08-28 09:09:23.0 -0400
+++ poliastro-0.15.2/debian/changelog	2021-12-01 17:30:34.0 -0500
@@ -1,3 +1,12 @@
+poliastro (0.15.2-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop debian/patches/Revert-the-adoption-PEP-621-metadata.patch and bump
+minimum flit version in build-depends to 3.2 (to ensure PEP 621 support)
+in order fo fix FTBFS with flit 3.3 (Closes: #1000753)
+
+ -- Scott Kitterman   Wed, 01 Dec 2021 17:30:34 -0500
+
 poliastro (0.15.2-3) unstable; urgency=medium
 
   * Negate the 32-bit test in xfail: was accidently reversed
diff -Nru poliastro-0.15.2/debian/control poliastro-0.15.2/debian/control
--- poliastro-0.15.2/debian/control	2021-08-24 10:56:53.0 -0400
+++ poliastro-0.15.2/debian/control	2021-12-01 17:30:29.0 -0500
@@ -5,7 +5,7 @@
 Uploaders: Ole Streicher 
 Build-Depends: debhelper-compat (= 13),
dh-python,
-   flit,
+   flit (>= 3.2),
python3-all,
python3-astropy (>= 3.2~),
python3-astroquery,
diff -Nru poliastro-0.15.2/debian/patches/Revert-the-adoption-PEP-621-metadata.patch poliastro-0.15.2/debian/patches/Revert-the-adoption-PEP-621-metadata.patch
--- poliastro-0.15.2/debian/patches/Revert-the-adoption-PEP-621-metadata.patch	2021-08-28 08:02:51.0 -0400
+++ poliastro-0.15.2/debian/patches/Revert-the-adoption-PEP-621-metadata.patch	1969-12-31 19:00:00.0 -0500
@@ -1,88 +0,0 @@
-From: =?utf-8?q?Juan_Luis_Cano_Rodr=C3=ADguez?= 
-Date: Fri, 23 Apr 2021 12:03:06 +0200
-Subject: Revert the adoption PEP 621 metadata
-
-https://github.com/takluyver/flit/issues/436

- pyproject.toml | 36 +++-
- 1 file changed, 15 insertions(+), 21 deletions(-)
-
-diff --git a/pyproject.toml b/pyproject.toml
-index b6bddd5..3fa7389 100644
 a/pyproject.toml
-+++ b/pyproject.toml
-@@ -1,28 +1,18 @@
- [build-system]
- requires = [
--"flit_core >=3.2,<3.3",
-+"flit_core >=2.0,<4",
- "wheel",
- "oldest-supported-numpy",
- ]
- build-backend = "flit_core.buildapi"
- 
--[project]
--name = "poliastro"
--readme = "README.md"
--requires-python = ">=3.7,<3.10"
--license = {file = "COPYING"}
--authors = [
--{name = "Juan Luis Cano Rodríguez", email = "hello@juanlu.space"}
--]
--keywords = [
--"aero",
--"aerospace",
--"engineering",
--"astrodynamics",
--"orbits",
--"kepler",
--"orbital mechanics"
--]
-+[tool.flit.metadata]
-+module = "poliastro"
-+author = "Juan Luis Cano Rodríguez"
-+author-email = "hello@juanlu.space"
-+description-file = "README.md"
-+home-page = "https://github.com/poliastro/poliastro/;
-+keywords = "aero,aerospace,engineering,astrodynamics,orbits,kepler,orbital mechanics"
- classifiers = [
- "License :: OSI Approved :: MIT License",
- "Development Status :: 4 - Beta",
-@@ -41,7 +31,8 @@ classifiers = [
- "Topic :: Scientific/Engineering :: Physics",
- "Topic :: Scientific/Engineering :: Astronomy",
- ]
--dependencies = [
-+requires-python = ">=3.7,<3.10"
-+requires = [
- "astropy >=3.2,<5",
- "astroquery >=0.3.9",
- "cached_property ; python_version<'3.8'",
-@@ -55,7 +46,6 @@ dependencies = [
- "pyerfa",
- "scipy >=1.4.0",
- ]
--dynamic = ["version", "description"]
- 
- [project.urls]
- Home-Page = "https://www.poliastro.space;
-@@ -64,7 +54,7 @@ Source = "https://github.com/poliastro/poliastro;
- Tracker = "https://github.com/poliastro/poliastro/issues;
- Funding = "https://opencollective.com/poliastro;
- 
--[project.optional-dependencies]
-+[tool.flit.metadata.requires-extra]
- jupyter = ["notebook", "ipywidgets>=7.6"]
- cesium = ["czml3 ~=0.5.3"]
- dev = [
-@@ -95,6 +85,10 @@ dev = [
- "sphinx-notfound-page",
- ]
- 
-+[tool.flit.metadata.urls]
-+Source = "https://github.com/poliastro/poliastro;
-+Tracker = "https://github.com/poliastro/poliastro/issues;
-+
- [tool.flit.sdist]
- include = [
- "src/poliastro/atmosphere/data/coesa62.dat",
diff -Nru poliastro-0.15.2/debian/patches/series 

Bug#997290: marked as pending in xfce4-sntray-plugin

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #997290 in xfce4-sntray-plugin 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/debian-ayatana-team/xfce4-sntray-plugin/-/commit/cfe88d145e02f9674d205dac6d7bf292a63d6b42


debian/patches: Add 1001_fix-FTBFS-in-dbusmenu-client-vala.patch. Fix FTBFS in 
src/dbusmenu/client.vala. (Closes: #997290).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/997290

Processed: Bug#997290 marked as pending in xfce4-sntray-plugin

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #997290 [src:xfce4-sntray-plugin] xfce4-sntray-plugin: FTBFS: 
client.vala:68.13-68.21: error: syntax error, no expression allowed between 
array brackets
Added tag(s) pending.

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

Processed: minimac4 autopkgtest regression confirmed

[Debian Bug Tracking System]

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

> tags 1000475 confirmed
Bug #1000475 [src:minimac4] minimac4: autopkgtest regression: *** stack 
smashing detected ***: terminated
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#1000146: cppcheck: incorrect dependencies: libc6 should be >= 2.32

[Joachim Reichel]

Hi Ian,

On 28.11.21 19:21, Ian Jackson wrote:

Joachim Reichel (cppcheck maintainer):

I'll upload a new version cppcheck with a workaround shortly


Would you mind both prioritising this fix ?  FTAOD it's not just
cppcheck that is scheduled for autoremoval.  Any package which
transitively [build-]depends on any package whose .debs are affected
will be scheduled for autoremoval (assuming some bug has been filed).


I'm aware of that. And "shortly" definitely means "before the autoremoval" 
(which is currently scheduled for 2022-01-01). Is there a particular reason for 
the urgency that I'm missing? Note that cppcheck is not a library, i.e., this 
wrong dependency should not spread out by delaying the upload a bit.


(Fixing dpkg-shlibdeps and binNMUs is a different topic and is probably better 
discussed in #100421.)


Best regards,
  Joachim

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 997368 gnunet
Bug #997368 [src:gnunet-fuse] FTBFS in sid
Bug reassigned from package 'src:gnunet-fuse' to 'gnunet'.
No longer marked as found in versions gnunet-fuse/0.13.0-2.
Ignoring request to alter fixed versions of bug #997368 to the same values 
previously set
> reassign 997306 gnunet
Bug #997306 [src:gnunet-gtk] FTBFS in sid
Bug reassigned from package 'src:gnunet-gtk' to 'gnunet'.
No longer marked as found in versions gnunet-gtk/0.13.1-2.
Ignoring request to alter fixed versions of bug #997306 to the same values 
previously set
> forcemerge 998290 997368 997306
Bug #998290 [gnunet] debianutils demoved tempfile, use mktemp
Bug #998290 [gnunet] debianutils demoved tempfile, use mktemp
Added tag(s) sid, experimental, ftbfs, and bookworm.
Bug #997368 [gnunet] FTBFS in sid
Marked as found in versions gnunet/0.14.0-6.
Bug #997306 [gnunet] FTBFS in sid
Marked as found in versions gnunet/0.14.0-6.
Merged 997306 997368 998290
> affects 998290 src:gnunet-gtk src:gnunet-fuse
Bug #998290 [gnunet] debianutils demoved tempfile, use mktemp
Bug #997306 [gnunet] FTBFS in sid
Bug #997368 [gnunet] FTBFS in sid
Added indication that 998290 affects src:gnunet-gtk and src:gnunet-fuse
Added indication that 997306 affects src:gnunet-gtk and src:gnunet-fuse
Added indication that 997368 affects src:gnunet-gtk and src:gnunet-fuse
> thanks
Stopping processing here.

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

Processed: update bts with right meta info

[Debian Bug Tracking System]

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

> reassign 1000552 src:python-agate-excel 0.2.3-1
Bug #1000552 {Done: Håvard Flaget Aasen } 
[src:openpyxl, src:python-agate-excel] openpyxl breaks python-agate-excel 
autopkgtest
Bug reassigned from package 'src:openpyxl, src:python-agate-excel' to 
'src:python-agate-excel'.
No longer marked as found in versions openpyxl/3.0.9-1 and 
python-agate-excel/0.2.3-1.
No longer marked as fixed in versions python-agate-excel/0.2.5-1.
Bug #1000552 {Done: Håvard Flaget Aasen } 
[src:python-agate-excel] openpyxl breaks python-agate-excel autopkgtest
Marked as found in versions python-agate-excel/0.2.3-1.
> fixed 1000552 0.2.5-1
Bug #1000552 {Done: Håvard Flaget Aasen } 
[src:python-agate-excel] openpyxl breaks python-agate-excel autopkgtest
Marked as fixed in versions python-agate-excel/0.2.5-1.
> affects 1000552 src:openpyxl
Bug #1000552 {Done: Håvard Flaget Aasen } 
[src:python-agate-excel] openpyxl breaks python-agate-excel autopkgtest
Added indication that 1000552 affects src:openpyxl
> thanks
Stopping processing here.

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

Bug#998206: calendar: cronjob processes all users’ calendars as root, allowing information disclosure

[Michael Meskes]

[Sorry, I have missed this bug report, didn't make it into the correct mailbox 
locally it seems.]

On Mon, Nov 01, 2021 at 12:02:48AM +, Thorsten Glaser wrote:
> #define·ssh·Nov·01→ ssh
> #include·"/root/.ssh/authorized_keys"

Hmm, not sure what I'm doing wrong. Using the same entries in my calendar file 
I get:

michael@feivel:~$ calendar 
:3:2: fatal error: /root/.ssh/authorized_keys: Permission denied
compilation terminated.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De
Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org

Processed: Re: minimac4: autopkgtest regression: *** stack smashing detected ***: terminated

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #1000475 [src:minimac4] minimac4: autopkgtest regression: *** stack 
smashing detected ***: terminated
Removed tag(s) moreinfo.

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

Bug#1000972: ruby-jaeger-client: Depends on ruby-thrift:amd64 which isn't available on other architectures

[Paul Gevers]

Package: ruby-jaeger-client
Version: 1.2.0-1
Severity: serious
Justification: uninstallable

ruby-jaeger-client is on my radar because it doesn't migrate for a
long time. I was very puzzled by the output of britney:
> ruby-jaeger-client/amd64 has unsatisfiable dependency
> ruby-jaeger-client/arm64 has unsatisfiable dependency

Turns out this is probably a bug in britney, but it does point out an
issue on all architectures but amd64. ruby-jaeger-client has a arch
specifier in its depends: ruby-thrift:amd64. As I couldn't find this
in the d/control file, I guess it's a tool chain issue (or a logical
flow inside this package).

You can see the uninstallability in action on ci.debian.net where all
architectures fail in unstable except amd64.

See below, grabbed from the arm64 Packages.

Paul

Package: ruby-jaeger-client
Version: 1.2.0-1
Installed-Size: 183
Maintainer: Debian Ruby Team 

Architecture: all
Depends: ruby:any, ruby-opentracing (>= 0.3), ruby-thrift:amd64
Description: OpenTracing Tracer implementation for Jaeger
Homepage: https://github.com/salemove/jaeger-client-ruby
Description-md5: a7ce2ef441d13cf5a973833acaa48379
Ruby-Versions: all
Section: ruby
Priority: optional
Filename: pool/main/r/ruby-jaeger-client/ruby-jaeger-client_1.2.0-1_all.deb
Size: 32476
MD5sum: 0d382dbd396d9496ce63cd2aa3360ec8
SHA256: 6df406498b9d15f095ece5355255c0a980ca70263c17bb0d3ab694261365d230

Processed: Re: minimac4: autopkgtest regression: *** stack smashing detected ***: terminated

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #1000475 [src:minimac4] minimac4: autopkgtest regression: *** stack 
smashing detected ***: terminated
Added tag(s) moreinfo.

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

Processed: Re: Bug#1000919: ldc: Please upgrade to llvm-toolchain-12 or 13

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1000919 [src:ldc] ldc: Please upgrade to llvm-toolchain-12 or 13
Severity set to 'serious' from 'important'
> retitle -1 ldc: FTBFS with llvm-toolchain-13
Bug #1000919 [src:ldc] ldc: Please upgrade to llvm-toolchain-12 or 13
Changed Bug title to 'ldc: FTBFS with llvm-toolchain-13' from 'ldc: Please 
upgrade to llvm-toolchain-12 or 13'.
> tags -1 sid bookworm ftbfs
Bug #1000919 [src:ldc] ldc: FTBFS with llvm-toolchain-13
Added tag(s) sid, ftbfs, and bookworm.
> found -1 1:1.28.0-1
Bug #1000919 [src:ldc] ldc: FTBFS with llvm-toolchain-13
Marked as found in versions ldc/1:1.28.0-1.

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

Processed: Re: Bug#1000930: faust: Please upgrade to llvm-toolchain-12 or 13

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.33.1~ds0-1
Bug #1000930 [src:faust] faust: Please upgrade to llvm-toolchain-12 or 13
Marked as found in versions faust/2.33.1~ds0-1.
> severity -1 serious
Bug #1000930 [src:faust] faust: Please upgrade to llvm-toolchain-12 or 13
Severity set to 'serious' from 'important'
> retitle -1 faust: FTBFS with llvm-toolchain-13
Bug #1000930 [src:faust] faust: Please upgrade to llvm-toolchain-12 or 13
Changed Bug title to 'faust: FTBFS with llvm-toolchain-13' from 'faust: Please 
upgrade to llvm-toolchain-12 or 13'.
> tags -1 sid bookworm ftbfs
Bug #1000930 [src:faust] faust: FTBFS with llvm-toolchain-13
Added tag(s) sid, bookworm, and ftbfs.

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

Processed: Re: Bug#1000923: ghdl: Please upgrade to llvm-toolchain-12 or 13

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1000923 [src:ghdl] ghdl: Please upgrade to llvm-toolchain-12 or 13
Severity set to 'serious' from 'important'
> retitle -1 ghdl: FTBFS with llvm-toolchain-13
Bug #1000923 [src:ghdl] ghdl: Please upgrade to llvm-toolchain-12 or 13
Changed Bug title to 'ghdl: FTBFS with llvm-toolchain-13' from 'ghdl: Please 
upgrade to llvm-toolchain-12 or 13'.
> tags -1 sid bookworm ftbfs
Bug #1000923 [src:ghdl] ghdl: FTBFS with llvm-toolchain-13
Added tag(s) sid, ftbfs, and bookworm.

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

Bug#1000753: poliastro FTBFS: plugin flit failed with: Use [project] table for metadata or [tool.flit.metadata], not both

[Scott Kitterman]

On Sun, 28 Nov 2021 14:17:14 + "Rebecca N. Palmer" 
 wrote:
> Package: python3-poliastro
> Version: 0.15.2-3
> Severity: serious
> 
> Fails to build with the error
> 
> E: pybuild pybuild:354: build: plugin flit failed with: Use [project] 
> table for metadata or [tool.flit.metadata], not both.

this should be pretty trivially resolved by dropping Revert-the-adoption-
PEP-621-metadata.patch and bumping the minimum flit version in build-depends to 
3.2.  Now that we have flit 3.3 in the archive, using the PEP 621 metadata is 
not a problem.

Scott K

Processed: tagging 996380

[Debian Bug Tracking System]

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

> tags 996380 + help
Bug #996380 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS with ruby3.0: ERROR: 
Test "ruby3.0" failed:   ArgumentError:
Added tag(s) help.
> thanks
Stopping processing here.

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

Processed: tagging 996297

[Debian Bug Tracking System]

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

> tags 996297 + help
Bug #996297 [src:ruby-ice-nine] ruby-ice-nine: FTBFS with ruby3.0: ERROR: Test 
"ruby3.0" failed:   Failure/Error: expect(subject.end).to be_frozen
Added tag(s) help.
> thanks
Stopping processing here.

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

Bug#998317: marked as done (PostgreSQL 14 transition)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 18:49:53 +
with message-id 
and subject line Bug#998317: fixed in gavodachs 2.5+dfsg-1
has caused the Debian Bug report #998317,
regarding PostgreSQL 14 transition
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.)


-- 
998317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gavodachs2-server
Version: 2.3+dfsg-3
Severity: serious

gavodachs2-server currently depends on the postgresql-13 versions of
-pgsphere and -q3c, and is blocking the transition to postgresql-14:

Package: gavodachs2-server
Source: gavodachs
Version: 2.3+dfsg-3
Depends: adduser, members, postgresql-13-pgsphere, postgresql-13-q3c, 
python3-gavo (= 2.3+dfsg-3)

Both packages are providing virtual packages that would make the need
to update the dependency every year obsolete, so I would suggest
switching that to:

Depends: postgresql-pgsphere, postgresql-q3c

Alternatively, switch it to postgresql-14-pgsphere, postgresql-14-q3c

(pgsphere itself still has problems with PG14 to be resolved, but
moving to the version-less dependency would already work now.)

Christoph
--- End Message ---
--- Begin Message ---
Source: gavodachs
Source-Version: 2.5+dfsg-1
Done: Markus Demleitner 

We believe that the bug you reported is fixed in the latest version of
gavodachs, 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.
Markus Demleitner  (supplier of updated gavodachs 
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, 17 Nov 2021 13:55:14 +0100
Source: gavodachs
Architecture: source
Version: 2.5+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Markus Demleitner 
Closes: 998317
Changes:
 gavodachs (2.5+dfsg-1) unstable; urgency=medium
 .
   [ Markus Demleitner ]
   * New upstream version 2.5+dfsg
 .
   [ Christoph Berg ]
   * Depend on postgresql-pgsphere, postgresql-q3c without a specific
 PostgreSQL version (Closes: #998317)
Checksums-Sha1:
 5b9eff13b76edac72884ee2f760faf973e0298e8 2397 gavodachs_2.5+dfsg-1.dsc
 e3d7695a4d8c8970801dbebaf9ca388b316a7973 1290240 gavodachs_2.5+dfsg.orig.tar.xz
 3b03f8c2ba76fab2561a2f2e620169cdacc26287 9332 
gavodachs_2.5+dfsg-1.debian.tar.xz
Checksums-Sha256:
 2830b7ce0bec3d6eafa476684610bdcf4680d9ab4fd15ab47e05372517dd04e3 2397 
gavodachs_2.5+dfsg-1.dsc
 7966bbb93d261aad367461f0fbe48d12a13fb2880421e4774771a58ea8b418a1 1290240 
gavodachs_2.5+dfsg.orig.tar.xz
 1a31e7f8b93f29c05a437ef4ae72b08e3d74f95e9985b904b5f607902b70607e 9332 
gavodachs_2.5+dfsg-1.debian.tar.xz
Files:
 3a4aca303f2a9f1f8cb7968083f642d0 2397 python optional gavodachs_2.5+dfsg-1.dsc
 740c3aed005a09d8ab9b7d483af01701 1290240 python optional 
gavodachs_2.5+dfsg.orig.tar.xz
 e591aebb29527f31bf3e0ee83fcd6884 9332 python optional 
gavodachs_2.5+dfsg-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmGnvWgACgkQcRWv0HcQ
3Pcq3BAAj6AjqTnNtbnm+rS2B9OYwkruGUl90b2nJ+/ZagDDtcq7HyV1AGVMgl/Q
Rx/QKyPkDc+QgwV/Rlbhzd+D+G4qPFeOzWZ0gsruzgmaDaCEphoainZYINGsXGUb
FpBq+bFS3s6RbxIVRJFDAwJzqPrEtJWPgK01pmM9+bgl13rUFQJbgCuoNmh/7sMW
gmx9qzkWdfl7ENtbI7ytnSC4ZwlBcshr29WaCm4EXdIsr4ocWMYd5Klod7b+ZMaa
BNzSibjyhDWqLc0fNWlM3vyv/OqinULDikAShBWfvz9wrBdfw5KgtVrxeGl8cPuh
SN5BtIBSvINrOQK0fIskYXfksv3YKhHhQSNjL5azovqvcH+3W1ZByw70FVPzFx7U
gmmd6rJYIyLdvpedgWORof9ef9i3JFP1XR6lNipAAl6/EeoazWzldr8vrQzr/29x
C64cSfNn2DlmS1DdqNOWeax91uutTwOqRXPlL02OyntShdIkpawMP7Rd9zxm/Ii7
HyKiVzokXKJiLZR2ui7NH8PNngjewC86PbGSnxj8l5eZoaIUiXTPp8dQg+gc4tCm
IBixQ84YoM/7ZwV6asrFv4bKpD29c9V/9zzKQo7kLVFAFxsmN8qBQPOkuP1VRCn7
2RDjAtASsr2iUhQIxyntpo/V2hpig2HYa02jddBZdhZ1oSP5SIU=
=TMl3
-END PGP SIGNATURE End Message ---

Bug#1000958: /etc/aliases dosn't work since bullseye

[Jörg Frings-Fürst]

Hi Marc,

Am Mittwoch, dem 01.12.2021 um 18:48 +0100 schrieb Marc Haber:
> On Wed, Dec 01, 2021 at 05:44:32PM +0100, Jörg Frings-Fürst wrote:
> > Here are the update-exim4.conf.conf:
> > 
> > dc_eximconfig_configtype='satellite'
> 
> That is the Debconf option "mail sent by smarthost; no local mail". The
> behavior actually means "no local mail". Was that actually your
> intention?
> 
> > And the output of `exim4 -D+all -bt logcheck.x` is:
> > 
> > exim: macro name set by -D must start with an upper case letter
> 
> Sorry, I didn't do that for too long. it's a small d.
> 
> exim -d+all foo@example
> 

No problem ;-)

> exim -d+all root@X
18:36:38  7034 Exim version 4.94.2 uid=0 gid=0 pid=7034 D=fff9
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC 
Event I18N OCSP PIPE_CONNECT PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Compiler: GCC [10.2.1 20210110]
Library version: Glibc: Compile: 2.31
Runtime: 2.31
Library version: BDB: Compile: Berkeley DB 5.3.28: (September  9, 2013)
  Runtime: Berkeley DB 5.3.28: (September  9, 2013)
Library version: GnuTLS: Compile: 3.7.1
 Runtime: 3.7.1
Library version: IDN2: Compile: 2.3.0
   Runtime: 2.3.0
Library version: Stringprep: Compile: 1.33
 Runtime: 1.33
Library version: PCRE: Compile: 8.39
   Runtime: 8.39 2016-06-14
18:36:38  7034 Total 14 lookups
WHITELIST_D_MACROS: "OUTGOING"
TRUSTED_CONFIG_LIST: "/etc/exim4/trusted_configs"
18:36:38  7034 changed uid/gid: forcing real = effective
18:36:38  7034   uid=0 gid=0 pid=7034
18:36:38  7034   auxiliary group list: 
18:36:38  7034 seeking password data for user "uucp": cache not available
18:36:38  7034 getpwnam() succeeded uid=10 gid=10
18:36:38  7034 configuration file is /var/lib/exim4/config.autogenerated
18:36:38  7034 log selectors = cffc 19005022 000f
18:36:38  7034 cwd=/root 3 args: exim -d+all root@x
18:36:38  7034 trusted user
18:36:38  7034 admin user
18:36:38  7034 changed uid/gid: privilege not needed
18:36:38  7034   uid=107 gid=111 pid=7034
18:36:38  7034   auxiliary group list: 111
18:36:38  7034 seeking password data for user "mail": cache not available
18:36:38  7034 getpwnam() succeeded uid=8 gid=8
18:36:38  7034  ╭considering: $1
18:36:38  7034  ├──expanding: $1
18:36:38  7034  ╰─result: root
18:36:38  7034 user name "root" extracted from gecos field "root"
18:36:38  7034 originator: uid=0 gid=0 login=root name=root
18:36:38  7034 sender address = root@x
18:36:38  7034 set_process_info:  7034 accepting a local non-SMTP message from 
 Greetings
> Marc
> 

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D


Jörg Frings-Fürst
D-54470 Lieser

git:  https://jff.email/cgit/


Threema: SYR8SJXB
Skype: joergpenguin
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Processed: Bug#996380 marked as pending in ruby-safe-yaml

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #996380 [src:ruby-safe-yaml] ruby-safe-yaml: FTBFS with ruby3.0: ERROR: 
Test "ruby3.0" failed:   ArgumentError:
Added tag(s) pending.

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

Bug#996380: marked as pending in ruby-safe-yaml

[Daniel Leidert]

Control: tag -1 pending

Hello,

Bug #996380 in ruby-safe-yaml 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-safe-yaml/-/commit/c41b54f5b21e3790adc8ed2973b848cdd56140ab


Add patch to fix build with Ruby 3.0

  * d/patches/fix_ruby_3_compatibility.patch: Add patch.
- Allow to run the gem with Ruby 3.0 (closes: #996380).
  * d/patches/series: Adjust.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996380

Bug#1000958: /etc/aliases dosn't work since bullseye

[Marc Haber]

On Wed, Dec 01, 2021 at 05:44:32PM +0100, Jörg Frings-Fürst wrote:
> Here are the update-exim4.conf.conf:
> 
> dc_eximconfig_configtype='satellite'

That is the Debconf option "mail sent by smarthost; no local mail". The
behavior actually means "no local mail". Was that actually your
intention?

> And the output of `exim4 -D+all -bt logcheck.x` is:
> 
> exim: macro name set by -D must start with an upper case letter

Sorry, I didn't do that for too long. it's a small d.

exim -d+all foo@example

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#997357: marked as done (ruby-fakefs: FTBFS: ERROR: Test "ruby2.7" failed.)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 17:33:58 +
with message-id 
and subject line Bug#997357: fixed in ruby-fakefs 1.2.0-2
has caused the Debian Bug report #997357,
regarding ruby-fakefs: FTBFS: ERROR: Test "ruby2.7" failed.
to be marked as done.

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

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


-- 
997357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fakefs
Version: 1.2.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

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


Relevant part (hopefully):
> /usr/bin/ruby2.7 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby2.7  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-fakefs/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -e gem\ \"fakefs\"
> 
> ┌──┐
> │ Run tests for ruby2.7 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-fakefs/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0
>  ruby2.7 -S rake -f debian/ruby-tests.rake
> Run options: --seed 31838
> 
> # Running:
> 
> F.S..F...
> 
> Finished in 0.704559s, 1000.6255 runs/s, 1950.1552 assertions/s.
> 
>   1) Failure:
> FakeFSTest#test_can_chown_files [/<>/test/fakefs_test.rb:1442]:
> Expected: 0
>   Actual: 1001
> 
>   2) Failure:
> FakeFSTest#test_can_chown_R_files [/<>/test/fakefs_test.rb:1479]:
> Expected: 0
>   Actual: 1001
> 
> 705 runs, 1374 assertions, 2 failures, 0 errors, 1 skips
> 
> You have skipped tests. Run with --verbose for details.
> rake aborted!
> Command failed with status (1)
> /usr/share/rubygems-integration/all/gems/rake-13.0.3/exe/rake:27:in ` (required)>'
> Tasks: TOP => default => test
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.7" failed.


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/ruby-fakefs_1.2.0-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-fakefs
Source-Version: 1.2.0-2
Done: Daniel Leidert 

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

Debian distribution maintenance software
pp.
Daniel Leidert  (supplier of updated ruby-fakefs package)

(This message was generated automatically at their request; 

Processed: closing 997322

[Debian Bug Tracking System]

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

> close 997322
Bug #997322 [src:ycmd] ycmd: FTBFS: FileNotFoundError: [Errno 2] No such file 
or directory: '/usr/share/unicode/emoji/emoji-data.txt'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1000958: /etc/aliases dosn't work since bullseye

[Jörg Frings-Fürst]

Hello Marc,


Am Mittwoch, dem 01.12.2021 um 15:58 +0100 schrieb Marc Haber:
> On Wed, Dec 01, 2021 at 02:25:13PM +0100, Jörg Frings-Fürst wrote:
> > here are my config and the logs:
> > 
> > /etc/aliases:
> > 
> > 
> > # /etc/aliases
> > mailer-daemon: postmaster
> > postmaster: root
> > nobody: root
> > hostmaster: root
> > usenet: root
> > news: root
> > webmaster: root
> > www: root
> > ftp: root
> > abuse: root
> > noc: root
> > security: root
> > root: ser...@x.de
> > logcheck: root
> > 
> > /etc/logcheck/logcheck.conf (without comments):
> > REPORTLEVEL="server"
> > SENDMAILTO="logcheck"
> > MAILASATTACH=0
> > FQDN=1
> > 
> > 
> > /var/log/exim4/mainlog:
> > 2021-12-01 13:02:03 1msPFL-0002D9-Dn <= logcheck@X U=logcheck
> > P=local S=19800
> > 2021-12-01 13:02:03 1msPFL-0002D9-Dn => logcheck@X R=smarthost
> > T=remote_smtp_smarthost H=mail.snct-dialer.de [62.138.12.194]
> > X=TLS1.2:ECDHE_SECP256R1__RSA_SHA256__AES_256_GCM:256 CV=yes
> > DN="CN=mail.jff.email" A=plain C="250 2.0.0 Ok: queued as
> > C02CE6BC824B"
> > 2021-12-01 13:02:03 1msPFL-0002D9-Dn Completed
> 
> We'd need update-exim4.conf.conf as well, and probably exim -D+all -
> bt
> logcheck@X.
> 
Here are the update-exim4.conf.conf:

dc_eximconfig_configtype='satellite'
dc_other_hostnames=''
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost='snct7'
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='mail.xx.de'
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='true'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'


And the output of `exim4 -D+all -bt logcheck.x` is:

exim: macro name set by -D must start with an upper case letter

> Greetings
> Marc
> 

CU
Jörg


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D


Jörg Frings-Fürst
D-54470 Lieser

git:  https://jff.email/cgit/


Threema: SYR8SJXB
Skype: joergpenguin
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#978893: marked as done (ripperx: ftbfs with autoconf 2.70)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 16:04:47 +
with message-id 
and subject line Bug#978893: fixed in ripperx 2.8.0-2.1
has caused the Debian Bug report #978893,
regarding ripperx: ftbfs with autoconf 2.70
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.)


-- 
978893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978893
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ripperx
Version: 2.8.0-2
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270

[This bug report is not targeted to the upcoming bullseye release]

The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/ripperx_2.8.0-2_unstable_ac270.log
The last lines of the build log are at the end of this report.

To build with autoconf 2.70, please install the autoconf package from
experimental:  apt-get -t=experimental install autoconf 

[...]
 from cddbp.c:25:
/usr/include/glib-2.0/glib/gtypes.h:545:26: note: declared here
  545 | typedef struct _GTimeVal GTimeVal 
GLIB_DEPRECATED_TYPE_IN_2_62_FOR(GDateTime);
  |  ^~~~
make[3]: *** [Makefile:480: main_data.o] Error 1
make[3]: *** [Makefile:480: cddbp.o] Error 1
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from select_frame_handler.h:8,
 from cddb.c:33:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:64: warning: ‘GTypeDebugFlags’ is 
deprecated [-Wdeprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  |^
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:22,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from select_frame_handler.h:8,
 from cddb.c:33:
/usr/include/glib-2.0/gobject/gtype.h:685:3: note: declared here
  685 | } GTypeDebugFlags GLIB_DEPRECATED_TYPE_IN_2_36;
  |   ^~~
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from select_frame_handler.h:8,
 from cddb.c:33:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:12: warning: ‘GTimeVal’ is 
deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from cddb.c:25:
/usr/include/glib-2.0/glib/gtypes.h:545:26: note: declared here
  545 | typedef struct _GTimeVal GTimeVal 
GLIB_DEPRECATED_TYPE_IN_2_62_FOR(GDateTime);
  |  ^~~~
cddb.c: In function ‘int do_cddb(char**, char**, int, int, long int*, const 
char*, int, int)’:
cddb.c:239:10: warning: ‘template class std::auto_ptr’ is deprecated 
[-Wdeprecated-declarations]
  239 | std::auto_ptr  server_ptr (new char[strlen(server)+1]);
  |  ^~~~
In file included from /usr/include/c++/10/memory:83,
 from cddb.c:37:
/usr/include/c++/10/bits/unique_ptr.h:57:28: note: declared here
   57 |   template class auto_ptr;
  |^~~~
cddb.c: In function ‘int read_local_file(char*, int, int, long int*)’:

Bug#994785: marked as done (python-ase: autopkgtest regression on arm64/ppc64el: TestSlab.test_vibration_on_surface)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 15:22:56 +
with message-id 
and subject line Bug#994785: fixed in python-ase 3.22.1-1
has caused the Debian Bug report #994785,
regarding python-ase: autopkgtest regression on arm64/ppc64el: 
TestSlab.test_vibration_on_surface
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.)


-- 
994785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ase
Version: 3.22.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
python-ase from testing3.22.0-1
all others from testingfrom testing

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

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

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

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
python-ase/3.22.0-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=python-ase

https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-ase/15401492/log.gz

=== FAILURES
===
__ TestSlab.test_vibration_on_surface
__

self = 
testdir =
PosixPath('/tmp/pytest-of-debci/pytest-0/test_vibration_on_surface0')

def test_vibration_on_surface(self, testdir):
from ase.build import fcc111, add_adsorbate
ag_slab = fcc111('Ag', (4, 4, 2), a=2)
n2 = Atoms('N2', positions=[[0., 0., 0.],
[0., np.sqrt(2), np.sqrt(2)]])
add_adsorbate(ag_slab, n2, height=1, position='fcc')

# Add an interaction between the N atoms
hessian_bottom_corner = np.zeros((2, 3, 2, 3))
hessian_bottom_corner[-1, :, -2] = [1, 1, 1]
hessian_bottom_corner[-2, :, -1] = [1, 1, 1]

hessian = np.zeros((34, 3, 34, 3))
hessian[32:, :, 32:, :] = hessian_bottom_corner

ag_slab.calc = ForceConstantCalculator(hessian.reshape((34 * 3,
34 * 3)),
   ref=ag_slab.copy(),
   f0=np.zeros((34, 3)))

# Check that Vibrations with restricted indices returns correct
Hessian
vibs = Vibrations(ag_slab, indices=[-2, -1])
vibs.run()
vibs.read()

assert_array_almost_equal(vibs.get_vibrations().get_hessian(),
  hessian_bottom_corner)

# These should blow up if the vectors don't match number of atoms
vibs.summary()
vibs.write_jmol()

for i in range(6):
# Frozen atoms should have zero displacement
assert_array_almost_equal(vibs.get_mode(i)[0], [0., 0., 0.])

# The N atoms should have finite displacement
>   assert np.all(vibs.get_mode(i)[-2:, :])
E   assert False
E+  where False = (array([[
0.e+00, -2.21811191e-17,  2.25296944e-17],\n
[-1.88935009e-01,  1.88935009e-01,  1.69152862e-18]]))
E+where  = np.all

/usr/lib/python3/dist-packages/ase/test/vibrations/test_vib.py:527:
AssertionError
- Captured stdout call
-
-
  #meV cm^-1
-
  0   29.9i241.3i
  10.0   0.0
  20.0   0.0
  30.0   0.0
  40.0   0.0
  5   29.9 241.3
-
Zero-point energy: 0.015 eV
--- Captured stdout teardown
---
Testdir: /tmp/pytest-of-debci/pytest-0/test_vibration_on_surface0
Global seed for "test/vibrations/test_vib.py:test_vibration_on_surface"
was: 16



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

Bug#999626: [Maxima-discuss] maxima-emacs: fails to install with xemacs21

[Camm Maguire]

Greetings!  Am uploading a fix for now.  cl-lib for xemacs21 can be
found in the mmm-mode package.  Other change is that image-map needs to
be nil if not bound.  Quite a few byte-compilation warnings in both
flavors, suppressed on install, but maintainers might want to look at
cleaning these up.

Take care,

Raymond Toy  writes:

> On Thu, Nov 25, 2021 at 7:02 PM Leo Butler  wrote:
>
>  Hi Camm,
>
>  I committed those changes after changes in emacs broke imaxima/imath.
>
>  My opinion is that xemacs is a dead project and it is a waste of time
>  maintaining patches for something that is dead.
>
> As a long-time user of xemacs (but no longer), I'm sorry to say I agree.  
> XEmacs had some nice things, but it's just too different from emacs now.
>
>  Best,
>  Leo
>
>  PS: I see that xemacs is currently blocked in debian testing:
>
>  https://tracker.debian.org/pkg/xemacs21
>
>  Camm Maguire  writes:
>
>  > 
>  > Caution: This message was sent from outside the University of Manitoba.
>  > 
>  >
>  > forwarded 999626 maxima-disc...@lists.sourceforge.net
>  > thanks
>  >
>  > Greetings!  Simple patch attempts fail when trying to get the latest
>  > working with xemacs -- perhaps an expert here can suggest a patch?
>  >
>  > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999626
>  >
>  > Take care,
>
>  ___
>  Maxima-discuss mailing list
>  maxima-disc...@lists.sourceforge.net
>  https://lists.sourceforge.net/lists/listinfo/maxima-discuss

-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Bug#1000467: marked as done (rpm, autopkgtest failure on armhf)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 15:05:54 +
with message-id 
and subject line Bug#1000467: fixed in rpm 4.17.0+dfsg1-4
has caused the Debian Bug report #1000467,
regarding rpm, autopkgtest failure on armhf
to be marked as done.

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

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


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

Package: rpm
Version: 4.17.0+dfsg1-1
Severity: serious

The new version of rpm added an autopkgtest, but unfortunately it's failing on 
armhf
and blocking the migration to testing (and hence blocking the fixes for two 
other rc bugs).

autopkgtest [04:40:50]: test rpmbuild: env PYTHONPATH="$(pwd)/debian/tests/src" 
python3 -B -u -m rpmtest -b /usr/bin -d debian/tests/data
autopkgtest [04:40:50]: test rpmbuild: [---
Using /tmp/tmpma2atafk as a temporary directory
Querying `rpm` for the target architecture
Unexpected `rpm --eval` output: '%{_arch}'
autopkgtest [04:40:51]: test rpmbuild: ---]
autopkgtest [04:40:51]: test rpmbuild:  - - - - - - - - - - results - - - - - - 
- - - -
rpmbuild FAIL non-zero exit status 1
autopkgtest [04:40:51]:  summary
rpmbuild FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: rpm
Source-Version: 4.17.0+dfsg1-4
Done: Peter Pentchev 

We believe that the bug you reported is fixed in the latest version of
rpm, 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.
Peter Pentchev  (supplier of updated rpm 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, 01 Dec 2021 16:39:27 +0200
Source: rpm
Architecture: source
Version: 4.17.0+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: RPM packaging team 
Changed-By: Peter Pentchev 
Closes: 1000467
Changes:
 rpm (4.17.0+dfsg1-4) unstable; urgency=medium
 .
   * Team upload.
   * Teach the autopkgtest about RPM target architecture families like
 "arm": try to expand the result of `rpm --eval '%{_arch}'` to see
 whether it corresponds to a list of architecture names.
 Closes: #1000467 (again, sorry!).
Checksums-Sha1:
 f820107ed9ba157cadd494121cb237befe4655b3 3069 rpm_4.17.0+dfsg1-4.dsc
 6241c3b05ed0e8ae71a5534eee5e446562c7f6fe 47348 rpm_4.17.0+dfsg1-4.debian.tar.xz
Checksums-Sha256:
 f8ac44b6708fae58e8a6333fc0bbade9331b7745d64e787e3bd77c3a61cb499c 3069 
rpm_4.17.0+dfsg1-4.dsc
 55da1d7ed67c351e2d5daeafdd8d5e990542ca8a96ff63ef26e88b42b4c107cb 47348 
rpm_4.17.0+dfsg1-4.debian.tar.xz
Files:
 ac90b3ab7f8a2b95dafed6c5602d2b34 3069 admin optional rpm_4.17.0+dfsg1-4.dsc
 79ab3d77a8b6c4bbb8f1db22efa69a22 47348 admin optional 
rpm_4.17.0+dfsg1-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmGniVUQHHJvYW1AZGVi
aWFuLm9yZwAKCRBlHu+wJSffEwK9D/9ymRJmLsP1iElf4ucJAzQUkef0cWFmcUuy
dJyMxlAGe2afKW+jsD34MytBzBueCtduEjvIysls9UazjfwnErFpuKgvOF9lCkzl
esdm9D8JmH1Rn02hNYTsnlnmUWgO998lFluO4DnNtvUQr5T6URL0X3UCepdfI+bn
4IUfGUqH1HLFuWV3cqYuM9FptZLFZn4QSMpwDRRtTOqFvb5rQhv4OQMKko10fbzp
Sp2mksS4Ekig2sfjlntob/NaZLCUzFzdXRwsAHgXhRFwwynlnBMQMj75p3YKrkJR
4VZN8RGoe+nlZZID2z5PVXaCH9bbl0XG2GE4OccM+CThL0c3WsGA1ZOS6e2aTkVf
xID2Q2tjUQVbsAiUBa4qoPV8K3OY9xH4vrsc22AEmjoUDHL7ebneWuMhKDFmXjuT
ud8GXhUwnsl5hj5QCoHkPxXG0xE3LI/tonb08CKqXFQp0dfoplttJMH8Hbf5Gnn3
mQBr1Xta/bXnZHLRKEpwoNY7HH5CoexlAhYGRUDUOOG1bx3nIjT7iAsL/lAmF7R1
Bp7OxCmALxKcE4lS+HNQVxWKWy1mqQH+NXCWH3vj6mBL094+pOFMLdMDV87lBUKJ
j6pVKbxZDVDi2uui56nQYtBRIAajFWPj5lvDYDFnBYvisEz9gstBFZT6PhcktGwd
Hi4gS4Ep7Q==
=FWz8
-END PGP SIGNATURE End Message ---

Bug#1000960: Wrong permissions after fresh install

[Marc Haber]

On Wed, Dec 01, 2021 at 01:36:52PM +, Jörg Frings-Fürst wrote:
> /etc/exim4/passwd.client
> 2021-12-01 09:37:02 1msM2w-kF-2M failed to expand "<; ${if 
> exists{/etc/exim4/passwd.client} 
> {${lookup{$host}nwildlsearch{/etc/exim4/passwd.client}{$host_address}}}{} }" 
> while checking a list: failed to open /etc/exim4/passwd.client for linear 
> search: Permission denied (euid=107 egid=111)

What are uid 107 and gid 111 on the affected system? Are there
dpkg-statoverrides present in the system?

The maintainer scripts do only chown to Debian-exim, in the alphabetic
representation.

> The same error on /var/log/exim4/mainlog.

The log gets created by exim proper. This having the wrong user/group
means something "deeper".

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1000958: /etc/aliases dosn't work since bullseye

[Marc Haber]

On Wed, Dec 01, 2021 at 02:25:13PM +0100, Jörg Frings-Fürst wrote:
> here are my config and the logs:
> 
> /etc/aliases:
> 
> 
> # /etc/aliases
> mailer-daemon: postmaster
> postmaster: root
> nobody: root
> hostmaster: root
> usenet: root
> news: root
> webmaster: root
> www: root
> ftp: root
> abuse: root
> noc: root
> security: root
> root: ser...@x.de
> logcheck: root
> 
> /etc/logcheck/logcheck.conf (without comments):
> REPORTLEVEL="server"
> SENDMAILTO="logcheck"
> MAILASATTACH=0
> FQDN=1
> 
> 
> /var/log/exim4/mainlog:
> 2021-12-01 13:02:03 1msPFL-0002D9-Dn <= logcheck@X U=logcheck
> P=local S=19800
> 2021-12-01 13:02:03 1msPFL-0002D9-Dn => logcheck@X R=smarthost
> T=remote_smtp_smarthost H=mail.snct-dialer.de [62.138.12.194]
> X=TLS1.2:ECDHE_SECP256R1__RSA_SHA256__AES_256_GCM:256 CV=yes
> DN="CN=mail.jff.email" A=plain C="250 2.0.0 Ok: queued as C02CE6BC824B"
> 2021-12-01 13:02:03 1msPFL-0002D9-Dn Completed

We'd need update-exim4.conf.conf as well, and probably exim -D+all -bt
logcheck@X.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Processed: reassign 939419 to src:samba, fixed 939419 in 2:4.11.0+dfsg-1, fixed 939419 in 2:4.9.5+dfsg-5+deb10u2 ...

[Debian Bug Tracking System]

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

> reassign 939419 src:samba 2:4.9.5+dfsg-5
Bug #939419 {Done: Salvatore Bonaccorso } 
[libparse-pidl-perl] libparse-pidl-perl: version ordering issue.
Bug reassigned from package 'libparse-pidl-perl' to 'src:samba'.
No longer marked as found in versions 2:4.9.5+dfsg-5+deb10u1, 
2:4.9.5+dfsg-5+deb10u1+really0.02, and 2:4.9.5+dfsg-5.
No longer marked as fixed in versions samba/2:4.9.5+dfsg-5+deb10u2 and 
samba/2:4.11.0+dfsg-1.
Bug #939419 {Done: Salvatore Bonaccorso } [src:samba] 
libparse-pidl-perl: version ordering issue.
Marked as found in versions samba/2:4.9.5+dfsg-5.
> fixed 939419 2:4.11.0+dfsg-1
Bug #939419 {Done: Salvatore Bonaccorso } [src:samba] 
libparse-pidl-perl: version ordering issue.
Marked as fixed in versions samba/2:4.11.0+dfsg-1.
> fixed 939419 2:4.9.5+dfsg-5+deb10u2
Bug #939419 {Done: Salvatore Bonaccorso } [src:samba] 
libparse-pidl-perl: version ordering issue.
Marked as fixed in versions samba/2:4.9.5+dfsg-5+deb10u2.
> found 939419 2:4.9.5+dfsg-5+deb10u1
Bug #939419 {Done: Salvatore Bonaccorso } [src:samba] 
libparse-pidl-perl: version ordering issue.
Marked as found in versions samba/2:4.9.5+dfsg-5+deb10u1.
> found 939419 2:4.9.5+dfsg-5+deb10u1+really0.02
Bug #939419 {Done: Salvatore Bonaccorso } [src:samba] 
libparse-pidl-perl: version ordering issue.
The source 'samba' and version '2:4.9.5+dfsg-5+deb10u1+really0.02' do not 
appear to match any binary packages
Marked as found in versions samba/2:4.9.5+dfsg-5+deb10u1+really0.02.
> thanks
Stopping processing here.

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

Processed: reassign 1000735 to src:linux, tagging 974779, found 1000798 in 2.3.2+r586-7 ..., tagging 977403 ...

[Debian Bug Tracking System]

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

> reassign 1000735 src:linux
Bug #1000735 [iwlwifi] iwlwifi: start the wifi, it makes a kernel opps
Warning: Unknown package 'iwlwifi'
Bug reassigned from package 'iwlwifi' to 'src:linux'.
No longer marked as found in versions firmware-iwlwifi.
Ignoring request to alter fixed versions of bug #1000735 to the same values 
previously set
> tags 974779 + sid bookworm
Bug #974779 [julia] julia: Please upgrade to llvm-toolchain-11
Added tag(s) bookworm and sid.
> found 1000798 2.3.2+r586-7
Bug #1000798 [src:vde2] vde2: Provides the same binary package as another 
source package
Marked as found in versions vde2/2.3.2+r586-7.
> found 1000797 4.0.1-2
Bug #1000797 [src:vdeplug4] vdeplug4: Provides the same binary package as 
another source package
Marked as found in versions vdeplug4/4.0.1-2.
> found 977403 1.0.2-8
Bug #977403 [php-text-captcha] php-text-captcha: Not compatible with php8.0
Marked as found in versions php-text-captcha/1.0.2-8.
> tags 977403 + sid bookworm
Bug #977403 [php-text-captcha] php-text-captcha: Not compatible with php8.0
Added tag(s) sid and bookworm.
> tags 1000818 + bullseye bookworm sid
Bug #1000818 [python3-ulmo] python3-ulmo: if rebuilt now, missing python3-suds 
dependency
Added tag(s) bullseye, sid, and bookworm.
> thanks
Stopping processing here.

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

Bug#1000960: Wrong permissions after fresh install

[Jörg Frings-Fürst]

Package: exim4-daemon-light
Version: 4.94.2-7
Severity: grave
File: /usr/sbin/exim4

Hello,

on a fresh install exim4 files has wrong permissions:

/etc/exim4/passwd.client
2021-12-01 09:37:02 1msM2w-kF-2M failed to expand "<; ${if 
exists{/etc/exim4/passwd.client} 
{${lookup{$host}nwildlsearch{/etc/exim4/passwd.client}{$host_address}}}{} }" 
while checking a list: failed to open /etc/exim4/passwd.client for linear 
search: Permission denied (euid=107 egid=111)


The same error on /var/log/exim4/mainlog.


CU
Jörg

-- Package-specific info:
Exim version 4.94.2 #2 built 13-Jul-2021 16:04:57
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC 
Event I18N OCSP PIPE_CONNECT PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is 
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated
# /etc/exim4/update-exim4.conf.conf
#
# Edit this file and /etc/mailname by hand and execute update-exim4.conf
# yourself or use 'dpkg-reconfigure exim4-config'
#
# Please note that this is _not_ a dpkg-conffile and that automatic changes
# to this file might happen. The code handling this will honor your local
# changes, so this is usually fine, but will break local schemes that mess
# around with multiple versions of the file.
#
# update-exim4.conf uses this file to determine variable values to generate
# exim configuration macros for the configuration file.
#
# Most settings found in here do have corresponding questions in the
# Debconf configuration, but not all of them.
#
# This is a Debian specific file

dc_eximconfig_configtype='satellite'
dc_other_hostnames=''
dc_local_interfaces='127.0.0.1 ; ::1'
dc_readhost='snct7'
dc_relay_domains=''
dc_minimaldns='false'
dc_relay_nets=''
dc_smarthost='xxx'
CFILEMODE='644'
dc_use_split_config='false'
dc_hide_mailname='true'
dc_mailname_in_oh='true'
dc_localdelivery='mail_spool'
mailname:snct7
# /etc/default/exim4
EX4DEF_VERSION=''

# 'combined' -   one daemon running queue and listening on SMTP port
# 'no'   -   no daemon running the queue
# 'separate' -   two separate daemons
# 'ppp'  -   only run queue with /etc/ppp/ip-up.d/exim4.
# 'nodaemon' - no daemon is started at all.
# 'queueonly' - only a queue running daemon is started, no SMTP listener.
# setting this to 'no' will also disable queueruns from /etc/ppp/ip-up.d/exim4
QUEUERUNNER='combined'
# how often should we run the queue
QUEUEINTERVAL='30m'
# options common to quez-runner and listening daemon
COMMONOPTIONS=''
# more options for the daemon/process running the queue (applies to the one
# started in /etc/ppp/ip-up.d/exim4, too.
QUEUERUNNEROPTIONS=''
# special flags given to exim directly after the -q. See exim(8)
QFLAGS=''
# Options for the SMTP listener daemon. By default, it is listening on
# port 25 only. To listen on more ports, it is recommended to use
# -oX 25:587:10025 -oP /run/exim4/exim.pid
SMTPLISTENEROPTIONS=''

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

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

Versions of packages exim4-daemon-light depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  exim4-base 4.94.2-7
ii  libc6  2.31-13+deb11u2
ii  libcrypt1  1:4.4.18-4
ii  libdb5.3   5.3.28+dfsg1-0.8
ii  libgnutls-dane03.7.1-5
ii  libgnutls303.7.1-5
ii  libidn11   1.33-3
ii  libidn2-0  2.3.0-5
ii  libnsl21.3.0-2
ii  libpcre3   2:8.39-13

exim4-daemon-light recommends no packages.

exim4-daemon-light suggests no packages.

-- debconf information:
  exim4-daemon-light/drec:

Bug#1000958: /etc/aliases dosn't work since bullseye

[Jörg Frings-Fürst]

Hello,

here are my config and the logs:

/etc/aliases:


# /etc/aliases
mailer-daemon: postmaster
postmaster: root
nobody: root
hostmaster: root
usenet: root
news: root
webmaster: root
www: root
ftp: root
abuse: root
noc: root
security: root
root: ser...@x.de
logcheck: root

/etc/logcheck/logcheck.conf (without comments):
REPORTLEVEL="server"
SENDMAILTO="logcheck"
MAILASATTACH=0
FQDN=1


/var/log/exim4/mainlog:
2021-12-01 13:02:03 1msPFL-0002D9-Dn <= logcheck@X U=logcheck
P=local S=19800
2021-12-01 13:02:03 1msPFL-0002D9-Dn => logcheck@X R=smarthost
T=remote_smtp_smarthost H=mail.snct-dialer.de [62.138.12.194]
X=TLS1.2:ECDHE_SECP256R1__RSA_SHA256__AES_256_GCM:256 CV=yes
DN="CN=mail.jff.email" A=plain C="250 2.0.0 Ok: queued as C02CE6BC824B"
2021-12-01 13:02:03 1msPFL-0002D9-Dn Completed



If you have questions, please ask me.

CU
Jörg


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D


Jörg Frings-Fürst
D-54470 Lieser

git:  https://jff.email/cgit/


Threema: SYR8SJXB
Skype: joergpenguin
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#1000661: Missing b-dep on libbase64-ocaml-dev

[Andreas Beckmann]

Control: tag -1 sid bookworm
Control: close -1 1:4.2.4-1

On Wed, 1 Dec 2021 16:09:41 +0800 Andy Li  wrote:

I've uploaded 1:4.2.4-1, which fixed the build problem regarding base64.


So we can close this.

Andreas

Processed: Re: Bug#1000661: Missing b-dep on libbase64-ocaml-dev

[Debian Bug Tracking System]

Processing control commands:

> tag -1 sid bookworm
Bug #1000661 [haxe] Missing b-dep on libbase64-ocaml-dev
Added tag(s) bookworm and sid.
> close -1 1:4.2.4-1
Bug #1000661 [haxe] Missing b-dep on libbase64-ocaml-dev
Marked as fixed in versions haxe/1:4.2.4-1.
Bug #1000661 [haxe] Missing b-dep on libbase64-ocaml-dev
Marked Bug as done

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

Bug#1000958: /etc/aliases dosn't work since bullseye

[Jörg Frings-Fürst]

Package: exim4-daemon-light
Version: 4.94.2-7
Severity: critical
File: /usr/sbin/exim4

Hello, 

on a new bullseye system /etc/aliases dosn't work.

I send all files with the next mail.


CU
Jörg


-- Package-specific info:
Exim version 4.94.2 #2 built 13-Jul-2021 16:04:57
Copyright (c) University of Cambridge, 1995 - 2018
(c) The Exim Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2018
Berkeley DB: Berkeley DB 5.3.28: (September  9, 2013)
Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages DANE DKIM DNSSEC 
Event I18N OCSP PIPE_CONNECT PRDR SOCKS TCP_Fast_Open
Lookups (built-in): lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmjz 
dbmnz dnsdb dsearch nis nis0 passwd
Authenticators: cram_md5 plaintext
Routers: accept dnslookup ipliteral manualroute queryprogram redirect
Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp
Fixed never_users: 0
Configure owner: 0:0
Size of off_t: 8
Configuration file search path is 
/etc/exim4/exim4.conf:/var/lib/exim4/config.autogenerated
Configuration file is /var/lib/exim4/config.autogenerated

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

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

Versions of packages exim4-daemon-light depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  exim4-base 4.94.2-7
ii  libc6  2.31-13+deb11u2
ii  libcrypt1  1:4.4.18-4
ii  libdb5.3   5.3.28+dfsg1-0.8
ii  libgnutls-dane03.7.1-5
ii  libgnutls303.7.1-5
ii  libidn11   1.33-3
ii  libidn2-0  2.3.0-5
ii  libnsl21.3.0-2
ii  libpcre3   2:8.39-13

exim4-daemon-light recommends no packages.

exim4-daemon-light suggests no packages.

-- debconf information:
  exim4-daemon-light/drec:

Bug#1000863: marked as done (php-predis: missing Breaks+Replaces: libphp-predis)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 12:33:37 +
with message-id 
and subject line Bug#1000863: fixed in php-nrk-predis 1.1.9-5
has caused the Debian Bug report #1000863,
regarding php-predis: missing Breaks+Replaces: libphp-predis
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.)


-- 
1000863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-predis
Version: 1.1.9-4
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 without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package php-predis.
  Preparing to unpack .../php-predis_1.1.9-4_all.deb ...
  Unpacking php-predis (1.1.9-4) ...
  dpkg: error processing archive 
/var/cache/apt/archives/php-predis_1.1.9-4_all.deb (--unpack):
   trying to overwrite '/usr/share/php/Predis/Autoloader.php', which is also in 
package libphp-predis 0.8.3-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/php-predis_1.1.9-4_all.deb

As libphp-predis has been requested to be removed, the B+R can probably be 
unversioned.

cheers,

Andreas


libphp-predis=0.8.3-1_php-predis=1.1.9-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: php-nrk-predis
Source-Version: 1.1.9-5
Done: David Prévot 

We believe that the bug you reported is fixed in the latest version of
php-nrk-predis, 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.
David Prévot  (supplier of updated php-nrk-predis 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, 01 Dec 2021 08:11:15 -0400
Source: php-nrk-predis
Architecture: source
Version: 1.1.9-5
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 1000863
Changes:
 php-nrk-predis (1.1.9-5) unstable; urgency=medium
 .
   * Break and replace libphp-predis.
 Thanks to Andreas Beckmann  (Closes: #1000863)
Checksums-Sha1:
 7afcb4f3f8ceb120ac8650d89ee05e35dfb69fe2 1857 php-nrk-predis_1.1.9-5.dsc
 50f2cf22b95e3bea6e5a9ec9989b0e1e08c07965 30948 
php-nrk-predis_1.1.9-5.debian.tar.xz
 98217b8692571792d50c6956de9e1b7408ada0c9 8226 
php-nrk-predis_1.1.9-5_amd64.buildinfo
Checksums-Sha256:
 c9f77ed0eb1f63080dba1aa2c5ceedf73e77ff37365f06f6294e3d9d95ed007f 1857 
php-nrk-predis_1.1.9-5.dsc
 206758509bf3ca158aac23e3406697afe451022650f840741f7a833867ed9eab 30948 
php-nrk-predis_1.1.9-5.debian.tar.xz
 5a2ba19dfe5959c373b6e94e013a0b1b455ab0a011cfe54421100791b91dacc5 8226 
php-nrk-predis_1.1.9-5_amd64.buildinfo
Files:
 5034415de13cd135c979399c60f92b0d 1857 php optional php-nrk-predis_1.1.9-5.dsc
 9fec7cb3a2aaf80525f074e1b1421618 30948 php optional 
php-nrk-predis_1.1.9-5.debian.tar.xz
 8032d01ddab791f4049ae960bf9b696b 8226 php optional 
php-nrk-predis_1.1.9-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAmGnZ14SHHRhZmZpdEBk
ZWJpYW4ub3JnAAoJEAWMHPlE9r08Y0UH/3FAzXk5YCgPdKTS/0QO7o2DjrUgqkDq
E5c5jtqKZt/wPd//Gx3NwovVlgP5p71U4snXzAOQAESQhRQdT3fzZwT/bpAvZg4S
yqJSvrO68QfE7Dup1QgpAft5oAIUis+ahMSHp+m5rHgIal+wCCU77D9zqxaz9YXD
xdMfm0vQ9i50l6Xui7dEViUYNJjnw7rGJ3slILJag7NempZyoL6XJl24iq+rE9+o
64jgShR4fWM7D1LM8gG+Ueuq7Ry+o1bjQM3tPJ0oqRa4+FOQ4cisR+hQpYmQD7pf
UfpfU9YCI0ZEeDNdX/9cToPvU+qLUxT6E1LqNxjjXXz4yeaJGOoGjXY=
=2TUV
-END PGP SIGNATURE End Message ---

Processed: limit source to php-nrk-predis, tagging 1000863

[Debian Bug Tracking System]

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

> limit source php-nrk-predis
Limiting to bugs with field 'source' containing at least one of 'php-nrk-predis'
Limit currently set to 'source':'php-nrk-predis'

> tags 1000863 + pending
Bug #1000863 [php-predis] php-predis: missing Breaks+Replaces: libphp-predis
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: severity of 998377 is important

[Debian Bug Tracking System]

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

> severity 998377 important
Bug #998377 [src:mlv] mlv: FTBFS with new dash version due to bashism in 
configure.ac
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1000955: libkf5globalaccel-bin: /usr/bin/kglobalaccel5 eats up huge amount of CPU after suspend

[Filippo Rusconi]

Package: libkf5globalaccel-bin
Version: 5.78.0-3
Severity: critical
Tags: upstream
Justification: breaks the whole system
X-Debbugs-Cc: lopi...@debian.org


Greetings,

it is now a reproducible fact that my Plasma session goes awry in two different
situations:

1. When I plug in a headphones+micro (LogiTech or Jabra) with a USB connector;

2. When I suspend my laptop using the "Moon" keyboard key.

In both cases my Plasma workspace session gets unresponsive as far as the
keyboard is concerned. Interestingly, the keyboard still catches strokes *only*
when I type the Ctrl+Alt+F2 sequence to get out of Plasma and reach a console.
In that console, I run htop and I can monitor that /usr/bin/kglobalaccel5 eats
almost a third of the CPU (37%). I tried to kill (9) the process but it is
recreated anew and eats the same amount of CPU.

Note that I also see a huge CPU consumption for the following processes:

/usr/lib/xorg/Xorg (63%)
/usr/sbin/rsyslogd (14%)
/lib/systemd/systemd-journald (10%)

Yeah, I know these percentages sum up to > 100 :-( 

I have to to specify that the case 1. does not happen when I am running not
Plasma but Gnome (Wayland).

Should I install other packages to fix the problem? What can I do to help?

Sincerely,
Filippo

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

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

Versions of packages libkf5globalaccel-bin depends on:
ii  libc6  2.31-13+deb11u2
ii  libkf5coreaddons5  5.78.0-4
ii  libkf5crash5   5.78.0-3
ii  libkf5dbusaddons5  5.78.0-2
ii  libkf5globalaccel-data 5.78.0-3
ii  libkf5globalaccelprivate5  5.78.0-3
ii  libkf5windowsystem55.78.0-2
ii  libqt5core5a   5.15.2+dfsg-9
ii  libqt5gui5 5.15.2+dfsg-9
ii  libqt5widgets5 5.15.2+dfsg-9
ii  libqt5x11extras5   5.15.2-2
ii  libstdc++6 10.2.1-6
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb-xkb11.14-3
ii  libxcb11.14-3

libkf5globalaccel-bin recommends no packages.

libkf5globalaccel-bin suggests no packages.

-- no debconf information

-- 

⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD
⣾⠁⢠⠒⠀⣿⡁   Research scientist at CNRS
⢿⡄⠘⠷⠚⠋⠀   Debian Developer
⠈⠳⣄  http://msxpertsuite.org
  http://www.debian.org

Bug#994841: marked as done (sqlparse: CVE-2021-32839)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 11:03:48 +
with message-id 
and subject line Bug#994841: fixed in sqlparse 0.4.2-1
has caused the Debian Bug report #994841,
regarding sqlparse: CVE-2021-32839
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.)


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

Hi,

The following vulnerability was published for sqlparse.

CVE-2021-32839[0]:
| sqlparse is a non-validating SQL parser module for Python. In sqlparse
| versions 0.4.0 and 0.4.1 there is a regular Expression Denial of
| Service in sqlparse vulnerability. The regular expression may cause
| exponential backtracking on strings containing many repetitions of
| '\r\n' in SQL comments. Only the formatting feature that removes
| comments from SQL statements is affected by this regular expression.
| As a workaround don't use the sqlformat.format function with keyword
| strip_comments=True or the --strip-comments command line flag when
| using the sqlformat command line tool. The issues has been fixed in
| sqlparse 0.4.2.


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-32839
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32839
[1] 
https://github.com/andialbrecht/sqlparse/security/advisories/GHSA-p5w8-wqhj-9hhf
[2] 
https://github.com/andialbrecht/sqlparse/commit/8238a9e450ed1524e40cb3a8b0b3c00606903aeb

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: sqlparse
Source-Version: 0.4.2-1
Done: Michael R. Crusoe 

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated sqlparse 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, 01 Dec 2021 11:42:26 +0100
Source: sqlparse
Architecture: source
Version: 0.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Andrii Senkovych 
Changed-By: Michael R. Crusoe 
Closes: 994841
Changes:
 sqlparse (0.4.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version. Fixes CVE-2021-32839 (Closes: #994841)
   * Standards-Version: 4.6.0 (routine-update)
   * watch file standard 4 (routine-update)
Checksums-Sha1:
 b3ca812af6f9ec98e0d9d97a4851523836014c59 2462 sqlparse_0.4.2-1.dsc
 e8f821c53be3bf9874e9dbd033975e8859033d10 67771 sqlparse_0.4.2.orig.tar.gz
 bda982d52da952678421c0a8c377da9d5128edae 488 sqlparse_0.4.2.orig.tar.gz.asc
 dcbc1d072c1d7331c748e557a34604ef04dd89a2 6924 sqlparse_0.4.2-1.debian.tar.xz
 77c8724ed1f93900cf3a8fe5a820bf2c92fd8f57 8299 sqlparse_0.4.2-1_source.buildinfo
Checksums-Sha256:
 e7a4c6c04b42b2acf925ddc669530c57bcde8a4179da49fd792c7aa881a8ce23 2462 
sqlparse_0.4.2-1.dsc
 0c00730c74263a94e5a9919ade150dfc3b19c574389985446148402998287dae 67771 
sqlparse_0.4.2.orig.tar.gz
 728ea6ce0d5dbbef9114509f3dc1b9e98156d0fc1d1b9fa30199e60ce021fbc6 488 
sqlparse_0.4.2.orig.tar.gz.asc
 cf528ca8bcc69e1bca45d5a6dbf8892a447b8547a4d8928be6db08752afbd168 6924 
sqlparse_0.4.2-1.debian.tar.xz
 cd69a03daa6d8d4b429300276fcf35d95ac378d3b3226030869b97bbd826ec19 8299 
sqlparse_0.4.2-1_source.buildinfo
Files:
 a0c4d151803dd6c23cf04d5868384d27 2462 python optional sqlparse_0.4.2-1.dsc
 66dce30d92823589f5e5e043f90b4f16 67771 python optional 
sqlparse_0.4.2.orig.tar.gz
 e7f91c882d7f7530ea04cdcac540210f 488 python optional 
sqlparse_0.4.2.orig.tar.gz.asc
 9727ae5f2615730d0ac9f972922fc850 6924 python optional 
sqlparse_0.4.2-1.debian.tar.xz
 70d0e157e0b6dbf8f5f183da4609dcbc 8299 python optional 
sqlparse_0.4.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmGnUh4ACgkQPCZ2P2xn

Bug#998557: spice-gtk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: "celt051"

[Simon Chopin]

Package: spice-gtk
Version: 0.39-3
Followup-For: Bug #998557
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch
X-Debbugs-Cc: simon.cho...@canonical.com
Control: tags -1 patch

Hi,

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

  * d/rules: remove the -Dcelt051=disabled option as the whole CELT
support has been removed upstream (Closes #998557)

Thanks for considering the patch.
Cheers,
Simon

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

Kernel: Linux 5.13.0-22-generic (SMP w/24 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru spice-gtk-0.39/debian/rules spice-gtk-0.39/debian/rules
--- spice-gtk-0.39/debian/rules 2021-09-24 01:59:54.0 +0200
+++ spice-gtk-0.39/debian/rules 2021-12-01 11:52:26.0 +0100
@@ -6,7 +6,7 @@
 override_dh_auto_configure:
dh_auto_configure -- \
 -Dsmartcard=enabled -Dgtk=enabled \
--Dintrospection=enabled -Dvapi=enabled -Dcelt051=disabled \
+-Dintrospection=enabled -Dvapi=enabled \
 -Dusbredir=enabled -Dpolkit=enabled \
 -Dlz4=enabled -Dgtk_doc=enabled \
 -Dusb-acl-helper-dir=/usr/libexec \

Processed: Re: spice-gtk: FTBFS: ../meson.build:4:0: ERROR: Unknown options: "celt051"

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #998557 [src:spice-gtk] spice-gtk: FTBFS: ../meson.build:4:0: ERROR: 
Unknown options: "celt051"
Added tag(s) patch.

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

Bug#1000953: c-blosc: FTBFS on mips64el

[Bastian Germann]

Source: c-blosc
Severity: serious
Version: 1.21.1+ds2-1

The build fails on mips64el with:

98% tests passed, 35 tests failed out of 1651

Total Test time (real) = 452.24 sec

The following tests FAILED:
  1 - test_api (Failed)
  2 - test_bitshuffle_leftovers (Failed)
270 - test_compressor (Failed)
672 - test_noinit (Failed)
673 - test_nolock (Failed)
674 - test_nthreads (Failed)
1606 - test_compat_blosc-1.11.1-blosclz.cdata (Failed)
1607 - test_compat_blosc-1.11.1-lz4.cdata (Failed)
1608 - test_compat_blosc-1.11.1-lz4hc.cdata (Failed)
1609 - test_compat_blosc-1.11.1-snappy.cdata (Failed)
1610 - test_compat_blosc-1.11.1-zlib.cdata (Failed)
1611 - test_compat_blosc-1.11.1-zstd.cdata (Failed)
1612 - test_compat_blosc-1.14.0-blosclz.cdata (Failed)
1613 - test_compat_blosc-1.14.0-lz4.cdata (Failed)
1614 - test_compat_blosc-1.14.0-lz4hc.cdata (Failed)
1615 - test_compat_blosc-1.14.0-snappy.cdata (Failed)
1616 - test_compat_blosc-1.14.0-zlib.cdata (Failed)
1617 - test_compat_blosc-1.14.0-zstd.cdata (Failed)
1618 - test_compat_blosc-1.18.0-blosclz-bitshuffle.cdata (Failed)
1619 - test_compat_blosc-1.18.0-blosclz.cdata (Failed)
1620 - test_compat_blosc-1.18.0-lz4-bitshuffle.cdata (Failed)
1621 - test_compat_blosc-1.18.0-lz4.cdata (Failed)
1622 - test_compat_blosc-1.18.0-lz4hc.cdata (Failed)
1623 - test_compat_blosc-1.18.0-zlib.cdata (Failed)
1624 - test_compat_blosc-1.18.0-zstd.cdata (Failed)
1625 - test_compat_blosc-1.3.0-blosclz.cdata (Failed)
1626 - test_compat_blosc-1.3.0-lz4.cdata (Failed)
1627 - test_compat_blosc-1.3.0-lz4hc.cdata (Failed)
1628 - test_compat_blosc-1.3.0-snappy.cdata (Failed)
1629 - test_compat_blosc-1.3.0-zlib.cdata (Failed)
1630 - test_compat_blosc-1.7.0-blosclz.cdata (Failed)
1631 - test_compat_blosc-1.7.0-lz4.cdata (Failed)
1632 - test_compat_blosc-1.7.0-lz4hc.cdata (Failed)
1633 - test_compat_blosc-1.7.0-snappy.cdata (Failed)
1634 - test_compat_blosc-1.7.0-zlib.cdata (Failed)
Errors while running CTest
make[1]: *** [Makefile:94: test] Error 8
make[1]: Leaving directory '/<>/obj-mips64el-linux-gnuabi64'
dh_auto_test: error: cd obj-mips64el-linux-gnuabi64 && make -j4 test 
ARGS\+=--verbose ARGS\+=-j4 returned exit code 2

Bug#1000942: [Pkg-rust-maintainers] Bug#1000942: rust-zbus-macros - autopkgtest failure, makes reverse dependencies FTBFS.

[Henry-Nicolas Tourneur]

Package: rust-zbus-macros
Version: 1.0.0-3
Severity: serious
x-debbugs-cc: deb...@nilux.be

The rust-zbus-macros autopkgtest is failing:



error[E0432]: unresolved import `zbus`
  --> 
/tmp/tmp.2o6G5gYnNc/registry/zbus-1.0.0/src/object_server.rs:54:1

   |
54 | #[dbus_interface(name = "org.freedesktop.DBus.Introspectable")]
   | ^^^ 
no `Type` in the root

   |
   = note: this error originates in the attribute macro 
`dbus_interface` (in Nightly builds, run with -Z macro-backtrace for 
more info)


I also did test-builds of the reverse dependencies rust-zbus and 
rust-libslirp (note: I had to manually
build mio-0.6 to test rust-libslirp as it is currently sitting in 
new) and they failed with similar

errors, so this is not just an autopkgtest issue.

I don't know for certain but I assume that just relaxing the 
dependency was
not enough to make it work correctly with the new version of 
rust-proc-macro-crate.


I also tried doing a test rebuild of rust-libslirp (which afaict is 
the only binary crate that depends on


I took a look in the upstream VCS and found a patch for 
rust-proc-macro-crate 1 and tried applying it, unfortunately
it dependeded on a bunch of other upstream commits. Updating to the 
latest stable upstream helped a bit with getting
the patches to apply and I was able to get a succesful build of 
rust-zbus-macros 1.9.2 with

a pile of upstream patches.

Unfortunately when running it's autopkgtests I ran into another 
issue. It seems that rust-zbus has a strictly versioned
dependency on the identical version rust-zbus-macros and rust-zbus 
1.9.2 brings several new dependencies.


dpkg-checkbuilddeps: error: Unmet build dependencies: 
librust-async-io-1+default-dev (>= 1.3.1-~~) 
librust-nb-connect-1+default-dev (>= 1.0.2-~~) 
librust-polling-2+default-dev (>= 2.0.2-~~)


That is pretty much as far as i'm prepared to go. I have pushed my 
attempts to 
https://salsa.debian.org/rust-team/debcargo-conf/-/tree/zbus-1.9.2

if anyone else wants to pick them up.



Hello Peter,

Sorry about that and thank you for the bug report.

I was actually working yesterday on updating zbus/zbus-macros and its 
dependencies to the latest upstream release.
So far, I am counting 7 new crates that will need to go through NEW and 
an additional eight one which is flagged as deprecated upstream 
(nb-connect).
I am trying to assess how to best approach that one (if possible, I am 
busy patching it out based on an upstream commit).





The other option would be to prepare/upload a 
rust-proc-macro-crate-0.1 package and then
revert the dependency in rust-zbus-macros. I may do that if noone 
comes up with a better

solution.


I would suggest we first try to get an updated zbus in the archive, 
which I'll be working on.
If it get stuck for any reason, then the alternative solution you are 
proposing has the benefit of introducing fewer new packages (only one 
vs the 7 new zbus deps mentionned above).


Best regards,

Henry-Nicolas Tourneur

Processed: tagging 1000255, tagging 1000732

[Debian Bug Tracking System]

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

> tags 1000255 + sid bookworm
Bug #1000255 {Done: Louis-Philippe Véronneau } 
[src:python-mpv] mpv: autopkgtest failures
Added tag(s) sid and bookworm.
> tags 1000732 + sid bookworm
Bug #1000732 {Done: Håvard Flaget Aasen } 
[python3-click-threading] python3-click-threading: broken monkeypatching
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#999799: marked as done (cffi breaks cl-plus-ssl autopkgtest on armhf and i386: OMPILE-FILE-ERROR while compiling #)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 08:34:17 +
with message-id 
and subject line Bug#999799: fixed in cffi 1:0.24.1-2
has caused the Debian Bug report #999799,
regarding cffi breaks cl-plus-ssl autopkgtest on armhf and i386: 
OMPILE-FILE-ERROR while compiling #
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.)


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

Source: cffi, cl-plus-ssl
Control: found -1 cffi/1:0.24.1-1
Control: found -1 cl-plus-ssl/20200609.gitff4634a-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
cffi   from testing1:0.24.1-1
cl-plus-sslfrom testing20200609.gitff4634a-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of cffi to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armhf/c/cl-plus-ssl/16722626/log.gz

; file: /usr/share/common-lisp/source/cl-cffi/src/types.lisp
; in: DEFCTYPE :SIZE
; (CFFI:DEFCTYPE :SIZE)
; ; caught ERROR:
;   (during macroexpansion of (DEFCTYPE :SIZE))
;   Error while parsing arguments to DEFMACRO DEFCTYPE:
; too few elements in
;   (:SIZE)
; to satisfy lambda list
;   (NAME BASE-TYPE  DOCUMENTATION):
; between 2 and 3 expected, but got 1
; processing (ERROR (QUOTE SB-INT:COMPILED-PROGRAM-ERROR) ...)
; processing (DEFCTYPE :SSIZE)
; file: /usr/share/common-lisp/source/cl-cffi/src/types.lisp
; in: DEFCTYPE :SSIZE
; (CFFI:DEFCTYPE :SSIZE)
; ; caught ERROR:
;   (during macroexpansion of (DEFCTYPE :SSIZE))
;   Error while parsing arguments to DEFMACRO DEFCTYPE:
; too few elements in
;   (:SSIZE)
; to satisfy lambda list
;   (NAME BASE-TYPE  DOCUMENTATION):
; between 2 and 3 expected, but got 1

; processing (ERROR (QUOTE SB-INT:COMPILED-PROGRAM-ERROR) ...)
; processing (DEFCTYPE :PTRDIFF ...)
; file: /usr/share/common-lisp/source/cl-cffi/src/types.lisp
; in: DEFCTYPE :PTRDIFF
; (CFFI:DEFCTYPE :PTRDIFF :SSIZE)
; ; caught ERROR:
;   (during macroexpansion of (DEFCTYPE :PTRDIFF ...))
;   Unknown CFFI type :SSIZE

; processing (ERROR (QUOTE SB-INT:COMPILED-PROGRAM-ERROR) ...)
; processing (DEFCTYPE :OFFSET ...)

; wrote 
/tmp/autopkgtest-lxc.w4ep9ku_/downtmp/autopkgtest_tmp/usr/share/common-lisp/source/cl-cffi/src/types-tmpBODYQO2B.fasl

; compilation finished in 0:00:00.460
Unhandled UIOP/LISP-BUILD:COMPILE-FILE-ERROR:
  COMPILE-FILE-ERROR while compiling #

Backtrace for: #
0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK 
# # :QUIT T)
1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* 
#)

2: (INVOKE-DEBUGGER #)
3: (ERROR UIOP/LISP-BUILD:COMPILE-FILE-ERROR :CONTEXT-FORMAT 
"~/asdf-action::format-action/" :CONTEXT-ARGUMENTS 
((# . #"cffi" "src" "types">)))
4: (UIOP/LISP-BUILD:CHECK-LISP-COMPILE-RESULTS NIL T T 
"~/asdf-action::format-action/" ((# . 
#)))
5: ((SB-PCL::EMF ASDF/ACTION:PERFORM) # #argument> # 
#)

6: ((LAMBDA NIL :IN ASDF/ACTION:CALL-WHILE-VISITING-ACTION))
7: ((:METHOD ASDF/ACTION:PERFORM :AROUND (ASDF/LISP-ACTION:COMPILE-OP 
ASDF/LISP-ACTION:CL-SOURCE-FILE)) # 
#) [fast-method]
8: ((:METHOD ASDF/ACTION:PERFORM-WITH-RESTARTS :AROUND (T T)) 
# #"src" "types">) [fast-method]
9: ((:METHOD ASDF/PLAN:PERFORM-PLAN (T)) #{4FD098D9}>) [fast-method]

10: ((FLET SB-C::WITH-IT :IN SB-C::%WITH-COMPILATION-UNIT))
11: ((:METHOD ASDF/PLAN:PERFORM-PLAN :AROUND (T)) 
#) [fast-method]
12: ((:METHOD ASDF/OPERATE:OPERATE (ASDF/OPERATION:OPERATION 
ASDF/COMPONENT:COMPONENT)) # 
# :PLAN-CLASS NIL :PLAN-OPTIONS NIL) 
[fast-method]
13: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) # #argument> # #)

14: ((LAMBDA NIL :IN ASDF/OPERATE:OPERATE))
15: ((:METHOD ASDF/OPERATE:OPERATE :AROUND (T T)) 
# #) 
[fast-method]
16: ((SB-PCL::EMF ASDF/OPERATE:OPERATE) 

Bug#998486: marked as done (ruby-puma-worker-killer: FTBFS: ERROR: Test "ruby3.0" failed.)

[Debian Bug Tracking System]

Your message dated Wed, 01 Dec 2021 08:37:29 +
with message-id 
and subject line Bug#998486: fixed in ruby-puma-worker-killer 0.3.1-3
has caused the Debian Bug report #998486,
regarding ruby-puma-worker-killer: FTBFS: ERROR: Test "ruby3.0" failed.
to be marked as done.

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

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


-- 
998486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-puma-worker-killer
Version: 0.3.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.0  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-puma-worker-killer/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -e gem\ \"puma_worker_killer\"
> 
> ┌──┐
> │ Run tests for ruby3.0 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-puma-worker-killer/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.0 -w -I"test" 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader.rb 
> "test/puma_worker_killer_test.rb" "test/test_helper.rb" -v
> Loaded suite 
> /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/rake_test_loader
> Started
> PumaWorkerKillerTest: 
>   test_kills_large_app:   
> /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:496:in
>  `materialize': Could not find puma-5.5.2 in any of the sources 
> (Bundler::GemNotFound)
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/definition.rb:234:in
>  `specs_for'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/runtime.rb:18:in
>  `setup'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler.rb:149:in 
> `setup'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/setup.rb:20:in
>  `block in '
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/ui/shell.rb:136:in
>  `with_level'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/ui/shell.rb:88:in
>  `silence'
>   from 
> /usr/share/rubygems-integration/all/gems/bundler-2.2.27/lib/bundler/setup.rb:20:in
>  `'
>   from 
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
>   from 
> /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require'
> Timeout waiting for "booted" to find a match using (?-mix:booted) in 
> ''
> E
> ===
> Error: test_kills_large_app(PumaWorkerKillerTest):
>   WaitForIt::WaitForItTimeoutError: Running command: 'bundle exec puma 
> /<>/test/fixtures/big.ru -t 1:1 -w 2 --preload --debug -p 0', 
> waiting for 'booted' did not occur within 5 seconds:
> /usr/share/rubygems-integration/all/gems/wait_for_it-0.2.1/lib/wait_for_it.rb:144:in
>  `wait!'
> /usr/share/rubygems-integration/all/gems/wait_for_it-0.2.1/lib/wait_for_it.rb:92:in
>  `initialize'
> /<>/test/puma_worker_killer_test.rb:32:in `new'
> /<>/test/puma_worker_killer_test.rb:32:in `test_kills_large_app'
>  29: command  = "bundle exec puma #{file} -t 1:1 -w 2 --preload 
> --debug -p #{port}"
>  30: options  = { wait_for: 'booted', timeout: 5, env: 

Processed: 999531: forwarded upstream

[Debian Bug Tracking System]

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

> forwarded 999531 https://gitlab.com/ase/ase/-/issues/1010
Bug #999531 [src:python-ase] python-ase: FTBFS with matplotlib 3.5 (in 
experimental): dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.9 returned exit code 13
Set Bug forwarded-to-address to 'https://gitlab.com/ase/ase/-/issues/1010'.
> thanks
Stopping processing here.

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

Processed: 994785: pending

[Debian Bug Tracking System]

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

> owner 994785 !
Bug #994785 [src:python-ase] python-ase: autopkgtest regression on 
arm64/ppc64el: TestSlab.test_vibration_on_surface
Owner recorded as Andrius Merkys .
> tags 994785 + upstream fixed-upstream
Bug #994785 [src:python-ase] python-ase: autopkgtest regression on 
arm64/ppc64el: TestSlab.test_vibration_on_surface
Added tag(s) upstream and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1000661: Missing b-dep on libbase64-ocaml-dev

[Andy Li]

Hi,

On Fri, Nov 26, 2021 at 11:45 PM Julien Puydt  wrote:
> I was checking whether a recent dune would break any package, and my
> test failed because Base64 was an unbound module -- it's a missing
> build-dep on libbase64-ocaml-dev, so it should be pretty
> straightforward to fix.

I've uploaded 1:4.2.4-1, which fixed the build problem regarding base64.

Best regards,
Andy

Bug#994785: marked as pending in python-ase

[Andrius Merkys]

Control: tag -1 pending

Hello,

Bug #994785 in python-ase 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/debichem-team/python-ase/-/commit/f4d1f4a0d5c75cc3a70378eea1e5131c0571962a


Add upstream patch to fix failing tests on arm64/ppc64el (Closes: #994785)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/994785

Processed: Bug#994785 marked as pending in python-ase

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #994785 [src:python-ase] python-ase: autopkgtest regression on 
arm64/ppc64el: TestSlab.test_vibration_on_surface
Added tag(s) pending.

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