Processed: Re: Bug#1050396: RM: pangoterm -- RoQA; low popcon; depends on gtk2

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 967680 -1
Bug #967680 [src:pangoterm] pangoterm: depends on deprecated GTK 2
Bug #1050396 [src:pangoterm] RM: pangoterm -- RoQA; low popcon; depends on gtk2
Severity set to 'normal' from 'serious'
947713 was blocked by: 967394 967389 967405 967432 967775 967606 967754 96 
967538 967563 967471 967342 967701 967659 967586 967591 967280 967407 967847 
967491 967507 967486 967797 967685 967571 967357 967463 967438 967355 967687 
967374 967532 967505 967845 967348 967795 967245 967725 967411 967717 967258 
967715 967247 967421 967727 967521 967252 967314 967511 967640 967760 967324 
967512 967418 967251 967522 967422 967518 967412 1027731 967528 967531 967478 
972085 967708 967444 967598 967572 967469 967492 967334 967702 967735 967653 
967592 967569 967472 967341 967498 967804 967366 967544 967578 967737 967383 
967431 967380 967814 967722 967242 967712 967824 967289 967294 967650 967728 
967248 1041799 967255 967274 967257 967718 967347 967772 967636 967402 967435 
967688 967437 967358 967731 967798 967345 967508 967848 967408 967744 967682 
967664 967537 967778 967649 967792 967842 967535 967502 967352 967769 967763 
967738 967351 967577 967791 967841 967643 967786 967501 967497 967304 967495 
967696 967554 967575 967681 967475 967454 967595 967676 967705 967732 967401 
967597 967707 967477 967771 967834 967515 967527 967460 967525 967517 1041790 
967626 967711 967417 967283 967266 967425 967560 967721 967616 967427 967415 
967514 967321 967524 967311 651587 967424 967630 967414 967557 967371 967442 
967307 967305 967332 967489 967494 967548 967555 967574 967474 967455 967837 
967656 967448 967589 967594 967704 967386 967391 967338 967751 967609 967542 
967802 967457 967363 967835 967752 967369 967610 967541 967603 967801 967434 
967392 967378 967620 967583 967566 967344 967260 967745 967398 967466 967758 
967483 967331 967665 967667 967534 967372 967441 967747 967297 967827 967815 
967318 967817 967670 967825 967295 967328 967312 967254 967275 967690 967277 
967322 1041794 1041806 967780 967458 967646 967783 967337 967445 967766 967741 
967552 967693 967447 967838 967302 967335 967661 967734 967673 967547 967807 
967452 967805 967832 967545 967639 967308 967558 967480 967271 967263 967286 
967291 967821 967623 967580 959083 967600 967613 967811 967619 967244 967724 
967360 967812 967278 967629 967822 967292 967714 967269 967272 967327 967315 
967818 967317 1041801 967325 967828 967298 967395 967748 967404 967633 967831 
967774 967755 967668 1041797 967451 967757 967397 967679 967301 967662 967684 
967699 967742 967551 1049936 967377 967354 967375 967504 967844 967794 967789 
967336 967493 967647 967388 967767 967573 967461 967658 967446 967765 967539 
967645 959090 967382 967439 1041791 967806 967720 967364 967473 967561 967349 
967593 967652 967710 967703 967523 967680 967259 967513 967840 967500 1041807 
967790 967350 967770 967400 967287 967413 967285 967423 967429 967730 967419 
967326 885752 967519 967316 967253 1041828 967529 967709 967651 967584 967599 
967343 967562 967479 967756 967604 967433 967381 967396 967468 967568 967533 
967376 967579 967462 967484 967499 967288 967530 967430 967729 967249 967614 
967340 967264 967282 967719 967624 967250 967689 967694 967556 967306 967799 
967784 967642 967509 967762 967359 967836 1041804 1041796 967779 967409 885135 
967385 967657 1041802 967733 967674 967655 967768 967387 967456 967648 967565 
967420 967739 967410 967403 967634 967773 967567 967467 967353 967761 967503 
967510 967843 967641 967793 967666 967746 967683 967520 967465 967281 967590 
967700 967826 967713 967296 967470 967243 967723 967816 967276 967570 967490 
967450 967830 967323 967550 967256 967300 967313 1041800 967637 967564 967346 
967582 967393 967436 967635 967361 967602 967809 967488 967753 967549 967449 
967588 967373 967536 967339 967608 967482 967464 967576 1041795 967695 967270 
967496 967787 967368 967333 967481 967785 1006984 967379 967443 967697 967803 
967601 967759 967362 967810 967543 967677 967399 967384 967820 967581 967290 
967706 967675 967654 967596 967476 967660 967319 967526 967740 967329 967516 
967416 967627 967267 967615 967426 967265 967617 959087 967625 967671 967585 
967459 967607 967839 967605 967776 967632 967406 967587 967796 967506 967846 
967781 967356 967691 967686 967743 967559 967485 967663 967638 967309 967261 
967716 967621 967823 967293 977295 967540 967611 967813 967726 967800 967246 
967440 967330 967273 967279 959088 967618 967268 967628 967370 967612 967819 
967750 967390 967622 967284 967829 967299 967262 967310 967303 967669 967749 
967553 967692 967764 967320 967678 967644 967782 967698 967365 967631 967833 
967453 967788 967367 967736 967672
947713 was not blocking any bugs.
Added blocking bug(s) of 947713: 1050396
Merged 967680 1050396

-- 
1050396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050396
947713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947713
967680: 

Bug#1050396: RM: pangoterm -- RoQA; low popcon; depends on gtk2

[James McCoy]

Control: forcemerge 967680 -1

On Thu, Aug 24, 2023 at 01:49:47AM +0200, Bastian Germann wrote:
> pangoterm does not seem to be used a lot and is unmaintained upstream.

It's not unmaintained upstream.

> I intend to file a RM bug.
> If you have any reasons to keep it in Debian please voice them here.

If more concrete plans develop to force gtk2 out of the archive, then
this package can be removed along with those.  Until then, leave it be.

> To get people's attention, I am filing as a serious bug and will reassign to
> the FTP team when the package is autoremoved from testing.

There was already a bug noting that this still depends on gtk2.  Merging
with that one and keeping its Severity: normal.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Processed: Formwarded

[Debian Bug Tracking System]

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

> forwarded 1050367 https://bugreports.qt.io/browse/QTCREATORBUG-29537
Bug #1050367 {Done: Gianfranco Costamagna } 
[src:qtcreator] qtcreator: FTBFS with newer yaml-cpp [PATCH]
Set Bug forwarded-to-address to 
'https://bugreports.qt.io/browse/QTCREATORBUG-29537'.
> thanks
Stopping processing here.

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

Bug#1050367: marked as done (qtcreator: FTBFS with newer yaml-cpp [PATCH])

[Debian Bug Tracking System]

Your message dated Thu, 24 Aug 2023 00:50:20 +
with message-id 
and subject line Bug#1050367: fixed in qtcreator 10.0.2-2
has caused the Debian Bug report #1050367,
regarding qtcreator: FTBFS with newer yaml-cpp [PATCH]
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.)


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

Source: qtcreator
Version: 10.0.2-1ubuntu1
Severity: important
tags: patch

Hello, looks like the new yaml-cpp version is making the embedded cmake fail to 
detect it.
An easy workaround/patch is the following:

diff -Nru qtcreator-10.0.2/debian/rules qtcreator-10.0.2/debian/rules
--- qtcreator-10.0.2/debian/rules   2022-11-29 08:15:58.0 +
+++ qtcreator-10.0.2/debian/rules   2023-08-23 08:59:59.0 +
@@ -32,6 +32,10 @@
 %:
dh $@ --builddirectory=builddir
 
+override_dh_auto_clean:

+   dh_auto_clean
+   rm -rf cmake/Findyaml-cpp.cmake
+
 override_dh_auto_configure:
dh_auto_configure --buildsystem=cmake -- \
-DBUILD_DEVELOPER_DOCS=ON \

thanks for considering it, this bug will become serious once yaml-cpp 
transition is ack'd by Release Team
G.


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: qtcreator
Source-Version: 10.0.2-2
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated qtcreator 
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, 23 Aug 2023 19:24:47 -0500
Source: qtcreator
Built-For-Profiles: noudeb
Architecture: source
Version: 10.0.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Gianfranco Costamagna 
Closes: 1050367
Changes:
 qtcreator (10.0.2-2) unstable; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * Remove cmake/Findyaml-cpp.cmake for compatibility with the new yaml-cpp
 (Closes: #1050367).
 .
   [ Simon Quigley ]
   * Ack and team upload, thanks Gianfranco!
Checksums-Sha1:
 bcead64d09d840c8106cfee0ffe42e5033a10ffe 2744 qtcreator_10.0.2-2.dsc
 4f801bd0f50ac40ca87f06f673d8846ddfacdcff 29432 qtcreator_10.0.2-2.debian.tar.xz
 4232bd4584c48dab14610281c047656621e716b5 13169 
qtcreator_10.0.2-2_source.buildinfo
Checksums-Sha256:
 8e096ed3cc4d5229934ecc13db2871439de44b4b60460c2f63051cdac48a9ac5 2744 
qtcreator_10.0.2-2.dsc
 a03369a0e1cc53cd63dc27aa8658145e8269928568bb43e66c574c7318fb693f 29432 
qtcreator_10.0.2-2.debian.tar.xz
 3e66915c0eaffd74f35b7e4a778cec7cc24064d62e5b64409a023762161a12ae 13169 
qtcreator_10.0.2-2_source.buildinfo
Files:
 dcd7a048926499f080c1d6e89f8f0fa7 2744 devel optional qtcreator_10.0.2-2.dsc
 29b6dc2d2b32eaa24824cb4feaf05b4d 29432 devel optional 
qtcreator_10.0.2-2.debian.tar.xz
 b153a055c4ba22690c691d7a7d87b842 13169 devel optional 
qtcreator_10.0.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXHq+og+GMEWcyMi14n8s+EWML6QFAmTmpFIACgkQ4n8s+EWM
L6S1PA//TyYFDt8BctVmaUztH7UXSGOuLsLw/+RSl7Hi99tCWzdOxAVSmtiTsbLC
PFs+qJRXLePIKOi7086PXoDmcuve0p2WDD0XJUcpdPtSeHt4xkq8IiFxc7FiZ+Oc
8dxWRVNCvMckSd/u0aNub4AOmhWWwPuRxl79uP3dzFHIyevzq9oL92o2H0wT2d0m
HppAU6Zs96TnVz1r2QEz8tf2Z5yaXwNtlZw7f2KOcEAviVrMu7WPjj2SUaEadPav
1zAe5E0jMgmUgiqYz0Ins+aI/l41+o8ZrPfI0PDXjvUMuLdSy2YRQA7b6QhgwZwe
uW9tnXiUCm6DQjOfoPey6MrewuXHeAJ8QjAa8Kq+psq7yOTP/goeXcMK4ZtK6x7B
bHbxUGGOb9fhQSRGrZqSAJ3Uo+YdLeEO0pzYOMOlj3S6jg0uHWG4t93WGNHuFw08
PbzVplyoaQCtgxkFEv4yf3hJAPNd8arcVZlgfStt9sdG0iHPIOpfwlE31yH6+YLu
X+LZcLBXfXnNKt3LVITDJ+fcr+ABV1kfQTWY89CjA/pJMjcmV8ixRr8PvXzwCm/F
h6Lqy+gWtq8fk6065H3QqKkbxLBug07pL1CbSJ4LexRLuEIqDJ8JqkF/NCtCi5Ju
sytiiDyKW9WOGO2NDp+qaowbQnza55MA2AG4CJ2CgVGYTZCt3zQ=
=A502
-END PGP SIGNATURE End Message ---

Processed: Bug#1050367 marked as pending in qtcreator

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1050367 [src:qtcreator] qtcreator: FTBFS with newer yaml-cpp [PATCH]
Added tag(s) pending.

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

Bug#1050367: marked as pending in qtcreator

[Simon Quigley]

Control: tag -1 pending

Hello,

Bug #1050367 in qtcreator 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/qt-kde-team/qt/qtcreator/-/commit/89ccbca724ef3665e784462442c02c158858515e


Remove cmake/Findyaml-cpp.cmake for compatibility with the new yaml-cpp 
(Closes: #1050367).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1050367

Bug#1050399: RM: starplot -- RoQA; low popcon; depends on gtk2

[Bastian Germann]

Source: starplot
Severity: serious

starplot does not seem to be used a lot and is unmaintained upstream.

I intend to file a RM bug.
If you have any reasons to keep it in Debian please voice them here.
To get people's attention, I am filing as a serious bug and will 
reassign to the FTP team when the package is autoremoved from testing.

Bug#1050396: RM: pangoterm -- RoQA; low popcon; depends on gtk2

[Bastian Germann]

Source: pangoterm
Severity: serious

pangoterm does not seem to be used a lot and is unmaintained upstream.

I intend to file a RM bug.
If you have any reasons to keep it in Debian please voice them here.
To get people's attention, I am filing as a serious bug and will 
reassign to the FTP team when the package is autoremoved from testing.

Bug#1050168: FTBFS: test_no_local_cert: tlsv13 alert certificate required

[Alberto Bertogli]

On Mon, Aug 21, 2023 at 05:32:53PM +0800, Shengjing Zhu wrote:

Source: kxd
Version: 0.15-4
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: albert...@blitiri.com.ar, z...@debian.org

I'm not sure if it's related to golang-defaults -> golang-1.21 recently.


[...]

Traceback (most recent call last):
 File "/<>/tests/run_tests", line 360, in test_no_local_cert
   self.assertEqual(err.reason, "SSLV3_ALERT_BAD_CERTIFICATE")
AssertionError: 'TLSV13_ALERT_CERTIFICATE_REQUIRED' != 
'SSLV3_ALERT_BAD_CERTIFICATE'
- TLSV13_ALERT_CERTIFICATE_REQUIRED
+ SSLV3_ALERT_BAD_CERTIFICATE


Thanks for filing this!

Yeah I think it's likely, this looks like a more specific and accurate 
error is now reported in this case, either due to the Go TLS library, or 
OpenSSL (which the tests use because they're written in Python).


I have a patch in the `next` branch that should update the test 
accordingly:


https://blitiri.com.ar/git/r/kxd/c/ca7d96cc6088cddbdd9904cc8de8192b417a9340/

https://blitiri.com.ar/git/r/kxd/c/ca7d96cc6088cddbdd9904cc8de8192b417a9340.patch

Would you mind giving it a try? It should solve the problem.

Thanks!
Alberto

Bug#1050388: canu: autopkgtest generates unreasonably large artifacts

[Paul Gevers]

Source: canu
Version: 2.2+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: other

Dear maintainer(s),

Your package has an autopkgtest, great. However, it breaks the 
infrastructure. In the last version upload to unstable, the package 
started to save unreasonably large files as artifacts:


root@ci-worker13:/tmp/debci-worker-37061072-xELMvGodQM/autopkgtest-incoming/unstable/amd64/c# 
du -h --max-depth=0 canu/

256Mcanu/

which is more than our communication infrastructure can handle. Yes, 
we'll implement sane handling, but at the moment this test breaks the 
ci.d.n infrastructure. I have therefore put the package on our reject 
list, until either this bug is fixed, or our tooling handles this better.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1042046: marked as done (pyranges: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 20:50:01 +
with message-id 
and subject line Bug#1042046: fixed in pyranges 0.0.111+ds-5
has caused the Debian Bug report #1042046,
regarding pyranges: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.11 returned exit code 13
to be marked as done.

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

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


-- 
1042046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyranges
Version: 0.0.111+ds-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230724 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> echo 'Generating corresponding files ...'
> Generating corresponding files ...
> cat debian/missing-sources/test_sorted.sam| samtools view -Sb - > 
> tests/test_data/test_sorted.bam
> cat debian/missing-sources/control.sam| samtools view -Sb - > 
> pyranges/example_data/control.bam
> samtools index tests/test_data/test_sorted.bam 
> tests/test_data/test_sorted.bam.bai
> samtools index pyranges/example_data/control.bam 
> pyranges/example_data/control.bam.bai
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:307: cp -av /<>/tests/*.bed 
> /<>/.pybuild/cpython3_3.11_pyranges/build/tests && cp -av 
> /<>/tests/test_data 
> /<>/.pybuild/cpython3_3.11_pyranges/build/tests && cp -av 
> /<>/tests/data 
> /<>/.pybuild/cpython3_3.11_pyranges/build/tests && cp -av 
> /<>/pyranges/example_data 
> /<>/.pybuild/cpython3_3.11_pyranges/build/pyranges
> '/<>/tests/chip_10.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/chip_10.bed'
> '/<>/tests/f1.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/f1.bed'
> '/<>/tests/f2.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/f2.bed'
> '/<>/tests/test_data' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/test_data'
> '/<>/tests/test_data/ensembl.gtf' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/test_data/ensembl.gtf'
> '/<>/tests/test_data/gencode.gff3' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/test_data/gencode.gff3'
> '/<>/tests/test_data/ucsc_df_to_parse.txt' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/test_data/ucsc_df_to_parse.txt'
> '/<>/tests/test_data/test_sorted.bam' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/test_data/test_sorted.bam'
> '/<>/tests/test_data/test_sorted.bam.bai' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/test_data/test_sorted.bam.bai'
> '/<>/tests/data' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/data'
> '/<>/tests/data/test_data.py' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/tests/data/test_data.py'
> '/<>/pyranges/example_data/exons.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/exons.bed'
> '/<>/pyranges/example_data/ensembl.gtf' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/ensembl.gtf'
> '/<>/pyranges/example_data/ucsc_human.bed.gz' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/ucsc_human.bed.gz'
> '/<>/pyranges/example_data/chipseq_background.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/chipseq_background.bed'
> '/<>/pyranges/example_data/f2.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/f2.bed'
> '/<>/pyranges/example_data/bw.bw' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/bw.bw'
> '/<>/pyranges/example_data/f1.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/f1.bed'
> '/<>/pyranges/example_data/cpg.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/cpg.bed'
> '/<>/pyranges/example_data/lamina.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/lamina.bed'
> '/<>/pyranges/example_data/gencode_human.gtf.gz' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/gencode_human.gtf.gz'
> '/<>/pyranges/example_data/chipseq.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/chipseq.bed'
> '/<>/pyranges/example_data/aorta.bed' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/aorta.bed'
> '/<>/pyranges/example_data/ensembl_human.gtf.gz' -> 
> '/<>/.pybuild/cpython3_3.11_pyranges/build/pyranges/example_data/ensembl_human.gtf.gz'
> 

Bug#1050077: marked as done (gtk4: 4.12 regression: FTBFS on mips(64)el: multiple test failures)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 20:39:51 +
with message-id 
and subject line Bug#1050077: fixed in gtk4 4.12.0+ds-3
has caused the Debian Bug report #1050077,
regarding gtk4: 4.12 regression: FTBFS on mips(64)el: multiple test failures
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.)


-- 
1050077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk4
Version: 4.12.0+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: debian-m...@lists.debian.org
User: debian-m...@lists.debian.org
Usertags: mips64el mipsel

gtk4 4.12.0 in experimental has test failures on multiple buildds.
Of those, mips64el and mipsel seem to have the same failure mode:
failure mode:

  72/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-flipped-gl / gl 
border-one-rounded flipped   FAIL   
  5.47s   exit status 1
 315/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl / gl opacity-overdraw   
 FAIL   
  4.89s   exit status 1
 316/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-flipped-gl / gl 
opacity-overdraw flipped FAIL   
  4.94s   exit status 1
 317/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-repeated-gl / 
gl opacity-overdraw repeated   FAIL 
5.05s   exit status 1
 318/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-rotated-gl / gl 
opacity-overdraw rotated FAIL   
  4.95s   exit status 1
 319/1464 gtk:gsk+gsk-compare+gsk-gl+gsk-compare-gl+gsk-compare-masked-gl / gl 
opacity-overdraw masked   FAIL  
   5.02s   exit status 1
1406/1464 gtk:reftest / reftest label-sizing.ui 
 FAIL   
 19.29s   0/1 subtests passed
1422/1464 gtk:reftest / reftest opacity.ui  
 FAIL   
  6.79s   0/1 subtests passed

These are "reftests", which work by rendering the same image in two
different ways and then doing a pixel-by-pixel comparison. Because
Debian buildds do not give us a way to capture test artifacts, the images
are output into the log with uuencode, for example these:

begin-base64 644 testsuite/gsk/compare/opacity-overdraw.png
iVBORw0KGgoNSUhEUgAAAB4eCAY7MK6iRklEQVRIie3WMQ4AIAxCUWo8uDev
B7BjYwc+I8tLmAgpjwayJlDgr9lVmYpWJJRP5zc1MDAwMDAwsDFcfq7qI3XHb2o/+AJ0lQS/vZJx
GQBJRU5ErkJggg==


begin-base64 644 
debian/build/deb/testsuite/gsk/compare/gl/x11/opacity-overdraw.out.png
iVBORw0KGgoNSUhEUgAAAB4eCAY7MK6iS0lEQVRIie3WMQ4AIAhD0aIe3Isb
vACDA5GB35HlJWWpSb5VkFGBAn/Nio5HlopM+Rv8o4Z+PwYGBgYGBgauh8PpY8FGyk6/qvvBF6Er
BMOKG8HLAElFTkSuQmCC


begin-base64 644 
debian/build/deb/testsuite/gsk/compare/gl/x11/opacity-overdraw.diff.png
iVBORw0KGgoNSUhEUgAAAB4eCAY7MK6iKklEQVRIie3NoQEAIAzEwGdvZPeG
BUBR3J2MSQKfjFOsZHVO5uUDAAC82WlIAgJv9eZaAElFTkSuQmCC


The way these work is that they are output in sets of three: a reference
image, an actual output, and an artifically-enhanced diff image to
highlight what the difference is. See #1024391, #993550, #1003348 for
previous examples of architecture-specific rendering differences (#1024391
was not on mips*, but has details of how to run individual tests which
might be useful, while the other two were on mips*el).

I haven't reconstructed the actual images for a visual comparison yet.
If the mis-rendering doesn't seem release-critically bad then we'll work
around this by ignoring those particular test failures on mips*el.

mips*el are the only architectures where we are using the softpipe GL
driver (because llvmpipe appears to be otherwise broken there) so that is a
possible root cause.

Having to investigate and work around failing tests in GL-dependent
packages on mips*el is becoming a significant time sink for the GNOME team,
so I would appreciate it if mips porters could fix its llvmpipe so that it
can be back in the same situation as every other release architecture.

smcv
--- End Message ---
--- Begin Message ---
Source: gtk4
Source-Version: 4.12.0+ds-3
Done: Simon 

Bug#1047864: marked as done (impressive: Crashes at startup: «module 'PIL.Image' has no attribute 'ANTIALIAS'»)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 20:40:00 +
with message-id 
and subject line Bug#1047864: fixed in impressive 0.13.1-1.1
has caused the Debian Bug report #1047864,
regarding impressive: Crashes at startup: «module 'PIL.Image' has no attribute 
'ANTIALIAS'»
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.)


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

Hello again,

I have stumbled upon a new bug that affects impressive :-(

When starting up, I see the logo screen, but immediately afterwards, impressive
crashes with the following:

$ impressive test.pdf 
Welcome to Impressive version 0.13.1
Platform library: [pygame-unix] Python 3.11.4 / PyGame 2.5.0 / SDL 2.28.1
Detected screen size: 3840x2160 pixels
PDF renderer: MuPDF 1.4 or newer
OpenGL renderer: Mesa Intel(R) UHD Graphics 600 (GLK 2)
Your version of PIL is too old or incomplete, disabling OSD.
warning: ICC support is not available
warning: ICC support is not available


===
OOPS! Impressive crashed!
This shouldn't happen. Please report this incident to the author, including 
the
full output of the program, particularly the following lines. If possible,
please also send the input files you used.

Impressive version: 0.13.1
Python version: 3.11.4 (main, Jun 7 2023, 10:13:09) [GCC 12.2.0]
Impressive platform: pygame-unix
PyGame version: 2.5.0
SDL version: 2.28.1
PIL version: Pillow 10.0.0
PDF renderer: MuPDF 1.4 or newer
OpenGL vendor: Intel
OpenGL renderer: Mesa Intel(R) UHD Graphics 600 (GLK 2)
OpenGL version: 4.6 (Compatibility Profile) Mesa 23.1.4-1
Operating system: Linux 6.4.0-1-amd64 (x86_64)
Linux distribution: Debian GNU/Linux trixie/sid
Command line: /usr/bin/impressive test.pdf
Traceback (most recent call last):
  File "/usr/bin/impressive", line 6569, in run_main
main()
  File "/usr/bin/impressive", line 6486, in main
RenderPage(Pcurrent, Tcurrent)
  File "/usr/bin/impressive", line 3741, in RenderPage
gl.TexImage2D(gl.TEXTURE_2D, 0, gl.RGB, TexWidth, TexHeight, 0, gl.RGB, 
gl.UNSIGNED_BYTE, PageImage(page))

  ^^^
  File "/usr/bin/impressive", line 3706, in PageImage
img.thumbnail((sx, sy), Image.ANTIALIAS)
^^^
AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS'
$ 

I suppose this comes as a change in python3-pil's API. I got impressive to work
again by very simplisticly substituting Image.ANTIALIAS in /usr/bin/impressive,
but of course, I'm sure there are better ways to patch this issue :-)

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

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

Versions of packages impressive depends on:
ii  mupdf-tools 1.22.2+ds1-1
ii  poppler-utils   22.12.0-2+b1
ii  python3 3.11.4-5
ii  python3-pil 10.0.0-1
ii  python3-pygame  2.5.0-1

Versions of packages impressive recommends:
ii  ffmpeg 7:6.0-5
ii  mplayer2:1.5+svn38423-2+b1
ii  perl   5.36.0-7
ii  xdg-utils  1.1.3-4.1

Versions of packages impressive suggests:
ii  ghostscript   10.01.2~dfsg-1
pn  latex-beamer  
pn  pdftk 

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: impressive
Source-Version: 0.13.1-1.1
Done: Gunnar Wolf 

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

Debian distribution maintenance software
pp.
Gunnar Wolf  (supplier of updated impressive package)

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

Bug#1050077: marked as pending in gtk4

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #1050077 in gtk4 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/gnome-team/gtk4/-/commit/f2ea697c57fe557cc9ebf55b2c6d2546323fe87e


d/rules: Accept minor rendering differences for some tests on mips*

Presumably these render a bit differently with softpipe.

Closes: #1050077


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1050077

Processed: Bug#1050077 marked as pending in gtk4

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1050077 [src:gtk4] gtk4: 4.12 regression: FTBFS on mips(64)el: multiple 
test failures
Added tag(s) pending.

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

Processed: Bug#1042046 marked as pending in pyranges

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042046 [src:pyranges] pyranges: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) pending.

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

Bug#1042046: marked as pending in pyranges

[Étienne Mollier]

Control: tag -1 pending

Hello,

Bug #1042046 in pyranges 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/med-team/pyranges/-/commit/051023b667ecae2f1ae9832b6652cda88a17f729


healthcheck-all.patch: new: fix test failure.

The test failure seems to be caused by a call to an obsoleted method
in a decorator describing the properties of the affected test.

Closes: #1042046


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042046

Bug#1042246: gdcm: FTBFS: make[1]: *** [debian/rules:107: override_dh_auto_configure] Error 2

[Aurelien Jarno]

Hi,

On 2023-07-26 22:24, Lucas Nussbaum wrote:
> Source: gdcm
> Version: 3.0.21-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230726 ftbfs-trixie
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 

I have started to investigate this, but my cmake knowledge is quite
limited, so I am progressing slowly. Here are my findings:

- The issue has been introduced by cmake 3.27. gdcm builds fine with
  cmake from stable and everything else from sid.

- The reported issue seems to be linked to a cache issue between the two
  libexpat detection: the one from gdcm in CMakeLists.txt:423 and using
  find_package() and the one shipped by libvtk9-dev in 
  $DEB_HOST_MULTIARCH/cmake/vtk-9.1/FindEXPAT.cmake: using
  find_library(). Dropping the first one or passing NO_CACHE to
  find_library() is enough to get rid of the issue.

- The issue is only visible with DGDCM_USE_SYSTEM_EXPAT:BOOL=ON which is
  not the default, so it is likely that the issue hasn't been noticed
  before.

- Independently of the reported issue, gdcm still uses find_package()
  with PythonInterp or PythonLibs which have been removed from cmake
  3.27, so fixing it is not enough to get gdcm working.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net


signature.asc
Description: PGP signature

Bug#1025568: marked as done (gparted: dependency on transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 18:35:21 +
with message-id 
and subject line Bug#1025568: fixed in gparted 1.5.0-1
has caused the Debian Bug report #1025568,
regarding gparted: dependency on transitional policykit-1 package
to be marked as done.

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

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


-- 
1025568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gparted
Version: 1.3.1-1
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1
Control: block 1025540 by -1

This package has a Depends and Build-Depends on the transitional
package policykit-1, which has been separated into polkitd, pkexec and
(deprecated) polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

If this package requires polkit at build-time (usually for the gettext
extensions polkit.its and polkit.loc), please build-depend on both
libpolkit-gobject-1-dev and polkitd, even if the package does not
actually depend on libpolkit-gobject-1 at runtime. This is because
the gettext extensions are currently in polkitd, but might be moved to
libpolkit-gobject-1-dev in future (see #955204). pkexec is usually not
required at build-time.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gparted
Source-Version: 1.5.0-1
Done: Phillip Susi 

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

Debian distribution maintenance software
pp.
Phillip Susi  (supplier of updated gparted 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, 10 Aug 2023 11:39:22 -0400
Source: gparted
Architecture: source
Version: 1.5.0-1
Distribution: unstable
Urgency: medium
Maintainer: Phillip Susi 
Changed-By: Phillip Susi 
Closes: 1025568
Changes:
 gparted (1.5.0-1) unstable; urgency=medium
 .
   * Fix the watch file
   * New upstream version 1.5.0
   * build-depend on libpolkit-gobject-1-dev
   * Switch dependency from transitional polkit-1 to pkexec package (Closes: 
#1025568)
Checksums-Sha1:
 5bb254ecb270780f3c9606d04d6c517e08f314c1 1917 gparted_1.5.0-1.dsc
 e5f841eef14d005d8e4c30aa453a11a04d49d26d 5416965 gparted_1.5.0.orig.tar.gz
 18214587e8fb1849096c979d5436bf82bed25c39 488 gparted_1.5.0.orig.tar.gz.asc
 6d4aada0dbb84eccd118ed5a9df57f96a8d7ef61 14924 gparted_1.5.0-1.debian.tar.xz
 3e98253eb3350ebebfae3d8085fdd0275825f658 15572 gparted_1.5.0-1_source.buildinfo
Checksums-Sha256:
 bdac41a72a77e81731efbcbd41a384059b7779856d655125dc946d8495a372c6 1917 
gparted_1.5.0-1.dsc
 3c95ea26a944083ff1d9b17639b1e2ad9758df225dc751ff407b2a6aa092a8de 5416965 
gparted_1.5.0.orig.tar.gz
 a464680ddd7c8f907feec69133a54ae69f699fc327fbbe0260fd29c66b2e3866 488 
gparted_1.5.0.orig.tar.gz.asc
 0f9aaca63b8d76badc22b1b4de44863279864ca3e6f7cae3f693300f89f23ee7 14924 
gparted_1.5.0-1.debian.tar.xz
 e841a2c49fa6b2b3c47321cd3f8000b5682b982b00b5f608a23cf2aee5353fc9 15572 
gparted_1.5.0-1_source.buildinfo
Files:
 0d18c7702ce7a077f9dfe30ab420983b 1917 gnome optional gparted_1.5.0-1.dsc
 9adbd4b1cbcb7a7c76dcc0e9ffed9a7c 5416965 gnome optional 
gparted_1.5.0.orig.tar.gz
 25eea742df2ab4e391e8a3572775c772 488 gnome optional 
gparted_1.5.0.orig.tar.gz.asc
 8a2889a93c28146cc36042d535ec50d8 14924 gnome optional 
gparted_1.5.0-1.debian.tar.xz
 6e856ed7bc62b034963a5ef57c24e96e 15572 gnome optional 
gparted_1.5.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFHBAEBCgAxFiEEWwRcGALhKS3ONyQ99qui/rDisKQFAmTmSOsTHHBoaWxsQHRo

Bug#1025568: gparted: diff for NMU version 1.3.1-1.1

[Phillip Susi]

Hugh McMaster  writes:

> I didn't see a need to build-depend on libpolkit-gobject-1-dev, but
> I'm not overly familiar with gparted's requirements.

I think something changed in 1.5 that made it require a file that moved
to this package in trixie, so I had to add it to get it to build.

> Please let me know if I should submit a PR for the NMU on salsa
> (noting you'd have to update the changelog to account for your recent
> changes), or whether I should cancel the upload.

Sorry for the late reply.  I would have said cancel it but it looks like
it already went through.  It sounds like it shouldn't hurt for me to
just upload my build though, so I'll do that now that I sorted out my
new signing subkey.

Processed: severity now serious

[Debian Bug Tracking System]

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

> severity 1050367 serious
Bug #1050367 [src:qtcreator] qtcreator: FTBFS with newer yaml-cpp [PATCH]
Severity set to 'serious' from 'important'
> severity 1050366 serious
Bug #1050366 [src:opencolorio] opencolorio: FTBFS with newer yaml-cpp [PATCH]
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1050375: Invalid command name "pg_connect"

[Christoph Berg]

Package: pfm
Version: 2.0.8-3
Severity: grave

pfm doesn't do anything useful here, it just produces a message popup
saying

Connection to database foo has failed:

invalid command name "pg_connect"

I guess Tcl/Tk has changed since this package was last updated 10 years ago.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages pfm depends on:
ii  itcl3  3.4.4-2
ii  libpgtcl   1:3.0.0-1
ii  postgresql-client  15+253.pgdg+1
ii  postgresql-client-10 [postgresql-  10.23-2.pgdg+1
client]
ii  postgresql-client-11 [postgresql-  11.21-1.pgdg+1
client]
ii  postgresql-client-12 [postgresql-  12.16-1.pgdg+1
client]
ii  postgresql-client-13 [postgresql-  13.12-1.pgdg+1
client]
ii  postgresql-client-14 [postgresql-  14.9-1.pgdg+1
client]
ii  postgresql-client-15 [postgresql-  15.4-1.pgdg+1
client]
ii  postgresql-client-16 [postgresql-  16~beta2-2.pgdg+~20230807.1056.ge8386b2
client]
ii  postgresql-client-17 [postgresql-  17~~devel-1.pgdg+~20230820.0934.g1951d21
client]
ii  postgresql-client-8.2 [postgresql  8.2.23-11.pgdg+1
-client]
ii  postgresql-client-8.4 [postgresql  8.4.22-9.pgdg+1
-client]
ii  postgresql-client-9.3 [postgresql  9.3.25-9.pgdg+1
-client]
ii  postgresql-client-9.4 [postgresql  9.4.26-8.pgdg+1
-client]
ii  postgresql-client-9.5 [postgresql  9.5.25-6.pgdg+1
-client]
ii  postgresql-client-9.6 [postgresql  9.6.24-5.pgdg+1
-client]
ii  sensible-utils 0.0.20
ii  tcl8.6.13
ii  tk 8.6.13

pfm recommends no packages.

Versions of packages pfm suggests:
ii  postgresql  15+253.pgdg+1

-- no debconf information

Christoph

Bug#1050372: RM: prooftree -- RoQA; depends on gtk2; no human uploader; unmaintained upstream; low popcon

[Bastian Germann]

Source: prooftree
Severity: serious

Please consider removing prooftree. It has a very low popcon, lists no 
Uploaders (team maintained), and depends transitively on gtk2. The last 
upstream release was in 2017.


I intend to file a RM bug.
If you have any reasons to keep it in Debian please voice them here.
To get people's attention, I am filing as a serious bug and will 
reassign to the FTP team when the package is autoremoved from testing.

Bug#1050369: RM: freetennis -- RoQA; dead upstream; depends on gtk2

[Bastian Germann]

Source: freetennis
Severity: serious

freetennis does not seem to be used a lot and is unmaintained upstream.
With tennix, there is a similar alternative available.

I intend to file a RM bug.
If you have any reasons to keep it in Debian please voice them here.
To get people's attention, I am filing as a serious bug and will 
reassign to the FTP team when the package is autoremoved from testing.

Bug#1050363: flit ftbfs in unstable

[Matthias Klose]

Package: src:flit
Version: 3.9.0-1
Severity: serious
Tags: sid trixie

flit ftbfs in unstable,

[...]
__ test_sdist __

rel_path = 'README.rst', proj_dir = PosixPath('.'), guess_mimetype = True

def description_from_file(rel_path: str, proj_dir: Path, 
guess_mimetype=True):
if osp.isabs(rel_path):
raise ConfigError("Readme path must be relative")

desc_path = proj_dir / rel_path
try:
>   with desc_path.open('r', encoding='utf-8') as f:

flit_core/config.py:281:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = PosixPath('README.rst'), mode = 'r', buffering = -1, encoding = 'utf-8'
errors = None, newline = None

def open(self, mode='r', buffering=-1, encoding=None,
 errors=None, newline=None):
"""
Open the file pointed by this path and return a file object, as
the built-in open() function does.
"""
if "b" not in mode:
encoding = io.text_encoding(encoding)
>   return io.open(self, mode, buffering, encoding, errors, newline)
E   FileNotFoundError: [Errno 2] No such file or directory: 'README.rst'

/usr/lib/python3.11/pathlib.py:1045: FileNotFoundError

During handling of the above exception, another exception occurred:

tmp_path = '/tmp/pytest-of-buildd/pytest-0/test_sdist0', cwd_project = None

def test_sdist(tmp_path, cwd_project):
tmp_path = str(tmp_path)
>   filename = buildapi.build_sdist(tmp_path)

flit_core/tests/test_build_thyself.py:51:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
flit_core/buildapi.py:82: in build_sdist
path = SdistBuilder.from_ini_path(pyproj_toml).build(Path(sdist_directory))
flit_core/sdist.py:90: in from_ini_path
ini_info = read_flit_config(ini_path)
flit_core/config.py:79: in read_flit_config
return prep_toml_config(d, path)
flit_core/config.py:106: in prep_toml_config
loaded_cfg = read_pep621_metadata(d['project'], path)
flit_core/config.py:454: in read_pep621_metadata
desc_content, mimetype = description_from_file(readme, path.parent)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

rel_path = 'README.rst', proj_dir = PosixPath('.'), guess_mimetype = True

def description_from_file(rel_path: str, proj_dir: Path, 
guess_mimetype=True):
if osp.isabs(rel_path):
raise ConfigError("Readme path must be relative")

desc_path = proj_dir / rel_path
try:
with desc_path.open('r', encoding='utf-8') as f:
raw_desc = f.read()
except IOError as e:
if e.errno == errno.ENOENT:
>   raise ConfigError(
"Description file {} does not exist".format(desc_path)
)
E   flit_core.config.ConfigError: Description file README.rst does 
not exist


flit_core/config.py:285: ConfigError
=== short test summary info 
FAILED flit_core/tests/test_build_thyself.py::test_prepare_metadata - flit_co...
FAILED flit_core/tests/test_build_thyself.py::test_wheel - flit_core.config.C...
FAILED flit_core/tests/test_build_thyself.py::test_sdist - flit_core.config.C...
= 3 failed, 87 passed in 0.38s =

Bug#1050361: RM: mangler -- RoQA; dead upstream; depends on gtk2

[Bastian Germann]

Source: mangler
Severity: serious
Version: 1.2.5-5

mangler does not seem to be used a lot and is dead upstream. I doubt 
that Ventrilo is still a thing nowadays.


I intend to file a RM bug.
If you have any reasons to keep it in Debian please voice them here.
To get people's attention, I am filing as a serious bug and will 
reassign to the FTP team when the package is autoremoved from testing.

Bug#1042196: marked as done (shasta: FTBFS: Base.hpp:35:18: error: ‘uint8_t’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 16:40:10 +
with message-id 
and subject line Bug#1042196: fixed in shasta 0.11.1-2
has caused the Debian Bug report #1042196,
regarding shasta: FTBFS: Base.hpp:35:18: error: ‘uint8_t’ was not declared in 
this scope
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.)


-- 
1042196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shasta
Version: 0.11.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/staticLibrary && /usr/bin/c++ 
> -DBOOST_ALLOW_DEPRECATED_HEADERS -DBOOST_ERROR_CODE_HEADER_ONLY 
> -DBOOST_SYSTEM_NO_DEPRECATED -DBUILD_ID=0.11.1 -DNDEBUG 
> -I/<>/staticLibrary/../src -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -std=c++20 -Wall 
> -Wconversion -Wno-unused-result -Wno-trigraphs -g0 -O3 -mcx16 -MD -MT 
> staticLibrary/CMakeFiles/shastaStaticLibrary.dir/__/src/Assembler.cpp.o -MF 
> CMakeFiles/shastaStaticLibrary.dir/__/src/Assembler.cpp.o.d -o 
> CMakeFiles/shastaStaticLibrary.dir/__/src/Assembler.cpp.o -c 
> /<>/src/Assembler.cpp
> In file included from /<>/src/AssembledSegment.hpp:5,
>  from /<>/src/AssembledSegment.cpp:2:
> /<>/src/Base.hpp:35:18: error: ‘uint8_t’ was not declared in 
> this scope
>35 | static array table;
>   |  ^~~
> /<>/src/Base.hpp:17:1: note: ‘uint8_t’ is defined in header 
> ‘’; did you forget to ‘#include ’?
>16 | #include "string.hpp"
>   +++ |+#include 
>17 | 
> /<>/src/Base.hpp:35:30: error: template argument 1 is invalid
>35 | static array table;
>   |  ^
> /<>/src/Base.hpp:48:5: error: ‘uint8_t’ does not name a type
>48 | uint8_t value;
>   | ^~~
> /<>/src/Base.hpp:48:5: note: ‘uint8_t’ is defined in header 
> ‘’; did you forget to ‘#include ’?
> /<>/src/Base.hpp:93:29: error: ‘uint8_t’ has not been declared
>93 | static Base fromInteger(uint8_t i)
>   | ^~~
> /<>/src/Base.hpp:99:29: error: ‘uint16_t’ has not been declared
>99 | static Base fromInteger(uint16_t i)
>   | ^~~~
> /<>/src/Base.hpp:99:17: error: ‘static shasta::Base 
> shasta::Base::fromInteger(int)’ cannot be overloaded with ‘static 
> shasta::Base shasta::Base::fromInteger(int)’
>99 | static Base fromInteger(uint16_t i)
>   | ^~~
> /<>/src/Base.hpp:93:17: note: previous declaration ‘static 
> shasta::Base shasta::Base::fromInteger(int)’
>93 | static Base fromInteger(uint8_t i)
>   | ^~~
> /<>/src/Base.hpp:105:29: error: ‘uint32_t’ has not been declared
>   105 | static Base fromInteger(uint32_t i)
>   | ^~~~
> /<>/src/Base.hpp:105:17: error: ‘static shasta::Base 
> shasta::Base::fromInteger(int)’ cannot be overloaded with ‘static 
> shasta::Base shasta::Base::fromInteger(int)’
>   105 | static Base fromInteger(uint32_t i)
>   | ^~~
> /<>/src/Base.hpp:93:17: note: previous declaration ‘static 
> shasta::Base shasta::Base::fromInteger(int)’
>93 | static Base fromInteger(uint8_t i)
>   | ^~~
> /<>/src/Base.hpp:111:29: error: ‘uint64_t’ has not been declared
>   111 | static Base fromInteger(uint64_t i)
>   | ^~~~
> /<>/src/Base.hpp:111:17: error: ‘static shasta::Base 
> shasta::Base::fromInteger(int)’ cannot be overloaded with ‘static 
> shasta::Base shasta::Base::fromInteger(int)’
>   111 | static Base fromInteger(uint64_t i)
>   | ^~~
> /<>/src/Base.hpp:93:17: note: previous declaration ‘static 
> shasta::Base shasta::Base::fromInteger(int)’
>93 | static Base fromInteger(uint8_t i)
>   | ^~~
> /<>/src/Base.hpp: In constructor ‘shasta::Base::Base()’:
> /<>/src/Base.hpp:51:14: error: class ‘shasta::Base’ does not 
> have any field named ‘value’
>51 | Base() : value(0) {}
>   |  ^
> /<>/src/Base.hpp: In member function ‘bool 
> shasta::Base::isValid() const’:
> /<>/src/Base.hpp:55:16: error: ‘value’ was not declared in this 
> scope
>55 | return value < 4;
>   | 

Bug#1050359: RM: gpr -- RoQA; dead upstream; depends on gtk2

[Bastian Germann]

Source: gpr
Severity: serious
Version: 0.15deb-2

gpr does not seem to be used a lot and is dead upstream. The Debian 
version is essentially a fork that is also not updated since 2011.


I intend to file a RM bug.
If you have any reasons to keep it in Debian please voice them here.
To get people's attention, I am filing as a serious bug and will 
reassign to the FTP team when the package is autoremoved from testing.

Bug#1050077: gtk4: 4.12 regression: FTBFS on mips(64)el: multiple test failures

[Simon McVittie]

Control: tags -1 - pending

On Sat, 19 Aug 2023 at 12:34:31 +0100, Simon McVittie wrote:
> I haven't reconstructed the actual images for a visual comparison yet.
> If the mis-rendering doesn't seem release-critically bad then we'll work
> around this by ignoring those particular test failures on mips*el.

The mis-rendering doesn't seem likely to cause RC-severity bugs for end
users, so yes I'm going to ignore them.
https://salsa.debian.org/gnome-team/gtk4/-/merge_requests/16

smcv

Processed: Re: Bug#1050077: gtk4: 4.12 regression: FTBFS on mips(64)el: multiple test failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - pending
Bug #1050077 [src:gtk4] gtk4: 4.12 regression: FTBFS on mips(64)el: multiple 
test failures
Ignoring request to alter tags of bug #1050077 to the same tags previously set

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

Processed: tagging 1050077

[Debian Bug Tracking System]

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

> tags 1050077 + experimental
Bug #1050077 [src:gtk4] gtk4: 4.12 regression: FTBFS on mips(64)el: multiple 
test failures
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Processed: tagging 1050075

[Debian Bug Tracking System]

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

> tags 1050075 + experimental
Bug #1050075 {Done: Simon McVittie } [src:gtk4] gtk4: 4.12 
regression: FTBFS on arm*|ppc64el|s390x: several checkerboard tests failing
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Processed: tagging 1050076

[Debian Bug Tracking System]

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

> tags 1050076 + experimental
Bug #1050076 {Done: Simon McVittie } [src:gtk4] gtk4: 4.12 
regression: FTBFS on i386: assertion failed (r == tests[i].r (+/- FLT_EPSILON))
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#1042174: marked as done (libnginx-mod-js: FTBFS: src/njs_iterator.c:358:25: error: storing the address of local variable ‘string_obj’ in ‘*args.value’ [-Werror=dangling-pointer=])

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 16:05:51 +
with message-id 
and subject line Bug#1042174: fixed in libnginx-mod-js 0.8.0-1
has caused the Debian Bug report #1042174,
regarding libnginx-mod-js: FTBFS: src/njs_iterator.c:358:25: error: storing the 
address of local variable ‘string_obj’ in ‘*args.value’ 
[-Werror=dangling-pointer=]
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.)


-- 
1042174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnginx-mod-js
Version: 0.7.12-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> cc -c -pipe -fPIC -fvisibility=hidden -O -W -Wall -Wextra 
> -Wno-unused-parameter -Wwrite-strings -Wmissing-prototypes -Werror -g 
> -fexcess-precision=standard -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -fPIC -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security   \
>   -Isrc -Ibuild -Injs \
>   -o build/src/njs_iterator.o \
>   -MMD -MF build/src/njs_iterator.dep -MT build/src/njs_iterator.o \
>   src/njs_iterator.c
> src/njs_iterator.c: In function ‘njs_object_iterate’:
> src/njs_iterator.c:358:25: error: storing the address of local variable 
> ‘string_obj’ in ‘*args.value’ [-Werror=dangling-pointer=]
>   358 | args->value = _obj;
>   | ^
> src/njs_iterator.c:300:58: note: ‘string_obj’ declared here
>   300 | njs_value_t *value, *entry, prop, character, string_obj;
>   |  ^~
> src/njs_iterator.c:293:55: note: ‘args’ declared here
>   293 | njs_object_iterate(njs_vm_t *vm, njs_iterator_args_t *args,
>   |  ~^~~~
> src/njs_iterator.c: In function ‘njs_object_iterate_reverse’:
> src/njs_iterator.c:522:25: error: storing the address of local variable 
> ‘string_obj’ in ‘*args.value’ [-Werror=dangling-pointer=]
>   522 | args->value = _obj;
>   | ^
> src/njs_iterator.c:462:58: note: ‘string_obj’ declared here
>   462 | njs_value_t *entry, *value, prop, character, string_obj;
>   |  ^~
> src/njs_iterator.c:455:63: note: ‘args’ declared here
>   455 | njs_object_iterate_reverse(njs_vm_t *vm, njs_iterator_args_t *args,
>   |  ~^~~~
> cc1: all warnings being treated as errors
> make[2]: *** [build/Makefile:702: build/src/njs_iterator.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/libnginx-mod-js_0.7.12-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results

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 mark 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: libnginx-mod-js
Source-Version: 0.8.0-1
Done: Jan Mojžíš 

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

Debian distribution maintenance software
pp.
Jan Mojžíš  (supplier of updated libnginx-mod-js 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: 

Bug#1050355: tiledarray has unfulfilled build dependencies

[Matthias Klose]

Package: src:tiledarray
Version: 1.0.0-1
Severity: serious
Tags: sid trixie

see https://buildd.debian.org/status/package.php?p=tiledarray

Dep-Wait (libbtas-dev (>= 0.0+git20221014.147bf4d4-1.1))	211d 27m	Dep-Wait 
(libmpich-dev (>= 4.0.2-2.1), libbtas-dev (>= 0.0+git20221014.147bf4d4-1.1))

Bug#1041427: marked as done (bitcoin: CVE-2023-37192)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:44:22 +
with message-id 
and subject line Bug#944744: Removed package(s) from unstable
has caused the Debian Bug report #1041427,
regarding bitcoin: CVE-2023-37192
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.)


-- 
1041427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bitcoin
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for bitcoin.

CVE-2023-37192[0]:
| Memory management and protection issues in Bitcoin Core v22 allows
| attackers to modify the stored sending address within the app's
| memory, potentially allowing them to redirect Bitcoin transactions
| to wallets of their own choosing.

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

For further information see:

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

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Version: 22.0-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1036647: marked as done (bitcoin: CVE-2023-33297)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:44:22 +
with message-id 
and subject line Bug#944744: Removed package(s) from unstable
has caused the Debian Bug report #1036647,
regarding bitcoin: CVE-2023-33297
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.)


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

Hi,

The following vulnerability was published for bitcoin.

CVE-2023-33297[0]:
| Bitcoin Core before 24.1, when debug mode is not used, allows
| attackers to cause a denial of service (CPU consumption) because
| draining the inventory-to-send queue is inefficient, as exploited in
| the wild in May 2023.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-33297
https://www.cve.org/CVERecord?id=CVE-2023-33297
[1] https://github.com/bitcoin/bitcoin/issues/27586
[2] https://github.com/bitcoin/bitcoin/issues/27623
[3] https://github.com/bitcoin/bitcoin/pull/27610

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 22.0-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1020260: marked as done (bitcoin FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:44:22 +
with message-id 
and subject line Bug#944744: Removed package(s) from unstable
has caused the Debian Bug report #1020260,
regarding bitcoin FTBFS: test failure
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.)


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

https://buildd.debian.org/status/logs.php?pkg=bitcoin=22.0-1%2Bb1

...
FAIL: tests
===

test count = 64
random seed = 6388444144dae7d2c5fc175f9e60b0b9
Failure 10 on 30 1d 02 03 bc ff ff 02 16 00 fb ff ff ff ff ff 00 c0 ff 07 00 00 
ff ff ff ff ff ff ff ff ff 
src/tests.c:5776: test condition failed: ret == 0
FAIL tests (exit status: 134)


Testsuite summary for libsecp256k1 0.1

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log

make[7]: *** [Makefile:1287: test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Version: 22.0-1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1014166: marked as done (bitcoin: CVE-2021-31876)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:44:22 +
with message-id 
and subject line Bug#944744: Removed package(s) from unstable
has caused the Debian Bug report #1014166,
regarding bitcoin: CVE-2021-31876
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.)


-- 
1014166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bitcoin
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for bitcoin.

CVE-2021-31876[0]:
| Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the
| replacement policy specified in BIP125, which makes it easier for
| attackers to trigger a loss of funds, or a denial of service attack
| against downstream projects such as Lightning network nodes. An
| unconfirmed child transaction with nSequence = 0xff_ff_ff_ff, spending
| an unconfirmed parent with nSequence = 0xff_ff_ff_fd, should be
| replaceable because there is inherited signaling by the child
| transaction. However, the actual PreChecks implementation does not
| enforce this. Instead, mempool rejects the replacement attempt of the
| unconfirmed child transaction.

https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures#CVE-2021-31876
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-May/018893.html


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-31876
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-31876

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Version: 22.0-1+rm

Dear submitter,

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

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

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

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

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

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

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

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:37:51 +
with message-id 
and subject line Bug#1049425: Removed package(s) from unstable
has caused the Debian Bug report #999318,
regarding libpam-blue: 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.)


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 0.9.0-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#965674: marked as done (libpam-blue: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:37:51 +
with message-id 
and subject line Bug#1049425: Removed package(s) from unstable
has caused the Debian Bug report #965674,
regarding libpam-blue: 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.)


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

Hi,

The package libpam-blue 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 ---
Version: 0.9.0-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#1026373: marked as done (json11: Upstream dead, known encoding bugs)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:36:45 +
with message-id 
and subject line Bug#1049414: Removed package(s) from unstable
has caused the Debian Bug report #1026373,
regarding json11: Upstream dead, known encoding bugs
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.)


-- 
1026373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026373
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: json11
Version: 1.0.0-3+b1
Severity: important

json11 is dead upstream, and has known encoding bugs. It currently has
no real users in Debian (except as a dependency of yet another library).

It would be good to remove it from (at least) testing before actual
users show up.

Chris
--- End Message ---
--- Begin Message ---
Version: 1.0.0-3+rm

Dear submitter,

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

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

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

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

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

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

Bug#1026369: marked as done (golang-github-unknwon-i18n: keep gitea deps out of testing)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:37:19 +
with message-id 
and subject line Bug#1049416: Removed package(s) from unstable
has caused the Debian Bug report #1026369,
regarding golang-github-unknwon-i18n: keep gitea deps out of testing
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.)


-- 
1026369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-unknwon-i18n
Version: 0.0~git20170218.0.8372b90-1
Severity: serious

This package was introduced as a library used by gitea, but has not seen
updates in 5 years and gitea itself is also long gone. Upstream also has
given up on it many years ago.

Lets keep these bits out of testing.

Chris
--- End Message ---
--- Begin Message ---
Version: 0.0~git20170218.0.8372b90-9+rm

Dear submitter,

as the package golang-github-unknwon-i18n has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

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

Bug#1024661: marked as done (r-bioc-bitseq: orphaned upstream and blocking BioC 3.16 transition)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:30:50 +
with message-id 
and subject line Bug#1049359: Removed package(s) from unstable
has caused the Debian Bug report #1024661,
regarding r-bioc-bitseq: orphaned upstream and blocking BioC 3.16 transition
to be marked as done.

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

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


-- 
1024661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-bitseq
Version: 1.40.0+dfsg-1
Severity: critical
Tags: ftbfs
Justification: breaks unrelated software
X-Debbugs-Cc: 1023...@bugs.debian.org, debia...@lists.debian.org

As per upstream

   https://lists.debian.org/debian-r/2022/11/msg00058.html

r-bioc-bitseq is not supported any more.  It does not build against the
packages that are part of the BioC 3.16 release (namely r-bioc-rhtslib
which does not contain the header file bam.h any more)

Before we might remove r-bioc-bitseq finally from Debian we want to give
interested people a chance to fix the code but this bug should remove the
package from testing to not block the BioC 3.16 transition.

Kind regards

  Andreas.


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

Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 1.40.0+dfsg-1+rm

Dear submitter,

as the package r-bioc-bitseq has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

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

Bug#981670: marked as done (libmsdw-smtp-perl needs Breaks+Replaces: dkimproxy)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:28:02 +
with message-id 
and subject line Bug#1049341: Removed package(s) from unstable
has caused the Debian Bug report #981670,
regarding libmsdw-smtp-perl needs Breaks+Replaces: dkimproxy
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.)


-- 
981670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmsdw-smtp-perl
Version: 1.2-1.1
Severity: serious

See #979415 and #980718.
--- End Message ---
--- Begin Message ---
Version: 1.2-1.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#1050350: flycheck: keep flycheck out of testing until it finds an uploader

[David Bremner]

Source: flycheck
Severity: serious
Justification: Team decision
X-Debbugs-Cc: debian-emac...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Nobody has stepped up to take care of flycheck, and it currently
blocks the transition of emacs 29 to testing. 

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

Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmTmA08ACgkQA0U5G1Wq
FSFx4RAAug0/SVS+L2nFAKwRHgsqypfuSZ46JP+ayMV+O3yLc2vyZy6HOgt1Ew7c
Psfjt3s3ba2adbOZraPT0CAx2Dgz/0cKg2Rm4M6fMOCwYsqjwNSlPpE8rw0o0k5i
xPV5x+WKpoGWQB4sWW3QqDmZEdU3OY3szkpCKxDnR2Dk4rGRXBbI1utH4DOpdT8R
fCN6Qg+MWtimK+M33n/nklxvK8Ze7RLo2swy19rk/3ekJ3ZkwmXLmlVCRjEyt/bR
6uROHIX4HzK0La8JlU7gTgc77tZpC7uovbRQiMZOX8Waw0eIb9lqSMtKWJI8XgLG
v255LLb8qyaAbXBlq+D/ettUauAcJkEAWPSMuJ+WPkKuYotbyIXYBpELOa1f0EkF
/khUdCYob2Jak81cRURC7cY4JDWVa0qlLCWGYaKpTW4ACAajBrq1BSfAyrjFFuGS
XfBDj+0CSqtWo1ZR4Krpgg23xPFPWo07+TGhSAyqsbhmWfsHLqB9+kF930yZ/76+
cXI/zgFZ0pAXRzBIVxPCB7qN9AH+Zr8et4U2mn2Rc3PbpmZZflOw/spqOsXJe1XR
8i7+K3AkPtfeaGXqaDQI4y+uTi7Vq8tWwBwqDavThQtZH1kSfUfx5AiqNuvCnyUb
yLd/pDqgRr69GEo2YuS3T2HvK55hFtiDGZWjiSF1ddybcOtaT5s=
=tOrz
-END PGP SIGNATURE-

Bug#964964: marked as done (ruby-codemirror-rails: ftbfs with rails 6 in experimental and unmainatained.)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:21:42 +
with message-id 
and subject line Bug#1043593: Removed package(s) from unstable
has caused the Debian Bug report #964964,
regarding ruby-codemirror-rails: ftbfs with rails 6 in experimental and 
unmainatained.
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.)


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

Package: ruby-codemirror-rails
Version: 5.16.0-1
Severity: important
Control: forwarded -1 
https://github.com/fixlr/codemirror-rails/issues/61


User: pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: rails6-transition

Hi,

This package's autopkgtest failed with rails 6 currently in
experimental. rails 6 will be uploaded to unstable in 2 weeks, so
please make sure this package is ready for rails 6. The severity of
this bug will be raised to serious after rails 6 is uploaded to
unstable.

Relevant error

GEM_PATH= ruby2.7 -e gem\ \"codemirror-rails\"
/usr/lib/ruby/2.7.0/rubygems/dependency.rb:313:in `to_specs': Could not 
find 'railties' (< 6.0, >= 3.0) - did find: [railties-6.0.3.1] 
(Gem::MissingSpecVersionError)
Checked in 
'GEM_PATH=/home/debci/.gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0', 
execute `gem env` for more information
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1402:in `block in 
activate_dependencies'

from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in `each'
from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1391:in 
`activate_dependencies'

from /usr/lib/ruby/2.7.0/rubygems/specification.rb:1373:in `activate'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `block 
in gem'
from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'

from /usr/lib/ruby/2.7.0/rubygems/core_ext/kernel_gem.rb:68:in `gem'
from -e:1:in `'

But it seems to be unmaintained upstream 
https://github.com/fixlr/codemirror-rails/issues/61 so it is better to 
remove this package and use libjs-codemirror directly. Another option 
may be rails-assets.org, but that service seems unmaintained as well.


Full error log 
https://people.debian.org/~praveen/rails6-meta-build/autopkgtest/ruby-codemirror-rails.log
--- End Message ---
--- Begin Message ---
Version: 5.16.0-1+rm

Dear submitter,

as the package ruby-codemirror-rails has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

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

Bug#999717: marked as done (ruby-omniauth-jwt: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_de

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:23:29 +
with message-id 
and subject line Bug#1043596: Removed package(s) from unstable
has caused the Debian Bug report #999717,
regarding ruby-omniauth-jwt: FTBFS with ruby-omniauth 2.0.x: ERROR: Test 
"ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in 
`rescue in block in activate_dependencies': Could not find 'omniauth' (~> 1.1) 
among 68 total gem(s) (Gem::MissingSpecError)
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.)


-- 
999717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-omniauth-jwt
Version: 0.0.2-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-omniauth-2.0

Hi,

I would like to upload ruby-omniauth 2.0.4 to unstable soon. During a test
rebuild, ruby-omniauth-jwt was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-omniauth from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block 
> in activate_dependencies': Could not find 'omniauth' (~> 1.1) among 68 total 
> gem(s) (Gem::MissingSpecError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-jwt/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  at: 
> /<>/debian/ruby-omniauth-jwt/usr/share/rubygems-integration/all/specifications/omniauth-jwt-0.0.2.gemspec,
>  execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not 
> find 'omniauth' (~> 1.1) - did find: [omniauth-2.0.4] 
> (Gem::MissingSpecVersionError)
> Checked in 
> 'GEM_PATH=/<>/debian/ruby-omniauth-jwt/usr/share/rubygems-integration/all:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
>  , execute `gem env` for more information
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block 
> in activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in 
> `activate_dependencies'
>   from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in 
> `activate'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `block in gem'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `synchronize'
>   from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
> `gem'
>   from -e:1:in `'
> benchmark (default: 0.1.0)
> bigdecimal (default: 2.0.0)
> bundler (default: 2.1.4)
> cgi (default: 0.1.0)
> csv (default: 3.1.2)
> date (default: 3.0.0)
> dbm (default: 1.1.0)
> delegate (default: 0.1.0)
> did_you_mean (default: 1.4.0)
> diff-lcs (1.4.4)
> etc (default: 1.1.0)
> fcntl (default: 1.0.0)
> fiddle (default: 1.0.0)
> fileutils (default: 1.4.1)
> forwardable (default: 1.3.1)
> gdbm (default: 2.1.0)
> getoptlong (default: 0.1.0)
> hashie (3.5.5)
> io-console (default: 0.5.6)
> ipaddr (default: 1.2.2)
> irb (default: 1.2.6)
> json (default: 2.3.0)
> jwt (2.2.2)
> logger (default: 1.4.2)
> matrix (default: 0.2.0)
> minitest (5.13.0)
> mutex_m (default: 0.1.0)
> net-pop (default: 0.1.0)
> net-smtp (default: 0.1.0)
> net-telnet (0.1.1)
> observer (default: 0.1.0)
> omniauth (2.0.4)
> open3 (default: 0.1.0)
> openssl (default: 2.1.2)
> ostruct (default: 0.2.0)
> 

Bug#981878: marked as done (ruby-gitlab-pg-query downloads from the internet during the build)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:22:50 +
with message-id 
and subject line Bug#1043595: Removed package(s) from unstable
has caused the Debian Bug report #981878,
regarding ruby-gitlab-pg-query downloads from the internet during the build
to be marked as done.

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

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


-- 
981878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981878
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gitlab-pg-query
Version: 1.3.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ruby-gitlab-pg-query=amd64=1.3.1-2=1612462914=0

...
Building native extensions. This could take a while...
current directory: 
/<>/debian/ruby-gitlab-pg-query/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/gitlab-pg_query-1.3.1/ext/pg_query
["/usr/bin/ruby2.7", "-I", "/usr/lib/ruby/vendor_ruby", "-r", 
"./siteconf20210204-26550-1qve3p5.rb", "extconf.rb"]
ERROR:  Error installing /tmp/d20210204-26547-bcny2z/gitlab-pg_query-1.3.1.gem:
ERROR: Failed to build gem native extension.

current directory: 
/<>/debian/ruby-gitlab-pg-query/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/gitlab-pg_query-1.3.1/ext/pg_query
/usr/bin/ruby2.7 -I /usr/lib/ruby/vendor_ruby -r 
./siteconf20210204-26550-1qve3p5.rb extconf.rb
Building has failed. See above output for more information on the failure.
extconf failed, exit code 1

Gem files will remain installed in 
/<>/debian/ruby-gitlab-pg-query/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/gitlab-pg_query-1.3.1
 for inspection.
Results logged to 
/<>/debian/ruby-gitlab-pg-query/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/extensions/x86_64-linux/2.7.0/gitlab-pg_query-1.3.1/gem_make.out
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/$(RUBY_BASE_NAME)2.7
/usr/lib/ruby/2.7.0/net/http.rb:960:in `initialize': Failed to open TCP 
connection to codeload.github.com:443 (Network is unreachable - connect(2) for 
"codeload.github.com" port 443) (Errno::ENETUNREACH)
from /usr/lib/ruby/2.7.0/net/http.rb:960:in `open'
from /usr/lib/ruby/2.7.0/net/http.rb:960:in `block in connect'
from /usr/lib/ruby/2.7.0/timeout.rb:95:in `block in timeout'
from /usr/lib/ruby/2.7.0/timeout.rb:105:in `timeout'
from /usr/lib/ruby/2.7.0/net/http.rb:958:in `connect'
from /usr/lib/ruby/2.7.0/net/http.rb:943:in `do_start'
from /usr/lib/ruby/2.7.0/net/http.rb:932:in `start'
from /usr/lib/ruby/2.7.0/open-uri.rb:346:in `open_http'
from /usr/lib/ruby/2.7.0/open-uri.rb:764:in `buffer_open'
from /usr/lib/ruby/2.7.0/open-uri.rb:235:in `block in open_loop'
from /usr/lib/ruby/2.7.0/open-uri.rb:233:in `catch'
from /usr/lib/ruby/2.7.0/open-uri.rb:233:in `open_loop'
from /usr/lib/ruby/2.7.0/open-uri.rb:174:in `open_uri'
from /usr/lib/ruby/2.7.0/open-uri.rb:744:in `open'
from /usr/lib/ruby/2.7.0/open-uri.rb:50:in `open'
from extconf.rb:19:in `block in '
from extconf.rb:18:in `open'
from extconf.rb:18:in `'
/usr/lib/ruby/2.7.0/net/http.rb:960:in `initialize': Network is unreachable - 
connect(2) for "codeload.github.com" port 443 (Errno::ENETUNREACH)
from /usr/lib/ruby/2.7.0/net/http.rb:960:in `open'
from /usr/lib/ruby/2.7.0/net/http.rb:960:in `block in connect'
from /usr/lib/ruby/2.7.0/timeout.rb:95:in `block in timeout'
from /usr/lib/ruby/2.7.0/timeout.rb:105:in `timeout'
from /usr/lib/ruby/2.7.0/net/http.rb:958:in `connect'
from /usr/lib/ruby/2.7.0/net/http.rb:943:in `do_start'
from /usr/lib/ruby/2.7.0/net/http.rb:932:in `start'
from /usr/lib/ruby/2.7.0/open-uri.rb:346:in `open_http'
from /usr/lib/ruby/2.7.0/open-uri.rb:764:in `buffer_open'
from /usr/lib/ruby/2.7.0/open-uri.rb:235:in `block in open_loop'
from /usr/lib/ruby/2.7.0/open-uri.rb:233:in `catch'
from /usr/lib/ruby/2.7.0/open-uri.rb:233:in `open_loop'
from /usr/lib/ruby/2.7.0/open-uri.rb:174:in `open_uri'
from 

Bug#925269: marked as done (redmine-plugin-recaptcha: breaks configuration of redmine)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:22:18 +
with message-id 
and subject line Bug#1043594: Removed package(s) from unstable
has caused the Debian Bug report #925269,
regarding redmine-plugin-recaptcha: breaks configuration of redmine
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.)


-- 
925269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redmine-plugin-recaptcha
Version: 0.1.0+git20121018-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up redmine (4.0.1-1) ...
  dbconfig-common: writing config to 
/etc/dbconfig-common/redmine/instances/default.conf
  
  Creating config file /etc/dbconfig-common/redmine/instances/default.conf with 
new version
  
  Creating config file /etc/redmine/default/database.yml with new version
  creating database redmine_default: success.
  verifying database redmine_default exists: success.
  [ESC][33m`/var/www` is not a directory.
  Bundler will use `/tmp/bundler-20190316-93214-1wljkzi' as your home directory 
temporarily.
  [ESC][0mrake aborted!
  NoMethodError: undefined method `alias_method_chain' for 
Recaptcha::ClientHelper:Module
  Did you mean?  alias_method
  /usr/share/redmine/plugins/redmine_recaptcha/lib/client_helper_patch.rb:5:in 
`block in included'
  /usr/share/redmine/plugins/redmine_recaptcha/lib/client_helper_patch.rb:4:in 
`class_eval'
  /usr/share/redmine/plugins/redmine_recaptcha/lib/client_helper_patch.rb:4:in 
`included'
  /usr/share/redmine/plugins/redmine_recaptcha/init.rb:11:in `include'
  /usr/share/redmine/plugins/redmine_recaptcha/init.rb:11:in `block in '
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:426:in
 `instance_exec'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:426:in
 `block in make_lambda'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:198:in
 `block (2 levels) in halting'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:606:in
 `block (2 levels) in default_terminator'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:605:in
 `catch'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:605:in
 `block in default_terminator'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:199:in
 `block in halting'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:513:in
 `block in invoke_before'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:513:in
 `each'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:513:in
 `invoke_before'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/callbacks.rb:131:in
 `run_callbacks'
  
/usr/share/rubygems-integration/all/gems/activesupport-5.2.2/lib/active_support/reloader.rb:89:in
 `prepare!'
  
/usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application/finisher.rb:63:in
 `block in '
  
/usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:32:in
 `instance_exec'
  
/usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:32:in
 `run'
  
/usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:61:in
 `block in run_initializers'
  
/usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/initializable.rb:60:in
 `run_initializers'
  
/usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:361:in
 `initialize!'
  /usr/share/redmine/config/environment.rb:14:in `'
  
/usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:337:in
 `require'
  
/usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:337:in
 `require_environment!'
  
/usr/share/rubygems-integration/all/gems/railties-5.2.2/lib/rails/application.rb:520:in
 `block in run_tasks_blocks'
  Tasks: TOP => db:migrate => db:load_config => environment
  (See full trace by running task with --trace)
  dpkg: error processing package redmine 

Bug#830916: marked as done (ActionView::Template::Error (undefined method `recaptcha_tags` ...))

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:22:18 +
with message-id 
and subject line Bug#1043594: Removed package(s) from unstable
has caused the Debian Bug report #830916,
regarding ActionView::Template::Error (undefined method `recaptcha_tags` ...)
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.)


-- 
830916: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830916
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redmine-plugin-recaptcha
Version: 0.1.0+git20121018-3
Severity: serious

Dear Maintainer,

when testing your redmine plugin against the current redmine in
sid (3.2.3-1), I've found that redmine aborts with an internal error when
clicking on the "Register" link. From production.log:

  Started GET "/account/register" for 192.168.234.1 at 2016-07-13 00:37:27 +0200
  Processing by AccountController#register as HTML
Current user: anonymous
Rendered plugins/redmine_recaptcha/app/views/account/register.html.erb 
within layouts/base (775.4ms)
  Completed 500 Internal Server Error in 782ms (ActiveRecord: 0.9ms)
  
  ActionView::Template::Error (undefined method `recaptcha_tags' for 
#<#:0x007f1f95b5d6f8>):
  40: 
  41: 
  42: 
  43: <%= recaptcha_tags :public_key => 
Setting.plugin_redmine_recaptcha['recaptcha_public_key'], :ssl => true %>
  44:  
  45: <%= submit_tag l(:button_submit) %>
  46: <% end %>
plugins/redmine_recaptcha/app/views/account/register.html.erb:43:in `block 
in 
_plugins_redmine_recaptcha_app_views_account_register_html_erb__732500603993694831_69886816182180'
plugins/redmine_recaptcha/app/views/account/register.html.erb:3:in 
`_plugins_redmine_recaptcha_app_views_account_register_html_erb__732500603993694831_69886816182180'
lib/redmine/sudo_mode.rb:63:in `sudo_mode'


-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-
--- End Message ---
--- Begin Message ---
Version: 0.1.0+git20121018-4+rm

Dear submitter,

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

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

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

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

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

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

Bug#985880: marked as done (ruby-flot-rails: broken symlinks: /usr/share/ruby-flot-rails/vendor/assets/javascripts/jquery.flot.canvas.* -> ../../../../javascript/jquery-flot/jquery.flot.canvas.*)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:20:44 +
with message-id 
and subject line Bug#1043590: Removed package(s) from unstable
has caused the Debian Bug report #985880,
regarding ruby-flot-rails: broken symlinks: 
/usr/share/ruby-flot-rails/vendor/assets/javascripts/jquery.flot.canvas.* -> 
../../../../javascript/jquery-flot/jquery.flot.canvas.*
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.)


-- 
985880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-flot-rails
Version: 0.0.7-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m30.1s ERROR: FAIL: Broken symlinks:
  
/usr/share/ruby-flot-rails/vendor/assets/javascripts/jquery.flot.canvas.min.js 
-> ../../../../javascript/jquery-flot/jquery.flot.canvas.min.js 
(ruby-flot-rails)
  /usr/share/ruby-flot-rails/vendor/assets/javascripts/jquery.flot.canvas.js -> 
../../../../javascript/jquery-flot/jquery.flot.canvas.js (ruby-flot-rails)

jquery.flot.canvas.* is no longer part of libjs-jquery-flot


cheers,

Andreas


ruby-flot-rails_0.0.7-1.1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.0.7-1.1+rm

Dear submitter,

as the package ruby-flot-rails has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

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

Bug#1002118: marked as done (ruby-heroku-deflater: FTBFS: ERROR: Test "ruby2.7" failed: NoMethodError: undefined method `match?' for #)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:21:11 +
with message-id 
and subject line Bug#1043592: Removed package(s) from unstable
has caused the Debian Bug report #1002118,
regarding ruby-heroku-deflater: FTBFS: ERROR: Test "ruby2.7" failed: 
NoMethodError: undefined method `match?' for 
#
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.)


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

Hi,

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


Relevant part (hopefully):
>   NoMethodError:
> undefined method `match?' for 
> #
>   Shared Example Group: "ServeZippedAssets" called from 
> ./spec/serve_zipped_assets_spec.rb:78
>   # ./lib/heroku-deflater/serve_zipped_assets.rb:31:in `call'
>   # ./spec/serve_zipped_assets_spec.rb:10:in `process'
>   # ./spec/serve_zipped_assets_spec.rb:55:in `block (3 levels) in  (required)>'
> 
> Finished in 0.01154 seconds (files took 0.28592 seconds to load)
> 24 examples, 12 failures
> 
> Failed examples:
> 
> rspec './spec/serve_zipped_assets_spec.rb[1:1:1:2]' # 
> HerokuDeflater::ServeZippedAssets Rais 4.x behaves like ServeZippedAssets 
> handles the pre-gzipped assets
> rspec './spec/serve_zipped_assets_spec.rb[1:1:1:3]' # 
> HerokuDeflater::ServeZippedAssets Rais 4.x behaves like ServeZippedAssets has 
> correct content type
> rspec './spec/serve_zipped_assets_spec.rb[1:1:1:4]' # 
> HerokuDeflater::ServeZippedAssets Rais 4.x behaves like ServeZippedAssets has 
> correct content encoding
> rspec './spec/serve_zipped_assets_spec.rb[1:1:1:5]' # 
> HerokuDeflater::ServeZippedAssets Rais 4.x behaves like ServeZippedAssets has 
> correct content length
> rspec './spec/serve_zipped_assets_spec.rb[1:1:1:6]' # 
> HerokuDeflater::ServeZippedAssets Rais 4.x behaves like ServeZippedAssets has 
> correct cache control
> rspec './spec/serve_zipped_assets_spec.rb[1:1:1:7]' # 
> HerokuDeflater::ServeZippedAssets Rais 4.x behaves like ServeZippedAssets 
> does not serve non-gzipped assets
> rspec './spec/serve_zipped_assets_spec.rb[1:2:1:2]' # 
> HerokuDeflater::ServeZippedAssets Rais 5.x behaves like ServeZippedAssets 
> handles the pre-gzipped assets
> rspec './spec/serve_zipped_assets_spec.rb[1:2:1:3]' # 
> HerokuDeflater::ServeZippedAssets Rais 5.x behaves like ServeZippedAssets has 
> correct content type
> rspec './spec/serve_zipped_assets_spec.rb[1:2:1:4]' # 
> HerokuDeflater::ServeZippedAssets Rais 5.x behaves like ServeZippedAssets has 
> correct content encoding
> rspec './spec/serve_zipped_assets_spec.rb[1:2:1:5]' # 
> HerokuDeflater::ServeZippedAssets Rais 5.x behaves like ServeZippedAssets has 
> correct content length
> rspec './spec/serve_zipped_assets_spec.rb[1:2:1:6]' # 
> HerokuDeflater::ServeZippedAssets Rais 5.x behaves like ServeZippedAssets has 
> correct cache control
> rspec './spec/serve_zipped_assets_spec.rb[1:2:1:7]' # 
> HerokuDeflater::ServeZippedAssets Rais 5.x behaves like ServeZippedAssets 
> does not serve non-gzipped assets
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> ERROR: Test "ruby2.7" failed: 


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/ruby-heroku-deflater_0.6.3-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 0.6.3-2+rm

Dear submitter,

as the package ruby-heroku-deflater has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

The version of this package that was in Debian prior 

Bug#1019671: marked as done (ruby-test-spec: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:18:19 +
with message-id 
and subject line Bug#1043569: Removed package(s) from unstable
has caused the Debian Bug report #1019671,
regarding ruby-test-spec: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.
to be marked as done.

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

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


-- 
1019671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-test-spec
Version: 0.10.0-3.1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-test-spec with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-test-files.yaml  
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby:. 
> GEM_PATH=/<>/debian/ruby-test-spec/usr/share/rubygems-integration/all:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ 
> \{\ \|f\|\ require\ f\ \}
> /<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby/test/spec.rb:506:
>  [BUG] the cvc table should be set
> ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu]
> 
> -- Control frame information ---
> c:0012 p:0042 s:0077 e:76 METHOD 
> /<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby/test/spec.rb:506
> c:0011 p:0011 s:0070 e:69 METHOD 
> /<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby/test/spec.rb:522
>  [FINISH]
> c:0010 p: s:0064 e:63 CFUNC  :new
> c:0009 p:0075 s:0057 e:53 METHOD 
> /<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby/test/spec.rb:650
> c:0008 p:0047 s:0046 e:45 METHOD 
> /<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby/test/spec.rb:654
> c:0007 p:0027 s:0039 E:0024a0 TOP
> /<>/test/spec_new_style.rb:78 [FINISH]
> c:0006 p: s:0036 e:35 CFUNC  :require
> c:0005 p:0194 s:0031 e:30 METHOD 
> :85
> c:0004 p:0005 s:0014 e:13 BLOCK  -e:1 [FINISH]
> c:0003 p: s:0010 e:09 CFUNC  :each
> c:0002 p:0016 s:0006 e:05 EVAL   -e:1 [FINISH]
> c:0001 p: s:0003 E:000550 (none) [FINISH]
> 
> -- Ruby level backtrace information 
> -e:1:in `'
> -e:1:in `each'
> -e:1:in `block in '
> :85:in
>  `require'
> :85:in
>  `require'
> /<>/test/spec_new_style.rb:78:in `'
> /<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby/test/spec.rb:654:in
>  `xcontext'
> /<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby/test/spec.rb:650:in
>  `context'
> /<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby/test/spec.rb:650:in
>  `new'
> /<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby/test/spec.rb:522:in
>  `initialize'
> /<>/debian/ruby-test-spec/usr/lib/ruby/vendor_ruby/test/spec.rb:506:in
>  `initialize'
> 
> -- C level backtrace information ---
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(0x7f954ebfd152) [0x7f954ebfd152]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(0x7f954ea4b1d3) [0x7f954ea4b1d3]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(rb_bug+0x99) [0x7f954e9d2992]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(0x7f954e9d441c) [0x7f954e9d441c]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(0x7f954ebe7f1a) [0x7f954ebe7f1a]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(rb_vm_exec+0xb3) [0x7f954ebeb723]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(0x7f954ebf264d) [0x7f954ebf264d]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(rb_funcallv_kw+0x52) 
> [0x7f954ebf31a2]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(rb_class_new_instance_pass_kw+0x36)
>  [0x7f954eaeecb6]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(0x7f954ebe1b40) [0x7f954ebe1b40]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(0x7f954ebe443b) [0x7f954ebe443b]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(0x7f954ebe724e) [0x7f954ebe724e]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(rb_vm_exec+0xb3) [0x7f954ebeb723]
> /usr/lib/x86_64-linux-gnu/libruby-3.1.so.3.1(0x7f954eaa3e92) [0x7f954eaa3e92]
> 

Bug#1026893: marked as done (ruby-haml-contrib: FTBFS: ERROR: Test "ruby3.1" failed: /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:8:in `': Filter

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:19:06 +
with message-id 
and subject line Bug#1043570: Removed package(s) from unstable
has caused the Debian Bug report #1026893,
regarding ruby-haml-contrib: FTBFS: ERROR: Test "ruby3.1" failed: 
/<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:8:in
 `': Filters is not a module (TypeError)
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.)


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

Hi,

After updaring ruby-haml to 6.6.1, ruby-haml-contrib fails to build with
a test failure.

Relevant part (hopefully):
> /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:8:in
>  `': Filters is not a module (TypeError)
> /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/haml-6.1.1/lib/haml/filters/base.rb:5:
>  previous definition of Filters was here
>   from 
> /<>/debian/ruby-haml-contrib/usr/lib/ruby/vendor_ruby/haml/filters/php.rb:7:in
>  `'
>   from 
> :85:in
>  `require'
>   from 
> :85:in
>  `require'
>   from /<>/test/php_filter_test.rb:2:in `'
>   from 
> :85:in
>  `require'
>   from 
> :85:in
>  `require'
>   from debian/ruby-tests.rb:2:in `block in '
>   from debian/ruby-tests.rb:2:in `each'
>   from debian/ruby-tests.rb:2:in `'
> ERROR: Test "ruby3.1" failed: 

Attached is the full build log.


ruby-haml-contrib.log.gz
Description: application/gzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.0.0.1-2.1+rm

Dear submitter,

as the package ruby-haml-contrib has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

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

Bug#1019670: marked as done (ruby-sprite-factory: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError: no image files found)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:20:10 +
with message-id 
and subject line Bug#1043588: Removed package(s) from unstable
has caused the Debian Bug report #1019670,
regarding ruby-sprite-factory: FTBFS with ruby3.1: ERROR: Test "ruby3.1" 
failed: RuntimeError: no image files found
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.)


-- 
1019670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sprite-factory
Version: 1.7.1-4
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-sprite-factory with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
> RuntimeError: no image files found
> 
> /<>/debian/ruby-sprite-factory/usr/lib/ruby/vendor_ruby/sprite_factory/runner.rb:41:in
>  `run!'
> 
> /<>/debian/ruby-sprite-factory/usr/lib/ruby/vendor_ruby/sprite_factory.rb:14:in
>  `run!'
> /<>/test/integration_test.rb:185:in `block in 
> test_generate_sprite_with_nocss'
> /<>/test/test_case.rb:67:in `with_clean_output'
> /<>/test/integration_test.rb:180:in 
> `test_generate_sprite_with_nocss'
> 
>  18) Failure:
> SpriteFactory::RunnerTest#test_images_are_filtered_correctly 
> [/<>/test/runner_test.rb:225]:
> Expected: [nil, nil, nil]
>   Actual: []
> 
>  19) Failure:
> SpriteFactory::RunnerTest#test_invalid_config 
> [/<>/test/runner_test.rb:172]:
> Expected /no\ output\ file\ specified/ to match "no image files found".
> 
> 50 runs, 186 assertions, 6 failures, 13 errors, 0 skips
> rake aborted!
> Command failed with status (1): [ruby -w 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "test/integration_test.rb" "test/library_test.rb" "test/runner_test.rb" 
> "test/style_test.rb" -v]
> 
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-sprite-factory/ruby-sprite-factory_1.7.1-4+rebuild1663008231_amd64-2022-09-12T18:43:52Z.build

To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on
when you try this, it might mean installing ruby-all-dev from experimental, or
if the transition has already started, a normal build on unstable will be
enough.  If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.7.1-4+rm

Dear submitter,

as the package ruby-sprite-factory has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

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

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

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

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

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

Bug#1019665: marked as done (ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 15:19:39 +
with message-id 
and subject line Bug#1043574: Removed package(s) from unstable
has caused the Debian Bug report #1019665,
regarding ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: 
  ArgumentError:
to be marked as done.

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

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


-- 
1019665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-safe-yaml
Version: 1.0.5-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-safe-yaml with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>   ArgumentError:
> wrong number of arguments (given 2, expected 1)
>   # ./lib/safe_yaml/load.rb:149:in `load'
>   # ./lib/safe_yaml.rb:29:in `safe_load'
>   # ./spec/safe_yaml_spec.rb:7:in `safe_load_round_trip'
>   # ./spec/safe_yaml_spec.rb:745:in `block (4 levels) in '
> 
> Finished in 0.08109 seconds (files took 0.12613 seconds to load)
> 134 examples, 20 failures
> 
> Failed examples:
> 
> rspec ./spec/safe_yaml_spec.rb:29 # Psych unsafe_load allows exploits through 
> objects defined in YAML w/ !ruby/hash via custom :[]= methods
> rspec ./spec/safe_yaml_spec.rb:34 # Psych unsafe_load allows exploits through 
> objects defined in YAML w/ !ruby/object via the :init_with method
> rspec ./spec/safe_yaml_spec.rb:40 # Psych unsafe_load allows exploits through 
> objects w/ sensitive instance variables defined in YAML w/ !ruby/object
> rspec ./spec/safe_yaml_spec.rb:50 # Psych unsafe_load with special 
> whitelisted tags defined effectively ignores the whitelist (since everything 
> is whitelisted)
> rspec ./spec/safe_yaml_spec.rb:318 # Psych safe_load with special whitelisted 
> tags defined will allow objects to be deserialized for whitelisted tags
> rspec ./spec/safe_yaml_spec.rb:330 # Psych safe_load with special whitelisted 
> tags defined will not deserialize objects without whitelisted tags
> rspec ./spec/safe_yaml_spec.rb:336 # Psych safe_load with special whitelisted 
> tags defined will not allow non-whitelisted objects to be embedded within 
> objects with whitelisted tags
> rspec ./spec/safe_yaml_spec.rb:378 # Psych safe_load with special whitelisted 
> tags defined with the :raise_on_unknown_tag option enabled does not raise an 
> exception as long as all tags are whitelisted
> rspec ./spec/safe_yaml_spec.rb:404 # Psych safe_load with special whitelisted 
> tags defined with the :raise_on_unknown_tag option enabled does not raise an 
> exception on the non-specific '!' tag
> rspec ./spec/safe_yaml_spec.rb:421 # Psych safe_load with special whitelisted 
> tags defined with the :raise_on_unknown_tag option enabled with whitelisted 
> custom class does not raise an exception on the non-specific '!' tag
> rspec ./spec/safe_yaml_spec.rb:464 # Psych safe_load when options are passed 
> direclty to #load which differ from the defaults (or, for example, when 
> certain tags are whitelisted) goes with the default option when it is not 
> overridden
> rspec ./spec/safe_yaml_spec.rb:497 # Psych unsafe_load_file allows exploits 
> through objects defined in YAML w/ !ruby/hash via custom :[]= methods
> rspec ./spec/safe_yaml_spec.rb:504 # Psych unsafe_load_file allows exploits 
> through objects defined in YAML w/ !ruby/object via the :init_with method
> rspec ./spec/safe_yaml_spec.rb:510 # Psych unsafe_load_file allows exploits 
> through objects w/ sensitive instance variables defined in YAML w/ 
> !ruby/object
> rspec ./spec/safe_yaml_spec.rb:550 # Psych load as long as a :default_mode 
> has been specified doesn't issue a warning for unsafe mode, since an explicit 
> mode has been set
> rspec ./spec/safe_yaml_spec.rb:708 # Psych whitelist! with a Class as its 
> argument successfully deserializes the specified class
> rspec ./spec/safe_yaml_spec.rb:719 # Psych whitelist! with a Class as its 
> argument works for ranges
> rspec ./spec/safe_yaml_spec.rb:724 # Psych whitelist! with a Class as its 
> argument works for regular expressions
> rspec ./spec/safe_yaml_spec.rb:729 # Psych whitelist! with a Class as its 
> argument works for multiple classes
> rspec ./spec/safe_yaml_spec.rb:734 # Psych whitelist! with a Class as its 
> argument works for arbitrary Exception subclasses
> 
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:

Bug#1042183: marked as done (ruby-kramdown-parser-gfm: FTBFS: ERROR: Test "ruby3.1" failed.)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 14:36:31 +
with message-id 
and subject line Bug#1042183: fixed in ruby-kramdown-parser-gfm 1.1.0-3
has caused the Debian Bug report #1042183,
regarding ruby-kramdown-parser-gfm: FTBFS: ERROR: Test "ruby3.1" failed.
to be marked as done.

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

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


-- 
1042183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-kramdown-parser-gfm
Version: 1.1.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.1  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-kramdown-parser-gfm/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -e gem\ \"kramdown-parser-gfm\"
> 
> ┌──┐
> │ Run tests for ruby3.1 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=. 
> GEM_PATH=/<>/debian/ruby-kramdown-parser-gfm/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0
>  ruby3.1 -S rake -f debian/ruby-tests.rake
> /usr/bin/ruby3.1 -w -I"test" 
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
> "test/test_files.rb"  -v
> /<>/test/test_files.rb:16: warning: setting 
> Encoding.default_external
> Run options: -v --seed 63952
> 
> # Running:
> 
> TestFiles#test_gfm_hard_line_breaks_to_html = 0.01 s = .
> TestFiles#test_gfm_task_list_to_html = 
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/ada.rb:158:
>  warning: character class has duplicated range: 
> /\b(\p{Pc}|[[alpha]])\p{Word}*/
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/clean.rb:82:
>  warning: character class has duplicated range: /_*[a-z][\w_`]*/
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/clean.rb:90:
>  warning: character class has duplicated range: /_*[A-Z][\w_`]*/
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/clean.rb:98:
>  warning: character class has duplicated range: /[^\w_\s`]/
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/clean.rb:139:
>  warning: character class has duplicated range: /[\w_]+/
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/c.rb:18:
>  warning: method redefined; discarding old keywords
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/c.rb:18:
>  warning: previous definition of keywords was here
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/c.rb:29:
>  warning: method redefined; discarding old keywords_type
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/c.rb:29:
>  warning: previous definition of keywords_type was here
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/c.rb:50:
>  warning: method redefined; discarding old reserved
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/c.rb:50:
>  warning: previous definition of reserved was here
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/c.rb:59:
>  warning: method redefined; discarding old builtins
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/c.rb:59:
>  warning: previous definition of builtins was here
> /usr/share/rubygems-integration/all/gems/rouge-4.1.2/lib/rouge/lexers/cpp.rb:23:
>  warning: method redefined; discarding old keywords
> 

Processed: notfound 1042183 in 1.1.0-3~exp1

[Debian Bug Tracking System]

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

> notfound 1042183 1.1.0-3~exp1
Bug #1042183 [src:ruby-kramdown-parser-gfm] ruby-kramdown-parser-gfm: FTBFS: 
ERROR: Test "ruby3.1" failed.
Ignoring request to alter found versions of bug #1042183 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#891197: ncbi-blast+ is marked for autoremoval from testing

[Aaron M. Ucko]

Andreas Tille  writes:

> On Mon, 21 Aug 2023 15:33:03 GMT this bug was set serious with the consequence
> that this package and all its dependencies are creating a lot of noise about
> testing removals. 

So I saw; sorry for the resulting noise.

> It would be really great if you could explain upstream the situation and
> we could fix this bug in the next couple of weeks.

I've been working on landing PCRE2 support upstream.  It wound up taking
longer than I'd initially anticipated because even though all usage is
via a wrapper, it's common to want to know where matches actually start
and end, and the relevant data type changed with PCRE2.  (The wrapper is
belatedly gaining a typedef abstracting this change away, but various
call sites maintained by different subteams still need formal updating.)

For the time being, we can switch to an embedded copy of classic PCRE by
dropping the build dependency on libpcre3-dev; that's of course not a
proper fix, but should at least let us downgrade this bug's severity.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Processed: found 1050300 in 33.0.3-2

[Debian Bug Tracking System]

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

> found 1050300 33.0.3-2
Bug #1050300 [mkbootimg] mkbootimg package missing gki module
There is no source info for the package 'mkbootimg' at version '33.0.3-2' with 
architecture ''
Unable to make a source version for version '33.0.3-2'
Marked as found in versions 33.0.3-2.
> thanks
Stopping processing here.

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

Processed: found 1050300 in 33.0.1-1~exp1

[Debian Bug Tracking System]

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

> found 1050300 33.0.1-1~exp1
Bug #1050300 [mkbootimg] mkbootimg package missing gki module
There is no source info for the package 'mkbootimg' at version '33.0.1-1~exp1' 
with architecture ''
Unable to make a source version for version '33.0.1-1~exp1'
Marked as found in versions 33.0.1-1~exp1.
> thanks
Stopping processing here.

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

Bug#1025568: marked as done (gparted: dependency on transitional policykit-1 package)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 12:20:57 +
with message-id 
and subject line Bug#1025568: fixed in gparted 1.3.1-1.1
has caused the Debian Bug report #1025568,
regarding gparted: dependency on transitional policykit-1 package
to be marked as done.

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

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


-- 
1025568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gparted
Version: 1.3.1-1
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1
Control: block 1025540 by -1

This package has a Depends and Build-Depends on the transitional
package policykit-1, which has been separated into polkitd, pkexec and
(deprecated) polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

If this package requires polkit at build-time (usually for the gettext
extensions polkit.its and polkit.loc), please build-depend on both
libpolkit-gobject-1-dev and polkitd, even if the package does not
actually depend on libpolkit-gobject-1 at runtime. This is because
the gettext extensions are currently in polkitd, but might be moved to
libpolkit-gobject-1-dev in future (see #955204). pkexec is usually not
required at build-time.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gparted
Source-Version: 1.3.1-1.1
Done: Hugh McMaster 

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

Debian distribution maintenance software
pp.
Hugh McMaster  (supplier of updated gparted package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Aug 2023 21:32:58 +1000
Source: gparted
Architecture: source
Version: 1.3.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Phillip Susi 
Changed-By: Hugh McMaster 
Closes: 1025568
Changes:
 gparted (1.3.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/control: Replace policykit-1 with pkexec (Closes: #1025568).
Checksums-Sha1:
 c0f3fe07b6105461518efad11338123dbfb1ac15 2242 gparted_1.3.1-1.1.dsc
 9068391ff13855abfc83d54c042a1a4b0d2ed57f 14908 gparted_1.3.1-1.1.debian.tar.xz
 0bed59d1cd03b8e7b059e62f66ef4ae13d00c5de 16326 
gparted_1.3.1-1.1_amd64.buildinfo
Checksums-Sha256:
 f94309ecfcab82a05b8fcb85a80f5ac1e820b4e3fe91572304a5620b0126acc3 2242 
gparted_1.3.1-1.1.dsc
 f785ecdb6fdf41d9853bdc276358fae166bb4da6734fa769e1c377ba3d6bccbf 14908 
gparted_1.3.1-1.1.debian.tar.xz
 6a52f5cad2ef3175424be4445ed44c9146cef6d2515c01ff5e20a1d0d9db5e73 16326 
gparted_1.3.1-1.1_amd64.buildinfo
Files:
 6313a59f98b803a26f770a7765ce3f4f 2242 gnome optional gparted_1.3.1-1.1.dsc
 77ef8b58f1295ef2815ee0dc520caa23 14908 gnome optional 
gparted_1.3.1-1.1.debian.tar.xz
 5c1594ac0324b054e47f84932ab6e748 16326 gnome optional 
gparted_1.3.1-1.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEOiCBPKV5RoaMUVIRWsYQdMXoG8QFAmTjTd0PHGhtY0BkZWJp
YW4ub3JnAAoJEFrGEHTF6BvE8GkP/RzCvnl2Oragw6frUkoZGUG13pRIGYdML9/8
+EzmQXM6+9MWJPkx/0iszjLjc6pBOe9AA4fthgLPo8SHuIsQONqiseuN+uxFnjkM
L4Ab+TJ53Y7u9XAWfKQX5/t1QdRppEn5kCLnBvn6hwm8b0XFCJaWgadqBwxeXDIa
3o5Bn6l7ZOjwOxA0PP1V8e6oNlDFxM44+I1FphkAPSgnPhreuAd0X6w/tTqdL8UH
YmbHCzroeEKTKOcaFHsH6h3fH4dWCAmd+pxOSF+Zuyof4SSAdsieY2QzQGlghZ/m
ncx0bB2715XiZyUzO9HG7xmhQkSCLgHKHN2xF1Cwdez0ycTOUjKp2mRTG/eR28a+
lchsFciVh4S8SnlLSKfsxRCTpXWOquhUEMRY9yOhRa8UxrrDxAjAMxt3V0xnecAh
CjjhlNKYzLJ3T+fh1IsUPiYZ/rpMIsUtLwiG2mt4K2NzHwtcwyHGgiVNDwbfXZsy
nCymJ549cOs0UUj0h68egrRmJ00tDPZ8Kdd50QiFnNgWuIMJd+Wxdz9V1XGK3RPP

Bug#1050240: marked as done (libqt5location5: Tiles not loading)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 12:07:22 +
with message-id 
and subject line Bug#1050240: fixed in qtlocation-opensource-src 5.15.10+dfsg-3
has caused the Debian Bug report #1050240,
regarding libqt5location5: Tiles not loading
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.)


-- 
1050240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5location5
Version: 5.15.8+dfsg-3
Severity: grave
Tags: bookworm
Justification: renders package unusable
X-Debbugs-Cc: raym...@orphiction.nl

Dear Maintainer,

Tiles are not loaded by qtlocation without this change.

The maintainer already showed that is fix is possible using unstable. A similar
fix is created for bookworm and now tiles are loaded as expected.


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

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

Versions of packages libqt5location5 depends on:
ii  libc6  2.36-9+deb12u1
ii  libgcc-s1  12.2.0-14
ii  libqt5core5a [qtbase-abi-5-15-8]   5.15.8+dfsg-11
ii  libqt5gui5 5.15.8+dfsg-11
ii  libqt5positioning5 5.15.8+dfsg-3
ii  libqt5positioningquick55.15.8+dfsg-3
ii  libqt5qml5 [qtdeclarative-abi-5-15-8]  5.15.8+dfsg-3
ii  libqt5qmlmodels5   5.15.8+dfsg-3
ii  libqt5quick5-gles  5.15.8+dfsg-1
ii  libstdc++6 12.2.0-14

libqt5location5 recommends no packages.

libqt5location5 suggests no packages.

-- no debconf information
Index: 
qtlocation-everywhere-src-5.15.8/src/location/labs/qsg/qgeomapobjectqsgsupport.cpp
===
--- 
qtlocation-everywhere-src-5.15.8.orig/src/location/labs/qsg/qgeomapobjectqsgsupport.cpp
 2022-11-10 21:42:35.0 +0100
+++ 
qtlocation-everywhere-src-5.15.8/src/location/labs/qsg/qgeomapobjectqsgsupport.cpp
  2023-08-22 12:03:25.950516809 +0200
@@ -158,7 +158,7 @@
 if (!root)
 return;
 
-if (m_mapObjectsRootNode && m_mapObjectsRootNode->parent())
+if (m_mapObjectsRootNode && !m_mapObjectsRootNode->parent())
 root->appendChildNode(m_mapObjectsRootNode.get());
 
 if (!m_mapObjectsRootNode) {
--- End Message ---
--- Begin Message ---
Source: qtlocation-opensource-src
Source-Version: 5.15.10+dfsg-3
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated 
qtlocation-opensource-src 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, 23 Aug 2023 14:25:47 +0300
Source: qtlocation-opensource-src
Architecture: source
Version: 5.15.10+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Closes: 1048265 1050240
Changes:
 qtlocation-opensource-src (5.15.10+dfsg-3) unstable; urgency=medium
 .
   * Backport upstream patch to fix condition for appendChildNode() call
 (closes: #1050240).
   * Update debian/libqt5location5.symbols from buildds’ logs.
   * Add debian/clean file (closes: #1048265).
Checksums-Sha1:
 c1d562fdf39ca369ff9ad84628d52fe37eaa8fb5 3898 
qtlocation-opensource-src_5.15.10+dfsg-3.dsc
 4361020f151255d084219cdf9a8807385c03f02f 24260 
qtlocation-opensource-src_5.15.10+dfsg-3.debian.tar.xz
 14703c1ac4d23d44a970122c135e46052ee0273f 12484 
qtlocation-opensource-src_5.15.10+dfsg-3_source.buildinfo
Checksums-Sha256:
 6973b89c787009e88110983944b52cbba550173caa2040d534b1600d857f2514 3898 
qtlocation-opensource-src_5.15.10+dfsg-3.dsc
 

Bug#1050336: libnet-xmpp-perl: unable to StartTLS, without any feedback

[Cyril Brulebois]

Package: libnet-xmpp-perl
Version: 1.05-1.1
Severity: serious
Justification: cannot perform basic authentication

Hi,

I have a few scripts around that use Net::XMPP to send notifications
when this or that happens, and all of them broke after upgrading from
bullseye to bookworm. This is definitely not related to changes on the
server side (which I control and didn't change), and other existing
hosts still on bullseye still work fine.

The error manifests itself like this:

AuthIQAuth requires a resource arguement at /local/wrapper.pm line 42.

Tracking it down, it appears AuthSend uses AuthSASL on bullseye (OK)
and AuthIQAuth on bookworm (KO). The latter is the fallback:

,---[ Net/XMPP/Protocol.pm ]---
| sub AuthSend
| {
[…]
| if($self->{STREAM}->GetStreamFeature($self->GetStreamID(),"xmpp-sasl"))
| {
| return $self->AuthSASL(%args);
| }
| return $self->AuthIQAuth(%args);
| }
`---

The GetStreamID isn't happy because it tries to pick the ID part of the
SESSION, which is missing.

Diving into the connection implementation, I managed to confirm that the
connection is established at first, giving me a $self->{SESSION} set,
but that goes away later on:

,---[ Net/XMPP/Connection.pm ]---
| sub Connect
| {   
| if ($self->{SESSION})
| {
| $self->{DEBUG}->Log1("Connect: connection made");
| 
| my $weak = $self;
| weaken $weak;
| $self->{STREAM}->SetCallBacks(node=>sub{ $weak->CallBack(@_) });
| $self->{CONNECTED} = 1;
| $self->{RECONNECTING} = 0;
| 
| if (exists($self->{SESSION}->{version}) &&
| ($self->{SESSION}->{version} ne ""))
| {
| my $tls = $self->GetStreamFeature("xmpp-tls");
| if (defined($tls) && $self->{SERVER}->{tls})
| {
| $self->{SESSION} =
| $self->{STREAM}->StartTLS(
| $self->{SESSION}->{id},
| $self->{SERVER}->{timeout},
| );

Here be dragons.

| }
| elsif (defined($tls) && ($tls eq "required"))
| {
| $self->SetErrorCode("The server requires us to use TLS, but 
you did not specify that\nTLS was an option.");
| return;
| }
| }
| 
| return 1;
| }
| else
| {
| $self->SetErrorCode($self->{STREAM}->GetErrorCode());
| return;
| }
`---

I also confirmed (yay for print-debugging) that the xmpp-tls branch is
entered, the StartTLS() fails for some reason (or at least returns
nothing at all), and $self->{SESSION} gets reset. The rest explodes.


There are only minor differences between the package in bullseye and
bookworm (mostly packaging metadata), so it looks to me something
external (undetermined at the moment) triggered this problem during
the upgrade. I thought I'd file my findings then think a little more
about a game plan.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Bug#1042983: marked as done (squeekboard - rust gtk stack update.)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 11:20:17 +
with message-id 
and subject line Bug#1042983: fixed in squeekboard 1.22.0-4
has caused the Debian Bug report #1042983,
regarding squeekboard - rust gtk stack update.
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.)


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

Package: squeekboard
Version: 1.22.0-3
Severity: serious

The rust gtk stack is currently being updated in Debian,
squeekboard needs a small patch

Please test that squeekboard works with this patch and
if-so apply it.diff -Nru squeekboard-1.22.0/debian/changelog 
squeekboard-1.22.0/debian/changelog
--- squeekboard-1.22.0/debian/changelog 2023-07-01 15:14:45.0 +
+++ squeekboard-1.22.0/debian/changelog 2023-08-03 16:41:53.0 +
@@ -1,3 +1,10 @@
+squeekboard (1.22.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update for gtk-rs 0.17.
+
+ -- Peter Michael Green   Thu, 03 Aug 2023 16:41:53 +
+
 squeekboard (1.22.0-3) unstable; urgency=medium
 
   * debian: update build dependencies.
diff -Nru squeekboard-1.22.0/debian/control squeekboard-1.22.0/debian/control
--- squeekboard-1.22.0/debian/control   2023-07-01 15:14:45.0 +
+++ squeekboard-1.22.0/debian/control   2023-08-03 16:39:01.0 +
@@ -17,11 +17,11 @@
  librust-aho-corasick-dev,
  librust-bitflags-1-dev (>= 1.0),
  librust-clap-4+std-dev (>= 4.0),
- librust-gio+v2-58-dev (>= 0.16),
- librust-glib+v2-58-dev (>= 0.16),
- librust-glib-sys-dev (>= 0.16),
- librust-gtk+v3-24-dev (>= 0.16),
- librust-gtk-sys-dev (>= 0.16),
+ librust-gio+v2-58-dev (>= 0.17),
+ librust-glib+v2-58-dev (>= 0.17),
+ librust-glib-sys-dev (>= 0.17),
+ librust-gtk+v3-24-dev (>= 0.17),
+ librust-gtk-sys-dev (>= 0.17),
  librust-maplit-1-dev (>= 1.0),
  librust-serde-derive-1-dev (>= 1.0),
  librust-serde-yaml-0.8-dev (>= 0.8),
diff -Nru squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch 
squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch
--- squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch1970-01-01 
00:00:00.0 +
+++ squeekboard-1.22.0/debian/patches/0005-gtk-rs-0.17.patch2023-08-03 
16:41:53.0 +
@@ -0,0 +1,56 @@
+Index: squeekboard-1.22.0/Cargo.deps.newer
+===
+--- squeekboard-1.22.0.orig/Cargo.deps.newer
 squeekboard-1.22.0/Cargo.deps.newer
+@@ -10,30 +10,30 @@ zvariant_derive = "2.10.*"
+ xkbcommon = { version = "0.5.*", features = ["wayland"] }
+ 
+ [dependencies.cairo-rs]
+-version = "0.16.*"
++version = "0.17.*"
+ 
+ [dependencies.cairo-sys-rs]
+-version = "0.16.*"
++version = "0.17.*"
+ 
+ [dependencies.gdk]
+-version = "0.16.*"
++version = "0.17.*"
+ 
+ [dependencies.gio]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v2_58"]
+ 
+ [dependencies.glib]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v2_58"]
+ 
+ [dependencies.glib-sys]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v2_58"]
+ 
+ [dependencies.gtk]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v3_24"]
+ 
+ [dependencies.gtk-sys]
+-version = "0.16.*"
++version = "0.17.*"
+ features = ["v3_24"]
+Index: squeekboard-1.22.0/src/popover.rs
+===
+--- squeekboard-1.22.0.orig/src/popover.rs
 squeekboard-1.22.0/src/popover.rs
+@@ -326,7 +326,7 @@ pub fn show(
+ let layout_action = gio::SimpleAction::new_stateful(
+ "layout",
+ Some(current_layout_name.to_variant().type_()),
+-_layout_name.to_variant()
++current_layout_name.to_variant()
+ );
+ 
+ let menu_inner = menu.clone();
diff -Nru squeekboard-1.22.0/debian/patches/series 
squeekboard-1.22.0/debian/patches/series
--- squeekboard-1.22.0/debian/patches/series2023-07-01 15:14:45.0 
+
+++ squeekboard-1.22.0/debian/patches/series2023-08-03 16:40:41.0 
+
@@ -2,3 +2,4 @@
 0002-src-popover-fix-build-with-newer-gtk-rs.patch
 0003-src-style-fix-build-with-newer-gtk-rs.patch
 0004-Cargo.-use-xkbcommon-v0.5.patch
+0005-gtk-rs-0.17.patch
--- End Message ---
--- Begin Message ---
Source: squeekboard
Source-Version: 1.22.0-4
Done: Arnaud Ferraris 

We believe that the bug you reported is fixed in the latest version of
squeekboard, 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#1050027: marked as done (libcoq-mathcomp-classical: undeclared file conflict with libcoq-mathcomp-analysis/bookworm+trixie)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 10:37:29 +
with message-id 
and subject line Bug#1050027: fixed in mathcomp-analysis 0.6.4-3
has caused the Debian Bug report #1050027,
regarding libcoq-mathcomp-classical: undeclared file conflict with 
libcoq-mathcomp-analysis/bookworm+trixie
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.)


-- 
1050027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcoq-mathcomp-classical
Version: 0.6.4-1+b1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libcoq-mathcomp-analysis

libcoq-mathcomp-classical starts to ship the following files:

/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/boolp.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/boolp.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/boolp.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/cardinality.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/cardinality.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/cardinality.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/classical_sets.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/classical_sets.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/classical_sets.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/fsbigop.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/fsbigop.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/fsbigop.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/functions.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/functions.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/functions.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/mathcomp_extra.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/mathcomp_extra.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/mathcomp_extra.vo
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/set_interval.glob
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/set_interval.v
/usr/lib/ocaml/coq/user-contrib/mathcomp/classical/set_interval.vo

They happen to also be part of libcoq-mathcomp-analysis as part of
bookworm and trixie. There is no Conflicts nor Replaces relation
addressing this conflict nor are there any diversions. As such, this
situation can result in unpack errors in an upgrade scenario.

Judging from the changelog (saying "package split") you mean to
restructure and therefore replace these files. If you agree, please add
the necessary Breaks+Replaces relations.

Helmut
--- End Message ---
--- Begin Message ---
Source: mathcomp-analysis
Source-Version: 0.6.4-3
Done: Julien Puydt 

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated mathcomp-analysis 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, 23 Aug 2023 11:57:00 +0200
Source: mathcomp-analysis
Architecture: source
Version: 0.6.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Julien Puydt 
Closes: 1050027
Changes:
 mathcomp-analysis (0.6.4-3) unstable; urgency=medium
 .
   * Add missing(?!) Replaces (Closes: #1050027).
Checksums-Sha1:
 40229934f3fef5e9f176f73a54c10eaceda3a907 2425 mathcomp-analysis_0.6.4-3.dsc
 eabd72448439836435ae2976ec43809b0a74c81c 9120 
mathcomp-analysis_0.6.4-3.debian.tar.xz
 c505226cdd280fc5bf1c26f989b47f5e88c208b0 8327 
mathcomp-analysis_0.6.4-3_source.buildinfo
Checksums-Sha256:
 a03593ee2318705a0981f0670d4677ea567e33b0598897ccc22b5b2f1cb6a7f2 2425 
mathcomp-analysis_0.6.4-3.dsc
 2ec53074e287c553197942706f67d72e3cb2b86ccec80cdee1cfb3e8e9e95324 9120 
mathcomp-analysis_0.6.4-3.debian.tar.xz
 2dac79c017c091eeb6aadbaa106fb7aef30e98a4dfb900a6e6a6e3e98c36453d 8327 
mathcomp-analysis_0.6.4-3_source.buildinfo
Files:
 f773adb732e1834ea75a144d3ead78ab 2425 ocaml optional 
mathcomp-analysis_0.6.4-3.dsc
 cb023885de01aa41aef96b3062701224 9120 ocaml optional 
mathcomp-analysis_0.6.4-3.debian.tar.xz
 

Processed: Bug#1042983 marked as pending in squeekboard

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042983 [squeekboard] squeekboard - rust gtk stack update.
Added tag(s) pending.

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

Bug#1042983: marked as pending in squeekboard

[Arnaud Ferraris]

Control: tag -1 pending

Hello,

Bug #1042983 in squeekboard 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/DebianOnMobile-team/squeekboard/-/commit/7eb4bdfef2e26e3668061848eb83708a14bce6b1


d/patches: update for gtk-rs 0.17

Closes: #1042983


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042983

Bug#1050096: virtualbox-dkms: Does not build on 6.4.0-3-amd64

[Jonas Andradas]

Package: virtualbox-dkms
Version: 7.0.10-dfsg-2
Followup-For: Bug #1050096
X-Debbugs-Cc: j.andra...@gmail.com

Following the comments in other bug trackers for this same bugs from other
distros, I could solve it by modifying the file

/usr/src/virtualbox-7.0.10/vboxnetflt/linux/VBoxNetFlt-linux.c

on line 50, changing the value from:

#if RTLNX_VER_MIN(6,5,0)

to:

#if RTLNX_VER_MIN(6,4,0)


After this, it built properly on 6.4.0-3 (where it previously had failed, so
dpkg had finished with errors:

Errors were encountered while processing:
 linux-headers-6.4.0-3-amd64
 linux-headers-amd64
 linux-image-6.4.0-3-amd64
 linux-image-amd64


Thus, `dpkg --configure -a` just compiled the module for 6.4.0-3 as it had been
able to build it fine for 6.4.0-2.
I am not sure if the change I made would break the module from building on
6.4.0-2 or other 6.4.0 kernels.





-- System Information:
Debian Release: trixie/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'stable')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages virtualbox-dkms depends on:
ii  dkms  3.0.11-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  7.0.10-dfsg-2

virtualbox-dkms suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file 
/usr/src/virtualbox-7.0.10/vboxnetflt/linux/VBoxNetFlt-linux.c (from 
virtualbox-dkms package)

Bug#1050027: libcoq-mathcomp-classical: undeclared file conflict with libcoq-mathcomp-analysis/bookworm+trixie

[julien . puydt]

Le mercredi 23 août 2023 à 09:07 +0100, Simon McVittie a écrit :
> On Wed, 23 Aug 2023 at 08:41:44 +0200, julien.pu...@gmail.com wrote:
> > let's lower the severity to avoid blocking migration during the
> > discussion -- after all the Breaks already avoids the file conflict
> > issue.
> 
> Sorry, no, it does not. What Helmut said looks correct.
> 
> The Breaks prevents apt from installing the new libcoq-mathcomp-
> classical
> without also upgrading or deconfiguring libcoq-mathcomp-analysis, but
> does not constrain the order in which apt/dpkg will carry out the
> upgrade.
> 
> If they happen to have chosen this order of operations, which is what
> happened when I tried an upgrade from bookworm to sid, and presumably
> also what you saw in your own testing:
> 
> 1. unpack the new libcoq-mathcomp-analysis
>   (leaving its dependency on libcoq-mathcomp-classical temporarily
>   unsatisfied - the overall state of the system is "partially
> broken")
> 2. unpack the new libcoq-mathcomp-classical
> 3. configure libcoq-mathcomp-classical
> 4. configure libcoq-mathcomp-analysis
>    (the system is back to a consistent state)
> 
> then the file-overwrite will be avoided. But if it chooses this order
> of operations:
> 
> 1. temporarily mark the old libcoq-mathcomp-analysis as deconfigured
>    (again, the overall state of the system is "partially broken")
> 2. unpack the new libcoq-mathcomp-classical
> 3. unpack the new libcoq-mathcomp-analysis
> 4. configure libcoq-mathcomp-classical
> 5. configure libcoq-mathcomp-analysis
>    (the system is back to a consistent state)
> 
> then step 2 is going to fail, because the old libcoq-mathcomp-
> analysis
> contained files also present in the new libcoq-mathcomp-classical.
> (Symptom: "trying to overwrite x, which is also in package y")
> 
> With the current metadata, there is no guarantee which of those
> two upgrade sequences apt will choose. It is common for bugs of this
> category to not happen during the maintainer's testing, but then be
> easily
> reproducible by other users who have more/different packages
> installed,
> which makes apt choose a slightly different upgrade path.


I'll just fix the bug like you want to avoid blocking other packages,
but I really do not understand, so I'll continue asking on the debian-
policy bug to get things clarified.

Cheers,

J.Puydt

Bug#1050329: sexpp FTBFS with nocheck profile

[Helmut Grohne]

Source: sexpp
Version: 0.8.7-3
Severity: serious
Justification: since trixie, nocheck FTBFS is serious
Tags: ftbfs patch

Hi,

trying to build sexpp with the nocheck build profile fails, because the
variable for disabling tests is subtly misspelled and therefore tests
are not deactivated. I'm attaching a patch for your convenience.

Helmut
diff --minimal -Nru sexpp-0.8.7/debian/changelog sexpp-0.8.7/debian/changelog
--- sexpp-0.8.7/debian/changelog2023-08-15 02:17:57.0 +0200
+++ sexpp-0.8.7/debian/changelog2023-08-23 10:34:18.0 +0200
@@ -1,3 +1,10 @@
+sexpp (0.8.7-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix nocheck FTBFS. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 23 Aug 2023 10:34:18 +0200
+
 sexpp (0.8.7-3) unstable; urgency=medium
 
   * drop .symbols file, since the C++ name mangling makes it too fragile
diff --minimal -Nru sexpp-0.8.7/debian/rules sexpp-0.8.7/debian/rules
--- sexpp-0.8.7/debian/rules2023-06-27 23:56:59.0 +0200
+++ sexpp-0.8.7/debian/rules2023-08-23 10:34:15.0 +0200
@@ -8,7 +8,7 @@
 CONFIGURE_OPTIONS = -DBUILD_SHARED_LIBS=on
 
 ifneq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
-CONFIGURE_OPTIONS += -DWITH_SEXPP_TESTS=off
+CONFIGURE_OPTIONS += -DWITH_SEXP_TESTS=off
 endif
 
 override_dh_auto_configure:

Bug#1028104: libboost-dev: Boost with C++20 uses unavailable std functions.

[Andre Naujoks]

For anyone stumbling upon this.

A simple workaround is to '#include ' before '#include 
'

utility is the header that declares std::exchange

this does not look like a C++20 problem but a simple missing include in the 
boost headers.
Maybe this is actually worth a small patch in debian, since its such a simple 
problem to avoid. And I don't think an added include  would break 
anything(?).

best regards
  Andre

Bug#1000089: marked as done (clisp: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 09:19:32 +
with message-id 
and subject line Bug#189: fixed in clisp 1:2.49.20210628.gitde01f0f-3.1
has caused the Debian Bug report #189,
regarding clisp: depends on obsolete pcre3 library
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

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

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: clisp
Source-Version: 1:2.49.20210628.gitde01f0f-3.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
clisp, 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.
Bastian Germann  (supplier of updated clisp 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: Fri, 18 Aug 2023 16:39:51 +
Source: clisp
Architecture: source
Version: 1:2.49.20210628.gitde01f0f-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Common Lisp Team 
Changed-By: Bastian Germann 
Closes: 189
Changes:
 clisp (1:2.49.20210628.gitde01f0f-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop clisp-module-pcre. (Closes: #189)
Checksums-Sha1:
 576730f7fb77df41086471427ad41a0a4284845f 2883 
clisp_2.49.20210628.gitde01f0f-3.1.dsc
 84c656dff9157184ff4130cd9a1e028d3228fa0e 27912 
clisp_2.49.20210628.gitde01f0f-3.1.debian.tar.xz
 05b513121f675d052be58a0a7225048dfc6823a4 8475 
clisp_2.49.20210628.gitde01f0f-3.1_source.buildinfo
Checksums-Sha256:
 81bc0d1dcb516ae2bfcdf536c618b8d4be96a4a7a260d2e7e8ca503cef4906c0 2883 
clisp_2.49.20210628.gitde01f0f-3.1.dsc
 39bea8dbb18b031f7e3df8c591c3f7b97553f8a8d5deea54c571549b9945402e 27912 
clisp_2.49.20210628.gitde01f0f-3.1.debian.tar.xz
 724c0bebbe15f0810e8628e3fc98416266d427debd71bcdc2aeba8d029859001 8475 
clisp_2.49.20210628.gitde01f0f-3.1_source.buildinfo
Files:
 a9092845c325142effbdefb01c1a1bb7 2883 lisp optional 
clisp_2.49.20210628.gitde01f0f-3.1.dsc
 055a6b3d72814d489ed07b162aa92104 27912 lisp optional 
clisp_2.49.20210628.gitde01f0f-3.1.debian.tar.xz
 a2dad87e78401974e95981b488a103fd 8475 lisp optional 
clisp_2.49.20210628.gitde01f0f-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTjIu8QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFG9+DADjfSNlNbS+3xo1KZTdUK1U7vaJonQNO/bA
G+R79t1qqtjpXyDEK6Giz+X0e+i9A7U6z4gNyrAvvkH4DdOKcFbLyghkcOu+f5oI
SGkGtYyoHkl3VDlZdDOTqWWz9i2qohzL3J/m0jWx6Ktx9M8oQsLk0S/+yGC+LBmd
ZGWIMW+6BZS1nmU901eInRlInAOl+as2ZFBcNqTKTXSt4MBoH9Q99koWvT6d65fj
MOJuR8voaglIiKYI31Op4Aaiwu0aDJ8hc+rt09dKX7dkAgAEbgoWIk2AyoSiiVbQ
fuNEm7NUsSGaOm/QWl91vv1LrRJ5mEgnViuQ/TgfCTHcP1hU+qsOQvmrWIBA0uCf
bmqzafdks4EYfpmYKEOSLODRJ+g5RjHUXtjruFqZnNnUx/881e2UIjvAb7lOVQPr
Y1PCoL6QztFuPUSJ8Z619Ubz/v5srkY9pScW/xp+qs/heiov0uy+5lMUxwONaE3Q
7VCKc16GrwQcBjvGBkVPUu0Cd2+mSlo=
=9CQn
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#1050027: Stop blocking other packages migration

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1050027 [libcoq-mathcomp-classical] libcoq-mathcomp-classical: undeclared 
file conflict with libcoq-mathcomp-analysis/bookworm+trixie
Severity set to 'serious' from 'normal'

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

Bug#1050327: gcc-arm-none-eabi update breaks other arm-none-eabi packages

[Matthias Klose]

Package: src:gcc-arm-none-eabi
Version: 15:12.3.rel1-1
Severity: serious
Tags: sid trixie

a typical upload-and-run-away package upload ...

see tracker.debian.org, doesn't pass autopkg tests, makes other packages 
uninstallable, breaks other packages autopkg tests.


https://tracker.debian.org/pkg/gcc-arm-none-eabi

Bug#1039529: [Debian-med-packaging] Bug#1039529: sight: FTBFS: /<>/libs/io/itk/helper/ProgressItkToFw.hxx:48:5: error: ‘::Create’ has not been declared

[Flavien Bridault]

Dear developers,

It turns out that sight FTBFS is due to a regression in itkMacro.h. This 
has been fixed upstream in 
https://github.com/InsightSoftwareConsortium/ITK/commit/7fbe8880a99ce1442b5b3e04ab05babdabe8e930. 



I could hack this in sight but this would be really tedious. This might 
break also other client code, as reported here 
https://github.com/InsightSoftwareConsortium/ITK/issues/4074/


Do you think it could be possible to add a patch for this in the 
insighttoolkit5 package ?


Thanks a lot.


*Dr. Flavien BRIDAULT*
Director of Software Development
IRCAD France & IRCAD Africa

flavien.brida...@ircad.fr 
Tél. : +33 (0)3 88 119 201
IRCAD France
http://www.ircad.fr/
http://www.ircad.africa/ 

Suivez l'IRCAD sur Facebook 



*IRCAD France*
Hôpitaux Universitaires - 1, place de l'Hôpital - 67091 Strasbourg Cedex 
- FRANCE


Le 27/06/2023 à 00:10, Sebastian Ramacher a écrit :

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

https://buildd.debian.org/status/fetch.php?pkg=sight=amd64=21.1.1-3%2Bb2=1687809257=0

[ 66%] Linking CXX shared library 
../../../lib/x86_64-linux-gnu/libsight_module_filter_vision.so
cd /<>/obj-x86_64-linux-gnu/modules/filter/vision && 
/usr/bin/cmake -E cmake_link_script CMakeFiles/module_filter_vision.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -Wl,--as-needed 
-Wl,--sort-common -Wl,-O2 -Wl,-z,relro -Wl,-z,now -shared 
-Wl,-soname,libsight_module_filter_vision.so.21.1 -o 
../../../lib/x86_64-linux-gnu/libsight_module_filter_vision.so.21.1.0 
CMakeFiles/module_filter_vision.dir/Plugin.cpp.o 
CMakeFiles/module_filter_vision.dir/SColourImageMasking.cpp.o 
CMakeFiles/module_filter_vision.dir/SDepthImageMasking.cpp.o 
CMakeFiles/module_filter_vision.dir/SOpticalFlow.cpp.o 
CMakeFiles/module_filter_vision.dir/SPointCloudFromDepthMap.cpp.o 
CMakeFiles/module_filter_vision.dir/STransformDepthMap2mm.cpp.o 
CMakeFiles/module_filter_vision.dir/STransformDepthTL2mm.cpp.o 
CMakeFiles/module_filter_vision.dir/SUltrasoundImage.cpp.o 
CMakeFiles/module_filter_vision.dir/registerServices.cpp.o  
-Wl,-rpath,/<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu: 
/usr/lib/x86_64-linux-gnu/libopencv_highgui.so.4.6.0 /usr/lib/x86_64-linux-gnu/libopencv_video.so.4.6.0 
../../../lib/x86_64-linux-gnu/libsight_service.so.21.1.0 
../../../lib/x86_64-linux-gnu/libsight_geometry_data.so.21.1.0 
../../../lib/x86_64-linux-gnu/libsight_filter_vision.so.21.1.0 
../../../lib/x86_64-linux-gnu/libsight_io_opencv.so.21.1.0 
/usr/lib/x86_64-linux-gnu/libopencv_videoio.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_imgcodecs.so.4.6.0 /usr/lib/x86_64-linux-gnu/libopencv_dnn.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_features2d.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_imgproc.so.4.6.0 /usr/lib/x86_64-linux-gnu/libopencv_flann.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_core.so.4.6.0 
../../../lib/x86_64-linux-gnu/libsight_activity.so.21.1.0 
/usr/lib/x86_64-linux-gnu/libopencv_ml.so.4.6.0 /usr/lib/x86_64-linux-gnu/libopencv_imgproc.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_core.so.4.6.0 ../../../lib/x86_64-linux-gnu/libsight_data.so.21.1.0 
../../../lib/x86_64-linux-gnu/libsight_core.so.21.1.0 
/usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_log_setup.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_log.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_regex.so.1.74.0 /usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_atomic.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 /usr/lib/x86_64-linux-gnu/libxml2.so 
/usr/lib/x86_64-linux-gnu/libcrypto.so -ldl /usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_features2d.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_flann.so.4.6.0 /usr/lib/x86_64-linux-gnu/libopencv_imgproc.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_core.so.4.6.0
In file included from /usr/include/ITK-5.3/itkLightObject.h:21,
  from /usr/include/ITK-5.3/itkObject.h:31,
  from /usr/include/ITK-5.3/itkLightProcessObject.h:21,
  from /usr/include/ITK-5.3/itkImageIOBase.h:24,
  from 
/<>/libs/io/itk/inr2itk/itkInrImageIOFactory.hpp:25,
  from /<>/libs/io/itk/ImageReader.cpp:25:
/<>/libs/io/itk/helper/ProgressItkToFw.hxx:48:5: error: 
‘LightObject’ in namespace ‘sight::io::itk’ does not name a type
48 | 

Bug#1043279: marked as done (musicbrainzngs build-depends on dropped package)

[Debian Bug Tracking System]

Your message dated Wed, 23 Aug 2023 07:49:21 +
with message-id 
and subject line Bug#1043279: fixed in musicbrainzngs 0.7.1-5
has caused the Debian Bug report #1043279,
regarding musicbrainzngs build-depends on dropped package
to be marked as done.

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

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


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

Package: musicbrainzngs
Version: 0.7.1-4
Severity: serious
Tags: trixie, sid
Justification: rc policy - "Packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

musicbrainzngs build-depends on python-libdiscid-doc which is no longer built by
the python-libdiscid source package. It is still present in unstable as a cruft
package, but is completely gone from testing.
--- End Message ---
--- Begin Message ---
Source: musicbrainzngs
Source-Version: 0.7.1-5
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated musicbrainzngs 
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, 23 Aug 2023 09:43:23 +0200
Source: musicbrainzngs
Architecture: source
Version: 0.7.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Sebastian Ramacher 
Closes: 1043279
Changes:
 musicbrainzngs (0.7.1-5) unstable; urgency=medium
 .
   * Team upload
   * debian/: Remove use of python-libdiscid-doc (Closes: #1043279)
Checksums-Sha1:
 9c9e93385142db6287df1d98fd40b337894b6327 1614 musicbrainzngs_0.7.1-5.dsc
 345695048b4d548bdcba0b1162bec2b782fba121 5424 
musicbrainzngs_0.7.1-5.debian.tar.xz
Checksums-Sha256:
 a19c6660aa02575aff2b911c6d1c3a8bb2f040db2a2eba94a934517e5ee62c35 1614 
musicbrainzngs_0.7.1-5.dsc
 330f2f9b681e071acd3803afcb8ec586e54cb263c92fe7153ba8001811a88f99 5424 
musicbrainzngs_0.7.1-5.debian.tar.xz
Files:
 f4aec03ac7bb2a4402c672049a54f959 1614 python optional 
musicbrainzngs_0.7.1-5.dsc
 49148bebb37e10f41dc39fe0a7503805 5424 python optional 
musicbrainzngs_0.7.1-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZOW5SAAKCRAhk2s2YA/N
iXT+AP9tLR4Ug+v0RQeR0Ap6geYjVUKRknxYRaUMJZ8AqCXq4gD/WJ+VI+dxutve
uAfdIvY1EkS7ysNMGvJ2I2hiaiDdAQY=
=qhkp
-END PGP SIGNATURE End Message ---

Bug#994171: 0.2.8+git20220410.81c5a42-1: unable to set up jediepcserver, permission denied

[Lev Lamberov]

Control: retitle -1 unable to set up jediepcserver, permission denied

Hi,

I've uploaded 0.2.8+git20220410.81c5a42-1, which contains all upstream
changes. Now emacs-jedi is compatible with jedi in Debian (the API was
updated to jedi 0.18).

Unfortunately, there's another problem, now due to permissions. Namely,
as follows:

Running: pip install --upgrade 
/usr/share/emacs/site-lisp/elpa/jedi-core-0.3.0/...Done
deferred error : (error "Deferred process exited abnormally:
  command: /home/dogsleg/.emacs.d/.python-environments/default/bin/pip
  exit status: exit 1
  event: exited abnormally with code 1
  buffer contents: \"Processing /usr/share/emacs/site-lisp/elpa/jedi-core-0.3.0
  Preparing metadata (setup.py) ... [?25l-  done
[?25hCollecting argparse (from jediepcserver==0.3.0)
  Using cached argparse-1.4.0-py2.py3-none-any.whl (23 kB)
Requirement already satisfied: epc>=0.0.4 in /usr/lib/python3/dist-packages 
(from jediepcserver==0.3.0) (0.0.5)
Requirement already satisfied: jedi>=0.11.0 in /usr/lib/python3/dist-packages 
(from jediepcserver==0.3.0) (0.18.2)
Requirement already satisfied: setuptools in 
./.emacs.d/.python-environments/default/lib/python3.11/site-packages (from 
jediepcserver==0.3.0) (68.0.0)
Building wheels for collected packages: jediepcserver
  Building wheel for jediepcserver (setup.py) ... [?25l-  error
  error: subprocess-exited-with-error
  
  × python setup.py bdist_wheel did not run successfully.
  │ exit code: 1
  ╰─> [5 lines of output]
  running bdist_wheel
  running build
  running build_py
  creating build
  error: could not create 'build': Permission denied
  [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem 
with pip.
  ERROR: Failed building wheel for jediepcserver
[?25h  Running setup.py clean for jediepcserver
Failed to build jediepcserver
ERROR: Could not build wheels for jediepcserver, which is required to install 
pyproject.toml-based projects
\"")

Looks like it tries to set up the Python environment in some system's
drectory, not in user's HOME. Currently, I don't have time to invest
into this, patches are welcome.

The severity is still grave, because the package is not usable, but I'm
retitling the bug report (instead of closing and submitting a new one)
to reflect this new problem.

Regards,
Lev

Processed: 0.2.8+git20220410.81c5a42-1: unable to set up jediepcserver, permission denied

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 unable to set up jediepcserver, permission denied
Bug #994171 [elpa-jedi-core] elpa-jedi-core incompatible with python3-jedi in 
bullseye
Changed Bug title to 'unable to set up jediepcserver, permission denied' from 
'elpa-jedi-core incompatible with python3-jedi in bullseye'.

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

Processed: Stop blocking other packages migration

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1050027 [libcoq-mathcomp-classical] libcoq-mathcomp-classical: undeclared 
file conflict with libcoq-mathcomp-analysis/bookworm+trixie
Severity set to 'normal' from 'serious'

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

Bug#1050027: Stop blocking other packages migration

[julien . puydt]

Control: severity -1 normal

Hi,

let's lower the severity to avoid blocking migration during the
discussion -- after all the Breaks already avoids the file conflict
issue.

Cheers,

J.Puydt

Bug#891197: ncbi-blast+ is marked for autoremoval from testing

[Andreas Tille]

Hi Aaron,

Am Wed, Aug 23, 2023 at 04:39:11AM + schrieb Debian testing autoremoval 
watch:
> ncbi-blast+ 2.12.0+ds-3 is marked for autoremoval from testing on 2023-09-20
> 
> It is affected by these RC bugs:
> 891197: ncbi-blast+: Please switch to pcre2
>  https://bugs.debian.org/891197

On Mon, 21 Aug 2023 15:33:03 GMT this bug was set serious with the consequence
that this package and all its dependencies are creating a lot of noise about
testing removals. 

On Mon, 05 Dec 2022 you wrote:
> At any rate, upstream is now open to moving on, albeit at low priority.
 
It would be really great if you could explain upstream the situation and
we could fix this bug in the next couple of weeks.

Kind regards
 Andreas.

-- 
http://fam-tille.de