Bug#990403: marked as done (depends on deprecated qhull library)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 07:18:32 +
with message-id 
and subject line Bug#990403: fixed in gdal 3.4.1~rc1+dfsg-1~exp1
has caused the Debian Bug report #990403,
regarding depends on deprecated qhull library
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.)


-- 
990403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gdal
Version: 3.2.2+dfsg-2
Severity: normal
X-Debbugs-Cc: roehl...@debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

your package builds and links against the non-reentrant version of
Qhull, which has been deprecated by Qhull upstream and is likely to
disappear soon.

This bug is not release-critical for Bullseye, but you can expect the
severity to raise eventually when Qhull stops shipping with the
non-reentrant library.

You can verify that your binary package links against the correct
library if it no longer depends on libqhull8.0 but libqhull-r8.0
instead.

Cheers
Timo

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmDZlQoACgkQ+C8H+466
LVmb8gwAm3Gfr3GELxhdaeOYnX8hqUEjwToNONG3LiBz2iQWb5LFcHRe/OziA5mE
qdHOMk7RkDaptpwTPd8MbnOsWQMAKxMMaF3lQT5KCXvwz2190Fy3MpkBA33KjUMb
YPgA9Uv67SVenuyzlVclZIIN3P3B0pViS8zC/r6+S8YWUcyFpwJo1UXDhH0HVjZX
gzRNE2+dU7JRLq4/G9R/pnEXsJp1/7iUE+UWwmqPHcywKTa8MByOpcfdhL0IAIZC
8A5WxNymBwOSbASs3+uK+VG5yhRmi81GgnE6rsfrjRYcNL8o/PYK440YSJNkX+5v
8OtfhtIY18O0tmqWWFE8Zleqp1xzfUeDbmXJ2315wpsZbcTI/5GpKZbj8UPKrqze
yjgLRbe8ANqkxc24y1fv7Yw5vT3gpZgXRMvjMWKiBD7CeOmA9ywqvJdacrVW7sWF
sNK9sQso5ImMTRi4ztVq6YnAAEF0Fza8phDqB7xvUdBDH1j/JzkgVaIH+4h3oXMn
AU856L5+
=6rPq
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: gdal
Source-Version: 3.4.1~rc1+dfsg-1~exp1
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated gdal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Dec 2021 06:00:43 +0100
Source: gdal
Architecture: source
Version: 3.4.1~rc1+dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 990403 1000119
Changes:
 gdal (3.4.1~rc1+dfsg-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate.
 (closes: #990403)
   * Refresh patches.
   * Switch to pcre2.
 (closes: #1000119)
Checksums-Sha1:
 44e25e1de24edac0476aecab2a931e99869058a3 3317 gdal_3.4.1~rc1+dfsg-1~exp1.dsc
 f598a76b0d4cafac3a607ce12686580091812c60 9428256 
gdal_3.4.1~rc1+dfsg.orig.tar.xz
 5c7ead160a16bd23cf77971230e12190fa07d719 262516 
gdal_3.4.1~rc1+dfsg-1~exp1.debian.tar.xz
 bb2e5292ecf61d7f41566d2c62fd9e608e45e279 17410 
gdal_3.4.1~rc1+dfsg-1~exp1_amd64.buildinfo
Checksums-Sha256:
 026af0440dbc4fe82d569ed62d143605e1f64d70eae8ddd9503433b3893d6db3 3317 
gdal_3.4.1~rc1+dfsg-1~exp1.dsc
 88d74d2699b2db034aea11aa29b27c633bdd0bd682a1cf8a98c7dfe7c68c2ff8 9428256 
gdal_3.4.1~rc1+dfsg.orig.tar.xz
 064830259b6d7f3af52774e970e2e1a297bcff82a4ba190774cfb02bceb9c587 262516 
gdal_3.4.1~rc1+dfsg-1~exp1.debian.tar.xz
 c42d674160906ce1de17d7eacc272bcdf2081930ee51f39826189b4237a98905 17410 
gdal_3.4.1~rc1+dfsg-1~exp1_amd64.buildinfo
Files:
 e6fa2acc1db5686dfe95a03d7deb8886 3317 science optional 
gdal_3.4.1~rc1+dfsg-1~exp1.dsc
 d3b3228ab319ee0612fac159b626d46e 9428256 science optional 
gdal_3.4.1~rc1+dfsg.orig.tar.xz
 5ab2aeb0963c21303dff25919220e54b 262516 science optional 
gdal_3.4.1~rc1+dfsg-1~exp1.debian.tar.xz
 39c1fbaae7eedd98e6a702de8de86234 17410 science optional 
gdal_3.4.1~rc1+dfsg-1~exp1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmHKtk0ACgkQZ1DxCuiN
SvH4rxAArn621IP+G6qUpTNoawcoPyKhZ7HHYHjki5O9eFDltvZjbqjt00T81cQX
4OZUQISQTrDxkhdQop2WTtJPhJg3+2zZGphiKUU7z8XUYuJQOqcFhZf3o2HmZfD3
QcJlBSrpqp/GilszsXX1IgOYIYUQGQ448zSI0LoA9p9dZ0ANyFSA5Vf2o00wW6sF
etqB08kx3oYIiTb3h86hyUS/RQ8elcLzWgr5/ztJDnmJjUZqtHwQnJBDuuau+Kgd

Bug#1000119: marked as done (gdal: depends on obsolete pcre3 library)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 07:18:32 +
with message-id 
and subject line Bug#1000119: fixed in gdal 3.4.1~rc1+dfsg-1~exp1
has caused the Debian Bug report #1000119,
regarding gdal: depends on obsolete pcre3 library
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.)


-- 
1000119: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000119
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdal
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: gdal
Source-Version: 3.4.1~rc1+dfsg-1~exp1
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
gdal, 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.
Bas Couwenberg  (supplier of updated gdal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Dec 2021 06:00:43 +0100
Source: gdal
Architecture: source
Version: 3.4.1~rc1+dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 990403 1000119
Changes:
 gdal (3.4.1~rc1+dfsg-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate.
 (closes: #990403)
   * Refresh patches.
   * Switch to pcre2.
 (closes: #1000119)
Checksums-Sha1:
 44e25e1de24edac0476aecab2a931e99869058a3 3317 gdal_3.4.1~rc1+dfsg-1~exp1.dsc
 f598a76b0d4cafac3a607ce12686580091812c60 9428256 
gdal_3.4.1~rc1+dfsg.orig.tar.xz
 5c7ead160a16bd23cf77971230e12190fa07d719 262516 
gdal_3.4.1~rc1+dfsg-1~exp1.debian.tar.xz
 bb2e5292ecf61d7f41566d2c62fd9e608e45e279 17410 
gdal_3.4.1~rc1+dfsg-1~exp1_amd64.buildinfo
Checksums-Sha256:
 026af0440dbc4fe82d569ed62d143605e1f64d70eae8ddd9503433b3893d6db3 3317 
gdal_3.4.1~rc1+dfsg-1~exp1.dsc
 88d74d2699b2db034aea11aa29b27c633bdd0bd682a1cf8a98c7dfe7c68c2ff8 9428256 
gdal_3.4.1~rc1+dfsg.orig.tar.xz
 064830259b6d7f3af52774e970e2e1a297bcff82a4ba190774cfb02bceb9c587 262516 
gdal_3.4.1~rc1+dfsg-1~exp1.debian.tar.xz
 c42d674160906ce1de17d7eacc272bcdf2081930ee51f39826189b4237a98905 17410 
gdal_3.4.1~rc1+dfsg-1~exp1_amd64.buildinfo
Files:
 e6fa2acc1db5686dfe95a03d7deb8886 3317 science optional 
gdal_3.4.1~rc1+dfsg-1~exp1.dsc
 d3b3228ab319ee0612fac159b626d46e 9428256 science optional 
gdal_3.4.1~rc1+dfsg.orig.tar.xz
 5ab2aeb0963c21303dff25919220e54b 262516 science optional 
gdal_3.4.1~rc1+dfsg-1~exp1.debian.tar.xz
 39c1fbaae7eedd98e6a702de8de86234 17410 science optional 
gdal_3.4.1~rc1+dfsg-1~exp1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmHKtk0ACgkQZ1DxCuiN
SvH4rxAArn621IP+G6qUpTNoawcoPyKhZ7HHYHjki5O9eFDltvZjbqjt00T81cQX
4OZUQISQTrDxkhdQop2WTtJPhJg3+2zZGphiKUU7z8XUYuJQOqcFhZf3o2HmZfD3
QcJlBSrpqp/GilszsXX1IgOYIYUQGQ448zSI0LoA9p9dZ0ANyFSA5Vf2o00wW6sF
etqB08kx3oYIiTb3h86hyUS/RQ8elcLzWgr5/ztJDnmJjUZqtHwQnJBDuuau+Kgd
u3ND5V712rQfO62NAUMdHmbF1+f8RGG/Jl2YmkPS8/EqT/A7iakpV9xZgCPLoRqC
M5G7vFH+O9jez0IYRjScDK+wGxZt9aS1rRf8ggxv0XPkfiyymi/zcD8Q2/ZuXslC
V9YjWblW9Sc8IlelC4cdmFkJ3E0sHauADLSsE0WrV0BovbcxwVSlDeGg71B6VMBj
YFld4by7IWMzfTx4ZkhSH5jmPf2dajR5am8EpPiSjGAkMbKvyPXUnGTzghhxyqda

Bug#1002654: marked as done (reportbug: Please report Desktop Environment which a user has logged in)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 01:47:43 -0500
with message-id 

and subject line Re: Bug#1002654: reportbug: Please report Desktop Environment 
which a user has logged in
has caused the Debian Bug report #1002654,
regarding reportbug: Please report Desktop Environment which a user has logged 
in
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.)


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

Dear Maintainers,

reportbug(1) supplies system information when generating a bug template.

> -- System Information:
> Debian Release: buster/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

I believe it would be desirable to have a line about desktop environment
used by a reporter. The tool can identify DE via the XDG_CURRENT_DESKTOP
environment variable mentioned in Desktop Entry Specification[1].
pam_systemd(8) sets the XDG_SESSION_TYPE, the XDG_SESSION_CLASS, and the
XDG_SESSION_DESKTOP environment variables; they can be taken into
account as well. The legacy and non-standardized DESKTOP_SESSION
environment variable could also be read.

 [1]: 
https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html

Please consider to include this information to bug reports to help
maintainers investigate issues in GUI applications. It could looks like

> DE: MATE

or

> DE: XFCE



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
> I can judge from my point of view only. There are some bugs in the
> telegram-desktop package where this information would be useful.

i think that you'd be better served by adding a bug-script to
telegram-desktop to collect the information you need to properly debug
issues with that package.

While there's could potentially be some value in adding the DE
information on all bugs, the bar needed is substantially higher than
what demonstrated here Given there is already support in reportbug to
support telegram-desktop needs, i'm going to close this ticket; we can
re-evaluate at a later time if further interest is shown.

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi--- End Message ---


Bug#996479: marked as done (httpie: Version 2.6.0 available)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 06:03:32 +
with message-id 
and subject line Bug#996479: fixed in httpie 2.6.0-1
has caused the Debian Bug report #996479,
regarding httpie: Version 2.6.0 available
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.)


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

Package: httpie
Severity: normal

Hello dear maintainers,

I've just released HTTPie 2.6.0, it brings interesting changes and bug fixes:

- Added support for formatting & coloring of JSON bodies preceded by non-JSON 
data (e.g., an XXSI prefix).
- Added charset auto-detection when Content-Type doesn’t include it.
- Added --response-charset to allow overriding the response encoding for 
terminal display purposes.
- Added --response-mime to allow overriding the response mime type for coloring 
and formatting for the terminal.
- Added the ability to silence warnings through using -q or --quiet twice (e.g. 
-qq).
- Added installed plugin list to --debug output.
- Fixed duplicate keys preservation in JSON data.

I guess the bug report about upgrading HTTPie 2.5.0 should be closed then 
(#993937)?

Thanks in advance.

Note: I changed the severity from wishlist to normal as HTTPie is obsolete on 
every Debian-derived distributions (mostly because it is too on Debian itself).
  I kindly hope to improve the situation, maybe is there another way to 
make the process smoother, and painless, for everyone?

--
Mickaël Schoentgen
https://www.tiger-222.fr

--- End Message ---
--- Begin Message ---
Source: httpie
Source-Version: 2.6.0-1
Done: Bartosz Fenski 

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

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

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

Debian distribution maintenance software
pp.
Bartosz Fenski  (supplier of updated httpie package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 28 Dec 2021 10:51:48 +0100
Source: httpie
Binary: httpie
Architecture: source all
Version: 2.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Bartosz Fenski 
Changed-By: Bartosz Fenski 
Description:
 httpie - CLI, cURL-like tool for humans
Closes: 993937 996479
Changes:
 httpie (2.6.0-1) unstable; urgency=medium
 .
   * The Akamai Technologies paid volunteer days release.
   * New upstream version. (Closes: #993937, #996479)
 - various minor packaging updates due to upstream changes
Checksums-Sha1:
 c4c89fc88de7f28fcf71ca39f433ce4d78f50fa8 1845 httpie_2.6.0-1.dsc
 8ef507cf8eed8add584a8cfd856d78434f6f2b74 1133495 httpie_2.6.0.orig.tar.gz
 96c8359b0c5e014cdc38a25bfce0dc3831f6b96c 7456 httpie_2.6.0-1.debian.tar.xz
 fe3b0245c038c2ecc8717002b5bd38933eb44f70 58660 httpie_2.6.0-1_all.deb
 004200d2c5040e766f9279d64efe413d614adba8 6996 httpie_2.6.0-1_amd64.buildinfo
Checksums-Sha256:
 4975eb5cb474ec344da957ae4769eda73565499dbd7b27ad33680c06486af35b 1845 
httpie_2.6.0-1.dsc
 3bcd9a8cb2b11299da12d3af36c095c6d4b665e41c395898a07f1ae4d99fc14a 1133495 
httpie_2.6.0.orig.tar.gz
 8752f69357a437520029f417a9dfe0201ced690904fb4fb1678469d1f7ba4925 7456 
httpie_2.6.0-1.debian.tar.xz
 263b776663915b814ec60c56d0ade3655f4b58fa779953b7c667b6059fb7c1d4 58660 
httpie_2.6.0-1_all.deb
 190f1147a3e9bdbe70669b726fde9b182472ffc0c7b8c54844a23eaac6a2ddf7 6996 
httpie_2.6.0-1_amd64.buildinfo
Files:
 24c08fc75bc4a5e276e21d488c8b0ef9 1845 web optional httpie_2.6.0-1.dsc
 a4be402f5992aa3b61ad60ab70581f4c 1133495 web optional httpie_2.6.0.orig.tar.gz
 733cd4d73774219fa381f886912ed084 7456 web optional httpie_2.6.0-1.debian.tar.xz
 c44d15b8a3c8e2448be545c9fb5384d5 58660 web optional httpie_2.6.0-1_all.deb
 85e1a189391118d3fd21f9c309f0bae4 6996 web optional 
httpie_2.6.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEK+x51vtJ+yJ4cpAbsNnUqDzTu8EFAmHKo8ARHGZlbmlvQGRl
Ymlhbi5vcmcACgkQsNnUqDzTu8GcGg//ejxzfLIkmK6ySuwFFyI6ZE44o9UpwbWg
xkBia/4oQspwsnOLZVkCd9ng2RJ1qSFw8vPmjf8C38PFpIxvJfqdJTB5VdNgsrQ2
r9uh5WKzpzpcnsqSe0XN9i5prEKSWUA/CCFo6rsOmuw4mTuJe0wP9R/9/AVBkrzT
sR8+AnvggnuNk+qYaQ1sRr9O4vRVuS8U74TcCTQ20+RVxQ9d3GRTV88fbcA4zTk4

Bug#993937: marked as done (httpie: Version 2.5.0 available)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 06:03:32 +
with message-id 
and subject line Bug#993937: fixed in httpie 2.6.0-1
has caused the Debian Bug report #993937,
regarding httpie: Version 2.5.0 available
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.)


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

Package: httpie
Severity: wishlist
X-Debbugs-Cc: Bartosz Fenski 

Dear Maintainer,

HTTPie 2.5.0 is now available, it brings those changes:

  - Added --raw to allow specifying the raw request body without extra 
processing as an alternative to stdin.

  - Added support for XML formatting.
  - Added internal support for file-like object responses to improve 
adapter plugin support.

  - Fixed --continue --download with a single byte to be downloaded left.
  - Fixed --verbose HTTP 307 redirects with streamed request body.
  - Fixed handling of session files with Cookie: followed by other headers.


Here are changes at the packaging level, from what I can see in 
https://sources.debian.org/src/httpie/2.4.0-1/debian.


* control:

  - Build-Depends: remove "python3-docutils"
  - Build-Depends: add "python3-defusedxml"
  - Build-Depends: add "python3-socks"
  - Build-Depends: add "python3-requests-toolbelt"
  - Build-Depends: add "python3-responses" (it is only used for 
testing, not sure it should be there though)

  - Homepage: replace "https://httpie.org; with "https://httpie.io;

* copyright:

  - replace "https://httpie.org; with "https://httpie.io;
  - replace "2019" with "2021"

* docs:

  - replace "REAMDE.rst" with "REAMDE.md"

* watch:

  - replace "https://github.com/jkbr/httpie/tags; with 
"https://github.com/httpie/httpie/tags;



Cheers,

--
Mickaël Schoentgen
http://www.tiger-222.fr
--- End Message ---
--- Begin Message ---
Source: httpie
Source-Version: 2.6.0-1
Done: Bartosz Fenski 

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

Debian distribution maintenance software
pp.
Bartosz Fenski  (supplier of updated httpie package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 28 Dec 2021 10:51:48 +0100
Source: httpie
Binary: httpie
Architecture: source all
Version: 2.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Bartosz Fenski 
Changed-By: Bartosz Fenski 
Description:
 httpie - CLI, cURL-like tool for humans
Closes: 993937 996479
Changes:
 httpie (2.6.0-1) unstable; urgency=medium
 .
   * The Akamai Technologies paid volunteer days release.
   * New upstream version. (Closes: #993937, #996479)
 - various minor packaging updates due to upstream changes
Checksums-Sha1:
 c4c89fc88de7f28fcf71ca39f433ce4d78f50fa8 1845 httpie_2.6.0-1.dsc
 8ef507cf8eed8add584a8cfd856d78434f6f2b74 1133495 httpie_2.6.0.orig.tar.gz
 96c8359b0c5e014cdc38a25bfce0dc3831f6b96c 7456 httpie_2.6.0-1.debian.tar.xz
 fe3b0245c038c2ecc8717002b5bd38933eb44f70 58660 httpie_2.6.0-1_all.deb
 004200d2c5040e766f9279d64efe413d614adba8 6996 httpie_2.6.0-1_amd64.buildinfo
Checksums-Sha256:
 4975eb5cb474ec344da957ae4769eda73565499dbd7b27ad33680c06486af35b 1845 
httpie_2.6.0-1.dsc
 3bcd9a8cb2b11299da12d3af36c095c6d4b665e41c395898a07f1ae4d99fc14a 1133495 
httpie_2.6.0.orig.tar.gz
 8752f69357a437520029f417a9dfe0201ced690904fb4fb1678469d1f7ba4925 7456 
httpie_2.6.0-1.debian.tar.xz
 263b776663915b814ec60c56d0ade3655f4b58fa779953b7c667b6059fb7c1d4 58660 
httpie_2.6.0-1_all.deb
 190f1147a3e9bdbe70669b726fde9b182472ffc0c7b8c54844a23eaac6a2ddf7 6996 
httpie_2.6.0-1_amd64.buildinfo
Files:
 24c08fc75bc4a5e276e21d488c8b0ef9 1845 web optional httpie_2.6.0-1.dsc
 a4be402f5992aa3b61ad60ab70581f4c 1133495 web optional httpie_2.6.0.orig.tar.gz
 733cd4d73774219fa381f886912ed084 7456 web optional httpie_2.6.0-1.debian.tar.xz
 c44d15b8a3c8e2448be545c9fb5384d5 58660 web optional httpie_2.6.0-1_all.deb
 85e1a189391118d3fd21f9c309f0bae4 6996 web optional 
httpie_2.6.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEK+x51vtJ+yJ4cpAbsNnUqDzTu8EFAmHKo8ARHGZlbmlvQGRl

Bug#1002542: marked as done (python-requests-cache breaks howdoi autopkgtest: 'requests_cache' has no attribute 'install_cache')

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 06:03:39 +
with message-id 
and subject line Bug#1002585: fixed in python-requests-cache 0.8.1-3
has caused the Debian Bug report #1002585,
regarding python-requests-cache breaks howdoi autopkgtest: 'requests_cache' has 
no attribute 'install_cache'
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.)


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

Source: python-requests-cache, howdoi
Control: found -1 python-requests-cache/0.8.1-2
Control: found -1 howdoi/1.1.9-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 python-requests-cache the autopkgtest of howdoi 
fails in testing when that autopkgtest is run with the binary packages 
of python-requests-cache from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python-requests-cache  from testing0.8.1-2
howdoi from testing1.1.9-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 
python-requests-cache 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=python-requests-cache

https://ci.debian.net/data/autopkgtest/testing/amd64/h/howdoi/17811284/log.gz

+ HOME=/tmp/autopkgtest-lxc.ovu9zioh/downtmp/autopkgtest_tmp
+ python3 -c import howdoi
+ howdoi --help
No module named 'url_normalize'
usage: howdoi [-h] [-p POS] [-a] [-l] [-c] [-n NUM_ANSWERS] [-C] [-v]
  [QUERY ...]

instant coding answers via the command line

positional arguments:
  QUERY the question to answer

optional arguments:
  -h, --helpshow this help message and exit
  -p POS, --pos POS select answer in specified position (default: 1)
  -a, --all display the full text of the answer
  -l, --linkdisplay only the answer link
  -c, --color   enable colorized output
  -n NUM_ANSWERS, --num-answers NUM_ANSWERS
number of answers to return
  -C, --clear-cache clear the cache
  -v, --version displays the current version of howdoi
+ howdoi --version
No module named 'url_normalize'
1.1.9
+ howdoi python numpy array
No module named 'url_normalize'
Traceback (most recent call last):
  File "/usr/bin/howdoi", line 9, in 
load_entry_point('howdoi==1.1.9', 'console_scripts', 'howdoi')()
  File "/usr/lib/python3/dist-packages/howdoi/howdoi.py", line 259, in 
command_line_runner

_enable_cache()
  File "/usr/lib/python3/dist-packages/howdoi/howdoi.py", line 205, in 
_enable_cache

requests_cache.install_cache(CACHE_FILE)
AttributeError: module 'requests_cache' has no attribute 'install_cache'
autopkgtest [14:10:28]: test tools



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-requests-cache
Source-Version: 0.8.1-3
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-requests-cache 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 28 Dec 2021 00:52:11 -0500
Source: python-requests-cache
Architecture: source
Version: 0.8.1-3
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 1002585
Changes:
 python-requests-cache (0.8.1-3) unstable; urgency=medium
 .
   * debian/control
 - add 

Bug#1002585: marked as done (python-requests-cache breaks rows autopkgtest: 'requests_cache' has no attribute 'install_cache')

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 06:03:39 +
with message-id 
and subject line Bug#1002585: fixed in python-requests-cache 0.8.1-3
has caused the Debian Bug report #1002585,
regarding python-requests-cache breaks rows autopkgtest: 'requests_cache' has 
no attribute 'install_cache'
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.)


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

Source: python-requests-cache, rows
Control: found -1 python-requests-cache/0.8.1-2
Control: found -1 rows/0.4.1-4
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 python-requests-cache the autopkgtest of rows 
fails in testing when that autopkgtest is run with the binary packages 
of python-requests-cache from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python-requests-cache  from testing0.8.1-2
rows   from testing0.4.1-4
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 
python-requests-cache 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=python-requests-cache

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rows/17837757/log.gz

#1  rows print debian/tests/table.csv
--
[FAILED #1, line 1] rows print debian/tests/table.csv
@@ -1,7 +1,17 @@
-+---+---+---+
-| a | b | c |
-+---+---+---+
-| 1 | 2 | 3 |
-| 4 | 5 | 6 |
-+---+---+---+
-
+No module named 'url_normalize'
+Traceback (most recent call last):
+  File "/usr/bin/rows", line 33, in 
+sys.exit(load_entry_point('rows==0.4.1', 'console_scripts', 'rows')())
+  File "/usr/lib/python3/dist-packages/click/core.py", line 1126, in 
__call__

+return self.main(*args, **kwargs)
+  File "/usr/lib/python3/dist-packages/click/core.py", line 1051, in main
+rv = self.invoke(ctx)
+  File "/usr/lib/python3/dist-packages/click/core.py", line 1654, in invoke
+super().invoke(ctx)
+  File "/usr/lib/python3/dist-packages/click/core.py", line 1393, in invoke
+return ctx.invoke(self.callback, **ctx.params)
+  File "/usr/lib/python3/dist-packages/click/core.py", line 752, in invoke
+return __callback(*args, **kwargs)
+  File "/usr/lib/python3/dist-packages/rows/cli.py", line 160, in cli
+requests_cache.install_cache(str(http_cache_path))
+AttributeError: module 'requests_cache' has no attribute 'install_cache'
--
#2  echo $?
#3  rows query "SELECT * FROM table1 WHERE a = 1" debian/tests/table.csv
--
[FAILED #3, line 11] rows query "SELECT * FROM table1 WHERE a = 1" 
debian/tests/table.csv

@@ -1,6 +1,17 @@
-+---+---+---+
-| a | b | c |
-+---+---+---+
-| 1 | 2 | 3 |
-+---+---+---+
-
+No module named 'url_normalize'
+Traceback (most recent call last):
+  File "/usr/bin/rows", line 33, in 
+sys.exit(load_entry_point('rows==0.4.1', 'console_scripts', 'rows')())
+  File "/usr/lib/python3/dist-packages/click/core.py", line 1126, in 
__call__

+return self.main(*args, **kwargs)
+  File "/usr/lib/python3/dist-packages/click/core.py", line 1051, in main
+rv = self.invoke(ctx)
+  File "/usr/lib/python3/dist-packages/click/core.py", line 1654, in invoke
+super().invoke(ctx)
+  File "/usr/lib/python3/dist-packages/click/core.py", line 1393, in invoke
+return ctx.invoke(self.callback, **ctx.params)
+  File "/usr/lib/python3/dist-packages/click/core.py", line 752, in invoke
+return __callback(*args, **kwargs)
+  File "/usr/lib/python3/dist-packages/rows/cli.py", line 160, in cli
+requests_cache.install_cache(str(http_cache_path))
+AttributeError: module 'requests_cache' has no attribute 'install_cache'
--
#4  echo $?

FAIL: 2 of 4 tests failed
autopkgtest [19:08:28]: test smoke-test



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

Bug#1002277: marked as done (tiles-request: FTBFS: [ERROR] Failed to execute goal on project tiles-request-servlet: Could not resolve dependencies for project org.apache.tiles:tiles-request-servlet:ja

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 05:03:50 +
with message-id 
and subject line Bug#1002277: fixed in tiles-request 1.0.7-2
has caused the Debian Bug report #1002277,
regarding tiles-request: FTBFS: [ERROR] Failed to execute goal on project 
tiles-request-servlet: Could not resolve dependencies for project 
org.apache.tiles:tiles-request-servlet:jar:1.0.7: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
javax.servlet:javax.servlet-api:jar:3.1 has not been downloaded from it before. 
-> [Help 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibtiles-request-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Tiles Request Framework
> [pom]
> [INFO] Tiles request - API
> [jar]
> [INFO] Tiles request - Servlet support
> [jar]
> [INFO] Tiles Request - Wildcard file loading in Servlets  
> [jar]
> [INFO] Tiles - Portlet support
> [jar]
> [INFO] Tiles Request - JSP support
> [jar]
> [INFO] Tiles Request - Freemarker support 
> [jar]
> [INFO] Tiles Request - Velocity support   
> [jar]
> [INFO] Tiles request - Mustache support   
> [jar]
> [INFO] 
> [INFO] ---< org.apache.tiles:tiles-request 
> >---
> [INFO] Building Tiles Request Framework 1.0.7 
> [1/9]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ 
> tiles-request ---
> [WARNING] Ignoring project type pom - supportedProjectTypes = [jar, bundle]
> [INFO] 
> [INFO] -< org.apache.tiles:tiles-request-api 
> >-
> [INFO] Building Tiles request - API 1.0.7 
> [2/9]
> [INFO] [ jar 
> ]-
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> tiles-request-api ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ 
> tiles-request-api ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 51 source files to 
> /<>/tiles-request-api/target/classes
> Use of target 1.6 is no longer supported, switching to 7
> Use of source 1.6 is no longer supported, switching to 7
> [INFO] 
> /<>/tiles-request-api/src/main/java/org/apache/tiles/request/reflect/ClassUtil.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /<>/tiles-request-api/src/main/java/org/apache/tiles/request/reflect/ClassUtil.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ 
> tiles-request-api ---
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ tiles-request-api ---
> [INFO] Not copying test resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:testCompile 

Bug#1000585: marked as done (php-doctrine-common: Failed tests on PHP 8.1: expected output order change)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 04:18:28 +
with message-id 
and subject line Bug#1000585: fixed in php-doctrine-common 3.2.1-1
has caused the Debian Bug report #1000585,
regarding php-doctrine-common: Failed tests on PHP 8.1: expected output order 
change
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.)


-- 
1000585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-doctrine-common
Version: 3.2.0-1
Severity: normal
Tags: patch
Control: block 976811 by -1

The tests fail on PHP 8.1 because the output is displayed in a different
order. The simple attached patch fixes the issue, but needs to be
applied in sync when PHP 8.1 becomes the default in Debian.

Regards

David
From 38efa9220b7290aeddbfdfa6ab4e7a4f7423b5d3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?David=20Pr=C3=A9vot?= 
Date: Thu, 25 Nov 2021 08:17:18 -0400
Subject: [PATCH] Reorder expected result for PHP 8.1

---
 tests/Doctrine/Tests/Common/Util/DebugTest.php | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/tests/Doctrine/Tests/Common/Util/DebugTest.php b/tests/Doctrine/Tests/Common/Util/DebugTest.php
index 306810c9..191e8120 100644
--- a/tests/Doctrine/Tests/Common/Util/DebugTest.php
+++ b/tests/Doctrine/Tests/Common/Util/DebugTest.php
@@ -148,12 +148,12 @@ class DebugTest extends DoctrineTestCase
 'different-attributes' => [
 new TestAsset\ChildClass(),
 [
-'childPublicAttribute' => 4,
-'childProtectedAttribute:protected' => 5,
-'childPrivateAttribute:Doctrine\Tests\Common\Util\TestAsset\ChildClass:private' => 6,
 'parentPublicAttribute' => 1,
 'parentProtectedAttribute:protected' => 2,
 'parentPrivateAttribute:Doctrine\Tests\Common\Util\TestAsset\ParentClass:private' => 3,
+'childPublicAttribute' => 4,
+'childProtectedAttribute:protected' => 5,
+'childPrivateAttribute:Doctrine\Tests\Common\Util\TestAsset\ChildClass:private' => 6,
 ],
 ],
 'same-attributes' => [
@@ -161,8 +161,8 @@ class DebugTest extends DoctrineTestCase
 [
 'parentPublicAttribute' => 4,
 'parentProtectedAttribute:protected' => 5,
-'parentPrivateAttribute:Doctrine\Tests\Common\Util\TestAsset\ChildWithSameAttributesClass:private' => 6,
 'parentPrivateAttribute:Doctrine\Tests\Common\Util\TestAsset\ParentClass:private' => 3,
+'parentPrivateAttribute:Doctrine\Tests\Common\Util\TestAsset\ChildWithSameAttributesClass:private' => 6,
 ],
 ],
 ];
-- 
2.34.0



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: php-doctrine-common
Source-Version: 3.2.1-1
Done: David Prévot 

We believe that the bug you reported is fixed in the latest version of
php-doctrine-common, 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-doctrine-common 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Dec 2021 23:15:31 -0400
Source: php-doctrine-common
Architecture: source
Version: 3.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 1000585
Changes:
 php-doctrine-common (3.2.1-1) unstable; urgency=medium
 .
   [ Maciej Malarz ]
   * Handle PHP 8.1 types (Closes: #1000585)
Checksums-Sha1:
 3a239b3f6e70e83958f331345a9b5e4502b236dc 1914 php-doctrine-common_3.2.1-1.dsc
 4a24520c65b479d4f2f2c9926de55e545aa4337d 38444 
php-doctrine-common_3.2.1.orig.tar.xz
 f0eccda3c960a7264a94974b149eb58fb6f346ff 14096 
php-doctrine-common_3.2.1-1.debian.tar.xz
 146e9ae7c27a16fafda50d5ea3c427264bc14ddc 7893 
php-doctrine-common_3.2.1-1_amd64.buildinfo
Checksums-Sha256:
 

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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 01:04:23 +
with message-id 
and subject line Bug#999014: fixed in playmidi 2.4debian-12
has caused the Debian Bug report #999014,
regarding playmidi: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: playmidi
Source-Version: 2.4debian-12
Done: Adrian Bunk 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Dec 2021 02:35:54 +0200
Source: playmidi
Architecture: source
Version: 2.4debian-12
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 965784 999014
Changes:
 playmidi (2.4debian-12) unstable; urgency=low
 .
   * QA upload.
   * debian/compat: 5 -> 7. (Closes: #965784)
   * debian/rules: Add build-{arch,indep}. (Closes: #999014)
Checksums-Sha1:
 675becd8c838b1317e616c76ae999f22f41082e1 1741 playmidi_2.4debian-12.dsc
 2d4890415847d857159d9aec226b8c71c44c5d3c 34272 playmidi_2.4debian-12.diff.gz
Checksums-Sha256:
 d05ce255813a3b8f5c0a0bb62835b60df168b5ecad730dfb717746ed3cb033c6 1741 
playmidi_2.4debian-12.dsc
 a06def8139694c0721524c604bc437a997771366e9e0932d1badf91cdef024ee 34272 
playmidi_2.4debian-12.diff.gz
Files:
 aa86b804ae46ba385870c1490d9c2971 1741 sound optional playmidi_2.4debian-12.dsc
 a425652522a7b3f6fab185602cdc1ce5 34272 sound optional 
playmidi_2.4debian-12.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKXLUACgkQiNJCh6LY
mLEtchAAvApjhzSZD/515TxIt52ThgAfd+DOtoFugp2pvhq0MGrNCAQXAq4Ic+fo
4La3N1PTvtu7qjyRxLS5U6aYak74Fp/A5I7/N1Ca0hdu5/qt0yqfyI+nfBgnTa+0
GcpEkDYEmWMkT5Cm0WF1VTtcpE2QpjS0tpWaNapuYPAxFWXWmBbK6qIvcnAckCNz
kvL0H/Yc7NyQ3he7jt6uW7bIsWZLiOPvfCfNINRVYBQa+K4TuAwdTXk7HmyHmLub
D0D0op88iLjoKMeoPVvRIcSFpvppZe+ssmYqbdf6x43gSjp0kATP4Nx8Ue9C+LgG
zQNH4YORSXL+kdfoUKeqEZmMZKriK4HpbAXWtkFZlHlBB7RCRd2edTPGtVU7hsLd
0AE3B82i//Y3Cs1/1Yt8IElemv7LAyiNGcpx58SRORfTu7y4/4y2t2LxKE6JTPbJ
fbNZ2f40cpZHdcpdRbeyTRLGDRvsp8cZcXNTXg8vY2ktiyLh0yUB01hl43gyu7BJ
J2xXfBf7cjZLlCxbROMNXDnWCDy0QO2d0ZsjG26DeHFlraUb7j8PbbpSNYDUDn7k
arjSdujqNfshxEZwFiZHP2leq6CEL+s0y0fve62BoS3LORWsZSY4RYXD0CEBOrYw
AoXA+78A36g2+KLdXWpiAyK3ZwbwIBPgYdxDGsLnJBuwiirGBRU=
=lzbZ
-END PGP SIGNATURE End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 01:03:39 +
with message-id 
and subject line Bug#998941: fixed in glbsp 2.24-6
has caused the Debian Bug report #998941,
regarding glbsp: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: glbsp
Source-Version: 2.24-6
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
glbsp, 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.
Adrian Bunk  (supplier of updated glbsp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Dec 2021 02:42:31 +0200
Source: glbsp
Architecture: source
Version: 2.24-6
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 965556 998941
Changes:
 glbsp (2.24-6) unstable; urgency=low
 .
   * QA upload.
   * debian/compat: 5 -> 7. (Closes: #965556)
   * debian/rules: Add build-{arch,indep}. (Closes: #998941)
Checksums-Sha1:
 d41fe7cc5bce66526e0bb20678b910eab89a9c41 1869 glbsp_2.24-6.dsc
 196d8789f96162d349ea5182d18f2092016f576a 4447 glbsp_2.24-6.diff.gz
Checksums-Sha256:
 3d23cb85261c7dfd7e9c31b61a37a80769e987078f3dad9c43db9e07a56f9f0a 1869 
glbsp_2.24-6.dsc
 f9a451ec404d1bd9c36e91f12692aaac1f500bb9faacb6768612ac8c2504e88d 4447 
glbsp_2.24-6.diff.gz
Files:
 6631c1f37e4dc38060cf43ca61a89161 1869 utils optional glbsp_2.24-6.dsc
 e9d0426236609f3ea403ce9d0619712e 4447 utils optional glbsp_2.24-6.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKXi8ACgkQiNJCh6LY
mLF8bxAAlpJK92MCUGrdXYxC2kqyi85YqbyLJZV9sGWvQA+bBmeySJyI6infHHLA
cEc5ZCipHOMsFDBTKdZ2iX+u/Ii19yoPr60tWtMdsDdBgxCHo+/hzkGCD2PMnUzY
ZHYva2apYHF8wHilz8XSc8aJ05mhV2yPXh+BDO2hgLlWridW8Xp9AxDl0ZRk5SV/
WWL/v/v9a9ryp4VyTCU5AlN5x2X3D/HUOPu5h1OxfHYFOVJ7seCaPEbsZQKwZj3k
cHveKa9eqXyUqdBom230Gny8sdMzV8dBCMM0qMuZxDzcI6hTfEaj9qBPJIbFjC1H
PExyfT5sood9JaWCia2MrIJK258vU7fJwsIlb5sdhaiGs1jg62i9puYFGlhwQmNO
LlCPDcdV/7NrT/KWHigWlc7lpcUrlUxKj+wImq0m4sHaY2ZIxfMPfm25crp6eLlD
SRZ22GM/aiWsBPxCFQe13TtD2HD26FN4s0m3haGiOKYc+l89obJarM4EA2xu6sQm
eBvKTNXjrkqQcCln8QWGzc7UCRwr8cCWlGBwkaodvAy8UVBe4hr/DTnU++oUdoP0
OVXId+JkPIj0p6Za5XEARbP5jwsJmkcpgk2TtY2ZKtlmdhH8J1Q996uqlrGYuUTM
/D8rYVvxJdlzlbb1F7BARGDflekZRrnCMpS134ebgaol7fboJXA=
=tUHV
-END PGP SIGNATURE End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 01:04:23 +
with message-id 
and subject line Bug#965784: fixed in playmidi 2.4debian-12
has caused the Debian Bug report #965784,
regarding playmidi: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: playmidi
Source-Version: 2.4debian-12
Done: Adrian Bunk 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Dec 2021 02:35:54 +0200
Source: playmidi
Architecture: source
Version: 2.4debian-12
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 965784 999014
Changes:
 playmidi (2.4debian-12) unstable; urgency=low
 .
   * QA upload.
   * debian/compat: 5 -> 7. (Closes: #965784)
   * debian/rules: Add build-{arch,indep}. (Closes: #999014)
Checksums-Sha1:
 675becd8c838b1317e616c76ae999f22f41082e1 1741 playmidi_2.4debian-12.dsc
 2d4890415847d857159d9aec226b8c71c44c5d3c 34272 playmidi_2.4debian-12.diff.gz
Checksums-Sha256:
 d05ce255813a3b8f5c0a0bb62835b60df168b5ecad730dfb717746ed3cb033c6 1741 
playmidi_2.4debian-12.dsc
 a06def8139694c0721524c604bc437a997771366e9e0932d1badf91cdef024ee 34272 
playmidi_2.4debian-12.diff.gz
Files:
 aa86b804ae46ba385870c1490d9c2971 1741 sound optional playmidi_2.4debian-12.dsc
 a425652522a7b3f6fab185602cdc1ce5 34272 sound optional 
playmidi_2.4debian-12.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKXLUACgkQiNJCh6LY
mLEtchAAvApjhzSZD/515TxIt52ThgAfd+DOtoFugp2pvhq0MGrNCAQXAq4Ic+fo
4La3N1PTvtu7qjyRxLS5U6aYak74Fp/A5I7/N1Ca0hdu5/qt0yqfyI+nfBgnTa+0
GcpEkDYEmWMkT5Cm0WF1VTtcpE2QpjS0tpWaNapuYPAxFWXWmBbK6qIvcnAckCNz
kvL0H/Yc7NyQ3he7jt6uW7bIsWZLiOPvfCfNINRVYBQa+K4TuAwdTXk7HmyHmLub
D0D0op88iLjoKMeoPVvRIcSFpvppZe+ssmYqbdf6x43gSjp0kATP4Nx8Ue9C+LgG
zQNH4YORSXL+kdfoUKeqEZmMZKriK4HpbAXWtkFZlHlBB7RCRd2edTPGtVU7hsLd
0AE3B82i//Y3Cs1/1Yt8IElemv7LAyiNGcpx58SRORfTu7y4/4y2t2LxKE6JTPbJ
fbNZ2f40cpZHdcpdRbeyTRLGDRvsp8cZcXNTXg8vY2ktiyLh0yUB01hl43gyu7BJ
J2xXfBf7cjZLlCxbROMNXDnWCDy0QO2d0ZsjG26DeHFlraUb7j8PbbpSNYDUDn7k
arjSdujqNfshxEZwFiZHP2leq6CEL+s0y0fve62BoS3LORWsZSY4RYXD0CEBOrYw
AoXA+78A36g2+KLdXWpiAyK3ZwbwIBPgYdxDGsLnJBuwiirGBRU=
=lzbZ
-END PGP SIGNATURE End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 01:03:39 +
with message-id 
and subject line Bug#965556: fixed in glbsp 2.24-6
has caused the Debian Bug report #965556,
regarding glbsp: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: glbsp
Source-Version: 2.24-6
Done: Adrian Bunk 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Dec 2021 02:42:31 +0200
Source: glbsp
Architecture: source
Version: 2.24-6
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 965556 998941
Changes:
 glbsp (2.24-6) unstable; urgency=low
 .
   * QA upload.
   * debian/compat: 5 -> 7. (Closes: #965556)
   * debian/rules: Add build-{arch,indep}. (Closes: #998941)
Checksums-Sha1:
 d41fe7cc5bce66526e0bb20678b910eab89a9c41 1869 glbsp_2.24-6.dsc
 196d8789f96162d349ea5182d18f2092016f576a 4447 glbsp_2.24-6.diff.gz
Checksums-Sha256:
 3d23cb85261c7dfd7e9c31b61a37a80769e987078f3dad9c43db9e07a56f9f0a 1869 
glbsp_2.24-6.dsc
 f9a451ec404d1bd9c36e91f12692aaac1f500bb9faacb6768612ac8c2504e88d 4447 
glbsp_2.24-6.diff.gz
Files:
 6631c1f37e4dc38060cf43ca61a89161 1869 utils optional glbsp_2.24-6.dsc
 e9d0426236609f3ea403ce9d0619712e 4447 utils optional glbsp_2.24-6.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKXi8ACgkQiNJCh6LY
mLF8bxAAlpJK92MCUGrdXYxC2kqyi85YqbyLJZV9sGWvQA+bBmeySJyI6infHHLA
cEc5ZCipHOMsFDBTKdZ2iX+u/Ii19yoPr60tWtMdsDdBgxCHo+/hzkGCD2PMnUzY
ZHYva2apYHF8wHilz8XSc8aJ05mhV2yPXh+BDO2hgLlWridW8Xp9AxDl0ZRk5SV/
WWL/v/v9a9ryp4VyTCU5AlN5x2X3D/HUOPu5h1OxfHYFOVJ7seCaPEbsZQKwZj3k
cHveKa9eqXyUqdBom230Gny8sdMzV8dBCMM0qMuZxDzcI6hTfEaj9qBPJIbFjC1H
PExyfT5sood9JaWCia2MrIJK258vU7fJwsIlb5sdhaiGs1jg62i9puYFGlhwQmNO
LlCPDcdV/7NrT/KWHigWlc7lpcUrlUxKj+wImq0m4sHaY2ZIxfMPfm25crp6eLlD
SRZ22GM/aiWsBPxCFQe13TtD2HD26FN4s0m3haGiOKYc+l89obJarM4EA2xu6sQm
eBvKTNXjrkqQcCln8QWGzc7UCRwr8cCWlGBwkaodvAy8UVBe4hr/DTnU++oUdoP0
OVXId+JkPIj0p6Za5XEARbP5jwsJmkcpgk2TtY2ZKtlmdhH8J1Q996uqlrGYuUTM
/D8rYVvxJdlzlbb1F7BARGDflekZRrnCMpS134ebgaol7fboJXA=
=tUHV
-END PGP SIGNATURE End Message ---


Bug#1002626: marked as done (When Rules-Require-Root: no, packages should not fail to build as non-root)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 17:54:24 -0700
with message-id <87mtkly2f3@melete.silentflame.com>
and subject line Re: Bug#1002626: debian-policy: building packages should not 
require to be root
has caused the Debian Bug report #1002626,
regarding When Rules-Require-Root: no, packages should not fail to build as 
non-root
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.)


-- 
1002626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-policy
Version: 4.6.0.1
Severity: important

Building packages should not require to be root.

I don't know what's going on, but see

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002497#31

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

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

debian-policy depends on no packages.

Versions of packages debian-policy recommends:
ii  libjs-sphinxdoc  4.3.2-1

Versions of packages debian-policy suggests:
ii  doc-base  0.11.1

-- no debconf information

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

On Mon 27 Dec 2021 at 12:50PM -08, Russ Allbery wrote:

> FWIW, I think Policy requirements may be the wrong way of thinking about
> this problem.  If I try to compile a Perl module with GCC in debian/rules,
> I would be hard-pressed to name a specific Policy requirement that
> violates, but the package wouldn't build and that's a FTBFS bug.  This
> feels more like that: the package metadata says to build it as non-root,
> which means that if it doesn't build as non-root, that's a FTBFS bug.

The sort of case I have in mind is an 'RRR: no'%e package that does not
FTBFS when built as root, but does do so as non-root.  I agree that
that's an FTBFS bug, but is it release-critical?  For a relatively new
feature like RRR, I'm not sure it is, unless Policy says it is.  But I
could be convinced, and I agree with you that the sort of reasoning
you're giving is a good way to think about this sort of thing.

> Anyway, it all seems to be sorted out now, and I suspect the root problem
> was some benign misunderstanding of the root cause Vincent's bug report.

Optimistically going ahead and closing the bug :)

-- 
Sean Whitton


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


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 00:18:31 +
with message-id 
and subject line Bug#999159: fixed in gkrellmoon 0.6-7
has caused the Debian Bug report #999159,
regarding gkrellmoon: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: gkrellmoon
Source-Version: 0.6-7
Done: Adrian Bunk 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Dec 2021 01:51:55 +0200
Source: gkrellmoon
Architecture: source
Version: 0.6-7
Distribution: unstable
Urgency: medium
Maintainer: Adrian Bunk 
Changed-By: Adrian Bunk 
Closes: 999159
Changes:
 gkrellmoon (0.6-7) unstable; urgency=medium
 .
   * debian/rules: Add build-{arch,indep}. (Closes: #999159)
Checksums-Sha1:
 265a29b8cf645c45f2895aa41c1b2164f016f7d0 1656 gkrellmoon_0.6-7.dsc
 5b6be01c169e6ac94b8bde814238d55ee7bae9d8 2533 gkrellmoon_0.6-7.diff.gz
Checksums-Sha256:
 65d4e4626cb2dc28fa387641492802ce332e1f916ef5ab5bf82352dc12b7724c 1656 
gkrellmoon_0.6-7.dsc
 654b800f458c0888c0edc3c6c0d002f6913cb38f10d803b63f823457507c7bd8 2533 
gkrellmoon_0.6-7.diff.gz
Files:
 20276a7714c601b857641b1934ce538b 1656 x11 optional gkrellmoon_0.6-7.dsc
 622b82b5503d6d10c38f0a6af8e02987 2533 x11 optional gkrellmoon_0.6-7.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKUhUACgkQiNJCh6LY
mLGV0g/+IgR/3vaq/ODNXLlyhYBWe4WPmihGa4/eY+X9tul3DQ/J9SUzbtEJYBdX
YY2Q4R0SsZrAZFcx5kWFGNw65FJQSUMlk4vwAix5jGJPyb874dVYiN6W6YfrStEj
MjRXumrv3W4Pz8tab/tcQJj1myBY4bbnUFw5xygscTswjBOmchDdrFicdBpei/ey
tGZxfIN7Uw3RyiKVWgkfbm856zYOoS1ggJZbBx+09VBfdfx12qhVgFl4yGI9AuUb
UvvKJt30AxH3nbDhPW90maZoeeeuFhg5d6hwuyMemjEfvbRL21kyq78Ao9EIXrx1
Xy4+SS5DjFlEbnE+HNyjBKWfCNMIq1kxrWk7i2jlZy2AqPJzE9sW+CfJBuDbtD8K
+sjK9HxmULs+kkbufldnyUbeDPX2IgBXy95pXZZekjUpM9ddesqGK9ilO0eY8C5I
5V6aWH76M7FQ0o0Gf4e91rzv/kThiMN+Jee9VXbJWhWvgOk9FiD+NvU3p8/NXcxY
fy3UYwMT46OrU8zSCBXCz7O6ZgqzEk0AbbxwHGMEX+epDG0Qe3bsK9MbT7k5m6do
lg2fehEg53DpsxaZVPSSaZtvD8hBC2GYgI3Wet59ICEY4sB/7x0uDt25mlVoOYHi
F1eH+PGf67ItA/Bq1FQAnAvqE8DoEhbmkbqmW12lWuiOjyqdQf4=
=w2xd
-END PGP SIGNATURE End Message ---


Bug#1002267: marked as done (libvt-ldap-java: FTBFS: [ERROR] Failed to execute goal on project vt-ldap: Could not resolve dependencies for project edu.vt.middleware:vt-ldap:jar:3.3.8: Cannot access ce

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 00:19:39 +
with message-id 
and subject line Bug#1002267: fixed in libvt-ldap-java 3.3.8-4
has caused the Debian Bug report #1002267,
regarding libvt-ldap-java: FTBFS: [ERROR] Failed to execute goal on project 
vt-ldap: Could not resolve dependencies for project 
edu.vt.middleware:vt-ldap:jar:3.3.8: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
javax.servlet:javax.servlet-api:jar:3.1 has not been downloaded from it before. 
-> [Help 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibvt-ldap-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for edu.vt.middleware:vt-ldap:jar:3.3.8
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but 
> found duplicate declaration of plugin 
> org.apache.maven.plugins:maven-resources-plugin @ line 158, column 12
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING] 
> [INFO] 
> [INFO] -< edu.vt.middleware:vt-ldap 
> >--
> [INFO] Building VT LDAP Libraries 3.3.8
> [INFO] [ jar 
> ]-
> [WARNING] The POM for javax.servlet:javax.servlet-api:jar:3.1 is missing, no 
> dependency information available
> [WARNING] The artifact dom4j:dom4j:jar:debian has been relocated to 
> org.dom4j:dom4j:jar:debian
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  0.136 s
> [INFO] Finished at: 2021-12-20T18:56:38Z
> [INFO] 
> 
> [ERROR] Failed to execute goal on project vt-ldap: Could not resolve 
> dependencies for project edu.vt.middleware:vt-ldap:jar:3.3.8: Cannot access 
> central (https://repo.maven.apache.org/maven2) in offline mode and the 
> artifact javax.servlet:javax.servlet-api:jar:3.1 has not been downloaded from 
> it before. -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
> dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
> make: *** [debian/rules:4: build] Error 25


The full build log is available from:

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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 00:19:44 +
with message-id 
and subject line Bug#998998: fixed in plib-doc 1:1.8.5-4
has caused the Debian Bug report #998998,
regarding plib-doc: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: plib-doc
Source-Version: 1:1.8.5-4
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
plib-doc, 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.
Adrian Bunk  (supplier of updated plib-doc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Dec 2021 01:57:37 +0200
Source: plib-doc
Architecture: source
Version: 1:1.8.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 998998
Changes:
 plib-doc (1:1.8.5-4) unstable; urgency=medium
 .
   * QA upload.
   * Set Maintainer to Debian QA Group. (see #674892)
   * debian/rules: Add build-{arch,indep}. (Closes: #998998)
Checksums-Sha1:
 88b4892177d4d4228725377f65467d06a911c1d7 1862 plib-doc_1.8.5-4.dsc
 3d4ea3818b8848a40f6b99789167f93624a230c4 649623 plib-doc_1.8.5-4.diff.gz
Checksums-Sha256:
 9887c4bac52d908dcaacfc41d4ccceaef211a21be16d2ac3f21aa2bee19bd380 1862 
plib-doc_1.8.5-4.dsc
 86da41f1e6e05e4c0480c9d83cf780b756b16391bd63b15fc63b39b87b461240 649623 
plib-doc_1.8.5-4.diff.gz
Files:
 d9ac6e4b7eb861d241f62030af32c674 1862 doc extra plib-doc_1.8.5-4.dsc
 b617f246aaac39e41cae32cbc4162502 649623 doc extra plib-doc_1.8.5-4.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKU7IACgkQiNJCh6LY
mLF1VA/9GUOAr+NSiPpF9Mzww5vf3PUYQXCfe6GQat6mU62SPo7OKyBA5eRC9V0I
r4uyZ0ySw833swnqwZkyMoE/rcTIf/DAtnxHkSQF6nESq3rZMpk8Vne8lzrIIH2L
QngGjO9GuH3Lc95w2DbkBaTcuR+BSYfAeaDKnc6LvxjxlUjZBp3JioCGcHczSRxy
yxt19qflB4K1GZ1NvNT5w1+ebcTsfAtLcqz/jsKoA6fMZXdrD/4+s437X2zF3TQK
lJtBi9P+iZbuLGKT9FUyhSsCZZ0MMCWAZa3URI3i4xqJhNDGM7FrH4dDlSd9LoVi
GT9o8A+GmOEku46LTQC5RGDoG06qt863EvTZVP8NBvzS9LPxya2Jj6PH8PHjXbd6
zfbYO7cFn9J7efHNZ1psZH23pDclOr/gjpk+OrRwENaXR3hiBbLpG1WlMcEdc9lq
FH7RBbHEfmFY8zacNOXHK2j7zhdqbzTiXkdQzMbhC3i7IYMpG16Jn9qGEZwe0GjW
dQ3W6o6naFfmYy+7SrZPKTn77o1QcQUedE+XuNuzp9uoPyuyePHqw4OMjV7FouGi
/q5SKKV0zS+Os+ebk0lwR3TIOrYUf4vQVs1ThqkZ3fYlHyDeD8zdUWPRPuNJ5Z4q
gyaUW2r4eOBTYQZ74QQW7nsuo0HFD3tQX21XRSM/WLescGRyQgI=
=X5Bh
-END PGP SIGNATURE End Message ---


Bug#1002265: marked as done (libquartz2-java: FTBFS: [ERROR] Failed to execute goal on project quartz-core: Could not resolve dependencies for project org.quartz-scheduler.internal:quartz-core:jar:2.3

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 00:19:34 +
with message-id 
and subject line Bug#1002265: fixed in libquartz2-java 2.3.2-3
has caused the Debian Bug report #1002265,
regarding libquartz2-java: FTBFS: [ERROR] Failed to execute goal on project 
quartz-core: Could not resolve dependencies for project 
org.quartz-scheduler.internal:quartz-core:jar:2.3.2: Cannot access 
terracotta-snapshots (http://www.terracotta.org/download/reflector/snapshots) 
in offline mode and the artifact javax.servlet:javax.servlet-api:jar:3.1 has 
not been downloaded from it before. -> [Help 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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with javahelper
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   mh_patchpoms -plibquartz2-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>jh_linkjars
>dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] quartz-parent  
> [pom]
> [INFO] quartz-core
> [jar]
> [INFO] quartz-commonj 
> [jar]
> [INFO] quartz-jobs
> [jar]
> [INFO] quartz-plugins 
> [jar]
> [INFO] quartz 
> [jar]
> [INFO] 
> [INFO] -< org.quartz-scheduler:quartz-parent 
> >-
> [INFO] Building quartz-parent 2.3.2   
> [1/6]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] -< org.quartz-scheduler.internal:quartz-core 
> >--
> [INFO] Building quartz-core 2.3.2 
> [2/6]
> [INFO] [ jar 
> ]-
> [WARNING] The POM for javax.servlet:javax.servlet-api:jar:3.1 is missing, no 
> dependency information available
> [INFO] 
> 
> [INFO] Reactor Summary for quartz-parent 2.3.2:
> [INFO] 
> [INFO] quartz-parent .. SUCCESS [  0.002 
> s]
> [INFO] quartz-core  FAILURE [  0.074 
> s]
> [INFO] quartz-commonj . SKIPPED
> [INFO] quartz-jobs  SKIPPED
> [INFO] quartz-plugins . SKIPPED
> [INFO] quartz . SKIPPED
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  0.180 s
> [INFO] Finished at: 2021-12-20T18:58:49Z
> [INFO] 
> 
> [ERROR] Failed to execute goal on project quartz-core: Could not resolve 
> dependencies for project org.quartz-scheduler.internal:quartz-core:jar:2.3.2: 
> Cannot access terracotta-snapshots 
> (http://www.terracotta.org/download/reflector/snapshots) in offline mode and 
> the artifact javax.servlet:javax.servlet-api:jar:3.1 has not been downloaded 
> from it before. -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> 

Bug#1002263: marked as done (jaxws: FTBFS: [ERROR] Failed to execute goal on project httpspi-servlet: Could not resolve dependencies for project com.sun.xml.ws:httpspi-servlet:jar:2.3.0.2: Cannot acce

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 00:03:43 +
with message-id 
and subject line Bug#1002263: fixed in jaxws 2.3.0.2-2
has caused the Debian Bug report #1002263,
regarding jaxws: FTBFS: [ERROR] Failed to execute goal on project 
httpspi-servlet: Could not resolve dependencies for project 
com.sun.xml.ws:httpspi-servlet:jar:2.3.0.2: Cannot access releases.java.net 
(http://maven.java.net/content/repositories/releases/) in offline mode and the 
artifact javax.servlet:javax.servlet-api:jar:3.1 has not been downloaded from 
it before. -> [Help 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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build -- -f jaxws-ri/pom.xml install -DskipTests
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode -f 
> jaxws-ri/pom.xml install -DskipTests -DskipTests -Dnotimestamp=true 
> -Dlocale=en_US
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] JAX-WS RI Bill-of-Materials (BOM)  
> [pom]
> [INFO] JAX-WS RI Bill-of-Materials (BOM) Extensions   
> [pom]
> [INFO] JAX-WS (JSR-224) Reference Implementation  
> [pom]
> [INFO] JAX-WS RI Runtime (rt) 
> [jar]
> [INFO] JAX-WS RI Fast Infoset Support (rt-fi) 
> [jar]
> [INFO] JAX-WS RI HTTP SPI (httpspi-servlet)   
> [jar]
> [INFO] JAX-WS RI Servlet Support (servlet)
> [jar]
> [INFO] JAX-WS RI Runtime 9 (rt-jdk9)  
> [jar]
> [INFO] JAX-WS RI Bundles  
> [pom]
> [INFO] JAX-WS RI Runtime Bundle   
> [pom]
> [INFO] 
> [INFO] < com.sun.xml.ws:jaxws-ri-bom 
> >-
> [INFO] Building JAX-WS RI Bill-of-Materials (BOM) 2.3.0.2
> [1/10]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ 
> jaxws-ri-bom ---
> [INFO] Installing /<>/jaxws-ri/boms/bom/pom.xml to 
> /<>/debian/maven-repo/com/sun/xml/ws/jaxws-ri-bom/2.3.0.2/jaxws-ri-bom-2.3.0.2.pom
> [INFO] 
> [INFO] --< com.sun.xml.ws:jaxws-ri-bom-ext 
> >---
> [INFO] Building JAX-WS RI Bill-of-Materials (BOM) Extensions 2.3.0.2 
> [2/10]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] --- maven-install-plugin:2.5.2:install (default-install) @ 
> jaxws-ri-bom-ext ---
> [INFO] Installing /<>/jaxws-ri/boms/bom-ext/pom.xml to 
> /<>/debian/maven-repo/com/sun/xml/ws/jaxws-ri-bom-ext/2.3.0.2/jaxws-ri-bom-ext-2.3.0.2.pom
> [INFO] 
> [INFO] ---< com.sun.xml.ws:project 
> >---
> [INFO] Building JAX-WS (JSR-224) Reference Implementation 2.3.0.2
> [3/10]
> [INFO] [ pom 
> ]-
> [WARNING] The artifact javax.jws:jsr181-api:jar:debian has been relocated to 
> javax.jws:javax.jws-api:jar:debian
> [INFO] 
> [INFO] --- import-properties-plugin:3.0.6:import-pom-properties (default) @ 
> project ---
> [WARNING] Searching project: jaxws-ri-bom
> [INFO] Resolving properties for com.sun.xml.ws:jaxws-ri-bom
> [INFO] Imported via import-scope: org.glassfish.jaxb:jaxb-bom:debian
> [INFO] Setting property: jaxb-api.version:2.3.0
> [INFO] Setting property: debian.originalVersion:2.3.0.1
> [INFO] Setting property: debian.package:libjaxb-java
> [INFO] Setting property: stax-ex.version:1.7.8
> [INFO] Setting property: 

Bug#1002284: marked as done (jersey1: FTBFS: [ERROR] Failed to execute goal on project jersey-servlet: Could not resolve dependencies for project com.sun.jersey:jersey-servlet:jar:1.19.3: Cannot acces

2021-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 28 Dec 2021 00:03:49 +
with message-id 
and subject line Bug#1002284: fixed in jersey1 1.19.3-7
has caused the Debian Bug report #1002284,
regarding jersey1: FTBFS: [ERROR] Failed to execute goal on project 
jersey-servlet: Could not resolve dependencies for project 
com.sun.jersey:jersey-servlet:jar:1.19.3: Cannot access repository.jboss.org 
(http://repository.jboss.org/nexus/content/groups/public/) in offline mode and 
the artifact javax.servlet:javax.servlet-api:jar:3.1 has not been downloaded 
from it before. -> [Help 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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> # Generate the classes manually since the maven-jaxb-plugin isn't in Debian
> /usr/bin/xjc -p com.sun.research.ws.wadl -d jersey-server/src/main/java 
> -catalog jersey-server/etc/catalog.xml jersey-server/etc/wadl.xsd
> Cannot find CatalogManager.properties
> parsing a schema...
> compiling a schema...
> com/sun/research/ws/wadl/Application.java
> com/sun/research/ws/wadl/Doc.java
> com/sun/research/ws/wadl/Grammars.java
> com/sun/research/ws/wadl/HTTPMethods.java
> com/sun/research/ws/wadl/Include.java
> com/sun/research/ws/wadl/Link.java
> com/sun/research/ws/wadl/Method.java
> com/sun/research/ws/wadl/ObjectFactory.java
> com/sun/research/ws/wadl/Option.java
> com/sun/research/ws/wadl/Param.java
> com/sun/research/ws/wadl/ParamStyle.java
> com/sun/research/ws/wadl/Representation.java
> com/sun/research/ws/wadl/Request.java
> com/sun/research/ws/wadl/Resource.java
> com/sun/research/ws/wadl/ResourceType.java
> com/sun/research/ws/wadl/Resources.java
> com/sun/research/ws/wadl/Response.java
> com/sun/research/ws/wadl/package-info.java
> dh_auto_build
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the effective model 
> for com.sun.jersey.contribs:jersey-guice:jar:1.19.3
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 138, column 
> 12
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING] 
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] jersey-project 
> [pom]
> [INFO] jersey-core
> [jar]
> [INFO] jersey-server  
> [jar]
> [INFO] jersey-servlet 
> [jar]
> [INFO] jersey-client  
> [jar]
> [INFO] jersey-guice   
> [jar]
> [INFO] Contributions to Jersey
> [pom]
> [INFO] jersey-atom
> [jar]
> [INFO] jersey-fastinfoset 
> [jar]
> [INFO] jersey-json
> [jar]
> [INFO] 
> [INFO] ---< com.sun.jersey:jersey-project 
> >
> [INFO] Building jersey-project 1.19.3
> [1/10]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:bundle (osgi-bundle) @ jersey-project ---
> [WARNING] Ignoring project type pom 

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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 23:49:03 +
with message-id 
and subject line Bug#999003: fixed in imgvtopgm 2.0-9.1
has caused the Debian Bug report #999003,
regarding imgvtopgm: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: imgvtopgm
Source-Version: 2.0-9.1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated imgvtopgm 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: Mon, 27 Dec 2021 21:04:01 +0200
Source: imgvtopgm
Architecture: source
Version: 2.0-9.1
Distribution: unstable
Urgency: medium
Maintainer: Erik Schanze 
Changed-By: Adrian Bunk 
Closes: 999003
Changes:
 imgvtopgm (2.0-9.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/rules: Add build-{arch,indep}. (Closes: #999003)
Checksums-Sha1:
 14bffdfca6ea5d9b73acb456c276b68b15ef902e 1711 imgvtopgm_2.0-9.1.dsc
 9c6b64147d9a0642697c22979cf625a893b9d498 6692 imgvtopgm_2.0-9.1.diff.gz
Checksums-Sha256:
 f50e551e4b91db5ce732564efbe2d65fb7275c28b4d1e29877193f42d8999122 1711 
imgvtopgm_2.0-9.1.dsc
 fc4f91897f1deecff28e56314c513948ef30cb9812a9b1e97ca926599c36d345 6692 
imgvtopgm_2.0-9.1.diff.gz
Files:
 9e3073b48d54ccf39443b1752b600134 1711 otherosfs optional imgvtopgm_2.0-9.1.dsc
 f7e243392ba60b1f0eeb8615d44cea93 6692 otherosfs optional 
imgvtopgm_2.0-9.1.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKDpsACgkQiNJCh6LY
mLEnvQ/7BRk1t3hjhBkmFkNUPUUmcm7yVvXwbJsTB4SY6u51C0Qkcn2n9LbflAiJ
Sxp1Q4l6Iw8IRO9++SUhLAMlMwyNKeaMtt5Zp9QBJDXT6MR0y0qyS+HKHmMjuFT0
oqlwaZOtihd4rXZHeZyHv5D++5SIX7cSvAvBC1wVOWrKFLV8GgIgp/3rGTFm+qRm
x7YmaVWZMpT6NIrAntZ7eAk1UaTKZzByHWJ6zS9/82cNw4DfdtOXP/GZ73SO8OV/
kReZvyPHMuI7w5OcuYnu9+p8/KR8R0Rl/GL/gchdNnPJSEUj+AonVSuTqlleXotx
a1WWs8gUNglif6qfJX7Ux6e0FsSNIbEsTZMp17Y0CZjG7LdAOVDBegt0EnkCgVkG
3u73TSPAFNE1zPF70VIzKdTHttYjHLWWLsfIcF7y+WeEDqm+Z7VG9tIEKhEDCwyF
hjfdaAFqR7mCnJqHVBxmIjU3V0chXz4RMJvPhd8t6qxsb2KHc7t5FrVetV2lY6lX
xNYpcGBm7tlws/vmyBktlUyyvGUfVzWGoXaZ6jclaB/JEvuo53j4FyN+6iw1Aa+y
jEbKmZdsauuPV98q1m/NZIdPZhY84az9EyXGixjgPDz60o6PnHZGGdHuOoD8yJwz
z2Zho8QeC88oZIBcAqp2M6HgBjkyXgfCt+OwQnirMdNYvChYBjM=
=Zddm
-END PGP SIGNATURE End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 23:33:30 +
with message-id 
and subject line Bug#999255: fixed in poppassd 1.8.5-6
has caused the Debian Bug report #999255,
regarding poppassd: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: poppassd
Source-Version: 1.8.5-6
Done: Adrian Bunk 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Dec 2021 01:09:09 +0200
Source: poppassd
Architecture: source
Version: 1.8.5-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 999255
Changes:
 poppassd (1.8.5-6) unstable; urgency=medium
 .
   * QA upload.
   * debian/rules: Add build-{arch,indep}. (Closes: #999255)
Checksums-Sha1:
 44b712e7e003a88f22c56cab8f12a488be7654d8 1648 poppassd_1.8.5-6.dsc
 3acd60730585fed04cc6b46bf08ddab684d85cf4 6122 poppassd_1.8.5-6.diff.gz
Checksums-Sha256:
 8021ab6a4a1d28b7d2c9b6369bd6ba8dceb93d1e06d55a60cfc60cbb77ca4aa1 1648 
poppassd_1.8.5-6.dsc
 6ef0c501f09996fa5fae7302f408bc5ea1ab0ff1c20e5b8cd48f632155ed811b 6122 
poppassd_1.8.5-6.diff.gz
Files:
 ec7c3301c0e84ce8fdbab6184acd98f5 1648 mail optional poppassd_1.8.5-6.dsc
 a90448437be959bb2c65b9332ff8dfc5 6122 mail optional poppassd_1.8.5-6.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKSCUACgkQiNJCh6LY
mLHpDA/7B3Pgt+z99E9USg3Mq4WjN8kI3xiGdap18WkIvex0FlLh6RgAerAmL0B+
RTP/s0DKp41kLDBLTYNPRkU9WYo9hDVqrFkx2d5bzf9uSebRudNiXQ6O52AXPagd
jB7AFr9u97p/cXP970Nli/q4T2G9jPhbVpv3nQnmtCgeiGuq+UGbdwmq0dF1Dwhq
nTIdJ4aLFR7XnU56FhdRn2P/NMK6IsVHyBhJd4fA18yUsR+tT3Hpjdek8iJhkPWb
+liB/eUo2ncfzcMRpiQRymYJek0wn6A72pZ+BdQeV1fmQ1LMngPSknF5Q/HfIfRT
Gm9iVxAidTjFFNZRahU8ftX/dHMq7Iv3hKnRnSJ3Rmx5ue9FlfNRmx8hu/NIt0Gd
5s44oidwY6hojhJJvELBcLwc25BwjMIHQd2UIqsPGFF794P4FJkBtSZ4c0BB8MKp
ikpWP9CmbJr3lkwvcUJkhnxedvX19kCB8EheNnwDcaldYn3RLj1BjZd3NAPBmSDO
We1+XwJXLbsMO48VsYOSzwsWRJAlqDYEqb3AEl3AyY4SznhQOPZdFNK4gYQ59sih
Hj3BymtR6dp7KBFIjLNsyOgWxPYSZH8SjysUVhX7XsI3p4uL2niTrLOew7kO5pvU
pXFjb/8zLl612YKHeuKPJliosD6d/yOVJr+xaDq7qZ6Pf5ZKu5w=
=N245
-END PGP SIGNATURE End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 23:18:55 +
with message-id 
and subject line Bug#999288: fixed in pppconfig 2.3.26
has caused the Debian Bug report #999288,
regarding pppconfig: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: pppconfig
Source-Version: 2.3.26
Done: Adrian Bunk 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Dec 2021 00:51:19 +0200
Source: pppconfig
Architecture: source
Version: 2.3.26
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 999288
Changes:
 pppconfig (2.3.26) unstable; urgency=medium
 .
   * QA upload.
   * debian/rules: Add build-{arch,indep}. (Closes: #999288)
Checksums-Sha1:
 55bfaaa10e5831c56408ef88946a9fe4fe2a145b 1457 pppconfig_2.3.26.dsc
 a12d7a1ed726b0ff39163c5a1b1a8fe022ad17e9 403030 pppconfig_2.3.26.tar.gz
Checksums-Sha256:
 eef0c324414388e8f753544cd627da005d9a591363e815e7eb28456938128b43 1457 
pppconfig_2.3.26.dsc
 37650f98a6a8a943de2d3075d45c117857414468db5030648f5429a21ba67050 403030 
pppconfig_2.3.26.tar.gz
Files:
 3eb7a23f30096768a916910e495e592e 1457 admin optional pppconfig_2.3.26.dsc
 83c9f44f5aa84a09dbb18cae193ac27e 403030 admin optional pppconfig_2.3.26.tar.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKQ+4ACgkQiNJCh6LY
mLFTThAAjywo82kVJ+RFsiGJl0GgVa+n600zLfEX+bU5IiE//unkPFw/meyJFQau
2QZmvqiimeoZkLU7QMd5ybdT1XUh/ceQgmye2in246i68uHmnqW488nIpkKQUxUS
qBFR4ves4mN4ydhbjn0qsv1gkYFalLtIQtSRDPg7vXZNKKt5HNb5saQU3g89AAs2
5HZ089THWOzmlK7X+DrR9FpScgH4U/QR14nea54+YNHa4UssE6emiGarBZPoQ+dY
YbxK6zeWNJDylprWq1+L8Y/0yy21swqBJyzMRj3Mz5h83KeZLTtmv2iWYrqc++si
Af99iTtfrLEoLfs8j+MCLNNoqtlw9Oiy9mUt5S5T1QHl5pFR6Nawxhxs/6wc+lQy
T/Uxnc0cIdjdw1/ac1RjtYJNcIOd9O6i+bzAbQt8D37d6SJgo8P1uNubCZh/SOP4
PcYlmZFrEsdol7RJK6fN4cZ/yiyA6v6qFKBJPLkQnNQb+kR0a1xDwDrkW/lv6Yc9
HrAvp82woUHltv8hUO/UkkWBuD0r3OS3GaxPKaHc8lgo6hiFUjTaCIWJ7b3gOiiF
AkdsH2jdPhaxnw7MCGkHedBbuBEEqt4npE6j53ehBca3DuZxgVMMLptALdGLkb6n
rLDTOpj1fUCcQ0VUtluf2ndEJibaZkbdUxbdeskmtZ8GKnDZJEo=
=cz0Y
-END PGP SIGNATURE End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 22:53:12 +
with message-id 
and subject line Bug#999005: fixed in razor 1:2.85-5
has caused the Debian Bug report #999005,
regarding razor: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: razor
Source-Version: 1:2.85-5
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated razor 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: Mon, 27 Dec 2021 23:34:34 +0200
Source: razor
Architecture: source
Version: 1:2.85-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 999005
Changes:
 razor (1:2.85-5) unstable; urgency=medium
 .
   * QA upload.
   * Set Maintainer to Debian QA Group. (see #866833)
   * debian/rules: Add build-{arch,indep}. (Closes: #999005)
Checksums-Sha1:
 3452e3bdfa731dd2729f8060b3498f38c37d9616 1864 razor_2.85-5.dsc
 778042d87c819632d714049f0863797009b0668c 15428 razor_2.85-5.diff.gz
Checksums-Sha256:
 97fc9ac1f46dc0441dc4a7eff248b917fb4586f29b197d810d58ac4e50cb3e89 1864 
razor_2.85-5.dsc
 18e9a2383cce7d9d82af40819a78b1f1b6e12f228bd302b9c19a01c95171e931 15428 
razor_2.85-5.diff.gz
Files:
 c885b9d5dead902d52f5975a963238ae 1864 mail optional razor_2.85-5.dsc
 ca70dd4c8ca8a2a1901e494a906839a5 15428 mail optional razor_2.85-5.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKMncACgkQiNJCh6LY
mLGltg//R6Bi21YHomzIuXHb/IGPTOa+BaeQJ6VodjVKSIsS51kcMCMn1EUDWA4t
TWJW2Drm00ItgdRYgkoJ825Ntk4Bd85GEEQOf8JAW03C8Flp2DKn0NSeSMPBi55w
PFAY/viDkGw7ECa8Na38kP8unchcMAZrknyWKLk8FsrwWxJyIPreh6rmuJe5VQmk
ol0Jy48pdwz/03k+q4e3Gxf9TcxAaDsLEnqX6rM44+2YRhiuCGd7vgDYUUFoYZtZ
ZsrBPW7rSxFHXjFn0DjGWwZZSdD69ka7Rkm1WPlXcY+7sjUfoKvqztW33Zjb3VCz
XLKMO6v/H4Hh8aUokJ/yERqpQkf00dbqKU/wByUAOb/w1bDBI2S7/9W2JNx73iVL
GnQL3NDrTM1Q26HsJs8NiwhYFlAEAx7pLT6x5Nn1rhb3keQg03woI4aytMkoUQ6T
Sc9fKj83Ya3cgOaMkzBnIVwDUyegG3hu9BeAoQpTxsZ/I9QQHvmLZmjgIFGQZX0A
QmeyktQ07w1XmLt44/Ax+dKKY1N9FpifIaKZ3y0qzo1htJiKg7/KVzIvn51BeMRK
JHkq8h2zMTBkt0yJOlZXQj4dpOABCh7ofYbRTRktFbSqhUMZ9dFfK8NV2S5RvPHM
KrMFh5d3FLtJMicwMWw6G5EXfSJ+6Rf6pDUdF1HgvP/GBSNzyOc=
=W00X
-END PGP SIGNATURE End Message ---


Bug#1002688: marked as done (ceph: b-d on python3-all-dev, but not built for all supported Python3 versions)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 21:48:38 +
with message-id 
and subject line Bug#1002688: fixed in ceph 16.2.6+ds-10
has caused the Debian Bug report #1002688,
regarding ceph: b-d on python3-all-dev, but not built for all supported Python3 
versions
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.)


-- 
1002688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ceph
Version: 16.2.6+ds-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev

Hi Maintainer

This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions.  This is seen
on the transition tracker for adding python3.10 support [1] and
creates false positives.

Please either replace the b-d python3-all-dev with python3-dev, or
build for all supported Python3 versions.  With the former solution
yet get later exposure to a new python3 version, with the latter
solution you get early exposure.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.10-add.html
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 16.2.6+ds-10
Done: Thomas Goirand 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Dec 2021 15:48:02 +0100
Source: ceph
Architecture: source
Version: 16.2.6+ds-10
Distribution: unstable
Urgency: medium
Maintainer: Ceph Packaging Team 
Changed-By: Thomas Goirand 
Closes: 1002688
Changes:
 ceph (16.2.6+ds-10) unstable; urgency=medium
 .
   * Fix libcephfs2.symbols.
   * Build-depends only on python3-dev, not python3-all-dev (Closes: #1002688).
Checksums-Sha1:
 d69a21a83bb37f044655627879c58d0a8b870a76 8256 ceph_16.2.6+ds-10.dsc
 af6247a6ac14075d0b0ad5413f57261fc320bcd7 116468 ceph_16.2.6+ds-10.debian.tar.xz
 4cf9b3cebb638450a780a6aa81642d7e1191c6ff 40664 
ceph_16.2.6+ds-10_amd64.buildinfo
Checksums-Sha256:
 f7f0d9f05a4c95e4c520cfa25584da9f237d5adcfd1be5314749a351721d5bd7 8256 
ceph_16.2.6+ds-10.dsc
 2a17212ebbb6b42a71dd5ac367ae15c13c4a40ba36b1e18ef66390c5f196 116468 
ceph_16.2.6+ds-10.debian.tar.xz
 d8946eeb8564063fb254e30307f2e146501e3c146de40693a3fbf07f54af777a 40664 
ceph_16.2.6+ds-10_amd64.buildinfo
Files:
 b4413ee0680910498c2f7084950d1afb 8256 admin optional ceph_16.2.6+ds-10.dsc
 eed5718ad5fe64cf44474cc318682a48 116468 admin optional 
ceph_16.2.6+ds-10.debian.tar.xz
 c856dcfb40e46c36c7c52a3097f3 40664 admin optional 
ceph_16.2.6+ds-10_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmHKL9cACgkQ1BatFaxr
Q/7ZTA/+Oz6EUMZlmSiVMDVCBdNpd0hX7VhLxcInTi3uw6ZnUp8bt5ec2aB7159K
XC1AerVuKE1c+IglNSMvvZGfFCrOe9tJaDgg3guR0dhRUwi0o6GN06IxwkCNpzp6
7XsGABU/11o9GtsbhOSZZtKf5gFIvg4jtkKClsQvERjGaSNN4K+1EBv60dBtlLHL
/901qfgxAFOuTxnzGZOdWOu1ztLcMroMfD+DbC6piyFWRGKsk1kSYIeS9VciYv3X
7qUyInMbKBK2WtT6xwkArKJpsmMNSq3aZYd3gpPqhKCnCdHEkvYq4PhIL1eKsjDR
xk/SMIzDwqh0vDgXRK09USLYa5xaksC+V7fE0g2Tww7sNzgyEVcSB6rYDpioVQgV
hnad/jfQNpF4nBncjdX1s77bnbzDERrzULZQLgjLamNzH0+CkNgSTrLikHOGeB9T
07ApbDp+BZgjFsX5wTna0ee+RoiuzTEwUTXgPa2WLPk0DP6319mBMvoV364iC07L
qg/M1KhfOAZYTpdkO6rirPbGlIWL5vnyOxKATdq8LN10Nsx3LFCnrpv+mp5LEAhC
YLxPWP5GNSaz3M4/a+2jO3CbLJL8Z3yf9GltDdDjykhciTRjqqNSAdF/8P7ByKEr
sOFfWJjok4Nrz4Lsh/PN1nmJUY9xaYCsHXM7pF8t2qh0Zwc8VUg=
=PrpK
-END PGP SIGNATURE End Message ---


Bug#1000305: marked as done (lsp-plugins FTCBFS: uses the build architecture ld and pkg-config)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 21:49:58 +
with message-id 
and subject line Bug#1000305: fixed in lsp-plugins 1.1.31-1
has caused the Debian Bug report #1000305,
regarding lsp-plugins FTCBFS: uses the build architecture ld and pkg-config
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.)


-- 
1000305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lsp-plugins
Version: 1.1.30-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

lsp-plugins fails to cross build from source, becaue it uses the build
architecture ld and pkg-config. For ld, dh_auto_build does not pass a
cross tool as the use of LD variable is inconsistent across upstream
projects. pkg-config instead is hard coded in the upstream build system.
The attached patch addresses both, but it does not make lsp-plugins
cross buildable, because lsp-plugins builds some build tools and fails
running them with an Exec format error (e.g. gen_resources.exe or
gen_php.exe). I suppose more thought is required for fixing these.
Please consider applying my patch as an incremental improvement and
close this bug when doing so.

Helmut
diff --minimal -Nru lsp-plugins-1.1.30/debian/changelog 
lsp-plugins-1.1.30/debian/changelog
--- lsp-plugins-1.1.30/debian/changelog 2021-08-19 12:50:50.0 +0200
+++ lsp-plugins-1.1.30/debian/changelog 2021-11-20 12:54:14.0 +0100
@@ -1,3 +1,10 @@
+lsp-plugins (1.1.30-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Improve cross building: Use the host arch ld and pkg-config. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 20 Nov 2021 12:54:14 +0100
+
 lsp-plugins (1.1.30-1) unstable; urgency=medium
 
   * Provide the lsp-plugins-r3d-glx package,
diff --minimal -Nru lsp-plugins-1.1.30/debian/patches/cross.patch 
lsp-plugins-1.1.30/debian/patches/cross.patch
--- lsp-plugins-1.1.30/debian/patches/cross.patch   1970-01-01 
01:00:00.0 +0100
+++ lsp-plugins-1.1.30/debian/patches/cross.patch   2021-11-20 
12:54:14.0 +0100
@@ -0,0 +1,58 @@
+--- lsp-plugins-1.1.30.orig/scripts/make/configure.mk
 lsp-plugins-1.1.30/scripts/make/configure.mk
+@@ -131,17 +131,17 @@
+   export ICONV_LIBS   = -liconv
+   export MATH_LIBS= -lm
+   export DL_LIBS  = -ldl
+-  export CAIRO_HEADERS= $(shell pkg-config --cflags cairo)
+-  export CAIRO_LIBS   = $(shell pkg-config --libs cairo)
+-  export XLIB_HEADERS = $(shell pkg-config --cflags x11)
+-  export XLIB_LIBS= $(shell pkg-config --libs x11)
+-  export LV2_HEADERS  = $(shell pkg-config --cflags lv2)
+-  export LV2_LIBS = $(shell pkg-config --libs lv2)
+-  export SNDFILE_HEADERS  = $(shell pkg-config --cflags sndfile)
+-  export SNDFILE_LIBS = $(shell pkg-config --libs sndfile)
+-  export JACK_HEADERS = $(shell pkg-config --cflags jack)
+-  export JACK_LIBS= $(shell pkg-config --libs jack)
+-  export OPENGL_HEADERS   = $(shell pkg-config --cflags gl 2>/dev/null || 
echo "")
+-  export OPENGL_LIBS  = $(shell pkg-config --libs gl 2>/dev/null || echo 
"")
++  export CAIRO_HEADERS= $(shell $(PKG_CONFIG) --cflags cairo)
++  export CAIRO_LIBS   = $(shell $(PKG_CONFIG) --libs cairo)
++  export XLIB_HEADERS = $(shell $(PKG_CONFIG) --cflags x11)
++  export XLIB_LIBS= $(shell $(PKG_CONFIG) --libs x11)
++  export LV2_HEADERS  = $(shell $(PKG_CONFIG) --cflags lv2)
++  export LV2_LIBS = $(shell $(PKG_CONFIG) --libs lv2)
++  export SNDFILE_HEADERS  = $(shell $(PKG_CONFIG) --cflags sndfile)
++  export SNDFILE_LIBS = $(shell $(PKG_CONFIG) --libs sndfile)
++  export JACK_HEADERS = $(shell $(PKG_CONFIG) --cflags jack)
++  export JACK_LIBS= $(shell $(PKG_CONFIG) --libs jack)
++  export OPENGL_HEADERS   = $(shell $(PKG_CONFIG) --cflags gl 2>/dev/null || 
echo "")
++  export OPENGL_LIBS  = $(shell $(PKG_CONFIG) --libs gl 2>/dev/null || 
echo "")
+ endif
+ 
+--- lsp-plugins-1.1.30.orig/scripts/make/tools.mk
 lsp-plugins-1.1.30/scripts/make/tools.mk
+@@ -3,6 +3,7 @@
+ TOOL_CC = gcc
+ TOOL_CXX= g++
+ TOOL_PHP= php
++TOOL_PKG_CONFIG = pkg-config
+ 
+ # Setup preferred flags
+ FLAG_RELRO  = -Wl,-z,relro,-z,now
+@@ -24,6 +25,7 @@
+ CXX  ?= $(TOOL_CXX)
+ PHP  ?= $(TOOL_PHP)
+ LD   ?= $(TOOL_LD)
++PKG_CONFIG   ?= $(TOOL_PKG_CONFIG)
+ 
+ MAKE_OPTS = -s
+ CFLAGS   += $(CC_ARCH) $(FLAG_CTUNE) 

Bug#996078: marked as done (gnome-shell-pomodoro: tighten dependency on g-shell)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 21:04:38 +
with message-id 
and subject line Bug#996078: fixed in gnome-shell-pomodoro 0.20.0-2
has caused the Debian Bug report #996078,
regarding gnome-shell-pomodoro: tighten dependency on g-shell
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.)


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

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

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

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

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

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

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-pomodoro
Source-Version: 0.20.0-2
Done: Tobias Frost 

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

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

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated gnome-shell-pomodoro 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Dec 2021 21:42:02 +0100
Source: gnome-shell-pomodoro
Architecture: source
Version: 0.20.0-2
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Closes: 996078
Changes:
 gnome-shell-pomodoro (0.20.0-2) unstable; urgency=medium
 .
   * Tighten dependency on gnome-shell (Closes: #996078)
   * Bump S-V to 4.6.0 -- no changes required.
Checksums-Sha1:
 8374a7efceeac8b6ada627d150969b6db3cd358e 2530 gnome-shell-pomodoro_0.20.0-2.dsc
 571231e2f4da41bed9f2e178aba1ef97873e0101 6588 
gnome-shell-pomodoro_0.20.0-2.debian.tar.xz
 d56cfc6fba480eac24e5a03ba89e9805fadaf842 22418 
gnome-shell-pomodoro_0.20.0-2_amd64.buildinfo
Checksums-Sha256:
 7e835a59f51cd4cab44a0e01380a78eb02598e2e20686a9b3509aaf174a31b20 2530 
gnome-shell-pomodoro_0.20.0-2.dsc
 89b805bd3201ff7170e25efc8aa4fafaa42f6891736a8777f521b90387479339 6588 
gnome-shell-pomodoro_0.20.0-2.debian.tar.xz
 2f7920c7d55761283fe41c1d0052129b81996a7963ad1c099e56836553009b0b 22418 
gnome-shell-pomodoro_0.20.0-2_amd64.buildinfo
Files:
 496b0daf49caad2a55d7d569e1a75c46 2530 gnome optional 
gnome-shell-pomodoro_0.20.0-2.dsc
 9390e344557d34bac38639c590cc8f9e 6588 gnome optional 
gnome-shell-pomodoro_0.20.0-2.debian.tar.xz
 475efc839d6d3ffd24e1114e7713d8d8 22418 gnome optional 
gnome-shell-pomodoro_0.20.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmHKJlUACgkQkWT6HRe9
XTa37A//WriWs0e2gxbBYFb4PZ7ROwy1onzelklcflXRF5sIkEhI5/6fTrVsTrG0
g7HXCnU6yXby4HxATUJaAS8p1N75CCSrWhqTftizdu5f1qJ3uLT5KpBkgOIYOlMC
I/sZ2pNq2izEQgV9yyLyTXcgNIlPiTjE4Om7T8OzAx9QiRmiY5XM7JQExGgcvXic
zsuNWl8KGvbp8qtanKHe91w9DLKlEG7YHoT/ubW1uRzw4g86nBFc201GfPgaMjfx
g4G4vzPTj5cNou/0EDxkLqSwving8n0ragHgrJoTQmagidaWp0Q5ob2GWfXSrWwg
RSdbnSPpWMzxgPB9bJSb9RKZ3gpVd4if8VMgiGLFJDi1tBboRs6HUUJvRgzLHJ3e
yBNTmCtvYBXp7LtNd8xa2EvRQcfeErhiUBtDjRQPFuThRENsJYR5vEka/hZX/RTV
H6HPuoMReODJ/Ooy7UWFPC3RYiiZPajOMRgHqxJyIbJ8QhIaL+sbPpvGGIeAzUr1

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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 20:53:38 +
with message-id 
and subject line Bug#999247: fixed in makepatch 2.03-2
has caused the Debian Bug report #999247,
regarding makepatch: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: makepatch
Source-Version: 2.03-2
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated makepatch 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: Mon, 27 Dec 2021 22:14:29 +0200
Source: makepatch
Architecture: source
Version: 2.03-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 999247
Changes:
 makepatch (2.03-2) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #862648)
   * debian/rules: Add build-{arch,indep}. (Closes: #999247)
Checksums-Sha1:
 c75ab1438d91e8ddcb4647a7824fe66c8948b5fb 1686 makepatch_2.03-2.dsc
 9e093d124428752aa11813f1fc0cb49b0a9ffdd2 3719 makepatch_2.03-2.diff.gz
Checksums-Sha256:
 f5ef4fb794833bfbfcf1c587c7b7e9385a274f682a5844d610dbfd806463aa21 1686 
makepatch_2.03-2.dsc
 cd91a8280b299f49e70b3056a6a9d3007997226a4df7f7c67136c7c4f4e353cb 3719 
makepatch_2.03-2.diff.gz
Files:
 239bb22627b2ad43a05cf97a2cef6f7b 1686 utils optional makepatch_2.03-2.dsc
 83e34ec77c61d1385ccd9fa1e4bf63cd 3719 utils optional makepatch_2.03-2.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKHzMACgkQiNJCh6LY
mLECKxAArn0jkPswfceMBe8PBdXuSemdTQ0MgvaHQj2hH2oZuVxMnKmD00FruzjU
eeBcNhVBhuM27UH0e2GRws9D8W0GHTB41bF4gF4kILAl8nZfy7yGjSiAqlhCuLhX
gA6hvHy+MKvNvjhJvqBb8vH7RoaGAaJ7QLAG5CLHNy8jrItgMeFHyrsq8yLB8tRx
eS2DSZp0J0zu/T1sRSMBLQapsacpBP0TpD9/PlgX7L0Daeky73Bq27ghIrJZOOMg
v4OSVGf8BG3sbumLG2rgK5niyU/ZRCdKkyLqt2y9Wn/CNlkGLyujURYo3fWgmFRa
P7uddruarIcjEjKLVoLAJKadUQMUIc0jJdkyO7fSt4tacXxXIzcandDQNNLD7K1k
pNDbfTgh3W8OKfRgMusiUqxJUxug2t7cbe6BqbgMeauYB37BCHh0PN/CTqcIvrOu
EWPpAE3fHHaDtpSzIGDv415V/wNeFfgQ9ukanQU38yZ31L1AFwWknRXOMvqvZZXz
ouOiVbvR0NgENBaX1VghqBryI5IJ6VuMgIs/epNpsuLJcwJlQtPshD7+nr3p7zTq
/C09IR497+TRTDPG1XCTZLnfhBIDdt22V52KZYLTXVk7NI3MYSHl4TGc2ApbRVc+
5k6oNtyY2IcMXwvkR/VYL6PRY6ndYrV1Hq+ybQYOhx0CCdKqp+Y=
=JL/z
-END PGP SIGNATURE End Message ---


Bug#996078: marked as done (gnome-shell-pomodoro: tighten dependency on g-shell)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 20:47:48 +
with message-id <61ca2674d3f0_3e32ab9fe5765c444...@godard.mail>
and subject line Bug#996078 fixed in gnome-shell-pomodoro
has caused the Debian Bug report #996078,
regarding gnome-shell-pomodoro: tighten dependency on g-shell
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.)


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

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

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

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

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

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

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Hello,

Bug #996078 in gnome-shell-pomodoro reported by you has been fixed in the Git 
repository.
You can see the commit message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/gnome-shell-pomodoro/-/commit/ade93d2b9524ac50fb50d37bba324ba7a00d3d37


Tighten dependency on gnome-shell (Closes: #996078)

Bump S-V to 4.6.0 -- no changes required.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/996078--- End Message ---


Bug#994402: marked as done (binutils-source: Re-enable building of ARC cross-binutils)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 20:22:14 +
with message-id 

and subject line 
has caused the Debian Bug report #994402,
regarding binutils-source: Re-enable building of ARC cross-binutils
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.)


-- 
994402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: binutils-source
Version: 2.37-6
Severity: normal
Tags: patch

Dear Maintainer,

W/o newer dpkg we cannot correctly build cross-Binutils for ARC
as target architecture won't be recognized. And so we disabled it
with [1]. And once new dpkg gets uploaded we're ready to re-enable this one
with a patch below.

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

-Alexey

--->8---
--- a/debian/rules
+++ b/debian/rules
@@ -116,14 +116,11 @@
 install_binary = install -m 755 -s --strip-program="$(STRIP)"
 
 NATIVE_ARCHS ?= amd64 i386 arm64 armhf armel ppc64el s390x
-NATIVE_ARCHS += alpha hppa ia64 m68k powerpc ppc64 \
+NATIVE_ARCHS += alpha arc hppa ia64 m68k powerpc ppc64 \
riscv64 sh4 sparc64 x32
 NATIVE_ARCHS += hurd-i386 kfreebsd-amd64 kfreebsd-i386
 #NATIVE_ARCHS += nios2 or1k s390 sparc
 
-# Once dpkg with ARC support is uploaded, add "arc" as well
-#NATIVE_ARCHS += arc
-
 # don't generate the control file entries for native packages which are never
 # built. Only valid for Ubuntu. The autopkg testers get confused otherwise
 ifneq ($(distribution)-$(CROSS_ARCHS),Ubuntu-)
@@ -140,12 +137,10 @@
 # DEB_HOST_ARCH is filtered-out later anyway, do not test here.
 CROSS_ARCHS ?= amd64 i386 x32 \
s390x ppc64el arm64 armhf armel \
-   alpha hppa m68k \
+   alpha arc hppa m68k \
powerpc ppc64 sh4 sparc64 \
ia64 riscv64 \
kfreebsd-amd64 kfreebsd-i386 hurd-i386
-# Once dpkg with ARC support is uploaded, add "arc" as well
-#  arc
   else ifeq ($(DEB_HOST_ARCH),arm64)
 CROSS_ARCHS ?= amd64 armel armhf i386 ppc64el riscv64 s390x x32
   else ifeq ($(DEB_HOST_ARCH),ppc64)
--->8---


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

Kernel: Linux 5.4.72-microsoft-standard-WSL2 (SMP w/12 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages binutils-source depends on:
ii  make4.2.1-1.2
ii  python3 3.8.2-0ubuntu2
ii  texinfo 6.7.0.dfsg.2-5
ii  zlib1g-dev  1:1.2.11.dfsg-2ubuntu1.2

binutils-source recommends no packages.

binutils-source suggests no packages.
--- End Message ---
--- Begin Message ---
Since initial ARC support suggested in #994190 was entirely reverted with 
2.37-7, this one no longer makes any sense.--- End Message ---


Bug#994287: marked as done (binutils-source: Disable building cross-binutils for ARC until dpkg upload)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 20:20:23 +
with message-id 

and subject line 
has caused the Debian Bug report #994287,
regarding binutils-source: Disable building cross-binutils for ARC until dpkg 
upload
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.)


-- 
994287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: binutils-source
Version: 2.37-6
Severity: normal
Tags: patch

Dear Maintainer,

ARC support introduced via [1] enabled builds of cross-binutils
for ARC, but with older dpkg which doesn't know ARC architecture
it leads to buold failures see [2].

Let's disable building of cross-binutils for ARC until dpkg with
so much needed fix [3], [4] gets uploaded.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994190
[2] https://buildd.debian.org/status/logs.php?pkg=binutils=2.37-6=all
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980963
[4] 
https://salsa.debian.org/dpkg-team/dpkg/-/commit/0d134cdcb0dcc6b21fa7926964c1426a5821181d

-Alexey

>8
--- a/debian/rules
+++ b/debian/rules
@@ -119,7 +119,10 @@
 NATIVE_ARCHS += alpha hppa ia64 m68k powerpc ppc64 \
riscv64 sh4 sparc64 x32
 NATIVE_ARCHS += hurd-i386 kfreebsd-amd64 kfreebsd-i386
-#NATIVE_ARCHS += arc nios2 or1k s390 sparc
+#NATIVE_ARCHS += nios2 or1k s390 sparc
+
+# Once dpkg with ARC support is uploaded, add "arc" as well
+#NATIVE_ARCHS += arc
 
 # don't generate the control file entries for native packages which are never
 # built. Only valid for Ubuntu. The autopkg testers get confused otherwise
@@ -137,10 +140,12 @@
 # DEB_HOST_ARCH is filtered-out later anyway, do not test here.
 CROSS_ARCHS ?= amd64 i386 x32 \
s390x ppc64el arm64 armhf armel \
-   alpha arc hppa m68k \
+   alpha hppa m68k \
powerpc ppc64 sh4 sparc64 \
ia64 riscv64 \
kfreebsd-amd64 kfreebsd-i386 hurd-i386
+# Once dpkg with ARC support is uploaded, add "arc" as well
+#  arc
   else ifeq ($(DEB_HOST_ARCH),arm64)
 CROSS_ARCHS ?= amd64 armel armhf i386 ppc64el riscv64 s390x x32
   else ifeq ($(DEB_HOST_ARCH),ppc64)
>8

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

Kernel: Linux 5.4.72-microsoft-standard-WSL2 (SMP w/12 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages binutils-source depends on:
ii  make4.2.1-1.2
ii  python3 3.8.2-0ubuntu2
ii  texinfo 6.7.0.dfsg.2-5
ii  zlib1g-dev  1:1.2.11.dfsg-2ubuntu1.2

binutils-source recommends no packages.

binutils-source suggests no packages.
--- End Message ---
--- Begin Message ---
This is no longer needed as all the changes from #994190 were reverted in 
2.37-7.--- End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 20:24:55 +
with message-id 
and subject line Bug#965630: fixed in libcobra-java 0.98.4-6
has caused the Debian Bug report #965630,
regarding libcobra-java: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

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

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 27 Dec 2021 11:43:31 -0800
Source: libcobra-java
Architecture: source
Version: 0.98.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: tony mancill 
Closes: 965630
Changes:
 libcobra-java (0.98.4-6) unstable; urgency=medium
 .
   * Team upload.
   * Update to debhelper compat 9 (Closes: #965630)
   * Import upstream branch and create pristine-tar to build with gbp.
Checksums-Sha1:
 c54533c3606488e50dab2ac50fb1c06bffb3e0e7 2095 libcobra-java_0.98.4-6.dsc
 e3cb613572c9c2b7755957cc29d95f4ce7775681 6424 
libcobra-java_0.98.4-6.debian.tar.xz
 9926e88a0ce50dcda87e2eaed9477418854d32cc 8504 
libcobra-java_0.98.4-6_amd64.buildinfo
Checksums-Sha256:
 abbaeb9ae15b90e78287f5c4b46d4869c2a68245827d7db61b7af2c4635a69c6 2095 
libcobra-java_0.98.4-6.dsc
 a2aecb596719a5274ad2550f646a423fb8008344a94e42b68220f994e63aed73 6424 
libcobra-java_0.98.4-6.debian.tar.xz
 f0bc0855bdab024202e94e74f46eccca30aa4f02abfd5aa5546af07cfe694a1e 8504 
libcobra-java_0.98.4-6_amd64.buildinfo
Files:
 1ba4673235126d1e1da94b2b3e45de8f 2095 java optional libcobra-java_0.98.4-6.dsc
 f1397253b8cb8ca74fc3937f4227839b 6424 java optional 
libcobra-java_0.98.4-6.debian.tar.xz
 4ac8d7024920b3429de78f6df01be76e 8504 java optional 
libcobra-java_0.98.4-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmHKHLEUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpapXA/9H2G6r4rExMjzbasoqK8Cs/yXzOOw
83M6VoZX4nmk+jgctnSM7I5ha20p5NRpKFIiwL6JaI7G5UQ5Anx6Dkul65GNOUhr
43D1hkxGsoecXtUzXidTBxcjxFo87Jvup4aR57sknlomsWOPcF0/CY0b02i7T0/6
jJRl5xDyCnkMz58lMhMOHP2LTCku7dEaLUNW6SxrIxIJxQIa7pR4IDewcr5vppKE
kietsWAGoIN6j8oCsEWn4uJPimlmSoDaI+J9Lp9U+TDlIJpHJcmxETZVeYsN2iTb
Qi9vPo4bsnP1Z2jGVpVNc78qZjRJCCVZlsEpKDmVSxnXgtmvG1K3Y4DBTpBvKD79
3UnfiCP0IPEdG4DH9A7TooU3T7OurC70YqlSmf1vyX0CxxmbV+/ShbxvJ6yPcSZX
89F/KFbXZF11ghfB/c+R+SqGUpsqes82HG4RkBUSTNXu781Kr8F9YQdZA2w+EjO1
B8hA9n9rwUzbTF/wNPSD56vCyczJQv6jUlgkgjXZduL/U7+JydA2W7Hi21X6NcFd
krrn4txUnxJJab230/xD0l4UbC0xjn3FR6H0RXFEpC7T1n8pugBgPRmGDN5Z+VxL

Processed: closing 1000844

2021-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # fixed already in 3.4.3 upstream
> close 1000844 3.4.3+ds1-1
Bug #1000844 {Done: Reinhard Tartler } [src:libpod] 
libpod: CVE-2021-4024: podman machine spawns gvproxy with port binded to all IPs
Marked as fixed in versions libpod/3.4.3+ds1-1.
Bug #1000844 {Done: Reinhard Tartler } [src:libpod] 
libpod: CVE-2021-4024: podman machine spawns gvproxy with port binded to all IPs
Bug 1000844 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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



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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:49:45 +
with message-id 
and subject line Bug#999128: fixed in memtest86 4.3.7-4
has caused the Debian Bug report #999128,
regarding memtest86: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: memtest86
Source-Version: 4.3.7-4
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated memtest86 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: Mon, 27 Dec 2021 21:27:25 +0200
Source: memtest86
Architecture: source
Version: 4.3.7-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 965718 999128
Changes:
 memtest86 (4.3.7-4) unstable; urgency=low
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #969192)
   * debian/compat: 5 -> 7. (Closes: #965718)
   * debian/rules: Add build-{arch,indep}. (Closes: #999128)
Checksums-Sha1:
 1dd0efd75b7ed29f72381b6e3ba3870705165014 1844 memtest86_4.3.7-4.dsc
 bd36fd738f95a2d939a6bddc1ec7251a51b89eb4 13640 memtest86_4.3.7-4.debian.tar.xz
Checksums-Sha256:
 19eeb56850c8e575fd43475b9989fff3dc7f58669334890362be14208402c473 1844 
memtest86_4.3.7-4.dsc
 a472976b4af7dd4304e2bea58f30fb924c37a23174b999ed86a661251c8b4e0c 13640 
memtest86_4.3.7-4.debian.tar.xz
Files:
 86e4d0c05ac44193942d8b1f96226155 1844 misc optional memtest86_4.3.7-4.dsc
 34814ca66ebaa669965d1c0737944e55 13640 misc optional 
memtest86_4.3.7-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKFKAACgkQiNJCh6LY
mLEd8Q/+JXOXIGB/PWnc2zcavgtaFp/Apzfl9rL/kZ/zq3aHW+QLO2duyAxeR0Xb
IyWL5XEcavALTq6H9T9ssDmBjQ4ZAiq3ZpkxWDZ9XHmhSXbnTfGaSqd6uv1v7DBU
yRpm7rwtrVnztZN/vM7Moq396BZHGiz8R7zuC5RlvFE0L2s9bTOOAaOcGO6NAP5c
jWWbG/8+QiI3QsLbd1LcqH8n0/NlerOZPgO7zKBVFA+doRMaQZKTjlxQ0xagONhV
tO61RLAmnat3vijyHvXjVjtv8Qsw1FePxMZLXtZMs9iuaxLIJgAc7iDI5Fem4M4o
C/rdJZzZFXHR9qqh31NgYJ0espabSg5qvUDYi1QNhqep+F1R9RQ67J6Pay2QzfSw
kLWyP5v+8JJhiOFL5+vYNbH+Zal0USZKezvQaV7P9mzldFmiXRgIRq7q5VMCbSMX
bGjZ9SJgro9tUwsIlBsL6RCmAsS4FOT83THIrqApSW11KfzWbruXxUaFZA3qFJGa
UYerFMo/IPR7GDqrkyWsRlOmEy/hCrRNtD44bYWxwW6kapFU8p4NVvgJi0K98O90
1VjqP2fAiqWxoyM9PjJspIcxN9Jp7NBwuVA1InEHllUhIMWrCCEU33w5BWRNr03j
YkeCL0Mn+R8ear8Q9j6bKX2Df+BBHE0AT851JmOBKzYETC0HY0A=
=qUy9
-END PGP SIGNATURE End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:49:45 +
with message-id 
and subject line Bug#965718: fixed in memtest86 4.3.7-4
has caused the Debian Bug report #965718,
regarding memtest86: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: memtest86
Source-Version: 4.3.7-4
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated memtest86 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: Mon, 27 Dec 2021 21:27:25 +0200
Source: memtest86
Architecture: source
Version: 4.3.7-4
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 965718 999128
Changes:
 memtest86 (4.3.7-4) unstable; urgency=low
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #969192)
   * debian/compat: 5 -> 7. (Closes: #965718)
   * debian/rules: Add build-{arch,indep}. (Closes: #999128)
Checksums-Sha1:
 1dd0efd75b7ed29f72381b6e3ba3870705165014 1844 memtest86_4.3.7-4.dsc
 bd36fd738f95a2d939a6bddc1ec7251a51b89eb4 13640 memtest86_4.3.7-4.debian.tar.xz
Checksums-Sha256:
 19eeb56850c8e575fd43475b9989fff3dc7f58669334890362be14208402c473 1844 
memtest86_4.3.7-4.dsc
 a472976b4af7dd4304e2bea58f30fb924c37a23174b999ed86a661251c8b4e0c 13640 
memtest86_4.3.7-4.debian.tar.xz
Files:
 86e4d0c05ac44193942d8b1f96226155 1844 misc optional memtest86_4.3.7-4.dsc
 34814ca66ebaa669965d1c0737944e55 13640 misc optional 
memtest86_4.3.7-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKFKAACgkQiNJCh6LY
mLEd8Q/+JXOXIGB/PWnc2zcavgtaFp/Apzfl9rL/kZ/zq3aHW+QLO2duyAxeR0Xb
IyWL5XEcavALTq6H9T9ssDmBjQ4ZAiq3ZpkxWDZ9XHmhSXbnTfGaSqd6uv1v7DBU
yRpm7rwtrVnztZN/vM7Moq396BZHGiz8R7zuC5RlvFE0L2s9bTOOAaOcGO6NAP5c
jWWbG/8+QiI3QsLbd1LcqH8n0/NlerOZPgO7zKBVFA+doRMaQZKTjlxQ0xagONhV
tO61RLAmnat3vijyHvXjVjtv8Qsw1FePxMZLXtZMs9iuaxLIJgAc7iDI5Fem4M4o
C/rdJZzZFXHR9qqh31NgYJ0espabSg5qvUDYi1QNhqep+F1R9RQ67J6Pay2QzfSw
kLWyP5v+8JJhiOFL5+vYNbH+Zal0USZKezvQaV7P9mzldFmiXRgIRq7q5VMCbSMX
bGjZ9SJgro9tUwsIlBsL6RCmAsS4FOT83THIrqApSW11KfzWbruXxUaFZA3qFJGa
UYerFMo/IPR7GDqrkyWsRlOmEy/hCrRNtD44bYWxwW6kapFU8p4NVvgJi0K98O90
1VjqP2fAiqWxoyM9PjJspIcxN9Jp7NBwuVA1InEHllUhIMWrCCEU33w5BWRNr03j
YkeCL0Mn+R8ear8Q9j6bKX2Df+BBHE0AT851JmOBKzYETC0HY0A=
=qUy9
-END PGP SIGNATURE End Message ---


Bug#902647: marked as done (maelstrom FTCBFS: configures for the build architecture)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:34:19 +
with message-id 
and subject line Bug#902647: fixed in maelstrom 1.4.3-L3.0.6+main-10
has caused the Debian Bug report #902647,
regarding maelstrom FTCBFS: configures for the build architecture
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.)


-- 
902647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maelstrom
Version: 1.4.3-L3.0.6+main-9
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

maelstrom fails to cross build from source, because it configures for
the build architecture. I'd normally suggest using dh_auto_configure
here, but dh_auto_configure passes --runstatedir and maelstrom's
./configure doesn't like that. Thus the attached patch adds the relevant
--build and --host flags explicitly. Please consider applying it.

Helmut
diff --minimal -Nru maelstrom-1.4.3-L3.0.6+main/debian/changelog 
maelstrom-1.4.3-L3.0.6+main/debian/changelog
--- maelstrom-1.4.3-L3.0.6+main/debian/changelog2018-03-01 
01:04:45.0 +0100
+++ maelstrom-1.4.3-L3.0.6+main/debian/changelog2018-06-28 
23:19:50.0 +0200
@@ -1,3 +1,10 @@
+maelstrom (1.4.3-L3.0.6+main-9.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 28 Jun 2018 23:19:50 +0200
+
 maelstrom (1.4.3-L3.0.6+main-9) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru maelstrom-1.4.3-L3.0.6+main/debian/rules 
maelstrom-1.4.3-L3.0.6+main/debian/rules
--- maelstrom-1.4.3-L3.0.6+main/debian/rules2015-09-30 22:00:00.0 
+0200
+++ maelstrom-1.4.3-L3.0.6+main/debian/rules2018-06-28 23:19:50.0 
+0200
@@ -1,5 +1,7 @@
 #!/usr/bin/make -f
 
+include /usr/share/dpkg/architecture.mk
+
 TMPDIR=maelstrom
 BINDIR=debian/${TMPDIR}/usr/games
 LIBDIR=debian/${TMPDIR}/usr/lib/games/maelstrom
@@ -22,7 +24,7 @@
 build:
cp /usr/share/misc/config.guess .
cp /usr/share/misc/config.sub .
-   ./configure CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" 
CPPFLAGS="$(CPPFLAGS)" LDFLAGS="$(LDFLAGS)"
+   ./configure --build=$(DEB_BUILD_GNU_TYPE) --host=$(DEB_HOST_GNU_TYPE) 
CFLAGS="$(CFLAGS)" CXXFLAGS="$(CXXFLAGS)" CPPFLAGS="$(CPPFLAGS)" 
LDFLAGS="$(LDFLAGS)"
$(MAKE)
touch build
 
--- End Message ---
--- Begin Message ---
Source: maelstrom
Source-Version: 1.4.3-L3.0.6+main-10
Done: Pino Toscano 

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated maelstrom 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: Mon, 27 Dec 2021 18:44:20 +0100
Source: maelstrom
Architecture: source
Version: 1.4.3-L3.0.6+main-10
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Pino Toscano 
Closes: 902647
Changes:
 maelstrom (1.4.3-L3.0.6+main-10) unstable; urgency=medium
 .
   * QA upload.
   * Use the https URL in Homepage, and copyright.
   * Drop removal of executables not shipped/installed anymore.
   * Remove trailing whitespaces in changelog.
   * Remove leftovers of the Debian menu.
   * Rename debian/maelstrom.6 to debian/Maelstrom.6, so it can be installed
 directly with dh_installman.
   * Remove migration of the scores from the old location
 /var/lib/games/maelstrom/Maelstrom-Scores, as it was done long ago.
   * Add a watch file.
   * Make sure that autoreconf can be run properly:
 - add a configure.patch to add the custom changes to configure.in;
   this also includes a couple of autotools modernizations needed
   - pass to ./configure the right parameters to change the directories we
 need, rather than hardcoding them as local patch
 - add destdir.patch to make sure $DESTDIR is respected
 - add install-hook.diff to rename the custom 'install' target as extra
   bits to the standard one, which otherwise overrides the custom one
 - drop 

Bug#1002587: marked as done (python3-sage: Depends on unavailable package)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:10:17 +
with message-id 
and subject line Re: Bug#1002587: python3-sage: Depends on unavailable package
has caused the Debian Bug report #1002587,
regarding python3-sage: Depends on unavailable package
to be marked as done.

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

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


-- 
1002587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sage
Version: 9.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I was trying for a few weeks to upgrade some packages and it couldn't
do that due to sage dependencies. Now it has a new version available
(9.4-1), which depends on python3-sage (9.4-1) that depends itself on
python3-memory-allocator that shows up as unavailable here.

Any advice?

Thanks in advance and best regards,
Alexandre

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-sage depends on:
ii  bc1.07.1-3+b1
ii  binutils  2.37-7
ii  bzip2 1.0.8-5
ii  ca-certificates   20210119
pn  cliquer   
ii  cmake 3.22.1-1+b1
ii  curl  7.79.1-2
ii  cython3   0.29.24-1+b1
ii  ecl   21.2.1+ds-1
ii  eclib-tools   20210625-1+b2
ii  fflas-ffpack  2.5.0-1
ii  flintqs   1:1.0-3+b1
ii  gap-atlasrep  2.1.0-3
ii  gap-dev   4.11.1-1
ii  gap-online-help   4.11.1-1
ii  gap-primgrp   3.4.0-1
ii  gap-smallgrp  1.4.1-2
ii  gap-table-of-marks1.2.9-1
ii  gap-transgrp  2.0.6-2
ii  gfan  0.6.2-6
pn  gfortran  
ii  glpk-utils5.0-1
ii  gmp-ecm   7.0.4+ds-6
ii  jmol  14.32.3+dfsg1-1
ii  lcalc 2.0.4-2
ii  libatlas3-base [libblas.so.3] 3.10.3-11
ii  libatomic-ops-dev 7.6.12-1
ii  libblas3 [libblas.so.3]   3.10.0-2
pn  libboost-dev  
pn  libbraiding-dev   
ii  libbraiding0  1.0-1+b1
pn  libbrial-dev  
pn  libbrial-groebner-dev 
ii  libbrial-groebner31.2.10-1+b2
ii  libbrial3 1.2.10-1+b2
pn  libbz2-dev
ii  libc6 2.33-1
pn  libcdd-dev
ii  libcdd-tools  094l-2
pn  libcliquer-dev
ii  libcliquer1   1.21-3
pn  libcurl4-openssl-dev  
pn  libec-dev 
ii  libec820210625-1+b2
pn  libecm-dev
ii  libecm1   7.0.4+ds-6
ii  libffi-dev3.4.2-3
ii  libflint-2.8.42.8.4-2
pn  libflint-arb-dev  
ii  libflint-arb2 1:2.21.1-2
pn  libflint-dev  
pn  libfplll-dev  
ii  libfreetype6-dev  2.11.0+dfsg-1
ii  libgap-dev4.11.1-1

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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:07:08 +
with message-id 
and subject line Bug#998976: fixed in midge 0.2.41-3
has caused the Debian Bug report #998976,
regarding midge: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: midge
Source-Version: 0.2.41-3
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
midge, 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.
Adrian Bunk  (supplier of updated midge 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: Mon, 27 Dec 2021 20:30:06 +0200
Source: midge
Architecture: source
Version: 0.2.41-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 998976
Changes:
 midge (0.2.41-3) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (see #840288)
   * debian/rules: Add build-{arch,indep}. (Closes: #998976)
Checksums-Sha1:
 18339ea97963f0d5e256a8d7baa5ee81fbf156f6 1666 midge_0.2.41-3.dsc
 02c805238c9d62848a7b4efc4dde77a2763f9394 2406 midge_0.2.41-3.diff.gz
Checksums-Sha256:
 98601237080ec4aaf7e3fdaf2cde9f47d61215fe227ad366cc57300457255ef4 1666 
midge_0.2.41-3.dsc
 81a74585fb0d08a3d9747c1869ba4b9e9469ebd1d439f497c4abdf2d035d5248 2406 
midge_0.2.41-3.diff.gz
Files:
 4b4a2fe85bc1e6588d2575205b7bd27a 1666 sound optional midge_0.2.41-3.dsc
 6c8fcf89af5cb7408f6dd49519045d08 2406 sound optional midge_0.2.41-3.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHKCuYACgkQiNJCh6LY
mLECcRAArFP1tb+F6dUUgX2DhverQzacccDD3QDM71CSWCTvbX/wfSvi6ovSIK3m
VCDlwypDP6xWb+HHyS//Xw/RaqXKaiVBAK0Rdbj6b6rBZDNg5n5FI9q0fy51hdPS
lqYejlP6SnT1v+fEafP0vvQ4oIroDxF2NJP+MFcteGrwdAj8BtblclbjPxb6fa+u
3Uzf4IW/tKLnIhDkNNKRvyN8IWCZdjhfxxbtf8WybNrW4fgCfa16BGXVzAhhENew
2vzFkNnwOQewXIt3BVHPIv8ic36WOGNBG0WerG0oi0Gxr8jGUdyTCfXHfBMDS6zE
Fx/t1Ah6aULrEIUMP6DDG/3m58t+325DiUnYRHY3PnGtBS3PEJeWLNAS0KhCs7W+
rqKRiV7M1GVIakW3Pcp0RXIitZ3cP9hez+xpjDEKJ7keRAjSpX4aA/k7bBjU5rqD
R9QPKxPha+0lel6c6cJyJXYSIrxJxtakZkWIub9YT0KHXV+3GXrSp8Tl1BupDLNC
o5gHnZrIWdzkdq9YPf6HYORKa1fGGPQkWFN2W6DB4Y6n4xxbGDzB3eMIvjbHCRLO
rSQh9QUwnpwcZkeQA5F1nwpIxT6YuhlIJPUGpLygRUyDiwL91Y7NI8u8lWOK2Kmj
6+C7IV2AwCZ4Ap15u3Qxjxep9oGqc8HwNfZqnnA15Ab++nxOGUc=
=wWXw
-END PGP SIGNATURE End Message ---


Bug#1000890: marked as done (libwxbase3.0-0v5: wxStandardPaths::GetDocumentsDir should not return a quoted string)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:07:15 +
with message-id 
and subject line Bug#1000890: fixed in wxwidgets3.0 3.0.5.1+dfsg-3
has caused the Debian Bug report #1000890,
regarding libwxbase3.0-0v5: wxStandardPaths::GetDocumentsDir should not return 
a quoted string
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.)


-- 
1000890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwxbase3.0-0v5
Version: 3.0.5.1+dfsg-2
Severity: normal
Tags: patch

wxStandardPaths::GetDocumentsDir returns a string with quotes at the
start and end. It should not do this. In
https://github.com/wxWidgets/wxWidgets/commit/a0fb80808771dfb27fcb452284a2cfdc9a9bf783
the code was changed to just remove all quotes (extract from the commit):

--- a/src/unix/stdpaths.cpp
+++ b/src/unix/stdpaths.cpp
@@ -260,6 +260,8 @@ wxString wxStandardPaths::GetDocumentsDir() const
 value.Replace(wxT("$HOME"), homeDir);
 value.Trim(true);
 value.Trim(false);
+// Remove quotes
+value.Replace("\"", "", true /* replace all */);
 if (!value.IsEmpty() && wxDirExists(value))
 return value;
 else

While I don't really agree with _how_ the quotes are removed (the string
should be unquoted like wxFileConfig does with FilterInValue instead of
just stripping all of the quotes), I would like this part of the
upstream commit to be backported to the current Debian package so that
the returned value is useable (and I don't want to wait for a new stable
release of wxWidgets).

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'stable-updates'), (500, 
'stable-security')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 5.14.0-2-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 libwxbase3.0-0v5 depends on:
ii  libc6   2.32-4
ii  libexpat1   2.4.1-3
ii  libgcc-s1   11.2.0-10
ii  libstdc++6  11.2.0-10
ii  zlib1g  1:1.2.11.dfsg-2

libwxbase3.0-0v5 recommends no packages.

libwxbase3.0-0v5 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: wxwidgets3.0
Source-Version: 3.0.5.1+dfsg-3
Done: Scott Talbert 

We believe that the bug you reported is fixed in the latest version of
wxwidgets3.0, 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.
Scott Talbert  (supplier of updated wxwidgets3.0 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: Mon, 27 Dec 2021 13:13:30 -0500
Source: wxwidgets3.0
Architecture: source
Version: 3.0.5.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: wxWidgets Maintainers 
Changed-By: Scott Talbert 
Closes: 1000890
Changes:
 wxwidgets3.0 (3.0.5.1+dfsg-3) unstable; urgency=medium
 .
   * Fix wxStandardPaths::GetDocumentsDir to not return a quoted string
 (Closes: #1000890)
   * Update Standards-Version to 4.6.0 (no changes needed)
Checksums-Sha1:
 8997f52fb6d486c53c7df84396501c4c0a6fdb17 3239 wxwidgets3.0_3.0.5.1+dfsg-3.dsc
 f34016cc910be2240209b08ed501d0cd6bf7d95c 41336 
wxwidgets3.0_3.0.5.1+dfsg-3.debian.tar.xz
 65db9d6b0d3204c5bcd37a889a311bb4eb8f4d9f 22865 
wxwidgets3.0_3.0.5.1+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 efaa4b378fe0eeef32b95de208b279e58a257b3edca2afbc429a8b238f46cf08 3239 
wxwidgets3.0_3.0.5.1+dfsg-3.dsc
 f103935c33ca065a1cb4d53f153b7862cd91ba27d53ed727ba7a84dcdf77e13a 41336 
wxwidgets3.0_3.0.5.1+dfsg-3.debian.tar.xz
 7444bfc83a662edf2e8f3dd4af94790d3c80e7c8363df3abc3095a0270661f08 22865 
wxwidgets3.0_3.0.5.1+dfsg-3_amd64.buildinfo
Files:
 4266ba2a0a3f6e19742d6e94d80885cf 3239 libs optional 
wxwidgets3.0_3.0.5.1+dfsg-3.dsc
 

Bug#992286: marked as done (libguestfs0: Please move from exfat-fuse and exfat-utils to exfatprogs)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:00:17 +
with message-id 
and subject line Bug#992286: fixed in libguestfs 1:1.46.2-2
has caused the Debian Bug report #992286,
regarding libguestfs0: Please move from exfat-fuse and exfat-utils to exfatprogs
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.)


-- 
992286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libguestfs0
Version: 1:1.44.1-1
Severity: normal

Hi,
with the release of bullseye we've the in kernel exFAT driver available.
If possible please remove the dependency on exfat-fuse and change from
exfat-utils to exfatprogs for the filesystem utilities. That would enable
us to drop the fuse driver soon.

If you make extensive use of special parameters of the filesystem utilities
there might be changes required. exfatprogs is a codebase created by Samsung 
while
exfat-utils was a completely independend implementation by another developer.

Regards,
Sven

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libguestfs0 depends on:
ii  acl  2.2.53-10
ii  attr 1:2.4.48-6
ii  binutils 2.37-4
ii  bsdextrautils2.36.1-8
pn  btrfs-progs  
ii  bzip21.0.8-4
ii  cpio 2.13+dfsg-6
ii  cryptsetup-bin   2:2.3.5-1
ii  curl 7.74.0-1.3+b1
ii  dash 0.5.11+git20210120+802ebd4-1
pn  db-util  
ii  debootstrap  1.0.123
ii  diffutils1:3.7-5
ii  dosfstools   4.2-1
ii  e2fsprogs1.46.2-2
ii  exfat-fuse   1.3.0-2
pn  exfat-utils  
pn  extlinux 
pn  f2fs-tools   
ii  fdisk2.36.1-8
ii  file 1:5.39-3
ii  gawk 1:5.1.0-1
pn  gdisk
ii  genisoimage  9:1.1.11-3.2
ii  grub2-common 2.04-20
pn  icoutils 
ii  iproute2 5.13.0-2
ii  isc-dhcp-client  4.4.1-2.3
ii  kmod 28-1
pn  kpartx   
pn  ldmtool  
ii  less 551-2
ii  libacl1  2.2.53-10
pn  libaugeas0   
ii  libc62.31-13
ii  libcap2  1:2.44-1
ii  libfuse2 2.9.9-5
pn  libhivex0
ii  libjansson4  2.13.1-1.1
ii  libpcre3 2:8.39-13
ii  libselinux1  3.1-3
ii  libsystemd0  247.9-1
ii  libtirpc31.3.1-1
ii  libtsk19 4.10.1+dfsg-1
pn  libvirt0 
ii  libxml2  2.9.10+dfsg-6.7
pn  libyara4 
pn  lsscsi   
ii  lvm2 2.03.11-2.1
ii  lzop 1.04-2
pn  mdadm
pn  mtools   
ii  netpbm   2:10.0-15.4
pn  ntfs-3g  
ii  openssh-client   1:8.4p1-5
pn  osinfo-db
pn  parted   
ii  pciutils 1:3.7.0-5
ii  procps   2:3.3.17-5
ii  psmisc   23.4-2
pn  qemu-system-x86  
ii  qemu-utils   1:5.2+dfsg-11
pn  scrub
ii  sleuthkit4.10.1+dfsg-1
ii  squashfs-tools   1:4.4-2
pn  supermin 
pn  syslinux 
ii  systemd-sysv 247.9-1
ii  udev 247.9-1
ii  util-linux   2.36.1-8
ii  uuid-runtime 2.36.1-8
ii  xz-utils 5.2.5-2
pn  zerofree 

Versions of packages libguestfs0 recommends:
pn  libguestfs-hfsplus   
pn  libguestfs-reiserfs  
pn  libguestfs-xfs   

Versions of packages libguestfs0 suggests:
pn  libguestfs-gfs2
pn  libguestfs-jfs 
pn  libguestfs-nilfs   
pn  libguestfs-rescue  
pn  libguestfs-rsync   
pn  libguestfs-zfs 
--- End Message ---
--- Begin Message ---
Source: libguestfs
Source-Version: 1:1.46.2-2
Done: Hilko Bengen 

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated libguestfs 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 

Bug#996707: marked as done (ITP: python-cattr -- Complex custom class converters for attrs Python library.)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:00:20 +
with message-id 
and subject line Bug#996707: fixed in python-cattrs 1.9.0-1
has caused the Debian Bug report #996707,
regarding ITP: python-cattr -- Complex custom class converters for attrs Python 
library.
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.)


-- 
996707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996707
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Romain Porte 
X-Debbugs-Cc: debian-de...@lists.debian.org, deb...@microjoe.org, 
debian-pyt...@lists.debian.org

* Package name: python-cattr
  Version : 1.8.0
  Upstream Author : Tin Tvrtković 
* URL : https://github.com/Tinche/cattrs
* License : MIT
  Programming Lang: Python
  Description : Complex custom class converters for attrs Python library.

cattrs is an open source Python library for structuring and
unstructuring data. cattrs works best with attrs classes, dataclasses
and the usual Python collections, but other kinds of classes are
supported by manually registering converters.

This package is introduced as a dependency for python-statmake. It will
be maintained under the umbrella of the Debian Python Team.
--- End Message ---
--- Begin Message ---
Source: python-cattrs
Source-Version: 1.9.0-1
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated python-cattrs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 26 Dec 2021 18:47:47 -0500
Source: python-cattrs
Binary: python-cattrs-doc python3-cattr
Architecture: source all
Version: 1.9.0-1
Distribution: unstable
Urgency: low
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Description:
 python-cattrs-doc - documentation for the cattrs Python library
 python3-cattr - composable complex class support for attrs and dataclasses
Closes: 996707
Changes:
 python-cattrs (1.9.0-1) unstable; urgency=low
 .
   * Initial release, autogenerated by py2dsp/2.20211223-morph; Closes: #996707
Checksums-Sha1:
 9f4096227e50a80066c069a567a2d39fb1e645b5 2422 python-cattrs_1.9.0-1.dsc
 46e8a270db56876fecbcac17fa6a968ca62c7936 102241 python-cattrs_1.9.0.orig.tar.gz
 40c058d15bfb7c1ccae0451536471e4187df263c 3436 
python-cattrs_1.9.0-1.debian.tar.xz
 268b9b207183b7945e2751acd500f81b1864cda7 89244 
python-cattrs-doc_1.9.0-1_all.deb
 1a264855d8860964bac95e71418aa451f2c323f4 9967 
python-cattrs_1.9.0-1_amd64.buildinfo
 224f1f177688ea667dda7017707779f7969923f3 24780 python3-cattr_1.9.0-1_all.deb
Checksums-Sha256:
 aae71affe9c1019d0b47584ee9f4292301308ad41a9c136fe023c0f4c45f 2422 
python-cattrs_1.9.0-1.dsc
 50b676734ada0486968299013dfc5f6fc3070c9a909dd1eef40c9ea5e971bbbd 102241 
python-cattrs_1.9.0.orig.tar.gz
 c035d0ab4becad6f263d7faccd89da7fcd78a9e98626391996e45bb05da64e16 3436 
python-cattrs_1.9.0-1.debian.tar.xz
 ccdce881528abf71eb5c055454a9df86843c7e39c545efdf3baa6602a2b0c17c 89244 
python-cattrs-doc_1.9.0-1_all.deb
 af2279a4db144e2f23660b4f20fb5d5074d59d88aa32e2964b457f653fa1 9967 
python-cattrs_1.9.0-1_amd64.buildinfo
 ff07d1f3e1ad2d8f1e9cc2d81409b589de875523bedab9d18ed263ad3b754027 24780 
python3-cattr_1.9.0-1_all.deb
Files:
 4e4b2d2c3da73172d8763ae223c5f493 2422 python optional python-cattrs_1.9.0-1.dsc
 4edd365501bccaa36ddab4704a70babf 102241 python optional 
python-cattrs_1.9.0.orig.tar.gz
 a7c8333f1f005b7ac2f3b1b9e67a8132 3436 python optional 
python-cattrs_1.9.0-1.debian.tar.xz
 5d2f9de27040467085db2a54bdc82e57 89244 doc optional 
python-cattrs-doc_1.9.0-1_all.deb
 7d1f69a232ed5bf0342fb9f4452c4cb2 9967 python optional 
python-cattrs_1.9.0-1_amd64.buildinfo
 51f9350df8b503777be29f3f0334c85d 24780 python optional 
python3-cattr_1.9.0-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmHJCdwACgkQh588mTgB
qU8QQw//RZi1WLqGJ+X4tuIWLYoK1g4JH2Mrpd7r0oK5No6vRe/CaElgHg1IU/kC
hHY2OSiMjPuAXdPIA3iowyEqfmecUSCGInR+A36EDGX/mJkibKRZpNKkA1+G9jPK

Bug#982234: marked as done (libguestfs0: please stop using cdrkit)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:00:15 +
with message-id 
and subject line Bug#982234: fixed in libguestfs 1:1.46.2-1
has caused the Debian Bug report #982234,
regarding libguestfs0: please stop using cdrkit
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.)


-- 
982234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982234
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libguestfs0
Version: 1:1.44.0-2
Severity: important

Dear libguestfs Maintainers,

your package depends on genisoimage, built from cdrkit sources.
cdrkit does not have a path forward, please switch away from it
rather soon. I'm told xorriso and libburnia are alternatives and are
alive and doing well.

It's been suggested cdrkit should not be in bookworm.

Chris
--- End Message ---
--- Begin Message ---
Source: libguestfs
Source-Version: 1:1.46.2-1
Done: Hilko Bengen 

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

Debian distribution maintenance software
pp.
Hilko Bengen  (supplier of updated libguestfs 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: Sat, 25 Dec 2021 02:17:59 +0100
Source: libguestfs
Binary: gir1.2-guestfs-1.0 golang-guestfs-dev guestfish guestfish-dbgsym 
guestfsd guestfsd-dbgsym guestmount guestmount-dbgsym libguestfs-dev 
libguestfs-gfs2 libguestfs-gobject-1.0-0 libguestfs-gobject-1.0-0-dbgsym 
libguestfs-gobject-dev libguestfs-hfsplus libguestfs-java 
libguestfs-java-dbgsym libguestfs-jfs libguestfs-nilfs libguestfs-ocaml 
libguestfs-ocaml-dbgsym libguestfs-ocaml-dev libguestfs-perl 
libguestfs-perl-dbgsym libguestfs-reiserfs libguestfs-rescue libguestfs-rsync 
libguestfs-tools libguestfs-tools-dbgsym libguestfs-xfs libguestfs-zfs 
libguestfs0 libguestfs0-dbgsym lua-guestfs lua-guestfs-dbgsym php-guestfs 
php-guestfs-dbgsym python3-guestfs python3-guestfs-dbgsym ruby-guestfs 
ruby-guestfs-dbgsym
Architecture: source amd64 all
Version: 1:1.46.2-1
Distribution: unstable
Urgency: medium
Maintainer: Hilko Bengen 
Changed-By: Hilko Bengen 
Description:
 gir1.2-guestfs-1.0 - guest disk image management system - GObject 
introspection files
 golang-guestfs-dev - guest disk image management system - Golang bindings
 guestfish  - guest filesystem shell
 guestfsd   - Daemon to access to guest virtual machine through virtio serial
 guestmount - FUSE-based mount utility for guest filesystems
 libguestfs-dev - guest disk image management system - development headers
 libguestfs-gfs2 - guest disk image management system - GFS2 support
 libguestfs-gobject-1.0-0 - guest disk image management system - GObject 
bindings
 libguestfs-gobject-dev - guest disk image management system - GObject 
development headers
 libguestfs-hfsplus - guest disk image management system - HFS+ support
 libguestfs-java - guest disk image management system - Java bindings
 libguestfs-jfs - guest disk image management system - JFS support
 libguestfs-nilfs - guest disk image management system - NILFS v2 support
 libguestfs-ocaml - guest disk image management system - OCaml bindings
 libguestfs-ocaml-dev - guest disk image management system - OCaml development 
files
 libguestfs-perl - guest disk image management system - Perl bindings
 libguestfs-reiserfs - guest disk image management system - ReiserFS support
 libguestfs-rescue - guest disk image management system - virt-rescue 
enhancements
 libguestfs-rsync - guest disk image management system - rsync support
 libguestfs-tools - guest disk image management system - tools
 libguestfs-xfs - guest disk image management system - XFS support
 libguestfs-zfs - guest disk image management system - ZFS support
 libguestfs0 - guest disk image management system - shared library
 lua-guestfs - guest disk image management system - Lua bindings
 php-guestfs - guest disk image management system - PHP bindings
 python3-guestfs - guest disk image management system - Python 3 bindings
 ruby-guestfs - guest disk image management system - Ruby bindings
Closes: 982234
Changes:
 libguestfs (1:1.46.2-1) 

Bug#927899: marked as done (ITP: cage -- A Wayland kiosk)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:00:09 +
with message-id 
and subject line Bug#927899: fixed in cage 0.1.4-1
has caused the Debian Bug report #927899,
regarding ITP: cage -- A Wayland kiosk
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.)


-- 
927899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Birger Schacht 

* Package name: cage
  Version : 0.1
  Upstream Author : Jente Hidskes
* URL : https://www.hjdskes.nl/projects/cage/
* License : MIT
  Programming Lang: C
  Description : A Wayland kiosk

Cage is a kiosk compositor for Wayland. A kiosk is a window manager (in
the X11 world) or compositor (in the Wayland world) that is designed for
a user experience wherein user interaction and activities outside the
scope of the running application are prevented. That is, a kiosk
compositor displays a single maximized application at a time and
prevents the user from interacting with anything but this application.
--- End Message ---
--- Begin Message ---
Source: cage
Source-Version: 0.1.4-1
Done: Birger Schacht 

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

Debian distribution maintenance software
pp.
Birger Schacht  (supplier of updated cage 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, 16 Dec 2021 12:19:06 +0100
Source: cage
Binary: cage cage-dbgsym
Architecture: source amd64
Version: 0.1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Sway and related packages team 
Changed-By: Birger Schacht 
Description:
 cage   - Kiosk compositor for Wayland
Closes: 927899
Changes:
 cage (0.1.4-1) unstable; urgency=medium
 .
   * Initial packaging (Closes: #927899)
Checksums-Sha1:
 822b448647a050cd779bd32af4c0fb2b66bd59c2 2018 cage_0.1.4-1.dsc
 4f34beeec15823de90fbc2a5c858ce3d17faeba0 25430 cage_0.1.4.orig.tar.gz
 948c6563616aecaff098351796602a423f76ce00 2104 cage_0.1.4-1.debian.tar.xz
 a032803f015f5d4c4747f8cf3e27238024a3ee2d 79864 cage-dbgsym_0.1.4-1_amd64.deb
 b685aac1b578c79540e254642e7adf615eab1d9a 10865 cage_0.1.4-1_amd64.buildinfo
 293c622a5aa99b42dab8f62a8a91b942057408f6 21672 cage_0.1.4-1_amd64.deb
Checksums-Sha256:
 a9b4fd9631bf7b001aca28ad62bcc1330ddd5e279031b892b510e2d0345e7d84 2018 
cage_0.1.4-1.dsc
 dfe27fb0c7d43db72d6c82f01e2736580a0791a23ba69d7b56285d08af98ad90 25430 
cage_0.1.4.orig.tar.gz
 42dabc9241257f78c1f7f815753a2c20dd488f255bb63d5200d11d55e2d06102 2104 
cage_0.1.4-1.debian.tar.xz
 e5a9a9a9fb4bf8649fb0fb80415290ed046b4530131806901cbd9558f67b5512 79864 
cage-dbgsym_0.1.4-1_amd64.deb
 49e0c72645fe4dd58af031be9b19f4f03fc486ca2672d3e5b5d4f974e2cd7b42 10865 
cage_0.1.4-1_amd64.buildinfo
 8063ef9b38398ecb4e64a4b2ea8d72d703471b15120bcd455601f46c46e8be6f 21672 
cage_0.1.4-1_amd64.deb
Files:
 a5ad6fb866d5101d2a241dd32f865503 2018 x11 optional cage_0.1.4-1.dsc
 b5874157dbded445cfe674a54805bca9 25430 x11 optional cage_0.1.4.orig.tar.gz
 31f8df551b416ccb3d583c9c179d17ab 2104 x11 optional cage_0.1.4-1.debian.tar.xz
 e76ca91f615a7acab5be0d15755abce6 79864 debug optional 
cage-dbgsym_0.1.4-1_amd64.deb
 d657897de77735ba682df83bf97cacbc 10865 x11 optional 
cage_0.1.4-1_amd64.buildinfo
 d9e9d3184608f0751728a0ff5437a7d1 21672 x11 optional cage_0.1.4-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEOvC8tnwmrEjOtOW8KgxdYPIEvbAFAmG8ad8SHGJpcmdlckBk
ZWJpYW4ub3JnAAoJECoMXWDyBL2wHz4QAMixp+QPDD5c3F9lz9hOmhmhRQ4mMHUc
OQRwoO0wt23EHjdYRmKF0AJpmJK9j9AQ9vNXgvgimqVydzBSy2lkAViAs1L0v4Yf
jy0ifUE3ExjsIpboO8YvTQ3Pi849JuPHdPXHXDMoCxaEBd12hDeu1rMsaQJ5Gope
mBDMnk0oU2a6rYgGXIKQSGlb0Jh5lEtiDb+4fma2LO8DkwgOwVnsUwXoyEnvfI7h
ZSbdGAHzw60lkZOzmHFlmNns2RyylWrjiA4WraV6lJ4iFAkdoxl+Oybtw8qIr1eo
VMOMsWoz6zH/NNG7pm87Irwb7WqProSpgUEE28603UuekumvnGSlxuctjSs+DORK
lAbkeLCKMcCZd9b7JnV0ZeqPgSvwOv5EQLZwq0UUxBmWKwzkgiUJh4eSrT3dxUq8
WS2y7W538LCb5XYF9l/H/o9KGrfE8gHyiYOILtmqnQ78bzuWqyMr/MpvXYGuyEJU
KJrCOhHHmzpYh/P+sM7U103TqmWuXFsk0HApu4qYbINVtyfb1Qu56A3x7hsMJOCq

Bug#1002042: marked as done (ITP: php-mock-integration -- integration package for PHP-Mock)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:00:19 +
with message-id 
and subject line Bug#1002042: fixed in php-mock-integration 2.1.0-1
has caused the Debian Bug report #1002042,
regarding ITP: php-mock-integration -- integration package for PHP-Mock
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.)


-- 
1002042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: James Valleroy 
X-Debbugs-Cc: debian-de...@lists.debian.org, jvalle...@mailbox.org, 
pkg-php-p...@lists.alioth.debian.org

* Package name: php-mock-integration
  Version : 2.1.0
  Upstream Author : Markus Malkusch , Michał Bundyra 

* URL : https://github.com/php-mock/php-mock-integration
* License : WTFPL
  Programming Lang: PHP
  Description : integration package for PHP-Mock

This is a support package for PHP-Mock integration into other
frameworks. It is used by integrations into PHPUnit, Mockery, and
Prophecy (phpspec).

This is a dependency for the latest release of Shaarli. Specifically,
it is required by php-mock-phpunit (ITP #1001912). It will be
maintained in php-team.
--- End Message ---
--- Begin Message ---
Source: php-mock-integration
Source-Version: 2.1.0-1
Done: James Valleroy 

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

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

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

Debian distribution maintenance software
pp.
James Valleroy  (supplier of updated 
php-mock-integration 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: Mon, 20 Dec 2021 14:49:57 -0500
Source: php-mock-integration
Binary: php-mock-integration
Architecture: source all
Version: 2.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: James Valleroy 
Description:
 php-mock-integration - integration package for PHP-Mock
Closes: 1002042
Changes:
 php-mock-integration (2.1.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1002042)
Checksums-Sha1:
 7b60ff57c38f03ae285ff1face007dd135f05cac 2179 php-mock-integration_2.1.0-1.dsc
 e4e8c5a10a871e4330705cb4c5e867f647b792a7 3852 
php-mock-integration_2.1.0.orig.tar.xz
 43f23d7a52073238d82b57297c19c16657e24f50 2476 
php-mock-integration_2.1.0-1.debian.tar.xz
 bd3a3b6243d1ef6671e55a15a9b5880657f54a38 4940 
php-mock-integration_2.1.0-1_all.deb
 a11db29e1e0c639828d756a313a56c55fd1e46d2 8002 
php-mock-integration_2.1.0-1_amd64.buildinfo
Checksums-Sha256:
 a6da309646e391749e65f83bc046dd5608f6e573348cacf104b09090539a9ed5 2179 
php-mock-integration_2.1.0-1.dsc
 3b7219e3bc85d126163eff94ac02e8396b5a3ae6178b4515fb763eaaa70d9035 3852 
php-mock-integration_2.1.0.orig.tar.xz
 bc6025d5b5caf3c549c9942ed00591a4b7be66d1922b1cf967cb365c613a0709 2476 
php-mock-integration_2.1.0-1.debian.tar.xz
 4464d06ecfad726e3d7cac88ba8d96585b1a47537b25457937c5ac6737dd04dd 4940 
php-mock-integration_2.1.0-1_all.deb
 59d9a286a78ac295f88c1f12cf30b542558e24af49c3cfe987d2094857945f7f 8002 
php-mock-integration_2.1.0-1_amd64.buildinfo
Files:
 8824ae87b58b67160144486bff916249 2179 php optional 
php-mock-integration_2.1.0-1.dsc
 14fc7e4695def62e554085177598d97e 3852 php optional 
php-mock-integration_2.1.0.orig.tar.xz
 36f71c9071aba32015e143b2af64ec19 2476 php optional 
php-mock-integration_2.1.0-1.debian.tar.xz
 ec4a8a4ddb32132e6455d7332413ff14 4940 php optional 
php-mock-integration_2.1.0-1_all.deb
 69cb7a8f427ee8498fad6632b226f05c 8002 php optional 
php-mock-integration_2.1.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmHA6EUWHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICMceD/4k/8KXKsME0j6/V2XA+vUP+sCu
TL7rVuYnawWrCJIOqAh1fxgVwaztCNBH9Q87zUwLkq4GMruwHxzlYWna+OFis+XR
9sv7Ei7exURY5VuGuuwsbKBuRjxM7JMkCc4t69vG9g/DSXDanwQ38GnGGoC8AALZ
nqLngXYbVWaXischc5PCMZ2YvOzEMHN1j2xKjZdSVNKMpFYKnec6BgHynZTSRZKT
6K/dpP7HadpYLysHTy5mbp79/R+xtV7DjHYB+0B2FtvNRJqUugrpf9w6cPLZjOqa
KKA8K3fgLaKMORibHXAix50MifRuUGQ3Z7lqT3kSfYuoMJKZBcLoUB5AamAEZVkE

Bug#1001913: marked as done (ITP: php-malkusch-lock -- mutex library for exclusive code execution)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:00:19 +
with message-id 
and subject line Bug#1001913: fixed in php-malkusch-lock 2.2+ds.1-1
has caused the Debian Bug report #1001913,
regarding ITP: php-malkusch-lock -- mutex library for exclusive code execution
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.)


-- 
1001913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001913
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: James Valleroy 
X-Debbugs-Cc: debian-de...@lists.debian.org, jvalle...@mailbox.org, 
pkg-php-p...@lists.alioth.debian.org

* Package name: php-malkusch-lock
  Version : 2.2
  Upstream Author : Willem Stuursma-Ruwen 
* URL : https://github.com/php-lock/lock
* License : WTFPL
  Programming Lang: PHP
  Description : mutex library for exclusive code execution

Lock library to provide serialized execution of PHP code. It helps
executing critical code in concurrent situations.

Choose from one of the provided implementations, or create/extend your
own. The provided implementations include: CASMutex, FlockMutex,
MemcachedMutex, PHPRedisMutex, PredisMutex, SemaphoreMutex,
TransactionalMutex, MySQLMutex, and PgAdvisoryLockMutex.

This is a dependency for the latest release of Shaarli. It will be
maintained in php-team.
--- End Message ---
--- Begin Message ---
Source: php-malkusch-lock
Source-Version: 2.2+ds.1-1
Done: James Valleroy 

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

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

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

Debian distribution maintenance software
pp.
James Valleroy  (supplier of updated php-malkusch-lock 
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, 16 Dec 2021 10:20:16 -0500
Source: php-malkusch-lock
Binary: php-malkusch-lock
Architecture: source all
Version: 2.2+ds.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: James Valleroy 
Description:
 php-malkusch-lock - mutex library for exclusive code execution
Closes: 1001913
Changes:
 php-malkusch-lock (2.2+ds.1-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1001913)
Checksums-Sha1:
 97530267c0c60b90ab612b57e3ebfcf738827cb1 2109 php-malkusch-lock_2.2+ds.1-1.dsc
 3cfafb090145fc32f68b777340423cccf377847e 24684 
php-malkusch-lock_2.2+ds.1.orig.tar.xz
 ef5a022368dadc4b7ca0556652102504981aee1c 3028 
php-malkusch-lock_2.2+ds.1-1.debian.tar.xz
 82ea29c6c2412879785ada585b5bd107a998a22f 26896 
php-malkusch-lock_2.2+ds.1-1_all.deb
 404f1f312424b9c86c38c24cd01224c23e101799 8028 
php-malkusch-lock_2.2+ds.1-1_amd64.buildinfo
Checksums-Sha256:
 961c267ca6f741736520daba58634a22ef9c69a82f15bf409840ef5e90b0f89b 2109 
php-malkusch-lock_2.2+ds.1-1.dsc
 9b73ca2b17fc36cbc856b492b874b9455f0caedd9b8570026aefc2a0bf640a45 24684 
php-malkusch-lock_2.2+ds.1.orig.tar.xz
 e58ecae6f02f24817492dd5bd75c5048eaf0e6fa9124ddbc2b53559f4419987c 3028 
php-malkusch-lock_2.2+ds.1-1.debian.tar.xz
 09c30183e65c73a8d1de4afa49e9310bc0441f3f76dc4b109bcfaedae7c13a50 26896 
php-malkusch-lock_2.2+ds.1-1_all.deb
 22a2142808e3a67d9a0bea9e73ccb1bb79c85637acd9e1a1991d75876a2180e6 8028 
php-malkusch-lock_2.2+ds.1-1_amd64.buildinfo
Files:
 e25949277b4bfa37f1c11fa12508b018 2109 php optional 
php-malkusch-lock_2.2+ds.1-1.dsc
 7fc44b8ef7429d1e6f5122514dcd176f 24684 php optional 
php-malkusch-lock_2.2+ds.1.orig.tar.xz
 8ab0515cc60bc3a75b9acf84a325df0f 3028 php optional 
php-malkusch-lock_2.2+ds.1-1.debian.tar.xz
 c2375a50f445a013dcaa9d3dbbc5d11f 26896 php optional 
php-malkusch-lock_2.2+ds.1-1_all.deb
 3f5a70259ee00d16147be0a71feddf8a 8028 php optional 
php-malkusch-lock_2.2+ds.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmHJ28kWHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICLdgD/47XqcnH0sz+UlIGQgJ3dA6HX0u
zO19KbT4wi7x89Y5zLE8x8yD7aN/9h7rC+zBsxh4DJ6Sqo6NHbw8y9HKMe3AQjFi
68/9fWcYt92qeP2kFLQjRAXjllbjElLUp7NTOXqVrUtruOWEqoCBB5LFaqaF77c4
1zORAoMBWa2VI1/hOnkpC5fnykTV2V/rxyKwIB595ILFVeWMoSVQf34ACE6GK1XP

Bug#1001912: marked as done (ITP: php-mock-phpunit -- mock built-in PHP functions with PHPUnit)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:00:19 +
with message-id 
and subject line Bug#1001912: fixed in php-mock-phpunit 2.6.0-1
has caused the Debian Bug report #1001912,
regarding ITP: php-mock-phpunit -- mock built-in PHP functions with PHPUnit
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.)


-- 
1001912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: James Valleroy 
X-Debbugs-Cc: debian-de...@lists.debian.org, jvalle...@mailbox.org, 
pkg-php-p...@lists.alioth.debian.org

* Package name: php-mock-phpunit
  Version : 2.6.0
  Upstream Author : Michał Bundyra 
* URL : https://github.com/php-mock/php-mock-phpunit
* License : WTFPL
  Programming Lang: PHP
  Description : mock built-in PHP functions with PHPUnit

Provides a trait for PHPUnit test cases to integrate with PHP-Mock, a
function mock library.

This is a dependency for the latest release of Shaarli. It will be
maintained in php-team.
--- End Message ---
--- Begin Message ---
Source: php-mock-phpunit
Source-Version: 2.6.0-1
Done: James Valleroy 

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

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

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

Debian distribution maintenance software
pp.
James Valleroy  (supplier of updated php-mock-phpunit 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Dec 2021 08:58:07 -0500
Source: php-mock-phpunit
Binary: php-mock-phpunit
Architecture: source all
Version: 2.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: James Valleroy 
Description:
 php-mock-phpunit - mock built-in PHP functions with PHPUnit
Closes: 1001912
Changes:
 php-mock-phpunit (2.6.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1001912)
Checksums-Sha1:
 fe0a1c20478a42936d873027c559128b03ba5d70 2131 php-mock-phpunit_2.6.0-1.dsc
 3b5c333f673fa98f80820837f076739c05de0010 6984 
php-mock-phpunit_2.6.0.orig.tar.xz
 2dce8ff0aab3e72f29aeb05e2c8f4e41ba5812a6 2572 
php-mock-phpunit_2.6.0-1.debian.tar.xz
 4e78c0589ba7280407866d8db3911e33dc53ba6c 7688 php-mock-phpunit_2.6.0-1_all.deb
 f1043f9299aced7993ddf2af27f7f37e0bd831cc 7966 
php-mock-phpunit_2.6.0-1_amd64.buildinfo
Checksums-Sha256:
 3d0b4132ebb55c06a92287df584811a83c10cbb688e501789bb24b146bc5aeba 2131 
php-mock-phpunit_2.6.0-1.dsc
 8d055bc9c591bb5d926fde4243d74bdec6eb66a21685c0f06de5ffef11b1d850 6984 
php-mock-phpunit_2.6.0.orig.tar.xz
 3087e3ed243fba86ba6b267e4994c90355d04bf9b21905c3522848654b7b33c2 2572 
php-mock-phpunit_2.6.0-1.debian.tar.xz
 db8f42602a478796d1dbccb51e3e3a631eb7c356ebc5912e47bcdcecb4ce31d2 7688 
php-mock-phpunit_2.6.0-1_all.deb
 ad0da4ae27c3ee297c173c4fb1ac9da1faa8142127b65d9b61124f79eb74748b 7966 
php-mock-phpunit_2.6.0-1_amd64.buildinfo
Files:
 e47688a09383ff8d0760aee47d319337 2131 php optional php-mock-phpunit_2.6.0-1.dsc
 c416f10f2a7f9df604396aa18e3114da 6984 php optional 
php-mock-phpunit_2.6.0.orig.tar.xz
 ff54d6dad767fa01b7930114d222bcdf 2572 php optional 
php-mock-phpunit_2.6.0-1.debian.tar.xz
 0ed69d92ca29ce2e2dc764bfbdd7b095 7688 php optional 
php-mock-phpunit_2.6.0-1_all.deb
 3c53d73b4caa3bd96d6c62750bcfe8e4 7966 php optional 
php-mock-phpunit_2.6.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmHB4+QWHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICESFD/0dIS8F/3dQN8kE0XSmxtNp3eGg
sGCa/Se6lsFiZqLuyYa2Rdfs2MjO4U6TuhkvLcEwnAzYiQ9fIZ6EPSFxsUHGAQEA
MGaDlZ7xMsYyMYews09ASfCb6GFhEu0FN3vb/noJwS5VzVXD2PMjarySyLIZkGBY
5Ph/PxwWj6aHVYtY4LmIhkhl7Q47UJPDax72AV1nV19Mu9IQeD3rmwWcfBLCfIxE
JbbJcEpoew2onb+TPCnzwrdGu5VfdpIy4siflQSMSgp3FB+5omsm3C9sDkmUa2M4
xwhvn7bBURyyaZJiFFRLOxG/XPKN5bu6yGTsDOhUQkg0oAoaGo9BoJhhOchpAQm2
wDiEVVdlaraHZP/pGgLBSEnn/wm9A7t2DQk8S01CmjEh3ll9PxEULKBXm5oTFSgv
ZKTUMf85qx9ZrpW1H6xLns1PsGeuo9aNoPRhiSpyLwVuNZfK9vaNu7uwLF5g+uSn
iVF0TyA5mycNIPOF5yri12wzq0VvSokGNzbVGquT6FxgXlQA1KffdoaqDy5HSCLQ
PxVG2XTcPjM0OWTtQc8ODi2u+7pG+3Wv3zbZRufS2Yu/6qso5hJ1z+W43sO6/8OB

Bug#1001909: marked as done (ITP: php-mock -- mock built-in PHP functions)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:00:19 +
with message-id 
and subject line Bug#1001909: fixed in php-mock 2.3.0-1
has caused the Debian Bug report #1001909,
regarding ITP: php-mock -- mock built-in PHP functions
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.)


-- 
1001909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: James Valleroy 
X-Debbugs-Cc: debian-de...@lists.debian.org, jvalle...@mailbox.org, 
pkg-php-p...@lists.alioth.debian.org

* Package name: php-mock
  Version : 2.3.0
  Upstream Author : Michał Bundyra 
* URL : https://github.com/php-mock/php-mock
* License : WTFPL
  Programming Lang: PHP
  Description : mock built-in PHP functions

PHP-Mock is a testing library which mocks non deterministic built-in
PHP functions like time() or rand(). This is achieved by PHP's
amespace fallback policy. Therefore it is required to be in a non
global namespace context and call the function unqualified.

PHP-Mock has integrations for PHPUnit, Mockery, and Prophecy
(phpspec).

This is a dependency for the latest release of Shaarli. It will be
maintained in php-team.
--- End Message ---
--- Begin Message ---
Source: php-mock
Source-Version: 2.3.0-1
Done: James Valleroy 

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

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

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

Debian distribution maintenance software
pp.
James Valleroy  (supplier of updated php-mock 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: Mon, 20 Dec 2021 07:58:23 -0500
Source: php-mock
Binary: php-mock
Architecture: source all
Version: 2.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: James Valleroy 
Description:
 php-mock   - mock built-in PHP functions
Closes: 1001909
Changes:
 php-mock (2.3.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1001909)
Checksums-Sha1:
 8bbb703a353c4433b280146c596e176f6af44a9c 2038 php-mock_2.3.0-1.dsc
 b1ecf93560f9d8a0db6f8fa4d7bd4970c6a37c36 17896 php-mock_2.3.0.orig.tar.xz
 185efbc93f977d1abd68365fdf7411c554160fa2 2428 php-mock_2.3.0-1.debian.tar.xz
 291d0e22a769cfb52a1d8dd9c1cf9fc4740eebda 13096 php-mock_2.3.0-1_all.deb
 9e66c727cf9255114a0afaf25301107540650914 7901 php-mock_2.3.0-1_amd64.buildinfo
Checksums-Sha256:
 3ed85e007642c7449dd8f01771b012c8d0009e59fff2d7667f990a6f216a54b6 2038 
php-mock_2.3.0-1.dsc
 c398ec8ff93d03dd9d84badc7f42766fd66cb89990aaebaf5d7c6e225edd8a10 17896 
php-mock_2.3.0.orig.tar.xz
 a41d2741bfd122d6745124c9cce02809cfdb6f1e3ee20c885184551327324e68 2428 
php-mock_2.3.0-1.debian.tar.xz
 202b70429b036eb7a6a749b2293e05a54e5b1d88575b040b39ccaca93424cac4 13096 
php-mock_2.3.0-1_all.deb
 94add4b5bcb8dc5d037e4e548d4e7b18f751eb797e012c01a17953d903f300ca 7901 
php-mock_2.3.0-1_amd64.buildinfo
Files:
 90ee693768494d5eff876818dc1c9047 2038 php optional php-mock_2.3.0-1.dsc
 e362fa894517621e362eae6572df4e4e 17896 php optional php-mock_2.3.0.orig.tar.xz
 5cdc24aef93c868186fe572da1a2b73f 2428 php optional 
php-mock_2.3.0-1.debian.tar.xz
 575fd1d0cd8734a4d38817e8f35a7d29 13096 php optional php-mock_2.3.0-1_all.deb
 baf5644568245acbbab7785d48e8c276 7901 php optional 
php-mock_2.3.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmHAhsEWHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICF/CD/9VGgWg2U4zhw3MJY3vTc/867Po
fSzvgo3vkItcMPgBz3x2oiVUdSmVXjp6ejrIRbTrGRtPBdmTjRyMPQhCHRcGpzE4
kyBQkRBlqyjJSSoyGcaCQiPGPC6a+/9/aw+QbV0431D7VND3o7Xu91IExIj00U3w
Xb9OFQW+n+6lTzep60ri5vHCfG7e+9AwWpbJan/jWNW2p6g5jMJ9igm2FKYm9ZZG
fbwjattwk0L5Q1DRW53Ej43cQ5CS9PLna9iMdfhfupDS/ZWGQaEwoYCJIxrlFJEA
YXgnsHItiyWTK0L3SxMrwV1OMeThlYTGO+uPnTCbN3Eemo6E36wipgAyb9RhPqa5
h/57RWjFEi97P1AoQGZNN88ohuTQWjsTslQU/j/FOr5+b6vANg1av6OK21jb28SU
JQvsMWhW8+faWb3Qh/Fe+3p2f7s1Q5eNcImB1dRgpKMQI5Xs//60xrjofQlSKO7W
E+BttCKKFFoNDUgVEvM/Z9EFWFBQ6SWAf8n5Qnm+/rbPh2ExOf2aO65tkp90cRn+
lNkcwMofO/6WglVjTwYc4sM9wh2IjptjymzxoYLcFE268C1daGwJDcVIQ1lbhOUu

Bug#1001760: marked as done (FTBFS: 'placeholders' is ambiguous)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:00:12 +
with message-id 
and subject line Bug#1001760: fixed in dart 6.12.1+dfsg4-1
has caused the Debian Bug report #1001760,
regarding FTBFS: 'placeholders' is ambiguous
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.)


-- 
1001760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001760
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dart
Version: 6.9.5-4
Severity: serious
Tags: patch
Justification: ftbfs
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Hi José Luís,

In rebuilding packages in Ubuntu for the liburdfdom-model package rename, I
found that dart currently fails to build from source:

/tmp/dart-6.9.5/unittests/unit/test_Signal.cpp: In member function 'virtual void
 Signal_NonStaticMemberFunction_Test::TestBody()':
/tmp/dart-6.9.5/unittests/unit/test_Signal.cpp:118:9: error: reference to 
'placeholders' is ambiguous
  118 |   using placeholders::_1;
  | ^~~~
In file included from /usr/include/eigen3/Eigen/Core:265,
 from /tmp/dart-6.9.5/obj-x86_64-linux-gnu/dart/config.hpp:5,
 from /tmp/dart-6.9.5/dart/dart.hpp:33,
 from /tmp/dart-6.9.5/unittests/unit/test_Signal.cpp:36:
/usr/include/eigen3/Eigen/src/Core/util/IndexedViewHelper.h:174:11: note: 
candidates are: 'namespace Eigen::placeholders { }'
  174 | namespace placeholders {
  |   ^~~~
In file included from /usr/include/c++/11/pstl/glue_algorithm_defs.h:13,
 from /usr/include/c++/11/algorithm:74,
 from 
/tmp/dart-6.9.5/unittests/gtest/include/gtest/internal/gtest-port.h:284,
 from 
/tmp/dart-6.9.5/unittests/gtest/include/gtest/internal/gtest-internal.h:40,
 from /tmp/dart-6.9.5/unittests/gtest/include/gtest/gtest.h:59,
 from /tmp/dart-6.9.5/unittests/unit/test_Signal.cpp:34:
/usr/include/c++/11/functional:219:13: note: 'namespace 
std::placeholders { }'
  219 |   namespace placeholders
  | ^~~~

Please find attached a patch that disambiguates and lets the package build.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru dart-6.9.5/debian/patches/series dart-6.9.5/debian/patches/series
--- dart-6.9.5/debian/patches/series2021-10-08 07:07:34.0 -0700
+++ dart-6.9.5/debian/patches/series2021-12-14 21:44:11.0 -0800
@@ -5,3 +5,4 @@
 0007-fix-soversion.patch
 0006-Reduce-test-result-accuracy-to-fix-i386.patch
 0008-fix-cmake-example.patch
+stdc++.patch
diff -Nru dart-6.9.5/debian/patches/stdc++.patch 
dart-6.9.5/debian/patches/stdc++.patch
--- dart-6.9.5/debian/patches/stdc++.patch  1969-12-31 16:00:00.0 
-0800
+++ dart-6.9.5/debian/patches/stdc++.patch  2021-12-15 07:49:05.0 
-0800
@@ -0,0 +1,22 @@
+Description: disambiguate 'placeholders' namespace
+ Eigen now has a 'placeholders' namespace, so specify that we're after
+ std::placeholders
+Author: Steve Langasek 
+Last-Update: 2021-12-15
+Forwarded: no
+
+Index: dart-6.9.5/unittests/unit/test_Signal.cpp
+===
+--- dart-6.9.5.orig/unittests/unit/test_Signal.cpp
 dart-6.9.5/unittests/unit/test_Signal.cpp
+@@ -115,8 +115,8 @@
+   signal2.connect(::onSignal2Static);
+ 
+   // Connect non-static member function
+-  using placeholders::_1;
+-  using placeholders::_2;
++  using std::placeholders::_1;
++  using std::placeholders::_2;
+   signal1.connect(bind(::onSignal1, , _1));
+   signal2.connect(bind(::onSignal2, , _1, _2));
+ 
--- End Message ---
--- Begin Message ---
Source: dart
Source-Version: 6.12.1+dfsg4-1
Done: Jose Luis Rivero 

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

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

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

Debian distribution maintenance software
pp.
Jose Luis Rivero  (supplier of updated dart package)

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

Bug#1001778: marked as done (ITP: libham-locator-perl -- Perl module for converting between Maidenhead locators and latitude/longitude)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:00:18 +
with message-id 
and subject line Bug#1001778: fixed in libham-locator-perl 0.1000-1
has caused the Debian Bug report #1001778,
regarding ITP: libham-locator-perl -- Perl module for converting between 
Maidenhead locators and latitude/longitude
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.)


-- 
1001778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Owner: Damyan Ivanov 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libham-locator-perl
  Version : 0.1000
  Upstream Author : Andy Smith 
* URL : https://metacpan.org/release/Ham-Locator
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Perl module for converting between Maidenhead locators and 
latitude/longitude

Ham::Locator provides methods for conversion between Maidenhead (QTH) locator
strings and latitude/longitude coordinates.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.
--- End Message ---
--- Begin Message ---
Source: libham-locator-perl
Source-Version: 0.1000-1
Done: Damyan Ivanov 

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

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

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated libham-locator-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 16 Dec 2021 07:10:43 +
Source: libham-locator-perl
Binary: libham-locator-perl
Architecture: source all
Version: 0.1000-1
Distribution: unstable
Urgency: low
Maintainer: Debian Perl Group 
Changed-By: Damyan Ivanov 
Description:
 libham-locator-perl - Perl module for converting between Maidenhead locators 
and latitu
Closes: 1001778
Changes:
 libham-locator-perl (0.1000-1) unstable; urgency=low
 .
   * Initial release. (Closes: #1001778 -- ITP)
Checksums-Sha1:
 184efea23a38d3d031b92ed14de801441d74ea0a 2144 libham-locator-perl_0.1000-1.dsc
 9a0283863db819681c937ab9dc6e229fda749b45 3742 
libham-locator-perl_0.1000.orig.tar.gz
 3ea0b72667623a1ad4a85d9509a7cad411bdbfe4 1972 
libham-locator-perl_0.1000-1.debian.tar.xz
 37c42f3faa624c885e7940f745b5b74dc410f814 6076 
libham-locator-perl_0.1000-1_all.deb
 bb1d52b4f0e34586e6891eac43e27ea67f1972c5 5800 
libham-locator-perl_0.1000-1_amd64.buildinfo
Checksums-Sha256:
 a1f7ee510698cef52f2f9743fc8ed4e509851a80334047249ecced48b1282640 2144 
libham-locator-perl_0.1000-1.dsc
 65ed17b3f9673662d254560051fee66f6e5f4fe5abde6808f54047436721e751 3742 
libham-locator-perl_0.1000.orig.tar.gz
 54b6e5f97e3730332e57103a1772fb259e6838488475e44b90d21de8adc16df4 1972 
libham-locator-perl_0.1000-1.debian.tar.xz
 e8926dbea7faa61d0470a4ee8fe04fb8ab517562df79fe9390375d442b58983c 6076 
libham-locator-perl_0.1000-1_all.deb
 9c7675c48cd7e598510cbaf4e8272c74b3b22d1cd22053d3776e96358df4ef37 5800 
libham-locator-perl_0.1000-1_amd64.buildinfo
Files:
 6c73e974982e2b15684213d4c63bd46d 2144 perl optional 
libham-locator-perl_0.1000-1.dsc
 48cdd6c84e3bf8a998b320f6bb0f666a 3742 perl optional 
libham-locator-perl_0.1000.orig.tar.gz
 b169226ecd120aa552de6fd881af5447 1972 perl optional 
libham-locator-perl_0.1000-1.debian.tar.xz
 21ae54e47d677081ea9fda671c90ee41 6076 perl optional 
libham-locator-perl_0.1000-1_all.deb
 15eed39f1f9e5d57d9cb3e0ad87a3122 5800 perl optional 
libham-locator-perl_0.1000-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAmG65pcACgkQ276dTZnS
oAS+Qg/9HxRIIWNZSbWHr2aGaWlN+2iurrkl15PZg1blw9aa45ojNyf3be+mvzXy
xxXrcuBN3k2Gu4euNEyRYNu2akpkPdrbvCGk94K9knT0pGQz8MK+riS6SQv5gjox
yogI39mNnuIKFFcaMkaAVw4uBM5EWcVgDtxecn4iknjZTqHW1iWgqg2Qr2KVubN6
c/CNU1xdEMJ7D1RLo1G0XtCLo7NlpmO0TUDCiLttnzHcBUU8GMn63y0PQn5cz97t
qg4Gf+19xGsIDD0jWt4Dczow6HwrYA7FX4Cl+JXUds2DkLjcZlCGkQt2/7GvJjr/
AjwdfuP2KETNtC12SfmqE2p8838iaiGljo5536Ya4wC0ZeYpaqHHqnsB+q1yeDbe

Bug#981502: marked as done (cython: reduce Build-Depends)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 18:48:54 +
with message-id 
and subject line Bug#981502: fixed in cython 0.29.24-2
has caused the Debian Bug report #981502,
regarding cython: reduce Build-Depends
to be marked as done.

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

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


-- 
981502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cython
Version: 0.29.21-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: cross-satisfiability

cython cannot be cross built, because its build dependencies are not
satisfiable. Instead of looking into such a difficult problem, I looked
for easily droppable dependencies and found two. The documentation is
shipped in an arch:all package and the build nicely degrades when sphinx
is absent. Therefore python3-sphinx can be moved to Build-Depends-Indep.
Similarly, not running the tests means that gdb goes unused, which in
turn means that it can be annotated . Please consider applying
the attached patch.

Helmut
diff --minimal -Nru cython-0.29.21/debian/changelog 
cython-0.29.21/debian/changelog
--- cython-0.29.21/debian/changelog 2020-10-18 16:30:27.0 +0200
+++ cython-0.29.21/debian/changelog 2021-01-31 14:30:04.0 +0100
@@ -1,3 +1,12 @@
+cython (0.29.21-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Reduce Build-Depends: (Closes: #-1)
++ Demote python3-sphinx to Build-Depends-Indep.
++ Annotate gdb dependency .
+
+ -- Helmut Grohne   Sun, 31 Jan 2021 14:30:04 +0100
+
 cython (0.29.21-3) unstable; urgency=medium
 
   * Team upload
diff --minimal -Nru cython-0.29.21/debian/control cython-0.29.21/debian/control
--- cython-0.29.21/debian/control   2020-10-18 16:29:42.0 +0200
+++ cython-0.29.21/debian/control   2021-01-31 14:30:01.0 +0100
@@ -7,11 +7,11 @@
dh-python,
dpkg-dev (>= 1.16.1~),
help2man (>= 1.37.1~),
-   python3-sphinx,
python3-all-dev,
python3-all-dbg,
python3-numpy (>= 1:1.12.1-3.1) ,
-   gdb,
+   gdb ,
+Build-Depends-Indep: python3-sphinx,
 Standards-Version: 4.5.0
 Homepage: http://cython.org/
 Vcs-Git: https://salsa.debian.org/python-team/packages/cython.git
--- End Message ---
--- Begin Message ---
Source: cython
Source-Version: 0.29.24-2
Done: Laurent Bigonville 

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated cython package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Dec 2021 18:47:04 +0100
Source: cython
Architecture: source
Version: 0.29.24-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Laurent Bigonville 
Closes: 981502
Changes:
 cython (0.29.24-2) unstable; urgency=medium
 .
   * Team upload.
   [ Helmut Grohne ]
   * Non-maintainer upload.
   * Reduce Build-Depends: (Closes: #981502)
 + Demote python3-sphinx to Build-Depends-Indep.
 + Annotate gdb dependency .
Checksums-Sha1:
 4fed66217945f4296b0908a2cef3dd15988d6d91 1986 cython_0.29.24-2.dsc
 7e1e6ae721a5cb9e1c050788fa559f7435276c26 28840 cython_0.29.24-2.debian.tar.xz
 b4ab6816c008ebb254704c0aaf79f5c719cdd6a5 7256 cython_0.29.24-2_source.buildinfo
Checksums-Sha256:
 75f966aa94ca067017d751ae284e51bbb3803fe37d1100331960cfb9b3afb02e 1986 
cython_0.29.24-2.dsc
 fbc6b20ad8a03e03d8e20edfc0a5a72ffbea4c3d1345845ba1d315b3cb0990c0 28840 
cython_0.29.24-2.debian.tar.xz
 06f765f57d11c001fa90547372d15ab3bca7cb797bebe690b71f8ecfe332f38d 7256 
cython_0.29.24-2_source.buildinfo
Files:
 510318ccfe3101e3705cdd55f8c99833 1986 python optional cython_0.29.24-2.dsc
 1acafb36ac31e1eeb91112837b7fd296 28840 python optional 
cython_0.29.24-2.debian.tar.xz
 90036940644cec7efd75285bf4da7fd8 7256 python optional 
cython_0.29.24-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAmHKBWMRHGJpZ29uQGRl

Bug#1001938: marked as done (cython: Please create a build-profile to avoind build-depending on gdb)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 18:48:54 +
with message-id 
and subject line Bug#981502: fixed in cython 0.29.24-2
has caused the Debian Bug report #981502,
regarding cython: Please create a build-profile to avoind build-depending on gdb
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.)


-- 
981502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cython
Version: 0.29.24-1
Severity: important

Hello,

It looks like that the build-dependency against gdb creates a dependency
loop

cython -> gdb -> libsource-highlight -> libboost-regex -> numpy -> cython

Creating a build-profile might help here I guess?

Kind regards,
Laurent Bigonville

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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
--- End Message ---
--- Begin Message ---
Source: cython
Source-Version: 0.29.24-2
Done: Laurent Bigonville 

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated cython package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Dec 2021 18:47:04 +0100
Source: cython
Architecture: source
Version: 0.29.24-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Laurent Bigonville 
Closes: 981502
Changes:
 cython (0.29.24-2) unstable; urgency=medium
 .
   * Team upload.
   [ Helmut Grohne ]
   * Non-maintainer upload.
   * Reduce Build-Depends: (Closes: #981502)
 + Demote python3-sphinx to Build-Depends-Indep.
 + Annotate gdb dependency .
Checksums-Sha1:
 4fed66217945f4296b0908a2cef3dd15988d6d91 1986 cython_0.29.24-2.dsc
 7e1e6ae721a5cb9e1c050788fa559f7435276c26 28840 cython_0.29.24-2.debian.tar.xz
 b4ab6816c008ebb254704c0aaf79f5c719cdd6a5 7256 cython_0.29.24-2_source.buildinfo
Checksums-Sha256:
 75f966aa94ca067017d751ae284e51bbb3803fe37d1100331960cfb9b3afb02e 1986 
cython_0.29.24-2.dsc
 fbc6b20ad8a03e03d8e20edfc0a5a72ffbea4c3d1345845ba1d315b3cb0990c0 28840 
cython_0.29.24-2.debian.tar.xz
 06f765f57d11c001fa90547372d15ab3bca7cb797bebe690b71f8ecfe332f38d 7256 
cython_0.29.24-2_source.buildinfo
Files:
 510318ccfe3101e3705cdd55f8c99833 1986 python optional cython_0.29.24-2.dsc
 1acafb36ac31e1eeb91112837b7fd296 28840 python optional 
cython_0.29.24-2.debian.tar.xz
 90036940644cec7efd75285bf4da7fd8 7256 python optional 
cython_0.29.24-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAmHKBWMRHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9Wn8gf+K1J9NKzZoZ6QuJI4NDCtTVLeVJGCSvTn
t9JxbJrFBixSLTCsKkWHeEj2Lkb6BvyT1szkL+pOe0KmqiK3k1TVY1U9jVZaLOq7
d4DTq9STtSQqgQGC2ZhvJfC8k8ZFKBzuxd1IpvVoy5pOWuMm2ZgesI/N0+q8jbCz
dcdleYtNXt7sxuMKcVEI6nY+XIXXPBGginEY1AsQtF/16NxEAullA9bRmY+lWa0b
CUMtbzQjs+mSfP6o6gtbSK6AONdZVSgtTpq8YtOnLuNZiZJubPKCGKqAeW/yCFkt
dXs8K9vISGpRob9YEgyTJ7GNP+ov3o+TYWZLoq3zAb2CL33I1WlrQQ==
=t55B
-END PGP SIGNATURE End Message ---


Bug#955784: marked as done (abicheck: Please consider Ubuntu-provided patches (binary-arch,indep and more))

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:14:01 +0100
with message-id <3b694a70-c601-5e33-3710-d3c4f88df...@yahoo.no>
and subject line Re: abicheck: Please consider Ubuntu-provided patches 
(binary-arch,indep and more)
has caused the Debian Bug report #955784,
regarding abicheck: Please consider Ubuntu-provided patches (binary-arch,indep 
and more)
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.)


-- 
955784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: abicheck
Version: 1.2-5
Severity: important
X-Debbugs-CC: sea...@debian.org

Dear package abicheck maintainer,

Your package received no maintainer upload in the last 11 years, missing some
important packaging technology updates. One of the important thing is the
missing support of build-arch and build-indep targets, which is causing
trouble in the maintenance of debhelper tool. You may find details in the
thread of https://lists.debian.org/debian-devel/2020/04/msg00015.html .

Downstream Ubuntu has provided patches on refreshing the packaging standard.
Please consider applying downstream patches.

-- 
Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: abicheck
Version: 1.2-7

Reported by Boyuan Yang, fixed by Boyuan Yang.
Package has been ported to dh sequencer.


Håvard--- End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 19:11:02 +0100
with message-id <8533c8d4-4e32-b45f-16a4-73ca0bd92...@yahoo.no>
and subject line Re: abicheck: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
has caused the Debian Bug report #965404,
regarding abicheck: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

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

Fixed by Boyuan Yang


Håvard--- End Message ---


Bug#1002349: marked as done (isodate: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 18:04:30 +
with message-id 
and subject line Bug#1002349: fixed in isodate 0.6.1-1
has caused the Debian Bug report #1002349,
regarding isodate: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.10 3.9" returned exit code 13
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.)


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

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py config 
> running config
> I: pybuild base:237: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:237: /usr/bin/python3.10 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> copying src/isodate/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> copying src/isodate/tzinfo.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> copying src/isodate/isodates.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> copying src/isodate/isotime.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> copying src/isodate/duration.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> copying src/isodate/isostrf.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> copying src/isodate/isoduration.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> copying src/isodate/isodatetime.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> copying src/isodate/isotzinfo.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> copying src/isodate/isoerror.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate
> creating /<>/.pybuild/cpython3_3.10_isodate/build/isodate/tests
> copying src/isodate/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate/tests
> copying src/isodate/tests/test_pickle.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate/tests
> copying src/isodate/tests/test_duration.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate/tests
> copying src/isodate/tests/test_date.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate/tests
> copying src/isodate/tests/test_datetime.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate/tests
> copying src/isodate/tests/test_time.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate/tests
> copying src/isodate/tests/test_strf.py -> 
> /<>/.pybuild/cpython3_3.10_isodate/build/isodate/tests
> I: pybuild base:237: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> copying src/isodate/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> copying src/isodate/tzinfo.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> copying src/isodate/isodates.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> copying src/isodate/isotime.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> copying src/isodate/duration.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> copying src/isodate/isostrf.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> copying src/isodate/isoduration.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> copying src/isodate/isodatetime.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> copying src/isodate/isotzinfo.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> copying src/isodate/isoerror.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate
> creating /<>/.pybuild/cpython3_3.9_isodate/build/isodate/tests
> copying src/isodate/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate/tests
> copying src/isodate/tests/test_pickle.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate/tests
> copying src/isodate/tests/test_duration.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate/tests
> copying src/isodate/tests/test_date.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate/tests
> copying src/isodate/tests/test_datetime.py -> 
> /<>/.pybuild/cpython3_3.9_isodate/build/isodate/tests
> 

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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 18:04:42 +
with message-id 
and subject line Bug#999312: fixed in ssed 3.62-8
has caused the Debian Bug report #999312,
regarding ssed: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: ssed
Source-Version: 3.62-8
Done: Jose Antonio Quevedo Muñoz 

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

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

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

Debian distribution maintenance software
pp.
Jose Antonio Quevedo Muñoz  (supplier of updated 
ssed package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Dec 2021 21:15:05 +0200
Source: ssed
Architecture: source
Version: 3.62-8
Distribution: unstable
Urgency: low
Maintainer: Jose Antonio Quevedo Muñoz 
Changed-By: Jose Antonio Quevedo Muñoz 
Closes: 999312
Changes:
 ssed (3.62-8) unstable; urgency=low
 .
   * Added build-arch and build-indep targets (closes: #999312)
   * Added testsuite.
   * Added hardening flags to debian/rules.
   * Upgraded debian source format to 3.0 (quilt).
   * Updated standards version to 4.3.0.
   * Updated copyright to DEP-5 standard.
   * Updated debhelper dependency and compat version to 10.
   * Updated package priority from extra to optional.
   * Updated config.guess config.sub in config.
   * Removed autotools-dev dependency.
   * Removed initial article from description
Checksums-Sha1:
 1dcd482e15fafa3e73d2592696873e6705ea0a45 1573 ssed_3.62-8.dsc
 f895182068d32aacdfddbf2e740f88ffc2ae9385 20368 ssed_3.62-8.debian.tar.xz
 6b7348909f7d697941890c8cf46701e33436c08b 5527 ssed_3.62-8_source.buildinfo
Checksums-Sha256:
 44b5e6f22f6efc532cf9b4e54699c7465825ea7d3e3556369848cde1ab883405 1573 
ssed_3.62-8.dsc
 21015660d0446d8addbe9608ca664b949070eabcd9554610f05f0b5a398f73ab 20368 
ssed_3.62-8.debian.tar.xz
 6e025f9afb339b27b22e4bd9e73969090c6d02e9de6c0ba0bc8b78f2a0718795 5527 
ssed_3.62-8_source.buildinfo
Files:
 60ad00b6290a10f47e49b6081a637868 1573 utils optional ssed_3.62-8.dsc
 3b781c4a43a5426750dca559a89504b3 20368 utils optional ssed_3.62-8.debian.tar.xz
 a0e7de957d5b378abbf4e009a37541c0 5527 utils optional 
ssed_3.62-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmHJ+/kQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFABGDACRz8w90063DhSH5zR1Bij6xSEwCEfRu/wZ
xwf/YDUFM4X6t6YWmzflD1ziBvssqX7jTlUzpqe04jdXdWoSr0a7UH4K5692lQ4L
oSBnXXUpqVvlGaQ4yTeTzS5BlEtIklULPrB7u/pfsr0uq6RJV/q2nStNV5qxt9TF
QSkVaNa1b1wqkGJPi3xBASH7dxkn6+L4sT8rWZc7bbCxWwMZ8hM9ZMBJCrxmASVI
1Q/N0spF80Ao9pbGuqlSdtQGu3V0ITaA1jQxvyWxLgAfauIWBfUfSx/j0lLyEk1a
dWomcObmCvOb//PA9UE8pec4QABYPSiFLvBfm6obEihx0dvwJ8H5bCKupOdOAVqd
pBK+NAKKk2ubLEDNLp6vupdgum1nQkkZzFeZeXzyjI0jxoBD16HBKHjSN8qaGASg
4uDtznFsaEmklfP+/isI9Q6IYEz+aldCmwCJzG64HR8bOp7Us6k0FD5DCAyt//nd
BY+Nri3qwxwdZRuAHF3Wp+HC2HwGBKE=
=I6vC
-END PGP SIGNATURE End Message ---


Bug#947179: marked as done (linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware drivers)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 18:00:38 +
with message-id 
and subject line Bug#947179: fixed in linux 5.16~rc7-1~exp1
has caused the Debian Bug report #947179,
regarding linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware 
drivers
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.)


-- 
947179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 5.3.15-1
Severity: wishlist

Hi,

it would be nice if the Debian kernel would provide drivers to interact
with CoreBoot. As far as I can see, those are "hidden" behind
CONFIG_GOOGLE_FIRMWARE ...

These seem to be all available as modules, so it won't hurt to switch
them on, right? (If I understand drivers/firmware/google/Makefile
correctly)

For reference:

CONFIG_GOOGLE_FIRMWARE=y
CONFIG_GOOGLE_SMI=m
CONFIG_GOOGLE_COREBOOT_TABLE=m
CONFIG_GOOGLE_MEMCONSOLE=m
CONFIG_GOOGLE_MEMCONSOLE_X86_LEGACY=m
CONFIG_GOOGLE_FRAMEBUFFER_COREBOOT=m
CONFIG_GOOGLE_MEMCONSOLE_COREBOOT=m
CONFIG_GOOGLE_VPD=m

Thanks for consideration!


Tobias

-- Package-specific info:
** Version:
Linux version 5.3.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 
20191130 (Debian 9.2.1-21)) #1 SMP Debian 5.3.15-1 (2019-12-07)

** Command line:
\\vmlinuz-5.3.0-3-amd64 ro root=/dev/mapper/ssd-root quiet splash 
initrd=\initrd.img-5.3.0-3-amd64

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Loaded modules:
vboxnetadp(OE)
vboxnetflt(OE)
vboxdrv(OE)

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de:en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-5.3.0-3-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.135
ii  kmod26-3
ii  linux-base  4.6

Versions of packages linux-image-5.3.0-3-amd64 recommends:
pn  apparmor 
ii  firmware-linux-free  3.4

Versions of packages linux-image-5.3.0-3-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.04-5
pn  linux-doc-5.3   

Versions of packages linux-image-5.3.0-3-amd64 is related to:
ii  firmware-amd-graphics 20190717-2
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
ii  firmware-misc-nonfree 20190717-2
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.16~rc7-1~exp1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux 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: Mon, 27 Dec 2021 00:18:19 +0100
Source: linux
Architecture: source
Version: 5.16~rc7-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 947179 1002460
Changes:
 linux (5.16~rc7-1~exp1) experimental; urgency=medium
 .
   * 

Bug#1002460: marked as done (linux-image-amd64: Missing kernel configuration for Microsoft Laptops and Surface devices)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 18:00:38 +
with message-id 
and subject line Bug#1002460: fixed in linux 5.16~rc7-1~exp1
has caused the Debian Bug report #1002460,
regarding linux-image-amd64: Missing kernel configuration for Microsoft Laptops 
and Surface devices
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.)


-- 
1002460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-amd64
Version: 5.15.5-1
Severity: normal
X-Debbugs-Cc: mbren...@gmail.com

Dear Maintainer,

Some features for Linux on Microsoft Laptops and Surface devices that were
implemented in the 5.13+ Linux kernel are not configured with the kernels
provided by Debian.

Full details (including a suggested fix) are available here:
https://github.com/linux-surface/linux-surface/issues/683


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE
Locale: LANG=en_CH.UTF-8, LC_CTYPE=en_CH.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 linux-image-amd64 depends on:
ii  linux-image-5.15.0-2-amd64  5.15.5-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 5.16~rc7-1~exp1
Done: Salvatore Bonaccorso 

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux 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: Mon, 27 Dec 2021 00:18:19 +0100
Source: linux
Architecture: source
Version: 5.16~rc7-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 947179 1002460
Changes:
 linux (5.16~rc7-1~exp1) experimental; urgency=medium
 .
   * New upstream release candidate
 .
   [ Uwe Kleine-König ]
   * [arm64] enable DRM_VMWGFX_FBCON to get a tty to login in the absence of a
 graphical login manager.
 .
   [ Vincent Blut ]
   * [x86] drivers/platform/surface/aggregator: Enable SURFACE_AGGREGATOR as
 module (Closes: #1002460)
   * [x86] drivers/platform/surface: Enable SURFACE_3_POWER_OPREGION,
 SURFACE_ACPI_NOTIFY, SURFACE_AGGREGATOR_REGISTRY, SURFACE_DTX,
 SURFACE_GPE, SURFACE_HOTPLUG and SURFACE_PLATFORM_PROFILE as modules
   * [x86] drivers/hid/surface-hid: Enable SURFACE_HID and SURFACE_KBD as
 modules
   * [x86] drivers/power/supply: Enable BATTERY_SURFACE and CHARGER_SURFACE as
 modules
 .
   [ Salvatore Bonaccorso ]
   * [rt] Update to 5.16-rc6-rt12
   * [x86] drivers/firmware/google: Re-enable GOOGLE_FIRMWARE (Closes: #947179)
Checksums-Sha1:
 5578aaf22d0f379d77ce95b3d405a305b5949a22 198878 linux_5.16~rc7-1~exp1.dsc
 e3f981788c5b9590766ffaa30df990ef977f58da 129138096 linux_5.16~rc7.orig.tar.xz
 573d1f046cd7fe43dc503c276c28c6a8b96ceb99 1273276 
linux_5.16~rc7-1~exp1.debian.tar.xz
 1461975430c186f44c300eb188bc52e4a1e79001 6384 
linux_5.16~rc7-1~exp1_source.buildinfo
Checksums-Sha256:
 0bf79b6833042da3882b2f66cb004bf6968e06f22b592e7c24bcea6c70dd5383 198878 
linux_5.16~rc7-1~exp1.dsc
 a625142e2013e573827097fe4374cb8f5b24ec696c1c6c1a8623937f41d45d7d 129138096 
linux_5.16~rc7.orig.tar.xz
 ee715679b0f4aaaf4b53619cf846965643b418237ef854fca94530a0a8e142ff 1273276 
linux_5.16~rc7-1~exp1.debian.tar.xz
 a7810423965cc7030097b6cbf551430f5539630cfc664f2439b6386097f7e93a 6384 
linux_5.16~rc7-1~exp1_source.buildinfo
Files:
 8b230f44f751cbbbdef65bac4555be06 198878 kernel optional 
linux_5.16~rc7-1~exp1.dsc
 07a1f269baeffa072c26d27a762dfb49 129138096 kernel optional 
linux_5.16~rc7.orig.tar.xz
 0c09a943d72044436d268c0cd82d25a6 1273276 kernel optional 

Bug#1002659: marked as done (RFS: ssed/3.62-8 - super sed stream editor)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 18:50:09 +0100
with message-id 
and subject line Re: RFS: ssed/3.6.2-8 - super sed stream editor
has caused the Debian Bug report #1002659,
regarding RFS: ssed/3.62-8 - super sed stream editor
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.)


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

Severity: normal


Dear mentors,

I am looking for a sponsor for my package "ssed":

 * Package name: ssed
   Version : 3.6.2-8
   Upstream Author : Paolo Bonzini
 * URL : http://sed.sf.net/grabbag/ssed/
 * License : GPL-2+
   Section : utils

It builds those binary packages:

  ssed - super sed stream editor

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/ssed/

Alternatively, one can download the package with dget using this command:

  dget -x https://mentors.debian.net/debian/pool/main/s/ssed/ssed_3.62-8.dsc


Changes since the last upload:

  * Added build-arch and build-indep targets (closes: #999312)
  * Added testsuite.
  * Added hardening flags to debian/rules.
  * Upgraded debian source format to 3.0 (quilt).
  * Updated standards version to 4.3.0.
  * Updated copyright to DEP-5 standard.
  * Updated debhelper dependency and compat version to 10.
  * Updated package priority from extra to optional.
  * Updated config.guess config.sub in config.
  * Removed autotools-dev dependency.
  * Removed initial article from description


I would be glad if someone uploaded this package for me.

Kind regards,
--
Jose Antonio Quevedo Muñoz



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

I have uploaded ssed with a minor change in d/changelog:
The line with the upstream URL including the wrong (old version) file name was 
removed.--- End Message ---


Bug#967260: marked as done (ats-lang-anairiats: depends on deprecated GTK 2)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 17:19:51 +
with message-id 
and subject line Bug#1002694: Removed package(s) from unstable
has caused the Debian Bug report #967260,
regarding ats-lang-anairiats: depends on deprecated GTK 2
to be marked as done.

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

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


-- 
967260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ats-lang-anairiats
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
Version: 0.2.11-1.1+rm

Dear submitter,

as the package ats-lang-anairiats 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/1002694

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#1002694: marked as done (RM: ats-lang-anairiats -- ROM; deprecated)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 17:19:46 +
with message-id 
and subject line Bug#1002694: Removed package(s) from unstable
has caused the Debian Bug report #1002694,
regarding RM: ats-lang-anairiats -- ROM; deprecated
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.)


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

Hi,

ATS2 has replaced ATS1 now for several years, so it is time for this
package to go as it is no longer maintained upstream.

Thanks,
Matt
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

ats-lang-anairiats | 0.2.11-1.1 | source, amd64, arm64, armel, armhf, i386, 
mips64el, mipsel, ppc64el, s390x
ats-lang-anairiats-doc | 0.2.11-1.1 | all
ats-lang-anairiats-examples | 0.2.11-1.1 | all

--- Reason ---
ROM; deprecated
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1002...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1002694

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#688479: marked as done (Conflicting declaration of the_ats_exception_stack)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 17:19:51 +
with message-id 
and subject line Bug#1002694: Removed package(s) from unstable
has caused the Debian Bug report #688479,
regarding Conflicting declaration of the_ats_exception_stack
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.)


-- 
688479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=688479
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ats-lang-anairiats
Version: 0.2.3-1

While building the package using our research compiler infrastructure we noticed
the following inconsistent declarations:

../ccomp/runtime/ats_exception.h:ats_exception_frame_type 
*the_ats_exception_stack ;
../ccomp/runtime/ats_prelude.c:** the type of [the_ats_exception_stack]
../ccomp/runtime/ats_prelude.c:ats_ptr_type *the_ats_exception_stack = NULL ;

with ats_exception_frame_type being a non-trivial struct and ats_ptr_type being
void*. These types are entirely incompatible and may cause arbitrary undefined
behaviour.

Best,
Michael



pgpSN0SLpDVbf.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.2.11-1.1+rm

Dear submitter,

as the package ats-lang-anairiats 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/1002694

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#650753: marked as done (ats-lang-anairiats: FTBFS on ia64: [compile_file_to_file] is sigtermed)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 17:19:51 +
with message-id 
and subject line Bug#1002694: Removed package(s) from unstable
has caused the Debian Bug report #650753,
regarding ats-lang-anairiats: FTBFS on ia64: [compile_file_to_file] is sigtermed
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.)


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

Source: ats-lang-anairiats
Version: 0.2.5-1
Severity: serious
Justification: fails to build from source
User: debian-i...@lists.debian.org
Usertags: ia64

ats-lang-anairiats FTBFS on ia64:
| 
"/build/buildd-ats-lang-anairiats_0.2.5-1-ia64-qH8hDa/ats-lang-anairiats-0.2.5"/bin/atscc
 -Wall -O2 -c -o dynloadall_dats.o dynloadall.dats
| 
/build/buildd-ats-lang-anairiats_0.2.5-1-ia64-qH8hDa/ats-lang-anairiats-0.2.5/bin/atsopt
 --output dynloadall_dats.c --dynamic dynloadall.dats
| [compile_file_to_file] is sigtermed
| make[2]: *** [dynloadall_dats.o] Error 1

Full build log:
https://buildd.debian.org/status/fetch.php?pkg=ats-lang-anairiats=ia64=0.2.5-1=1322839830

--
Jakub Wilk


--- End Message ---
--- Begin Message ---
Version: 0.2.11-1.1+rm

Dear submitter,

as the package ats-lang-anairiats 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/1002694

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#1000042: marked as done (ats-lang-anairiats: depends on obsolete pcre3 library)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 17:19:51 +
with message-id 
and subject line Bug#1002694: Removed package(s) from unstable
has caused the Debian Bug report #142,
regarding ats-lang-anairiats: depends on obsolete pcre3 library
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.)


-- 
142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ats-lang-anairiats
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Version: 0.2.11-1.1+rm

Dear submitter,

as the package ats-lang-anairiats 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/1002694

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#1000844: marked as done (libpod: CVE-2021-4024: podman machine spawns gvproxy with port binded to all IPs)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 17:03:54 +
with message-id 
and subject line Bug#1000844: fixed in libpod 3.4.4+ds1-1
has caused the Debian Bug report #1000844,
regarding libpod: CVE-2021-4024: podman machine spawns gvproxy with port binded 
to all IPs
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.)


-- 
1000844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpod
Version: 3.4.2+ds1-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/containers/podman/pull/12283
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 3.4.1+ds1-2

Hi,

The following vulnerability was published for libpod.

CVE-2021-4024[0]:
| podman machine spawns gvproxy with port binded to all IPs

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-4024
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4024
[1] https://github.com/containers/podman/pull/12283

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libpod
Source-Version: 3.4.4+ds1-1
Done: Reinhard Tartler 

We believe that the bug you reported is fixed in the latest version of
libpod, 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.
Reinhard Tartler  (supplier of updated libpod package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 25 Dec 2021 19:48:14 -0500
Source: libpod
Architecture: source
Version: 3.4.4+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Reinhard Tartler 
Closes: 1000844
Changes:
 libpod (3.4.4+ds1-1) unstable; urgency=medium
 .
   * New upstream release
 Confirming that CVE-2021-4024 is fixed in 3.4.3, Closes: #1000844
Checksums-Sha1:
 4609a81f525ed40a73e9f413579ef6c03b13e661 5157 libpod_3.4.4+ds1-1.dsc
 241a480bdada64b2428ff84e5e29f9ebc30a82b2 1965884 libpod_3.4.4+ds1.orig.tar.xz
 e3803a0427b2b1dc54f7bfee3c9a512cd6c6d0e4 15480 libpod_3.4.4+ds1-1.debian.tar.xz
Checksums-Sha256:
 4f35d7e2d6929f59b9baf1b3c0509f28b49408dc86a80a74f7dc100076276c99 5157 
libpod_3.4.4+ds1-1.dsc
 66c4f9e4ffc8c63319e8b5f69eca33b13eee5af7b89124cf23659eb91e4f388e 1965884 
libpod_3.4.4+ds1.orig.tar.xz
 7d1c1c262ca9ddd789058d36cf4520e7e8300163ac2359f42012392eb97e49ba 15480 
libpod_3.4.4+ds1-1.debian.tar.xz
Files:
 327d7d563a53ac7e8758e11db4a502f6 5157 admin optional libpod_3.4.4+ds1-1.dsc
 617e006a7f3ef0909d2b4eacd7ec8278 1965884 admin optional 
libpod_3.4.4+ds1.orig.tar.xz
 78e4b7fc95ec9987ceaa6a4d6f92d09e 15480 admin optional 
libpod_3.4.4+ds1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmHJ72AUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJsvH7hAAvSb/LrCyMnC362BotcIjOCQhrSZa
aECQvEXyZ2NDU27NwMujvBVSViv2Cm+dXz6j8O/XA3Yh/o+N+PJjTjzXnutoZ00c
ynogXLQqZcpVJR3tp7WWbOU1i1QLLPLwMLYzDhVgj0z0kNYH7RLgFYvcJZi/EEY+
T2ADxwUCNYvfrsGGJfeqJ2+mQhbHTJxnvQeGpvonNUNeRW2joDYzpzmXYhzPFtBx
CujC+IHIYyIrOaX0sK4StIQwIfrifCZjBzSD5kiLlrWU9fx5z/ySiXGBY93/qzmD
FsPKbrFqrmuQrXpmo1pBJNjnSiUtx5hpDYc/qbOiGEcOvJUn6CxfHo9o44ojkuEK
ATyhhahC/AFLNsyMyHWxL5+oHei8KtHSXeeeqUFgOzkqiR3nboYtBs46i6/SyjhV
wqcTkY1QXXjBa1YEyo6AweMtgAZ+xm4jdenM9MAot6zg9w+JTKsK8Humf7oDOgjC
tj3x6s7fckgibVh2x1q9l387WGodyCIgA2gwNENLFUFATr9P5omsdpW3JGFNZ8ti
AppXzfjwdTsilGpnaQvgBhaYR+5Tdr8LTA/Hal1G+RZ94yCOg57IEoeQ6Av5zqoc
NZK1+OFQlGW7Fk/eGdp3e89q6bqP/JfidUA9F1KuQbm2uOk0OOne17vW8FWcjzgI
8m4Qidx+ahCmVvk=
=2D/a
-END PGP SIGNATURE End Message ---


Bug#998597: marked as done (sysprof: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "sysprofd")

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 16:48:56 +
with message-id 
and subject line Bug#998597: fixed in sysprof 3.42.1-1
has caused the Debian Bug report #998597,
regarding sysprof: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "sysprofd"
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.)


-- 
998597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sysprof
Version: 3.40.1-3
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):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- \
>   -Denable_examples=true \
>   -Denable_tests=true \
>   -Denable_tools=true \
>   -Dsysprofd=bundled \
>   -Dsystemdunitdir=/lib/systemd/system
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Denable_examples=true 
> -Denable_tests=true -Denable_tools=true -Dsysprofd=bundled 
> -Dsystemdunitdir=/lib/systemd/system
> The Meson build system
> Version: 0.60.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> 
> ../meson.build:1:0: ERROR: Unknown options: "sysprofd"
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2021-11-04T09:49:15.125639
> Main binary: /usr/bin/python3
> Build Options: -Denable_examples=true -Denable_tests=true -Denable_tools=true 
> -Dsysprofd=bundled -Dsystemdunitdir=/lib/systemd/system -Dprefix=/usr 
> -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc 
> -Dbuildtype=plain -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.60.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> 
> ../meson.build:1:0: ERROR: Unknown options: "sysprofd"
> dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Denable_examples=true 
> -Denable_tests=true -Denable_tools=true -Dsysprofd=bundled 
> -Dsystemdunitdir=/lib/systemd/system returned exit code 1
> make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/11/04/sysprof_3.40.1-3_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: sysprof
Source-Version: 3.42.1-1
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
sysprof, 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.
Simon McVittie  (supplier of updated sysprof package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Dec 2021 16:08:31 +
Source: sysprof
Architecture: source
Version: 3.42.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 998597
Changes:
 sysprof (3.42.1-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream release
   * d/sysprof.symbols: Ignore removal of private rax* symbols
   * d/copyright: Update
   * Correct name of with_sysprofd build option (Closes: #998597)
   * d/rules: Explicitly set build options.
 Explicit is better than 

Processed: your mail

2021-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1002530 openrazer-driver-dkms 3.2.0+dfsg-1
Bug #1002530 {Done: Dylan Aïssi } [openrazer] Openrazer 3.2 
builds dummy drivers
Bug reassigned from package 'openrazer' to 'openrazer-driver-dkms'.
No longer marked as found in versions 3.2.0+dfsg-1.
No longer marked as fixed in versions openrazer/3.2.0+dfsg-2.
Bug #1002530 {Done: Dylan Aïssi } [openrazer-driver-dkms] 
Openrazer 3.2 builds dummy drivers
Marked as found in versions openrazer/3.2.0+dfsg-1.
> forcemerge 1002530 1002574
Bug #1002530 {Done: Dylan Aïssi } [openrazer-driver-dkms] 
Openrazer 3.2 builds dummy drivers
Bug #1002574 [openrazer-driver-dkms] System not supported with v. 3.2
Marked Bug as done
Merged 1002530 1002574
> thanks
Stopping processing here.

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



Bug#1001273: marked as done (gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 16:18:45 +
with message-id 
and subject line Bug#1001273: fixed in gcc-sh-elf 2
has caused the Debian Bug report #1001273,
regarding gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
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.)


-- 
1001273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-avr,gcc-sh-elf
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1:5.4.0+Atmel3.6.2-2
Control: found -1 11.2.0-12+1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Preparing to unpack .../gcc-sh-elf_11.2.0-12+1_amd64.deb ...
  Unpacking gcc-sh-elf (11.2.0-12+1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gcc-sh-elf_11.2.0-12+1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/libcc1.so.0.0.0', which is also in package 
gcc-avr 1:5.4.0+Atmel3.6.2-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/gcc-sh-elf_11.2.0-12+1_amd64.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/lib/libcc1.so
  /usr/lib/libcc1.so.0
  /usr/lib/libcc1.so.0.0.0

But, maybe even worse, there is also libcc1-0 shipping

  /usr/lib//libcc1.so.0
  /usr/lib//libcc1.so.0.0.0

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


gcc-avr=1:5.4.0+Atmel3.6.2-2_gcc-sh-elf=11.2.0-12+1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gcc-sh-elf
Source-Version: 2
Done: John Scott 

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

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

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

Debian distribution maintenance software
pp.
John Scott  (supplier of updated gcc-sh-elf 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: Mon, 06 Dec 2021 17:44:55 -0500
Source: gcc-sh-elf
Architecture: source
Version: 2
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: John Scott 
Closes: 1001273
Changes:
 gcc-sh-elf (2) unstable; urgency=medium
 .
   * Disable building libcc1, which is superfluous. (Closes: #1001273)
   * Make new source-only upload to enable testing migration.
Checksums-Sha1:
 9cc02d1c06a31593b62b61cdaaec17b5fdbcef6d 1754 gcc-sh-elf_2.dsc
 a563d52cc5c0e7d950c230f9b973ff2fa4957a4d 7792 gcc-sh-elf_2.tar.xz
 d9f7bcb3b54990fedcb680fec02474579f90874c 5641 gcc-sh-elf_2_source.buildinfo
Checksums-Sha256:
 1f0a50cbf08078effde62edd45f6da9f61337d3a13841afbe51bf2c6df85cb71 1754 
gcc-sh-elf_2.dsc
 f30c1eee7e7a0613079e0e05ad23b2a99112eeb1bd0145baed37984b4d315f27 7792 
gcc-sh-elf_2.tar.xz
 04a0a084956531140db46f0745d074f5dab36bf1e0a052490c56df0fc69f8fb5 5641 
gcc-sh-elf_2_source.buildinfo
Files:
 4c3bda7a227a4feaeb518da0a3b28807 1754 devel optional 

Bug#997688: marked as done (rust-bat: FTBFS because of a recent upload)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 16:10:21 +
with message-id 
and subject line re: rust-bat: FTBFS because of a recent upload
has caused the Debian Bug report #997688,
regarding rust-bat: FTBFS because of a recent upload
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.)


-- 
997688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-bat
Severity: important

Dear Maintainer,

This package currently FTBFS with:

  package: sbuild-build-depends-main-dummy
  version: 0.invalid.0
  architecture: amd64
  status: broken
  reasons:
   -
missing:
 pkg:
  package: librust-bindgen+logging-dev
  version: 0.59.1-1
  architecture: amd64
  unsat-dependency: librust-env-logger-0.7+default-dev:amd64
 depchains:
  -
   depchain:
-
 package: sbuild-build-depends-main-dummy
 version: 0.invalid.0
 architecture: amd64
 depends: librust-syntect-3+parsing-dev:amd64 (>= 3.2.1-~~) | 
librust-syntect-3+parsing-dev:amd64 (>= 3.2.1-~~)
-
 package: librust-syntect+parsing-dev
 version: 3.3.0-4
 architecture: amd64
 depends: librust-onig-6+default-dev:amd64 | 
librust-onig-6+default-dev:amd64
-
 package: librust-onig-dev
 version: 6.1.0-1
 architecture: amd64
 depends: librust-onig-sys-69-dev:amd64 (>= 69.5-~~) | 
librust-onig-sys-69-dev:amd64 (>= 69.5-~~)
-
 package: librust-onig-sys-dev
 version: 69.5.1-4
 architecture: amd64
 depends: librust-bindgen-0.59+default-dev:amd64 | 
librust-bindgen-0.59+default-dev:amd64 | librust-bindgen-0.58+default-dev:amd64 
| librust-bindgen-0.57+default-dev:amd64 | 
librust-bindgen-0.56+default-dev:amd64 | librust-bindgen-0.55+default-dev:amd64
-
 package: librust-bindgen+default-dev
 version: 0.59.1-1
 architecture: amd64
 depends: librust-bindgen+logging-dev:amd64 (= 0.59.1-1)

Cheers,

Sylvestre
--- End Message ---
--- Begin Message ---

This bug was fixed by the upload of rust-bindgen 0.59.1-1.1--- End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 16:04:32 +
with message-id 
and subject line Bug#965492: fixed in dlocate 1.09
has caused the Debian Bug report #965492,
regarding dlocate: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: dlocate
Source-Version: 1.09
Done: Craig Sanders 

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

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

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

Debian distribution maintenance software
pp.
Craig Sanders  (supplier of updated dlocate package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 28 Dec 2021 02:44:11 +1100
Source: dlocate
Architecture: source
Version: 1.09
Distribution: unstable
Urgency: medium
Maintainer: Craig Sanders 
Changed-By: Craig Sanders 
Closes: 965492
Changes:
 dlocate (1.09) unstable; urgency=medium
 .
   * forgot to update debian/compat. fixed.  Closes: #965492
Checksums-Sha1:
 e74d317573991858d437c025a2184a82e7a0c8da 1374 dlocate_1.09.dsc
 0c2a6653e8541ab5982299e9eb3f4b98a490a29f 27364 dlocate_1.09.tar.gz
 ef0721487aef7287abc79a7f2c2f5dd805845e57 6248 dlocate_1.09_source.buildinfo
Checksums-Sha256:
 142e4aee638c2d239f760a25a4c39d05e2f252f8613cd9b12339261a21f8e6cf 1374 
dlocate_1.09.dsc
 c81b03765318ac0055e98a4a13566f7b51640516eac79fd05fce549eab0516e9 27364 
dlocate_1.09.tar.gz
 71dd161da74fbab8ed5407f66f7f4f5568e038837013f8812dc0f1194d549296 6248 
dlocate_1.09_source.buildinfo
Files:
 b17e1997ff990d7634b358e3db2734f0 1374 utils optional dlocate_1.09.dsc
 e683e56178c7907cfbcc069c479d8f22 27364 utils optional dlocate_1.09.tar.gz
 0fc91ec1132229d0da16e18e9e0ff5cd 6248 utils optional 
dlocate_1.09_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEiAOqS+GRXKeiEbpiY0kOBV4HdMUFAmHJ4D8ACgkQY0kOBV4H
dMXYFA//d3/AcKljgLzMwyVFdVdVwEm92ct9c9oc2a/RRQSu4Xx/uTg/jZXQlUoa
8ZK4bWFmciqimKNTHhKqvF4yba+KP1jts5a2Sa7796FxrsWr/1YZBpSO3JW6nPal
45SsMQVRAWEU6fiHBT7GBa1xDCIEURNsTDxquSr23q8qtGAvIeNT70icMGbXvev4
YG8Hj5mC62SKTR9CLoGzIqOuMQhemPqfjVPC0DeSRzo9gnzNRJbV/2RW4Lnj9sER
d4XSjddAgwR9ArpneO3hE9D+vWbegYbooXQhoiX7TbUu+vwFRimbdza/p40yzTxl
zqRICbtmboqa+jfGAYwCNqFmnTWzM0d2UuKVEmQKkL0pzi4AxRWhdTgjTkLtxb9w
MF9xpWe43K1dtcy9kOmz4QVy6hMTPgGLpvpygPC4k/FaIySce5QGQK5dcI6E7O2J
4/JLFaHM3wtcjvo5AzUI6nYQ+UWHaPuKCJIz/o8ECpjikML+wJTuaogIOGQ/WZQ3
nqlLtlEn+qXHznnf56IaT86G1F9eCb3+dxTiUfaXIWTJQIbkbHaUICh9ChfM/q5y
TajAGL/ViVorLBKoGjV7a9SKndPn7lPtyR3by+pk2pUbVPFFtKU+aGJW/pIf3i0K
P1OPccCAQI+H+Mtx5E7RGAqQ97zLk607vKt5eUZCfYBWKwmN7Sc=
=FsAq
-END PGP SIGNATURE End Message ---


Bug#1002440: marked as done (python-testtools: FTBFS: testtools.matchers._impl.MismatchError)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 16:05:19 +
with message-id 
and subject line Bug#1002440: fixed in python-testtools 2.5.0-3
has caused the Debian Bug report #1002440,
regarding python-testtools: FTBFS: testtools.matchers._impl.MismatchError
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -ex ; for pyvers in 3.10 3.9; do \
>   PYTHONPATH=/<> PYTHON=python$pyvers python$pyvers -m 
> testtools.run testtools.tests.test_suite ; \
> done
> + PYTHONPATH=/<> PYTHON=python3.10 python3.10 -m testtools.run 
> testtools.tests.test_suite
> /usr/lib/python3.10/runpy.py:126: RuntimeWarning: 'testtools.run' found in 
> sys.modules after import of package 'testtools', but prior to execution of 
> 'testtools.run'; this may result in unpredictable behaviour
>   warn(RuntimeWarning(msg))
> Tests running...
> ==
> FAIL: testtools.tests.test_testresult.TestNonAsciiResults.test_syntax_error
> --
> Traceback (most recent call last):
>   File "/<>/testtools/tests/test_testresult.py", line 2676, in 
> test_syntax_error
> self.assertIn(self._as_output(
>   File "/<>/testtools/testcase.py", line 399, in assertIn
> self.assertThat(haystack, Contains(needle), message)
>   File "/<>/testtools/testcase.py", line 480, in assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: '  File "", line 1\nf(a, 
> b c)\n ^\nSyntaxError: ' not in 'Tests 
> running...\n==\nERROR:
>  
> test_syntax_error.Test.runTest\n--\nTraceback
>  (most recent call last):\n  File 
> "/tmp/TestNonAsciiResults07m6k1o1/test_syntax_error.py", line 6, in runTest\n 
>exec (\'f(a, b c)\')\n  File "", line 1\nf(a, b c)\n 
> ^^^\nSyntaxError: invalid syntax. Perhaps you forgot a comma?\n\nRan 1 test 
> in 0.001s\nFAILED (failures=1)\n'
> ==
> FAIL: 
> testtools.tests.test_testresult.TestNonAsciiResultsWithUnittest.test_syntax_error
> --
> Traceback (most recent call last):
>   File "/<>/testtools/tests/test_testresult.py", line 2676, in 
> test_syntax_error
> self.assertIn(self._as_output(
>   File "/<>/testtools/testcase.py", line 399, in assertIn
> self.assertThat(haystack, Contains(needle), message)
>   File "/<>/testtools/testcase.py", line 480, in assertThat
> raise mismatch_error
> testtools.matchers._impl.MismatchError: '  File "", line 1\nf(a, 
> b c)\n ^\nSyntaxError: ' not in 
> 'E\n==\nERROR:
>  runTest 
> (test_syntax_error.Test)\ntest_syntax_error.Test.runTest\n--\ntesttools.testresult.real._StringException:
>  Traceback (most recent call last):\n  File 
> "/tmp/TestNonAsciiResultsWithUnittestwnxlmk1_/test_syntax_error.py", line 6, 
> in runTest\nexec (\'f(a, b c)\')\n  File "", line 1\nf(a, b 
> c)\n ^^^\nSyntaxError: invalid syntax. Perhaps you forgot a 
> comma?\n\n\n--\nRan
>  1 test in 0.000s\n\nFAILED (errors=1)\n'
> 
> Ran 2625 tests in 0.376s
> FAILED (failures=2)
> make[1]: *** [debian/rules:36: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/python-testtools_2.5.0-2_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, 

Bug#1002582: marked as done (RFS: gcc-sh-elf/2 [RC] -- GNU C compiler for embedded SuperH devices)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 16:59:23 +0100
with message-id 
and subject line Re: RFS: gcc-sh-elf/2 [RC] -- GNU C compiler for embedded 
SuperH devices
has caused the Debian Bug report #1002582,
regarding RFS: gcc-sh-elf/2 [RC] -- GNU C compiler for embedded SuperH devices
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.)


-- 
1002582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: pkg-electronics-de...@alioth-lists.debian.net

Dear mentors and Electronics Team,

I'm looking for a sponsor for my package "gcc-sh-elf":

 * Package name    : gcc-sh-elf
   Version : 2 (this is a native package)
 * License : GPL-3+
 * Vcs : 
https://salsa.debian.org/electronics-team/toolchains/gcc-sh-elf
   Section : devel

It builds those binary packages:

  gcc-sh-elf - GNU C compiler for embedded SuperH devices
  libnewlib-sh-elf-dev - small ISO C standard library for embedded
SuperH devices

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/gcc-sh-elf/

Alternatively, one can download the package with dget using this
command:

  dget -x
https://mentors.debian.net/debian/pool/main/g/gcc-sh-elf/gcc-sh-elf_2.dsc

Changes since the last upload:

 gcc-sh-elf (2) unstable; urgency=medium
 .
   * Disable building libcc1, which is superfluous. (Closes: #1001273)
   * Make new source-only upload to enable testing migration.

In addition, I marked gcc-sh-elf Multi-Arch: foreign and set the
homepages for the respective binary packages instead of the source
package since we build Newlib as well.

There are no regressions in the GCC test suite; there seem to be 42
unique failures (on amd64 and arm64 at least) as determined by
grep -E "^FAIL" ../buildlog.txt | cut -d ' ' -f 2 | uniq | wc -
l
and these are the same ones as for the first upload with GCC 11.2.0-12.
The autopkgtests are numerous and still passing and I don't anticipate
any issues with this building on all architectures as it has before.

Thanks,
John


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

Hi John,

I have just uploaded your new package revision.
Thanks for provding it.

Cheers,
Bastian--- End Message ---


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

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 15:50:08 +
with message-id 
and subject line Bug#999302: fixed in fortunes-bg 1.4
has caused the Debian Bug report #999302,
regarding fortunes-bg: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: fortunes-bg
Source-Version: 1.4
Done: Anton Zinoviev 

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

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

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

Debian distribution maintenance software
pp.
Anton Zinoviev  (supplier of updated fortunes-bg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Dec 2021 17:07:15 +0200
Source: fortunes-bg
Architecture: source
Version: 1.4
Distribution: unstable
Urgency: medium
Maintainer: Anton Zinoviev 
Changed-By: Anton Zinoviev 
Closes: 999302
Changes:
 fortunes-bg (1.4) unstable; urgency=medium
 .
   * debian/rules: add build-indep and build-arch targets, closes: #999302.
   * Raise Standards-Version to 4.5.0.
Checksums-Sha1:
 b5ce9c620dc0d2f592f5a7fcba0f3e5fb0b87d81 1411 fortunes-bg_1.4.dsc
 432e1603d7fa0aac29e49706b9be4e4717102b1e 67927 fortunes-bg_1.4.tar.gz
 da054179180f269b91fd27d41c7ef0b3850f3bdc 4663 fortunes-bg_1.4_source.buildinfo
Checksums-Sha256:
 2497431018f28a8da78b035db93262b71ec17794027deb082f7068bf4932462c 1411 
fortunes-bg_1.4.dsc
 02fe7ff2736733b1fbcb3eaf49ff3b4318ab6ff5a53dbf21fb0672f2f117fc93 67927 
fortunes-bg_1.4.tar.gz
 dc0cb88e65b7ef28bd375a3403c3365895b99278aede0914e35bc4041aa67e09 4663 
fortunes-bg_1.4_source.buildinfo
Files:
 23d134e31cd37ed88068174f1705fedd 1411 games optional fortunes-bg_1.4.dsc
 2f837e0d61bd57a3fd11850d1af5452c 67927 games optional fortunes-bg_1.4.tar.gz
 28c3e466f0fcb820f618292eb096cfd8 4663 games optional 
fortunes-bg_1.4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEicc1SOihLZMLEYmNk7cW45P7GKYFAmHJ3AcACgkQk7cW45P7
GKbO+BAAiv+Z/5t8y1LtBAh0JLOdlEYnLkGGdtgis3ksXJSHKhkb/Zhgvk0J4NKQ
KiFnQrDwgbKcLD20hpvxawappNpbebyP0nZP16dwFzNn9yicHq53i/92/lWp80M+
siKkyk8qFIvWGQoQ44nGDgNEXHD0XkF1Yt3TL31vP73ftkLELXK+c/IXxeXqgCeA
tTDyC+SczFKEGUXJ1d82uKU9rC92I/egiPnYnWqoY0IAtTbV+I91FlfIqD3ZEIXJ
cuzU3ZZqudMpRdTnIavPYrs6Ez4p+8lng/UUdQjPFl+e/RzUR4AiSMGqXJLJGqaD
JU7BXmCHPouFlMK06JveZogyYldi9yClwk/s2mK/hP3SnDBl21RUckCrNOmNHsS3
mox/8pA9QAcIkB7lCBOChCpRPkgZNGc+7/i5G+2yBjSFIOmuM/qcAUmHydmo5fty
igj6giTIrbO6UsXGiHbrztcF4HIVPP1XnvVkn4QPg2QITgaCgzaWXW2RFWwhAp59
oGwMiaxggfYZ8WnUdrN1e2F07fvccsZeKJ2n9WDH1d9QhINOhuSoB8JQgvSv/0Fg
cqQQpTULg7pmNYNzFUvnemE68HEgj8UhJAtxsfwlJw5+1JZJ3M9rAtf6J3nUwlB9
I3WvsyNcr2ZeeSivrGXDeSHTdm+T0T+6VgfuMKGecH6BODf98NI=
=reX0
-END PGP SIGNATURE End Message ---


Bug#988635: marked as done (keystone: Keystone missing sso_callback_template.html)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 16:48:46 +0100
with message-id <8ca155b1-ac19-face-8001-5d463a329...@debian.org>
and subject line This was fixed earlier
has caused the Debian Bug report #988635,
regarding keystone: Keystone missing sso_callback_template.html
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.)


-- 
988635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: keystone
Version: 2:18.0.0-3
Severity: normal

Dear Maintainer,

Keystone package is missing sso_callback_template.html in /etc/keystone as it's 
documented in upstream,
because it's missing keystone with federation is not working. More precisely 
said,
redirect does not work to the external authentication mechanism.

This is fixed in experimental in version 2:19.0.0-2.

Some links:
- https://github.com/openstack/keystone/tree/master/etc


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

Kernel: Linux 4.19.0-8-amd64 (SMP w/32 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
This was fixed earlier, closing this bug.--- End Message ---


Bug#994914: marked as done (python-autobahn: Please package new upstream release of autobahn)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 16:39:18 +0100
with message-id <37ca675b-d7c2-08c9-1204-89c2aa112...@debian.org>
and subject line Fixed
has caused the Debian Bug report #994914,
regarding python-autobahn: Please package new upstream release of autobahn
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.)


-- 
994914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-autobahn
Severity: wishlist

Dear Maintainer,

We are working on to reintroduce tahoe-lafs to Debian since a new version
with python3 support has been release. New version need autobahn >= 19.5.2. 

Can you please consider updating the package to latest upstream release so we 
will be
unblocked on introducing tahoe again to Debian.

Thanks and Regards,
Vasudev

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

Kernel: Linux 5.14.0-trunk-amd64 (SMP w/8 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
--- End Message ---
--- Begin Message ---
Fixed--- End Message ---


Bug#979503: marked as done (python-django-compressor: Make dependency on calmjs optional at runtime)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 16:38:41 +0100
with message-id 
and subject line Wont fix no bug
has caused the Debian Bug report #979503,
regarding python-django-compressor: Make dependency on calmjs optional at 
runtime
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.)


-- 
979503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django-compressor
Version: 2.4-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Dear Maintainer,

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

  * d/control: Drop runtime dependency on python-calmjs to a Suggests
as it is an optional dependency and rjsmin already provides the
default JS minifier implementation.

Thanks for considering the patch.


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

Kernel: Linux 5.8.0-33-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru python-django-compressor-2.4/debian/control 
python-django-compressor-2.4/debian/control
--- python-django-compressor-2.4/debian/control 2020-10-14 10:14:55.0 
+0100
+++ python-django-compressor-2.4/debian/control 2021-01-07 10:13:16.0 
+
@@ -39,7 +39,6 @@
 Architecture: all
 Depends:
  python3-csscompressor (>= 0.9.5),
- python3-calmjs,
  python3-django,
  python3-django-appconf (>= 1.0.3),
  python3-rcssmin,
@@ -47,6 +46,8 @@
  python3-six,
  ${misc:Depends},
  ${python3:Depends},
+Suggests:
+ python3-calmjs,
 Description: Compresses linked, inline JS or CSS into single cached files - 
Python 3.x
  Django Compressor combines and compresses linked and inline Javascript or CSS
  in a Django templates into cacheable static files by using the compress
--- End Message ---
--- Begin Message ---
Wont fix no bug--- End Message ---


Bug#1001650: marked as done (src:clutter-1.0: fails to migrate to testing for too long: FTBFS on mips64el)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 15:33:30 +
with message-id 
and subject line Bug#1001650: fixed in clutter-1.0 1.26.4+dfsg-4
has caused the Debian Bug report #1001650,
regarding src:clutter-1.0: fails to migrate to testing for too long: FTBFS on 
mips64el
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.)


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

Source: clutter-1.0
Version: 1.26.4+dfsg-2
Severity: serious
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:clutter-1.0 has been trying to migrate for 
61 days [2]. Hence, I am filing this bug. There are segfaults during 
some of its tests that are part of its build on mip64el for the latest 
upload.


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


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


I have tagged this bug to only affect sid and bookworm, so it doesn't 
affect (old-)stable.


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: clutter-1.0
Source-Version: 1.26.4+dfsg-4
Done: Simon McVittie 

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated clutter-1.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Dec 2021 14:36:36 +
Source: clutter-1.0
Architecture: source
Version: 1.26.4+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1001650
Changes:
 clutter-1.0 (1.26.4+dfsg-4) unstable; urgency=medium
 .
   * Team upload
   * Revert "d/rules: Stop ignoring test results on mips*el".
 Workaround for #1002690. (Closes: #1001650)
Checksums-Sha1:
 62380e33be2e17d7cfee72e6fea5fccb32aafbca 3622 clutter-1.0_1.26.4+dfsg-4.dsc
 377db816d372bfa95dbf3424b3d200f7005bc0e0 23464 
clutter-1.0_1.26.4+dfsg-4.debian.tar.xz
 7194d78a20838a33d0d711c491c00324d32ebe0d 15025 
clutter-1.0_1.26.4+dfsg-4_source.buildinfo
Checksums-Sha256:
 cca04efd0d92c826e77fa2d5d92a1562fc9324591b2007b417a2cd8385714c43 3622 
clutter-1.0_1.26.4+dfsg-4.dsc
 2d3855febbd337b62513912542e1f785866902ceefe88d95f4e19ee11d2bd3f3 23464 
clutter-1.0_1.26.4+dfsg-4.debian.tar.xz
 1566a8e03ce911d33c7027261c5ada66fb83c2c899ade045b8cca07dea858028 15025 
clutter-1.0_1.26.4+dfsg-4_source.buildinfo
Files:
 a21b837bbddd29b0c2aabd9cdc6dbbca 3622 libs optional 
clutter-1.0_1.26.4+dfsg-4.dsc
 067024fd6564fa8cac1510b337cfae6f 23464 libs optional 
clutter-1.0_1.26.4+dfsg-4.debian.tar.xz
 d4f3569fc8127dc27673bcd5965b75e5 15025 libs optional 
clutter-1.0_1.26.4+dfsg-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmHJ10sACgkQ4FrhR4+B
TE8EWA//Z5kKNHv09IMJHLARQmy5j94Tg6HaSZzcNsiGvXtQ4zimtOKM6nw3PQUl
RhDyqv4HKVURnNtLcKuwRH8ikgLdSXo7ovIzFAvZX6DEwvRky6QLDBp8nEatMWrj
PWGcWX8t3FuhmqK3r8sf5DpPhoEuH14La7eHFSZqpvihTI2/dvffmu7AthVSaGFn

Bug#986182: marked as done (zaqar-common: fails to install: install: cannot stat '/usr/share/zaqar-common/policy.json': No such file or directory)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 15:19:42 +
with message-id 
and subject line Bug#986182: fixed in zaqar 13.0.0-2
has caused the Debian Bug report #986182,
regarding zaqar-common: fails to install: install: cannot stat 
'/usr/share/zaqar-common/policy.json': No such file or directory
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.)


-- 
986182: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zaqar-common
Version: 12.0.0~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up zaqar-common (12.0.0~rc1-1) ...
  install: cannot stat '/usr/share/zaqar-common/policy.json': No such file or 
directory
  dpkg: error processing package zaqar-common (--configure):
   installed zaqar-common package post-installation script subprocess returned 
error exit status 1


cheers,

Andreas


zaqar-common_12.0.0~rc1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: zaqar
Source-Version: 13.0.0-2
Done: Thomas Goirand 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Dec 2021 15:55:16 +0100
Source: zaqar
Architecture: source
Version: 13.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 986182
Changes:
 zaqar (13.0.0-2) unstable; urgency=medium
 .
   * Do not pkgos_write_new_conf ${PROJECT_NAME} policy.json (Closes: #986182).
Checksums-Sha1:
 1b84468dadfd746ecdf39e5e41a0362c232f7d2f 3141 zaqar_13.0.0-2.dsc
 69ee1c6257ddbdcc06f6feac1fbfa1e27f0adb7e 7992 zaqar_13.0.0-2.debian.tar.xz
 561078ac45a17640cead9376fbbff9f2986569df 15817 zaqar_13.0.0-2_amd64.buildinfo
Checksums-Sha256:
 06e52a62c1d5d4dc1d9fb65caeedda140ac512a6646f8fe9b9bc706860c6d11d 3141 
zaqar_13.0.0-2.dsc
 b18c7049b315521419b2e76e83552d8e234f874281e8732358d5225e3e1dcb8d 7992 
zaqar_13.0.0-2.debian.tar.xz
 965b3503195ae50903666b6604d0c042f86a6438dcd0f8f46af15f77258f690e 15817 
zaqar_13.0.0-2_amd64.buildinfo
Files:
 8ebfda0ee19fcb34901c81657b730966 3141 net optional zaqar_13.0.0-2.dsc
 f269d34792cbdc4385ac38d8b4c1af69 7992 net optional zaqar_13.0.0-2.debian.tar.xz
 4fa96843624a1f757a8c8c2fb25118ee 15817 net optional 
zaqar_13.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmHJ1TsACgkQ1BatFaxr
Q/7Qyw/9HQxSKqsk73ILhdOR16sq0Kkmgo+JErPtifZHHO93dJbwExETMVX/da5o
GD4BDXM3sWw3Nwp3gmHCEf17ZDLQU0eA7T1nVdvAMKVqnQyy4lrEgFRcDJtWdhwj
gQFfRQ6xC0sNPAq1ndqV9bBMFA/vjOM/T57wgNDGAMRbLzilSA5MoPHJz4ImqJk8
UtjQniiWhJRuUfrAHk3JvC/6GQambXogrnrHZMhlmUrsU/qO6q/8YSb3z1sFKZc1
iSjWYg1XJ1NFzjJJqfZL8cSVKTRMc1nIonh9+ss77s85D/3Wd7ykLzdDkByi9H8E
RuVg9NdS2IFOwz3HsCq0642R+Ybu/MpKLspZ6fwOG9/aNAYUjLkO9Zk9f1rmdBVH
IpF63uaPd8sQPVLFyfv8SUMDUqQiWT9wZbPLSRiZvqxDh1IEXbbZAqxZSFETMQao
L4n+AUdb1qt83OfzYZ/r4DwfOdVUe+XQTCZVgbPtcFbeE/3UW5Dy3H1wcbrHC8bP
ngXahboxiZLecS29Bk6RppkVxgIApf4snMW24IN4jC/TeG0iPjmIX8kuadJx4QCW
gmpygcM7d14PAewh4fM0ZlLEejTumwEfuOjitQNzQyBKUlKNqgrlc6E+amwnTpha
2pMOpPotFgquSL70aRhdo038zR/MIC1UX9QaQyVadXib13yeYLI=
=Uiz0
-END PGP SIGNATURE End Message ---


Bug#979510: marked as done (python-sqlalchemy-utils: infinity and psycopg2cffi shouldn't be installed by default with sqlalchemy-utils)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 16:03:40 +0100
with message-id <05145f5b-1171-4a08-94a9-d512de40d...@debian.org>
and subject line Wont fix
has caused the Debian Bug report #979510,
regarding python-sqlalchemy-utils: infinity and psycopg2cffi shouldn't be 
installed by default with sqlalchemy-utils
to be marked as done.

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

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


-- 
979510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-sqlalchemy-utils
Version: 0.36.8-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch

Dear Maintainer,

Installing sqlalchemy-utils currently also installs infinity and psycopg2cffi,
two python libraries that are considered optional in the upstream source of
sqlalchemy-utils. It would be better to have them be Suggests instead so that
a user can include them if desired but isn't forced.

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

  * d/control: Make infinity and psycopq2cffi optional as they are not
required for proper functionality and are considered optional upstream.

Thanks for considering the patch.


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

Kernel: Linux 5.8.0-31-generic (SMP w/6 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 python-sqlalchemy-utils-0.36.8/debian/control 
python-sqlalchemy-utils-0.36.8/debian/control
--- python-sqlalchemy-utils-0.36.8/debian/control   2020-12-04 
23:02:16.0 +
+++ python-sqlalchemy-utils-0.36.8/debian/control   2021-01-07 
13:52:13.0 +
@@ -49,13 +49,13 @@
  python3-anyjson,
  python3-arrow,
  python3-babel,
- python3-infinity,
- python3-psycopg2cffi,
  python3-six,
  python3-sqlalchemy,
  ${misc:Depends},
  ${python3:Depends},
 Suggests:
+ python3-infinity,
+ python3-psycopg2cffi,
  python-sqlalchemy-utils-doc,
 Description: various utility functions for SQLAlchemy - Python 3.x
  Various utility functions and custom data types for SQLAlchemy.
--- End Message ---
--- Begin Message ---
Wont fix this in Debian.

Thomas--- End Message ---


Bug#989720: marked as done (openvswitch-switch: /etc/network/interfaces seems ignored)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 15:51:38 +0100
with message-id <97d6aa63-1a9b-e044-39e6-034d2f14b...@debian.org>
and subject line No need for a fix
has caused the Debian Bug report #989720,
regarding openvswitch-switch: /etc/network/interfaces seems ignored
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.)


-- 
989720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openvswitch-switch
Version: 2.15.0+ds1-2
Severity: important
X-Debbugs-Cc: dspil...@datatipp.se

As of 2.15.0+ds1-2 in Bullseye definitions of bridges and ports in 
/etc/network/interfaces seem ignored. Here is an example interfaces file 
which worked fine on Buster with openvswitch-switch 2.10.7+ds1-0+deb10u1:

###
allow-ovs br0
iface br0 inet manual
 ovs_type OVSBridge
 ovs_ports enp7s0 vlan1

allow-br0 enp7s0
iface enp7s0 inet manual
 ovs_bridge br0
 ovs_type OVSPort

allow-br0 vlan1
iface vlan1 inet manual
ovs_bridge br0
ovs_type OVSIntPort
ovs_options tag=1
###

The above should create a bridge (br0) with a port (vlan1):

4: ovs-system:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
link/ether c2:62:99:b6:2c:f4 brd ff:ff:ff:ff:ff:ff
5: br0:  mtu 1500 qdisc noqueue state 
UNKNOWN mode DEFAULT group default qlen 1000
link/ether 32:87:cc:b7:40:4f brd ff:ff:ff:ff:ff:ff
6: vlan1:  mtu 1500 qdisc noqueue state 
UNKNOWN mode DEFAULT group default qlen 1000
link/ether 72:f3:8a:99:f7:06 brd ff:ff:ff:ff:ff:ff


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

Kernel: Linux 5.10.0-7-amd64 (SMP w/16 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=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openvswitch-switch depends on:
ii  kmod28-1
ii  lsb-base11.1.0
ii  netbase 6.3
ii  openvswitch-common  2.15.0+ds1-2
ii  procps  2:3.3.17-5
ii  uuid-runtime2.36.1-7

openvswitch-switch recommends no packages.

openvswitch-switch suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

Using auto fixes the issue, so I'm closing this bug.

Cheers,

Thomas Goirand (zigo)--- End Message ---


Bug#1002680: marked as done (Fails to build)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 14:33:56 +
with message-id 
and subject line Bug#1002680: fixed in openrazer 3.2.0+dfsg-3
has caused the Debian Bug report #1002680,
regarding Fails to build
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.)


-- 
1002680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openrazer-driver-dkms
Version: 3.2.0+dfsg-2
Severity: grave

Justification for "grave": Package rendered completely unusable due to
failure to compile module.

There's a () unbalance in the fix for #1002530. Here's the make.log:


DKMS make.log for openrazer-driver-3.2.0 for kernel 5.15.0-2-amd64 (x86_64)
Mon Dec 27 00:18:03 PST 2021
-e 
:: Compiling OpenRazer kernel modules

make -C /lib/modules/5.15.0-2-amd64/build 
M=/var/lib/dkms/openrazer-driver/3.2.0/build/driver modules
make[1]: Entering directory '/usr/src/linux-headers-5.15.0-2-amd64'
  CC [M]  /var/lib/dkms/openrazer-driver/3.2.0/build/driver/razerkbd_driver.o
/var/lib/dkms/openrazer-driver/3.2.0/build/driver/razerkbd_driver.c:26:80: 
error: missing '(' in expression
   26 | #if defined(CONFIG_HIDRAW) && defined(CONFIG_USB) || 
defined(CONFIG_USB_MODULE))
  | 
   ^
In file included from 
/var/lib/dkms/openrazer-driver/3.2.0/build/driver/razerkbd_driver.c:32:
/var/lib/dkms/openrazer-driver/3.2.0/build/driver/razercommon.h:29:80: error: 
missing '(' in expression
   29 | #if defined(CONFIG_HIDRAW) && defined(CONFIG_USB) || 
defined(CONFIG_USB_MODULE))
  | 
   ^
/var/lib/dkms/openrazer-driver/3.2.0/build/driver/razerkbd_driver.c:34:80: 
error: missing '(' in expression
   34 | #if defined(CONFIG_HIDRAW) && defined(CONFIG_USB) || 
defined(CONFIG_USB_MODULE))
  | 
   ^
/var/lib/dkms/openrazer-driver/3.2.0/build/driver/razerkbd_driver.c:50:80: 
error: missing '(' in expression
   50 | #if defined(CONFIG_HIDRAW) && defined(CONFIG_USB) || 
defined(CONFIG_USB_MODULE))
  | 
   ^
make[2]: *** 
[/usr/src/linux-headers-5.15.0-2-common/scripts/Makefile.build:282: 
/var/lib/dkms/openrazer-driver/3.2.0/build/driver/razerkbd_driver.o] Error 1
make[1]: *** [/usr/src/linux-headers-5.15.0-2-common/Makefile:1892: 
/var/lib/dkms/openrazer-driver/3.2.0/build/driver] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.15.0-2-amd64'
make: *** [Makefile:41: driver] Error 2


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/16 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

Versions of packages openrazer-driver-dkms depends on:
ii  dkms  2.8.7-2
ii  udev  249.7-1

openrazer-driver-dkms recommends no packages.

openrazer-driver-dkms suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openrazer
Source-Version: 3.2.0+dfsg-3
Done: Dylan Aïssi 

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

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

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

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated openrazer 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: Mon, 27 Dec 2021 15:18:09 +0100
Source: openrazer
Architecture: source
Version: 3.2.0+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Dylan Aïssi 
Changed-By: Dylan Aïssi 
Closes: 1002680
Changes:
 openrazer (3.2.0+dfsg-3) unstable; urgency=medium
 .
   * Fix syntax in 

Bug#1002403: marked as done (dput-ng: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.10 3.9" returned exit code 13)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 13:52:40 +
with message-id 
and subject line Bug#1002403: fixed in dput-ng 1.34
has caused the Debian Bug report #1002403,
regarding dput-ng: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
python{version} -p "3.10 3.9" returned exit code 13
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> sphinx-build -b html -W -d _build/doctrees   . _build/html
> Running Sphinx v4.3.2
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 36 source files that are out of date
> updating environment: [new config] 36 added, 0 changed, 0 removed
> reading sources... [  2%] index
> reading sources... [  5%] library/changes
> reading sources... [  8%] library/config
> reading sources... [ 11%] library/configs/dputcf
> reading sources... [ 13%] library/configs/dputng
> reading sources... [ 16%] library/configs/index
> reading sources... [ 19%] library/core
> reading sources... [ 22%] library/exceptions
> reading sources... [ 25%] library/hooks
> reading sources... [ 27%] library/hooks/checksum
> reading sources... [ 30%] library/hooks/deb
> reading sources... [ 33%] library/hooks/distribution
> reading sources... [ 36%] library/hooks/gpg
> reading sources... [ 38%] library/hooks/impatient
> reading sources... [ 41%] library/hooks/index
> reading sources... [ 44%] library/hooks/lintian
> reading sources... [ 47%] library/index
> reading sources... [ 50%] library/interface
> reading sources... [ 52%] library/interfaces/clinterface
> reading sources... [ 55%] library/interfaces/index
> reading sources... [ 58%] library/overrides
> reading sources... [ 61%] library/profile
> reading sources... [ 63%] library/uploader
> reading sources... [ 66%] library/uploaders/ftp
> reading sources... [ 69%] library/uploaders/http
> reading sources... [ 72%] library/uploaders/index
> reading sources... [ 75%] library/uploaders/local
> reading sources... [ 77%] library/uploaders/scp
> reading sources... [ 80%] library/uploaders/sftp
> reading sources... [ 83%] library/util
> reading sources... [ 86%] reference/configs
> reading sources... [ 88%] reference/contributing
> reading sources... [ 91%] reference/hookinstall
> reading sources... [ 94%] reference/hooks
> reading sources... [ 97%] reference/index
> reading sources... [100%] reference/migrating
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> writing output... [  2%] index
> writing output... [  5%] library/changes
> writing output... [  8%] library/config
> writing output... [ 11%] library/configs/dputcf
> writing output... [ 13%] library/configs/dputng
> writing output... [ 16%] library/configs/index
> writing output... [ 19%] library/core
> writing output... [ 22%] library/exceptions
> writing output... [ 25%] library/hooks
> writing output... [ 27%] library/hooks/checksum
> writing output... [ 30%] library/hooks/deb
> writing output... [ 33%] library/hooks/distribution
> writing output... [ 36%] library/hooks/gpg
> writing output... [ 38%] library/hooks/impatient
> writing output... [ 41%] library/hooks/index
> writing output... [ 44%] library/hooks/lintian
> writing output... [ 47%] library/index
> writing output... [ 50%] library/interface
> writing output... [ 52%] library/interfaces/clinterface
> writing output... [ 55%] library/interfaces/index
> writing output... [ 58%] library/overrides
> writing output... [ 61%] library/profile
> writing output... [ 63%] library/uploader
> writing output... [ 66%] library/uploaders/ftp
> writing output... [ 69%] library/uploaders/http
> writing output... [ 72%] library/uploaders/index
> writing output... [ 75%] library/uploaders/local
> writing output... [ 77%] library/uploaders/scp
> writing output... [ 80%] library/uploaders/sftp
> writing output... [ 83%] library/util
> writing output... [ 86%] reference/configs
> writing output... [ 88%] reference/contributing
> writing output... [ 91%] reference/hookinstall
> writing output... [ 94%] reference/hooks
> writing output... [ 97%] 

Bug#977939: marked as done (linux-base: [INTL:de] updated German man page translation)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 12:33:58 +
with message-id 
and subject line Bug#977939: fixed in linux-base 4.7
has caused the Debian Bug report #977939,
regarding linux-base: [INTL:de] updated German man page translation
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.)


-- 
977939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-base
Version: 4.6
Severity: wishlist
Tags: patch l10n

Please find the updated German man page translation for linux-base
attached.

If you update your template, please use 
'msgfmt --statistics '
to check the po-files for fuzzy or untranslated strings.

If there are such strings, please contact me so I can update the 
German translation.

Greetings
Helge
# Translation of the linux-base documentation to German.
# Copyright (C) 1996-2006 Manoj Srivastava.
# This file is distributed under the GPL version 2 or later.
# Copyright (C) of this file 2011, 2012 Chris Leick.
# Helge Kreutzmann , 2020.
#
msgid ""
msgstr ""
"Project-Id-Version: linux-base 4.6\n"
"Report-Msgid-Bugs-To: linux-b...@packages.debian.org\n"
"POT-Creation-Date: 2019-03-24 21:37+\n"
"PO-Revision-Date: 2020-12-23 07:39+0100\n"
"Last-Translator: Ben Hutchings \n"
"Language-Team: German \n"
"Language: de\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. type: TH
#: man/kernel-img.conf.5:25
#, no-wrap
msgid "KERNEL-IMG.CONF"
msgstr "KERNEL-IMG.CONF"

#. type: TH
#: man/kernel-img.conf.5:25
#, no-wrap
msgid "24 March 2019"
msgstr "24. März 2019"

#. type: TH
#: man/kernel-img.conf.5:25
#, no-wrap
msgid "Debian"
msgstr "Debian"

#. type: TH
#: man/kernel-img.conf.5:25
#, no-wrap
msgid "Debian GNU/Linux manual"
msgstr "Debian-GNU/Linux-Handbuch"

#.  NAME should be all caps, SECTION should be 1-8, maybe w/ subsection
#.  other parms are allowed: see man(7), man(1)
#. type: SH
#: man/kernel-img.conf.5:28
#, no-wrap
msgid "NAME"
msgstr "BEZEICHNUNG"

#. type: Plain text
#: man/kernel-img.conf.5:30
msgid "kernel-img.conf - configuration file for Linux kernel packages"
msgstr "kernel-img.conf - Konfigurationsdatei für Linux-Kernel-Image-Pakete"

#. type: SH
#: man/kernel-img.conf.5:30
#, no-wrap
msgid "SYNOPSIS"
msgstr "ÜBERSICHT"

#. type: Plain text
#: man/kernel-img.conf.5:32
msgid "I"
msgstr "I"

#. type: SH
#: man/kernel-img.conf.5:32
#, no-wrap
msgid "DESCRIPTION"
msgstr "BESCHREIBUNG"

#. type: Plain text
#: man/kernel-img.conf.5:38
msgid ""
"The file I is used by the kernel package installation "
"and removal process to allow local options for handling some aspects of the "
"installation.  Most configuration variables apply only to kernel image "
"packages."
msgstr ""
"Die Datei I wird von dem Kernelpaket-Installations- "
"und -Entfernungsprozess verwandt, um lokale Optionen "
"zu ermöglichen, die einige Aspekte der Installation behandeln. Die meisten "
"Konfigurationsvariablen gelten nur für Kernel-Abbild-Pakete."

#. type: Plain text
#: man/kernel-img.conf.5:41
msgid ""
"Not all kernel image package creators support this file, or all the "
"configuration variables.  Support status for the file itself is:"
msgstr ""
"Nicht alle Erstellprogramme für Kernelabbilder unterstützen diese Datei oder "
"alle Konfigurationsvariablen. Der Unterstützungsstatus für die Datei selbst "
"ist wie folgt:"

#. type: tbl table
#: man/kernel-img.conf.5:44 man/kernel-img.conf.5:74 man/kernel-img.conf.5:88
#: man/kernel-img.conf.5:102 man/kernel-img.conf.5:142
#: man/kernel-img.conf.5:177 man/kernel-img.conf.5:207
#: man/kernel-img.conf.5:242 man/kernel-img.conf.5:275
#: man/kernel-img.conf.5:304 man/kernel-img.conf.5:319
#: man/kernel-img.conf.5:337 man/kernel-img.conf.5:352
#: man/kernel-img.conf.5:367 man/kernel-img.conf.5:380
#: man/kernel-img.conf.5:402 man/kernel-img.conf.5:416
#, no-wrap
msgid "B"
msgstr "B"

#. type: tbl table
#: man/kernel-img.conf.5:44 man/kernel-img.conf.5:74 man/kernel-img.conf.5:88
#: man/kernel-img.conf.5:102 man/kernel-img.conf.5:142
#: man/kernel-img.conf.5:177 man/kernel-img.conf.5:207
#: man/kernel-img.conf.5:242 man/kernel-img.conf.5:275
#: man/kernel-img.conf.5:304 man/kernel-img.conf.5:319
#: man/kernel-img.conf.5:337 man/kernel-img.conf.5:352
#: man/kernel-img.conf.5:367 man/kernel-img.conf.5:380
#: man/kernel-img.conf.5:402 man/kernel-img.conf.5:416
#, no-wrap
msgid "B"
msgstr "B"

#. type: tbl table
#: man/kernel-img.conf.5:45 man/kernel-img.conf.5:75 man/kernel-img.conf.5:89
#: 

Bug#931506: marked as done (linux-base: "are are" in man 1 perf)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 12:33:58 +
with message-id 
and subject line Bug#931506: fixed in linux-base 4.7
has caused the Debian Bug report #931506,
regarding linux-base: "are are" in man 1 perf
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.)


-- 
931506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-base
Version: 4.6
Severity: minor
Tags: patch

Errors in man 1 perf. See patch in the end of the report.

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-7-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages linux-base depends on:
ii  debconf [debconf-2.0]  1.5.72

linux-base recommends no packages.

linux-base suggests no packages.

-- debconf information:
  linux-base/removing-title:
  linux-base/removing-running-kernel: true

--- a/man/perf.1
+++ b/man/perf.1
@@ -6,8 +6,8 @@ perf \- performance analysis tools for Linux
 \fBperf\fR [\fB\-\-version\fR] [\fB\-\-help\fR] \fICOMMAND\fR [\fIARGS\fR]
 .SH DESCRIPTION
 .LP
-Performance counters for Linux are are a new kernel\-based subsystem
-that provide a framework for all things performance analysis.  It
+Performance counters for Linux are a new kernel\-based subsystem
+that provide a framework for performance analysis.  It
 covers hardware level (CPU/PMU, Performance Monitoring Unit) features
 and software features (software counters, tracepoints) as well.
 .LP
--- End Message ---
--- Begin Message ---
Source: linux-base
Source-Version: 4.7
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated linux-base 
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: Mon, 27 Dec 2021 13:21:16 +0100
Source: linux-base
Architecture: source
Version: 4.7
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Salvatore Bonaccorso 
Closes: 931506 977939
Changes:
 linux-base (4.7) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * man: perf.1: Remove doubled word 'are' in manpage.
 Thanks to Ivan Kharpalev for the report and patch (Closes: #931506)
   * po: de.po: Updated German man page translation.
 Thanks to Helge Kreutzmann (Closes: #977939)
   * Set Rules-Requires-Root to no
   * Annotate test-only build dependencies with 
   * debian/copyright: Convert to machine-readable format 1.0
   * Declare compliance with Debian policy 4.6.0
   * postinst: Use 'set -e' in script body instead of passing -e to shell in
 shebang line
   * Add myself to Uploaders
 .
   [ Debian Janitor ]
   * Bump debhelper from deprecated 9 to 13.
   * Set debhelper-compat version in Build-Depends.
Checksums-Sha1: 
 7a638c5d0552dec5396eba06d2a9759c59879a53 1842 linux-base_4.7.dsc
 0ec2dc6c00da6ef94f0cc9ffbf35032bcaba1c1a 33700 linux-base_4.7.tar.xz
Checksums-Sha256: 
 182fa557534467c801f4c024ef618eb82a37ec6bd876c2414ca922cdca097cb9 1842 
linux-base_4.7.dsc
 5776701ea0ef1dce2a60dec0ce1444afef68edcb5fed28980259fe9ff31e6b64 33700 
linux-base_4.7.tar.xz
Files: 
 8c26a057ff1603e995efbc783b9a9dc2 1842 kernel optional linux-base_4.7.dsc
 a4e3a749c9b46e2ed54aed10d763ba0d 33700 kernel optional linux-base_4.7.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmHJr/xfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EP8cP/R6u3KmSanuEJoE5Od7J4Kq//EtVmsjo
P+TR3zxSIXWow2tL/hyv8vyaD+LhhFM/mB9e4hNwr2lQK8vGjqgdFH/Vt6kEMXAJ
t42DL0ohSSGTQjTAbXyVFJ3AiX2UqTwqFIBDtjqZFhJfKqKfIFfFUj8atB+dHixf
IBKkU7VJHnEhs5xQBcm9aYOk/tQjUtgnNQOBQknhCJdrhMouOJW4Id7ldv7/PZb4

Bug#995542: marked as done (Updating the lua-dbi Uploaders list)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 12:19:42 +
with message-id 
and subject line Bug#995542: fixed in lua-dbi 0.7.2-3
has caused the Debian Bug report #995542,
regarding Updating the lua-dbi Uploaders list
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.)


-- 
995542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-dbi
Version: 0.7.2-2
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Enrico Tassi  has retired, so can't work on
the lua-dbi package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lua-dbi
Source-Version: 0.7.2-3
Done: Victor Seva 

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

Debian distribution maintenance software
pp.
Victor Seva  (supplier of updated lua-dbi 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: Mon, 27 Dec 2021 12:48:58 +0100
Source: lua-dbi
Architecture: source
Version: 0.7.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Lua Team 
Changed-By: Victor Seva 
Closes: 995542
Changes:
 lua-dbi (0.7.2-3) unstable; urgency=medium
 .
   * Lua team as maintainer, me as uploader (Closes: #995542)
   * watch to version 4
   * add Lua5.4 support
Checksums-Sha1:
 a8943dd5b0847dab1b6b184dffd55b6efb528748 2091 lua-dbi_0.7.2-3.dsc
 c10dce0ad254449fce94630e84c59d5cc9c51d33 4236 lua-dbi_0.7.2-3.debian.tar.xz
 63a4257eeff2742e795821d758da5b3862cc875b 11029 lua-dbi_0.7.2-3_amd64.buildinfo
Checksums-Sha256:
 dd8e27d46540db5a652a537ac944ca07117a232ba9d6f99054654bbaa289f1ef 2091 
lua-dbi_0.7.2-3.dsc
 7a6178edd61726a44e225c566532afb604e72e588d788a9cbdb1e45e442f25cc 4236 
lua-dbi_0.7.2-3.debian.tar.xz
 227cb80622a708aa61003414c0deba2ef6c96d039f26007ba6d7c316566fbe65 11029 
lua-dbi_0.7.2-3_amd64.buildinfo
Files:
 dd9da0d77230d9af4904e07987676dda 2091 interpreters optional lua-dbi_0.7.2-3.dsc
 104817a93384b5c92e3c2136870888d1 4236 interpreters optional 
lua-dbi_0.7.2-3.debian.tar.xz
 749551d6b501cc776802b6c49a09439e 11029 interpreters optional 
lua-dbi_0.7.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEE3S3PbKiJPTunbGuNsViYiXJxmOAFAmHJqTgRHHZzZXZhQGRl
Ymlhbi5vcmcACgkQsViYiXJxmOCmnAgAkYF0vn8+sRCM7nDMqsVp538q0qRx1MzJ
WRS3XgPY4U9KR2dbMYEbzTQOVxZbQWsfvnrcTTvPU2aIcs9gcMmrfbBlu08FJ1VD
+DC5fLAUxQFRbTVRTeRDIxO76ugYPjH7IFkRm53Mw4dPPWA+lsTCFrM6Z7/csh5/
S/IXD8gY3rNsOLzWGSvtIvVZi4AUe9SbWr8QEd3hKCs/0DUK6xSzDWFHz91nVKfy
K/6M2cbKqBcKx5gIzYYMUnjNW8l2xb1D8/7nOk3OlnjBTkAlPecNfTd6Kyn9qr1j
aje/rDcK0Udr9UIVunE7Uf6dODzxBnSMgZ2bo5uCvIfcgtDwoEeUuQ==
=zLVP
-END PGP SIGNATURE End Message ---


Bug#984275: marked as done (openmw: ftbfs with GCC-11)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 12:19:50 +
with message-id 
and subject line Bug#984275: fixed in openmw 0.47.0-1
has caused the Debian Bug report #984275,
regarding openmw: ftbfs with GCC-11
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.)


-- 
984275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openmw
Version: 0.46.0-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

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

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. 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://people.debian.org/~doko/logs/20210228/filtered/gcc11/openmw_0.46.0-3_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
   33 | #define dbl_max std::numeric_limits::max()
  | ^~
/<>/components/sceneutil/mwshadowtechnique.cpp:2837:78: note: in 
expansion of macro ‘dbl_max’
 2837 | min_x_ratio = convexHull.valid() ? 
convexHull.minRatio(virtual_eye,0) : -dbl_max;
  | 
 ^~~
/<>/components/sceneutil/mwshadowtechnique.cpp:33:22: error: 
‘numeric_limits’ is not a member of ‘std’
   33 | #define dbl_max std::numeric_limits::max()
  |  ^~
/<>/components/sceneutil/mwshadowtechnique.cpp:2838:77: note: in 
expansion of macro ‘dbl_max’
 2838 | max_x_ratio = convexHull.valid() ? 
convexHull.maxRatio(virtual_eye,0) : dbl_max;
  | 
^~~
/<>/components/sceneutil/mwshadowtechnique.cpp:33:37: error: 
expected primary-expression before ‘double’
   33 | #define dbl_max std::numeric_limits::max()
  | ^~
/<>/components/sceneutil/mwshadowtechnique.cpp:2838:77: note: in 
expansion of macro ‘dbl_max’
 2838 | max_x_ratio = convexHull.valid() ? 
convexHull.maxRatio(virtual_eye,0) : dbl_max;
  | 
^~~
/<>/components/sceneutil/mwshadowtechnique.cpp:33:22: error: 
‘numeric_limits’ is not a member of ‘std’
   33 | #define dbl_max std::numeric_limits::max()
  |  ^~
/<>/components/sceneutil/mwshadowtechnique.cpp:2882:28: note: in 
expansion of macro ‘dbl_max’
 2882 | if (min_z_ratio == dbl_max || rli.min_z_ratio > min_z_ratio)
  |^~~
/<>/components/sceneutil/mwshadowtechnique.cpp:33:37: error: 
expected primary-expression before ‘double’
   33 | #define dbl_max std::numeric_limits::max()
  | ^~
/<>/components/sceneutil/mwshadowtechnique.cpp:2882:28: note: in 
expansion of macro ‘dbl_max’
 2882 | if (min_z_ratio == dbl_max || rli.min_z_ratio > min_z_ratio)
  |^~~
/<>/components/sceneutil/mwshadowtechnique.cpp:33:37: error: 
expected ‘)’ before ‘double’
   33 | #define dbl_max std::numeric_limits::max()
  | ^~
/<>/components/sceneutil/mwshadowtechnique.cpp:2882:28: note: in 
expansion of macro ‘dbl_max’
 2882 | if (min_z_ratio == dbl_max || rli.min_z_ratio > min_z_ratio)
  |^~~

Bug#1001621: marked as done (RFS: openmw/0.47.0-1 -- Open-world RPG game engine)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 13:07:11 +0100
with message-id 
and subject line Re: RFS: OpenMW
has caused the Debian Bug report #1001621,
regarding RFS: openmw/0.47.0-1 -- Open-world RPG game engine
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.)


-- 
1001621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Hello Debian,

I've prepared the OpenMW 0.47.0 package for validation and upload. It is
lintian clean and tested with pbuilder. Further information about this
package can be accessed from the URL :
https://salsa.debian.org/games-team/openmw

Caveat: it requires librecast-dev which is still awaiting approval for
upload by FTP-Master:
https://ftp-master.debian.org/new.html

it's been put into use here.
https://launchpad.net/~openmw/+archive/ubuntu/openmw/+packages

Cheers,
Bret Curtis
--- End Message ---
--- Begin Message ---

Hi Bret,

The debian/copyright file is not maintained properly. I fixed obvious mistakes and included the 
changed info from the new version diff. But I guess there are more things to do.


Please scan the source more thoroughly for copyright/license info on the next 
upload.

Thanks,
Bastian--- End Message ---


Bug#995552: marked as done (Updating the lua-yaml Uploaders list)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 12:03:49 +
with message-id 
and subject line Bug#995552: fixed in lua-yaml 6.2.7-2
has caused the Debian Bug report #995552,
regarding Updating the lua-yaml Uploaders list
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.)


-- 
995552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-yaml
Version: 6.2.7-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Enrico Tassi  has retired, so can't work on
the lua-yaml package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lua-yaml
Source-Version: 6.2.7-2
Done: Victor Seva 

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

Debian distribution maintenance software
pp.
Victor Seva  (supplier of updated lua-yaml 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: Mon, 27 Dec 2021 12:33:10 +0100
Source: lua-yaml
Architecture: source
Version: 6.2.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Lua Team 
Changed-By: Victor Seva 
Closes: 995552
Changes:
 lua-yaml (6.2.7-2) unstable; urgency=medium
 .
   * Lua team as maintainer, me as uploader (Closes: #995552)
   * add Lua5.4 support
   * debhelper 13
Checksums-Sha1:
 c4b4fd0b1576f31c4ff84f21c219320ed52a3c44 1667 lua-yaml_6.2.7-2.dsc
 43231138a1288116e63830b5c73d16385d0b53b7 3452 lua-yaml_6.2.7-2.debian.tar.xz
 0c6d243654aecc6a7205b3145f68ba980c6e825a 6730 lua-yaml_6.2.7-2_amd64.buildinfo
Checksums-Sha256:
 ac20855812af58e483a6bf917876bbdef510fb3793308877159eee33d78d12fa 1667 
lua-yaml_6.2.7-2.dsc
 57322a329b0e5c766a5628918ff9c10c0a53f947c5d07b5ca4ed841f9247e5cd 3452 
lua-yaml_6.2.7-2.debian.tar.xz
 bb395c0dff4f86eaa6ea579144c1c780e63ce955e5407fa17bba60dcd70d3f36 6730 
lua-yaml_6.2.7-2_amd64.buildinfo
Files:
 40c5b4ade99ac66c5494242b7e4efd65 1667 interpreters optional 
lua-yaml_6.2.7-2.dsc
 fd829c3bfc7e0b86d49a41cf83732378 3452 interpreters optional 
lua-yaml_6.2.7-2.debian.tar.xz
 77b1eedeb9029413acf1328c781caeac 6730 interpreters optional 
lua-yaml_6.2.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEE3S3PbKiJPTunbGuNsViYiXJxmOAFAmHJpXMRHHZzZXZhQGRl
Ymlhbi5vcmcACgkQsViYiXJxmOBsFgf/V28xXiayqyek81GgRucqv/+tM1O2oiBm
ezyvUewY9PlFhN/pDYQvc0Gi9QDx3/xpeyHX53tqSdzNO1WvAk96IiawBtyDzeyD
NjilpSX0mUqhLde/nL2QC2blTIWdnjmvmpfljc45Ew6ve6ksfcvbiy3bTn+GtEtR
5rcQSMxjS6HoWHvQ9ycx3588L44puTbOg52uDrIpi36Rc24bWnIlrkznuwD7kd/C
/uKwtFr4I5KZoPiYSQ9CS9U5QZFOxZs1dSQktHblHqeFAAjDRlkrnMjB8BwazBfj
LcRKBGicCvN6SuPArBATDy1sN/DHuTOBbivWPnqCBa7XfkicdS3fyA==
=mTd6
-END PGP SIGNATURE End Message ---


Bug#995539: marked as done (Updating the lua-event Uploaders list)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 12:03:43 +
with message-id 
and subject line Bug#995539: fixed in lua-event 0.4.6-2
has caused the Debian Bug report #995539,
regarding Updating the lua-event Uploaders list
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.)


-- 
995539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-event
Version: 0.4.6-1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Enrico Tassi  has retired, so can't work on
the lua-event package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lua-event
Source-Version: 0.4.6-2
Done: Victor Seva 

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

Debian distribution maintenance software
pp.
Victor Seva  (supplier of updated lua-event 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: Mon, 20 Dec 2021 13:06:29 +0100
Source: lua-event
Architecture: source
Version: 0.4.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Lua Team 
Changed-By: Victor Seva 
Closes: 995539
Changes:
 lua-event (0.4.6-2) unstable; urgency=medium
 .
   * Lua team as maintainer, me as uploader (Closes: #995539)
   * add Lua5.4 support
Checksums-Sha1:
 c81756f528bd997eefa59c217a6ee32b40f38704 1689 lua-event_0.4.6-2.dsc
 52e4076ff9635ad7757a2d812bbbaeabe53789b0 3180 lua-event_0.4.6-2.debian.tar.xz
 fdb5ee2e678cdf2aff87de2a7c11016635879cb5 6909 lua-event_0.4.6-2_amd64.buildinfo
Checksums-Sha256:
 726d7da3f48f37c7f998dbb5b26ee85c753dbb0fa8d8ffaf13ca52a55d414786 1689 
lua-event_0.4.6-2.dsc
 e45c7c3cf3b5bd4c9f7827c7ceae2645763367b6dc93103a7323703686aa0e42 3180 
lua-event_0.4.6-2.debian.tar.xz
 5bdd799566a450eee5ba20ec8e5723b30cb9a18459b68a006bab9144c4115210 6909 
lua-event_0.4.6-2_amd64.buildinfo
Files:
 55b9844c7e3228e7aa6fa24443cb863b 1689 interpreters optional 
lua-event_0.4.6-2.dsc
 8c940adb04ff26a863186fde8dfa478b 3180 interpreters optional 
lua-event_0.4.6-2.debian.tar.xz
 0b150bd58062fe27e32242b651e00d02 6909 interpreters optional 
lua-event_0.4.6-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEE3S3PbKiJPTunbGuNsViYiXJxmOAFAmHJpdARHHZzZXZhQGRl
Ymlhbi5vcmcACgkQsViYiXJxmODQYggAvvGTZyl4AIwwiowUeEwySJ9thr7h/dMD
HZuKUzoO0yglDJ/MreDJ3k5bz0BHwqvhYuj5aaiA39BOPB/BA3aINnhoHOZS026x
MAojpwoJuXrT2CCa5ZTKdRlHAkMG9Gp2dwxulL+NgkGq7rdWY1nbKh4uFpxmZ2Kb
w1o7HH1h9nfKTW4AeiqRyNmpCs8ptTV+kGy3XlvA0h7osrAjpKvrn2YQl3g7jEjR
GXVJ8gbwG3ZDdoG/bcPWLxLJLsilXP+lkiDxZajoKwpvpRsdQD8z+0/2WCXWFv/v
NZ0msO5BUPkPP8ZePTr8BilRcRcDwdk2HQfacwPyMXIC1BWntY1Frw==
=y4Gr
-END PGP SIGNATURE End Message ---


Bug#998826: marked as done (ceph-mgr-modules-core,ceph-mgr: both ship /usr/share/ceph/mgr/*)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 11:48:37 +
with message-id 
and subject line Bug#998826: fixed in ceph 16.2.6+ds-9
has caused the Debian Bug report #998826,
regarding ceph-mgr-modules-core,ceph-mgr: both ship /usr/share/ceph/mgr/*
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.)


-- 
998826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ceph-mgr-modules-core,ceph-mgr
Version: 16.2.6+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package ceph-mgr.
  Preparing to unpack .../111-ceph-mgr_16.2.6+ds-2_amd64.deb ...
  Unpacking ceph-mgr (16.2.6+ds-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-3hMgRk/111-ceph-mgr_16.2.6+ds-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/ceph/mgr/balancer/__init__.py', which is 
also in package ceph-mgr-modules-core 16.2.6+ds-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-3hMgRk/111-ceph-mgr_16.2.6+ds-2_amd64.deb

These files are shipped by both packages:

usr/share/ceph/mgr/balancer/__init__.py
usr/share/ceph/mgr/balancer/module.py
usr/share/ceph/mgr/crash/__init__.py
usr/share/ceph/mgr/crash/module.py
usr/share/ceph/mgr/devicehealth/__init__.py
usr/share/ceph/mgr/devicehealth/module.py
usr/share/ceph/mgr/influx/__init__.py
usr/share/ceph/mgr/influx/module.py
usr/share/ceph/mgr/insights/__init__.py
usr/share/ceph/mgr/insights/health.py
usr/share/ceph/mgr/insights/module.py
usr/share/ceph/mgr/iostat/__init__.py
usr/share/ceph/mgr/iostat/module.py
usr/share/ceph/mgr/localpool/__init__.py
usr/share/ceph/mgr/localpool/module.py
usr/share/ceph/mgr/orchestrator/README.md
usr/share/ceph/mgr/orchestrator/__init__.py
usr/share/ceph/mgr/orchestrator/_interface.py
usr/share/ceph/mgr/orchestrator/module.py
usr/share/ceph/mgr/pg_autoscaler/__init__.py
usr/share/ceph/mgr/pg_autoscaler/module.py
usr/share/ceph/mgr/progress/__init__.py
usr/share/ceph/mgr/progress/module.py
usr/share/ceph/mgr/progress/test_progress.py
usr/share/ceph/mgr/prometheus/__init__.py
usr/share/ceph/mgr/prometheus/module.py
usr/share/ceph/mgr/rbd_support/__init__.py
usr/share/ceph/mgr/rbd_support/common.py
usr/share/ceph/mgr/rbd_support/mirror_snapshot_schedule.py
usr/share/ceph/mgr/rbd_support/module.py
usr/share/ceph/mgr/rbd_support/perf.py
usr/share/ceph/mgr/rbd_support/schedule.py
usr/share/ceph/mgr/rbd_support/task.py
usr/share/ceph/mgr/rbd_support/trash_purge_schedule.py
usr/share/ceph/mgr/restful/__init__.py
usr/share/ceph/mgr/restful/api/__init__.py
usr/share/ceph/mgr/restful/api/config.py
usr/share/ceph/mgr/restful/api/crush.py
usr/share/ceph/mgr/restful/api/doc.py
usr/share/ceph/mgr/restful/api/mon.py
usr/share/ceph/mgr/restful/api/osd.py
usr/share/ceph/mgr/restful/api/perf.py
usr/share/ceph/mgr/restful/api/pool.py
usr/share/ceph/mgr/restful/api/request.py
usr/share/ceph/mgr/restful/api/server.py
usr/share/ceph/mgr/restful/common.py
usr/share/ceph/mgr/restful/context.py
usr/share/ceph/mgr/restful/decorators.py
usr/share/ceph/mgr/restful/hooks.py
usr/share/ceph/mgr/restful/module.py
usr/share/ceph/mgr/selftest/__init__.py
usr/share/ceph/mgr/selftest/module.py
usr/share/ceph/mgr/status/__init__.py
usr/share/ceph/mgr/status/module.py
usr/share/ceph/mgr/telegraf/__init__.py
usr/share/ceph/mgr/telegraf/basesocket.py
usr/share/ceph/mgr/telegraf/module.py
usr/share/ceph/mgr/telegraf/protocol.py
usr/share/ceph/mgr/telegraf/utils.py
usr/share/ceph/mgr/telemetry/__init__.py
usr/share/ceph/mgr/telemetry/module.py
usr/share/ceph/mgr/test_orchestrator/README.md
usr/share/ceph/mgr/test_orchestrator/__init__.py
usr/share/ceph/mgr/test_orchestrator/dummy_data.json
usr/share/ceph/mgr/test_orchestrator/module.py
usr/share/ceph/mgr/volumes/__init__.py
usr/share/ceph/mgr/volumes/fs/__init__.py
usr/share/ceph/mgr/volumes/fs/async_cloner.py
usr/share/ceph/mgr/volumes/fs/async_job.py
usr/share/ceph/mgr/volumes/fs/exception.py
usr/share/ceph/mgr/volumes/fs/fs_util.py
usr/share/ceph/mgr/volumes/fs/operations/__init__.py
usr/share/ceph/mgr/volumes/fs/operations/access.py
usr/share/ceph/mgr/volumes/fs/operations/clone_index.py
usr/share/ceph/mgr/volumes/fs/operations/group.py
usr/share/ceph/mgr/volumes/fs/operations/index.py
usr/share/ceph/mgr/volumes/fs/operations/lock.py

Bug#1002573: marked as done (general: fstrim, 2 errors)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 12:46:40 +0100 (CET)
with message-id 
and subject line Re: Bug#1002573: (no subject)
has caused the Debian Bug report #1002573,
regarding general: fstrim, 2 errors
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.)


-- 
1002573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: grave
Justification: renders package unusable

1st error:
fstrim --verbose --all
reports nothing

2nd error:
fstrim --verbose /
gives a wrong error message

For both cases, see attachment 1.png, system l5

This happens on Debian 11.2 Bullseye on an Intel hardware

The root file system is a RAID1 software array, but on a second Intel
hardware with only one SSD, same Debian version, the behavior of fstrim
is the same

On a Raspberry Pi with Debian 10 Buster, everything works fine (see
attachment 2.png, system b4)

Notice on both screenshots: the fstrim versions are the same
--- End Message ---
--- Begin Message ---

On Mon, 27 Dec 2021, detlev schmidtke wrote:


No, I am out of here

If the bug is not reproducible for you by now, it is not worth
to persue it

You might want to close this issue


We are not a shop that is providing services to you. If the ticket needs 
to be closed then please *do the work* (done herewith).

*t--- End Message ---


Bug#997536: marked as done (rally-openstack: FTBFS: tests failed directory)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 11:04:18 +
with message-id 
and subject line Bug#997536: fixed in rally-openstack 2.2.0-1
has caused the Debian Bug report #997536,
regarding rally-openstack: FTBFS: tests failed directory
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.)


-- 
997536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rally-openstack
Version: 2.0.0-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):
> === short test summary info 
> 
> FAILED 
> tests/unit/task/contexts/network/test_allow_ssh.py::AllowSSHContextTestCase::test__prepare_open_secgroup_rules
> FAILED 
> tests/unit/task/contexts/vm/test_custom_image.py::BaseCustomImageContextVMTestCase::test_create_one_image
> === 2 failed, 2226 passed in 37.72s 
> 
> make[1]: *** [debian/rules:25: override_dh_auto_install] Error 1


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/rally-openstack_2.0.0-2_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: rally-openstack
Source-Version: 2.2.0-1
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
rally-openstack, 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.
Thomas Goirand  (supplier of updated rally-openstack 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, 03 Nov 2021 10:52:16 +0100
Source: rally-openstack
Architecture: source
Version: 2.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 997536
Changes:
 rally-openstack (2.2.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Removed python3-ceilometerclient from (build-)depends.
   * Test with installed package.
   * Use -W ignore::pytest.PytestCollectionWarning when running tests
 (Closes: #997536).
   * Add remove-gnocchiclient-constraint.patch.
Checksums-Sha1:
 7eed5074e3e9863f4079885ddca90db4febbfea4 2939 rally-openstack_2.2.0-1.dsc
 e600ddb34b1250b28cffd5e0d6ab758ee213c439 455072 
rally-openstack_2.2.0.orig.tar.xz
 ae829e6da65e7d1467743f5dcf7dbe202c0b0061 3992 
rally-openstack_2.2.0-1.debian.tar.xz
 edfb48b481734b8a8cbc5a2fb07c1c27117e7f56 13841 
rally-openstack_2.2.0-1_amd64.buildinfo
Checksums-Sha256:
 6cc2f75a1278af5e2b0cc12b5ae89330e1ce1bd6893bd23a77142e1c97628b82 2939 
rally-openstack_2.2.0-1.dsc
 66ac5dc63988eea1b0a2e06243a333d7d54655ec4b10f0ba9faedb948731 455072 
rally-openstack_2.2.0.orig.tar.xz
 65f66146444784ffa403459a49a44d480a290648c368fd6954f0a5095e54054f 3992 
rally-openstack_2.2.0-1.debian.tar.xz
 9b0fe877d1f73ab28d7f85faee3a1d16441b8827e70dc0a6bb1871b187bb1125 13841 
rally-openstack_2.2.0-1_amd64.buildinfo
Files:
 003eec1f5c6b9816c2438f78b81f8191 2939 net optional rally-openstack_2.2.0-1.dsc
 c136c91227a43cbf46d8d0a7050e4367 455072 net optional 
rally-openstack_2.2.0.orig.tar.xz
 69fff702202200b4155c399250bb4ee1 3992 net optional 
rally-openstack_2.2.0-1.debian.tar.xz
 7003871c961da2651d0707e12ad7e442 13841 net optional 
rally-openstack_2.2.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmHJmYIACgkQ1BatFaxr
Q/4grg//aJLS0ICy9KaKKTBnYSPRAzIpSy8zBX63WtQL/A/BkY22OiJoz/BwlDKZ
p0ry26hTZGn64ZV3JlGR/PATCrSffIHLSDBETjVcTZIS/VboMjOd83E4Sj/Fv/Kx

Bug#892244: marked as done (debian-www: doc-debian package page contains invalid URL)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 11:53:31 +0100
with message-id <20211227105331.gt13...@beskar.mdcc.cx>
and subject line Re: Bug #892244: debian-www: doc-debian package page contains 
invalid URL
has caused the Debian Bug report #892244,
regarding debian-www: doc-debian package page contains invalid URL
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.)


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

Dear Maintainer,

On https://packages.debian.org/sid/doc-debian the "All of these files are 
available at fttp://ftp.debian.org/debian/doc/" text is an invalid url. This is 
solved by chanting it to http://ftp.debian.org/debian/doc/

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

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi,

annadane: thanks for reporing this issue!
Paul Wise: thanks for properly assigning this bug.

The problem has been fixed in doc-debian (6.5) (jan 2021) or earlier:
Currently, https://packages.debian.org/sid/doc-debian no longer mentions
ftp://ftp.debian.org but correctly states "All of these files are available
at http://ftp.debian.org/debian/doc/ and mirrors thereof."

( It's _also_ fixed in debian-faq,
https://packages.debian.org/sid/debian-faq is now correct too. )

Thanks, Bye,

Joost--- End Message ---


Bug#985864: marked as done (trove-common: fails to install: install: cannot stat '/usr/share/trove-common/trove-guestagent.conf': No such file or directory)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 11:49:04 +0100
with message-id <56aa1561-4e09-6868-b384-a9fe81b01...@debian.org>
and subject line Fixed
has caused the Debian Bug report #985864,
regarding trove-common: fails to install: install: cannot stat 
'/usr/share/trove-common/trove-guestagent.conf': No such file or directory
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.)


-- 
985864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trove-common
Version: 1:15.0.0~rc1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up trove-common (1:15.0.0~rc1-1) ...
  install: cannot stat '/usr/share/trove-common/trove-guestagent.conf': No such 
file or directory
  dpkg: error processing package trove-common (--configure):
   installed trove-common package post-installation script subprocess returned 
error exit status 1
  Processing triggers for ca-certificates (20210119) ...
  Updating certificates in /etc/ssl/certs...
  0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d...
  done.
  Errors were encountered while processing:
   trove-common


cheers,

Andreas


trove-common_1:15.0.0~rc1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
This was fixed in debian/15.0.0-2
Closing this bug.

Cheers,

Thomas Goirand (zigo)--- End Message ---


Bug#999488: marked as done (plocate: updatedb: cannot prune whitespace-containing directories / paths)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 10:33:50 +
with message-id 
and subject line Bug#999488: fixed in plocate 1.1.14-1
has caused the Debian Bug report #999488,
regarding plocate: updatedb: cannot prune whitespace-containing directories / 
paths
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.)


-- 
999488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plocate
X-Debbugs-Cc: d...@gnui.org
Version: 1.1.13-1
Severity: normal

Dear developer,

as you find it okay to break backward-compatibility with mlocate 
, let me suggest you a thing, that is 
definitely worth being broken:

a *very* unorthodox handling¹ of arguments to -n / --add-prunenames and -e / 
--add-prunepaths by updatedb(8), that prevents users from specifying 
whitespace-containing filenames here.

Instead, it seems to be reasonable to stick by the simplest approach possible, 
where a switch accepts a single argument, and to specify multiple values, one 
have to repeat it:

$ updatedb -l no -o "$HOME/.cache/plocate.db" -U "$HOME" -e 
"$HOME/.local/share/Trash" -e "$HOME/various useless stuff"

Support for repeated switches is already here, so all what is to be done is to 
stop splitting their arguments.

-- 
¹ For anyone unaware: they accept a single argument, which is expected to be a 
whitespace-separated list of filenames.  Can anybody suggest any other util, 
that has the same inteface?

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: plocate
Source-Version: 1.1.14-1
Done: Steinar H. Gunderson 

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

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

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

Debian distribution maintenance software
pp.
Steinar H. Gunderson  (supplier of updated plocate package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 27 Dec 2021 11:13:31 +0100
Source: plocate
Architecture: source
Version: 1.1.14-1
Distribution: unstable
Urgency: medium
Maintainer: Steinar H. Gunderson 
Changed-By: Steinar H. Gunderson 
Closes: 999488
Changes:
 plocate (1.1.14-1) unstable; urgency=medium
 .
   * New upstream release.
 * Adds option --add-single-prunepath. (Closes: #999488)
Checksums-Sha1:
 e8cea319a732687babe0c32f5eb87520cce42005 1872 plocate_1.1.14-1.dsc
 b9127dd84e3fec7ef6403717742c9c2722d5880b 73037 plocate_1.1.14.orig.tar.gz
 805c80c202d99a4c7da175f2c25aa548f6e42a5f 6340 plocate_1.1.14-1.debian.tar.xz
 68877e16801e4830bc689f5e8b4f059cf5850e2c 7504 plocate_1.1.14-1_amd64.buildinfo
Checksums-Sha256:
 03a7652fd807ceea86f9798cbf10443ff33b0ae1605208894537c2da715238bf 1872 
plocate_1.1.14-1.dsc
 5560e527aa55cbe2de4de3783953bc64e26e338f797f58b7be99da0318f4dc18 73037 
plocate_1.1.14.orig.tar.gz
 2bd6b59cf8c27ce7197fa635b8e7ef0051326eec19e0535d7fe0b78663664494 6340 
plocate_1.1.14-1.debian.tar.xz
 aa770db561981744eccbc5b265f4fe1cd9eea35854f1c5c8d72e6ea52e20c2a6 7504 
plocate_1.1.14-1_amd64.buildinfo
Files:
 c035fbca28957498e3dffbeb092e6439 1872 utils optional plocate_1.1.14-1.dsc
 aa748642d348deb1d2b197eaccea98fe 73037 utils optional 
plocate_1.1.14.orig.tar.gz
 2c317a699b6cde634482add3a6969ead 6340 utils optional 
plocate_1.1.14-1.debian.tar.xz
 168feaae831941413160d8fe284f5dab 7504 utils optional 
plocate_1.1.14-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwukAT/AowY5OrduDf2F1YXeXj3YFAmHJkmcACgkQf2F1YXeX
j3ZnDRAAwc8majjmZbczwjRl972tPt3P2sbYHjeHh43wkT5EqTtaUVVv6UItZ6VP
LkCBghKXfEpXvzX3Z7Epc1quHky/0DsF2ywoVm5m2Y5ljYGL8UUZ+Jpi4bEMkk/K
b7nvGA/53yLr5ghTiZDl8lOYDSKStLaF6jg5ToKVAfElsNBSGdGZC9YcPzfvfwU7
dgugmIY/NoCm8we8vR1LEQS/n9BcHCMpXSxqmy/vaLw6jVlZomIY0yGKLwD95o8/
XYs2h4i52U+886e7kccZKZtRs+M7tGzzGuNO7/P+X+d7Mz5KZ/Y2CJBd+0a0qZzN
a64wZ8N2Px2l7uKHDjXAlG+sRLA7fAtinM7LjTz6nj+6LRHFdKKLTPfWPLJDpYlb
bM4x0UZuh/eaagMdFAdScIn2cnY7CRAYrOZs7IOxuscye3KryJNuLjn6PcSCPiWN

Bug#1002425: marked as done (python-autobahn: FTBFS: FAILED autobahn/wamp/test/test_serializer.py::TestSerializer::test_crosstrip)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 11:10:26 +0100
with message-id 
and subject line Closing
has caused the Debian Bug report #1002425,
regarding python-autobahn: FTBFS: FAILED 
autobahn/wamp/test/test_serializer.py::TestSerializer::test_crosstrip
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.)


-- 
1002425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-autobahn
Version: 17.10.1+dfsg1-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -e ; set -x ; for i in 3.10 3.9 ; do \
>   rm -rf build ; \
>   PYTHONPATH=. python$i -m pytest autobahn ; \
> done
> + rm -rf build
> + PYTHONPATH=. python3.10 -m pytest autobahn
> = test session starts 
> ==
> platform linux -- Python 3.10.1, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
> rootdir: /<>, configfile: setup.cfg
> collected 169 items
> 
> autobahn/asyncio/test/test_asyncio_rawsocket.py  [  
> 4%]
> autobahn/rawsocket/test/test_rawsocket_url.py .  [ 
> 14%]
> autobahn/test/test_util.py ..[ 
> 15%]
> autobahn/wamp/test/test_auth.py .[ 
> 21%]
> autobahn/wamp/test/test_cryptosign.py ...[ 
> 23%]
> autobahn/wamp/test/test_exception.py ..  [ 
> 24%]
> autobahn/wamp/test/test_message.py . [ 
> 46%]
> ..   [ 
> 61%]
> autobahn/wamp/test/test_protocol_peer.py ..  [ 
> 62%]
> autobahn/wamp/test/test_runner.py .  [ 
> 65%]
> autobahn/wamp/test/test_serializer.py .F.F   [ 
> 68%]
> autobahn/wamp/test/test_uri_pattern.py   [ 
> 77%]
> autobahn/websocket/test/test_protocol.py .   [ 
> 82%]
> autobahn/websocket/test/test_websocket_url.py .. [ 
> 98%]
> ...  
> [100%]
> 
> === FAILURES 
> ===
>  TestSerializer.test_crosstrip 
> _
> 
> self = 
> payload = b'\x93\x01\xa6realm1\x81\xa5roles\x81\xaasubscriber\x80'
> isBinary = True
> 
> def unserialize(self, payload, isBinary=None):
> """
> Implements :func:`autobahn.wamp.interfaces.ISerializer.unserialize`
> """
> if isBinary is not None:
> if isBinary != self._serializer.BINARY:
> raise ProtocolError("invalid serialization of WAMP message 
> (binary {0}, but expected {1})".format(isBinary, self._serializer.BINARY))
> 
> try:
> >   raw_msgs = self._serializer.unserialize(payload)
> 
> autobahn/wamp/serializer.py:104: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self =  0x7f05673a7160>
> payload = b'\x93\x01\xa6realm1\x81\xa5roles\x81\xaasubscriber\x80'
> 
> def unserialize(self, payload):
> """
> Implements 
> :func:`autobahn.wamp.interfaces.IObjectSerializer.unserialize`
> """
> 
> if self._batched:
> msgs = []
> N = len(payload)
> i = 0
> while i < N:
> # read message length prefix
> if i + 4 > N:
> raise Exception("batch format error [1]")
> l = struct.unpack("!L", payload[i:i + 4])[0]
> 
> # read message data
> if i + 4 + l > N:
> raise Exception("batch format error [2]")
> data = payload[i + 4:i + 4 + l]
> 
> # append parsed raw message
> msgs.append(umsgpack.unpackb(data))
> 
> # advance until everything consumed
> i = i + 4 + l
> 
> if i != N:
> raise Exception("batch format error [3]")
> return msgs
> 
>

Bug#981623: marked as done (r-cran-glmmtmb: needs a rebuild when r-cran-tmb is updated)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 10:03:33 +
with message-id 
and subject line Bug#981623: fixed in r-cran-glmmtmb 1.1.2.3-2
has caused the Debian Bug report #981623,
regarding r-cran-glmmtmb: needs a rebuild when r-cran-tmb is updated
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.)


-- 
981623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-glmmtmb
Version: 1.0.2.1-1
Forwarded: https://github.com/glmmTMB/glmmTMB/issues/615

Hi Maintainer

Since the upload of r-cran-tmb 1.7.18-1, r-cran-glmmtmb's autopkgtests
show hundreds of similar errors [1]:

Error in .Call("FreeADFunObject", ptr, PACKAGE = DLL) :
  "FreeADFunObject" not available for .Call() for package "glmmTMB"
Calls: 

Yet the auopkgtests still pass.  I found this issue is known upstream,
and I have scheduled a binNMU (1.0.2.1-1+b1) for r-cran-glmmtmb, which
seems to have fixed it [2].

It would be nice if we had some automated way of detecting when
r-cran-glmmtmb needs a rebuild.

Regards
Graham


[1] 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-glmmtmb/10184561/log.gz
[2] 
https://ci.debian.net/data/autopkgtest/testing/armhf/r/r-cran-glmmtmb/10185795/log.gz
--- End Message ---
--- Begin Message ---
Source: r-cran-glmmtmb
Source-Version: 1.1.2.3-2
Done: Graham Inggs 

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated r-cran-glmmtmb 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: Mon, 27 Dec 2021 09:18:07 +
Source: r-cran-glmmtmb
Built-For-Profiles: noudeb
Architecture: source
Version: 1.1.2.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Graham Inggs 
Closes: 981623
Changes:
 r-cran-glmmtmb (1.1.2.3-2) unstable; urgency=medium
 .
   * Team upload
   * Add autopkgtest that fails when r-cran-tmb is upgraded and
 r-cran-glmmtmb needs a rebuild (Closes: #981623)
Checksums-Sha1:
 fdbebf557a23c9f52db38311430512087941019d 2198 r-cran-glmmtmb_1.1.2.3-2.dsc
 aec6ac0293cebd49b0c192efe4b385674edda6c0 13656 
r-cran-glmmtmb_1.1.2.3-2.debian.tar.xz
Checksums-Sha256:
 cc59b4365ab1e3c86ecbe3debceec5ac22feab5456eb8298f896c246fb396e4f 2198 
r-cran-glmmtmb_1.1.2.3-2.dsc
 a39a934884204f27dc48dd1c719f9e9807f967d10210c8bf552374659dd177c5 13656 
r-cran-glmmtmb_1.1.2.3-2.debian.tar.xz
Files:
 f02eb9eaf7a79107d1d4202cb7623d3e 2198 gnu-r optional 
r-cran-glmmtmb_1.1.2.3-2.dsc
 2f8efff3d5c0ec532ca65a2f8010638c 13656 gnu-r optional 
r-cran-glmmtmb_1.1.2.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmHJiCoACgkQr8/sjmac
4cKLlw/9HGTnlSz3Kx0VGHjHACD/dE3iaCdlWnwNt10Sk2Orlojp5hx+OZ170u8t
qrfobK0kwb6jIfiR+gSmsIS/Mt9x/4z22QZKZhnyDQ0ILDJ9367shKpYgs10dhPk
+xfJUcK6pNQPnsaEQFRPoEUujgqf+g5Qr6reXonJsI9m6NXK4XHEAESBg6M9rbST
O/yzUjUQ4hoc87eiYZHvkI/R7MZtDL8U3Ql185Z5ayIGfV0L18LROf56lqX/7QXs
nCe+QGDUQRXOneAQ1HzlOe6wbowviKM0itXn5JtXb9+6Srm0Fpqvxkifvf6u/vIo
WSkU4JdTvTxkUgj8uZFErF6yYG9E2G0yg0csHmHAOVdmn1tc3OiZJhY1LuLelQzt
UsKd3M82cVmO820zRk+Gd3W5Jv2miM+DzxMld8KSh27ao/ouDHH1Gb4b8oVkAfKn
cBBlpoXkLeh2FWx/6yMbOkc8ozMSzta2/qfO6t76xaB6CND4+Qjd9iv4TzZvRMyN
10WyMcYJ3ADT6bXiZbBKpdNuEmuQZlbbNIu6IrpIVgwDiWXoPmZoIaVZtrBio9b/
wm5tHCGUkWgrQRIN+l7phObrZzvNC+aAloWlRvqFHjqNixKvza/FAR5Ez2gq8TCK
E2iCBig2UaEm23g/vUV171vOwshIXUANOJk6+UeJ5F8oy8s62p8=
=6pqU
-END PGP SIGNATURE End Message ---


Bug#956860: marked as done (ceph 14.x packages lost init script)

2021-12-27 Thread Debian Bug Tracking System
Your message dated Mon, 27 Dec 2021 10:19:35 +0100
with message-id 
and subject line Closing this bug
has caused the Debian Bug report #956860,
regarding ceph 14.x packages lost init script
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.)


-- 
956860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ceph-base
Version: 14.2.7-1~bpo10+1

First of all thanks for the high activity in packaging recent versions of ceph, 
lately!

ceph-base (or ceph) binary packages were supplying /etc/init.d/ceph, but 
beginning with 14.x versions neither of ceph binary packages seems to provide 
/etc/init.d/ceph any longer.

Could you please consider to keep packaging a working init script file?
--- End Message ---
--- Begin Message ---
Hi,

Since nobody is contributing anything regarding this bug, I see no
reason to keep it open. To anyone annoyed by this: we don't mind adding
sysv-rc support, but we just have no time to add it. Just contribute it
and we will add it to the package.

Cheers,

Thomas Goirand (zigo)--- End Message ---