Bug#1003644: src:frr: fails to migrate to testing for too long: FTBFS on mips64el & non-migrating new dependency

[Paul Gevers]

Source: frr
Version: 7.5.1-1.1
Severity: serious
Control: close -1 8.1-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:frr has been trying to migrate for 61 days 
[2]. Hence, I am filing this bug. Your package fails to build from 
source on mips64el. Your package also grew a (build) dependency that's 
new, but that's not migrating [3].


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


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


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


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


Paul

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


OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:frr: fails to migrate to testing for too long: FTBFS on mips64el & non-migrating new dependency

[Debian Bug Tracking System]

Processing control commands:

> close -1 8.1-1
Bug #1003644 [src:frr] src:frr: fails to migrate to testing for too long: FTBFS 
on mips64el & non-migrating new dependency
Marked as fixed in versions frr/8.1-1.
Bug #1003644 [src:frr] src:frr: fails to migrate to testing for too long: FTBFS 
on mips64el & non-migrating new dependency
Marked Bug as done

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

Bug#1003643: src:lintian: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: lintian
Version: 2.111.0
Severity: serious
Control: close -1 2.114.0
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 999768

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:lintian has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. You have an unresolved RC bug 
that applies to the unstable package but not to the testing package, 
hence blocking migration.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:lintian: fails to migrate to testing for too long: unresolved RC bug

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.114.0
Bug #1003643 [src:lintian] src:lintian: fails to migrate to testing for too 
long: unresolved RC bug
Marked as fixed in versions lintian/2.114.0.
Bug #1003643 [src:lintian] src:lintian: fails to migrate to testing for too 
long: unresolved RC bug
Marked Bug as done
> block -1 by 999768
Bug #1003643 {Done: Paul Gevers } [src:lintian] src:lintian: 
fails to migrate to testing for too long: unresolved RC bug
1003643 was not blocked by any bugs.
1003643 was not blocking any bugs.
Added blocking bug(s) of 1003643: 999768

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

Bug#1000717: supysonic: FTBFS on Python 3.10

[Louis-Philippe Véronneau]

forwarded 1000717 https://github.com/spl0k/supysonic/issues/229
thanks

Pony has been updated to a version that supports python3.10, but using
it, I get this testsuite error, so I can't build:

==
FAIL: test_add_nowait_stop (tests.base.test_watcher.AudioWatcherTestCase)
--
Traceback (most recent call last):
  File
"/<>/.pybuild/cpython3_3.9/build/tests/base/test_watcher.py",
line 117, in test_add_nowait_stop
self.assertTrackCountEqual(1)
  File "", line 2, in assertTrackCountEqual
  File "/usr/lib/python3/dist-packages/pony/orm/core.py", line 531, in
new_func
result = func(*args, **kwargs)
  File
"/<>/.pybuild/cpython3_3.9/build/tests/base/test_watcher.py",
line 106, in assertTrackCountEqual
self.assertEqual(Track.select().count(), expected)
AssertionError: 0 != 1


-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: supysonic: FTBFS on Python 3.10

[Debian Bug Tracking System]

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

> forwarded 1000717 https://github.com/spl0k/supysonic/issues/229
Bug #1000717 [src:supysonic] supysonic: FTBFS on Python 3.10
Set Bug forwarded-to-address to 'https://github.com/spl0k/supysonic/issues/229'.
> thanks
Stopping processing here.

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

Bug#1003540: marked as done (gsl-doc: please update to 2.7.1)

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 02:49:13 +
with message-id 
and subject line Bug#1003540: fixed in gsl-doc 2.7.1-1
has caused the Debian Bug report #1003540,
regarding gsl-doc: please update to 2.7.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.)


-- 
1003540: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsl-doc
Version: 2.6-2
Severity: serious

Hi,

please update gsl-doc to 2.7.1 to match the gsl version in the archive:

gsl| 2.7.1+dfsg-3  | unstable | source
gsl-doc| 2.6-2 | unstable/non-free| source

Andreas
--- End Message ---
--- Begin Message ---
Source: gsl-doc
Source-Version: 2.7.1-1
Done: Dirk Eddelbuettel 

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated gsl-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: SHA256

Format: 1.8
Date: Wed, 12 Jan 2022 20:00:40 -0600
Source: gsl-doc
Binary: gsl-doc-info gsl-doc-pdf
Architecture: source all
Version: 2.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Description:
 gsl-doc-info - GNU Scientific Library (GSL) Reference Manual in info
 gsl-doc-pdf - GNU Scientific Library (GSL) Reference Manual in pdf
Closes: 1003540
Changes:
 gsl-doc (2.7.1-1) unstable; urgency=medium
 .
   * New upstream release   (Closes: #1003540)
Checksums-Sha1:
 7785920aa634b03dedadb6a8ccde3b9ab0530b45 2025 gsl-doc_2.7.1-1.dsc
 549e1105cd1198537be9707257161531e109bd94 7509209 gsl-doc_2.7.1.orig.tar.gz
 b52528a939faca9863d40c36274b3d8dd25eb4ab 12428 gsl-doc_2.7.1-1.debian.tar.xz
 b6f15a17af7c805ff2b78351328c4411133ad121 493940 gsl-doc-info_2.7.1-1_all.deb
 d3055d125165583f63eccee72b952f7c5f8ea159 4987500 gsl-doc-pdf_2.7.1-1_all.deb
 414b27e12f56a7f7dc2d39d79d3043579b660373 10418 gsl-doc_2.7.1-1_amd64.buildinfo
Checksums-Sha256:
 42ef043634dcbfbf363d79829d55239055926bdf2f95128db20b814ab0b04c4e 2025 
gsl-doc_2.7.1-1.dsc
 dcb0fbd43048832b757ff9942691a8dd70026d5da0ff85601e52687f6deeb34b 7509209 
gsl-doc_2.7.1.orig.tar.gz
 3715950aa87082c14ec63e91e4e3a2d19ce60749e0b55bf0da95c0afbcfb5a4e 12428 
gsl-doc_2.7.1-1.debian.tar.xz
 1bece4a841bdde5719096261f35ff1c96f1292b06f34606f43ae819031e382ed 493940 
gsl-doc-info_2.7.1-1_all.deb
 bf17e87fc5c689966e65c9e8e314ee41fa0601fba51c5bc937aac5a6c818db78 4987500 
gsl-doc-pdf_2.7.1-1_all.deb
 43ba178a04e4e1ff84503b07c4b3a712679f5ee51497123674b2ed0841ea9bba 10418 
gsl-doc_2.7.1-1_amd64.buildinfo
Files:
 2a57df3182094a8311927822c7b3db7f 2025 non-free/math optional 
gsl-doc_2.7.1-1.dsc
 36aee97e67f64dbdab7afae197e3483b 7509209 non-free/math optional 
gsl-doc_2.7.1.orig.tar.gz
 4cb25f0f898fd72edd360bb4c0b3b265 12428 non-free/math optional 
gsl-doc_2.7.1-1.debian.tar.xz
 7c54f5f8402689d5ee6e27054301b197 493940 non-free/doc optional 
gsl-doc-info_2.7.1-1_all.deb
 7c56fc5f69c2b8e158fdea60eb740fb4 4987500 non-free/doc optional 
gsl-doc-pdf_2.7.1-1_all.deb
 eb6d9f4247bc3029ba82cbf098479499 10418 non-free/math optional 
gsl-doc_2.7.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIVAwUBYd+NbKFIn+KrmaIaAQidbA//btiEq0IZWJNrzUuQnBE1O6k0x6mSDasc
lX86ztq+/x9Vu6/tTs5Xvw1EG/YDpbGnpvJ4F66l4DYsznCDlI1wjoKtR1sPOtGL
QR/JiAFaBPvTfWmUKw1LEdVHUnJxCy3U9FjhxTfZQwWss7fGxduowgkLWkR+e1Jn
JayE75M/xVLSalUt+Yx7lN2IDQyuJkMZ6VH7AzDh/aBBDKEibRknAlRTlvo+jp85
agZdrlEUHzTNmKSdHCaZWzlzOXe3RgOYbvUqMlJPJgf4+OfTeDxW1mZtXaGXTqTG
OMbok7HQhHPT/phU5ZmFogQ9Yr5vViUi0Qi7FDBUxTWnXaoEkRinUiqZiY2mQbDK
lKBsmGCTkVDs9XrQgyTU2zdREfrL5iH5koleyS18g1AZYBFbqVLGPlU04UI3yuHs
LNh2QZ9PU9VQN1XZf2FCYoT8heVhdrQTM3jGtNN+7rx8FmOv29IeqnT1AJpfxvVJ
KkrcQxbarOomrtX3XrDGxFXIdoA0wPyN5Z3VpXLpwrYusJ2E/7vCjNrm0FiEGsdS
rRpFYUgfIsG5t4w1FarUsa1dZzfsU3S4KBjNtWf47xWVuEm0H1kvDS9l2Qa2um3y
Zpohcrn1XxHluy4qrImhpWh5LnQGP2Eg1iIQlty+xvXAaovcz3rY6ntD7I8l+l4/
RGpM3wqydI0=
=9iTt
-END PGP SIGNATURE End Message ---

Bug#1003540: gsl-doc: please update to 2.7.1

[Dirk Eddelbuettel]

On 13 January 2022 at 02:29, Andreas Beckmann wrote:
| On 11/01/2022 17.54, Dirk Eddelbuettel wrote:
| > On 11 January 2022 at 17:31, Andreas Beckmann wrote:
| > | Package: gsl-doc
| > | Version: 2.6-2
| > | Severity: serious
| > 
| > Why would that be a serious bug rather normal or even minor?
| 
| Feel free to downgrade, but try to have the versions in sync for the 
| bookworm release.

I have a moment now so I'll probably just do it.

| > It's a bit of a manual process becuase of the dfsg dance and manual ops.  
And
| > there generally is not that much that changes between versions -- GSL is
| > fairly mature and stable at this point.
| 
| because of such manual processes the separate src:*-doc sometimes look 
| like bitrot (e.g. scalapack 2.1 vs scalapack-doc 1.5) ...

Yes. And I starting to think that it may almost be better to withdraw the
-doc package then.  When we started to package (esp html-based) documentation
back in the day (say 20 years ago) connectivity was way worse.  Today most
people reach for the browser first. I would suspect popcon number support this.

Anyway, thanks for the nag :)

Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1003540: gsl-doc: please update to 2.7.1

[Andreas Beckmann]

On 11/01/2022 17.54, Dirk Eddelbuettel wrote:

On 11 January 2022 at 17:31, Andreas Beckmann wrote:
| Package: gsl-doc
| Version: 2.6-2
| Severity: serious

Why would that be a serious bug rather normal or even minor?


Feel free to downgrade, but try to have the versions in sync for the 
bookworm release.



It's a bit of a manual process becuase of the dfsg dance and manual ops.  And
there generally is not that much that changes between versions -- GSL is
fairly mature and stable at this point.


because of such manual processes the separate src:*-doc sometimes look 
like bitrot (e.g. scalapack 2.1 vs scalapack-doc 1.5) ...



Andreas

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

[Debian Bug Tracking System]

Your message dated Thu, 13 Jan 2022 00:33:28 +
with message-id 
and subject line Bug#965703: fixed in liece 2.0+0.20030527cvs-13
has caused the Debian Bug report #965703,
regarding liece: 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.)


-- 
965703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liece
Version: 2.0+0.20030527cvs-12
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package liece 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: liece
Source-Version: 2.0+0.20030527cvs-13
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
liece, 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.
Andreas Beckmann  (supplier of updated liece 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, 13 Jan 2022 01:15:09 +0100
Source: liece
Architecture: source
Version: 2.0+0.20030527cvs-13
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 965703
Changes:
 liece (2.0+0.20030527cvs-13) unstable; urgency=medium
 .
   * QA upload.
   * Switch to debhelper-compat (= 13).  (Closes: #965703)
   * Switch from cdbs to dh.
   * Switch to a machine readable copyright file.
   * Bump Standards-Version to 4.6.0.
Checksums-Sha1:
 0679921960516a63f9e60703979951a7b5698863 1828 liece_2.0+0.20030527cvs-13.dsc
 93fa8d0a81da4906739a7785f1c4d3f592bf3849 13440 
liece_2.0+0.20030527cvs-13.debian.tar.xz
 45ce693cc6fe4c8793d0e449da0186a78b3e78b5 9024 
liece_2.0+0.20030527cvs-13_source.buildinfo
Checksums-Sha256:
 929371fc829653aef73bbc4ce89f928677244e4877c7facf451900aa5b381aae 1828 
liece_2.0+0.20030527cvs-13.dsc
 41098f30fa0b0980eea00ab1b27b9db964eb60ec72b1b90807e2b68571766a96 13440 
liece_2.0+0.20030527cvs-13.debian.tar.xz
 e272060c215746256dd8074b204ca91239daf1b5a8273006ee5c8226cc99d97f 9024 
liece_2.0+0.20030527cvs-13_source.buildinfo
Files:
 c532cca6f17937f57d563e3cc4c9d323 1828 net optional 
liece_2.0+0.20030527cvs-13.dsc
 f930cf3e42db5a9fa314bc9a10b93cef 13440 net optional 
liece_2.0+0.20030527cvs-13.debian.tar.xz
 d392dcb3414fba0b761d59706c6a72f9 9024 net optional 
liece_2.0+0.20030527cvs-13_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmHfcQ4QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCGj2D/9O/Tp7XfxX1fBa67veYEbg08fmGVNx/BNX
k4md/dDgAHbU0Jvd3WyDEUdfY+apLH8KDFxEDDLZbYNU7jbrxHHWruPIFWANx2Ub
Wmm4vXKg5pnnaoVR+ERMzdJ7fRmxvexWYV78U8/93+SBhcsAGo4pTkodbWvOyaJj
rCsSiNxWphKD2QiBRTEo9TaZ8WVYuHJbVS1uBEnTYlAHtZhJJfgc+Doha3dhCNy0
jnB7w7tUnOeFbR3nXLbrZ2U3loH/xQA4kXhiMOh0JU1owTJDSugi6XdGOxf4+wiq
7yycjGu0Zr8jsnvkZQI0Ta6RqEUA6E+/Z5ntJr+igqhylnOmQMQ7bu13/wamK7+l
yXB9dOBNPOrekM9Pb/gEfMgqiPIUtQaNG6Atu+G25Qx1euJGTgC3nlWK3ZKXQyA9
geBNM0IeR5Fl8sCn2HK4CTE7D+ivbK8x3HkzirP8RB7VnVsKfD3NZUIso8jdwPqU
2TunQ9YkEcV+jbm2TO5YsUyAeQtd9PF+6REmceryFIXodpSxSthnhED3RxtZCxsZ

Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Steve Langasek]

Control: tags -1 moreinfo unreproducible

On Wed, Jan 12, 2022 at 06:28:45PM +0100, Vincent-Xavier JUMEL wrote:
> Package: libpam-runtime
> Version: 1.4.0-11
> Severity: critical
> Justification: breaks the whole system

> Dear Maintainer,
> 
>* Upgrade to the unstable version of libpam-runtime_1.14.0_11_all
>with 
>```
>auth[success=0 default=ignore]  pam_ssh.so use_first_pass
>```
>* Login then failed
>* I've modified "success=0" -> "success=1" to get back the login.

So where does this 'success=0' come from?  It doesn't come from
/usr/share/pam-configs/ssh.  Installing libpam-ssh in unstable does not
result in a config containing this line.  I'm not sure 'success=0' is valid,
and if it is, it means 'on success, process the next module' so your bug
report, by slicing your config file to only show the single pam_ssh line,
does not show what happens afterward that actually fails the stack.

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


signature.asc
Description: PGP signature

Processed: Re: Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo unreproducible
Bug #1003617 [libpam-runtime] libpam-runtime: When upgrading to 
libpam-runtime_1.4.0-11 pam_ssh is broken
Added tag(s) moreinfo and unreproducible.

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

Bug#997599: marked as done (python-libusb1: FTBFS: error in libusb1 setup command: use_2to3 is invalid.)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 23:18:31 +
with message-id 
and subject line Bug#997599: fixed in python-libusb1 1.10.1-0.1
has caused the Debian Bug report #997599,
regarding python-libusb1: FTBFS: error in libusb1 setup command: use_2to3 is 
invalid.
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.)


-- 
997599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-libusb1
Version: 1.9.1-1
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):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> error in libusb1 setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:7: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-libusb1_1.9.1-1_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-libusb1
Source-Version: 1.10.1-0.1
Done: Adrian Bunk 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 06 Jan 2022 14:54:48 +0200
Source: python-libusb1
Architecture: source
Version: 1.10.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Arnaud Fontaine 
Changed-By: Adrian Bunk 
Closes: 997599
Changes:
 python-libusb1 (1.10.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream release.
 - Compatible with new setuptools. (Closes: #997599)
Checksums-Sha1:
 c47bcf9350e9372800a4f4063d0a2e20d5241932 2211 python-libusb1_1.10.1-0.1.dsc
 aabe339255977e816196098629fccb24fc651e39 82398 
python-libusb1_1.10.1.orig.tar.gz
 eb7e930b25e3d0e46901d5b2abe548b3aac8f202 2788 
python-libusb1_1.10.1-0.1.debian.tar.xz
Checksums-Sha256:
 131d8780a7c047d8775b4c0b2ff9a585ce35fa198544f5f85d3e12cc98f08190 2211 
python-libusb1_1.10.1-0.1.dsc
 8d70e5ef11a9facf304e696cc1d571c526bd9e02a8710a045b3b2567db7a54e0 82398 
python-libusb1_1.10.1.orig.tar.gz
 9edd9fdbba3bd8eb4d6e2d43a024cd52322f0d62f7caa291db672ffdc259293d 2788 
python-libusb1_1.10.1-0.1.debian.tar.xz
Files:
 8d7ca3f3bbb0fa5642387684ad3fa082 2211 python optional 
python-libusb1_1.10.1-0.1.dsc
 378b8220d99ffd3d360a4c0f5e48783a 82398 python optional 
python-libusb1_1.10.1.orig.tar.gz
 6de2ee0401cbeb8e5d624a99a38a8abd 2788 python optional 
python-libusb1_1.10.1-0.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHW7ZQACgkQiNJCh6LY
mLFkSQ/+MiyOtlv1STgXknEbtScWzJtGuFqz8xcNPYsX3/tP9p+wwikXjiC2dOoE
4okLreTEH1KDcdMG3vOhIfXu1G8t3tADGg9BnG3udv4oiuhxLi1bKtKD9OwEXN2U
usYSioCagC0mjoDwWo4MQG48hEgkK/pLZJfo/GMxixaAHw08t+rBiLsvo4CKXflB
BLJ/G+ZuCPIQ/oRIFkZgMuinqreNwz7wlSow1sLmyTie1YaBxQOzpLsRJ1NN2Z1u
7CIPw4v5+CdCeMLw4xt/xPjh+yRw1GYdq6+WRs18LmgoCxVYOPgegCg7lQ0ZtSGj
zvKw8wP8CKpEaB3TroewIKXPyHTTlRhi2Oa36wfTbeb6PnqVeJ6k5QMGpjqaH4a9
XboxfMdd7AhVBMiZ9d6fdRYBmzUarG7fs1Zdps2pofolTy9hDrvpzgojHK+LMzqy
vOW9XmBtpGSQMV6CusQCGxSFLflpE30aI4yAdYpUjPbHZTcB6vOCCXcLqESbmlOl

Bug#1003150: marked as done (python3-wheel: Missing depends on python3-distutils)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 23:00:10 +
with message-id 
and subject line Bug#1003150: fixed in wheel 0.37.1-1
has caused the Debian Bug report #1003150,
regarding python3-wheel: Missing depends on python3-distutils
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.)


-- 
1003150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-wheel
Version: 0.34.2-1
Severity: serious
Justification: Policy 4.5

Attempted to unpack a wheel in a pretty minimal sid chroot and got this
error:

$ python3 -m wheel unpack setuptools-44.1.1-py2.py3-none-any.whl 
Traceback (most recent call last):
  File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
  File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3/dist-packages/wheel/__main__.py", line 19, in 
sys.exit(main())
  File "/usr/lib/python3/dist-packages/wheel/__main__.py", line 15, in main
sys.exit(wheel.cli.main())
  File "/usr/lib/python3/dist-packages/wheel/cli/__init__.py", line 83, in main
args.func(args)
  File "/usr/lib/python3/dist-packages/wheel/cli/__init__.py", line 24, in 
unpack_f
from .unpack import unpack
  File "/usr/lib/python3/dist-packages/wheel/cli/unpack.py", line 6, in 
from ..wheelfile import WheelFile
  File "/usr/lib/python3/dist-packages/wheel/wheelfile.py", line 10, in 
from distutils import log as logger
ImportError: cannot import name 'log' from 'distutils' 
(/usr/lib/python3.9/distutils/__init__.py)

Now that distutils is split out, wheel will need to explicitly depend on
it.

Scott K
--- End Message ---
--- Begin Message ---
Source: wheel
Source-Version: 0.37.1-1
Done: Stefano Rivera 

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

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

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated wheel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jan 2022 13:29:30 -0400
Binary: python3-wheel python3-wheel-whl python-wheel-common
Source: wheel
Architecture: all source
Version: 0.37.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 970183 1002533 1003150 1003573
Description: 
 python3-wheel - built-package format for Python
 python3-wheel-whl - built-package format for Python (wheel wheel)
 python-wheel-common - built-package format for Python (command-line scripts)
Changes:
 wheel (0.37.1-1) unstable; urgency=medium
 .
   [ Stefano Rivera ]
   * New upstream release.
   * Add myself as an uploader.
   * Update copyright.
   * Bump Standards-Version to 4.6.0, no changes needed.
   * Bump watch format to 4.
   * Build upstream's RST manpage with Sphinx (requiring a patch).
   * Run tests at build time with tox.
 - Patch: Skip MacOS tests.
   * Run test suite as an autopkgtest.
   * Mark existing autopkgtests as allow-stderr, due to deprecation warning
 emitted by newer setuptools. (Closes: #1002533)
   * Explicitly depend on python3-distutils (Closes: #1003150)
   * Extend upstream metadata.
   * Build a python3-wheel-whl package. (Closes: #1003573)
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * Remove MIA uploader Barry Warsaw . Closes: #970183
Checksums-Sha1: 
 624f88ad69d8dbcc9f66f632ca3ba0bf749f340d 1708 wheel_0.37.1-1.dsc
 62f852caca877bf8ca4e651e6103c15fa8420221 55972 wheel_0.37.1.orig.tar.xz
 a5e1593555bae87f412477880c06cfe06c535699 6768 wheel_0.37.1-1.debian.tar.xz
 da6a74ecb3e765e6784cd5e3f5e39c32a344d777 7639 wheel_0.37.1-1_source.buildinfo
 dc08e96dda78feac2b5c9f1d9e74a02c00222d48 6108 
python-wheel-common_0.37.1-1_all.deb
 4cc7006e1f7709c9d75a881c5200c4234b6c2a11 38728 
python3-wheel-whl_0.37.1-1_all.deb
 2d173ddac8658ee0569563e421c35c37f9619d5f 

Bug#1002533: marked as done (wheel: autopkgtest needs update for new version of setuptools: deprecation warning on stderr)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 23:00:10 +
with message-id 
and subject line Bug#1002533: fixed in wheel 0.37.1-1
has caused the Debian Bug report #1002533,
regarding wheel: autopkgtest needs update for new version of setuptools: 
deprecation warning on stderr
to be marked as done.

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

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


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

Source: wheel
Version: 0.34.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, setupto...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:setuptools

Dear maintainer(s),

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


   passfail
setuptools from testing59.6.0-1
wheel  from testing0.34.2-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test 
passes, but a deprecation warning is printed on stderr and autopkgtest 
fails by default on that unless the allow-stderr restriction is used.


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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/w/wheel/17811345/log.gz

running bdist_wheel
running build
running build_py
creating build
creating build/lib
creating build/lib/dummy
copying dummy/yes.py -> build/lib/dummy
copying dummy/no.py -> build/lib/dummy
copying dummy/__init__.py -> build/lib/dummy
/usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build 
and pip and other standards-based tools.

  warnings.warn(
installing to /tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/build
running install
running install_lib
creating /tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/build
creating /tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/build/dummy
copying build/lib/dummy/yes.py -> 
/tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/build/dummy
copying build/lib/dummy/no.py -> 
/tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/build/dummy
copying build/lib/dummy/__init__.py -> 
/tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/build/dummy

running install_egg_info
running egg_info
creating dummy.egg-info
writing dummy.egg-info/PKG-INFO
writing dependency_links to dummy.egg-info/dependency_links.txt
writing top-level names to dummy.egg-info/top_level.txt
writing manifest file 'dummy.egg-info/SOURCES.txt'
reading manifest file 'dummy.egg-info/SOURCES.txt'
writing manifest file 'dummy.egg-info/SOURCES.txt'
Copying dummy.egg-info to 
/tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/build/dummy-0.0.egg-info

running install_scripts
creating 
/tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/build/dummy-0.0.dist-info/WHEEL
creating 
'/tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/wheels/dummy-0.0-py3-none-any.whl' 
and adding '/tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/build' 
to it

adding 'dummy/__init__.py'
adding 'dummy/no.py'
adding 'dummy/yes.py'
adding 'dummy-0.0.dist-info/METADATA'
adding 'dummy-0.0.dist-info/WHEEL'
adding 'dummy-0.0.dist-info/top_level.txt'
adding 'dummy-0.0.dist-info/RECORD'
removing /tmp/autopkgtest-lxc.x6s6pv29/downtmp/autopkgtest_tmp/build
yes = yes
no = no
autopkgtest [14:16:50]: test smoketest-3



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: wheel
Source-Version: 0.37.1-1
Done: 

Bug#1002523: marked as done (setuptools-scm: autopkgtest needs update for new version of setuptools: deprecation warning is treated as error)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 22:49:13 +
with message-id 
and subject line Bug#1002523: fixed in setuptools-scm 6.3.2-2
has caused the Debian Bug report #1002523,
regarding setuptools-scm: autopkgtest needs update for new version of 
setuptools: deprecation warning is treated as error
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.)


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

Source: setuptools-scm
Version: 6.3.2-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, setupto...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:setuptools

Dear maintainer(s),

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


   passfail
setuptools from testing59.6.0-1
setuptools-scm from testing6.3.2-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. It seems the 
test fails on a deprecation warning.


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


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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/s/setuptools-scm/17807988/log.gz

= test session starts 
==

platform linux -- Python 3.9.9, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
setuptools version 59.6.0 from 
'/usr/lib/python3/dist-packages/setuptools/__init__.py'
setuptools_scm version 6.3.2 from 
'/usr/lib/python3/dist-packages/setuptools_scm/__init__.py'
rootdir: /tmp/autopkgtest-lxc.99ltvr94/downtmp/build.4q7/src, 
configfile: tox.ini, testpaths: testing

collected 201 items / 1 error / 3 deselected / 197 selected

 ERRORS 

_ ERROR collecting testing/test_setuptools_support.py 
__

testing/test_setuptools_support.py:10: in 
from virtualenv.run import cli_run
/usr/lib/python3/dist-packages/virtualenv/__init__.py:3: in 
from .run import cli_run, session_via_cli
/usr/lib/python3/dist-packages/virtualenv/run/__init__.py:14: in 
from .plugin.creators import CreatorSelector
/usr/lib/python3/dist-packages/virtualenv/run/plugin/creators.py:6: in 

from virtualenv.create.via_global_ref.builtin.builtin_way import 
VirtualenvBuiltin
/usr/lib/python3/dist-packages/virtualenv/create/via_global_ref/builtin/builtin_way.py:7: 
in 

from virtualenv.create.creator import Creator
/usr/lib/python3/dist-packages/virtualenv/create/creator.py:15: in 
from virtualenv.discovery.cached_py_info import LogCmd
/usr/lib/python3/dist-packages/virtualenv/discovery/cached_py_info.py:23: in 


_CACHE[Path(sys.executable)] = PythonInfo()
/usr/lib/python3/dist-packages/virtualenv/discovery/py_info.py:86: in 
__init__
self.distutils_install = {u(k): u(v) for k, v in 
self._distutils_install().items()}
/usr/lib/python3/dist-packages/virtualenv/discovery/py_info.py:155: in 
_distutils_install

i = d.get_command_obj("install", create=True)
/usr/lib/python3.9/distutils/dist.py:858: in get_command_obj
cmd_obj = self.command_obj[command] = klass(self)
/usr/lib/python3/dist-packages/setuptools/__init__.py:172: in __init__
_Command.__init__(self, dist)
/usr/lib/python3.9/distutils/cmd.py:62: in __init__
self.initialize_options()
/usr/lib/python3/dist-packages/setuptools/command/install.py:34: in 
initialize_options

warnings.warn(
E   setuptools._deprecation_warning.SetuptoolsDeprecationWarning: 

Bug#1002523: marked as pending in setuptools-scm

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/setuptools-scm/-/commit/25c5340a975e92afe189f5cf62b82b830df30986


Mark autopkgtest as allow-stderr, setuptools now prints a deprecation warning 
when setup.py is invoked directly. (Closes: #1002523)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1002523

Processed: Bug#1002523 marked as pending in setuptools-scm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1002523 [src:setuptools-scm] setuptools-scm: autopkgtest needs update for 
new version of setuptools: deprecation warning is treated as error
Added tag(s) pending.

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

Bug#1000650: marked as done (phploc: Failing testsuite with PHP 8.1)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 22:19:19 +
with message-id 
and subject line Bug#1000650: fixed in phploc 7.0.2-2
has caused the Debian Bug report #1000650,
regarding phploc: Failing testsuite with PHP 8.1
to be marked as done.

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

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


-- 
1000650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: phploc
Version: 7.0.2-1
Severity: important
Tags: upstream
Control: block 976811 by -1

The testsuite is currently failing with PHP 8.1, I didn’t notice any
upstream activity about it yet.

autopkgtest [02:32:56]: test command1: phpunit --bootstrap 
/usr/share/php/SebastianBergmann/PHPLOC/autoload.php
autopkgtest [02:32:56]: test command1: [---
PHPUnit 9.5.10 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.0RC5
Configuration: /tmp/autopkgtest-lxc.dgngl6tq/downtmp/build.Jf8/src/phpunit.xml

FF.   31 / 31 (100%)

Time: 00:00.013, Memory: 6.00 MB

There were 2 failures:

1) SebastianBergmann\PHPLOC\AnalyserTest::testWithoutTests
Failed asserting that two arrays are equal.
--- Expected
+++ Actual
@@ @@
 'nonFinalClasses' => 1
 'finalClasses' => 0
 'functions' => 2
-'namedFunctions' => 1
-'anonymousFunctions' => 1
+'namedFunctions' => 0
+'anonymousFunctions' => 2
 'methods' => 4
 'publicMethods' => 2
 'nonPublicMethods' => 2
@@ @@
 'globalConstants' => 1
 'testClasses' => 0
 'testMethods' => 0
-'ccnByLloc' => 0.08
+'ccnByLloc' => 0.08333
 'llocByNof' => 0.5
 'methodCalls' => 6
 'staticMethodCalls' => 4
@@ @@
 'namespaces' => 1
 'ncloc' => 68
 'classCcnMin' => 1
-'classCcnAvg' => 1.65
+'classCcnAvg' => 1.6667
 'classCcnMax' => 3
 'methodCcnMin' => 1
-'methodCcnAvg' => 1.65
+'methodCcnAvg' => 1.6667
 'methodCcnMax' => 2
 'classLlocMin' => 0
-'classLlocAvg' => 7.3
+'classLlocAvg' => 7.333
 'classLlocMax' => 22
 'methodLlocMin' => 4
-'methodLlocAvg' => 5.6
+'methodLlocAvg' => 5.667
 'methodLlocMax' => 7
-'averageMethodsPerClass' => 1.33
+'averageMethodsPerClass' => 1.
 'minimumMethodsPerClass' => 0
 'maximumMethodsPerClass' => 4
 )

/tmp/autopkgtest-lxc.dgngl6tq/downtmp/build.Jf8/src/tests/unit/AnalyserTest.php:104

2) SebastianBergmann\PHPLOC\AnalyserTest::testWithTests
Failed asserting that two arrays are equal.
--- Expected
+++ Actual
@@ @@
 'nonFinalClasses' => 1
 'finalClasses' => 0
 'functions' => 2
-'namedFunctions' => 1
-'anonymousFunctions' => 1
+'namedFunctions' => 0
+'anonymousFunctions' => 2
 'methods' => 4
 'publicMethods' => 2
 'nonPublicMethods' => 2
@@ @@
 'globalConstants' => 1
 'testClasses' => 1
 'testMethods' => 2
-'ccnByLloc' => 0.08
+'ccnByLloc' => 0.08333
 'llocByNof' => 0.5
 'methodCalls' => 6
 'staticMethodCalls' => 4
@@ @@
 'classCcnAvg' => 1.5
 'classCcnMax' => 3
 'methodCcnMin' => 1
-'methodCcnAvg' => 1.66
+'methodCcnAvg' => 1.6667
 'methodCcnMax' => 2
 'classLlocMin' => 0
 'classLlocAvg' => 5.5
 'classLlocMax' => 22
 'methodLlocMin' => 4
-'methodLlocAvg' => 5.6
+'methodLlocAvg' => 5.667
 'methodLlocMax' => 7
 'averageMethodsPerClass' => 1
 'minimumMethodsPerClass' => 0
 'maximumMethodsPerClass' => 4
 )

/tmp/autopkgtest-lxc.dgngl6tq/downtmp/build.Jf8/src/tests/unit/AnalyserTest.php:183

FAILURES!
Tests: 31, Assertions: 43, Failures: 2.
autopkgtest [02:32:57]: test command1: ---]
autopkgtest [02:32:57]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL non-zero exit status 1


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: phploc
Source-Version: 7.0.2-2
Done: David Prévot 

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

(This 

Processed: severity of 1003578 is serious

[Debian Bug Tracking System]

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

> severity 1003578 serious
Bug #1003578 [hash-slinger] hash-slinger: Unnecessary dependency on 
python3-ipaddr
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: limit source to phploc, tagging 1000650

[Debian Bug Tracking System]

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

> limit source phploc
Limiting to bugs with field 'source' containing at least one of 'phploc'
Limit currently set to 'source':'phploc'

> tags 1000650 + pending
Bug #1000650 [phploc] phploc: Failing testsuite with PHP 8.1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1003606: marked as done (python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4))

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 21:07:31 +
with message-id 
and subject line Bug#1003606: fixed in python-flask-httpauth 4.5.0-2
has caused the Debian Bug report #1003606,
regarding python3-flask-httpauth: missing Breaks+Replaces: 
python-flask-httpauth-doc (<< 4)
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.)


-- 
1003606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-flask-httpauth
Version: 4.5.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../python3-flask-httpauth_4.5.0-1_all.deb ...
  Unpacking python3-flask-httpauth (4.5.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/flask-httpauth.1.gz', which is also 
in package python-flask-httpauth-doc 3.2.4-3.1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb

Obviously the manpage was moved between the packages.


cheers,

Andreas


python-flask-httpauth-doc=3.2.4-3.1_python3-flask-httpauth=4.5.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-flask-httpauth
Source-Version: 4.5.0-2
Done: Martina Ferrari 

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

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

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

Debian distribution maintenance software
pp.
Martina Ferrari  (supplier of updated python-flask-httpauth 
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, 12 Jan 2022 20:27:40 +
Source: python-flask-httpauth
Architecture: source
Version: 4.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Martina Ferrari 
Changed-By: Martina Ferrari 
Closes: 1003606
Changes:
 python-flask-httpauth (4.5.0-2) unstable; urgency=medium
 .
   * Add .mailmap file.
   * d/control: Revert cme's incorrect "fix". Closes: #1003606
Checksums-Sha1:
 7c8e6bdbdbc92972a24485b135cde7bee27ccf94 2220 python-flask-httpauth_4.5.0-2.dsc
 4ec43ecb527c702e75273d1277da39b01b52ec7c 5176 
python-flask-httpauth_4.5.0-2.debian.tar.xz
 f76e720b65c88a14dcbcd5fb040619c2a3358ece 8440 
python-flask-httpauth_4.5.0-2_amd64.buildinfo
Checksums-Sha256:
 4df188c3de6d0a78175cad55a6cda4df86546e2662fa45e31bd88b983e5a149b 2220 
python-flask-httpauth_4.5.0-2.dsc
 d3083489e578c407b232e8611a6936d08821e6780c0c5fb8f58a3f229829ca76 5176 
python-flask-httpauth_4.5.0-2.debian.tar.xz
 7ab2b33dc45d32af55cae1e1b6b26ca9f6d5a3c66e0d4f201a0e8f1121fb823e 8440 
python-flask-httpauth_4.5.0-2_amd64.buildinfo
Files:
 34cd43a944dc76e2c7cb482e1ebf9870 2220 python optional 
python-flask-httpauth_4.5.0-2.dsc
 369b4d4e0fb5eb7c723e099ecb135669 5176 python optional 
python-flask-httpauth_4.5.0-2.debian.tar.xz
 743090ff5083ba6f911965be8551fbea 8440 python optional 
python-flask-httpauth_4.5.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE2qbv8cYn6hwmsaaSqiMPxF+MJ7EFAmHfOlsACgkQqiMPxF+M
J7F+KBAArPwMVwra2GD4ZR8cVKh/HBwr3i7g+3sLXdcPzSxoO/cM0BZFO5x6n8o9
QM3m0vF41tu/0AxxoOKBcE/XPwsx/rj0dtBPxEAQkfcMGwyB2dxtR7Edjiz+n5xO
sGzRUIeben9C+HeIkQpEajDJKWfQparX0Qq4Lo+a3yxioVQAosL0OAuiGZmbsTjb
ABC60qDKGPnjNC2VGEBTeS4kzNJhjw8GzYNmVJsiMeSHcQSIUqHT8TpSUPiwQJpA
Zdpp9c3MFUmLAi3aihSPq23dntHFur6u/NoJpw9lzXg2f8rZkUXE6g96zfM8X1w4
0RlrdiryTFgFyL7Pwzoc+RG+IlHGybNVC2zwOSCjCAEelXp4tMwri1xWeYRssijd
A1jyHbakI89bk6g9/J4qz+en1hP0rbKbvv5kMDk/3eReSTTuihMJs5vJZagd8Y1Q
mr2HLVIeH3qfy91+dr/wUK+I2OPdk0i+vqzrKpOFwetHCe5iudH+LHg3ad377MVl
ZqrEceE8O1O4cG1oD+0Tx5Icg49qscLUxEchybJF2gM1+Br8P8vfrRZ4aLJq1Gkc

Bug#1003563: aide: autopkgtest regression: unexpected character: '@' in /etc/aide/aide.conf.d/31_aide_spamassassin

[Marc Haber]

tags #1003563 confirmed pending
thanks

On Tue, Jan 11, 2022 at 10:29:55PM +0100, Paul Gevers wrote:
> With a recent upload of aide the autopkgtest of aide fails in testing when
> that autopkgtest is run with the binary packages of aide from unstable.

I somehow forgot to upload the fixed package I prepared to fix this. I
apologize but it will be next week until the fix, which is:

commit 1500412bacbde4c362744e7ca516778a80b04ef1 (tag: debian/0.17.3-6)
Author: Marc Haber 
Date:   Thu Dec 30 22:25:08 2021 +0100

fix broken 31_aide_spamassassinrule

diff --git a/debian/aide.conf.d/31_aide_spamassassin 
b/debian/aide.conf.d/31_aide_spamassassin
index b8fc83c..73528e5 100644
--- a/debian/aide.conf.d/31_aide_spamassassin
+++ b/debian/aide.conf.d/31_aide_spamassassin
@@ -1,6 +1,6 @@
 @@ifndef SAVERSION
 @@define SAVERSION 3.004006
-@endif
+@@endif
 
 /@@{RUN}/spamd\\.pid$ f VarFile
 /var/spool/spamassassin/bayes$ d VarDir

which can be applied manualy since it's a conffile. This won't help with
autopkgtests, but it makes the package useable where it is installed.

Marc
Greetings

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

Bug#999074: iec16022: missing required debian/rules targets build-arch and/or build-indep

[Jakob Haufe]

Debdiff attached


-- 
ceterum censeo microsoftem esse delendam.


iec16022_0.2.4-1.3.debdiff
Description: Binary data


pgp1MGui9kV9T.pgp
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 20:33:04 +
with message-id 
and subject line closing
has caused the Debian Bug report #965679,
regarding libpixels-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.)


-- 
965679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpixels-java
Version: 2.1.3+svn.42-2
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package libpixels-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 ---

I forgot to close this bug with my latest upload, the issue is now fixed.

--
Martina Ferrari (Tina)--- End Message ---

Bug#1003606: python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4)

[Martina Ferrari]

Argh, this was removed by `cme fix dpkg` and I trusted it.. :-/

Thanks for the report!

On 12/01/2022 14:15, Andreas Beckmann wrote:

Package: python3-flask-httpauth
Version: 4.5.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

   Preparing to unpack .../python3-flask-httpauth_4.5.0-1_all.deb ...
   Unpacking python3-flask-httpauth (4.5.0-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man1/flask-httpauth.1.gz', which is 
also in package python-flask-httpauth-doc 3.2.4-3.1
   Errors were encountered while processing:
/var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb

Obviously the manpage was moved between the packages.


cheers,

Andreas



--
Martina Ferrari (Tina)

Bug#1003628: imdbpy: autopkgtest failure on arm64: AssertionError: assert '' == 'Mandariinid'

[Paul Gevers]

Source: imdbpy
Version: 2021.04.18-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package imdbpy, great. 
However, it fails. Currently this failure is blocking the migration to 
testing [1]. Can you please investigate the situation and fix it?


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

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=imdbpy

https://ci.debian.net/data/autopkgtest/testing/arm64/i/imdbpy/18081764/log.gz

=== FAILURES 
===
___ test_movie_original_title[http] 



ia = 

def test_movie_original_title(ia):
movie = ia.get_movie('2991224', info=['main'])
title = movie.get('original title', '')

  assert title == 'Mandariinid'

E   AssertionError: assert '' == 'Mandariinid'
E - Mandariinid

tests/test_http_movie_titles.py:13: AssertionError
=== short test summary info 

FAILED tests/test_http_movie_titles.py::test_movie_original_title[http] 
- Ass...
 1 failed, 342 passed, 19 skipped in 308.55s (0:05:08) 
=

autopkgtest [11:35:41]: test unittests



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003627: fpc: autopkgtest regression on ppc64el:

[Paul Gevers]

Source: fpc
Version: 3.2.2+dfsg-5
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
fpcfrom testing3.2.2+dfsg-5
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/ppc64el/f/fpc/18260761/log.gz

Total = 7734 (55:7679)
Total number of compilations = 4753 (17:4736)
Successfully compiled = 3605
Successfully failed = 1131
Compilation failures = 14
Compilation that did not fail while they should = 3
Total number of runs = 2981 (38:2943)
Successful runs = 2943
Failed runs = 38
Number units compiled = 152
Number program that should not be run = 468
Number of skipped tests = 632
Number of skipped graph tests = 10
Number of skipped interactive tests = 31
Number of skipped known bug tests = 7
Number of skipped tests for other versions = 5
Number of skipped tests for other cpus = 397
Number of skipped tests for other targets = 182
make: Leaving directory 
'/tmp/autopkgtest-lxc.ims6woux/downtmp/build.IH3/src/fpcsrc/tests'

Let's save some of the output
Compare the new results with known results if we have them

Difference between expected failures and current failures:
--- debian/tests/ref_fail_powerpc64-linux	2021-12-30 13:48:26.0 
+
+++ fpcsrc/tests/output/powerpc64-linux/faillist	2022-01-12 
08:26:51.116689429 +

@@ -39,6 +39,7 @@
 webtbs/tw3157
 webtbs/tw36179
 webtbs/tw36863
+webtbs/tw36934a
 webtbs/tw3930
 webtbs/tw3964b
 webtbs/tw4809

Checking (and fail if so) for new failures:
Unexpected failures
autopkgtest [08:26:51]: test run-upstream-testsuite



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003621: marked as done (emscripten: test_icu and test_pthread_icu attempt to download files from github)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 19:33:49 +
with message-id 
and subject line Bug#1003621: fixed in emscripten 3.1.1~dfsg+~1.39.6-3
has caused the Debian Bug report #1003621,
regarding emscripten: test_icu and test_pthread_icu attempt to download files 
from github
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.)


-- 
1003621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emscripten
Version: 3.0.0~dfsg+~1.39.6-2
Severity: serious
Tags: patch
Justification: Policy 4.9
thanks

The test_icu and test_pthread_icu tests both attempt to download the
file 
.
This leads to an error like this on builders where access to the
network is restricted:

```
ports:INFO: retrieving port: icu from
https://github.com/unicode-org/icu/releases/download/release-68-2/icu4c-68_2-src.zip
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/urllib3/connection.py", line
169, in _new_conn
conn = connection.create_connection(
  File "/usr/lib/python3/dist-packages/urllib3/util/connection.py",
line 73, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
  File "/usr/lib/python3.9/socket.py", line 954, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution
```

I've attached a patch that disables the offending tests.

-- 
Mike Gerow
ge...@google.com
From f6aba87cf4bfa0093f0cd7bed280294dc38790ca Mon Sep 17 00:00:00 2001
From: Mike Gerow 
Date: Mon, 10 Jan 2022 14:12:57 -0800
Bug: b/213944458
Last-Update: 2022-01-10
Subject: [PATCH] Disable test_{,pthread}_icu since it opens sockets

test_icu and test_pthread_icu both attempt to download the file
'https://github.com/unicode-org/icu/releases/download/release-68-2/icu4c-68_2-src.zip'
as a part of their test. Builders and build servers don't always provide
full network access and this can cause false failures, in addition to
the potentially security implications of introducing an arbitrary remote
file as a part of the package build process.

This change skips those tests.
---
 debian/rules | 5 +
 1 file changed, 5 insertions(+)

diff --git a/debian/rules b/debian/rules
index c37b742f2..fc71b56a2 100755
--- a/debian/rules
+++ b/debian/rules
@@ -120,6 +120,11 @@ FAILS_wasm += \
  test_pthread_dylink_tls \
  test_dylink_tls_export
 
+# attempts to download files from a remote server
+FAILS_other += \
+  test_icu \
+  test_pthread_icu
+
 # unknown cause
 FAILS_wasm2js2 += \
  test_pthread_abort
-- 
2.34.1.575.g55b058a8bb-goog

--- End Message ---
--- Begin Message ---
Source: emscripten
Source-Version: 3.1.1~dfsg+~1.39.6-3
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated emscripten package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jan 2022 20:21:24 +0100
Source: emscripten
Architecture: source
Version: 3.1.1~dfsg+~1.39.6-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jonas Smedegaard 
Closes: 1003621
Changes:
 emscripten (3.1.1~dfsg+~1.39.6-3) unstable; urgency=medium
 .
   * avoid tests which attempts to download files from a remote server;
 closes: bug#1003621, thanks to Mike Gerow 
Checksums-Sha1:
 68c58e4e50af8d488adfad6597f9ece3fe03865a 2976 
emscripten_3.1.1~dfsg+~1.39.6-3.dsc
 7dfde46fc590cfd587d9ca855d37d1657dbf303a 83796 
emscripten_3.1.1~dfsg+~1.39.6-3.debian.tar.xz
 0541874a244c1ab93306eacd380789866b0a3d61 12276 
emscripten_3.1.1~dfsg+~1.39.6-3_amd64.buildinfo
Checksums-Sha256:
 d2230d2cc8a460c721a325ceee98ad9dac7ddc6608534ac130e16cbe46edaf2c 2976 
emscripten_3.1.1~dfsg+~1.39.6-3.dsc
 57ada6d8680088477258354eec61c245fb0ad9f75d344cecca03c914f3cf8938 83796 

Processed: tagging 999074

[Debian Bug Tracking System]

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

> tags 999074 + pending
Bug #999074 [src:iec16022] iec16022: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#984049: enblend-enfuse: ftbfs with GCC-11

[Andreas Tille]

Control: tags -1 help

Hi,

Am Tue, Dec 14, 2021 at 06:27:47PM +0100 schrieb Heinz Repp:
> > /usr/include/vigra/separableconvolution.hxx:1413:13: error: ISO C++17 does 
> > not allow dynamic exception specifications
> > /usr/include/vigra/stdconvolution.hxx:796:13: error: ISO C++17 does not 
> > allow dynamic exception specifications
> 
> For those two errors I propose the first patch (c++17conf, in
> include/vigra): The original code had conditional compilation in place: all
> non Microsoft compilers got a pre-C++11 and C++17-forbidden construct, and
> Microsoft Visual C++ 2014 and up got a C++11-introduced and C++17-conformant
> construct. I removed the condition and left only the latter - this means you
> need at least GCC 4.8.1 to compile this (or MSC 2014/201).

I applied this patch in Git and it seems that it helps to build this
package.
 
> 
> Then I found another syntax error in Python code - Python 3.10 requires
> parentheses around multiple except-clauses (pythonexcept, in vigranumpy).

This patch does not apply (the ',' was replaced by 'as' which is also
valid).
 
> With those two patches it compiles, but then 22 tests fail, all with the
> same error in C++ template syntax I am not familiar with. They all fail
> because of a single discrepancy between Python and C++ representation of the
> constructArrayFromAxistags function:
> 
> > Boost.Python.ArgumentError: Python argument types in
> > vigra.vigranumpycore.constructArrayFromAxistags(type, tuple, 
> > numpy.dtype[float32], AxisTags, bool)
> > did not match C++ signature:
> > constructArrayFromAxistags(boost::python::api::object, 
> > vigra::ArrayVector >, NPY_TYPES, 
> > vigra::AxisTags, bool)

I can confirm these test issues.  Any help would be welcome.
 
Kind regards

 Andreas.

-- 
http://fam-tille.de

Processed: Re: enblend-enfuse: ftbfs with GCC-11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #984049 [src:libvigraimpex] enblend-enfuse: ftbfs with GCC-11
Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11
Bug #1003547 [src:libvigraimpex] hugin: Hugun begins to block for a great 
number of packages
Bug #1003549 [src:libvigraimpex] enblend blocks for a number of packages
Bug #1003550 [src:libvigraimpex] enfuse blocks for a great number of packages
Ignoring request to alter tags of bug #984049 to the same tags previously set
Ignoring request to alter tags of bug #984213 to the same tags previously set
Ignoring request to alter tags of bug #1003547 to the same tags previously set
Ignoring request to alter tags of bug #1003549 to the same tags previously set
Ignoring request to alter tags of bug #1003550 to the same tags previously set

-- 
1003547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003547
1003549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003549
1003550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003550
984049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984049
984213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#1003621 marked as pending in emscripten

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1003621 [src:emscripten] emscripten: test_icu and test_pthread_icu attempt 
to download files from github
Added tag(s) pending.

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

Bug#1003621: marked as pending in emscripten

[Jonas Smedegaard]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/emscripten/-/commit/e884002497845ff5f36c6ee012595da5f7d54d59


avoid tests which attempts to download files from a remote server; closes: 
bug#1003621, thanks to Mike Gerow 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1003621

Bug#1003621: [Pkg-javascript-devel] Bug#1003621: emscripten: test_icu and test_pthread_icu attempt to download files from github

[Jonas Smedegaard]

Quoting Mike Gerow (2022-01-12 19:40:33)
> The test_icu and test_pthread_icu tests both attempt to download the
> file 
> .
> This leads to an error like this on builders where access to the
> network is restricted:

Thanks!

Should be fixed within few hours...

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1001545: [Pkg-opencl-devel] Bug#1001545: pyopencl, build-depends on package that is no longer in testing

[Drew Parsons]

On 2022-01-12 20:00, Rebecca N. Palmer wrote:

On 12/01/2022 12:50, Drew Parsons wrote:
mesa-opencl-icd is running and passing its own tests on these arches. 
What is pyopencl doing in build and tests that's different from what 
mesa-opencl-icd itself does?


Probably that pyopencl's tests actually run OpenCL code and mesa's (at
least the ones that get run on a buildd) don't.

pyopencl is a package that uses OpenCL, so it makes sense to run its
tests via whatever OpenCL driver works on that hardware, which on the
buildds means pocl-opencl-icd.

mesa-opencl-icd is an OpenCL driver that requires a GPU, so if it has
tests that run OpenCL code, it probably doesn't run them on the
buildd.  (It might run them on a maintainer's local machine where the
right GPU is available, like beignet-opencl-icd does.)


Thanks Rebecca.

Do we know what pyopencl would do on, say, ppc64el with mesa-opencl-icd 
installed?  At the moment it not even trying. Would it fail to build? If 
it's only tests that would fail, then they could be skipped.


Another way to put the question, does OpenCL make any sense at all on 
the failing architectures like ppc64el? (and are GPUs potentially 
available for ppc64el etc, even if not available on buildds?)


What I'm wondering is whether we might want

  Build-Depends: pocl-opencl-icd [amd64 arm64 armel armhf i386 
hurd-i386], mesa-opencl-icd [!amd64 !arm64 !armel !armhf !i386 
!hurd-i386]

Processed: block 1003573 with 1003618, block 1002444 with 1003618, tagging 1002444

[Debian Bug Tracking System]

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

> block 1003573 with 1003618
Bug #1003573 [python-pip-whl] python-pip-whl: Migrate from dirtbike back to 
individual wheel packages
1003573 was not blocked by any bugs.
1003573 was not blocking any bugs.
Added blocking bug(s) of 1003573: 1003618
> block 1002444 with 1003618
Bug #1002444 [src:python-setuptools] python-setuptools: FTBFS: 
ModuleNotFoundError: No module named 'distutils.command.bdist_wininst'
1002444 was not blocked by any bugs.
1002444 was not blocking any bugs.
Added blocking bug(s) of 1002444: 1003618
> tags 1002444 + pending
Bug #1002444 [src:python-setuptools] python-setuptools: FTBFS: 
ModuleNotFoundError: No module named 'distutils.command.bdist_wininst'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1003309: marked as done (vdr-plugin-streamdev FTBFS: error: invalid conversion from ‘cChannel*’ to ‘int’)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 19:03:58 +
with message-id 
and subject line Bug#1003309: fixed in vdr-plugin-streamdev 0.6.1+git20180514-5
has caused the Debian Bug report #1003309,
regarding vdr-plugin-streamdev FTBFS: error: invalid conversion from 
‘cChannel*’ to ‘int’
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.)


-- 
1003309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-streamdev
Version: 0.6.1+git20180514-4
Severity: serious
Tags: ftbfs

vdr-plugin-streamdev fails to build from source in unstable on amd64. A
non-parallel build now ends as follows:

| g++ -g -O2 -ffile-prefix-map=/build/vdr-dx7twj/vdr-2.6.0=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE 
-DPLUGIN_NAME_I18N='"streamdev-server"' -I/include -I.. -o connectionVTP.o 
connectionVTP.c
| connectionVTP.c: In member function ‘bool cConnectionVTP::CmdMOVC(const 
char*)’:
| connectionVTP.c:1885:108: error: invalid conversion from ‘cChannel*’ to ‘int’ 
[-fpermissive]
|  1885 |   
  cDevice::SetCurrentChannel(CurrentChannel);
|   |   
 ^~
|   |   
 |
|   |   
 cChannel*
| In file included from /usr/include/vdr/dvbdevice.h:15,
|  from /usr/include/vdr/menuitems.h:14,
|  from /usr/include/vdr/plugin.h:14,
|  from ../common.h:15,
|  from ../server/connection.h:9,
|  from ../server/connectionVTP.h:4,
|  from connectionVTP.c:5:
| /usr/include/vdr/device.h:366:37: note:   initializing argument 1 of ‘static 
void cDevice::SetCurrentChannel(int)’
|   366 |   static void SetCurrentChannel(int ChannelNumber) { currentChannel = 
ChannelNumber; }
|   | ^
| connectionVTP.c: In member function ‘bool cConnectionVTP::CmdDELC(const 
char*)’:
| connectionVTP.c:1986:84: error: invalid conversion from ‘cChannel*’ to ‘int’ 
[-fpermissive]
|  1986 | 
cDevice::SetCurrentChannel(CurrentChannel);
|   |   
 ^~
|   |   
 |
|   |   
 cChannel*
| In file included from /usr/include/vdr/dvbdevice.h:15,
|  from /usr/include/vdr/menuitems.h:14,
|  from /usr/include/vdr/plugin.h:14,
|  from ../common.h:15,
|  from ../server/connection.h:9,
|  from ../server/connectionVTP.h:4,
|  from connectionVTP.c:5:
| /usr/include/vdr/device.h:366:37: note:   initializing argument 1 of ‘static 
void cDevice::SetCurrentChannel(int)’
|   366 |   static void SetCurrentChannel(int ChannelNumber) { currentChannel = 
ChannelNumber; }
|   | ^
| make[2]: *** [Makefile:39: connectionVTP.o] Error 1
| make[2]: Leaving directory '/<>/server'
| make[1]: *** [Makefile:80: server] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 "INSTALL=install --strip-program=true" 
returned exit code 2
| make: *** [debian/rules:9: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Source: vdr-plugin-streamdev
Source-Version: 0.6.1+git20180514-5
Done: Tobias Grimm 

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

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

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

Debian distribution maintenance software
pp.
Tobias 

Bug#1002020: marked as done (php-proxy-manager: Failing testsuite with PHP 8.1)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 18:49:18 +
with message-id 
and subject line Bug#1002020: fixed in php-proxy-manager 2.11.1+1.0.5-2
has caused the Debian Bug report #1002020,
regarding php-proxy-manager: Failing testsuite with PHP 8.1
to be marked as done.

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

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


-- 
1002020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-proxy-manager
Version: 2.11.1+1.0.3-1
Severity: important
Control: block 976811 by -1
Control: found -1 2.11.1+1.0.5-1

Hi,

The testsuite is currently failing with PHP 8:

(see
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/php-proxy-manager/17524886/log.gz
or more recent)

[…]
There were 9 failures:

1) 
/tmp/autopkgtest-lxc.bnfk1eqk/downtmp/build.0sn/src/tests/language-feature-scripts/access-interceptor-scope-localizer-serialized-class-private-property-isset.phpt
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'bool(false)'
+'Deprecated: Kitchen implements the Serializable interface, which is 
deprecated. Implement __serialize() and __unserialize() instead (or in 
addition, if support for old PHP versions is necessary) in Standard input code 
on line 5\n
+\n
+Deprecated: 
ProxyManagerGeneratedProxy\__PM__\Kitchen\Generated3e0dd340cc53a6b11dc36d7d0976dff6
 implements the Serializable interface, which is deprecated. Implement 
__serialize() and __unserialize() instead (or in addition, if support for old 
PHP versions is necessary) in 
/usr/share/php/ProxyManager/GeneratorStrategy/EvaluatingGeneratorStrategy.php(54)
 : eval()'d code on line 3\n
+bool(false)'

/tmp/autopkgtest-lxc.bnfk1eqk/downtmp/build.0sn/src/tests/language-feature-scripts/access-interceptor-scope-localizer-serialized-class-private-property-isset.phpt:30

2) 
/tmp/autopkgtest-lxc.bnfk1eqk/downtmp/build.0sn/src/tests/language-feature-scripts/access-interceptor-scope-localizer-serialized-class-private-property-read.phpt
Failed asserting that string matches format description.
--- Expected
+++ Actual
@@ @@
-%SFatal error:%sCannot access private property %s::$sweets in %a
+Deprecated: Kitchen implements the Serializable interface, which is 
deprecated. Implement __serialize() and __unserialize() instead (or in 
addition, if support for old PHP versions is necessary) in Standard input code 
on line 5
+
+Deprecated: 
ProxyManagerGeneratedProxy\__PM__\Kitchen\Generated3e0dd340cc53a6b11dc36d7d0976dff6
 implements the Serializable interface, which is deprecated. Implement 
__serialize() and __unserialize() instead (or in addition, if support for old 
PHP versions is necessary) in 
/usr/share/php/ProxyManager/GeneratorStrategy/EvaluatingGeneratorStrategy.php(54)
 : eval()'d code on line 3
+
+Fatal error: Uncaught Error: Cannot access private property Kitchen::$sweets 
in 
/usr/share/php/ProxyManager/GeneratorStrategy/EvaluatingGeneratorStrategy.php(54)
 : eval()'d code:155
+Stack trace:
+#0 
/usr/share/php/ProxyManager/GeneratorStrategy/EvaluatingGeneratorStrategy.php(54)
 : eval()'d code(160): 
ProxyManager\Stub\EmptyClassStub->ProxyManagerGeneratedProxy\__PM__\Kitchen\{closure}()
+#1 Standard input code(24): 
ProxyManagerGeneratedProxy\__PM__\Kitchen\Generated3e0dd340cc53a6b11dc36d7d0976dff6->__get()
+#2 {main}
+  thrown in 
/usr/share/php/ProxyManager/GeneratorStrategy/EvaluatingGeneratorStrategy.php(54)
 : eval()'d code on line 155

/tmp/autopkgtest-lxc.bnfk1eqk/downtmp/build.0sn/src/tests/language-feature-scripts/access-interceptor-scope-localizer-serialized-class-private-property-read.phpt:30
[…]


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: php-proxy-manager
Source-Version: 2.11.1+1.0.5-2
Done: David Prévot 

We believe that the bug you reported is fixed in the latest version of
php-proxy-manager, 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.
David Prévot  (supplier of updated php-proxy-manager 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, 12 Jan 2022 14:32:25 -0400

Processed: limit source to php-proxy-manager, tagging 1002020

[Debian Bug Tracking System]

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

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

> tags 1002020 + pending
Bug #1002020 [php-proxy-manager] php-proxy-manager: Failing testsuite with PHP 
8.1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1000647: marked as done (php-phpseclib3: Failing testsuite with PHP 8.1)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 18:19:02 +
with message-id 
and subject line Bug#1000647: fixed in php-phpseclib3 3.0.12-2
has caused the Debian Bug report #1000647,
regarding php-phpseclib3: Failing testsuite with PHP 8.1
to be marked as done.

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

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


-- 
1000647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-phpseclib3
Version: 3.0.11-2
Severity: normal
Tags: upstream
Control: block by -1

Hi,

The testsuite is currently failing under PHP 8.1. I didn’t notice any
upstream activity about it yet, but hope it will happen soon.

Regards

David


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: php-phpseclib3
Source-Version: 3.0.12-2
Done: David Prévot 

We believe that the bug you reported is fixed in the latest version of
php-phpseclib3, 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-phpseclib3 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, 12 Jan 2022 12:10:59 -0400
Source: php-phpseclib3
Architecture: source
Version: 3.0.12-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 1000647
Changes:
 php-phpseclib3 (3.0.12-2) unstable; urgency=medium
 .
   * Fix tests for PHP 8.1 (Closes: #1000647)
Checksums-Sha1:
 0510a6009209608c44c2146b37227263a242b84e 1869 php-phpseclib3_3.0.12-2.dsc
 86332e1d997271e99fbb9e951a72640183918ef5 11996 
php-phpseclib3_3.0.12-2.debian.tar.xz
 732ffd07d7d0b0c25d4a559899ceb773276bf2df 7694 
php-phpseclib3_3.0.12-2_amd64.buildinfo
Checksums-Sha256:
 40bebadf368a18d7f892f151fb0e7ec050add2ecaa930e63391e9a7334d6298e 1869 
php-phpseclib3_3.0.12-2.dsc
 5726a77aa630961c81887cd4cf1f63095f211b7553b2453437b8940a93132a79 11996 
php-phpseclib3_3.0.12-2.debian.tar.xz
 c32c1dc26b7b17da27cc11e3e1f43ac9400b1eb0ee9a51d4fc0810b1c981ca18 7694 
php-phpseclib3_3.0.12-2_amd64.buildinfo
Files:
 14d51747610ee0f3498b09cc4b7d72b1 1869 php optional php-phpseclib3_3.0.12-2.dsc
 f7a9ae34f2c2303ba0e481b0493bfc21 11996 php optional 
php-phpseclib3_3.0.12-2.debian.tar.xz
 8e7da077c290b41b9688bd2ccb1ac3b9 7694 php optional 
php-phpseclib3_3.0.12-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAmHfAKASHHRhZmZpdEBk
ZWJpYW4ub3JnAAoJEAWMHPlE9r08IcgH+wR8jSDyLVWmyeStHRp+n6tqTNhNS0sF
4IJGgSdV0oy63mFLaUK/bnZY1dBMhdLVFUVwpvyNBh1g2OjAtoym3DsBTA4MXPqq
5DFadbrCootHgfq6AGaTRmy4MqmMeEV+b+b21HqbZEU6rQxxyWE++8bxNkZn3crP
/flB7S8Pn2h1LVMbzAUTRVozMEc1fSgCCusCBe90uRSV+vzNLe4sA+WfQ+PyaSu3
gF9AZGqVgVENhDOs/dcc4qS8dXjuws19JkBB4bVX7BHCSt5mKhqxtoWdCp1vJyAV
scSR4dFiUZCEGo10ou+dsjKnXT22PXvCJwvDQM89ZZCfhQVfcaBNXJo=
=nQ95
-END PGP SIGNATURE End Message ---

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Michael Biebl]

Control: found -1 249.7-1
Control: severity -1 important

Am 12.01.22 um 18:20 schrieb Christian Weeks:

I don't see anything in the journal, I've had a fairly long look. I do not have
the coredump utility installed.
As I have mentioned, rebooting fixed whatever caused the problem during the
upgrade, so I have no idea how I can help you further.

In looking at my running system since, I notice that systemd isn't defaulting to
running, so I guess the problem was actually that dbus was failing to activate
systemd properly, during the upgrade.

I have found a core file, but it's dated from 10 days ago, not today, which is
weird. There was no activity on the computer at the time, I believe, and this
went unnoticed, perhaps for 10 days?!


As said, systemd freezes execution when it crashes.
If PID 1 actually crashed, the kernel would panic and you'd notice :-)


Jan  2 10:14:48 cheesypuffs kernel: [336844.954825] systemd[1]: segfault at 18
ip 55bd29c926ea sp 7ffdcd0c56c8 error 4 in systemd[55bd29c38000+d9000]


ls -l /core
-rw--- 1 root root 22482944 Jan  2 10:14 /core

I can share this core file with you if you wish (how?), though perhaps it's not
so related to the upgrade anymore?


Given the timestamps match, it's pretty certain, that the core file 
belongs to the segfault.
It also shows that PID 1 crashing is not actually affecting the running 
services. As long as you don't interact with systemd (e.g. via 
systemctl), your system should continue to run fine.

I'm thus downgrading the severity.
As it is not actually related to the upgrade, I'm marking it as found in 
249.7-1.


You can attach the core file to the bug report (gzipped) or mail it to 
me directly. I will try to see if a backtrace reveals something.


Michael


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Debian Bug Tracking System]

Processing control commands:

> found -1 249.7-1
Bug #1003611 [systemd] systemd: Upgrade from 249.7 to 250.2 seems to have 
crashed the systemd root process, leaving system unstable
Marked as found in versions systemd/249.7-1.
> severity -1 important
Bug #1003611 [systemd] systemd: Upgrade from 249.7 to 250.2 seems to have 
crashed the systemd root process, leaving system unstable
Severity set to 'important' from 'critical'

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

Bug#1003617: libpam-runtime: When upgrading to libpam-runtime_1.4.0-11 pam_ssh is broken

[Vincent-Xavier JUMEL]

Package: libpam-runtime
Version: 1.4.0-11
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * Upgrade to the unstable version of libpam-runtime_1.14.0_11_all
   with 
   ```
   auth[success=0 default=ignore]  pam_ssh.so use_first_pass
   ```
   * Login then failed
   * I've modified "success=0" -> "success=1" to get back the login.



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-debug'), (500, 
'oldstable-updates'), (500, 'oldstable-debug'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (500, 'oldstable'), (100, 'buster-fasttrack'), 
(100, 'buster-backports'), (100, 'bullseye-fasttrack'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libpam-runtime depends on:
ii  debconf [debconf-2.0]  1.5.79
ii  libpam-modules 1.4.0-11

libpam-runtime recommends no packages.

libpam-runtime suggests no packages.

-- debconf information:
  libpam-runtime/conflicts:
  libpam-runtime/override: false
* libpam-runtime/profiles: passwdqc, unix, ssh-pwd, tmpdir, systemd
  libpam-runtime/no_profiles_chosen:
  libpam-runtime/title:

-- 
Vincent-Xavier JUMEL Id: 0xBC8C2BAB14ABB3F2 https://blog.thetys-retz.net

Société Libre, Logiciel Libre http://www.april.org/adherer
Parinux, logiciel libre à Paris : http://www.parinux.org

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Christian Weeks]

I don't see anything in the journal, I've had a fairly long look. I do not have
the coredump utility installed.
As I have mentioned, rebooting fixed whatever caused the problem during the
upgrade, so I have no idea how I can help you further.

In looking at my running system since, I notice that systemd isn't defaulting to
running, so I guess the problem was actually that dbus was failing to activate
systemd properly, during the upgrade.

I have found a core file, but it's dated from 10 days ago, not today, which is
weird. There was no activity on the computer at the time, I believe, and this
went unnoticed, perhaps for 10 days?!

Jan  2 10:14:48 cheesypuffs kernel: [336844.954825] systemd[1]: segfault at 18
ip 55bd29c926ea sp 7ffdcd0c56c8 error 4 in systemd[55bd29c38000+d9000]


ls -l /core
-rw--- 1 root root 22482944 Jan  2 10:14 /core

I can share this core file with you if you wish (how?), though perhaps it's not
so related to the upgrade anymore?

Christian
On Wed, 2022-01-12 at 18:01 +0100, Michael Biebl wrote:
> Control: tags -1 + moreinfo
> 
> Hello,
> 
> systemd freezes execution when it crashes (you should see a 
> corresponding log message in the journal).
> 
> For this bug report to be actionable, we will need at the very least a 
> backtrace of the crash.
> In case you had systemd-coredump installed, coredumpctl should show you.
> Or maybe you still have a core file in /.
> 
> 
> Regards,
> Michael
> 

Bug#1001811: marked as done (postgresql-mysql-fdw: autopkgtest regression on armhf and i386: failed to look up symbol "evalexpr_19_0")

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 17:18:45 +
with message-id 
and subject line Bug#1001811: fixed in postgresql-mysql-fdw 2.7.0-2
has caused the Debian Bug report #1001811,
regarding postgresql-mysql-fdw: autopkgtest regression on armhf and i386: 
failed to look up symbol "evalexpr_19_0"
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.)


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

Source: postgresql-mysql-fdw
Version: 2.7.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
postgresql-mysql-fdw   from testing2.7.0-1
all others from testingfrom testing

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

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


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

Paul

[1] https://qa.debian.org/excuses.php?package=postgresql-mysql-fdw

https://ci.debian.net/data/autopkgtest/testing/i386/p/postgresql-mysql-fdw/17609222/log.gz

== creating the MySQL test database
--
CREATE DATABASE mysql_fdw_regress
--

--
CREATE DATABASE mysql_fdw_regress1
--

--
CREATE USER 'edb'@'localhost' IDENTIFIED BY 'edb'
--

--
GRANT ALL PRIVILEGES ON mysql_fdw_regress.* TO 'edb'@'localhost'
--

--
GRANT ALL PRIVILEGES ON mysql_fdw_regress1.* TO 'edb'@'localhost'
--

### PostgreSQL 14 installcheck ###
Creating new PostgreSQL cluster 14/regress ...
/usr/lib/postgresql/14/lib/pgxs/src/makefiles/../../src/test/regress/pg_regress 
--inputdir=./ --bindir='/usr/lib/postgresql/14/bin' 
--dbname=contrib_regression server_options connection_validation dml 
select pushdown join_pushdown aggregate_pushdown

(using postmaster on localhost, port 5433)
== dropping database "contrib_regression" ==
NOTICE:  database "contrib_regression" does not exist, skipping
DROP DATABASE
== creating database "contrib_regression" ==
CREATE DATABASE
ALTER DATABASE
== running regression test queries==
test server_options   ... ok  107 ms
test connection_validation... ok   70 ms
test dml  ... ok  132 ms
test select   ... ok  555 ms
test pushdown ... ok  123 ms
test join_pushdown... ok 1620 ms
test aggregate_pushdown   ... FAILED 2824 ms

==
 1 of 7 tests failed. ==

The differences that caused some tests to fail can be viewed in the
file 
"/tmp/autopkgtest-lxc.r_7rxru0/downtmp/build.z8H/src/regression.diffs". 
 A copy of the test summary that you see
above is saved in the file 
"/tmp/autopkgtest-lxc.r_7rxru0/downtmp/build.z8H/src/regression.out".


make: *** [/usr/lib/postgresql/14/lib/pgxs/src/makefiles/pgxs.mk:433: 
installcheck] Error 1
*** /tmp/pg_virtualenv.joAylJ/log/postgresql-14-regress.log (last 100 
lines) ***
2021-12-16 10:13:48.401 UTC [4153] LOG:  starting PostgreSQL 14.1 
(Debian 14.1-1) on i686-pc-linux-gnu, compiled by gcc (Debian 11.2.0-10) 
11.2.0, 32-bit
2021-12-16 10:13:48.402 UTC [4153] LOG:  listening on IPv6 address 
"::1", port 5433
2021-12-16 10:13:48.402 UTC [4153] LOG:  listening on IPv4 address 
"127.0.0.1", port 5433
2021-12-16 10:13:48.402 UTC [4153] LOG:  listening on Unix socket 
"/var/run/postgresql/.s.PGSQL.5433"
2021-12-16 10:13:48.403 UTC [4154] LOG:  database system was shut down 
at 2021-12-16 10:13:48 UTC
2021-12-16 10:13:48.407 UTC [4153] LOG:  database system is ready to 
accept connections
2021-12-16 10:13:50.785 UTC [4205] postgres@contrib_regression WARNING: 
 MySQL secure authentication is off
2021-12-16 10:13:50.791 UTC [4205] postgres@contrib_regression ERROR: 
"fetch_size" requires an integer value between 1 to 4294967295
2021-12-16 10:13:50.791 UTC [4205] postgres@contrib_regression 
STATEMENT:  ALTER 

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Michael Biebl]

Control: tags -1 + moreinfo

Hello,

systemd freezes execution when it crashes (you should see a 
corresponding log message in the journal).


For this bug report to be actionable, we will need at the very least a 
backtrace of the crash.

In case you had systemd-coredump installed, coredumpctl should show you.
Or maybe you still have a core file in /.


Regards,
Michael



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1003611 [systemd] systemd: Upgrade from 249.7 to 250.2 seems to have 
crashed the systemd root process, leaving system unstable
Added tag(s) moreinfo.

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

Processed: Bug#1001811 marked as pending in postgresql-mysql-fdw

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1001811 [src:postgresql-mysql-fdw] postgresql-mysql-fdw: autopkgtest 
regression on armhf and i386: failed to look up symbol "evalexpr_19_0"
Added tag(s) pending.

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

Bug#1001811: marked as pending in postgresql-mysql-fdw

[Christoph Berg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/postgresql/postgresql-mysql-fdw/-/commit/28e57b9486b6c2d2221b82134f3c4a2eafc27be0


Disable jit for tests; works around "failed to resolve name __mulodi4".

Cf. https://github.com/EnterpriseDB/mysql_fdw/pull/227.

Closes: #1001811


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1001811

Processed: limit source to php-phpseclib3, tagging 1000647

[Debian Bug Tracking System]

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

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

> tags 1000647 + pending
Bug #1000647 [php-phpseclib3] php-phpseclib3: Failing testsuite with PHP 8.1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1003611: Acknowledgement (systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable)

[Christian Weeks]

The reboot fixed the issue - I now have a working computer again, though getting
to a reboot was a bit painful.

> systemctl reboot
Failed to reboot system via logind: Connection timed out
Failed to start reboot.target: Connection timed out
See system logs and 'systemctl status reboot.target' for details.
It is possible to perform action directly, see discussion of --force --force in
man:systemctl(1).
> systemctl reboot --force
Failed to execute operation: Failed to activate service
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
It is possible to perform action directly, see discussion of --force --force in
man:systemctl(1).
> systemctl reboot --force --force 



On Wed, 2022-01-12 at 15:36 +, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> You can follow progress on this Bug here: 1003611:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003611.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Debian systemd Maintainers 
> 
> If you wish to submit further information on this problem, please
> send it to 1003...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 

Bug#1003611: systemd: Upgrade from 249.7 to 250.2 seems to have crashed the systemd root process, leaving system unstable

[Christian Weeks]

Package: systemd
Version: 250.2-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

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

   * What led up to the situation?
I upgraded my local sid installation, which was about a week out of date.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Nothing
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

I have just performed an upgrade of sid, which included the 250.2 systemd 
update. It seems that during that update the root systemd
process has died, and now every request of systemd is timing out, causing 
packages to fail to install and who knows what other issues.
I'm reluctant to reboot, but I will have to I guess, and hope that systemd 
manages to load itself properly afterwards.

Some relevant snippets from the upgrade in flight:

...
Unpacking xserver-xorg-core (2:1.20.14-1) over (2:1.20.13-3) ...
Preparing to unpack .../15-systemd-timesyncd_250.2-1_amd64.deb ...
Unpacking systemd-timesyncd (250.2-1) over (249.7-1) ...
Preparing to unpack .../16-libpam-systemd_250.2-1_amd64.deb ...
Unpacking libpam-systemd:amd64 (250.2-1) over (249.7-1) ...
Setting up libc6:amd64 (2.33-2) ...
(Reading database ... 639000 files and directories currently installed.)
Preparing to unpack .../systemd_250.2-1_amd64.deb ...
Unpacking systemd (250.2-1) over (249.7-1) ...
Setting up libc6:i386 (2.33-2) ...
(Reading database ... 639034 files and directories currently installed.)
Preparing to unpack .../00-libsystemd0_250.2-1_amd64.deb ...
De-configuring libsystemd0:i386 (249.7-1), to allow configuration of 
libsystemd0:amd64 (249.7-1) ...
Unpacking libsystemd0:amd64 (250.2-1) over (249.7-1) ...
Preparing to unpack .../01-libsystemd0_250.2-1_i386.deb ...
Unpacking libsystemd0:i386 (250.2-1) over (249.7-1) ...
Preparing to unpack .../02-libudev-dev_250.2-1_i386.deb ...
De-configuring libudev-dev:amd64 (249.7-1), to allow configuration of 
libudev-dev:i386 (249.7-1) ...
Unpacking libudev-dev:i386 (250.2-1) over (249.7-1) ...
Preparing to unpack .../03-libudev-dev_250.2-1_amd64.deb ...
Unpacking libudev-dev:amd64 (250.2-1) over (249.7-1) ...
Preparing to unpack .../04-udev_250.2-1_amd64.deb ...
Unpacking udev (250.2-1) over (249.7-1) ...
Preparing to unpack .../05-libudev1_250.2-1_amd64.deb ...
De-configuring libudev1:i386 (249.7-1), to allow configuration of 
libudev1:amd64 (249.7-1) ...
Unpacking libudev1:amd64 (250.2-1) over (249.7-1) ...
Preparing to unpack .../06-libudev1_250.2-1_i386.deb ...
Unpacking libudev1:i386 (250.2-1) over (249.7-1) ...
Preparing to unpack .../07-libglx-dev_1.4.0-1_i386.deb ...
De-configuring libglx-dev:amd64 (1.3.4-2+b1), to allow configuration of 
libglx-dev:i386 (1.3.4-2+b1) ...
...
De-configuring libglvnd0:i386 (1.3.4-2+b1), to allow configuration of 
libglvnd0:amd64 (1.3.4-2+b1) ...
Unpacking libglvnd0:amd64 (1.4.0-1) over (1.3.4-2+b1) ...
Preparing to unpack .../53-libglvnd0_1.4.0-1_i386.deb ...
Unpacking libglvnd0:i386 (1.4.0-1) over (1.3.4-2+b1) ...
Setting up libsystemd0:amd64 (250.2-1) ...
Setting up systemd (250.2-1) ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/system.conf ...
Failed to try-restart systemd-networkd.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
See system logs and 'systemctl status systemd-networkd.service' for details.
Failed to try-restart systemd-resolved.service: Connection timed out
See system logs and 'systemctl status systemd-resolved.service' for details.
Failed to try-restart systemd-journald.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
See system logs and 'systemctl status systemd-journald.service' for details.
(Reading database ... 639016 files and directories currently installed.)
Preparing to unpack .../00-systemd-sysv_250.2-1_amd64.deb ...
Unpacking systemd-sysv (250.2-1) over (249.7-1) ...
Preparing to unpack .../01-libgnutls28-dev_3.7.2-5_amd64.deb ...
De-configuring libgnutls28-dev:i386 (3.7.2-4), to allow configuration of 
libgnutls28-dev:amd64 (3.7.2-4) ...
...
Setting up udev (250.2-1) ...
Failed to reload daemon: Failed to activate service 'org.freedesktop.systemd1': 
timed out (service_start_timeout=25000ms)
Failed to restart udev.service: Failed to activate service 
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
See system logs and 'systemctl status udev.service' for details.
invoke-rc.d: initscript udev, action "restart" failed.
Failed to get properties: Connection timed out
dpkg: error processing package udev (--configure):
 installed udev package post-installation script subprocess returned error exit 
status 1
Setting up libss2:amd64 (1.46.5-2) ...
...
Errors were encountered while processing:
 udev
 

Processed: Re: mpqc: ftbfs with GCC-11

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/ValeevGroup/mpqc/issues/60
Bug #984244 [src:mpqc] mpqc: ftbfs with GCC-11
Set Bug forwarded-to-address to 'https://github.com/ValeevGroup/mpqc/issues/60'.

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

Bug#984244: mpqc: ftbfs with GCC-11

[Andreas Tille]

Control: forwarded -1 https://github.com/ValeevGroup/mpqc/issues/60

Bug#984121: fbreader: ftbfs with GCC-11

[Ying-Chun Liu (PaulLiu)]

Hi,


this patches fixes the bug. I'll do QA uploads soon.

Yours,
Paul

Description: Fix FTBFS for gcc 11
 Comparator operator() have to be const in gcc 11.
Bug-Debian: http://bugs.debian.org/984121
Author: Ying-Chun Liu (PaulLiu) 
Index: fbreader-0.12.10dfsg2/fbreader/src/library/Comparators.cpp
===
--- fbreader-0.12.10dfsg2.orig/fbreader/src/library/Comparators.cpp
+++ fbreader-0.12.10dfsg2/fbreader/src/library/Comparators.cpp
@@ -25,7 +25,7 @@
 bool BookComparator::operator() (
 	const shared_ptr book0,
 	const shared_ptr book1
-) {
+) const {
 	const std::string  = book0->seriesTitle();
 	const std::string  = book1->seriesTitle();
 	int comp = seriesTitle0.compare(seriesTitle1);
@@ -50,14 +50,14 @@ bool BookComparator::operator() (
 bool BookByFileNameComparator::operator() (
 	const shared_ptr book0,
 	const shared_ptr book1
-) {
+) const {
 	return book0->filePath() < book1->filePath();
 }
 
 bool AuthorComparator::operator() (
 	const shared_ptr author0,
 	const shared_ptr author1
-) {
+) const {
 	if (author0.isNull()) {
 		return !author1.isNull();
 	}
@@ -72,7 +72,7 @@ bool AuthorComparator::operator() (
 bool TagComparator::operator() (
 	shared_ptr tag0,
 	shared_ptr tag1
-) {
+) const {
 	if (tag0.isNull()) {
 		return !tag1.isNull();
 	}
Index: fbreader-0.12.10dfsg2/fbreader/src/library/Comparators.h
===
--- fbreader-0.12.10dfsg2.orig/fbreader/src/library/Comparators.h
+++ fbreader-0.12.10dfsg2/fbreader/src/library/Comparators.h
@@ -32,7 +32,7 @@ public:
 	bool operator () (
 		const shared_ptr book0,
 		const shared_ptr book1
-	);
+	) const;
 };
 
 class BookByFileNameComparator {
@@ -41,7 +41,7 @@ public:
 	bool operator () (
 		const shared_ptr book0,
 		const shared_ptr book1
-	);
+	) const;
 };
 
 class AuthorComparator {
@@ -50,7 +50,7 @@ public:
 	bool operator () (
 		const shared_ptr author0,
 		const shared_ptr author1
-	);
+	) const;
 };
 
 class TagComparator {
@@ -59,7 +59,7 @@ public:
 	bool operator () (
 		shared_ptr tag0,
 		shared_ptr tag1
-	);
+	) const;
 };
 
 #endif /* __COMPARATORS_H__ */
Index: fbreader-0.12.10dfsg2/fbreader/src/network/NetworkComparators.cpp
===
--- fbreader-0.12.10dfsg2.orig/fbreader/src/network/NetworkComparators.cpp
+++ fbreader-0.12.10dfsg2/fbreader/src/network/NetworkComparators.cpp
@@ -19,7 +19,7 @@
 
 #include "NetworkComparators.h"
 
-bool NetworkBookItemComparator::operator () (const shared_ptr , const shared_ptr ) {
+bool NetworkBookItemComparator::operator () (const shared_ptr , const shared_ptr ) const {
 	const bool book0isABook =
 		bookPtr0->isInstanceOf(NetworkBookItem::TYPE_ID);
 	const bool book1isABook =
@@ -81,7 +81,7 @@ bool NetworkBookItemComparator::operator
 NetworkAuthorComparator::NetworkAuthorComparator(const std::map ) : myRates(rates) {
 }
 
-bool NetworkAuthorComparator::operator () (const NetworkBookItem::AuthorData , const NetworkBookItem::AuthorData ) {
+bool NetworkAuthorComparator::operator () (const NetworkBookItem::AuthorData , const NetworkBookItem::AuthorData ) const {
 	std::map::const_iterator it1 = myRates.find(author0);
 	std::map::const_iterator it2 = myRates.find(author1);
 	if (it1 == myRates.end() && it2 == myRates.end()) {
Index: fbreader-0.12.10dfsg2/fbreader/src/network/NetworkComparators.h
===
--- fbreader-0.12.10dfsg2.orig/fbreader/src/network/NetworkComparators.h
+++ fbreader-0.12.10dfsg2/fbreader/src/network/NetworkComparators.h
@@ -29,7 +29,7 @@
 class NetworkBookItemComparator {
 
 public:
-	bool operator () (const shared_ptr , const shared_ptr );
+	bool operator () (const shared_ptr , const shared_ptr ) const;
 };
 
 
@@ -38,7 +38,7 @@ class NetworkAuthorComparator {
 public:
 	NetworkAuthorComparator(const std::map );
 
-	bool operator () (const NetworkBookItem::AuthorData , const NetworkBookItem::AuthorData );
+	bool operator () (const NetworkBookItem::AuthorData , const NetworkBookItem::AuthorData ) const;
 
 private:
 	const std::map 


OpenPGP_signature
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 15:43:52 +0100
with message-id <37cf8428-0fa8-60dc-8578-2736a666a...@debian.org>
and subject line Re: lgrind: missing required debian/rules targets build-arch 
and/or build-indep
has caused the Debian Bug report #999122,
regarding lgrind: 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.)


-- 
999122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lgrind
Version: 3.67-4
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 ---

Version: 3.67-5

On Tue, 09 Nov 2021 22:28:16 +0100 Lucas Nussbaum  wrote:

Source: lgrind
Version: 3.67-4



Your package does not include build-arch and/or build-indep targets in

...

could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.


lgrind (3.67-5) unstable; urgency=medium

  * QA upload.
  * Fix building with TeX Live 2022, thanks to Hilmar Preuße.  (See: 
#998240)

  * Fix typos.
  * Let tex-common handle mktexlsr.
  * Add Homepage pointing to ctan.
  * Switch to debhelper-compat (= 13).
  * Switch to dh.
  * Set Rules-Requires-Root: no.
  * Set XS-Autobuild: yes.
  * Fix some issues found by Lintian.

 -- Andreas Beckmann   Sat, 13 Nov 2021 11:33:15 +0100


Andreas--- End Message ---

Processed: Re: aspell-cs: missing required debian/rules targets build-arch and/or build-indep

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch pending
Bug #998937 [src:aspell-cs] aspell-cs: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending and patch.

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

Bug#998937: aspell-cs: missing required debian/rules targets build-arch and/or build-indep

[Andreas Beckmann]

Followup-For: Bug #998937
Control: tag -1 patch pending

Hi,

I've just uploaded a NMU to DELAYED/10 to fix this issue.
Please let me know if I should delay it longer.


Andreas
diff -Nru aspell-cs-0.51.0/debian/changelog aspell-cs-0.51.0/debian/changelog
--- aspell-cs-0.51.0/debian/changelog   2021-02-22 15:45:32.0 +0100
+++ aspell-cs-0.51.0/debian/changelog   2022-01-12 15:25:42.0 +0100
@@ -1,3 +1,10 @@
+aspell-cs (0.51.0-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/rules: Add build-arch and build-indep targets.  (Closes: #998937)
+
+ -- Andreas Beckmann   Wed, 12 Jan 2022 15:25:42 +0100
+
 aspell-cs (0.51.0-1.2) unstable; urgency=medium
 
   [ Andreas Beckmann ]
diff -Nru aspell-cs-0.51.0/debian/rules aspell-cs-0.51.0/debian/rules
--- aspell-cs-0.51.0/debian/rules   2021-02-22 15:30:48.0 +0100
+++ aspell-cs-0.51.0/debian/rules   2022-01-12 15:23:33.0 +0100
@@ -12,6 +12,8 @@
dh_testdir
 
 build: build-stamp
+build-arch: build-stamp
+build-indep: build-stamp
 
 build-stamp:  config.status
dh_testdir

Processed: do not autoremove

[Debian Bug Tracking System]

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

> severity 984953 normal
Bug #984953 [gparted] libgtkmm-3.0-1v5: GParted crashes on 
Gdk::Pixbuf::get_width() const ()
Severity set to 'normal' from 'grave'
> severity 948739 normal
Bug #948739 [gparted] gparted should not mask .mount units
Severity set to 'normal' from 'serious'
> severity 984714 normal
Bug #984714 [gparted] gparted should suggest exfatprogs and backport the commit 
that rejects exfat-utils
Bug #990393 [gparted] gparted should suggest exfatprogs and backport the commit 
that rejects exfat-utils
Severity set to 'normal' from 'serious'
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#1003606: python3-flask-httpauth: missing Breaks+Replaces: python-flask-httpauth-doc (<< 4)

[Andreas Beckmann]

Package: python3-flask-httpauth
Version: 4.5.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../python3-flask-httpauth_4.5.0-1_all.deb ...
  Unpacking python3-flask-httpauth (4.5.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb (--unpack):
   trying to overwrite '/usr/share/man/man1/flask-httpauth.1.gz', which is also 
in package python-flask-httpauth-doc 3.2.4-3.1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-flask-httpauth_4.5.0-1_all.deb

Obviously the manpage was moved between the packages.


cheers,

Andreas


python-flask-httpauth-doc=3.2.4-3.1_python3-flask-httpauth=4.5.0-1.log.gz
Description: application/gzip

Processed: reassign 990183 to src:openscap, fixed 990183 in 1.3.5-0.1, reassign 1003256 to src:linux ...

[Debian Bug Tracking System]

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

> reassign 990183 src:openscap 1.3.4-1
Bug #990183 {Done: Hideki Yamane } [libopenscap8] 
libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by 
scap-workbench
Bug reassigned from package 'libopenscap8' to 'src:openscap'.
No longer marked as found in versions openscap/1.3.4-1.
No longer marked as fixed in versions openscap/1.3.5-0.1.
Bug #990183 {Done: Hideki Yamane } [src:openscap] 
libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by 
scap-workbench
Marked as found in versions openscap/1.3.4-1.
> fixed 990183 1.3.5-0.1
Bug #990183 {Done: Hideki Yamane } [src:openscap] 
libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by 
scap-workbench
Marked as fixed in versions openscap/1.3.5-0.1.
> reassign 1003256 src:linux
Bug #1003256 [unknown] .part file created when modifying file on NAS device
Warning: Unknown package 'unknown'
Bug reassigned from package 'unknown' to 'src:linux'.
No longer marked as found in versions unknown.
Ignoring request to alter fixed versions of bug #1003256 to the same values 
previously set
> notfixed 996261 ruby-fii/1.15.4+dfsg-1
Bug #996261 {Done: Cédric Boutillier } [ruby-ffi] ruby-ffi: 
FTBFS on riscv64 due missing types.conf
The source ruby-fii and version 1.15.4+dfsg-1 do not appear to match any binary 
packages
No longer marked as fixed in versions ruby-fii/1.15.4+dfsg-1.
> fixed 996261 1.15.4+dfsg-1
Bug #996261 {Done: Cédric Boutillier } [ruby-ffi] ruby-ffi: 
FTBFS on riscv64 due missing types.conf
Marked as fixed in versions ruby-ffi/1.15.4+dfsg-1.
> tags 819617 - buster
Bug #819617 {Done: Andreas Tille } [src:bcftools] FTBFS: 
any-i386 - floating point idiosyncracies
Bug #860682 {Done: Andreas Tille } [src:bcftools] bcftools: 
FTBFS on i386: Test failures
Bug #860704 {Done: Andreas Tille } [src:bcftools] 
python-pysam: FTBFS on i386: build-dependency not installable: bcftools (>= 
1.3.1)
Removed tag(s) buster.
Removed tag(s) buster.
Removed tag(s) buster.
> tags 638240 =
Bug #638240 {Done: Adrian Bunk } [src:alsamixergui] 
alsamixergui: set architecture to linux-any
Removed tag(s) stretch, bullseye, wheezy, bookworm, buster, patch, jessie, and 
sid.
> tags 955650 - bullseye
Bug #955650 {Done: Carsten Schoenert } 
[src:python-tablib] python-tablib: FTBFS: E   NotImplementedError: 
DataFrame Format requires `pandas` to be installed. Try `pip install 
tablib[pandas]`.
Removed tag(s) bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1003256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003256
638240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638240
819617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819617
860682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860682
860704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860704
955650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955650
990183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990183
996261: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1003561: mypy breaks python-sop autopkgtest: Missing type parameters for generic type "_SubParsersAction"

[Antonio Terceiro]

On Tue, Jan 11, 2022 at 10:22:44PM +0100, Paul Gevers wrote:
> Source: mypy, python-sop
> Control: found -1 mypy/0.931-1
> Control: found -1 python-sop/0.2.0-1.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 mypy the autopkgtest of python-sop fails in testing
> when that autopkgtest is run with the binary packages of mypy from unstable.
> It passes when run with only packages from testing. In tabular form:
> 
>passfail
> mypy   from testing0.931-1
> python-sop from testing0.2.0-1.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 mypy 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=mypy
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-sop/18224287/log.gz
> 
> sop/__init__.py:224: error: Missing type parameters for generic type
> "_SubParsersAction"
> sop/__init__.py:387: error: Missing type parameters for generic type
> "_SubParsersAction"
> Found 2 errors in 1 file (checked 3 source files)
> autopkgtest [21:22:47]: test command2

Running static analysis tools such as mypy as part of autopkgtest, or
even as build time tests, is an anti-pattern. New versions of the tools
tend to always find new issues but they usually have no impact on the
runtime behavior of the package.

I understand it's useful to have this type of checks against the source,
but I suggest you do that on salsa CI instead since there it won't
affect the tools themselves.


signature.asc
Description: PGP signature

Bug#1001545: pyopencl, build-depends on package that is no longer in testing

[Drew Parsons]

On 2022-01-12 00:04, Rebecca N. Palmer wrote:

That's probably a good idea for runtime Depends, but *not*
Build-Depends and test-Depends: those are likely to be run on GPU-less
servers, where only CPU ICDs (i.e. pocl-opencl-icd) will work.

(Roughly: pocl-opencl-icd = CPUs, mesa-opencl-icd = AMD/ATI GPUs,
intel-opencl-icd = Intel GPUs; the GPU ICDs work on integrated GPUs,
but server processors often don't even have those.  I think of
pocl-opencl-icd as slow enough to be mostly for testing, but don't
know how generally true that is.)



It might be that I'm not understanding how pyopencl interacts with 
opencl-icd, I'm no expert in opencl.  What made me suggest building via 
mesa-opencl-icd was that mesa-opencl-icd builds for all arches, even the 
niche minor arches.


mesa-opencl-icd is running and passing its own tests on these arches.  
What is pyopencl doing in build and tests that's different from what 
mesa-opencl-icd itself does?


Drew

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

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 11:33:35 +
with message-id 
and subject line Bug#999107: fixed in htag 0.0.24-2
has caused the Debian Bug report #999107,
regarding htag: 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.)


-- 
999107: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: htag
Version: 0.0.24-1.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: htag
Source-Version: 0.0.24-2
Done: Simon Huggins 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jan 2022 11:12:06 +
Source: htag
Architecture: source
Version: 0.0.24-2
Distribution: unstable
Urgency: low
Maintainer: Simon Huggins 
Changed-By: Simon Huggins 
Closes: 965581 999107
Changes:
 htag (0.0.24-2) unstable; urgency=low
 .
   * Update build system (closes: #999107)
   * Bump debhelper-compat (closes: #965581)
   * Lintian: Switch to dpkg-source 3.0 (quilt) format
- update copyright to explicitly state GPL-v2-only
- Remove article from start of package description
Checksums-Sha1:
 1ec9df889041687fb159420b8821087bc13d5cd2 1735 htag_0.0.24-2.dsc
 ddf816ed7af7cc8f942767c061afd3eb424ffabe 2756 htag_0.0.24-2.debian.tar.xz
 c7e780811b73c82ec4c9750e917444821c3ac984 5729 htag_0.0.24-2_amd64.buildinfo
Checksums-Sha256:
 b11bda50efc99f6de5cefab53f70fab97544418fecdee868a86773e2ebe6655b 1735 
htag_0.0.24-2.dsc
 51b438209448a81b36653b160dec52d472b8defd01c9f097710be47f78d5b26e 2756 
htag_0.0.24-2.debian.tar.xz
 cfda3fa5e797af00034090e5f30ed05f72c2b4de50a5d58e6043d2304b0d0cad 5729 
htag_0.0.24-2_amd64.buildinfo
Files:
 d375092c2a8f1b5f5b8cacc68b96f469 1735 mail optional htag_0.0.24-2.dsc
 68095e6de99c63a210dd0fb9dd7c46a9 2756 mail optional htag_0.0.24-2.debian.tar.xz
 f858c97e64c392ac1ac14a171c04b125 5729 mail optional 
htag_0.0.24-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE/S8txYRw4wP3eXWjSgDzSK903QIFAmHeurERHG5vb2RsZXNA
ZWFydGgubGkACgkQSgDzSK903QJ6lg/6Ajfca14vwESJygW+stfi+WeSSYCtnhTX
NMl23nxk58q6u9xF5Rw8diBEAr29fh9XJrD4njEk70U/TJbIt8DjNA8xlPAf9T2Q
AX1GXBh2kNAxztIHBWCqTpF9e11kw3gxADuzKj6LXG3zQ90YcN/dAFimU8zeB7iy
e5HyjnWHP5A35JbkVK+d+w6npwyTIB5XbbC+9CPKXZg8xmTy1ZYDup2decKpHs5q
AUmugeWMEfD3dOvsGgcUQPiDG75BfYpEPZqTbE4qlvHAK3rZMr3TIwWy5fgHfoUA
Sva9zpcOURM792MqT851PBOU0KpsTNO3u0XNZO0IOcR0z2zZiPgU1Uo6BCwhOGAy
jVDCXhajkbVShZ6FWPAJynw9tytoRidKq+lpYmQFFc+lENfCB7AB3nw4b8qB5Ybb
egTu+FBUOHY1kTGyyG/QHRFj0n2daYM+7gCH67Vm98ui3KjMaPV+YGGdjpyVOFF0
EoeyGMtiK7YVMF5VavtJMYQ/92eb0o7HF2zAFqDvVCjBH/dpsQFAGWAly6wvJCX3
KYBC3TxFDb+ZKMs2RZeefE+tKW87It2hL90VGBfiMMsUA3eM/NFPZVGvYiqslEi5
1u5tT4vBe7wTj4Bh+cLt7BWMa4TUnxERG8J5Tt7sU5Zvfg3DZSL0oL0Knotcr02L
oOOdHHchfQc=
=16pe
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 11:33:35 +
with message-id 
and subject line Bug#965581: fixed in htag 0.0.24-2
has caused the Debian Bug report #965581,
regarding htag: 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.)


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

Hi,

The package htag 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: htag
Source-Version: 0.0.24-2
Done: Simon Huggins 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 12 Jan 2022 11:12:06 +
Source: htag
Architecture: source
Version: 0.0.24-2
Distribution: unstable
Urgency: low
Maintainer: Simon Huggins 
Changed-By: Simon Huggins 
Closes: 965581 999107
Changes:
 htag (0.0.24-2) unstable; urgency=low
 .
   * Update build system (closes: #999107)
   * Bump debhelper-compat (closes: #965581)
   * Lintian: Switch to dpkg-source 3.0 (quilt) format
- update copyright to explicitly state GPL-v2-only
- Remove article from start of package description
Checksums-Sha1:
 1ec9df889041687fb159420b8821087bc13d5cd2 1735 htag_0.0.24-2.dsc
 ddf816ed7af7cc8f942767c061afd3eb424ffabe 2756 htag_0.0.24-2.debian.tar.xz
 c7e780811b73c82ec4c9750e917444821c3ac984 5729 htag_0.0.24-2_amd64.buildinfo
Checksums-Sha256:
 b11bda50efc99f6de5cefab53f70fab97544418fecdee868a86773e2ebe6655b 1735 
htag_0.0.24-2.dsc
 51b438209448a81b36653b160dec52d472b8defd01c9f097710be47f78d5b26e 2756 
htag_0.0.24-2.debian.tar.xz
 cfda3fa5e797af00034090e5f30ed05f72c2b4de50a5d58e6043d2304b0d0cad 5729 
htag_0.0.24-2_amd64.buildinfo
Files:
 d375092c2a8f1b5f5b8cacc68b96f469 1735 mail optional htag_0.0.24-2.dsc
 68095e6de99c63a210dd0fb9dd7c46a9 2756 mail optional htag_0.0.24-2.debian.tar.xz
 f858c97e64c392ac1ac14a171c04b125 5729 mail optional 
htag_0.0.24-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE/S8txYRw4wP3eXWjSgDzSK903QIFAmHeurERHG5vb2RsZXNA
ZWFydGgubGkACgkQSgDzSK903QJ6lg/6Ajfca14vwESJygW+stfi+WeSSYCtnhTX
NMl23nxk58q6u9xF5Rw8diBEAr29fh9XJrD4njEk70U/TJbIt8DjNA8xlPAf9T2Q
AX1GXBh2kNAxztIHBWCqTpF9e11kw3gxADuzKj6LXG3zQ90YcN/dAFimU8zeB7iy
e5HyjnWHP5A35JbkVK+d+w6npwyTIB5XbbC+9CPKXZg8xmTy1ZYDup2decKpHs5q
AUmugeWMEfD3dOvsGgcUQPiDG75BfYpEPZqTbE4qlvHAK3rZMr3TIwWy5fgHfoUA
Sva9zpcOURM792MqT851PBOU0KpsTNO3u0XNZO0IOcR0z2zZiPgU1Uo6BCwhOGAy
jVDCXhajkbVShZ6FWPAJynw9tytoRidKq+lpYmQFFc+lENfCB7AB3nw4b8qB5Ybb
egTu+FBUOHY1kTGyyG/QHRFj0n2daYM+7gCH67Vm98ui3KjMaPV+YGGdjpyVOFF0
EoeyGMtiK7YVMF5VavtJMYQ/92eb0o7HF2zAFqDvVCjBH/dpsQFAGWAly6wvJCX3
KYBC3TxFDb+ZKMs2RZeefE+tKW87It2hL90VGBfiMMsUA3eM/NFPZVGvYiqslEi5
1u5tT4vBe7wTj4Bh+cLt7BWMa4TUnxERG8J5Tt7sU5Zvfg3DZSL0oL0Knotcr02L
oOOdHHchfQc=
=16pe
-END PGP 

Bug#1000892: marked as done (cvise: Please upgrade to llvm-toolchain-12 or 13)

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 11:33:29 +
with message-id 
and subject line Bug#1000892: fixed in cvise 2.4.0-2.1
has caused the Debian Bug report #1000892,
regarding cvise: Please upgrade to llvm-toolchain-12 or 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.)


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

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the
archive, please upgrade to -13 (or -12).

It has:
  llvm-9-dev [armel armhf], libclang-9-dev [armel armhf], clang-9 [armel 
armhf], clang-format-9 [armel armhf],


Thanks,
Sylvestre


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (500, 'oldstable-updates'), (500, 
'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (300, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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
--- End Message ---
--- Begin Message ---
Source: cvise
Source-Version: 2.4.0-2.1
Done: Adrian Bunk 

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 29 Dec 2021 22:41:49 +0200
Source: cvise
Architecture: source
Version: 2.4.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Adrian Bunk 
Closes: 1000892 1001375
Changes:
 cvise (2.4.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove stale LLVM 9 build dependencies on armel/armhf.
 (Closes: #1000892)
   * Recommend colordiff. (Closes: #1001375)
Checksums-Sha1:
 541623660e12a72c9177e91ab7e2281724df3a22 1972 cvise_2.4.0-2.1.dsc
 e0fef2e1597f0f0226b11dd52ce03b5b8ab2fa29 5680 cvise_2.4.0-2.1.debian.tar.xz
Checksums-Sha256:
 38fff65c4100ab31cb6832029d348850004bc6820cceed85ce1c8f30ff9ed23b 1972 
cvise_2.4.0-2.1.dsc
 1b614beb0d83d0b320cdd027ec3877608719596911d765a835774729aaf37d80 5680 
cvise_2.4.0-2.1.debian.tar.xz
Files:
 d0cea68c2ac2f2dedd89782ebfc149fd 1972 misc optional cvise_2.4.0-2.1.dsc
 91ce34117e2fee85e465efb74b1c4464 5680 misc optional 
cvise_2.4.0-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHM0KQACgkQiNJCh6LY
mLG43A//XU53P4KmSpKq13ybcMLgdK5wnTZeR0imGvBzQgKqGdAwpNxoNvTl/B2e
Dpp54sntVB1gj0bfH9wP+E0LtZcreV8J+wJ5GXnu8yb4V8OClb9neETQ93kN2ey1
BATKGv0E231QVyaDlCjyJbSbH7DBuLkQQA9xl1Ps0cOp1Yxr8CpfRc9X9C6xe41Z
TxgNFdvh/TQ/apFfOsBTkuGxtEyIrw0S4lBxsXWAsnx2N4lw3UbHSa3nGF/WkUHF
tf6ZvrMA/oirSDTK4lwSI9kzsHSUaiVNAuu6PgW++orux21/7lHS0t1QSQ+aH0Au
uT8by65MGGAg+T0hRDUhVbLsUKyAMzolGBBc/xkekm1RlbMSiRizZgGgOrO2cumg
G7VE2LPWuzVeatQzcNcLPb4DenlBzGfTgKzipGcNj9h7LEO1y3RGXs2UrK1tN8v2
l2erLC9jzGuCWzv/q4eEraH2Go4cDMYXysXfje5GbnEWhyHSJ11yBKvhQkFpDmC/
6tdx9/JTq4/A88YJeBf6vGeYc4aS86TFKYNZ3EAaJAAqWvw4ZpbmM9xvbSkEMxDT
8Z04lHq7QmEmlOKek9xkedHIKk0ZeiBzrAJANRpoNkhnMBwvKwNGsPMhyQEm7LcN
W1GW38Ifmcx7vXBaZ27dE1hcJyrRjkiuTvLWuL1T42gtztUk27g=
=SyIS
-END PGP SIGNATURE End Message ---

Bug#1003113: python-django: CVE-2021-45115, CVE-2021-45116 & CVE-2021-45452

[Chris Lamb]

Hi Moritz,

>> I was just looking at these CVEs for ELTS and LTS, but before I make
>> a move there, I was just wondering if you were planning on (or would
>> like) a DSA.
>
> Hi Chris,
> these both seem rather harmless to me, I'd say we postpone them until
> the next round of more serious Django issues?

That works for me. I think I've reflected that in data/CVE/list in
this commit:


https://salsa.debian.org/security-tracker-team/security-tracker/commit/09807490bc5924c02b11adb4f85ed9467f50efcf


Regards,

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

Processed: Forwarded to PR addressing the issue

[Debian Bug Tracking System]

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

> forwarded 1002360 https://github.com/zopefoundation/zope.exceptions/pull/23
Bug #1002360 [src:zope.exceptions] zope.exceptions: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Set Bug forwarded-to-address to 
'https://github.com/zopefoundation/zope.exceptions/pull/23'.
> --
Stopping processing here.

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

Processed: libjavascript-rpc-perl: diff for salvaging upload version 0.10-2

[Debian Bug Tracking System]

Processing control commands:

> tags 999265 + patch pending
Bug #999265 [src:libjavascript-rpc-perl] libjavascript-rpc-perl: missing 
required debian/rules targets build-arch and/or build-indep
Ignoring request to alter tags of bug #999265 to the same tags previously set
> tags 1001975 + patch pending
Bug #1001975 [src:libjavascript-rpc-perl] ITS: libjavascript-rpc-perl
Ignoring request to alter tags of bug #1001975 to the same tags previously set

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

Bug#999265: libjavascript-rpc-perl: diff for salvaging upload version 0.10-2

[Christoph Biedl]

Control: tags 999265 + patch pending
Control: tags 1001975 + patch pending

Dear maintainer,

to fix the issues with this package, I've prepared a salvaging upload
for libjavascript-rpc-perl (versioned as 0.10-2), debdiff below. An
upload to DELAYED/14 will follow shortly. Please feel free to tell me
if I should delay it longer.

Regards.

Christoph

diff -Nru libjavascript-rpc-perl-0.10/debian/changelog 
libjavascript-rpc-perl-0.10/debian/changelog
--- libjavascript-rpc-perl-0.10/debian/changelog2022-01-12 
09:19:25.0 +0100
+++ libjavascript-rpc-perl-0.10/debian/changelog2022-01-10 
18:51:57.0 +0100
@@ -1,3 +1,11 @@
+libjavascript-rpc-perl (0.10-2) unstable; urgency=medium
+
+  * Salvaging upload
+  * Take maintainership. Closes: #1001975
+  * Packaging cleanup. Closes: #999265
+
+ -- Christoph Biedl   Mon, 10 Jan 2022 
18:51:57 +0100
+
 libjavascript-rpc-perl (0.10-1.3) unstable; urgency=medium
 
   * Non-maintainer upload
@@ -37,4 +45,3 @@
   * Initial Release (closes: Bug#292272).
 
  -- Ivan Kohler   Tue, 25 Jan 2005 17:51:57 -0800
-
diff -Nru libjavascript-rpc-perl-0.10/debian/compat 
libjavascript-rpc-perl-0.10/debian/compat
--- libjavascript-rpc-perl-0.10/debian/compat   2022-01-12 09:19:25.0 
+0100
+++ libjavascript-rpc-perl-0.10/debian/compat   1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-10
diff -Nru libjavascript-rpc-perl-0.10/debian/control 
libjavascript-rpc-perl-0.10/debian/control
--- libjavascript-rpc-perl-0.10/debian/control  2022-01-12 09:19:25.0 
+0100
+++ libjavascript-rpc-perl-0.10/debian/control  2022-01-10 18:47:00.0 
+0100
@@ -1,19 +1,25 @@
 Source: libjavascript-rpc-perl
-Section: perl
+Maintainer: Christoph Biedl 
+Standards-Version: 4.6.0
+Testsuite: autopkgtest-pkg-perl
+Build-Depends: debhelper-compat (= 13),
+libcgi-pm-perl,
+libcgi-simple-perl,
+libmodule-build-perl,
+libtest-pod-coverage-perl,
+libtest-pod-perl,
 Priority: optional
-Build-Depends: debhelper (>= 10~)
-Build-Depends-Indep: perl (>= 5.6), libcgi-pm-perl | perl (<< 5.19), 
libcgi-simple-perl, libtest-pod-coverage-perl, libtest-pod-perl
-Maintainer: Jonas Genannt 
-Standards-Version: 3.6.2
+Rules-Requires-Root: no
+Section: perl
 
 Package: libjavascript-rpc-perl
 Architecture: all
-Depends: ${perl:Depends} 
+Depends: ${misc:Depends}, ${perl:Depends},
 Description: Perl module to process Remote procedure calls from JavaScript
- JavaScript::RPC::Server::CGI is a CGI-based server library for use with Brent
- Ashley's JavaScript Remote Scripting (JSRS) client library. It works
- asynchronously and uses DHTML to deal with the payload.
+ JavaScript::RPC::Server::CGI is a CGI-based server library for use
+ with Brent Ashley's JavaScript Remote Scripting (JSRS) client library.
+ It works asynchronously and uses DHTML to deal with the payload.
  .
- The most current version (as of the release of this module) of the client
- library as well as a demo application have been included in this
- distribution.
+ The most current version (as of the release of this module) of the
+ client library as well as a demo application have been included in
+ this distribution.
diff -Nru libjavascript-rpc-perl-0.10/debian/copyright 
libjavascript-rpc-perl-0.10/debian/copyright
--- libjavascript-rpc-perl-0.10/debian/copyright2022-01-12 
09:19:25.0 +0100
+++ libjavascript-rpc-perl-0.10/debian/copyright2022-01-10 
18:47:00.0 +0100
@@ -1,46 +1,52 @@
-This is the debian package for the JavaScript-RPC module.
-It was created by Ivan Kohler  using dh-make-perl.
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 
-It was downloaded from http://search.cpan.org/~bricas/
-
-The Javascript::RPC perl module is covered by the following copyright:
-
-  Copyright 2005 by Brian Cassidy 
-
-  This library is free software; you can redistribute it and/or modify
-  it under the same terms as Perl itself. 
-
-  Perl is distributed under your choice of the GNU General Public License or
-  the Artistic License.  On Debian GNU/Linux systems, the complete text of the
-  GNU General Public License can be found in `/usr/share/common-licenses/GPL'
-  and the Artistic Licence in `/usr/share/common-licenses/Artistic'.
-
-
-The JSRS client library (jsrsClient.js) is covered by the follwing copyright:
-
-  No Nonsense Copyright and License for JSRS JavaScript Remote Scripting
-  ==
-
-  Copyright:
-
-  This JSRS stuff was written by me.  I find it useful.  Others find it 
useful. 
-  You are welcome to use it, modify it to suit your needs, distribute it as 
you 
-  see fit.  I'm happy if you use it for personal stuff or for commercial gain.
-
-  The only thing you can't do is to restrict anyone else from using it however 
-  they see fit.  You may not copyright it yourself or change the rules I have 
-  set on how it can be used.
-
-  JSRS Javascript Remote 

Processed: libcgi-ssi-parser-perl: diff for salvaging upload version 0.01-2

[Debian Bug Tracking System]

Processing control commands:

> tags 466397 + patch pending
Bug #466397 [libcgi-ssi-parser-perl] Odd description
Ignoring request to alter tags of bug #466397 to the same tags previously set
> tags 999223 + patch pending
Bug #999223 [src:libcgi-ssi-parser-perl] libcgi-ssi-parser-perl: missing 
required debian/rules targets build-arch and/or build-indep
Ignoring request to alter tags of bug #999223 to the same tags previously set
> tags 1001973 + patch pending
Bug #1001973 [src:libcgi-ssi-parser-perl] ITS: libcgi-ssi-parser-perl
Ignoring request to alter tags of bug #1001973 to the same tags previously set

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

Bug#998954: libppd: diff for salvaging upload version 2:0.10-8

[Christoph Biedl]

Control: tags 912689 + patch pending
Control: tags 998954 + patch pending
Control: tags 1001976 + patch pending

Dear maintainer,

to fix the issues with this package, I've prepared a salvaging upload
for libppd (versioned as 2:0.10-8), debdiff below. An upload to
DELAYED/14 will follow shortly. Please feel free to tell me if I should
delay it longer.

Note: To keep the debdiff short, it only contains the changes to
the debian/ directory. About any other file, they now have the content
as in libppd_0.10.orig.tar.gz, as a consequence of the migration to the
3.0 (quilt source) format. Incuding these changes adds no information
but increases the diff size by factor 58.

Regards,

Christoph

diff -Nru libppd-0.10/debian/changelog libppd-0.10/debian/changelog
--- libppd-0.10/debian/changelog2022-01-12 09:19:27.0 +0100
+++ libppd-0.10/debian/changelog2022-01-10 20:37:21.0 +0100
@@ -1,3 +1,10 @@
+libppd (2:0.10-8) unstable; urgency=medium
+
+  * Take maintainership. Closes: #1001976
+  * Packaging cleanup. Closes: #998954, #912689
+
+ -- Christoph Biedl   Mon, 10 Jan 2022 
20:37:21 +0100
+
 libppd (2:0.10-7.3) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru libppd-0.10/debian/compat libppd-0.10/debian/compat
--- libppd-0.10/debian/compat   2022-01-12 09:19:27.0 +0100
+++ libppd-0.10/debian/compat   1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-10
diff -Nru libppd-0.10/debian/control libppd-0.10/debian/control
--- libppd-0.10/debian/control  2022-01-12 09:19:27.0 +0100
+++ libppd-0.10/debian/control  2022-01-10 20:18:49.0 +0100
@@ -1,22 +1,27 @@
 Source: libppd
-Section: libs
+Maintainer: Christoph Biedl 
+Homepage: 
http://sourceforge.net/project/showfiles.php?group_id=3800_id=11729
+Standards-Version: 4.6.0
+Build-Depends: debhelper-compat (= 13),
+libglib2.0-dev,
 Priority: optional
-Maintainer: A Mennucc1 
-Build-Depends: debhelper (>= 10~), dh-autoreconf, libglib2.0-dev
-Standards-Version: 3.8.0.0
+Section: libs
+Rules-Requires-Root: no
 
 Package: libppd-dev
-Section: libdevel
 Architecture: any
-Depends: libppd0 (= ${binary:Version}), libc6-dev
+Depends: ${misc:Depends},
+libc6-dev,
+libppd0 (= ${binary:Version}),
+Section: libdevel
 Description: postscript PPD file library, development kit
  This package contains the static library and header files used in
  development of programs that use libppd.
 
 Package: ppdfilt
-Section: utils
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends},
+Section: utils
 Description: filter that inserts printer specific commands into print jobs
  ppdfilt is a filter program designed to be used within a filter
  script or from the command line tool to insert printer specific
@@ -27,12 +32,11 @@
 
 Package: libppd0
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends},
 Description: postscript PPD file library
  PostScript was designed as a device independent language. To be able
  to access device specific features like selecting different paper
  trays and turning on different imaging models, each printer vendor
  supplies a PostScript Printer Definition or PPD file. This library
  reads those PPD files and provides functions that allow a program to
- modify PostScript print jobs to acces these special features.
-
+ modify PostScript print jobs to access these special features.
diff -Nru libppd-0.10/debian/copyright libppd-0.10/debian/copyright
--- libppd-0.10/debian/copyright2022-01-12 09:19:27.0 +0100
+++ libppd-0.10/debian/copyright2022-01-10 20:18:49.0 +0100
@@ -1,29 +1,22 @@
-This is a Debian prepackaged version of libppd.
-
-This package was put together by Joey Hess , using
-sources from:
-   http://download.sourceforge.net/libppd/
-or  http://sourceforge.net/project/showfiles.php?group_id=3800_id=11729
-
-Copyright 1993-1999 by Easy Software Products.
-
-Authors:
- Ben Woodard 
- Mark Fasheh 
-
-
-License :  GNU GENERAL PUBLIC LICENSE ,  Version 2, June 1991
-
-This program is free software; you can redistribute it and/or modify
-it under the terms of the GNU General Public License as published by
-the Free Software Foundation; either version 2 of the License, or
-(at your option) any later version.
-
-This program is distributed in the hope that it will be useful,
-but WITHOUT ANY WARRANTY; without even the implied warranty of
-MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
-GNU General Public License for more details.
-
-On Debian systems, the complete text of the GNU Library
-General Public License can be found in /usr/share/common-licenses/GPL
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 
+Files: *
+Copyright: Copyright 1993-1999 by Easy Software Products
+License: GPL-2.0+
+
+License: GPL-2.0+
+ This package is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public 

Bug#999223: libcgi-ssi-parser-perl: diff for salvaging upload version 0.01-2

[Christoph Biedl]

Control: tags 466397 + patch pending
Control: tags 999223 + patch pending
Control: tags 1001973 + patch pending

Dear maintainer,

to fix the issues with this package, I've prepared a salvaging upload
for libcgi-ssi-parser-perl (versioned as 0.01-2), debdiff below. An
upload to DELAYED/14 will follow shortly. Please feel free to tell me
if I should delay it longer.

Regards.

Christoph

diff -Nru libcgi-ssi-parser-perl-0.01/debian/changelog 
libcgi-ssi-parser-perl-0.01/debian/changelog
--- libcgi-ssi-parser-perl-0.01/debian/changelog2022-01-12 
09:19:13.0 +0100
+++ libcgi-ssi-parser-perl-0.01/debian/changelog2022-01-08 
12:48:43.0 +0100
@@ -1,3 +1,11 @@
+libcgi-ssi-parser-perl (0.01-2) unstable; urgency=medium
+
+  * Salvaging upload
+  * Take maintainership. Closes: #1001973
+  * Packaging cleanup. Closes: #466397, #999223
+
+ -- Christoph Biedl   Sat, 08 Jan 2022 
12:48:43 +0100
+
 libcgi-ssi-parser-perl (0.01-1.2) unstable; urgency=medium
 
   * Non-maintainer upload
@@ -19,4 +27,3 @@
   * Initial Release.
 
  -- Jason Thomas   Fri, 28 Mar 2003 11:01:28 +1100
-
diff -Nru libcgi-ssi-parser-perl-0.01/debian/compat 
libcgi-ssi-parser-perl-0.01/debian/compat
--- libcgi-ssi-parser-perl-0.01/debian/compat   2022-01-12 09:19:13.0 
+0100
+++ libcgi-ssi-parser-perl-0.01/debian/compat   1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-10
diff -Nru libcgi-ssi-parser-perl-0.01/debian/control 
libcgi-ssi-parser-perl-0.01/debian/control
--- libcgi-ssi-parser-perl-0.01/debian/control  2022-01-12 09:19:13.0 
+0100
+++ libcgi-ssi-parser-perl-0.01/debian/control  2022-01-08 12:48:43.0 
+0100
@@ -1,22 +1,25 @@
 Source: libcgi-ssi-parser-perl
+Maintainer: Christoph Biedl 
+Homepage: https://metacpan.org/pod/CGI::SSI_Parser
+Standards-Version: 4.6.0
+Testsuite: autopkgtest-pkg-perl
+Build-Depends: debhelper-compat (= 13),
+Priority: optional
+Rules-Requires-Root: no
 Section: web
-Priority: extra
-Maintainer: Jason Thomas 
-Build-Depends-Indep: debhelper (>= 10~), perl (>= 5.6.0-16)
-Standards-Version: 3.5.8
 
 Package: libcgi-ssi-parser-perl
 Architecture: all
-Depends: ${perl:Depends}
-Description: used in CGI scripts for parsing SSI directives
- in files or string variables, and fully implements
- the functionality of apache's mod_include module.
+Depends: ${misc:Depends}, ${perl:Depends},
+Description: parse Apache server-side includes directives
+ This module is used in CGI scripts for parsing SSI directives in files
+ or string variables, and fully implements the functionality of
+ apache's mod_include module.
  .
- It is an alternative to famous Apache::SSI modules, but it
- doesn't require mod_perl. This is an advantage to those who are
- using public hosting services. There is a disadvantage, however
- - the module consumes much memory, and I don't recommend using
- it on heavy-loaded sites (currently it's being used on a site
- with 1 hits, and I consider this as a limit). I hope to get
- rid of this disadvantage by the time the release comes out
- (currently it's beta).
+ It is an alternative to famous Apache::SSI modules, but it doesn't
+ require mod_perl. This is an advantage to those who are using public
+ hosting services. There is a disadvantage, however - the module
+ consumes much memory, and the upstream author don't recommend using it
+ on heavy-loaded sites (currently it's being used on a site with 1
+ hits, and this is considered a limit). There's hope to get rid of this
+ disadvantage by the time the release comes out (currently it's beta).
diff -Nru libcgi-ssi-parser-perl-0.01/debian/copyright 
libcgi-ssi-parser-perl-0.01/debian/copyright
--- libcgi-ssi-parser-perl-0.01/debian/copyright2022-01-12 
09:19:13.0 +0100
+++ libcgi-ssi-parser-perl-0.01/debian/copyright2022-01-08 
12:38:04.0 +0100
@@ -1,29 +1,27 @@
-This package was debianized by Jason Thomas  on
-Fri, 28 Mar 2003 11:01:28 +1100.
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 
-It was downloaded from http://www.cpan.org/authors/id/V/VA/VADIM/
-
-Upstream Author: Vadim Y. Ponomarenko 
-
-Copyright:
-
-Date: Tue, 1 Apr 2003 16:25:59 +0300 (EEST)
-From: Vadim Ponomarenko 
-To: Jason Thomas 
-Subject: Re: CGI-SSI_Parser
-
-Hi.
-
-This module is not copyrighted, you can use him as you wish.
-
-
-On Fri, 28 Mar 2003, Jason Thomas wrote:
-
-> Hi, I'd like to package your program for debian linux. The only thing
-> missing is the license.
->
-> Can you tell me what license it is under. Maybe you could make a new
-> release with the license infomation.
-
-
-Vadim Ponomarenko
+Files: *
+Copyright: Vadim Y. Ponomarenko 
+License: not-copyrighted
+
+License: not-copyrighted
+ Date: Tue, 1 Apr 2003 16:25:59 +0300 (EEST)
+ From: Vadim Ponomarenko 
+ To: Jason Thomas 
+ Subject: Re: CGI-SSI_Parser
+ .
+ Hi.
+ .
+ This module is not copyrighted, you can use him as you wish.
+ .
+ .
+ On Fri, 28 Mar 2003, Jason Thomas 

Processed: libppd: diff for salvaging upload version 2:0.10-8

[Debian Bug Tracking System]

Processing control commands:

> tags 912689 + patch pending
Bug #912689 [src:libppd] libppd FTCBFS: multiple reasons
Ignoring request to alter tags of bug #912689 to the same tags previously set
> tags 998954 + patch pending
Bug #998954 [src:libppd] libppd: missing required debian/rules targets 
build-arch and/or build-indep
Ignoring request to alter tags of bug #998954 to the same tags previously set
> tags 1001976 + patch pending
Bug #1001976 [src:libppd] ITS: libppd
Ignoring request to alter tags of bug #1001976 to the same tags previously set

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

Bug#998918: libdebian-package-html-perl: diff for salvaging upload version 0.1-3

[Christoph Biedl]

Control: tags 610178 + patch pending
Control: tags 998918 + patch pending
Control: tags 1001974 + patch pending

Dear maintainer,

to fix the issues with this package, I've prepared a salvaging upload
for libdebian-package-html-perl (versioned as 0.1-3), debdiff below. An
upload to DELAYED/14 will follow shortly. Please feel free to tell me
if I should delay it longer.

Regards.

Christoph

diff -Nru libdebian-package-html-perl-0.1/debian/changelog 
libdebian-package-html-perl-0.1/debian/changelog
--- libdebian-package-html-perl-0.1/debian/changelog2022-01-12 
09:19:10.0 +0100
+++ libdebian-package-html-perl-0.1/debian/changelog2022-01-06 
23:20:53.0 +0100
@@ -1,3 +1,13 @@
+libdebian-package-html-perl (0.1-3) unstable; urgency=medium
+
+  * Salvaging upload
+  * Take maintainership. Closes: #1001974
+  * Packaging cleanup. Closes: #998918
+  * Remove external example reference from documentation.
+Closes: #610178
+
+ -- Christoph Biedl   Thu, 06 Jan 2022 
23:20:53 +0100
+
 libdebian-package-html-perl (0.1-2.1) unstable; urgency=medium
 
   * Non-maintainer upload
@@ -16,4 +26,3 @@
   * Initial Release (Closes: #379284)
 
  -- Jose Parrella   Thu, 20 Jul 2006 14:01:22 -0400
-
diff -Nru libdebian-package-html-perl-0.1/debian/compat 
libdebian-package-html-perl-0.1/debian/compat
--- libdebian-package-html-perl-0.1/debian/compat   2022-01-12 
09:19:10.0 +0100
+++ libdebian-package-html-perl-0.1/debian/compat   1970-01-01 
01:00:00.0 +0100
@@ -1 +0,0 @@
-10
diff -Nru libdebian-package-html-perl-0.1/debian/control 
libdebian-package-html-perl-0.1/debian/control
--- libdebian-package-html-perl-0.1/debian/control  2022-01-12 
09:19:10.0 +0100
+++ libdebian-package-html-perl-0.1/debian/control  2022-01-06 
23:20:53.0 +0100
@@ -1,17 +1,22 @@
 Source: libdebian-package-html-perl
-Section: perl
+Maintainer: Christoph Biedl 
+Homepage: https://metacpan.org/dist/Debian-Package-HTML
+Standards-Version: 4.6.0
+Testsuite: autopkgtest-pkg-perl
+Build-Depends: debhelper-compat (= 13),
+libhtml-template-perl,
 Priority: optional
-Build-Depends: debhelper (>= 10~), libhtml-template-perl (>= 2.6-2)
-Build-Depends-Indep: perl (>= 5.8.0-7)
-Maintainer: Jose Parrella 
-Standards-Version: 3.7.3
+Rules-Requires-Root: no
+Section: perl
 
 Package: libdebian-package-html-perl
 Architecture: all
-Depends: ${perl:Depends}, libhtml-template-perl (>= 2.6-2)
+Depends: ${misc:Depends}, ${perl:Depends},
+libhtml-template-perl,
 Description: generates HTML from a Debian source/binary package
  This module outputs a webpage using HTML::Template templates which
- resumes the information of a normal build environment for a package
- in Debian (source files, binary packages and changelogs) using 
- Linda/Lintian for sanity checks. It is useful for making unified presentation
- webpages for those packages which are being sponsorized by someone in Debian.
+ resumes the information of a normal build environment for a package in
+ Debian (source files, binary packages and changelogs) using
+ Linda/Lintian for sanity checks. It is useful for making unified
+ presentation webpages for those packages which are being sponsorized
+ by someone in Debian.
diff -Nru libdebian-package-html-perl-0.1/debian/copyright 
libdebian-package-html-perl-0.1/debian/copyright
--- libdebian-package-html-perl-0.1/debian/copyright2022-01-12 
09:19:10.0 +0100
+++ libdebian-package-html-perl-0.1/debian/copyright2022-01-06 
23:20:53.0 +0100
@@ -1,16 +1,29 @@
-This is the debian package for the Debian-Package-HTML module.
-It was created by Jose Parrella  using dh-make-perl.
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: Debian-Package-HTML
 
-The upstream author is: 
+Files: *
+Copyright: 2006 Jose Parrella 
+License: Artistic or GPL-1+
 
-Jose Parrella (joseparre...@cantv.net)
+Files:
+ debian/*
+Copyright:
+ 2006 Jose Parrella 
+ 2022 Christoph Biedl 
+License: Artistic or GPL-1+
 
-Copyright 2006 Jose Parrella. All rights reserved.
+License: Artistic
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the Artistic License, which comes with Perl.
+ .
+ On Debian systems, the complete text of the Artistic License can be
+ found in `/usr/share/common-licenses/Artistic'.
 
-This library is free software; you can redistribute it and/or
-modify it under the same terms as Perl itself.
-
-Perl is distributed under your choice of the GNU General Public License or
-the Artistic License.  On Debian GNU/Linux systems, the complete text of the
-GNU General Public License can be found in `/usr/share/common-licenses/GPL'
-and the Artistic Licence in `/usr/share/common-licenses/Artistic'.
+License: GPL-1+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 

Processed: libdebian-package-html-perl: diff for salvaging upload version 0.1-3

[Debian Bug Tracking System]

Processing control commands:

> tags 610178 + patch pending
Bug #610178 [libdebian-package-html-perl] libdebian-package-html-perl: Examples 
URLs are no longer valid
Ignoring request to alter tags of bug #610178 to the same tags previously set
> tags 998918 + patch pending
Bug #998918 [src:libdebian-package-html-perl] libdebian-package-html-perl: 
missing required debian/rules targets build-arch and/or build-indep
Ignoring request to alter tags of bug #998918 to the same tags previously set
> tags 1001974 + patch pending
Bug #1001974 [src:libdebian-package-html-perl] ITS: libdebian-package-html-perl
Ignoring request to alter tags of bug #1001974 to the same tags previously set

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

Processed: libppd: diff for salvaging upload version 2:0.10-8

[Debian Bug Tracking System]

Processing control commands:

> tags 912689 + patch pending
Bug #912689 [src:libppd] libppd FTCBFS: multiple reasons
Ignoring request to alter tags of bug #912689 to the same tags previously set
> tags 998954 + patch pending
Bug #998954 [src:libppd] libppd: missing required debian/rules targets 
build-arch and/or build-indep
Ignoring request to alter tags of bug #998954 to the same tags previously set
> tags 1001976 + patch pending
Bug #1001976 [src:libppd] ITS: libppd
Ignoring request to alter tags of bug #1001976 to the same tags previously set

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

Processed: libdebian-package-html-perl: diff for salvaging upload version 0.1-3

[Debian Bug Tracking System]

Processing control commands:

> tags 610178 + patch pending
Bug #610178 [libdebian-package-html-perl] libdebian-package-html-perl: Examples 
URLs are no longer valid
Ignoring request to alter tags of bug #610178 to the same tags previously set
> tags 998918 + patch pending
Bug #998918 [src:libdebian-package-html-perl] libdebian-package-html-perl: 
missing required debian/rules targets build-arch and/or build-indep
Ignoring request to alter tags of bug #998918 to the same tags previously set
> tags 1001974 + patch pending
Bug #1001974 [src:libdebian-package-html-perl] ITS: libdebian-package-html-perl
Ignoring request to alter tags of bug #1001974 to the same tags previously set

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

Processed: libcgi-ssi-parser-perl: diff for salvaging upload version 0.01-2

[Debian Bug Tracking System]

Processing control commands:

> tags 466397 + patch pending
Bug #466397 [libcgi-ssi-parser-perl] Odd description
Ignoring request to alter tags of bug #466397 to the same tags previously set
> tags 999223 + patch pending
Bug #999223 [src:libcgi-ssi-parser-perl] libcgi-ssi-parser-perl: missing 
required debian/rules targets build-arch and/or build-indep
Ignoring request to alter tags of bug #999223 to the same tags previously set
> tags 1001973 + patch pending
Bug #1001973 [src:libcgi-ssi-parser-perl] ITS: libcgi-ssi-parser-perl
Ignoring request to alter tags of bug #1001973 to the same tags previously set

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

Processed: libppd: diff for salvaging upload version 2:0.10-8

[Debian Bug Tracking System]

Processing control commands:

> tags 912689 + patch pending
Bug #912689 [src:libppd] libppd FTCBFS: multiple reasons
Added tag(s) pending.
> tags 998954 + patch pending
Bug #998954 [src:libppd] libppd: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending and patch.
> tags 1001976 + patch pending
Bug #1001976 [src:libppd] ITS: libppd
Added tag(s) pending and patch.

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

Processed: libjavascript-rpc-perl: diff for salvaging upload version 0.10-2

[Debian Bug Tracking System]

Processing control commands:

> tags 999265 + patch pending
Bug #999265 [src:libjavascript-rpc-perl] libjavascript-rpc-perl: missing 
required debian/rules targets build-arch and/or build-indep
Added tag(s) patch and pending.
> tags 1001975 + patch pending
Bug #1001975 [src:libjavascript-rpc-perl] ITS: libjavascript-rpc-perl
Added tag(s) pending and patch.

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

Processed: libdebian-package-html-perl: diff for salvaging upload version 0.1-3

[Debian Bug Tracking System]

Processing control commands:

> tags 610178 + patch pending
Bug #610178 [libdebian-package-html-perl] libdebian-package-html-perl: Examples 
URLs are no longer valid
Added tag(s) patch and pending.
> tags 998918 + patch pending
Bug #998918 [src:libdebian-package-html-perl] libdebian-package-html-perl: 
missing required debian/rules targets build-arch and/or build-indep
Added tag(s) pending and patch.
> tags 1001974 + patch pending
Bug #1001974 [src:libdebian-package-html-perl] ITS: libdebian-package-html-perl
Added tag(s) pending and patch.

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

Processed: libcgi-ssi-parser-perl: diff for salvaging upload version 0.01-2

[Debian Bug Tracking System]

Processing control commands:

> tags 466397 + patch pending
Bug #466397 [libcgi-ssi-parser-perl] Odd description
Added tag(s) pending and patch.
> tags 999223 + patch pending
Bug #999223 [src:libcgi-ssi-parser-perl] libcgi-ssi-parser-perl: missing 
required debian/rules targets build-arch and/or build-indep
Added tag(s) pending and patch.
> tags 1001973 + patch pending
Bug #1001973 [src:libcgi-ssi-parser-perl] ITS: libcgi-ssi-parser-perl
Added tag(s) pending and patch.

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

Bug#1003424: marked as done (halide13-api-doc: missing Breaks+Replaces: libhalide13-doc (<< 13.0.3))

[Debian Bug Tracking System]

Your message dated Wed, 12 Jan 2022 11:28:00 +0300
with message-id 

and subject line Re: Accepted halide 13.0.3-2 (source) into unstable
has caused the Debian Bug report #1003424,
regarding halide13-api-doc: missing Breaks+Replaces: libhalide13-doc (<< 13.0.3)
to be marked as done.

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

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


-- 
1003424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: halide13-api-doc
Version: 13.0.3-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

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

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

  Preparing to unpack .../halide13-api-doc_13.0.3-1_all.deb ...
  Unpacking halide13-api-doc (13.0.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/halide13-api-doc_13.0.3-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/halide13/html/_a_s_log_8h.html', which 
is also in package libhalide13-doc 13.0.2-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/halide13-api-doc_13.0.3-1_all.deb


cheers,

Andreas


libhalide13-doc=13.0.2-2_halide13-api-doc=13.0.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 13.0.3-2

This bug has now been fixed, but apparently "Fixes" isn't recognized
as a pattern that would auto-close the bug.

Roman

On Tue, Jan 11, 2022 at 9:03 PM Debian FTP Masters
 wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Format: 1.8
> Date: Mon, 10 Jan 2022 12:15:10 +0300
> Source: halide
> Architecture: source
> Version: 13.0.3-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Roman Lebedev 
> Changed-By: Roman Lebedev 
> Changes:
>  halide (13.0.3-2) unstable; urgency=medium
>  .
>* Declare missing Breaks+Replaces on halide13-api-doc. Fixes #1003424.
>* Drop liblld dependency - only needed for WebAssembly,
>  but we don't build that anyway.
>* Don't enable LLD/PGO on some more architectures where that fails.
>* Fine-tune some more missing dependencies.
> Checksums-Sha1:
>  76ec663cbdb1b5484fe17e981ee1be2d3c3be097 2653 halide_13.0.3-2.dsc
>  0b78b0bb5e6d1353e13d5d1997aa44e5db722ccb 292512 halide_13.0.3-2.debian.tar.xz
>  e7603bb376aa4de28b7c66f2905b6ef51d4a0172 13334 
> halide_13.0.3-2_amd64.buildinfo
> Checksums-Sha256:
>  c97f966d941d62d35cf000a74def37e662de44960269b3c491bd1f4e322d0436 2653 
> halide_13.0.3-2.dsc
>  72ff81b1702e3fa38716854663777f9320eb5a18e98dc9000929fed5d1c685b4 292512 
> halide_13.0.3-2.debian.tar.xz
>  029367711573fbb89187cf6c743727c7deb781654abb1eb7cc88cfc7cf8858b4 13334 
> halide_13.0.3-2_amd64.buildinfo
> Files:
>  6f07b93971e45d4e1b94bbaf6bdf852e 2653 devel optional halide_13.0.3-2.dsc
>  407c22abe4fd050f9af1b59afa09a818 292512 devel optional 
> halide_13.0.3-2.debian.tar.xz
>  0f7441d4317a8107ebaa3d92eab22cff 13334 devel optional 
> halide_13.0.3-2_amd64.buildinfo
>
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmHdwfMACgkQfmUo2nUv
> G+HPqg//R4OP3EXK20/jYntvi5RM12CnMeI2lI4QgFAXUzxcg5zx49pJGYY7Su5O
> q51P/St4xBbxNPu1OamUITRCNzcagsYC7BWv8XoneF7EhXbZeYR+T2VBHk9/6tGc
> 8zxQmWyREpXMHBdm3dAbpFLHNaucF7hb73gaVTmVi48nmhHD9urkf11eWQO//1vJ
> zWnOeStpvcnS9/At2IETBSzOON1sE8EkK6i/ujpuWUoIR7oX0sgiEw3SXd6Y9qxg
> 4qbckpg3UyfMijcR+84jqDBsfI4bH52qG/dQO2eYVPnh/OowxCAKJYq7h49QiCwp
> E4cWalppdgmTSjZpRLAQzmIZdCI5u3dB5tzoYIfgiLqr6Gy+m2PmuRN+jmpmx6U4
> Bzo4/RxxHTF7CGfvpTcdkDeRWy3ahlPySvYJ53eT97TadleFfNHABaqyZ1by3+iq
> 0pm1EbCYcCnBc6cuH5e2SDu2/jM6DKRX7l9nG/nfIZn0AWr/T3juTqbuWevZO6av
> 4q4curxfTwareJ0jMKb1EUq1gPjngs8VGSGqwPeAnzQCcnWjj4DD9gXH73N0+vHN
> 0/5p0a6Scz49W1vHQZinWD4b4YvHvlLEMYwuLSL7Dqu8Klz4za6nTndy+SjzbVF4
> DFdStFwbugwTBsdK4FTCydElv23HO6/As/coT4gOb6Y3R0JyGzQ=
> =+kao
> -END PGP SIGNATURE-
>--- End Message ---