Bug#1005040: marked as done (tortoize: Remove wrong hard-coded dependency on libcifpp1)

[Debian Bug Tracking System]

Your message dated Sun, 06 Feb 2022 07:48:54 +
with message-id 
and subject line Bug#1005040: fixed in tortoize 2.0.5-2
has caused the Debian Bug report #1005040,
regarding tortoize: Remove wrong hard-coded dependency on libcifpp1
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.)


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

Hi Maarten,

The tortoize package has a hard-coded dependency on libcifpp1 listed in
debian/control.  It is always wrong to hard-code specific runtime libraries
in debian/control, and this now makes tortoize uninstallable with current
libcifpp, which has bumped its soname to libcifpp.so.2.

Please drop the reference to libcifpp1 as in the attached patch.

The hard-coded reference to libzeep5.1 is almost certainly also incorrect
but I have not verified this.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru tortoize-2.0.5/debian/control tortoize-2.0.5/debian/control
--- tortoize-2.0.5/debian/control   2022-02-04 22:41:14.0 -0800
+++ tortoize-2.0.5/debian/control   2022-02-05 12:32:24.0 -0800
@@ -22,7 +22,7 @@
 
 Package: tortoize
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libcifpp1, libzeep5.1
+Depends: ${shlibs:Depends}, ${misc:Depends}, libzeep5.1
 Description: Application to calculate ramachandran z-scores
  Tortoize validates protein structure models by checking the
  Ramachandran plot and side-chain rotamer distributions. Quality
--- End Message ---
--- Begin Message ---
Source: tortoize
Source-Version: 2.0.5-2
Done: Maarten L. Hekkelman 

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

Debian distribution maintenance software
pp.
Maarten L. Hekkelman  (supplier of updated tortoize 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 06 Feb 2022 08:01:13 +0100
Source: tortoize
Architecture: source
Version: 2.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Maarten L. Hekkelman 
Closes: 1005040
Changes:
 tortoize (2.0.5-2) unstable; urgency=medium
 .
   * Fix dependency, Closes: #1005040
Checksums-Sha1:
 c64ccf8a7190e270593df2983735bbe4a8100c31 2176 tortoize_2.0.5-2.dsc
 4a3fa81a32ad603cd9237224d0295c5bcf8cee42 3592 tortoize_2.0.5-2.debian.tar.xz
 0f2c26b07aacba5afdd77cd597e43cf0891da4ce 8080 tortoize_2.0.5-2_amd64.buildinfo
Checksums-Sha256:
 ced47c6bcfac2b4d45f7aad25a13fc059d93b4964e94c356b0c0a6d112271a77 2176 
tortoize_2.0.5-2.dsc
 728abc5d8217fe8781715ff24db37cdb15eecb64cf4207a341ec2beaca62d2bc 3592 
tortoize_2.0.5-2.debian.tar.xz
 2a6d8bdbfd7d284bd1ec8105862c31ad159929dcf19e8d15668f7dc1e8551729 8080 
tortoize_2.0.5-2_amd64.buildinfo
Files:
 749a18dc96cbbf55bafeb577c1969077 2176 science optional tortoize_2.0.5-2.dsc
 9068e153d3f7398eda966d56521c6c54 3592 science optional 
tortoize_2.0.5-2.debian.tar.xz
 f56ecdf7af94c581252d039509236b94 8080 science optional 
tortoize_2.0.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEpytoJCJrtAfiS56AWHUD7Hrn7c4FAmH/eeAWHG1hYXJ0ZW5A
aGVra2VsbWFuLmNvbQAKCRBYdQPseuftzgNYD/9d6a5ZV6JA26B9kJI1DBuLdtjj
HhMn4wef+83a63eHYLYGlVH5fqVJma3Jz6Z8e9h3JUMBR7sW9jSwsAdX5AeU7mVa
194xNFwDfD5C94CyrALkAl/My99JCiOR5oy43tytSWtFF3MJEuFvG833B7Dvu2mr
qBEla8cqj9WEvl6EbsZ7MY7BoeS5KkL2eWgetrKN8CJv27bA/iSORuqcU4cuHSJG
hHyCsa8JZptmrOIjxCTPLMbk8ory8G0nEPn8/j2SlkeLzaxyenTCedGE4Oy/0d28
lDoT+UK+5M77wglXCXaO8vhPsqkZQcwx8fFv0qMrgKg/UKH1WrhKf252QKb83Bii
UyH/kJXJ3fe/k42RNjoZymcx5wqcj7vvQfPPiSqEf5WlluNI4s39LxhEatGBg+gK

Bug#992575: closing 992575

[Christian Marillat]

close 992575 
thanks

Bug fixed in libtorrent-rasterbar 2.0.5

Christian

Processed: closing 999422

[Debian Bug Tracking System]

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

> close 999422
Bug #999422 {Done: Christian Marillat } 
[libtorrent-rasterbar10] Deluge fails with ModuleNotFoundError
Bug #992575 {Done: Christian Marillat } 
[libtorrent-rasterbar10] libtorrent-rasterbar10: import fails on Raspberry Pi 3b
Bug 999422 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: closing 992575

[Debian Bug Tracking System]

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

> close 992575
Bug #992575 {Done: Christian Marillat } 
[libtorrent-rasterbar10] libtorrent-rasterbar10: import fails on Raspberry Pi 3b
Bug #999422 {Done: Christian Marillat } 
[libtorrent-rasterbar10] Deluge fails with ModuleNotFoundError
Bug 992575 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#999422: closing 999422

[Christian Marillat]

close 999422 
thanks

Bug fixed in libtorrent-rasterbar 2.0.5

Christian

Processed: 1005006 is not ftbfs

[Debian Bug Tracking System]

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

> tags 1005006 - ftbfs
Bug #1005006 [avogadro] avogadro: manipulation tools do not work
Removed tag(s) ftbfs.
> severity 1005006 normal
Bug #1005006 [avogadro] avogadro: manipulation tools do not work
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: tagging 1001367

[Debian Bug Tracking System]

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

> tags 1001367 + pending
Bug #1001367 [src:pyeapi] pyeapi: (autopkgtest) needs update for python3.10: 
'collections' has no attribute 'Iterable'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: closing 997247

[Debian Bug Tracking System]

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

> close 997247
Bug #997247 [src:litecoin] litecoin: FTBFS: ld: 
libbitcoin_server.a(libbitcoin_server_a-dbwrapper.o):(.data.rel.ro._ZTI21CBitcoinLevelDBLogger[_ZTI21CBitcoinLevelDBLogger]+0x10):
 undefined reference to `typeinfo for leveldb::Logger'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1005053: salt FTBFS on IPV6-only buildds

[Adrian Bunk]

Source: salt
Version: 3004+dfsg1-6
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=salt=all

...
=== FAILURES ===
__ test_connected_ids __

def test_connected_ids():
"""
test ckminion connected_ids when
local_port_tcp returns 127.0.0.1
"""
opts = {"publish_port": 4505, "detect_remote_minions": False}
minion = "minion"
ip = salt.utils.network.ip_addrs()
mdata = {"grains": {"ipv4": ip, "ipv6": []}}
ckminions = salt.utils.minions.CkMinions({"minion_data_cache": True})
patch_net = patch("salt.utils.network.local_port_tcp", 
return_value={"127.0.0.1"})
patch_list = patch("salt.cache.Cache.list", return_value=[minion])
patch_fetch = patch("salt.cache.Cache.fetch", return_value=mdata)
with patch.dict(ckminions.opts, opts):
with patch_net, patch_list, patch_fetch:
ret = ckminions.connected_ids()
>   assert ret == {minion}
E   AssertionError: assert set() == {'minion'}
E Extra items in the right set:
E 'minion'
E Use -v to get the full diff

/<>/tests/pytests/unit/utils/test_minions.py:22: AssertionError
__ test_connected_ids_remote_minions ___

def test_connected_ids_remote_minions():
"""
test ckminion connected_ids when
detect_remote_minions is set
"""
opts = {
"publish_port": 4505,
"detect_remote_minions": True,
"remote_minions_port": 22,
}
minion = "minion"
minion2 = "minion2"
minion2_ip = "192.168.2.10"
ip = salt.utils.network.ip_addrs()
mdata = {"grains": {"ipv4": ip, "ipv6": []}}
mdata2 = {"grains": {"ipv4": [minion2_ip], "ipv6": []}}
ckminions = salt.utils.minions.CkMinions({"minion_data_cache": True})
patch_net = patch("salt.utils.network.local_port_tcp", 
return_value={"127.0.0.1"})
patch_remote_net = patch(
"salt.utils.network.remote_port_tcp", return_value={minion2_ip}
)
patch_list = patch("salt.cache.Cache.list", return_value=[minion, 
minion2])
patch_fetch = patch("salt.cache.Cache.fetch", side_effect=[mdata, 
mdata2])
with patch.dict(ckminions.opts, opts):
with patch_net, patch_list, patch_fetch, patch_remote_net:
ret = ckminions.connected_ids()
>   assert ret == {minion2, minion}
E   AssertionError: assert {'minion2'} == {'minion', 'minion2'}
E Extra items in the right set:
E 'minion'
E Use -v to get the full diff

/<>/tests/pytests/unit/utils/test_minions.py:51: AssertionError
...
FAILED tests/pytests/unit/utils/test_minions.py::test_connected_ids - Asserti...
FAILED 
tests/pytests/unit/utils/test_minions.py::test_connected_ids_remote_minions
= 2 failed, 9692 passed, 1751 skipped, 5 xfailed, 4 xpassed, 552 warnings in 
470.23s (0:07:50) =
Exception ignored in: 
Traceback (most recent call last):
  File "/<>/salt/transport/ipc.py", line 702, in _read
TypeError: catching classes that do not inherit from BaseException is not 
allowed
Exception ignored in: 
Traceback (most recent call last):
  File "/<>/salt/transport/ipc.py", line 702, in _read
TypeError: catching classes that do not inherit from BaseException is not 
allowed
make[1]: *** [debian/rules:35: override_dh_auto_test] Error 1

Bug#1004900: marked as done (zim-tools: FTBFS on slow buildds)

[Debian Bug Tracking System]

Your message dated Sun, 06 Feb 2022 01:05:38 +
with message-id 
and subject line Bug#1004900: fixed in zim-tools 3.1.0-3
has caused the Debian Bug report #1004900,
regarding zim-tools: FTBFS on slow buildds
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.)


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

https://buildd.debian.org/status/logs.php?pkg=zim-tools=riscv64
https://buildd.debian.org/status/logs.php?pkg=zim-tools=mips64el

...
Expected equality of these values:
...
-[INFO] Total time taken by zimcheck: 0 seconds.\n
+[INFO] Total time taken by zimcheck: 1 seconds.\n
...
--- End Message ---
--- Begin Message ---
Source: zim-tools
Source-Version: 3.1.0-3
Done: Kunal Mehta 

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

Debian distribution maintenance software
pp.
Kunal Mehta  (supplier of updated zim-tools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Feb 2022 16:35:49 -0800
Source: zim-tools
Architecture: source
Version: 3.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Kunal Mehta 
Changed-By: Kunal Mehta 
Closes: 1004900
Changes:
 zim-tools (3.1.0-3) unstable; urgency=medium
 .
   * Fix autopkgtests, don't output to stderr on purpose
   * Don't require zimcheck tests finish in less than half a second
 (Closes: #1004900)
Checksums-Sha1:
 2880bc9fd339cd2fa28513426d92c802c4d181b6 2104 zim-tools_3.1.0-3.dsc
 7ce97d4898589c4e21e6d101035dec5e71e7a341 13920 zim-tools_3.1.0-3.debian.tar.xz
 89bb063e4a3c6d711792b1c46ab57bf35ed08b9a 8132 zim-tools_3.1.0-3_amd64.buildinfo
Checksums-Sha256:
 dc1c10c3928ba7e0a3e00be04aa2293ffb395efdf9229bd8f28bda53b80038cb 2104 
zim-tools_3.1.0-3.dsc
 1a377c15fe126c5082ef4426f7dbd1ff8a4d7dbad4f7925470631ee28559 13920 
zim-tools_3.1.0-3.debian.tar.xz
 709253e4bdaac21eca6b9e1da5ba3178b251ad1f3902eb12c2fb66afc629a8c2 8132 
zim-tools_3.1.0-3_amd64.buildinfo
Files:
 f16ddb3960f839f989395f595a33d638 2104 utils optional zim-tools_3.1.0-3.dsc
 54435c2a7cf63e8e976b5a88666845fa 13920 utils optional 
zim-tools_3.1.0-3.debian.tar.xz
 f9096405786e8e1e0e8bf510bd85264a 8132 utils optional 
zim-tools_3.1.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE2MtZ8F27ngU4xIGd8QX4EBsFJpsFAmH/GiYTHGxlZ29rdG1A
cmlzZXVwLm5ldAAKCRDxBfgQGwUmm/F4EACvELPr0f9mYn1wyrhzucza+dAYLvYt
R3gsh5NeNCNfL+axl8JAwxR9D8RFDjZob5FLry/Be/4gwh/q638dIy6xEPx6j+lF
mgV32x0Knf2D+5+OK5qdke3wf7KUNRu4rkGX0nGzSuHAIORv6GT1cJ6ve0Azo6ld
2Ug+1/0AwVhjWMcBZBI7wdY7N6IKVc6UI5I4PtRmdqEkXjffLXJM71zccGX+6iwY
493Eh2+51LPSdXGibKphIUpexIGAW0yV8GTvL9SamL9WrRcuBSzs1VJ6I5JR20Xv
meaYf7GFfu91kjmLYCF1ZcVGqT8noeIZg27jCoHxfr2OEwNLn9K73Cj82EkGdh+Q
S6Um/fHj8w3PjOAoBmyJ00BQeoHRBOTZMaMlSey7IuqCpmvK7ehyx9q5iR+AEVLd
HUD4xAyENaYhVlCDmiF9s76H0rfSCIFmW6efK6xqzZDAEwwHOX1OEQd1f1p5+cch
Dub3sbVhHoPo1CYCw/duvfy3wwxKtZeRCWzKoVMVJqZgnix0M5qbyv07do5w7an6
DEEtXOuftNwcaMfs54CLIRMC2sUJYHQhmzWyyAaJSy6tCQZ2ekysa89FG9GS3qts
W3vvwGgK3y/efOz78omC/AjfZ9Vp9fhW5sKr4Cld2aAFjrveaDmzwbxME2Cbedn8
uRKhHn9vpswKxw==
=Xvtu
-END PGP SIGNATURE End Message ---

Processed: reassign 1004918 to wnpp, reassign 1004954 to wnpp, reassign 1004924 to x11-xkb-utils ...

[Debian Bug Tracking System]

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

> reassign 1004918 wnpp
Bug #1004918 [php-slack] ITP:php-slack - PHP package for Slack
Warning: Unknown package 'php-slack'
Bug reassigned from package 'php-slack' to 'wnpp'.
Ignoring request to alter found versions of bug #1004918 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1004918 to the same values 
previously set
> reassign 1004954 wnpp
Bug #1004954 [php-bacon-qr-code] ITP:php-bacon-qr-code - QR Code generator
Warning: Unknown package 'php-bacon-qr-code'
Bug reassigned from package 'php-bacon-qr-code' to 'wnpp'.
Ignoring request to alter found versions of bug #1004954 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1004954 to the same values 
previously set
> reassign 1004924 x11-xkb-utils 7.7+5
Bug #1004924 [xkb] xkb: Alt key ceased working after last update
Warning: Unknown package 'xkb'
Bug reassigned from package 'xkb' to 'x11-xkb-utils'.
Ignoring request to alter found versions of bug #1004924 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1004924 to the same values 
previously set
Bug #1004924 [x11-xkb-utils] xkb: Alt key ceased working after last update
Marked as found in versions x11-xkb-utils/7.7+5.
> tags 1004170 + sid bookworm
Bug #1004170 [rust-rand-os] rust-rand-os - abandoned upstream should this 
package be removed?
Added tag(s) bookworm and sid.
> tags 1003479 + sid bookworm
Bug #1003479 [swig] swig: Missing support for php8.1
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

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

Bug#1005050: rust-csv - autopkgtest failure

[Peter Michael Green]

Package: rust-csv
Version: 1.1.5-2
Severity: serious

rust-csv's autopkgtest is failing, which is blocking it's migration to 
testing.



--- cookbook_read_basic stdout 
thread 'cookbook_read_basic' panicked at 'command spawns successfully: Os { code: 2, 
kind: NotFound, message: "No such file or directory" }', tests/tests.rs:412:33
stack backtrace:
0: rust_begin_unwind
  at /usr/src/rustc-1.56.0/library/std/src/panicking.rs:517:5
1: core::panicking::panic_fmt
  at /usr/src/rustc-1.56.0/library/core/src/panicking.rs:101:14
2: core::result::unwrap_failed
  at /usr/src/rustc-1.56.0/library/core/src/result.rs:1617:5
3: core::result::Result::expect
  at /usr/src/rustc-1.56.0/library/core/src/result.rs:1259:23
4: tests::cmd_output_with
  at ./tests/tests.rs:412:21
5: tests::cookbook_read_basic
  at ./tests/tests.rs:27:15
6: tests::cookbook_read_basic::{{closure}}
  at ./tests/tests.rs:25:1
7: core::ops::function::FnOnce::call_once
  at /usr/src/rustc-1.56.0/library/core/src/ops/function.rs:227:5
8: core::ops::function::FnOnce::call_once
  at /usr/src/rustc-1.56.0/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.
Doing some experiments running the tests manually, it appears the 
culprit is the "--all-targets" option
passed to cargo test by the autopkgtests. This seems to stop cargo from 
building the examples in a

runnable form.

I'm not sure what the best way forward here is, one could override 
debian/tests/control, but experiance
shows that is a maintinance burden, because debian/tests/control 
hardcodes the crate version.


The other option would be to just disable the tests in question. Not 
ideal but probablly not a disaster

either.

Does anyone have any better ideas?

Bug#1005011: lots of missing entries in debian/copyright

[Thorsten Alteholz]

Hi Tony,

On 05.02.22 17:26, tony mancill wrote:


I believe there is ambiguity here.  For this bug to be severity serious,
doesn't policy need to be revised to change "should" to "must" so that
it is clear that **every** upstream author **must** be enumerated in
debian/copyright?  If this is a requirement for software to be part of
Debian, policy should say so directly.


I am afraid you are mixing two different things here.
The paragraph above is about the header section of the machine readable 
copyright file. You are right, information about the upstream author must 
not be present there. This field is just meant to easily find a person to 
contact for this software.


The severity of the bug is related to §2.3 which says that 
debian/copyright must have "... verbatim copy of its distribution 
license(s) ...". This means that all copyright holder must be listed in 
the corresponding license blocks below the header. If some are missing, 
you both infringe policy and don't comply to the licenses. Both violations 
justify a severity of "serious".



In my personal opinion, policy requiring an exhaustive debian/copyright
is less useful for our users than functioning free software that
correctly documents the provenance of the software, albeit perhaps not
down to the detail of every individual who has ever contributed a line
of code.


I have to object here. If you work with open source software, you got some 
rights from the author, but you also have to fulfill some duties. One of 
the duties is to comply with the license the author has choosen. Most 
licenses require that you add information about the author to binary 
distributions of the software. In Debian this is achieved by adding 
debian/copyright to the binary package.
Our users benefit from this compilation as well. First, Debian gives them 
the right to further distribute the software, even only in binary form. 
But of course the users need to know under what conditions they are 
allowed to do this. Second, they can check whether Debian keeps a promise, 
namely point 1 of the Social Contract. Debian promises to distribute 100% 
free software. If you know of any other way how to achieve this goal, 
please let me know.



I expect that I could trivially find thousands of source
packages in the main archive for which such a requirement does not hold.


Ok, I challenge your word. Please file a bug for every incomplete 
debian/copyright.



But that is beside the point.  The point is that I don't understand the
policy basis upon which this bug is severity serious.


Ok, I hope my explanation above make things clearer now and I thank you 
for packaging open source software for Debian.


  Thorsten

Bug#1004606: marked as done (django-q: autopkgtest regression on armhf and i386)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 23:48:54 +
with message-id 
and subject line Bug#1004606: fixed in django-q 1.3.9-3
has caused the Debian Bug report #1004606,
regarding django-q: autopkgtest regression on armhf and i386
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.)


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

Source: django-q
Version: 1.3.9-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
django-q   from testing1.3.9-2
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

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

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


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

Paul

[0] You can see what packages were added from the second line of the log 
file quoted below. The migration software adds source package from 
unstable to the list if they are needed to install packages from 
django-q/1.3.9-2. I.e. due to versioned dependencies or breaks/conflicts.

[1] https://qa.debian.org/excuses.php?package=django-q

https://ci.debian.net/data/autopkgtest/testing/armhf/d/django-q/18808527/log.gz

=== FAILURES 
===
_ test_max_rss 
_


broker = 
monkeypatch = <_pytest.monkeypatch.MonkeyPatch object at 0xf44d7f28>

@pytest.mark.django_db
def test_max_rss(broker, monkeypatch):
# set up the Sentinel
broker.list_key = "test_max_rss_test:q"
async_task("django_q.tests.tasks.multiply", 2, 2, broker=broker)
start_event = Event()
stop_event = Event()
cluster_id = uuidlib.uuid4()
# override settings
monkeypatch.setattr(Conf, "MAX_RSS", 4)
monkeypatch.setattr(Conf, "WORKERS", 1)
# set a timer to stop the Sentinel
threading.Timer(3, stop_event.set).start()
s = Sentinel(stop_event, start_event, cluster_id=cluster_id, 
broker=broker)

assert start_event.is_set()
assert s.status() == Conf.STOPPED

  assert s.reincarnations == 1

E   assert 0 == 1
E+  where 0 = 0xf568e640>.reincarnations


tests/test_cluster.py:424: AssertionError
- Captured stderr call 
-

02:12:56 [Q] INFO Enqueued 1
02:12:56 [Q] DEBUG Pushed ('eight-louisiana-pasta-summer', 
'8aef005e7ce344a6845dacd8b847476e')

02:12:56 [Q] INFO Process-1305 ready for work at 3677
02:12:56 [Q] INFO Process-1306 monitoring at 3678
02:12:56 [Q] INFO MainProcess guarding cluster winter-wisconsin-oscar-one
02:12:56 [Q] INFO Process-1307 pushing tasks at 3679
02:12:56 [Q] INFO Q Cluster winter-wisconsin-oscar-one running.
02:12:56 [Q] DEBUG queueing from test_max_rss_test:q
02:12:56 [Q] INFO Process-1305 processing [eight-louisiana-pasta-summer]
02:12:56 [Q] INFO Processed [eight-louisiana-pasta-summer]
02:12:59 [Q] INFO MainProcess stopping cluster processes
02:13:00 [Q] INFO Process-1307 stopped pushing tasks
02:13:00 [Q] INFO Process-1305 stopped doing work
02:13:00 [Q] INFO Process-1306 stopped monitoring results
02:13:00 [Q] INFO MainProcess waiting for the monitor.
=== warnings summary 
===

../../../../usr/lib/python3/dist-packages/django_q/conf.py:139
  /usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: 
Retry and timeout are misconfigured. Set retry larger than timeout, 
  failure to do so will cause the tasks to be retriggered before 
completion.   See 
https://django-q.readthedocs.io/en/latest/configure.html#retry for details.

warn(

tests/test_scheduler.py::test_scheduler_atomic_transaction_must_specify_a_database_when_no_replicas_are_used
tests/test_scheduler.py::test_scheduler_atomic_transaction_must_specify_no_database_when_read_write_replicas_are_used

Processed: Bug#1004606 marked as pending in django-q

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1004606 [src:django-q] django-q: autopkgtest regression on armhf and i386
Added tag(s) pending.

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

Bug#1004606: marked as pending in django-q

[Pierre-Elliott Bécue]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/django-q/-/commit/5458c7fa4f8fc8bb48eec09f8db47931f547d1d8


d/p/0006: Decrease the MAX_RSS for the test_max_rss test

Closes: #1004606


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1004606

Bug#1004980: marked as done (libtbb12: missing Breaks+Replaces: libtbb2 (<< 2021))

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 23:22:26 +
with message-id 
and subject line Bug#1004980: fixed in onetbb 2021.5.0-2
has caused the Debian Bug report #1004980,
regarding libtbb12: missing Breaks+Replaces: libtbb2 (<< 2021)
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.)


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

Hi,

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

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

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

  Preparing to unpack .../libtbb12_2021.5.0-1_amd64.deb ...
  Unpacking libtbb12:amd64 (2021.5.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libtbb12_2021.5.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libtbbmalloc.so.2', which is 
also in package libtbb2:amd64 2020.3-1
  Errors were encountered while processing:
   /var/cache/apt/archives/libtbb12_2021.5.0-1_amd64.deb


If libtbb12 contains multiple libraries with different SOVERSIONs, you
should consider splitting the package further ...


cheers,

Andreas


libtbb2=2020.3-1_libtbb12=2021.5.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: onetbb
Source-Version: 2021.5.0-2
Done: Mo Zhou 

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated onetbb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 05 Feb 2022 17:57:13 -0500
Source: onetbb
Architecture: source
Version: 2021.5.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mo Zhou 
Closes: 1004980
Changes:
 onetbb (2021.5.0-2) experimental; urgency=medium
 .
   * Breaks+Replaces: libtbb2 (<< 2021). (Closes: #1004980)
   * B-D on cmake for all architectures.
   * Reintroduce remove-unaligned-test.patch to fix bus error during test.
Checksums-Sha1:
 0a5ee47922d372bda95d758b377d90b672b04481 2359 onetbb_2021.5.0-2.dsc
 74d8709c30599c8887a367e6a46c323ef055 13552 onetbb_2021.5.0-2.debian.tar.xz
 b836cd161fd0181f994bc2cdbe459c2c704e8345 8133 
onetbb_2021.5.0-2_source.buildinfo
Checksums-Sha256:
 28e656d74cbaf0225e925b731553000c69c466f2f7f2b9bdfe8fd8301829de4a 2359 
onetbb_2021.5.0-2.dsc
 0b19e74bb60b83a99bd99042564163b8f414990ab0c0105c037a220955b607c6 13552 
onetbb_2021.5.0-2.debian.tar.xz
 3337d979fd52290af6a51eb2067f879c83f092fef62b630e19a8f6ba3ac48096 8133 
onetbb_2021.5.0-2_source.buildinfo
Files:
 4db5167275a2a3d29b5bad9d07353c96 2359 libs optional onetbb_2021.5.0-2.dsc
 7203987a06351a76509c51b499a0008d 13552 libs optional 
onetbb_2021.5.0-2.debian.tar.xz
 b176a066f57a8938d6717f2cfd453098 8133 libs optional 
onetbb_2021.5.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAmH/AbYRHGx1bWluQGRl
Ymlhbi5vcmcACgkQYmRes19oaorYRA//Tm1LLq1Z534u0tKu8J6KZNntkpdKHqmy
HWRWofqrkPXJ8nYv7X+u08KDkagwjpBztPm72M1t/WgTijxz7o8V23y95tQyCtXF
Dv2rEHoKqIlDldIyF9tYRhhOXNpltba63S22PLdxPDVi4EkU1KMr+E/4cNgnfhV0
SD3siM9F1DPKSz2fFmjUoQ64jKW9SqOr6QFH7V10RZFmKDpPNCwI3c0PkrSyQDFY
TserklMl4Bo0IVtvtsNFOurGfyY4r0NbnpZbOgLD3V5oyMzuDVRx+LUTUq+9UWHt
RMzU6jXCiF3VGismoqIf4pJa22mfI71BuAc2XTiqD+1dOycAYg+f6j1+wxPGjrCE
QDAxzKafgXiLU7BTuXgl/Zwz1W6lrVL1iJzTHhMa6YO8qGH5I+koKJ/ra3DYtgcj
16DMba56MxR8cbZqGS8nFYJ/oxjVbGw0T6IWJMOu70Uh2SrkXuvWVGF973QaTNqo
1b48c4a1CPjC9ePEoum+KMFN6MFzbYClmWdnWaY/MruvudnhjoMw72mf1NeflJRB

Processed: tagging 1003291

[Debian Bug Tracking System]

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

> tags 1003291 + pending
Bug #1003291 [goobook] ModuleNotFoundError: No module named 'pkg_resources'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: biber breaks rubber autopkgtest: There were errors running biber.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1005033 [src:biber, src:rubber] biber breaks rubber autopkgtest: There 
were errors running biber.
Added tag(s) pending.

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

Bug#1005033: biber breaks rubber autopkgtest: There were errors running biber.

[Hilmar Preuße]

Control: tags -1 + pending

Am 05.02.2022 um 21:29 teilte Paul Gevers mit:

Hi,


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

Today I uploaded the biblatex release, which corresponds to the biber 
package. Hence the issue should be already solved. We just have to wait 
for another round of test results.


Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1005044: python3-subnettree: package completely broken, module won't load

[Michael Stone]

It seems to be some kind of incompatibility in swig. Upstream .cc files 
are built with swig 3, debian has swig 4. If the package is built with 
the upstream .cc files (ditching the associated lines in debian/rules) 
it seems to work fine.

Bug#1004157: marked as done (src:xtpcpp: fails to migrate to testing for too long: uploader built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 22:29:25 +
with message-id 
and subject line Bug#1004157: fixed in xtpcpp 0.4.43-1.1
has caused the Debian Bug report #1004157,
regarding src:xtpcpp: fails to migrate to testing for too long: uploader built 
arch:all binaries
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.)


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

Source: xtpcpp
Version: 0.4.18-1
Severity: serious
Control: close -1 0.4.43-1
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:xtpcpp has been trying to migrate for 61 
days [2]. Hence, I am filing this bug.


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: xtpcpp
Source-Version: 0.4.43-1.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated xtpcpp 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: Fri, 21 Jan 2022 22:29:02 +0100
Source: xtpcpp
Architecture: source
Version: 0.4.43-1.1
Distribution: unstable
Urgency: medium
Maintainer: The Debichem Group 
Changed-By: Paul Gevers 
Closes: 1004157
Changes:
 xtpcpp (0.4.43-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1004157)
Checksums-Sha1:
 de826644a92dc995bc6bf377fe2b8746395f985e 1972 xtpcpp_0.4.43-1.1.dsc
 d223b2c4b67fb84c9b51d1dc7af572cdd1f0af10 273552 xtpcpp_0.4.43-1.1.debian.tar.xz
Checksums-Sha256:
 d5c75fcaad389025a902bafe2fe29830806d13e306ea701d1ac19b61e290a9a6 1972 
xtpcpp_0.4.43-1.1.dsc
 78d0ee3d9f1ee16bf04512eb586fda98d50ebb7bf0c7a2fcf54e9e74ce607f96 273552 
xtpcpp_0.4.43-1.1.debian.tar.xz
Files:
 9c089c6c119bca61eb837b48c893865e 1972 science optional xtpcpp_0.4.43-1.1.dsc
 be8f719708397d6b50a77dd79300ba9e 273552 science optional 
xtpcpp_0.4.43-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmHrJcgACgkQnFyZ6wW9
dQoruggAg00M8F7l2zb+KezmT5C9sTJfGAyZIEUGw13WYlWHdwJf//qGQ91/sCcF
wVb1seYnmWsgpSwCOGej9fwrJbI014IcqdRxTzhhVhnJ/wR+0pydqEhksdnSrvxg
EnGQXqTHnISrvhJkOsAGs+fpI7WZIwM4GhLkuJcswegLXSQLo6Vq+XNlPCGgHWcQ
rvmU/7S24dhURr/xoqwZ1Wa70LCzWFPNj8zNhRK93UQNHhEs6y2oW7ZGI52SriiZ
yjc+vxpOYHO30Lut4GvlLOoUhMImmNtimh0a+NqR7csJpEPZEeG8Md2KeIWhG1f0
fa2PGAhOZfnKf95WBA8qZvYlwgix2A==
=pA6g
-END PGP 

Bug#1005044: python3-subnettree: package completely broken, module won't load

[Michael Stone]

Package: python3-subnettree
Version: 0.33-1+b3
Severity: grave
Justification: renders package unusable

Documentation says:

A simple example which associates CIDR prefixes with strings::

>>> import SubnetTree
>>> t = SubnetTree.SubnetTree()
>>> t["10.1.0.0/16"] = "Network 1"
>>> t["10.1.42.0/24"] = "Network 1, Subnet 42"
>>> print("10.1.42.1" in t)
True


But the version in bullseye (and 0.35 currently in unstable) produce:

Python 3.9.2 (default, Feb 28 2021, 17:03:44) 
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import SubnetTree
>>> t = SubnetTree.SubnetTree()
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/SubnetTree.py", line 82, in __init__
_SubnetTree.SubnetTree_swiginit(self, 
_SubnetTree.new_SubnetTree(binary_lookup_mode))
AttributeError: module '_SubnetTree' has no attribute 'SubnetTree_swiginit'
>>> 


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

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

Versions of packages python3-subnettree depends on:
ii  libc6   2.31-13+deb11u2
ii  libgcc-s1   10.2.1-6
ii  libstdc++6  10.2.1-6
ii  python3 3.9.2-3

python3-subnettree recommends no packages.

python3-subnettree suggests no packages.

-- no debconf information

Bug#999753: marked as done (wine-development: unsatisfiable build-dependency on unicode-data (< 14))

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 21:26:25 +
with message-id 
and subject line Bug#999753: fixed in wine-development 6.0+repack-2
has caused the Debian Bug report #999753,
regarding wine-development: unsatisfiable build-dependency on unicode-data (< 
14)
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.)


-- 
999753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wine-development
Version: 6.0+repack-1
Severity: serious
Usertag: edos-uninstallable

Hi, 

wine-development build-deoends on unicode-data (< 14) but the version in
testing and in sid is 14.0.0-1.1.

-Ralf.
--- End Message ---
--- Begin Message ---
Source: wine-development
Source-Version: 6.0+repack-2
Done: Michael Gilbert 

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

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

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated wine-development 
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, 04 Feb 2022 13:24:54 +
Source: wine-development
Architecture: source
Version: 6.0+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Closes: 991823 999753
Changes:
 wine-development (6.0+repack-2) unstable; urgency=medium
 .
   * Support building with gcc 11.
   * Support building with unicode-data 14 (closes: #999753).
   * Avoid deleting files outside of package source directory (closes: #991823).
 - Thanks to Bálint Réczey.
Checksums-Sha1:
 97a4b212619e515af8adf201b4a288b1d8c6751d 4697 wine-development_6.0+repack-2.dsc
 4eb94c7c346a28c208ca9cf3191801e9987b8fb3 5685804 
wine-development_6.0+repack-2.debian.tar.xz
 4158296a77eef1e4ad1f80bc10f64aa31859db41 18955 
wine-development_6.0+repack-2_source.buildinfo
Checksums-Sha256:
 e2013e9cf710c86c52f6f0ff8792f576aa0d682b0f7d7697bd236e0ec5567b91 4697 
wine-development_6.0+repack-2.dsc
 8b351910a01708bb716971f1a2960622e5b8bc5127fed3a50d2f0c21c138f644 5685804 
wine-development_6.0+repack-2.debian.tar.xz
 11297eba3f719c4e13e7cd8f76b6794721d5eaeb5585c8c5bbfc0fe3dbd2aff2 18955 
wine-development_6.0+repack-2_source.buildinfo
Files:
 221fb6430acb16abee05e66aca5e9ded 4697 otherosfs optional 
wine-development_6.0+repack-2.dsc
 528edfe3e16dbe71f551324bf7dedb96 5685804 otherosfs optional 
wine-development_6.0+repack-2.debian.tar.xz
 b89dc49dfe36a1da5f1de039cff4c6f7 18955 otherosfs optional 
wine-development_6.0+repack-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAmH+1TgACgkQmD40ZYkU
ayiIYCAAvcvgB+pizwdjKtgfK5US1kESpaxnW3OlgRaBjrl9Yq4VFXcXYPT/NymH
k568b9dM4D5J3Igrw+ngJ/DQ6mEwh+lGOkOsHaNRZzFyA3YkJs6YgDLcy7z8nifj
wjBGYYRPdlCtdE4O2WtPYQ7oyR4TJL9tkliNZtVQJ0er55gWTxmZPpaYoHwDFYKg
jQxRXYVmrP1sX79DsawOlP88dvE9jOf/ZueIeYZQAjt0VAxp8gJBvqNrGmcfN2wg
HY2v/DmUNO7QTKUzzkD0qhpdhx7l86rJ5WGbs70VcicNERutoqkofBoHSKCo3nc/
NwREMwwefPikF6xXtez7bGSATMMhDH1p2QQiVfRtq+MqJIhVQWOXdDGiPXVL63IG
1Gx14BKne/rjAY8YIt8ovZYHfrOvcr4RGudWSd0hwh8oQI8+Mp+F3AogqE8Y/GDC
FiXGjQRxS0vDEP1Ns2QQLXupz/xuRN3w9s35YHK3zgh9udEEFRu8jYGQbCRxUHia
algeiumXsq8XHPDIQMIzLIxK2WjB2qLSQiM8FytpyUQUzqj+w2+9CUJtSSex61mc
5yZqlp9GAq5PPJvHiQGmN0eGzOjTNiQWtjm00NXD9GFxhi8RO6vw1+eRnz7HljGN
XNN23y+hthVsbmc35XA1YFEPUWp/KJnBnRsa3AnuZ61Kq7IiiS3DF548e7C92owv
XJwuDB1dFZvv2UcTkVxfN8CNSialAg9HCcPoKX0ElES3wfMkQgiYDcEIlJwXVynO
UNzwjHGcRNoFA0KCOKwOBxj1yRjOelYm5W3nsLFZgu9pOebvPhxOU+yzcXF6S+8r
lZaZv2Y22JLzCedsIjg6ZZDqnsDNlooL3TgM+nGeCSVkM8iYnj+rkt2V10qoU4l3
rHWc/7btdGhwTMLG9XYUGvgqIJlV2I2abdNwOSg2OD4BY6c62j9D1htf15t+yvnM
6dkMPwP0CK3DPOuzar32j0/oFGsJ94V+CcbRB84FJTaknYmHWKr667sVsQX753Ps
d70xQVdiwkoxi2fjts6LHuOU+iyppTWkGuqumHLkV/dsJZbhIygHmGVdsKm4vWcg
jH2zGemJFWr4aNbLdX1oO5B1gvKZ8aHIPy4SlzVJJ5/NohgsxSZgf6OlHav+hPGe
beHPBwTPPJwznzRJr4McNcyuPOb9jRtRwcXR/poxfwr796xuLD8bmQz26AyoHn1f
kXP2vIwl7TShMdcTdTYFRD9UW9jJP9uo4Vy7Ks+lw6Mfprw6Ud1lkkXcZCYhkdnL
qQI/XWsN95rong/cNFfRVncseO0eKZuqgyvEInfaYYEIjQdBoAiyCBK0UvSYZ95e
pcepmxqgUNTSpBYRJM2DjHHuZZtGiQ==
=89Ol
-END PGP SIGNATURE End Message ---

Bug#991823: marked as done (src:wine: dh_auto_clean deletes unrelated files outside of package source)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 21:26:25 +
with message-id 
and subject line Bug#991823: fixed in wine-development 6.0+repack-2
has caused the Debian Bug report #991823,
regarding src:wine: dh_auto_clean deletes unrelated files outside of package 
source
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.)


-- 
991823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wine
Severity: critical
Version: 5.0.3-3

Hi,

The following snippet in debian/rules wiped out every package source
next to wine and the wine source dir itself, too, because my $HOME is
stored in git:

...
override_dh_auto_clean:
git clean -Xdf || true
...

It is not safe to assume that the package source is always a git directory.

Cheers,
Balint
--- End Message ---
--- Begin Message ---
Source: wine-development
Source-Version: 6.0+repack-2
Done: Michael Gilbert 

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated wine-development 
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, 04 Feb 2022 13:24:54 +
Source: wine-development
Architecture: source
Version: 6.0+repack-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Closes: 991823 999753
Changes:
 wine-development (6.0+repack-2) unstable; urgency=medium
 .
   * Support building with gcc 11.
   * Support building with unicode-data 14 (closes: #999753).
   * Avoid deleting files outside of package source directory (closes: #991823).
 - Thanks to Bálint Réczey.
Checksums-Sha1:
 97a4b212619e515af8adf201b4a288b1d8c6751d 4697 wine-development_6.0+repack-2.dsc
 4eb94c7c346a28c208ca9cf3191801e9987b8fb3 5685804 
wine-development_6.0+repack-2.debian.tar.xz
 4158296a77eef1e4ad1f80bc10f64aa31859db41 18955 
wine-development_6.0+repack-2_source.buildinfo
Checksums-Sha256:
 e2013e9cf710c86c52f6f0ff8792f576aa0d682b0f7d7697bd236e0ec5567b91 4697 
wine-development_6.0+repack-2.dsc
 8b351910a01708bb716971f1a2960622e5b8bc5127fed3a50d2f0c21c138f644 5685804 
wine-development_6.0+repack-2.debian.tar.xz
 11297eba3f719c4e13e7cd8f76b6794721d5eaeb5585c8c5bbfc0fe3dbd2aff2 18955 
wine-development_6.0+repack-2_source.buildinfo
Files:
 221fb6430acb16abee05e66aca5e9ded 4697 otherosfs optional 
wine-development_6.0+repack-2.dsc
 528edfe3e16dbe71f551324bf7dedb96 5685804 otherosfs optional 
wine-development_6.0+repack-2.debian.tar.xz
 b89dc49dfe36a1da5f1de039cff4c6f7 18955 otherosfs optional 
wine-development_6.0+repack-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEIwTlZiOEpzUxIyp4mD40ZYkUaygFAmH+1TgACgkQmD40ZYkU
ayiIYCAAvcvgB+pizwdjKtgfK5US1kESpaxnW3OlgRaBjrl9Yq4VFXcXYPT/NymH
k568b9dM4D5J3Igrw+ngJ/DQ6mEwh+lGOkOsHaNRZzFyA3YkJs6YgDLcy7z8nifj
wjBGYYRPdlCtdE4O2WtPYQ7oyR4TJL9tkliNZtVQJ0er55gWTxmZPpaYoHwDFYKg
jQxRXYVmrP1sX79DsawOlP88dvE9jOf/ZueIeYZQAjt0VAxp8gJBvqNrGmcfN2wg
HY2v/DmUNO7QTKUzzkD0qhpdhx7l86rJ5WGbs70VcicNERutoqkofBoHSKCo3nc/
NwREMwwefPikF6xXtez7bGSATMMhDH1p2QQiVfRtq+MqJIhVQWOXdDGiPXVL63IG
1Gx14BKne/rjAY8YIt8ovZYHfrOvcr4RGudWSd0hwh8oQI8+Mp+F3AogqE8Y/GDC
FiXGjQRxS0vDEP1Ns2QQLXupz/xuRN3w9s35YHK3zgh9udEEFRu8jYGQbCRxUHia
algeiumXsq8XHPDIQMIzLIxK2WjB2qLSQiM8FytpyUQUzqj+w2+9CUJtSSex61mc
5yZqlp9GAq5PPJvHiQGmN0eGzOjTNiQWtjm00NXD9GFxhi8RO6vw1+eRnz7HljGN
XNN23y+hthVsbmc35XA1YFEPUWp/KJnBnRsa3AnuZ61Kq7IiiS3DF548e7C92owv
XJwuDB1dFZvv2UcTkVxfN8CNSialAg9HCcPoKX0ElES3wfMkQgiYDcEIlJwXVynO
UNzwjHGcRNoFA0KCOKwOBxj1yRjOelYm5W3nsLFZgu9pOebvPhxOU+yzcXF6S+8r
lZaZv2Y22JLzCedsIjg6ZZDqnsDNlooL3TgM+nGeCSVkM8iYnj+rkt2V10qoU4l3
rHWc/7btdGhwTMLG9XYUGvgqIJlV2I2abdNwOSg2OD4BY6c62j9D1htf15t+yvnM
6dkMPwP0CK3DPOuzar32j0/oFGsJ94V+CcbRB84FJTaknYmHWKr667sVsQX753Ps
d70xQVdiwkoxi2fjts6LHuOU+iyppTWkGuqumHLkV/dsJZbhIygHmGVdsKm4vWcg
jH2zGemJFWr4aNbLdX1oO5B1gvKZ8aHIPy4SlzVJJ5/NohgsxSZgf6OlHav+hPGe
beHPBwTPPJwznzRJr4McNcyuPOb9jRtRwcXR/poxfwr796xuLD8bmQz26AyoHn1f

Bug#1002164: marked as done (rust-alacritty-terminal: FTBFS: build-dependency not installable: librust-signal-hook-registry-1.2+default-dev)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 21:25:14 +
with message-id 
and subject line Bug#1002164: fixed in rust-alacritty-terminal 0.16.0-1
has caused the Debian Bug report #1002164,
regarding rust-alacritty-terminal: FTBFS: build-dependency not installable: 
librust-signal-hook-registry-1.2+default-dev
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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-alacritty-config-derive-0.1+default-dev, 
> librust-base64-0.13+default-dev, librust-bitflags-1+default-dev, 
> librust-dirs-3+default-dev (>= 3.0.1-~~), librust-libc-0.2+default-dev, 
> librust-log-0.4+default-dev, librust-mio-0.6+default-dev, 
> librust-mio-extras-2+default-dev, librust-nix-0.23+default-dev, 
> librust-parking-lot-0.10+default-dev, librust-regex-automata-0.1+default-dev 
> (>= 0.1.8-~~), librust-serde-1+default-dev, librust-serde-1+derive-dev, 
> librust-serde-yaml-0.8+default-dev, librust-signal-hook-0.1+default-dev, 
> librust-signal-hook-0.1+mio-support-dev, 
> librust-unicode-width-0.1+default-dev, librust-vte-0.10-dev, build-essential, 
> fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, 
> libstd-rust-dev, librust-alacritty-config-derive-0.1+default-dev, 
> librust-base64-0.13+default-dev, librust-bitflags-1+default-dev, 
> librust-dirs-3+default-dev (>= 3.0.1-~~), librust-libc-0.2+default-dev, 
> librust-log-0.4+default-dev, librust-mio-0.6+default-dev, 
> librust-mio-extras-2+default-dev, librust-nix-0.23+default-dev, 
> librust-parking-lot-0.10+default-dev, librust-regex-automata-0.1+default-dev 
> (>= 0.1.8-~~), librust-serde-1+default-dev, librust-serde-1+derive-dev, 
> librust-serde-yaml-0.8+default-dev, librust-signal-hook-0.1+default-dev, 
> librust-signal-hook-0.1+mio-support-dev, 
> librust-unicode-width-0.1+default-dev, librust-vte-0.10-dev, build-essential, 
> fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [594 B]
> Get:5 copy:/<>/apt_archive ./ Packages [664 B]
> Fetched 2221 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  librust-signal-hook-dev : Depends: 
> librust-signal-hook-registry-1.2+default-dev but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/rust-alacritty-terminal_0.15.0-2_unstable.log

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: rust-alacritty-terminal
Source-Version: 0.16.0-1
Done: James McCoy 

We believe that the bug you reported is fixed in the 

Bug#1005011: lots of missing entries in debian/copyright

[Tom Lee]

Tony, without commenting on severity and policy concerns I'm happy to have
a first stab at this if you like.

And seconding Tony, thank you for the detailed review Thorsten!

On Sat, Feb 5, 2022 at 8:51 AM tony mancill  wrote:

> On Sat, Feb 05, 2022 at 12:08:03PM +, Thorsten Alteholz wrote:
> > Package: capnproto
> > please rework your debian/copyright. Especially
>
> Hi Thorsten,
>
> In my previous response, I neglected to say thank you for the thorough
> review of the package and its debian/copyright.  Thank you for the
> effort and detail you put into these reviews!
>
> Regards,
> tony
>


-- 
*Tom Lee */ http://tomlee.co / @tglee 

Bug#1005040: tortoize: Remove wrong hard-coded dependency on libcifpp1

[Steve Langasek]

Package: tortoize
Version: 2.0.5-1
Severity: serious
Tags: patch
Justification: uninstallable
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Hi Maarten,

The tortoize package has a hard-coded dependency on libcifpp1 listed in
debian/control.  It is always wrong to hard-code specific runtime libraries
in debian/control, and this now makes tortoize uninstallable with current
libcifpp, which has bumped its soname to libcifpp.so.2.

Please drop the reference to libcifpp1 as in the attached patch.

The hard-coded reference to libzeep5.1 is almost certainly also incorrect
but I have not verified this.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru tortoize-2.0.5/debian/control tortoize-2.0.5/debian/control
--- tortoize-2.0.5/debian/control   2022-02-04 22:41:14.0 -0800
+++ tortoize-2.0.5/debian/control   2022-02-05 12:32:24.0 -0800
@@ -22,7 +22,7 @@
 
 Package: tortoize
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libcifpp1, libzeep5.1
+Depends: ${shlibs:Depends}, ${misc:Depends}, libzeep5.1
 Description: Application to calculate ramachandran z-scores
  Tortoize validates protein structure models by checking the
  Ramachandran plot and side-chain rotamer distributions. Quality

Bug#1005036: deepdiff: autopkgtest failure on armhf and i386

[Paul Gevers]

Source: deepdiff
Version: 5.6.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

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


I copied some of the output at the bottom of this report. It seems that 
the reference in the test is expecting the test to run on a 64 bit system.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/i386/d/deepdiff/18967210/log.gz

=== python3.9 ===
= test session starts 
==

platform linux -- Python 3.9.10, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.9n6crap7/downtmp/autopkgtest_tmp
collected 645 items

tests/test_anyset.py . 
 [  0%]
tests/test_cache.py ss 
 [  1%]
tests/test_command.py ... 
 [  5%]
tests/test_delta.py  
[ 13%]
F 
 [ 18%]
tests/test_diff_math.py  
 [ 19%]
tests/test_diff_numpy.py  
 [ 20%]
tests/test_diff_other.py . 
 [ 22%]
tests/test_diff_text.py  
[ 29%]
sss. 
[ 40%]
... 
 [ 43%]
tests/test_diff_tree.py .s 
 [ 45%]
tests/test_distance.py .. 
 [ 51%]
tests/test_hash.py . 
[ 59%]
... 
 [ 63%]
tests/test_helper.py ... 
 [ 69%]
tests/test_ignore_order.py . 
[ 76%]
.. 
 [ 78%]
tests/test_lfucache.py  
 [ 79%]
tests/test_model.py . 
 [ 82%]
tests/test_operators.py  
 [ 83%]
tests/test_path.py  
 [ 85%]
tests/test_search.py ... 
[ 93%]
.. 
 [ 94%]
tests/test_serialization.py .. 
 [100%]


=== FAILURES 
===
_ 
TestNumpyDelta.test_numpy_delta_cases[delta_numpy7_arrays_of_different_sizes] 
_


self = 
t1 = array([1, 2, 3, 4]), t2 = array([ 5,  6,  7,  8,  9, 10])
deepdiff_kwargs = {}, to_delta_kwargs = {}
expected_delta_dict = {'_numpy_paths': {'root': 'int64'}, 
'iterable_item_added': {'root[4]': 9, 'root[5]': 10}, 'values_changed': 
{'root[0]': {'new_value': 5}, 'root[1]': {'new_value': 6}, 'root[2]': 
{'new_value': 7}, 'root[3]': {'new_value': 8}}}

expected_result = 't2'

@pytest.mark.parametrize(**DELTA_NUMPY_TEST_PARAMS)
def test_numpy_delta_cases(self, t1, t2, deepdiff_kwargs, 
to_delta_kwargs, expected_delta_dict, expected_result):

diff = DeepDiff(t1, t2, **deepdiff_kwargs)
delta_dict = diff._to_delta_dict(**to_delta_kwargs)
if expected_delta_dict:

  assert expected_delta_dict == delta_dict
E   AssertionError: assert {'_numpy_path...w_value': 8}}} == 
{'_numpy_path...w_value': 8}}}

E Omitting 2 identical items, use -vv to show
E Differing items:
E {'_numpy_paths': {'root': 'int64'}} != {'_numpy_paths': 
{'root': 'int32'}}

E Use -v to get the full diff

tests/test_delta.py:991: AssertionError
=== short test summary info 

FAILED 
tests/test_delta.py::TestNumpyDelta::test_numpy_delta_cases[delta_numpy7_arrays_of_different_sizes]
=== 1 failed, 638 passed, 6 skipped in 5.08s 
===

autopkgtest [09:10:54]: test unittests



OpenPGP_signature
Description: OpenPGP digital signature

Processed: biber breaks rubber autopkgtest: There were errors running biber.

[Debian Bug Tracking System]

Processing control commands:

> found -1 biber/2.17-1
Bug #1005033 [src:biber, src:rubber] biber breaks rubber autopkgtest: There 
were errors running biber.
Marked as found in versions biber/2.17-1.
> found -1 rubber/1.6.0-2
Bug #1005033 [src:biber, src:rubber] biber breaks rubber autopkgtest: There 
were errors running biber.
Marked as found in versions rubber/1.6.0-2.

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

Bug#1005033: biber breaks rubber autopkgtest: There were errors running biber.

[Paul Gevers]

Source: biber, rubber
Control: found -1 biber/2.17-1
Control: found -1 rubber/1.6.0-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
biber  from testing2.17-1
rubber from testing1.6.0-2
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rubber/18968283/log.gz

(cd tests && ./run.sh *)
When a test fails, please remove the /var/tmp/rubber-20220205-nb7OCD 
directory manually.

Test: asymptote-aux-overwritten
Running python3 -W error -X dev ../rubber.py   doc ...
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
running: asy doc-1.asy
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
nothing to be done for doc.tex
removing doc.dvi
removing doc.log
removing doc.aux
removing doc.pre
removing doc-1.asy
removing doc-1.eps
Test: asymptote-dvi
Running python3 -W error -X dev ../rubber.py   doc ...
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
running: asy doc-1.asy
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
nothing to be done for doc.tex
removing doc.dvi
removing doc.log
removing doc.aux
removing doc.pre
removing doc-1.asy
removing doc-1.eps
Test: asymptote-dvipdfm
Running python3 -W error -X dev ../rubber.py   doc ...
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
running: asy doc-1.asy
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
executing: dvipdfm doc.dvi
doc.dvi -> doc.pdf
[1]
3016 bytes written
nothing to be done for doc.tex
removing doc.dvi
removing doc.log
removing doc.aux
removing doc.pdf
removing doc.pre
removing doc-1.asy
removing doc-1.eps
Test: asymptote-dvips
Running python3 -W error -X dev ../rubber.py   doc ...
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
running: asy doc-1.asy
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
executing: dvips doc.dvi
This is dvips(k) 2021.1 (TeX Live 2022/dev)  Copyright 2021 Radical Eye 
Software (www.radicaleye.com)

' TeX output 2022.02.05:1012' -> doc.ps



. 
[1

<./doc-1.eps>] nothing to be done for doc.tex
removing doc.dvi
removing doc.log
removing doc.aux
removing doc.ps
removing doc.pre
removing doc-1.asy
removing doc-1.eps
Test: asymptote-dvips-ps2pdf
Running python3 -W error -X dev ../rubber.py   doc ...
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
running: asy doc-1.asy
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
executing: dvips doc.dvi
This is dvips(k) 2021.1 (TeX Live 2022/dev)  Copyright 2021 Radical Eye 
Software (www.radicaleye.com)

' TeX output 2022.02.05:1012' -> doc.ps



. 
[1

<./doc-1.eps>] running: ps2pdf doc.ps doc.pdf
nothing to be done for doc.tex
removing doc.dvi
removing doc.log
removing doc.aux
removing doc.ps
removing doc.pdf
removing doc.pre
removing doc-1.asy
removing doc-1.eps
Test: asymptote-inline-dvi
Running python3 -W error -X dev ../rubber.py   doc ...
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
running: asy doc-1.asy
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
nothing to be done for doc.tex
removing doc.dvi
removing doc.log
removing doc.aux
removing doc.pre
removing doc-1.asy
removing doc-1.tex
removing doc-1_0.eps
removing doc-1.pre
Test: asymptote-inline-dvipdfm
Running python3 -W error -X dev ../rubber.py   doc ...
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
running: asy doc-1.asy
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
executing: dvipdfm doc.dvi
doc.dvi -> doc.pdf
[1]
3016 bytes written
nothing to be done for doc.tex
removing doc.dvi
removing doc.log
removing doc.aux
removing doc.pdf
removing doc.pre
removing doc-1.asy
removing doc-1.tex
removing doc-1_0.eps
removing doc-1.pre
Test: asymptote-inline-dvips
Running python3 -W error -X dev ../rubber.py   doc ...
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
running: asy doc-1.asy
compiling doc.tex
executing: latex \nonstopmode \input{doc.tex}
executing: dvips doc.dvi
This is dvips(k) 2021.

Bug#1005032: ruby-hamster: autopkgtest regression: output differ

[Paul Gevers]

Source: ruby-hamster
Version: 3.0.0-4
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
ruby-hamster   from testing3.0.0-4
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-hamster/18964952/log.gz


Failures:

  1) Hamster.to_ruby with Hamster::SortedSet[] as input should return 
::SortedSet.new
 Failure/Error: Hamster.to_ruby(Hamster::SortedSet[]).should == 
::SortedSet.new


   expected: #
got: # (using ==)
 # ./spec/lib/hamster/nested/construction_spec.rb:85:in `block (4 
levels) in '


Finished in 13.72 seconds (files took 1.56 seconds to load)
4593 examples, 1 failure, 10 pending

Failed examples:

rspec ./spec/lib/hamster/nested/construction_spec.rb:84 # 
Hamster.to_ruby with Hamster::SortedSet[] as input should return 
::SortedSet.new


/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.lib lib
autopkgtest [07:11:17]: test gem2deb-test-runner



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003243: marked as done (wordpress: WordPress 5.8.3 Security Release)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 19:03:55 +
with message-id 
and subject line Bug#1003243: fixed in wordpress 5.0.15+dfsg1-0+deb10u1
has caused the Debian Bug report #1003243,
regarding wordpress: WordPress 5.8.3 Security Release
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.)


-- 
1003243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wordpress
Version: 5.8.2+dfsg1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team 

WordPress have released version 5.8.3 which fixes 4 security bugs.
https://wordpress.org/news/2022/01/wordpress-5-8-3-security-release/

 * An issue with stored XSS through post slugs.
   CVE-2022-21662 - Stored XSS through authenticated users
   
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-699q-3hj9-889w
   https://hackerone.com/reports/425342


 * An issue with Object injection in some multisite installations.
   CVE-2022-21663 - Authenticated Object Injection in Multisites
   
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-jmmq-m8p8-332h
   https://hackerone.com/reports/541469


 * A SQL injection vulnerability in WP_Query.
   CVE-2022-21661 - WordPress: SQL Injection through WP_Query
   
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-6676-cqfm-gw84
   https://hackerone.com/reports/1378209

 * A SQL injection vulnerability in WP_Meta_Query
   CVE-2022-21664 - SQL injection due to improper sanitization in WP_Meta_Query
   
https://github.com/WordPress/wordpress-develop/security/advisories/GHSA-jp3p-gw8h-6x86
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 5.0.15+dfsg1-0+deb10u1
Done: Craig Small 

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

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

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated wordpress package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 08 Jan 2022 08:06:09 +1100
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentynineteen 
wordpress-theme-twentyseventeen wordpress-theme-twentysixteen
Architecture: source all
Version: 5.0.15+dfsg1-0+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentynineteen - weblog manager - twentynineteen theme files
 wordpress-theme-twentyseventeen - weblog manager - twentyseventeen theme files
 wordpress-theme-twentysixteen - weblog manager - twentysixteen theme files
Closes: 1003243
Changes:
 wordpress (5.0.15+dfsg1-0+deb10u1) buster-security; urgency=high
 .
   * Upstream security release Closes: #1003243
  - CVE-2022-21662 - Stored XSS through authenticated users
  - CVE-2022-21663 - Authenticated Object Injection in Multisites
  - CVE-2022-21661 - WordPress: SQL Injection through WP_Query
  - CVE-2022-21664 - SQL injection due to improper sanitization
in WP_Meta_Query
Checksums-Sha1:
 4be07b5016ccd61feaca7b2a42e8e38ca865cee5 2481 
wordpress_5.0.15+dfsg1-0+deb10u1.dsc
 2551f5d788e3d51943a9fea2e794e41d9de9564c 7866164 
wordpress_5.0.15+dfsg1.orig.tar.xz
 2e7d90386e2688e20f859fda7b60e708f2424c3b 6819796 
wordpress_5.0.15+dfsg1-0+deb10u1.debian.tar.xz
 1f0e26c33409ca67b4b015b89cb02771ad3f537e 4386328 
wordpress-l10n_5.0.15+dfsg1-0+deb10u1_all.deb
 010775300dccc91b6f817c1876be0bfd4b27a495 307288 
wordpress-theme-twentynineteen_5.0.15+dfsg1-0+deb10u1_all.deb
 9b790ef59e675808a0464e8018908afc6cf999b1 946868 
wordpress-theme-twentyseventeen_5.0.15+dfsg1-0+deb10u1_all.deb
 82d6e240d5d486e80235562b25d11225fe318db7 594616 
wordpress-theme-twentysixteen_5.0.15+dfsg1-0+deb10u1_all.deb
 7a343345221c698602f68a69a5f81ab94b8024ae 6026352 
wordpress_5.0.15+dfsg1-0+deb10u1_all.deb
 099565b86fc4be1c076099c70eb2f20a5a21da53 7368 
wordpress_5.0.15+dfsg1-0+deb10u1_amd64.buildinfo

Bug#985263: marked as done (librust-num-bigint+quickcheck-macros-dev: depends on unavailable librust-quickcheck-macros-0.8-dev)

[Debian Bug Tracking System]

Your message dated Sat, 5 Feb 2022 18:32:47 +
with message-id <505e21fa-03f5-0f86-201d-fbc1f6511...@debian.org>
and subject line re: librust-num-bigint+quickcheck-macros-dev: depends on 
unavailable librust-quickcheck-macros-0.8-dev
has caused the Debian Bug report #985263,
regarding librust-num-bigint+quickcheck-macros-dev: depends on unavailable 
librust-quickcheck-macros-0.8-dev
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.)


-- 
985263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-num-bigint+quickcheck-macros-dev
Version: 0.2.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

  The following packages have unmet dependencies:
   librust-num-bigint+quickcheck-macros-dev : Depends: 
librust-quickcheck-macros-0.8-dev but it is not installable


Cheers,

Andreas
--- End Message ---
--- Begin Message ---

Version: 0.4.3-1

The librust-num-bigint+quickcheck-macros-dev binary package is gone
and the remaining binary package is installable in current sid.--- End Message ---

Processed: owner 1005011

[Debian Bug Tracking System]

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

> owner 1005011 !
Bug #1005011 [capnproto] lots of missing entries in debian/copyright
Owner recorded as tony mancill .
> thanks
Stopping processing here.

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

Bug#1004461: marked as done (python-anyio FTBFS on IPV6-only buildds)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 16:55:52 +
with message-id 
and subject line Bug#1004461: fixed in python-anyio 3.5.0-2
has caused the Debian Bug report #1004461,
regarding python-anyio FTBFS on IPV6-only buildds
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.)


-- 
1004461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-anyio
Version: 3.3.0-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-anyio=all

...
_ TestTLSListener.test_handshake_fail[asyncio] _
tests/streams/test_tls.py:328: in test_handshake_fail
listener = await create_tcp_listener(local_host='127.0.0.1')
anyio/_core/_sockets.py:236: in create_tcp_listener
gai_res = await getaddrinfo(local_host, local_port, family=family,  # type: 
ignore[arg-type]
anyio/_core/_sockets.py:419: in getaddrinfo
gai_res = await get_asynclib().getaddrinfo(encoded_host, port, 
family=family, type=type,
anyio/_backends/_asyncio.py:1570: in getaddrinfo
result = await get_running_loop().getaddrinfo(
/usr/lib/python3.9/asyncio/base_events.py:856: in getaddrinfo
return await self.run_in_executor(
/usr/lib/python3.9/concurrent/futures/thread.py:58: in run
result = self.fn(*self.args, **self.kwargs)
/usr/lib/python3.9/asyncio/base_events.py:839: in _getaddrinfo_debug
addrinfo = socket.getaddrinfo(host, port, family, type, proto, flags)
/usr/lib/python3.9/socket.py:954: in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
E   socket.gaierror: [Errno -9] Address family for hostname not supported
=== short test summary info 
SKIPPED [1] tests/test_taskgroups.py:57: could not import 'trio': No module 
named 'trio'
SKIPPED [1] tests/test_fileio.py:119: Drive only makes sense on Windows
SKIPPED [1] tests/test_fileio.py:159: Only makes sense on Windows
SKIPPED [2] tests/test_fileio.py:318: os.lchmod() is not available
=== 57 failed, 696 passed, 5 skipped, 2 deselected in 28.27s ===
E: pybuild pybuild:367: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.9/build; python3.9 -m pytest --verbose -W 
ignore -k "not test_is_block_device"
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 
--before-test "{interpreter} {dir}/setup.py egg_info 
--egg-base={dir}/.pybuild/egg" --test-pytest --test-args "--verbose -W ignore 
-k \"not test_is_block_device\"" returned exit code 13
make[1]: *** [debian/rules:14: override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: python-anyio
Source-Version: 3.5.0-2
Done: Julien Puydt 

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated python-anyio package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 05 Feb 2022 17:18:10 +0100
Source: python-anyio
Architecture: source
Version: 3.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julien Puydt 
Closes: 1004461
Changes:
 python-anyio (3.5.0-2) unstable; urgency=medium
 .
   * Add patch to disable IPv4 tests if not available (Closes: #1004461).
Checksums-Sha1:
 f9b2af012d9b061ca877e482618fcc89a6b26cba 2325 python-anyio_3.5.0-2.dsc
 b46bb7e8dca6d4a2089e24dc0d0b7aaa895b10b9 4976 
python-anyio_3.5.0-2.debian.tar.xz
 ce8d31fb33bbf09844073be0699b34c15a56ced5 8005 
python-anyio_3.5.0-2_source.buildinfo
Checksums-Sha256:
 c072ad2311a98b4c8a2da26d423c6fe8408d50050816b2f8aa8a2e2e9f7f9dfc 2325 
python-anyio_3.5.0-2.dsc
 1954f8f2903754bd7f8eed5e61c3c36c4b1537a9b76f2c0fabb0b272ed50d814 4976 
python-anyio_3.5.0-2.debian.tar.xz
 a200458d8e23981813c45a067fc1d16357fff2fb0598ac53e3ca7e102df15f45 8005 
python-anyio_3.5.0-2_source.buildinfo
Files:
 006969605b6c5f5b858d7256fccd730a 2325 python optional python-anyio_3.5.0-2.dsc
 53016bcf2cbf95b0cea582a4a7f7d187 

Bug#1005011: lots of missing entries in debian/copyright

[tony mancill]

On Sat, Feb 05, 2022 at 12:08:03PM +, Thorsten Alteholz wrote:
> Package: capnproto
> please rework your debian/copyright. Especially

Hi Thorsten,

In my previous response, I neglected to say thank you for the thorough
review of the package and its debian/copyright.  Thank you for the
effort and detail you put into these reviews!

Regards,
tony


signature.asc
Description: PGP signature

Processed: closing 1002153

[Debian Bug Tracking System]

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

> close 1002153 1.9.2-1
Bug #1002153 [src:rust-zbus] rust-zbus: FTBFS: build-dependency not 
installable: librust-zbus-macros-1.0.0+default-dev
Marked as fixed in versions rust-zbus/1.9.2-1.
Bug #1002153 [src:rust-zbus] rust-zbus: FTBFS: build-dependency not 
installable: librust-zbus-macros-1.0.0+default-dev
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1005011: lots of missing entries in debian/copyright

[tony mancill]

Hi Thorsten,

On Sat, Feb 05, 2022 at 12:08:03PM +, Thorsten Alteholz wrote:
> Package: capnproto
> Severity: serious
> Usertags: ftp
> thanks
> 
> Hi,
> 
> please rework your debian/copyright. Especially
> 
>  Kenton Varda
>  Cloudflare, Inc.
>  Google Inc.
>  Nathan C. Myers 
>  Philip Quinn
>  Ian Denhardt
>  Alexander Peslyak
> 
> need to be mentioned.
> Please also check other releases.

Thanks for the bug report.  I will get the debian/copyright updated in
the next upload.  However, I do have a question about the severity of
the bug, which implies that the package is in violation of Debian
policy.

First the bug severity as per
https://www.debian.org/Bugs/Developer#severities:

> serious
>
> is a severe violation of Debian policy (roughly, it violates
> a must or required directive), or, in the package maintainer's or
> release manager's opinion, makes the package unsuitable for release.

And are the sections of Debian policy that pertain to copyright:

- 2.3: 
https://www.debian.org/doc/debian-policy/ch-archive.html#copyright-considerations
- 4.5: 
https://www.debian.org/doc/debian-policy/ch-source.html#copyright-debian-copyright
- 12.5: 
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information
- 12.5.1: 
https://www.debian.org/doc/debian-policy/ch-docs.html#machine-readable-copyright-information

In section 12.5, it states (emphasis on **should** added):

> In addition, the copyright file must say where the upstream sources
> (if any) were obtained, and **should** include a name or contact
> address for the upstream authors. This can be the name of an
> individual or an organization, an email address, a web forum or
> bugtracker, or any other means to unambiguously identify who to
> contact to participate in the development of the upstream source code.

I believe there is ambiguity here.  For this bug to be severity serious,
doesn't policy need to be revised to change "should" to "must" so that
it is clear that **every** upstream author **must** be enumerated in
debian/copyright?  If this is a requirement for software to be part of
Debian, policy should say so directly.

In my personal opinion, policy requiring an exhaustive debian/copyright
is less useful for our users than functioning free software that
correctly documents the provenance of the software, albeit perhaps not
down to the detail of every individual who has ever contributed a line
of code.  I expect that I could trivially find thousands of source
packages in the main archive for which such a requirement does not hold.
But that is beside the point.  The point is that I don't understand the
policy basis upon which this bug is severity serious.

Thank you,
tony


signature.asc
Description: PGP signature

Bug#1005006: [Debichem-devel] Bug#1005006: avogadro: manipulation tools do not work

[Andrius Merkys]

Hi Fulvio,

On Sat, 5 Feb 2022, 13:03 fulvio ciriaco,  wrote:

> Package: avogadro
> Version: 1.95.1-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the
> past)
>
> clicking on bond centric manipulation or manipulation does nothing.
> the functionality of the mouse remains the same: rotate, translate,
> scale.


This seems to be a usability bug of successfully built and installed
package. Hence ftbfs tag and the justification you have provided do not
seem appropriate.

Andrius

Bug#1004671: marked as done (incompatible with current biblatex version)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 15:34:33 +
with message-id 
and subject line Bug#1004671: fixed in biber 2.17-2
has caused the Debian Bug report #1004671,
regarding incompatible with current biblatex version
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.)


-- 
1004671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: biber
Version: 2.17-1
Severity: grave
Justification: Renders package unusable
X-Debbugs-Cc: r...@debian.org

I'm not sure if this should instead be filed against
texlive-bibtex-extra, but the current version of biber is incompatible
with the biblatex package currently in Debian unstable. This effectively
renders biber useless and makes it impossible to compile documents that
use biblatex.

Attempting to compile the following MWE

\documentclass{article}
\usepackage[backend=biber]{biblatex}
\begin{document}
\printbibliography
\end{document}

results in

ERROR - Error: Found biblatex control file version 3.7, expected version 
3.8.
This means that your biber (2.17) and biblatex (3.16) versions are 
incompatible.

Here is the complete log:

This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) 
(preloaded format=pdflatex)
 restricted \write18 enabled.
entering extended mode
(./mwe.tex
LaTeX2e <2021-11-15> patch level 1
L3 programming layer <2021-11-22>
(/usr/share/texlive/texmf-dist/tex/latex/base/article.cls
Document Class: article 2021/10/04 v1.4n Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.sty
(/usr/share/texlive/texmf-dist/tex/generic/pdftexcmds/pdftexcmds.sty
(/usr/share/texlive/texmf-dist/tex/generic/infwarerr/infwarerr.sty)
(/usr/share/texlive/texmf-dist/tex/generic/iftex/iftex.sty)
(/usr/share/texlive/texmf-dist/tex/generic/ltxcmds/ltxcmds.sty))
(/usr/share/texlive/texmf-dist/tex/latex/etoolbox/etoolbox.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/kvoptions/kvoptions.sty
(/usr/share/texlive/texmf-dist/tex/generic/kvsetkeys/kvsetkeys.sty))
(/usr/share/texlive/texmf-dist/tex/latex/logreq/logreq.sty
(/usr/share/texlive/texmf-dist/tex/latex/logreq/logreq.def))
(/usr/share/texlive/texmf-dist/tex/latex/base/ifthen.sty)
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-dm.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-compat.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.def)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/bbx/numeric.bbx
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/bbx/standard.bbx))
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/cbx/numeric.cbx)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.cfg))
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-pdftex.def)
(./mwe.aux) (/usr/share/texlive/texmf-dist/tex/latex/biblatex/lbx/english.lbx)
(/usr/share/texlive/texmf-dist/tex/latex/l3kernel/expl3.sty)
(/usr/share/texlive/texmf-dist/tex/latex/biblatex/blx-case-expl3.sty
(/usr/share/texlive/texmf-dist/tex/latex/l3packages/xparse/xparse.sty))
(./mwe.bbl)

LaTeX Warning: Empty bibliography on input line 5.

(./mwe.aux) )
No pages of output.
Transcript written on mwe.log.
Use of uninitialized value in quotemeta at /usr/share/perl5/Biber/Config.pm 
line 228.
Use of uninitialized value $tool in concatenation (.) or string at 
/usr/share/perl5/Biber/Config.pm line 307.
INFO - This is Biber 2.17
INFO - Logfile is 'mwe.blg'
INFO - Reading 'mwe.bcf'
ERROR - Error: Found biblatex control file version 3.7, expected version 3.8.
This means that your biber (2.17) and biblatex (3.16) versions are incompatible.
See compat matrix in biblatex or biber PDF documentation.
INFO - ERRORS: 1

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

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

Versions of packages biber depends on:
ii  libautovivification-perl  0.18-1+b3
ii  libbusiness-isbn-perl 3.006-1
ii  libbusiness-ismn-perl 1.202-1
ii  libbusiness-issn-perl 1.004-1

Bug#1004994: marked as done (src:ibm-3270: fails to migrate to testing for too long: uploader built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 13:34:36 +
with message-id 
and subject line Bug#1004994: fixed in ibm-3270 4.1ga10-1.1
has caused the Debian Bug report #1004994,
regarding src:ibm-3270: fails to migrate to testing for too long: uploader 
built arch:all binaries
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.)


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

Source: ibm-3270
Version: 4.0ga14-1
Severity: serious
Control: close -1 4.1ga10-1
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:ibm-3270 has been trying to migrate for 61 
days [2]. Hence, I am filing this bug.


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ibm-3270
Source-Version: 4.1ga10-1.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated ibm-3270 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Feb 2022 14:08:43 +0100
Source: ibm-3270
Architecture: source
Version: 4.1ga10-1.1
Distribution: unstable
Urgency: medium
Maintainer: Philipp Kern 
Changed-By: Paul Gevers 
Closes: 1004994
Changes:
 ibm-3270 (4.1ga10-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1004994)
Checksums-Sha1:
 0dba233ef3f32a0cd0b20f804fe82f846508c83b 1951 ibm-3270_4.1ga10-1.1.dsc
 c63f8e69fca1eb9f4123286da97310a094458cd8 42816 
ibm-3270_4.1ga10-1.1.debian.tar.xz
Checksums-Sha256:
 f9e133c182fd32b6e52243ec43687f2ad16f901ce5cbd6734efce7189f5ec6ed 1951 
ibm-3270_4.1ga10-1.1.dsc
 ea3326937894522076cd44561ebed8148c52e37f013cf74df5dbea3e9a92f22a 42816 
ibm-3270_4.1ga10-1.1.debian.tar.xz
Files:
 08745002c5f4d09d2cb2fb3365290771 1951 net optional ibm-3270_4.1ga10-1.1.dsc
 e4e05ce99ee1025349561c136df16ba8 42816 net optional 
ibm-3270_4.1ga10-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmH+dyUACgkQnFyZ6wW9
dQr9Ogf/ZuJIw+NLFFaZioiTAbNNEfdoCl5k4JM1WuEkuDKCnm61fEDnjecqierg
cnrvuLgvEoJEE1JdRLKiD2X1O73r+Nmo4AOYeTpM9BLGZABSS4z72fl4P4zGW4e7
a15czcaC4d9f8jqhqT72OqxHf3OQqHcH7S4qFqqZmlDAznhd5e6xXNB1Rf0S5/DG
mosRkcPm14ZqI92TmNSm8tE1k6n5A5RTsS87qvE86bgAD5254w40CLHIaF61WCy1
CR+TGEyLe5loAM9UZs3529Vm8aR9L890G3ec7NERP2EiGmKu/K+TsFhjLIZ11PF2
/8LYDq3cQeUMLqML7rCIdMbOk3TRwA==

Bug#1005011: lots of missing entries in debian/copyright

[Thorsten Alteholz]

Package: capnproto
Severity: serious
Usertags: ftp
thanks

Hi,

please rework your debian/copyright. Especially

 Kenton Varda
 Cloudflare, Inc.
 Google Inc.
 Nathan C. Myers 
 Philip Quinn
 Ian Denhardt
 Alexander Peslyak

need to be mentioned.
Please also check other releases.

Thanks!
  Thorsten

Bug#1005004: lots of missing entries in debian/copyright

[Martin Pitt]

tag -1 moreinfo

Hallo Thorsten,

Thorsten Alteholz [2022-02-05  9:40 +]:
> please rework your debian/copyright. Especially everything from node_modules
> seems to be missing. Please also check other releases.

The webpack bits in dist/ are autogenerated, and we have spent quite some
effort to make sure that this is correct and up to date. Over the last year it
shrank significantly, as we were able to drop a lot of npm modules (such as
jquery, mustache, or PatternFly 3).

Indeed copyright for the three node_modules/ are missing (these are test
dependencies for the integration test); they are not shipped in debs, but in
the source package, so they should be mentioned. That part is clear.

However, your report sounds like you found other problems apart from
node_modules/ -- what are they? Do you have an example?

Thanks,

Martin

Bug#1004994: src:ibm-3270: fails to migrate to testing for too long: uploader built arch:all binaries

[Philipp Kern]

Hi Paul,

On 05.02.22 08:50, Paul Gevers wrote:
Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Feel free to accelerate this upload. Thanks!

Kind regards
Philipp Kern

Processed: severity of 1003479 is serious

[Debian Bug Tracking System]

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

> severity 1003479 serious
Bug #1003479 [swig] swig: Missing support for php8.1
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1005006: avogadro: manipulation tools do not work

[fulvio ciriaco]

Package: avogadro
Version: 1.95.1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)



clicking on bond centric manipulation or manipulation does nothing.
the functionality of the mouse remains the same: rotate, translate,
scale.

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

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

Versions of packages avogadro depends on:
ii  libavogadro2-1  1.95.1-6
ii  libc6   2.33-5
ii  libgcc-s1   11.2.0-14
ii  libqt5core5a5.15.2+dfsg-14
ii  libqt5gui5  5.15.2+dfsg-14
ii  libqt5network5  5.15.2+dfsg-14
ii  libqt5widgets5  5.15.2+dfsg-14
ii  libstdc++6  11.2.0-14

Versions of packages avogadro recommends:
ii  avogadro-utils  1.95.1-6
ii  molequeue   0.9.0-1+b1

avogadro suggests no packages.

-- no debconf information

Bug#1004972: marked as done (atd forgets to run a job in the queue)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 10:48:43 +
with message-id 
and subject line Bug#1004972: fixed in at 3.2.5-1
has caused the Debian Bug report #1004972,
regarding atd forgets to run a job in the queue
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.)


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

At 14:01:50, I submitted a job to be run at 14:03 (thus more than
2 hours ago), but this job has not been run and it is still in the
queue:

$ atq
502 Mon Feb 14 23:00:00 2022 a vinc17
503 Tue Feb 15 09:00:00 2022 a vinc17
507 Fri Feb  4 14:03:00 2022 a vinc17

# ls -l /var/spool/cron/atjobs
total 24
-rwx-- 1 vinc17 daemon 7340 2022-01-26 10:44:09 a001f601a25048
-rwx-- 1 vinc17 daemon 7340 2022-01-26 10:44:16 a001f701a252a0
-rwx-- 1 vinc17 daemon 7287 2022-02-04 14:01:50 a001fb01a215ef

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

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

Versions of packages at depends on:
ii  libc6   2.33-5
ii  libpam-runtime  1.4.0-11
ii  libpam0g1.4.0-11
ii  libselinux1 3.3-1+b1
ii  lsb-base11.1.0

Versions of packages at recommends:
ii  postfix [mail-transport-agent]  3.6.4-1

at suggests no packages.

-- Configuration Files:
/etc/at.deny [Errno 13] Permission denied: '/etc/at.deny'

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: at
Source-Version: 3.2.5-1
Done: Jose M Calhariz 

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

Debian distribution maintenance software
pp.
Jose M Calhariz  (supplier of updated at package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Feb 2022 10:03:59 +
Source: at
Architecture: source
Version: 3.2.5-1
Distribution: unstable
Urgency: medium
Maintainer: Jose M Calhariz 
Changed-By: Jose M Calhariz 
Closes: 1004972
Changes:
 at (3.2.5-1) unstable; urgency=medium
 .
   * Fix: atd forgets to run a job in the queue (Closes: #1004972), thank
 you Vincent Lefevre for the analisys and the fix.
Checksums-Sha1:
 1e88d18d823c0fc785533fc3316cda27690f75b0 1941 at_3.2.5-1.dsc
 ab60b97fb2d878d37a4eba9062a0a3e99f423334 132660 at_3.2.5.orig.tar.gz
 f76e22dd5e3b2322853591d9eb557c06eec40e12 21432 at_3.2.5-1.debian.tar.xz
 3b9f64b5631ce2316c62967c58729fee27395846 6296 at_3.2.5-1_amd64.buildinfo
Checksums-Sha256:
 4160b81c8c75231096ea74b021736df209bce077af989210dd5c163a4e65afdd 1941 
at_3.2.5-1.dsc
 bb066b389d7c9bb9d84a35738032b85c30cba7d949f758192adc72c9477fd3b8 132660 
at_3.2.5.orig.tar.gz
 713652a19d84ec18d40a65ea4d49bd5c63810fa348c7078398b5d92cda541822 21432 
at_3.2.5-1.debian.tar.xz
 ef7611b0836de5869aa48bd8f06626c384244b54780cbd491e0906242cb9909e 6296 
at_3.2.5-1_amd64.buildinfo
Files:
 4f3729e00b05589ade7c31a1ac08e357 1941 admin standard at_3.2.5-1.dsc
 ca3657a1c90d7c3d252e0bc17feddc6e 132660 admin standard at_3.2.5.orig.tar.gz
 5238ca022338426452231581c7224329 21432 admin standard at_3.2.5-1.debian.tar.xz
 136ffef82e70c12bb1a717f1923c4967 6296 admin standard at_3.2.5-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERkvHzUOf7l6LQJigNIp3jWiF748FAmH+UicACgkQNIp3jWiF
74/bFA/8DSVHU0pkQdpzYhukTdti4i+o7hqCo6lwoMndJigjcudSr/mzx/vUVGkh

Processed: severity of 993328 is serious

[Debian Bug Tracking System]

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

> # Perl 5.34 transition imminent
> severity 993328 serious
Bug #993328 [src:openscap] openscap: FTBFS with Perl 5.34: hardcodes Perl 
version 5.32
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1005004: lots of missing entries in debian/copyright

[Thorsten Alteholz]

Package: cockpit
Severity: serious
Usertags: ftp
thanks

Hi,

please rework your debian/copyright. Especially everything from 
node_modules seems to be missing. Please also check other releases.


Thanks!
  Thorsten

Processed: Re: Bug#1004671: incompatible with current biblatex version

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 biber
Bug #1004671 [texlive-bibtex-extra] incompatible with current biblatex version
Bug reassigned from package 'texlive-bibtex-extra' to 'biber'.
No longer marked as found in versions texlive-extra/2021.20211217-1.
Ignoring request to alter fixed versions of bug #1004671 to the same values 
previously set
> found -1 2.17-1
Bug #1004671 [biber] incompatible with current biblatex version
Marked as found in versions biber/2.17-1.

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

Bug#1004671: incompatible with current biblatex version

[Hilmar Preuße]

Control: reassign -1 biber
Control: found -1 2.17-1

Am 04.02.2022 um 22:42 teilte Hilmar Preuße mit:


Control: reassign -1 texlive-bibtex-extra
Control: found -1 2021.20211217-1
Control: tags -1 + pending

Maybe leave it better on the biber package to make sure, people don't 
install the biber upload, which broke the whole thing.


H.
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#994866: marked as done (gmerlin-data,libgmerlin-dev: both ship /usr/share/gmerlin/plugin.sym)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 10:00:14 +
with message-id 
and subject line Bug#994866: fixed in gmerlin 2.0.0~svn6298~dfsg0-1~exp1
has caused the Debian Bug report #994866,
regarding gmerlin-data,libgmerlin-dev: both ship /usr/share/gmerlin/plugin.sym
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.)


-- 
994866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gmerlin-data,libgmerlin-dev
Version: 1.2.0+svn6244~dfsg0-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package libgmerlin-dev:amd64.
  Preparing to unpack 
.../145-libgmerlin-dev_1.2.0+svn6244~dfsg0-1~exp1_amd64.deb ...
  Unpacking libgmerlin-dev:amd64 (1.2.0+svn6244~dfsg0-1~exp1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-MXWnBc/145-libgmerlin-dev_1.2.0+svn6244~dfsg0-1~exp1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/gmerlin/plugin.sym', which is also in 
package gmerlin-data 1.2.0+svn6244~dfsg0-1~exp1
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-MXWnBc/145-libgmerlin-dev_1.2.0+svn6244~dfsg0-1~exp1_amd64.deb


cheers,

Andreas


gmerlin-data=1.2.0+svn6244~dfsg0-1~exp1_libgmerlin-dev=1.2.0+svn6244~dfsg0-1~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gmerlin
Source-Version: 2.0.0~svn6298~dfsg0-1~exp1
Done: IOhannes m zmölnig (Debian/GNU) 

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
gmerlin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Feb 2022 16:41:32 +0100
Source: gmerlin
Binary: gmerlin gmerlin-data gmerlin-dbgsym gmerlin-plugins-base 
gmerlin-plugins-base-dbgsym libgmerlin-common libgmerlin-dev libgmerlin2 
libgmerlin2-dbgsym
Architecture: source all amd64
Version: 2.0.0~svn6298~dfsg0-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 gmerlin- multiformat media player
 gmerlin-data - multiformat media player - data files
 gmerlin-plugins-base - gmerlin plugins from the "base" set
 libgmerlin-common - core library for gmerlin - common runtime files
 libgmerlin-dev - core library for gmerlin - development files
 libgmerlin2 - core library for gmerlin - runtime files
Closes: 994866 1003785
Changes:
 gmerlin (2.0.0~svn6298~dfsg0-1~exp1) experimental; urgency=medium
 .
   * New upstream version 2.0.0~svn6298~dfsg0
 - Drop patches applied upstream
 - Refresh patches
   * Remove /usr/share/gmerlin/plugin.sym from gmerlin-data (Closes: #994866)
   * Add patch to fix FTBFS with format-security (Closes: #1003785)
   * Add patch for gmerlin-transcoder launcher
   * Rename libgmerlin0 to libgermlin2 to follow soname bump
 * Update symbols file
   * B-D on gavl>=2
   * Drop Breaks/Replaces relation against packages
 that are not even in oldoldstable
   * Use execute_before_dh_* instead of override_dh_*
   * Drop on-the-fly manpage generation
   * Drop lintian-override to gmerlin
   * Apply 'wrap-and-sort -ast'
   * Have d/watch mangle the version to 2.0.0~svn
   * Bump dates in d/copyright
 * Regenerate d/copyright_hints
Checksums-Sha1:
 288f744ac6c4aa82303043d9d143b5cfcb4d7ccc 2820 
gmerlin_2.0.0~svn6298~dfsg0-1~exp1.dsc
 92e4fc15d04f0464297453d43f842d502a4cf03e 3247208 
gmerlin_2.0.0~svn6298~dfsg0.orig.tar.xz
 4781aa63fb7e37abf9522940e77bc3d570d1d57a 27076 
gmerlin_2.0.0~svn6298~dfsg0-1~exp1.debian.tar.xz
 1e96350797f8af2c5f6660b2e904782699e0aaaf 2157824 
gmerlin-data_2.0.0~svn6298~dfsg0-1~exp1_all.deb
 049ad4bf253a81e49b448ee94341113f7dc3900c 409644 
gmerlin-dbgsym_2.0.0~svn6298~dfsg0-1~exp1_amd64.deb
 

Bug#1003785: marked as done (gmerlin: FTBFS: format not a string literal and no format arguments)

[Debian Bug Tracking System]

Your message dated Sat, 05 Feb 2022 10:00:14 +
with message-id 
and subject line Bug#1003785: fixed in gmerlin 2.0.0~svn6298~dfsg0-1~exp1
has caused the Debian Bug report #1003785,
regarding gmerlin: FTBFS: format not a string literal and no format arguments
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.)


-- 
1003785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gmerlin
Version: 1.2.0+svn6244~dfsg0-1~exp1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

gmerlin/experimental recently started to FTBFS after some toolchain
package or build dependency was updated (probably when the default
compiler was switched to GCC 11):

frontend_player_ncurses.c: In function 'draw_status':
frontend_player_ncurses.c:164:5: error: format not a string literal and no 
format arguments [-Werror=format-security]
  164 | mvwprintw(p->player_win, 2, p->win_w - 4, status_str);
  | ^


Andreas


gmerlin_1.2.0+svn6244~dfsg0-1~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gmerlin
Source-Version: 2.0.0~svn6298~dfsg0-1~exp1
Done: IOhannes m zmölnig (Debian/GNU) 

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

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

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
gmerlin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 03 Feb 2022 16:41:32 +0100
Source: gmerlin
Binary: gmerlin gmerlin-data gmerlin-dbgsym gmerlin-plugins-base 
gmerlin-plugins-base-dbgsym libgmerlin-common libgmerlin-dev libgmerlin2 
libgmerlin2-dbgsym
Architecture: source all amd64
Version: 2.0.0~svn6298~dfsg0-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 gmerlin- multiformat media player
 gmerlin-data - multiformat media player - data files
 gmerlin-plugins-base - gmerlin plugins from the "base" set
 libgmerlin-common - core library for gmerlin - common runtime files
 libgmerlin-dev - core library for gmerlin - development files
 libgmerlin2 - core library for gmerlin - runtime files
Closes: 994866 1003785
Changes:
 gmerlin (2.0.0~svn6298~dfsg0-1~exp1) experimental; urgency=medium
 .
   * New upstream version 2.0.0~svn6298~dfsg0
 - Drop patches applied upstream
 - Refresh patches
   * Remove /usr/share/gmerlin/plugin.sym from gmerlin-data (Closes: #994866)
   * Add patch to fix FTBFS with format-security (Closes: #1003785)
   * Add patch for gmerlin-transcoder launcher
   * Rename libgmerlin0 to libgermlin2 to follow soname bump
 * Update symbols file
   * B-D on gavl>=2
   * Drop Breaks/Replaces relation against packages
 that are not even in oldoldstable
   * Use execute_before_dh_* instead of override_dh_*
   * Drop on-the-fly manpage generation
   * Drop lintian-override to gmerlin
   * Apply 'wrap-and-sort -ast'
   * Have d/watch mangle the version to 2.0.0~svn
   * Bump dates in d/copyright
 * Regenerate d/copyright_hints
Checksums-Sha1:
 288f744ac6c4aa82303043d9d143b5cfcb4d7ccc 2820 
gmerlin_2.0.0~svn6298~dfsg0-1~exp1.dsc
 92e4fc15d04f0464297453d43f842d502a4cf03e 3247208 
gmerlin_2.0.0~svn6298~dfsg0.orig.tar.xz
 4781aa63fb7e37abf9522940e77bc3d570d1d57a 27076 
gmerlin_2.0.0~svn6298~dfsg0-1~exp1.debian.tar.xz
 1e96350797f8af2c5f6660b2e904782699e0aaaf 2157824 
gmerlin-data_2.0.0~svn6298~dfsg0-1~exp1_all.deb
 049ad4bf253a81e49b448ee94341113f7dc3900c 409644 
gmerlin-dbgsym_2.0.0~svn6298~dfsg0-1~exp1_amd64.deb
 599cf0a7d45308c5b97cdf1fee0da3d96d246c39 545516 
gmerlin-plugins-base-dbgsym_2.0.0~svn6298~dfsg0-1~exp1_amd64.deb
 7112758015fad55ec30d44f6d2217e52d9640295 185744 
gmerlin-plugins-base_2.0.0~svn6298~dfsg0-1~exp1_amd64.deb
 5a1b5b3c43b94f1d118bf316b99a1518fe5e9c44 21666 
gmerlin_2.0.0~svn6298~dfsg0-1~exp1_amd64.buildinfo
 b4c81144579939a8aa07e889c034c857b2da58b0 173672 

Bug#1004974: atftpd: Potential information leak in atftpd<0.7.5

[Andreas B. Mundt]

Hi Salvatore,

On Fri, Feb 04, 2022 at 09:17:04PM +0100, Salvatore Bonaccorso wrote:
> […]
> The issue has been assigned CVE-2021-46671.
> 
> Andreas, unless I miss something crucial, I think this issue can be
> fixed in the upcoming point releases and does not require a DSA.

With Johannes' help I was able to reproduce the bug:  It looks like
only very special circumstances lead to the described information
leak. (For example, with option '--verbose', it did not work).

So no DSA and a fix via proposed updates is perfectly fine.
PUs are tracked/asked for in #1004999 and #1005000. 

Thanks and best regards,

  Andi

Processed: re: rust-rand-os - abandoned upstream should this package be removed?

[Debian Bug Tracking System]

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

> severity 1004170 serious
Bug #1004170 [rust-rand-os] rust-rand-os - abandoned upstream should this 
package be removed?
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1002961: [Pkg-pascal-devel] Bug#1002961: src:castle-game-engine: fails to migrate to testing for too long: FTBFS on armel

[Paul Gevers]

Hi Abou,

On 05-02-2022 09:07, Abou Al Montacir wrote:
I don't know why as I verified on my machine that the script returns 0 
as exit code.
It complains about messages on stderr, does it consider writing to 
stderr as a n error?
In that case, is it possible to disable that? The test program is 
upstream maintained and I don't want to hack in it.


autopkgtest by default considers output on stderr as bad. You can 
disable that with the allow-stderr restriction.


(In hindsight, having the check for stderr as optional instead of 
default seems like it would have been better, but that ship sailed long 
ago).


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1002961: src:castle-game-engine: fails to migrate to testing for too long: FTBFS on armel

[Abou Al Montacir]

Hi Paul,

On Mon, 2022-01-24 at 00:16 +0100, Abou Al Montacir wrote:
> Hi Paul,
> 
> On Sun, 2022-01-02 at 16:30 +0100, Paul Gevers wrote:
> > ..
> > Moreover CGE upstream think we should abandon armel (and other non 
> > widely used architectures) as a target for CGE, but I think myself it is 
> > a good test for the compiler and tend to think we should  keep it.
> 
> I agree with you. However, as a Release Team member, I also want to 
> prevent packages from being out-of-sync for too long. So, what I suggest 
> in this case is to temporarily disable the test on armel until we have 
> figured out how to fix the situation. That way the package can migrate 
> to testing, without making the situation much worse there.
> Can you please review [1] before upload?
> 
> [1] 
> https://salsa.debian.org/pascal-team/castle-game-engine/-/commit/d9b628c179bb53868e3d0bf9adc0b271969a613b
Thanks for the review.

I've uploaded with the tests moved to CI and the script executed as expected,
but the CI system detects failure.
I don't know why as I verified on my machine that the script returns 0 as exit
code.
It complains about messages on stderr, does it consider writing to stderr as a n
error?
In that case, is it possible to disable that? The test program is upstream
maintained and I don't want to hack in it.
-- 
Cheers,
Abou Al Montacir



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

Bug#1004994: src:ibm-3270: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: ibm-3270
Version: 4.0ga14-1
Severity: serious
Control: close -1 4.1ga10-1
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:ibm-3270 has been trying to migrate for 61 
days [2]. Hence, I am filing this bug.


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:ibm-3270: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 4.1ga10-1
Bug #1004994 [src:ibm-3270] src:ibm-3270: fails to migrate to testing for too 
long: uploader built arch:all binaries
Marked as fixed in versions ibm-3270/4.1ga10-1.
Bug #1004994 [src:ibm-3270] src:ibm-3270: fails to migrate to testing for too 
long: uploader built arch:all binaries
Marked Bug as done

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