Bug#989344: closing 989344

[Jochen Sprickerhof]

close 989344 
thanks

Processed: closing 989344

[Debian Bug Tracking System]

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

> close 989344
Bug #989344 [src:ogre-1.12] libogre-1.12: package name does not match soname
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1007915: [Pkg-javascript-devel] Bug#1007915: node-wikibase-cli: incompatible with node-commander >= 8

[Andrius Merkys]

On 2022-03-30 07:50, Yadd wrote:
> /usr/bin/* links were wrong. I fixed all these issues

Thanks a lot!

Best,
Andrius

Bug#1008633: marked as done (node-spdx-license-ids: autopkgtest regression: Cannot find module 'fettuccine-class')

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 05:03:49 +
with message-id 
and subject line Bug#1008633: fixed in node-spdx-license-ids 3.0.11+repack1-1
has caused the Debian Bug report #1008633,
regarding node-spdx-license-ids: autopkgtest regression: Cannot find module 
'fettuccine-class'
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.)


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

Source: node-spdx-license-ids
Version: 3.0.11-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, since the start of 
2022, it started to fail in testing. I copied some of the output at the 
bottom of this report.


Failing tests are considered RC bugs by the release team.

Paul

[1] https://ci.debian.net/packages/n/node-spdx-license-ids/

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-spdx-license-ids/20269931/log.gz

autopkgtest [11:24:40]: test pkg-js-autopkgtest-require: 
/usr/share/pkg-js-autopkgtest/runner require
autopkgtest [11:24:40]: test pkg-js-autopkgtest-require: 
[---

# Using ./package.(json|yaml)
# Node module name is spdx-license-ids
# Test: require
#   Testing spdx-license-ids: SKIPPED
#   Testing get-spdx-license-ids: internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module 'fettuccine-class'
Require stack:
- /usr/share/nodejs/get-spdx-license-ids/index.js
- /tmp/autopkgtest-lxc.49dkppxa/downtmp/autopkgtest_tmp/[eval]
at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:815:15)

at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. 
(/usr/share/nodejs/get-spdx-license-ids/index.js:3:19)

at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1027:10)

at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
'/usr/share/nodejs/get-spdx-license-ids/index.js',
'/tmp/autopkgtest-lxc.49dkppxa/downtmp/autopkgtest_tmp/[eval]'
  ]
}
not ok
autopkgtest [11:24:42]: test pkg-js-autopkgtest-require: 
---]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-spdx-license-ids
Source-Version: 3.0.11+repack1-1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-spdx-license-ids package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 30 Mar 2022 06:46:53 +0200
Source: node-spdx-license-ids
Architecture: source
Version: 3.0.11+repack1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1008633
Changes:
 node-spdx-license-ids (3.0.11+repack1-1) unstable; urgency=medium
 .
   * Team upload
   * Drop component get-spdx-license-ids (Closes: #1008633) and repack
Checksums-Sha1: 
 e9c7977a071c0a68d459bcb1ce758c63cf27638c 2205 
node-spdx-license-ids_3.0.11+repack1-1.dsc
 dfca980388c2e4980d6a1db63507fdd260c68742 43763 
node-spdx-license-ids_3.0.11+repack1.orig.tar.gz
 44cbc52e22d9a9d3f47d70ca0501a470dc5bf384 3200 
node-spdx-license-ids_3.0.11+repack1-1.debian.tar.xz
Checksums-Sha256: 
 4543086e8320f65ab17a010c54c54c5a75f7eb7183b04eb8878528632ba1ae52 2205 
node-spdx-license-ids_3.0.11+repack1-1.dsc
 aa4e0bcbf7087f849383dabf2d190dfff0278eb28b5b5350458fbeb819a71b97 43763 
node-spdx-license-ids_3.0.11+repack1.orig.tar.gz
 71c2b27f9f6c90adfa94d65453fb3fc96b6dcc0e9fcc7d4354f36aa1f2e96455 3200 
node-spdx-license-ids_3.0.11+repack1-1.debian.tar.xz
Files: 
 555845f7c705f57304

Bug#1007915: [Pkg-javascript-devel] Bug#1007915: node-wikibase-cli: incompatible with node-commander >= 8

[Yadd]

On 29/03/2022 18:17, Yadd wrote:

On 29/03/2022 17:44, Yadd wrote:

Hi Andrius,

you fix is enough for commander 8, I'm currently writing commander 9 
patch


Fixed and pushed. However package looks unusable because all bin/* 
commands are not in $PATH. You could either:

  * install all commands in /usr/bin
  * or change path in /usr/bin/wd and /usr/bin/wb


/usr/bin/* links were wrong. I fixed all these issues

Processed: Bug#1008633 marked as pending in node-spdx-license-ids

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008633 [src:node-spdx-license-ids] node-spdx-license-ids: autopkgtest 
regression: Cannot find module 'fettuccine-class'
Added tag(s) pending.

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

Bug#1008633: marked as pending in node-spdx-license-ids

[Yadd]

Control: tag -1 pending

Hello,

Bug #1008633 in node-spdx-license-ids reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-spdx-license-ids/-/commit/f75f128a14d7d925c5bebd67814de7bca0e757c3


Drop component get-spdx-license-ids

Closes: #1008633


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008633

Bug#1008636: marked as done (cluster3: rebuild with Python 3.10 as default)

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 04:48:41 +
with message-id 
and subject line Bug#1008636: fixed in cluster3 1.59+ds-4
has caused the Debian Bug report #1008636,
regarding cluster3: rebuild with Python 3.10 as default
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.)


-- 
1008636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cluster3
Version: 1.59+ds-3
Severity: serious

cluster3 is not auto-builddable, so it requires a manual rebuild for the
python3.10-default transition. Please upload a build with Python 3.10 as
default.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: cluster3
Source-Version: 1.59+ds-4
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated cluster3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Mar 2022 21:32:28 -0700
Source: cluster3
Binary: cluster3 cluster3-dbgsym
Architecture: source amd64
Version: 1.59+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: tony mancill 
Description:
 cluster3   - Reimplementation of the Eisen-clustering software
Closes: 1008636
Changes:
 cluster3 (1.59+ds-4) unstable; urgency=medium
 .
   * Team upload.
   * Binary upload built against python3.10 (Closes: #1008636)
Checksums-Sha1:
 948ff4274f77bca1335f38edb2a95c5e92835565 2275 cluster3_1.59+ds-4.dsc
 0119994589632a6305ae0a6add50bf3dd6e7fe5d 289048 
cluster3_1.59+ds-4.debian.tar.xz
 09506c37f703f7e642418d56b6fdf88aa4cbffee 244480 
cluster3-dbgsym_1.59+ds-4_amd64.deb
 f41ebad063854f5e80d43562d39e6a8453b02c53 8780 
cluster3_1.59+ds-4_amd64.buildinfo
 4765881c6b9aa52e5f83f290a8f5a3b7cd4e2530 1460612 cluster3_1.59+ds-4_amd64.deb
Checksums-Sha256:
 54f3449a12d2a9a7662b0c6df4c612ef863f50189aeef99c54e5a721de79b2d5 2275 
cluster3_1.59+ds-4.dsc
 0f46b2b70e94d42ec211757b3cd7f002fd47adf0e4b7e109f51bd240ff9c0512 289048 
cluster3_1.59+ds-4.debian.tar.xz
 a27395582fb5a145d85f32d5574672544776482c8fda48cf4eca3b02d249afe4 244480 
cluster3-dbgsym_1.59+ds-4_amd64.deb
 0a6b522f79c5aa1f255ca5c3b2b62e5c0671da70b8dc179541459785996a3181 8780 
cluster3_1.59+ds-4_amd64.buildinfo
 a3e7a717642898e818251eee32ee4a9204efdc278070db6c3b13a17a5e864234 1460612 
cluster3_1.59+ds-4_amd64.deb
Files:
 d66839455f2e1f8beb1a05663a56aa4f 2275 non-free/science optional 
cluster3_1.59+ds-4.dsc
 aabe82f6ec18d7dd2bc9c5107b9534c1 289048 non-free/science optional 
cluster3_1.59+ds-4.debian.tar.xz
 d20c1fd27792c0f381ee646e2e4fad5e 244480 non-free/debug optional 
cluster3-dbgsym_1.59+ds-4_amd64.deb
 20c7962f4fcb537f79676ed5d12ac66b 8780 non-free/science optional 
cluster3_1.59+ds-4_amd64.buildinfo
 7ee9208a167a9d62b7c8112aaa348b13 1460612 non-free/science optional 
cluster3_1.59+ds-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmJD3q0UHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZudA//fOYEaTejE7yFKnNMTCCN2O6GwYHO
9SWpn1CnJGsYjBfxjtTJwXWDeS18TaEj+b1Q9dSKStBoD6qtnFhpmONvyMkYMGH2
QHY5pLqgcOnqo8ra8m3/YIkKuucuJzxsgaAaIAwRmjWDiscFadgLrUe9+xVsdM0L
Cmr3HUvujGF9FJFwMnFPzvNaxeQXMf4Jw4zpctlUh9raGyltUCuJzOwjy9UCyIWb
/vws2FXpqRPNSrkppottDMYK+CZ+saOWZWQzNBvrhQWwQp/htkFtKs3QlU9ni6mv
/Jk1ebZDOKdOxWLBAjZiuWbwz7NawGmFrvlHdViLg8gxwLTMtnZ2n2fycV+Wxb9G
qV3tiXlz2HenIIv1XhHy+i/ZiIcxmAy/EUoFuk/e4cy/7UyDAbU5pCy8XqTGTAak
GENprSakt04DuHPzZpsq0dhTESifJCFXHdmEp8frcLvRcJntQeTVf/4i1Uspnr3o
hKeQRM3EpbwsvQnNL/nwKHwdAO33V3OHDurVaN36ZEIpydqx9HQ1CvbrXr/vi1Vr
h8xaRJ1TOPzZ7juR0RWGeRB2vbz6ipj2i3gCoL8PqlK9QwfwiYWNZeq90MoqDkeH
faE1oCbiZHHKJUQSGYzvrR8sNNgzuz8rhgmF+BNzBc8UR4CA4RL09X9ezpFu6GhP
Q+LXc15a6X8tqVU=
=kTXv
-END PGP SIGNATURE End Message ---

Processed: block puppetserver itp by jruby

[Debian Bug Tracking System]

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

> block 830904 by 972230
Bug #830904 [wnpp] ITP: puppetserver -- the next-generation application for 
managing Puppet agents
830904 was blocked by: 964222 819811 976751
830904 was not blocking any bugs.
Added blocking bug(s) of 830904: 972230
> thanks
Stopping processing here.

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

Processed: bug 1006999 is forwarded to https://github.com/ialbert/plac/issues/71

[Debian Bug Tracking System]

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

> forwarded 1006999 https://github.com/ialbert/plac/issues/71
Bug #1006999 [src:python-plac] python-plac: Non-determinstically FTBFS on 
amd64/unstable due to timing in tests
Set Bug forwarded-to-address to 'https://github.com/ialbert/plac/issues/71'.
> thanks
Stopping processing here.

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

Bug#1008493: gnome-control-center and gnome-settings-daemon version mismatch makes keyboard shortcuts fail

[Daniel Kahn Gillmor]

On Tue 2022-03-29 19:09:50 +0100, Simon McVittie wrote:
> Major GNOME components are expected to be upgraded together, except for
> when that's unnecessary. That is an unsatisfying answer, but unfortunately
> it's the only true answer.

Thanks for the clarification, Simon, even if it's unsatisfying.  It's
disappointing to hear that about GNOME: i'd have expected the project
overall to have taken more time to think about API issues given the
amount of ecosystem knowledge (and dependency hell scars) that i'm sure
exists within the active developers.

I do understand the tradeoffs between rigidity and fluidity that you
describe, and how you can get unmanageable delays on one end, and hidden
breakage on the other. That tradeoff is precisely why i'm inclined to
gravitate toward declaring something API-like, even between "internal"
components.  I tend to think that approach will give the best balance
possible on that tradeoff, but i also recognize that getting there
requires some significant engineering investment (in both tooling and
training) if that's not already established practice.

>> GNOME typically does a good job in handling a novice user's behaviors
>> well without hassling them with confusing technical arcana, but that
>> means that silent and complete crashes like the one observed here just
>> look like unrecoverable breakage to the normal user who doesn't know
>> anything about stderr or how to launch settings from the terminal.
>
> Sorry, but that normal user probably should not be using unstable.

Agreed, the normal user is most likely to use a released version of
Ubuntu, which as you said is shipping a mixed set of packages.  Yikes!

Thanks very much for your work on GNOME, Simon!

   --dkg


signature.asc
Description: PGP signature

Bug#1008635: marked as done (atropos: ImportError: cannot import name 'Iterable' from 'collections' (/usr/lib/python3.10/collections/__init__.py))

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 21:49:08 +
with message-id 
and subject line Bug#1008635: fixed in atropos 1.1.31+dfsg-2
has caused the Debian Bug report #1008635,
regarding atropos: ImportError: cannot import name 'Iterable' from 
'collections' (/usr/lib/python3.10/collections/__init__.py)
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.)


-- 
1008635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: atropos
Version: 1.1.31+dfsg-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

atropos FTBFS with python 3.10

E   ImportError: cannot import name 'Iterable' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)
___ ERROR collecting .pybuild/cpython3_3.10/build/tests/test_trim.py ___
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.10/build/tests/test_trim.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_trim.py:2: in 
from atropos.adapters import Adapter, ColorspaceAdapter, PREFIX, BACK
atropos/adapters/__init__.py:13: in 
from atropos import align
atropos/align/__init__.py:7: in 
from atropos.util import RandomMatchProbability, reverse_complement
atropos/util/__init__.py:3: in 
from collections import OrderedDict, Iterable, Sequence
E   ImportError: cannot import name 'Iterable' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)
=== warnings summary ===
tests/test_paired.py:612
  /<>/.pybuild/cpython3_3.10/build/tests/test_paired.py:612: 
PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You 
can register custom marks to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html
@pytest.mark.timeout(10)

-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info 
ERROR tests/test_adapters.py
ERROR tests/test_align.py
ERROR tests/test_colorspace.py
ERROR tests/test_commands.py
ERROR tests/test_filters.py
ERROR tests/test_modifiers.py
ERROR tests/test_multicore.py
ERROR tests/test_qualtrim.py
ERROR tests/test_seqio.py
ERROR tests/test_trim.py
!!! Interrupted: 10 errors during collection !!!
 1 warning, 10 errors in 1.05s =
E: pybuild pybuild:367: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.10/build; python3.10 -m pytest tests
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 
"--before-test=ln -s /<>/tests/cut {build_dir}/tests && ln -s 
/<>/tests/data {build_dir}/tests" returned exit code 13

See
https://buildd.debian.org/status/fetch.php?pkg=atropos&arch=amd64&ver=1.1.31%2Bdfsg-1%2Bb1&stamp=1648449686&raw=0

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: atropos
Source-Version: 1.1.31+dfsg-2
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated atropos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Mar 2022 23:21:04 +0200
Source: atropos
Architecture: source
Version: 1.1.31+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1008635
Changes:
 atropos (1.1.31+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Add python3.10.patch.  (Closes: #1008635)
   * Cleanup d/patches/.
Checksums-Sha1:
 d052c1af4ee21db7b59ebda24d9000a0209c3cce 2178 atropos_1.1.31+dfsg-2.dsc
 06e84cd183707452e29b09e5f799c9b0741eade9 5960 
atropos_1.1.31+dfsg-2.debian.tar.xz
 0695d560f39e35b1fa358801ad6f91afede95bdc 8079 
a

Bug#1008641:

[Andreas Hasenack]

I believe these patches from upstream fix the build problem:

https://git.launchpad.net/ubuntu/+source/unbound/tree/debian/patches/python3.10.patch
https://git.launchpad.net/ubuntu/+source/unbound/tree/debian/patches/python3.10-2.patch

Bug#1008641: unbound: FTBFS: ./pythonmod/pythonmod.c:338: undefined reference to `_Py_fopen'

[Sebastian Ramacher]

Source: unbound
Version: 1.13.1-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

unbound FTBFS:

libtool: link: ( cd ".libs" && rm -f "libunbound.la" && ln -s 
"../libunbound.la" "libunbound.la" )
./libtool --tag=CC --mode=link gcc   -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/python3.10 -DSRCDIR=. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -pthread -I/usr/include/google -Wl,--as-needed 
-Wl,-z,relro -Wl,-z,now -o unbound acl_list.lo cachedump.lo daemon.lo 
shm_main.lo remote.lo stats.lo unbound.lo worker.lo  dns.lo infra.lo rrset.lo 
dname.lo msgencode.lo as112.lo msgparse.lo msgreply.lo packed_rrset.lo 
iterator.lo iter_delegpt.lo iter_donotq.lo iter_fwd.lo iter_hints.lo 
iter_priv.lo iter_resptype.lo iter_scrub.lo iter_utils.lo localzone.lo mesh.lo 
modstack.lo view.lo outbound_list.lo alloc.lo config_file.lo configlexer.lo 
configparser.lo fptr_wlist.lo edns.lo locks.lo log.lo mini_event.lo module.lo 
net_help.lo random.lo rbtree.lo regional.lo rtt.lo dnstree.lo lookup3.lo 
lruhash.lo slabhash.lo tcp_conn_limit.lo timehist.lo tube.lo winsock_event.lo 
autotrust.lo val_anchor.lo rpz.lo validator.lo val_kcache.lo val_kentry.lo 
val_neg.lo val_nsec3.lo val_nsec.lo val_secalgo.lo val_sigcrypt.lo val_utils.lo 
dns64.lo cachedb.lo redis.lo authzone.lo edns-subnet.lo subnetmod.lo 
addrtree.lo subnet-whitelist.lo pythonmod.lo pythonmod_utils.lo  dnstap.lo 
dnstap.pb-c.lo dnstap_fstrm.lo dtstream.lo respip.lo netevent.lo 
listen_dnsport.lo outside_network.lo ub_event.lo keyraw.lo sbuffer.lo 
wire2str.lo parse.lo parseutil.lo rrdef.lo str2wire.lo strlcat.lo strlcpy.lo 
arc4random.lo arc4random_uniform.lo arc4_lock.lo   -lssl -lprotobuf-c -levent 
-L/usr/lib/x86_64-linux-gnu -L/usr/lib/python3.10 -lpython3.10  -lsystemd 
-lcrypto 
libtool: link: gcc -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/python3.10 -DSRCDIR=. -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/include/google -Wl,--as-needed -Wl,-z -Wl,relro 
-Wl,-z -Wl,now -o unbound .libs/acl_list.o .libs/cachedump.o .libs/daemon.o 
.libs/shm_main.o .libs/remote.o .libs/stats.o .libs/unbound.o .libs/worker.o 
.libs/dns.o .libs/infra.o .libs/rrset.o .libs/dname.o .libs/msgencode.o 
.libs/as112.o .libs/msgparse.o .libs/msgreply.o .libs/packed_rrset.o 
.libs/iterator.o .libs/iter_delegpt.o .libs/iter_donotq.o .libs/iter_fwd.o 
.libs/iter_hints.o .libs/iter_priv.o .libs/iter_resptype.o .libs/iter_scrub.o 
.libs/iter_utils.o .libs/localzone.o .libs/mesh.o .libs/modstack.o .libs/view.o 
.libs/outbound_list.o .libs/alloc.o .libs/config_file.o .libs/configlexer.o 
.libs/configparser.o .libs/fptr_wlist.o .libs/edns.o .libs/locks.o .libs/log.o 
.libs/mini_event.o .libs/module.o .libs/net_help.o .libs/random.o 
.libs/rbtree.o .libs/regional.o .libs/rtt.o .libs/dnstree.o .libs/lookup3.o 
.libs/lruhash.o .libs/slabhash.o .libs/tcp_conn_limit.o .libs/timehist.o 
.libs/tube.o .libs/winsock_event.o .libs/autotrust.o .libs/val_anchor.o 
.libs/rpz.o .libs/validator.o .libs/val_kcache.o .libs/val_kentry.o 
.libs/val_neg.o .libs/val_nsec3.o .libs/val_nsec.o .libs/val_secalgo.o 
.libs/val_sigcrypt.o .libs/val_utils.o .libs/dns64.o .libs/cachedb.o 
.libs/redis.o .libs/authzone.o .libs/edns-subnet.o .libs/subnetmod.o 
.libs/addrtree.o .libs/subnet-whitelist.o .libs/pythonmod.o 
.libs/pythonmod_utils.o .libs/dnstap.o .libs/dnstap.pb-c.o .libs/dnstap_fstrm.o 
.libs/dtstream.o .libs/respip.o .libs/netevent.o .libs/listen_dnsport.o 
.libs/outside_network.o .libs/ub_event.o .libs/keyraw.o .libs/sbuffer.o 
.libs/wire2str.o .libs/parse.o .libs/parseutil.o .libs/rrdef.o .libs/str2wire.o 
.libs/strlcat.o .libs/strlcpy.o .libs/arc4random.o .libs/arc4random_uniform.o 
.libs/arc4_lock.o  -lssl -lprotobuf-c -levent -L/usr/lib/x86_64-linux-gnu 
-L/usr/lib/python3.10 -lpython3.10 -lsystemd -lcrypto -pthread 
/usr/bin/ld: .libs/pythonmod.o: in function `pythonmod_init':
./pythonmod/pythonmod.c:338: undefined reference to `_Py_fopen'
/usr/bin/ld: ./pythonmod/pythonmod.c:371: undefined reference to 
`PyParser_SimpleParseFile'
collect2: error: ld returned 1 exit status
make[1]: *** [Makefile:350: unbound] Error 1

See
https://buildd.debian.org/status/fetch.php?pkg=unbound&arch=amd64&ver=1.13.1-1%2Bb1&stamp=1648466560&raw=0

Cheers
-- 
Sebastian Ramacher

Bug#1008640: scikit-fmm: FTBFS: /usr/include/python3.10/object.h:133:33: error: lvalue required as increment operand

[Sebastian Ramacher]

Source: scikit-fmm
Version: 2019.1.30-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

scikit-fmm FTBFS:

compile options: '-I/usr/lib/python3/dist-packages/numpy/core/include 
-Ibuild/src.linux-x86_64-3.9/numpy/distutils/include -I/usr/include/python3.9 
-c'
extra options: '-msse -msse2 -msse3'
x86_64-linux-gnu-g++: skfmm/pheap.cpp
x86_64-linux-gnu-g++: skfmm/heap.cpp
In file included from /usr/include/python3.10/Python.h:74,
 from skfmm/pheap.cpp:16:
skfmm/pheap.cpp: In function ‘void 
__pyx_tp_dealloc_5skfmm_5pheap_pheap(PyObject*)’:
/usr/include/python3.10/object.h:133:33: error: lvalue required as increment 
operand
  133 | #define Py_REFCNT(ob) _Py_REFCNT(_PyObject_CAST_CONST(ob))
  |   ~~^~
skfmm/pheap.cpp:1257:7: note: in expansion of macro ‘Py_REFCNT’
 1257 | ++Py_REFCNT(o);
  |   ^
/usr/include/python3.10/object.h:133:33: error: lvalue required as decrement 
operand
  133 | #define Py_REFCNT(ob) _Py_REFCNT(_PyObject_CAST_CONST(ob))
  |   ~~^~
skfmm/pheap.cpp:1260:7: note: in expansion of macro ‘Py_REFCNT’
 1260 | --Py_REFCNT(o);
  |   ^
In file included from /usr/include/python3.10/unicodeobject.h:1046,
 from /usr/include/python3.10/Python.h:83,
 from skfmm/pheap.cpp:16:
skfmm/pheap.cpp: In function ‘int __Pyx_ParseOptionalKeywords(PyObject*, 
PyObject***, PyObject*, PyObject**, Py_ssize_t, const char*)’:
/usr/include/python3.10/cpython/unicodeobject.h:451:61: warning: ‘Py_ssize_t 
_PyUnicode_get_wstr_length(PyObject*)’ is deprecated [-Wdeprecated-declarations]
  451 | #define PyUnicode_WSTR_LENGTH(op) 
_PyUnicode_get_wstr_length((PyObject*)op)
  |   
~~^~~
/usr/include/python3.10/cpython/unicodeobject.h:261:7: note: in expansion of 
macro ‘PyUnicode_WSTR_LENGTH’
  261 |   PyUnicode_WSTR_LENGTH(op) :\
  |   ^
skfmm/pheap.cpp:1598:22: note: in expansion of macro ‘PyUnicode_GET_SIZE’
 1598 | (PyUnicode_GET_SIZE(**name) != 
PyUnicode_GET_SIZE(key)) ? 1 :
  |  ^~
/usr/include/python3.10/cpython/unicodeobject.h:446:26: note: declared here
  446 | static inline Py_ssize_t _PyUnicode_get_wstr_length(PyObject *op) {
  |  ^~
/usr/include/python3.10/cpython/unicodeobject.h:262:33: warning: ‘Py_UNICODE* 
PyUnicode_AsUnicode(PyObject*)’ is deprecated [-Wdeprecated-declarations]
  262 |   ((void)PyUnicode_AsUnicode(_PyObject_CAST(op)),\
  |  ~~~^~~~
skfmm/pheap.cpp:1598:22: note: in expansion of macro ‘PyUnicode_GET_SIZE’
 1598 | (PyUnicode_GET_SIZE(**name) != 
PyUnicode_GET_SIZE(key)) ? 1 :
  |  ^~
/usr/include/python3.10/cpython/unicodeobject.h:580:45: note: declared here
  580 | Py_DEPRECATED(3.3) PyAPI_FUNC(Py_UNICODE *) PyUnicode_AsUnicode(
  | ^~~
/usr/include/python3.10/cpython/unicodeobject.h:451:61: warning: ‘Py_ssize_t 
_PyUnicode_get_wstr_length(PyObject*)’ is deprecated [-Wdeprecated-declarations]
  451 | #define PyUnicode_WSTR_LENGTH(op) 
_PyUnicode_get_wstr_length((PyObject*)op)
  |   
~~^~~
/usr/include/python3.10/cpython/unicodeobject.h:264:8: note: in expansion of 
macro ‘PyUnicode_WSTR_LENGTH’
  264 |PyUnicode_WSTR_LENGTH(op)))
  |^
skfmm/pheap.cpp:1598:22: note: in expansion of macro ‘PyUnicode_GET_SIZE’
 1598 | (PyUnicode_GET_SIZE(**name) != 
PyUnicode_GET_SIZE(key)) ? 1 :
  |  ^~
/usr/include/python3.10/cpython/unicodeobject.h:446:26: note: declared here
  446 | static inline Py_ssize_t _PyUnicode_get_wstr_length(PyObject *op) {
  |  ^~
/usr/include/python3.10/cpython/unicodeobject.h:451:61: warning: ‘Py_ssize_t 
_PyUnicode_get_wstr_length(PyObject*)’ is deprecated [-Wdeprecated-declarations]
  451 | #define PyUnicode_WSTR_LENGTH(op) 
_PyUnicode_get_wstr_length((PyObject*)op)
  |   
~~^~~
/usr/include/python3.10/cpython/unicodeobject.h:261:7: note: in expansion of 
macro ‘PyUnicode_WSTR_LENGTH’
  261 |   PyUnicode_WSTR_LENGTH(op) :\
  |   ^
skfmm/pheap.cpp:1598:52: note: in expansion of macro ‘PyUnicode_GET_SIZE’
 1598 | (PyUnicode_GET_SIZE(**name) != 
PyUnicode_GET_SIZE(key)) ? 1 :
  |^~~~

Bug#1008639: libsigrokdecode: FTBFS: ./.libs/libsigrokdecode.so: undefined reference to `PyList_Insert'

[Sebastian Ramacher]

Source: libsigrokdecode
Version: 0.5.3-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

libsigrokdecode FTBFS:

/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyList_Insert'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyModule_AddObject'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PySys_GetObject'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyDict_SetItemString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyType_GenericNew'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyImport_Import'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyList_GetItem'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyBytes_AsStringAndSize'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_CallMethod'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyGILState_Release'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyBytes_Size'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyBool_FromLong'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyUnicode_FromString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_CallFunctionObjArgs'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyExc_TypeError'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`Py_InitializeEx'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyExc_Exception'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyObject_Str'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_Next'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyLong_AsLong'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyModule_AddIntConstant'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyErr_Format'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyFloat_FromDouble'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyArg_ParseTuple'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyErr_Occurred'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PySet_Pop'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_IsSubclass'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyArg_ParseTupleAndKeywords'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyFloat_Type'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyExc_IndexError'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyEval_InitThreads'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`_Py_FalseStruct'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyEval_RestoreThread'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyBytes_AsString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyType_FromSpec'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `_Py_TrueStruct'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyEval_SaveThread'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_Size'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PySequence_GetItem'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_GetItem'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PySequence_Size'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyList_Size'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyType_IsSubtype'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `Py_DecRef'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyGILState_Ensure'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyErr_NormalizeException'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_CallObject'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyType_GetFlags'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyErr_Fetch'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyFloat_AsDouble'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PySequence_Check'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyLong_AsSize_t'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PySet_Add'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `Py_BuildValue'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_GetAttrString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to `PyLong_Type'
/usr/bin/ld: ./.libs/libsigrokdecode.so: undefined reference to 
`PyObject_SetAttrString'
/usr/bin/ld: ./.libs/libsigrokdecode.so: 

Bug#1008638: ldns: FTBFS: checking for the distutils Python package... no

[Sebastian Ramacher]

Source: ldns
Version: 1.7.1-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

ldns FTBFS:

checking for the distutils Python package... no
configure: error: cannot import Python module "distutils".
Please check your Python installation. The error was:
:1: DeprecationWarning: The distutils package is deprecated and slated 
for removal in Python 3.12. Use setuptools or check PEP 632 for potential 
alternatives


See
https://buildd.debian.org/status/fetch.php?pkg=ldns&arch=amd64&ver=1.7.1-2%2Bb2&stamp=1648456911&raw=0

Cheers
-- 
Sebastian Ramacher

Bug#1008637: crossfire: cfpython.c:63:10: fatal error: node.h: No such file or directory

[Sebastian Ramacher]

Source: crossfire
Version: 1.75.0-3
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

crossfire FTBFS:

cfpython.c:63:10: fatal error: node.h: No such file or directory
   63 | #include 
  |  ^~~~
compilation terminated.


See
https://buildd.debian.org/status/fetch.php?pkg=crossfire&arch=amd64&ver=1.75.0-3%2Bb1&stamp=1648451503&raw=0

Cheers
-- 
Sebastian Ramacher

Bug#1008636: cluster3: rebuild with Python 3.10 as default

[Sebastian Ramacher]

Source: cluster3
Version: 1.59+ds-3
Severity: serious

cluster3 is not auto-builddable, so it requires a manual rebuild for the
python3.10-default transition. Please upload a build with Python 3.10 as
default.

Cheers
-- 
Sebastian Ramacher

Bug#1008635: atropos: ImportError: cannot import name 'Iterable' from 'collections' (/usr/lib/python3.10/collections/__init__.py)

[Sebastian Ramacher]

Source: atropos
Version: 1.1.31+dfsg-1
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)

atropos FTBFS with python 3.10

E   ImportError: cannot import name 'Iterable' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)
___ ERROR collecting .pybuild/cpython3_3.10/build/tests/test_trim.py ___
ImportError while importing test module 
'/<>/.pybuild/cpython3_3.10/build/tests/test_trim.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_trim.py:2: in 
from atropos.adapters import Adapter, ColorspaceAdapter, PREFIX, BACK
atropos/adapters/__init__.py:13: in 
from atropos import align
atropos/align/__init__.py:7: in 
from atropos.util import RandomMatchProbability, reverse_complement
atropos/util/__init__.py:3: in 
from collections import OrderedDict, Iterable, Sequence
E   ImportError: cannot import name 'Iterable' from 'collections' 
(/usr/lib/python3.10/collections/__init__.py)
=== warnings summary ===
tests/test_paired.py:612
  /<>/.pybuild/cpython3_3.10/build/tests/test_paired.py:612: 
PytestUnknownMarkWarning: Unknown pytest.mark.timeout - is this a typo?  You 
can register custom marks to avoid this warning - for details, see 
https://docs.pytest.org/en/stable/mark.html
@pytest.mark.timeout(10)

-- Docs: https://docs.pytest.org/en/stable/warnings.html
=== short test summary info 
ERROR tests/test_adapters.py
ERROR tests/test_align.py
ERROR tests/test_colorspace.py
ERROR tests/test_commands.py
ERROR tests/test_filters.py
ERROR tests/test_modifiers.py
ERROR tests/test_multicore.py
ERROR tests/test_qualtrim.py
ERROR tests/test_seqio.py
ERROR tests/test_trim.py
!!! Interrupted: 10 errors during collection !!!
 1 warning, 10 errors in 1.05s =
E: pybuild pybuild:367: test: plugin distutils failed with: exit code=2: cd 
/<>/.pybuild/cpython3_3.10/build; python3.10 -m pytest tests
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 
"--before-test=ln -s /<>/tests/cut {build_dir}/tests && ln -s 
/<>/tests/data {build_dir}/tests" returned exit code 13

See
https://buildd.debian.org/status/fetch.php?pkg=atropos&arch=amd64&ver=1.1.31%2Bdfsg-1%2Bb1&stamp=1648449686&raw=0

Cheers
-- 
Sebastian Ramacher

Bug#1008611: bambam autopkgtest failure with pygame 2.1

[Marcin Owsiany]

Thanks for the report. Since showing text is proven to still work (as seen
in the screenshots) I suspect the app is no longer receiving the
(simulated) keypresses, because otherwise it should show at least the
colorful "m" letters (even if rendering pictures would stop working for
some reason).

To fix this, I need to figure out a way to interactively run the app
against the new version of the library without messing up my (Debian
stable) system... I'll try running it under xvfb in a container, but other
ideas most welcome :-)

Marcin

Bug#1008634: condor: CVE-2022-26110 / HTCONDOR-2022-0003

[Salvatore Bonaccorso]

Source: condor
Version: 8.6.8~dfsg.1-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for condor.

CVE-2022-26110[0], HTCONDOR-2022-0003

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-26110
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-26110
[1] https://htcondor.org/security/vulnerabilities/HTCONDOR-2022-0003

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1008633: node-spdx-license-ids: autopkgtest regression: Cannot find module 'fettuccine-class'

[Paul Gevers]

Source: node-spdx-license-ids
Version: 3.0.11-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, since the start of 
2022, it started to fail in testing. I copied some of the output at the 
bottom of this report.


Failing tests are considered RC bugs by the release team.

Paul

[1] https://ci.debian.net/packages/n/node-spdx-license-ids/

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-spdx-license-ids/20269931/log.gz

autopkgtest [11:24:40]: test pkg-js-autopkgtest-require: 
/usr/share/pkg-js-autopkgtest/runner require
autopkgtest [11:24:40]: test pkg-js-autopkgtest-require: 
[---

# Using ./package.(json|yaml)
# Node module name is spdx-license-ids
# Test: require
#   Testing spdx-license-ids: SKIPPED
#   Testing get-spdx-license-ids: internal/modules/cjs/loader.js:818
  throw err;
  ^

Error: Cannot find module 'fettuccine-class'
Require stack:
- /usr/share/nodejs/get-spdx-license-ids/index.js
- /tmp/autopkgtest-lxc.49dkppxa/downtmp/autopkgtest_tmp/[eval]
at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:815:15)

at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. 
(/usr/share/nodejs/get-spdx-license-ids/index.js:3:19)

at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1027:10)

at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
'/usr/share/nodejs/get-spdx-license-ids/index.js',
'/tmp/autopkgtest-lxc.49dkppxa/downtmp/autopkgtest_tmp/[eval]'
  ]
}
not ok
autopkgtest [11:24:42]: test pkg-js-autopkgtest-require: 
---]


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008493: marked as done (gnome-control-center and gnome-settings-daemon version mismatch makes keyboard shortcuts fail)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:35:05 +
with message-id 
and subject line Bug#1008493: fixed in gnome-settings-daemon 42.1-2
has caused the Debian Bug report #1008493,
regarding gnome-control-center and gnome-settings-daemon version mismatch makes 
keyboard shortcuts fail
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.)


-- 
1008493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-settings-daemon
Version: 42.1-1
Control: affects -1 gnome-control-center

I have gnome-settings-daemon 42.1-1 installed, and gnome-control-cennter
1:41.4-1

When i open gnome-control-center and go to "Keyboard" and click on "View
and Customize Shortcuts", gnome-control-center crashes, and produces
this on stderr:


(gnome-control-center:3522): GLib-GIO-ERROR **: 12:05:52.032: Settings 
schema 'org.gnome.settings-daemon.plugins.media-keys' does not contain a key 
named 'screenshot'
Trace/breakpoint trap

I reported this upstream:

https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1728

And Jeremy Bicha responded with:

> I think your issue is caused by a version mismatch in Debian, so I'm
> closing this as Not GNOME.

I think either gnome-settings-daemon 42.1-* should indicate that it
Breaks: earlier versions of gnome-control-center, or
gnome-control-center should indicate that it is tightly bound to the
version of gnome-settings-daemon that it ships with.

--dkg


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gnome-settings-daemon
Source-Version: 42.1-2
Done: Simon McVittie 

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gnome-settings-daemon 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Mar 2022 19:10:46 +0100
Source: gnome-settings-daemon
Architecture: source
Version: 42.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1008493
Changes:
 gnome-settings-daemon (42.1-2) unstable; urgency=medium
 .
   * Team upload
 .
   [ Jeremy Bicha ]
   * Seitch back to libgweather4
   * debian/control.in: Build-Depend on libgweather4
   * debian/control.in: Break older gnome-control-center (Closes: #1008493)
Checksums-Sha1:
 fd360e73d9809a1a9a0176cfb61bfd8cba7f677f 3564 gnome-settings-daemon_42.1-2.dsc
 eb3d24a8a7a2f51102c311bd4a71f3910799d929 22080 
gnome-settings-daemon_42.1-2.debian.tar.xz
 8105bdfddb97a969c9fa9a923222fda695140be3 20756 
gnome-settings-daemon_42.1-2_source.buildinfo
Checksums-Sha256:
 da87f504915ae15c52da9c57f59e7ec9f7fc815de53c40bfd635b22d6edc599a 3564 
gnome-settings-daemon_42.1-2.dsc
 7b5b2dc081d07487853771b8de4a1d7ca4d3a5c16aac0f0edc07190952f42903 22080 
gnome-settings-daemon_42.1-2.debian.tar.xz
 a54e39eef66a27922ef0c0fcd43fb39e1789f767b579301547c5716ab74067fd 20756 
gnome-settings-daemon_42.1-2_source.buildinfo
Files:
 7c1ca269745d34c83f8ec939f99aa850 3564 gnome optional 
gnome-settings-daemon_42.1-2.dsc
 59ac750866f0227d28bdd0ab7b5fb124 22080 gnome optional 
gnome-settings-daemon_42.1-2.debian.tar.xz
 5a73efb33cbb5c3847a14e55ed0836d1 20756 gnome optional 
gnome-settings-daemon_42.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmJDWNgACgkQ4FrhR4+B
TE8zDg/+IG0Yh2t4TCib2c5krcDLFOTFL01/rsH59yifYtstNrM6Kqd5Pn3krDqk
sLr0Nw05ZNKe6dgFno9WDN/gU08mb9DyqiWXf4vwE1VCzhZBDdf99CALoecoGlVo
zkNMvjuzhqXj8Wj+tz1399HUnY0K8rx2uNOovtamY1EbrLixvzFCXG+PMAtutNzi
fusNJj57q+IXhjaXIr+YxS4ADGyEGnUgAXT88FR6yjW1tjyjAr1+mvDimO1r5KiU
Jpss/VUgWEdeUGU5EbjZf3hNTSoRzy4rR7Z6mSaEU5P4xbP73rm8XC69gTCBH0EI
eb4vVS6L6pVSTSwea3lheDOe3X5cgA6g2gGOK6yVKT6cRT5X9fm+Vp72EVY/BaKD
fzAVhCLVz0pIrGptXEsuqp32Yxc/pvmS708zQ9Det0655gD2TNG2D5sFHaXI73bF
c+lWEr4io7I2+5SjC/mQ5RD27RzYgWPibAj4y3LV1nvH0itkOvkX2fOaJaWY9GCo
BBrcPTF03wmH0tbAYt967ule/D4nHxeJp1FKnNLAub/jsIyOaLmrC6qAYFex0h+k
TqSrXBjXXXEQsdHOHc4pG+/

Bug#996051: marked as done (gnome-shell-extension-desktop-icons: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:33:35 +
with message-id 
and subject line Bug#1008545: Removed package(s) from unstable
has caused the Debian Bug report #996051,
regarding gnome-shell-extension-desktop-icons: does not declare compatibility 
with GNOME Shell 41
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.)


-- 
996051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-desktop-icons
Version: 20.04.0+git20200908-8
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

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

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

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

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

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

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 20.04.0+git20200908-8+rm

Dear submitter,

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

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

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

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

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

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

Bug#993724: marked as done (crashes when I click on PDF-files)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:33:35 +
with message-id 
and subject line Bug#1008545: Removed package(s) from unstable
has caused the Debian Bug report #993724,
regarding crashes when I click on PDF-files
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.)


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

Package: gnome-shell-extension-desktop-icons
Version: 20.04.0+git20200908-5
Severity: grave

The error occurs when I click at a PDF-file on the
desktop. I start the computer and directly click
at a PDF-file on the desktop. Then I get logged out
of the gnome desktop and have to log in again with my
password.(I normally use autologin and don't have
to type in my password.) The extension is also switched
off thereafter and I have to switch it on again via
gnome-tweaks.

The extension Desktop Icons NG from the gnome extensions
website works well. It does not have this bug, so it could
make sense to check the difference between these.


_

Ihr Recht auf Privatsph�re. Sch�tzen Sie Ihre Daten und wechseln jetzt zu eclipso 
Mail & Cloud - https://www.eclipso.de
--- End Message ---
--- Begin Message ---
Version: 20.04.0+git20200908-8+rm

Dear submitter,

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

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

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

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

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

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

Bug#966109: marked as done (frobtads: FTBFS with GCC 10: error: missing '(' after "__has_builtin")

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:34:02 +
with message-id 
and subject line Bug#996625: Removed package(s) from unstable
has caused the Debian Bug report #966109,
regarding frobtads: FTBFS with GCC 10: error: missing '(' after "__has_builtin"
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.)


-- 
966109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966109
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: frobtads
Version: 1:1.2.4-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Usertags: ftbfs-gcc-10

Hi,

frobtads started to FTBFS (at least on amd64) when GCC 10 was made
the default compiler:

[..]
g++ -DHAVE_CONFIG_H -I. -I/build/frobtads-1.2.4/.  -DFROBTADS -DTC_TARGET_T3 
-DTADSNET  -DOS_DECLARATIVE_TLS  -DVMGLOB_VARS  -D_M_IX86_64 -DRUNFAST 
-I/build/frobtads-1.2.4/./src -I/build/frobtads-1.2.4/./tads2 
-I/build/frobtads-1.2.4/./tads3 -I/build/frobtads
-1.2.4/./tads3/unix  -DT3_INC_DIR=\"/usr/share/frobtads/tads3/include\" 
-DT3_LIB_DIR=\"/usr/share/frobtads/tads3/lib\" 
-DT3_RES_DIR=\"/usr/share/frobtads/tads3/res\" -DT3_LOG_FILE=\"/tmp/frob.log\" 
-I/build/frobtads-1.2.4/./src -I/build/frobtads-1.2.4/./tads2
 -I/build/frobtads-1.2.4/./src -I/build/frobtads-1.2.4/./tads3 
-I/build/frobtads-1.2.4/./tads3/test -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/build/frobtads-1.2.4=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-strict-aliasi
ng -pthread -c -o tads3/charmap.o /build/frobtads-1.2.4/./tads3/charmap.cpp
In file included from /build/frobtads-1.2.4/./tads3/osifcnet.h:942,
 from /build/frobtads-1.2.4/./tads3/vmdatasrc.h:23,
 from /build/frobtads-1.2.4/./tads3/charmap.cpp:31:
/build/frobtads-1.2.4/./tads3/unix/osnetunix.h:222:20: error: missing '(' after 
"__has_builtin"
  222 | # if __has_builtin == 0
  |^~
/build/frobtads-1.2.4/./tads3/unix/osnetunix.h:222:23: error: missing binary 
operator before token "0"
  222 | # if __has_builtin == 0
  |   ^
make[2]: *** [Makefile:10276: tads3/charmap.o] Error 1
make[2]: Leaving directory '/build/frobtads-1.2.4/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:3854: all] Error 2
make[1]: Leaving directory '/build/frobtads-1.2.4/obj-x86_64-linux-gnu'
make: *** [/usr/share/cdbs/1/class/makefile.mk:77: debian/stamp-makefile-build] 
Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


Andreas
--- End Message ---
--- Begin Message ---
Version: 1:1.2.4-1.1+rm

Dear submitter,

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

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

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

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

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

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

Bug#954531: marked as done (hgsubversion: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:33:06 +
with message-id 
and subject line Bug#1008498: Removed package(s) from unstable
has caused the Debian Bug report #954531,
regarding hgsubversion: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
to be marked as done.

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

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


-- 
954531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hgsubversion
Version: 1.9.3+git20190419+6a6ce-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python2,python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python2.7 setup.py clean 
> /usr/lib/python2.7/distutils/dist.py:267: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> running clean
> removing '/<>/.pybuild/cpython2_2.7/build' (and everything under 
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8/build' (and everything under 
> it)
> /usr/lib/python3.8/distutils/dist.py:274: UserWarning: Unknown distribution 
> option: 'install_requires'
>   warnings.warn(msg)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building hgsubversion using existing 
> ./hgsubversion_1.9.3+git20190419+6a6ce.orig.tar.bz2
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  hgsubversion-1.9.3+git20190419+6a6ce/hgsubversion/__version__.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/hgsubversion_1.9.3+git20190419+6a6ce-3.diff.V9NXsU
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-03-22T03:23:24Z

The full build log is available from:
   
http://qa-logs.debian.net/2020/03/21/hgsubversion_1.9.3+git20190419+6a6ce-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 1.9.3+git20190419+6a6ce-5+rm

Dear submitter,

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

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

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

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

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

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

Bug#948847: marked as done (hgsubversion: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:33:06 +
with message-id 
and subject line Bug#1008498: Removed package(s) from unstable
has caused the Debian Bug report #936700,
regarding hgsubversion: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hgsubversion
Version: 1.9.3+git20190419+6a6ce-3
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests, in details:

(source:hgsubversion)Build-Depends->python
(source:hgsubversion)Build-Depends->python-subvertpy
(binary:hgsubversion)Depends->python-subvertpy
(binary:hgsubversion)Depends->python-subversion
(binary:hgsubversion)Depends->python2:any
(binary:hgsubversion)Depends->python2:any

Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

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

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

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

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

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

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

Bug#947299: marked as done (hgsubversion: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:33:06 +
with message-id 
and subject line Bug#1008498: Removed package(s) from unstable
has caused the Debian Bug report #936700,
regarding hgsubversion: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
936700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hgsubversion
Version: 1.9.3+git20190419+6a6ce-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests, in details:

(source:hgsubversion)Build-Depends->python
(source:hgsubversion)Build-Depends->python-subvertpy
(binary:hgsubversion)Depends->python-subvertpy
(binary:hgsubversion)Depends->python-subversion
(binary:hgsubversion)Depends->python2:any
(binary:hgsubversion)Depends->python2:any

Please stop using Python2, and fix this issue by one of the following
actions.

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

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

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

  This is the least preferred option.

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

Dear submitter,

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

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

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

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

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

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

Bug#936700: marked as done (hgsubversion: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:33:06 +
with message-id 
and subject line Bug#1008498: Removed package(s) from unstable
has caused the Debian Bug report #936700,
regarding hgsubversion: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:hgsubversion

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

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

Dear submitter,

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

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

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

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

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

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

Bug#836934: marked as done (frobtads: FTBFS with C++14 on i386: error: exception cleanup for this placement new selects non-placement operator delete)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:34:02 +
with message-id 
and subject line Bug#996625: Removed package(s) from unstable
has caused the Debian Bug report #836934,
regarding frobtads: FTBFS with C++14 on i386: error: exception cleanup for this 
placement new selects non-placement operator delete
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.)


-- 
836934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: frobtads
Version: 1:1.2.3-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source

Hi,

frobtads FTBFS since the default compiler was switched to GCC 6 (which
defaults to -std=c++14):

g++ -DHAVE_CONFIG_H -I. -I/build/frobtads-1.2.3/.  -DFROBTADS -DTC_TARGET_T3 
-DTADSNET  -DOS_DECLARATIVE_TLS  -DVMGLOB_VARS  -D_M_IX86_64 -DRUNFAST 
-I/build/frobtads-1.2.3/./src -I/build/frobtads-1.2.3/./tads2 
-I/build/frobtads-1.2.3/./tads3 -I/build/frobtads-1.2.3/./tads3/unix  
-DT3_INC_DIR=\"/usr/share/frobtads/tads3/include\" 
-DT3_LIB_DIR=\"/usr/share/frobtads/tads3/lib\" 
-DT3_RES_DIR=\"/usr/share/frobtads/tads3/res\" -DT3_LOG_FILE=\"/tmp/frob.log\" 
-I/build/frobtads-1.2.3/./src -I/build/frobtads-1.2.3/./tads2 
-I/build/frobtads-1.2.3/./src -I/build/frobtads-1.2.3/./tads3 
-I/build/frobtads-1.2.3/./tads3/test -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/build/frobtads-1.2.3=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-strict-aliasing -pthread -c -o tads3/tcprs.o 
/build/frobtads-1.2.3/./tads3/tcprs.cpp
In file included from /build/frobtads-1.2.3/./tads3/tcprs.cpp:39:0:
/build/frobtads-1.2.3/./tads3/vmbignum.h: In static member function 'static 
vm_obj_id_t CVmObjBigNum::create(int, const bignum_t*)':
/build/frobtads-1.2.3/./tads3/vmbignum.h:585:45: error: exception cleanup for 
this placement new selects non-placement operator delete [-fpermissive]
 new (vmg_ id) CVmObjBigNum(vmg_ prec);
 ^
: note: 'void operator delete(void*, unsigned int)' is a usual 
(non-placement) deallocation function in C++14 (or with -fsized-deallocation)
/build/frobtads-1.2.3/./tads3/vmbignum.h: In static member function 'static 
vm_obj_id_t CVmObjBigNum::create(int, const bignum_t&)':
/build/frobtads-1.2.3/./tads3/vmbignum.h:596:45: error: exception cleanup for 
this placement new selects non-placement operator delete [-fpermissive]
 new (vmg_ id) CVmObjBigNum(vmg_ prec);
 ^
: note: 'void operator delete(void*, unsigned int)' is a usual 
(non-placement) deallocation function in C++14 (or with -fsized-deallocation)
/build/frobtads-1.2.3/./tads3/vmbignum.h: In member function 'virtual void 
CVmMetaclassBigNum::create_for_image_load(vm_obj_id_t)':
/build/frobtads-1.2.3/./tads3/vmbignum.h:1640:36: error: exception cleanup for 
this placement new selects non-placement operator delete [-fpermissive]
 new (vmg_ id) CVmObjBigNum();
^
: note: 'void operator delete(void*, unsigned int)' is a usual 
(non-placement) deallocation function in C++14 (or with -fsized-deallocation)
/build/frobtads-1.2.3/./tads3/vmbignum.h: In member function 'virtual void 
CVmMetaclassBigNum::create_for_restore(vm_obj_id_t)':
/build/frobtads-1.2.3/./tads3/vmbignum.h:1647:36: error: exception cleanup for 
this placement new selects non-placement operator delete [-fpermissive]
 new (vmg_ id) CVmObjBigNum();
^
: note: 'void operator delete(void*, unsigned int)' is a usual 
(non-placement) deallocation function in C++14 (or with -fsized-deallocation)
Makefile:6604: recipe for target 'tads3/tcprs.o' failed
make[2]: *** [tads3/tcprs.o] Error 1


Andreas
--- End Message ---
--- Begin Message ---
Version: 1:1.2.4-1.1+rm

Dear submitter,

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

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

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

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

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

Debian distribu

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

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:30:26 +
with message-id 
and subject line Bug#1008286: Removed package(s) from unstable
has caused the Debian Bug report #999221,
regarding nglister: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 1.0.2+rm

Dear submitter,

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

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

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

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

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

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

Bug#937138: marked as done (nglister: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:30:26 +
with message-id 
and subject line Bug#1008286: Removed package(s) from unstable
has caused the Debian Bug report #937138,
regarding nglister: Python2 removal in sid/bullseye
to be marked as done.

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

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


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:nglister

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

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

Dear submitter,

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

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

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

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

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

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

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

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:27:31 +
with message-id 
and subject line Bug#1008071: Removed package(s) from unstable
has caused the Debian Bug report #965889,
regarding xcal: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 4.1-19+rm

Dear submitter,

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

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

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

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

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

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

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

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:27:31 +
with message-id 
and subject line Bug#1008071: Removed package(s) from unstable
has caused the Debian Bug report #999228,
regarding xcal: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 4.1-19+rm

Dear submitter,

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

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

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

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

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

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

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

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:26:57 +
with message-id 
and subject line Bug#1008070: Removed package(s) from unstable
has caused the Debian Bug report #999136,
regarding bopm: missing required debian/rules targets build-arch and/or 
build-indep
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

Best,

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

Dear submitter,

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

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

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

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

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

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

Bug#669728: marked as done ([PATCH] bopm: Helping to update to packaging format 3.0)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:26:57 +
with message-id 
and subject line Bug#1008070: Removed package(s) from unstable
has caused the Debian Bug report #669728,
regarding [PATCH] bopm: Helping to update to packaging format 3.0
to be marked as done.

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

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


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

Hi,

The dpatch patch management system has been deprecated for some time. The
Lintian currently flags use of dpatch packages as an error. The new 3.0
packaging format is an improved version which, among other things, contains
patch management built-in. For more information, see:

http://wiki.debian.org/Projects/DebSrc3.0

I had some free time; see attached patch to migrate to new package
format. Note that all files in debian/patches/* are canocalized to
*.patch.

Let me know if there is anything that needs adjusting or if it is ok
to upload this version in a NMU in case you are working on other
issues needing attention.

Thanks,
Jari

>From 23e2d48e39a85ae1531e2e55aa157696f6c60a02 Mon Sep 17 00:00:00 2001
From: Jari Aalto 
Date: Sat, 21 Apr 2012 15:22:48 +0300
Subject: [PATCH] format-3.0
Organization: Private
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Signed-off-by: Jari Aalto 
---
 debian/README.source   |2 --
 debian/bopm.postrm |4 +++-
 debian/changelog   |   13 +
 debian/compat  |2 +-
 debian/control |4 ++--
 debian/copyright   |2 +-
 debian/docs|2 +-
 debian/patches/00list  |1 -
 ...-topic-check.diff => 03-bopm-topic-check.patch} |7 ++-
 debian/patches/series  |1 +
 debian/rules   |   17 +
 debian/source.lintian-overrides|2 --
 debian/source/format   |2 +-
 13 files changed, 34 insertions(+), 25 deletions(-)
 delete mode 100644 debian/README.source
 mode change 100644 => 100755 debian/bopm.postrm
 delete mode 100644 debian/patches/00list
 rename debian/patches/{03_bopm-topic-check.diff => 03-bopm-topic-check.patch} (97%)
 create mode 100644 debian/patches/series
 delete mode 100644 debian/source.lintian-overrides

diff --git a/debian/README.source b/debian/README.source
deleted file mode 100644
index 5e94a7b..000
--- a/debian/README.source
+++ /dev/null
@@ -1,2 +0,0 @@
-This packages uses dpatch to manage differences between the upsteram and the
-Debian version. 
diff --git a/debian/bopm.postrm b/debian/bopm.postrm
old mode 100644
new mode 100755
index c34eee2..799eecb
--- a/debian/bopm.postrm
+++ b/debian/bopm.postrm
@@ -1,4 +1,6 @@
-#!/bin/sh -e
+#!/bin/sh
+
+set -e
 
 case "$1" in
 remove)
diff --git a/debian/changelog b/debian/changelog
index ab2011c..9449f11 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,16 @@
+bopm (3.1.3-3.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
+  * Update to Standards-Version to 3.9.3 and debhelper to 9.
+  * Add build-arch and build-indep targets; use dh_prep in rules file.
+  * Delete debian/source.lintian-overrides; no longer needed.
+  * Fix copyright-refers-to-symlink-license (Lintian).
+  * Fix maintainer-script-without-set-e (Lintian)
+  * Fix duplicate-changelog-files (Lintian)
+
+ -- Jari Aalto   Sat, 21 Apr 2012 15:21:44 +0300
+
 bopm (3.1.3-3) unstable; urgency=low
 
   * added debian source format
diff --git a/debian/compat b/debian/compat
index 7f8f011..ec63514 100644
--- a/debian/compat
+++ b/debian/compat
@@ -1 +1 @@
-7
+9
diff --git a/debian/control b/debian/control
index db5d7ec..2e93e18 100644
--- a/debian/control
+++ b/debian/control
@@ -2,8 +2,8 @@ Source: bopm
 Section: net
 Priority: optional
 Maintainer: Martin Wuertele 
-Build-Depends: debhelper (>= 7.0.50), dpatch, autotools-dev
-Standards-Version: 3.9.2
+Build-Depends: debhelper (>= 9), autotools-dev
+Standards-Version: 3.9.3
 Homepage: http://wiki.blitzed.org/BOPM
 
 Package: bopm
diff --git a/debian/copyright b/debian/copyright
index 1b56761..599c608 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -43,4 +43,4 @@ along with this program;  if

Bug#996065: marked as done (gnome-shell-extension-move-clock: does not declare compatibility with GNOME Shell 41)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 19:22:22 +
with message-id 
and subject line Bug#1007897: Removed package(s) from unstable
has caused the Debian Bug report #996065,
regarding gnome-shell-extension-move-clock: does not declare compatibility with 
GNOME Shell 41
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.)


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

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

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

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

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

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

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 1.01-2+rm

Dear submitter,

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

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

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

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

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

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

Bug#1001001: closed by Salvatore Bonaccorso (Re: linux-image-5.10.0-9-arm64: kernel BUG at include/linux/swapops.h:204!)

[Paul Gevers]

Hi all,

On 20-02-2022 13:44, Paul Gevers wrote:

Sad to say, but this week we had two hangs again.


And this week another two.

 ci-worker-arm64-07 ==

Mar 26 10:15:55 ci-worker-arm64-07 kernel: kernel BUG at 
include/linux/swapops.h:204!
Mar 26 10:15:55 ci-worker-arm64-07 kernel: Internal error: Oops - BUG: 0 
[#1] SMP


Linux kernel from before the last point release:
Linux version 5.10.0-12-arm64 (debian-ker...@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2>


 ci-worker-arm64-08 ==
Mar 25 22:13:44 ci-worker-arm64-08 kernel: kernel BUG at 
include/linux/swapops.h:204!
Mar 25 22:13:44 ci-worker-arm64-08 kernel: Internal error: Oops - BUG: 0 
[#1] SMP


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008493: gnome-control-center and gnome-settings-daemon version mismatch makes keyboard shortcuts fail

[Simon McVittie]

On Tue, 29 Mar 2022 at 12:44:32 -0400, Daniel Kahn Gillmor wrote:
> If there is no explicit API dependency tracking within GNOME, but
> version numbers of major GNOME components are supposed to advance in
> lockstep, then shouldn't the corresponding packages in debian have
> automated and explicit dependency annotations to enforce that lockstep
> transition?

Major GNOME components are expected to be upgraded together, except for
when that's unnecessary. That is an unsatisfying answer, but unfortunately
it's the only true answer.

GNOME is intended (by upstream) to be upgraded as a suite of packages that
go together, and we should make sure that each released version of Debian
contains packages that are consistent with each other. Interfaces that
are only intended to be used within the group of GNOME core packages,
and are not intended to be "API" to be used by unrelated software,
will sometimes get incompatible changes.

We find out about incompatible changes within core GNOME components by
reading diffs, or by trying it and seeing what works. We try to set up
appropriate versioned Depends/Breaks to make known-broken situations
impossible to achieve, but in the case of gnome-control-center and
gnome-settings-daemon, we could not proceed with this until the ongoing
python3.10 transition got far enough to make gnome-control-center
buildable again (my upload from yesterday only became buildable today,
after Samba libraries were rebuilt).

If we speculatively added versioned Depends/Breaks even without evidence
of a potentially-incompatible change, then we'd be less likely to see
transient brokenness in unstable, but we'd also be making the overall
system more rigid: we'd be unable to get any of the GNOME 42 core
components into testing until *all* of them were ready to migrate,
which seems like a recipe for making the migration not actually happen
because there's always something blocking it.

I think we need to strike a balance between, at one extreme, having
unstable be so unusable that it is not useful to test, and at the
other extreme, being so conservative about transitions that everything
happens months too late, by which time upstream won't take our patches
or bug reports because they already moved on to the next release cycle
(for example GNOME 40, which didn't reach unstable until GNOME 41 was
already in hard freeze upstream).

The 41 -> 42 transition is more partial than most because Ubuntu want
to ship a mixture of 41 and 42 in their 22.04 LTS release (I'm not 100%
clear on why, I think they want to keep some components on GTK 3 that
would be GTK 4 upstream), and we're being nice to Ubuntu by not upgrading
the components they don't want to upgrade until after their freeze has
reached a sufficiently frozen stage.

> GNOME typically does a good job in handling a novice user's behaviors
> well without hassling them with confusing technical arcana, but that
> means that silent and complete crashes like the one observed here just
> look like unrecoverable breakage to the normal user who doesn't know
> anything about stderr or how to launch settings from the terminal.

Sorry, but that normal user probably should not be using unstable.

smcv

Bug#1007915: [Pkg-javascript-devel] Bug#1007915: Bug#1007915: node-wikibase-cli: incompatible with node-commander >= 8

[Yadd]

Le 29 mars 2022 18:21:22 GMT+02:00, Andrius Merkys  a écrit :
>Hi Yadd,
>
>On 2022-03-29 19:17, Yadd wrote:
>> On 29/03/2022 17:44, Yadd wrote:
>>> Hi Andrius,
>>>
>>> you fix is enough for commander 8, I'm currently writing commander 9
>>> patch
>> 
>> Fixed and pushed. However package looks unusable because all bin/*
>> commands are not in $PATH. You could either:
>>  * install all commands in /usr/bin
>>  * or change path in /usr/bin/wd and /usr/bin/wb
>
>Thanks a lot for taking care of this! I will check why the executables
>do not end in /usr/bin/. Once I am done, I will upload.
>
>Thanks once more,
>Andrius

After that, please remove my workaround in debian/tests/pkg-js/test

-- 
Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma 
brièveté.

Processed: Re: qiskit-terra: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:nbconvert
Bug #1008459 [src:qiskit-terra] qiskit-terra: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13
Bug reassigned from package 'src:qiskit-terra' to 'src:nbconvert'.
No longer marked as found in versions qiskit-terra/0.12.0-4.
Ignoring request to alter fixed versions of bug #1008459 to the same values 
previously set
> forcemerge -1 1008376
Bug #1008459 [src:nbconvert] qiskit-terra: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.10 3.9" returned exit code 13
Bug #1008459 [src:nbconvert] qiskit-terra: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.10 3.9" returned exit code 13
Marked as found in versions nbconvert/6.4.4-1.
Bug #1008376 [src:nbconvert] nbconvert: FTBFS: ModuleNotFoundError: No module 
named 'ipython_genutils'
Merged 1008376 1008459
> affects -1 src:qiskit-terra
Bug #1008459 [src:nbconvert] qiskit-terra: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.10 3.9" returned exit code 13
Bug #1008376 [src:nbconvert] nbconvert: FTBFS: ModuleNotFoundError: No module 
named 'ipython_genutils'
Added indication that 1008459 affects src:qiskit-terra
Added indication that 1008376 affects src:qiskit-terra

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

Bug#1008459: qiskit-terra: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

[Nilesh Patra]

control: reassign -1 src:nbconvert
control: forcemerge -1 1008376
control: affects -1 src:qiskit-terra

Hi,

>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.9/build/test/python/tools/jupyter/test_notebooks.py _
> ImportError while importing test module 
> '/<>/.pybuild/cpython3_3.9/build/test/python/tools/jupyter/test_notebooks.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> /usr/lib/python3.9/importlib/__init__.py:127: in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> test/python/tools/jupyter/test_notebooks.py:22: in 
> from nbconvert.preprocessors import ExecutePreprocessor
> /usr/lib/python3/dist-packages/nbconvert/__init__.py:4: in 
> from .exporters import *
> /usr/lib/python3/dist-packages/nbconvert/exporters/__init__.py:4: in 
> from .slides import SlidesExporter
> /usr/lib/python3/dist-packages/nbconvert/exporters/slides.py:12: in 
> from ..preprocessors.base import Preprocessor
> /usr/lib/python3/dist-packages/nbconvert/preprocessors/__init__.py:10: in 
> 
> from .execute import ExecutePreprocessor
> /usr/lib/python3/dist-packages/nbconvert/preprocessors/execute.py:8: in 
> 
> from nbclient import NotebookClient, execute as _execute
> /usr/lib/python3/dist-packages/nbclient/__init__.py:5: in 
> from .client import NotebookClient, execute  # noqa: F401
> /usr/lib/python3/dist-packages/nbclient/client.py:35: in 
> from .output_widget import OutputWidget
> /usr/lib/python3/dist-packages/nbclient/output_widget.py:6: in 
> from .jsonutil import json_clean
> /usr/lib/python3/dist-packages/nbclient/jsonutil.py:16: in 
> from ipython_genutils import py3compat
> E   ModuleNotFoundError: No module named 'ipython_genutils'

Clearly this is due to nbclient instead. Re-assigning and merging with another 
BR(#1008376)
which says the same thing

Nilesh


signature.asc
Description: PGP signature

Bug#1008440: marked as done (golang-github-arceliar-ironwood: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/Arceliar/ironwood/encrypted github.com/Arceliar/ironwood/encr

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 17:33:47 +
with message-id 
and subject line Bug#1008440: fixed in golang-github-arceliar-ironwood 
0.0~git20211125.8951369-3
has caused the Debian Bug report #1008440,
regarding golang-github-arceliar-ironwood: FTBFS: dh_auto_test: error: cd 
_build && go test -vet=off -v -p 8 github.com/Arceliar/ironwood/encrypted 
github.com/Arceliar/ironwood/encrypted/internal/e2c 
github.com/Arceliar/ironwood/network github.com/Arceliar/ironwood/signed 
github.com/Arceliar/ironwood/types returned exit code 1
to be marked as done.

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

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


-- 
1008440: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008440
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-arceliar-ironwood
Version: 0.0~git20211125.8951369-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --builddirectory=_build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--builddirectory=_build -O--buildsystem=golang
>dh_autoreconf -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_configure -O--builddirectory=_build -O--buildsystem=golang
>dh_auto_build -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go install -trimpath -v -p 8 
> github.com/Arceliar/ironwood/encrypted 
> github.com/Arceliar/ironwood/encrypted/internal/e2c 
> github.com/Arceliar/ironwood/network github.com/Arceliar/ironwood/signed 
> github.com/Arceliar/ironwood/types
> internal/goarch
> internal/goos
> internal/unsafeheader
> internal/goexperiment
> internal/race
> internal/cpu
> runtime/internal/syscall
> runtime/internal/atomic
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> sync/atomic
> unicode
> unicode/utf8
> math/bits
> crypto/subtle
> internal/itoa
> internal/bytealg
> crypto/internal/subtle
> internal/nettrace
> golang.org/x/crypto/internal/subtle
> golang.org/x/crypto/salsa20/salsa
> math
> runtime
> internal/reflectlite
> sync
> github.com/Arceliar/phony
> internal/singleflight
> math/rand
> internal/testlog
> runtime/cgo
> errors
> sort
> strconv
> internal/oserror
> path
> io
> vendor/golang.org/x/net/dns/dnsmessage
> syscall
> container/heap
> bytes
> hash
> strings
> reflect
> crypto
> bufio
> time
> internal/syscall/execenv
> internal/syscall/unix
> context
> io/fs
> internal/poll
> os
> internal/fmtsort
> encoding/binary
> crypto/cipher
> crypto/sha512
> golang.org/x/crypto/curve25519/internal/field
> golang.org/x/crypto/internal/poly1305
> crypto/ed25519/internal/edwards25519/field
> internal/godebug
> io/ioutil
> fmt
> internal/intern
> golang.org/x/crypto/nacl/secretbox
> crypto/aes
> golang.org/x/sys/cpu
> crypto/ed25519/internal/edwards25519
> net/netip
> golang.org/x/crypto/blake2b
> net
> golang.org/x/crypto/curve25519
> encoding/hex
> math/big
> crypto/rand
> crypto/ed25519
> golang.org/x/crypto/nacl/box
> github.com/Arceliar/ironwood/encrypted/internal/e2c
> github.com/Arceliar/ironwood/types
> github.com/Arceliar/ironwood/network
> github.com/Arceliar/ironwood/signed
> github.com/Arceliar/ironwood/encrypted
>dh_auto_test -O--builddirectory=_build -O--buildsystem=golang
>   cd _build && go test -vet=off -v -p 8 
> github.com/Arceliar/ironwood/encrypted 
> github.com/Arceliar/ironwood/encrypted/internal/e2c 
> github.com/Arceliar/ironwood/network github.com/Arceliar/ironwood/signed 
> github.com/Arceliar/ironwood/types
> === RUN   TestEdX25519
> --- PASS: TestEdX25519 (0.00s)
> PASS
> okgithub.com/Arceliar/ironwood/encrypted  0.004s
> ? github.com/Arceliar/ironwood/encrypted/internal/e2c [no test files]
> === RUN   TestTwoNodes
> --- PASS: TestTwoNodes (0.00s)
> === RUN   TestLineNetwork
> core_test.go:206: 
> ac38b1eff77dc82e0544610df53ff3b3bb881f4d505b9f8e4558f408fbe23f97 : 
> bc8a4adcba5278941dde60e803256e59e7f574ac860d11a495e729ff98f0b684 : 
> c04f1c2a68fd6d3b810c8cef63b85c765238b5eb9ded69f8d27f6bd3af54e9ee : 
> 0a6b9edac3aff60f5fa5b510bba826ff7937acd0271bd0cece7215074aefd0cd
> core_test.go:206: 
> a831a0843f4ac04f7303160862a7470ab6a567fee1281d9afd03fbac2e0f9057 : 
> ac38b1eff77dc82e0544610df53ff3b3bb881f4d505b9f8e4558f408fbe23f97 : 
> bc8a4adcba5278941dde60e803256e59e7f574ac860d11a495e729ff98f0b684 : 
> 0a6b9edac3aff60f5fa5b510bba826ff7937acd0271bd0cece7215074aefd0cd
> core_test.go:206: 
> 0a6b9edac3aff60f5fa5b510bba826ff7937acd0271bd0cec

Processed: Re: Bug#1008382: meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies

[Debian Bug Tracking System]

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

> tags 1008382 +fixed-upstream
Bug #1008382 [meson] meson 0.62 regression: gtk-doc targets in src:glib2.0 lose 
their dependencies
Added tag(s) fixed-upstream.
> forwarded 1008382 https://github.com/mesonbuild/meson/commit/823da39
Bug #1008382 [meson] meson 0.62 regression: gtk-doc targets in src:glib2.0 lose 
their dependencies
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/commit/823da39'.
>
End of message, stopping processing here.

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

Processed: Re: Bug#1008382: meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies

[Debian Bug Tracking System]

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

> forwarded 1008382 https://github.com/mesonbuild/meson/pull/10203
Bug #1008382 [meson] meson 0.62 regression: gtk-doc targets in src:glib2.0 lose 
their dependencies
Changed Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/pull/10203' from 
'https://github.com/mesonbuild/meson/commit/823da39'.
>
End of message, stopping processing here.

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

Processed: Re: pipenv: update to latest pipenv

[Debian Bug Tracking System]

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

> found 945139 11.9.0-1.1
Bug #945139 [pipenv] pipenv: update to latest pipenv
Ignoring request to alter found versions of bug #945139 to the same values 
previously set
> severity 945139 serious
Bug #945139 [pipenv] pipenv: update to latest pipenv
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#1008537: marked as done (gnome-shell-extension-autohidetopbar: does not declare compatibility with GNOME Shell 42)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 17:18:55 +
with message-id 
and subject line Bug#1008537: fixed in gnome-shell-extension-autohidetopbar 
1:107-1
has caused the Debian Bug report #1008537,
regarding gnome-shell-extension-autohidetopbar: does not declare compatibility 
with GNOME Shell 42
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.)


-- 
1008537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-autohidetopbar
Version: 20211109-1
Severity: normal
Tags: bookworm sid fixed-upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-42

The metadata.json for this extension doesn't declare compatibility with
GNOME 42. New upstream releases appear to have fixed this.

gnome-shell 42 is in experimental and will be entering unstable soon,
at which point this will become a RC bug.

During the GNOME Shell 42 transition, this extension will be removed from
testing if it continues to be incompatible.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-autohidetopbar
Source-Version: 1:107-1
Done: Tobias Frost 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Mar 2022 19:01:31 +0200
Source: gnome-shell-extension-autohidetopbar
Architecture: source
Version: 1:107-1
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Closes: 1008537
Changes:
 gnome-shell-extension-autohidetopbar (1:107-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #1008537)
   * d/control: Update Depends: on gnome-shell to include version 42.
   * Package version is now matching the version on extensions.gnome.org,
 therefore an epoch has been introduced.
   * Updating d/watch to follow upstream tags (matching the version on
 extension.gnome.org as well)
   * Update d/copyright.
Checksums-Sha1:
 8e03899fcbc9d4d06c43ded165c6f38d837d1426 2154 
gnome-shell-extension-autohidetopbar_107-1.dsc
 b20fa7a3d15e22afc59f31820eca9399e57d7976 36000 
gnome-shell-extension-autohidetopbar_107.orig.tar.gz
 a63aae24a7d0a939cde7e2197ea17ec29c5bbc86 5416 
gnome-shell-extension-autohidetopbar_107-1.debian.tar.xz
 cf31c169a91d37c5617d853ad146332dfe0ecfcd 5796 
gnome-shell-extension-autohidetopbar_107-1_source.buildinfo
Checksums-Sha256:
 4e97d3a74c8af38f4a88f111bab025c0dbdbf2f247582fef73b32a6bf89a73a8 2154 
gnome-shell-extension-autohidetopbar_107-1.dsc
 30edd043edfae4d2b7828e2b9344cc7fdd9f9cf975b95cd75af3183aa9ce8c7c 36000 
gnome-shell-extension-autohidetopbar_107.orig.tar.gz
 9dcefd190cbf9c50fbf117b56d84f4288d16ac8dbdaceb7eda67627a284c3755 5416 
gnome-shell-extension-autohidetopbar_107-1.debian.tar.xz
 2992429d51b5aa1508d91f13f23ad4f56ba0006766d1e25ab30f53c6bc1925e5 5796 
gnome-shell-extension-autohidetopbar_107-1_source.buildinfo
Files:
 f5e0f22b41e3a14672fd4e0cf778804c 2154 gnome optional 
gnome-shell-extension-autohidetopbar_107-1.dsc
 e22f5e14972083928638f38368e688a1 36000 gnome optional 
gnome-shell-extension-autohidetopbar_107.orig.tar.gz
 ffa2613c14b624e40345ed2f9f3c2787 5416 gnome optional 
gnome-shell-extension-autohidetopbar_107-1.debian.tar.xz
 6c32c0a064bac9a8d2b6dcf5ef66d810 5796 gnome optional 
gnome-shell-extension-autohidetopbar_107-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmJDO5EACgkQkWT6HRe9
XTZ0lw//fzleeEJXCdU/bmwqH0KzArYs0P0mkyWIZtlGyZaYRKLR+gGnYuVP0Aoh
uTIikhQ/zWwynZLtwODtM6XHP4Iqk2KfgLvkIa1rWE7xNyMyPP34oRkv+2Li74a6
ZfhsPq1GnkK+PM8pEK9ibAS7k4xI3rjlb2tBBD7MktGOI6qUHDarhLFofnrKe9aV
4qQ6qCol5btlmBWvroWt4QgZKNEvvyJa/ahB3348koTYFHQiZN8oS7zq1lri0+fh
ajw011SDWIKXlYrKGiTsPsFJV3NHWZ8gEvcFw2l1oWYofD8M8eNbDFg6LwOoo9Me
LiF+MA6bVpyid5UOC3707hY/B97bIasE98etT1xhYXVzA+ZNPRKc2f8IjMfA7Yps
VHFlJ6QDemD

Processed: reassign 996625 to ftp.debian.org, severity of 996625 is normal

[Debian Bug Tracking System]

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

> reassign 996625 ftp.debian.org
Bug #996625 [frobtads] RM: frobtads -- RoQA, unmainained, several RC bugs, low 
popcon
Bug reassigned from package 'frobtads' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #996625 to the same values 
previously set
Ignoring request to alter fixed versions of bug #996625 to the same values 
previously set
> severity 996625 normal
Bug #996625 [ftp.debian.org] RM: frobtads -- RoQA, unmainained, several RC 
bugs, low popcon
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: Bug#1008537 marked as pending in gnome-shell-extension-autohidetopbar

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008537 [gnome-shell-extension-autohidetopbar] 
gnome-shell-extension-autohidetopbar: does not declare compatibility with GNOME 
Shell 42
Added tag(s) pending.

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

Bug#1008493: gnome-control-center and gnome-settings-daemon version mismatch makes keyboard shortcuts fail

[Daniel Kahn Gillmor]

On Mon 2022-03-28 21:26:16 -0400, Jeremy Bicha wrote:
> This fix is pending

Thanks for the pending fix, Jeremy.  I can't help noticing that this
failure looks like a classic backward-incompatible API change.  The API
happens to be across a gsettings schema instead of a C library,
language-specific module, or network service, but it's still the same
thing.

As a community, we have decades of hard-won experience in reasoning
about and handling API changes: thinking about what kinds of changes are
backward-compatible (adding interfaces) or backward-incompatible
(removing or changing interfaces), how to signal them (SONAMEs for C
shared objects, libtool's current/revision/age, semver in many of the
modern language ecosystems, URL prefixes for HTTP REST, etc), and how to
declare dependencies on them in ways that are not hard to propagate into
downstream package managers.

How does GNOME track these API changes across its constitutent projects?
I'm too much of a newbie in GNOME to know how that's done, but if there
is some sort of API version tracking within gnome, then it seems like
either gnome-settings-daemon should have marked a backward-incompatible
API bump when it removed the "screenshot" key from the schema or
gnome-control-center didn't accurately specify its particular API needs
from gnome-settings-daemon.  If that signalling is present, and either
of those were fixed upstream, that knowledge should be propagated to the
debian packaging.

If there is no explicit API dependency tracking within GNOME, but
version numbers of major GNOME components are supposed to advance in
lockstep, then shouldn't the corresponding packages in debian have
automated and explicit dependency annotations to enforce that lockstep
transition?

There are other options too, of course, including:

 - gnome-settings-daemon could declare that any given key in its schema
   could go away, and expect callers to deal with such an outage.  In
   that case, gnome-control-center is at fault for aborting when the
   'screenshot' key was not found.

 - gnome-settings-daemon could avoid a backward-incompatible API change
   by retaining the "screenshot" key, possibly emitting deprecation
   warnings somewhere when the deprecated key is accessed.  Some future
   version could bundle a collection of schema removals into a larger
   backward-incompatible API change after a suitable deprecation window.

This is a larger general concern about the health of GNOME in Debian
going forward: i don't expect the GNOME interdependencies to get simpler
over time (what user-facing software does?), so i would like to
understand how GNOME and the Debian GNOME team think about handling them
in general.

GNOME typically does a good job in handling a novice user's behaviors
well without hassling them with confusing technical arcana, but that
means that silent and complete crashes like the one observed here just
look like unrecoverable breakage to the normal user who doesn't know
anything about stderr or how to launch settings from the terminal.

If you think this is an upstream GNOME issue and no debian-specific at
all, I'm happy to move this off the Debian BTS, just tell me where you
think the appropriate venue is.

Thanks for your work maintaining GNOME in debian!

--dkg


signature.asc
Description: PGP signature

Bug#1008537: marked as pending in gnome-shell-extension-autohidetopbar

[Tobias Frost]

Control: tag -1 pending

Hello,

Bug #1008537 in gnome-shell-extension-autohidetopbar reported by you has been 
fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/gnome-shell-extension-autohidetopbar/-/commit/a74322cad6db7b40fe919b0d42d72578dc492520


New upstream release. (Closes: #1008537)

Package version is now matching the version on extensions.gnome.org, therefore
an epoch has been introduced.

Updating d/watch to follow upstream tags (matching the version on
extension.gnome.org as well)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008537

Bug#1007915: marked as done (node-wikibase-cli: incompatible with node-commander >= 8)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 16:39:23 +
with message-id 
and subject line Bug#1007915: fixed in node-wikibase-cli 15.15.4-2
has caused the Debian Bug report #1007915,
regarding node-wikibase-cli: incompatible with node-commander >= 8
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.)


-- 
1007915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-wikibase-cli
Version: 15.15.4
Severity: serious
Tags: help

While node-wikibase-cli was in NEW, node-commander was updated from
6.2.1 to 9.0.0. node-wikibase-cli is compatible with node-commander 6.x
only and simple patching does not seem to help. I will try patching it a
bit more, but I would appreciate any help from someone more accustomed
to node-commander API.

Andrius
--- End Message ---
--- Begin Message ---
Source: node-wikibase-cli
Source-Version: 15.15.4-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-wikibase-cli package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Mar 2022 18:10:35 +0200
Source: node-wikibase-cli
Architecture: source
Version: 15.15.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1007915
Changes:
 node-wikibase-cli (15.15.4-2) unstable; urgency=medium
 .
   * Team upload
 .
   [ lintian-brush ]
   * Remove obsolete fields Contact, Name from debian/upstream/metadata
 (already present in machine-readable debian/copyright)
 .
   [ Yadd ]
   * Add "Rules-Requires-Root: no"
   * Add debian/gbp.conf
   * Update nodejs dependency to nodejs:any
   * Add fix for node-commander 8 and 9 (Closes: #1007915)
   * Fix untested autopkgtest
Checksums-Sha1: 
 31f0597ac1be037b5ce65e4fa21387e05b625451 2385 node-wikibase-cli_15.15.4-2.dsc
 dfccab80f485a9484670134523011ae1c7b64e92 5916 
node-wikibase-cli_15.15.4-2.debian.tar.xz
Checksums-Sha256: 
 1f02e8fc5f3806b772977faa8226435b470301c5b5842461397901f2dfafe03f 2385 
node-wikibase-cli_15.15.4-2.dsc
 a6e3678989ac719fe91d005a75579b21091926eb4d3db90aabf101dea8745d47 5916 
node-wikibase-cli_15.15.4-2.debian.tar.xz
Files: 
 87ddf4d9ba69339c402d3119cf60554c 2385 javascript optional 
node-wikibase-cli_15.15.4-2.dsc
 1b53c9153cb31e4c5543401ebe9b2f18 5916 javascript optional 
node-wikibase-cli_15.15.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJDMG8ACgkQ9tdMp8mZ
7uko6w/9GjY+HqA2zUvp/ObQnRirjMH76dqqo/o7UKXIxkjHgAfebXQxSvshb/Dx
V0/A299HpigSsdHTE75rxue/0+U+aj896qr6j+hsF8HniuLZZZoDSIGPYQYV5eEW
WnRQmLIzlCiT6U8AyOKKYfaS99rCjcbNkhY3wY9J4QYP6R1yBAn7TzNQHJgOgl21
Uv6SrVfnpe6XuDw9YV2yIAgqtvbcT8hfMfJ6Ke/clCQTNsiIA3iUwBuOQkbVy7Lx
eiuUSL2gSGqs3naldIoCiEPuYYJ/AChksSFUt0KpGJlHhcNOgKzciwJzkE+Kv4KP
iVN316+eGcgIrxjF8b+UOROzoFOEMruWebBIivK/kDjF9svy1sgNGwdqrDGewbtZ
CiuUJdP96uN/xeSPCCiJLwL9IeBqwflWlCOvYG5UBLVQN/H+2hnx7PfsvY7d3sPV
ke9M/ZOe+xduUT57SZNqNpQqXkmMYwZL6+EgCeTsQg+kdLEm7xDXKkmL5qAFwvPP
E32nb/gaFXgWioo72YIgf77lRJ6PqeZPw9vxHPKSVBTPPT/zvFBtcBmo+D/3saNh
R51Na6hN+iRb6KK3c5mIeB41zvEI6LM9RwNNTSY5Jay4JTcZd6SKluHskOrSJmdG
H1oYMpii7uEmdsT8CfehGBjfkQNLoLoFIMGfF3TOYttXObA8p1k=
=3XLn
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 965432 0.8.11
Bug #965432 {Done: Eriberto Mota } [src:beancounter] 
beancounter: Removal of obsolete debhelper compat 5 and 6 in bookworm
Marked as fixed in versions beancounter/0.8.11.
>
End of message, stopping processing here.

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

Bug#1007915: [Pkg-javascript-devel] Bug#1007915: node-wikibase-cli: incompatible with node-commander >= 8

[Andrius Merkys]

Hi Yadd,

On 2022-03-29 19:17, Yadd wrote:
> On 29/03/2022 17:44, Yadd wrote:
>> Hi Andrius,
>>
>> you fix is enough for commander 8, I'm currently writing commander 9
>> patch
> 
> Fixed and pushed. However package looks unusable because all bin/*
> commands are not in $PATH. You could either:
>  * install all commands in /usr/bin
>  * or change path in /usr/bin/wd and /usr/bin/wb

Thanks a lot for taking care of this! I will check why the executables
do not end in /usr/bin/. Once I am done, I will upload.

Thanks once more,
Andrius

Bug#1007915: [Pkg-javascript-devel] Bug#1007915: node-wikibase-cli: incompatible with node-commander >= 8

[Yadd]

On 29/03/2022 17:44, Yadd wrote:

Hi Andrius,

you fix is enough for commander 8, I'm currently writing commander 9 patch


Fixed and pushed. However package looks unusable because all bin/* 
commands are not in $PATH. You could either:

 * install all commands in /usr/bin
 * or change path in /usr/bin/wd and /usr/bin/wb

Cheers,
Yadd

Bug#1007915: marked as pending in node-wikibase-cli

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-wikibase-cli/-/commit/1e45e6a6ff5381fd64cf65ba057697fbe564cc6b


Add fix for node-commander 8 and 9

Closes: #1007915


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1007915

Processed: Bug#1007915 marked as pending in node-wikibase-cli

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1007915 [src:node-wikibase-cli] node-wikibase-cli: incompatible with 
node-commander >= 8
Added tag(s) pending.

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

Bug#1008560: marked as done (gnome-shell-extension-vertical-overview: does not declare compatibility with GNOME Shell 42)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 16:03:52 +
with message-id 
and subject line Bug#1008560: fixed in gnome-shell-extension-vertical-overview 
8-3
has caused the Debian Bug report #1008560,
regarding gnome-shell-extension-vertical-overview: does not declare 
compatibility with GNOME Shell 42
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.)


-- 
1008560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-vertical-overview
Version: 8-2
Severity: normal
Tags: bookworm sid upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-42
Forwarded: https://github.com/RensAlthuis/vertical-overview/issues/98

The metadata.json for this extension doesn't declare compatibility with
GNOME 42, and from the upstream issue tracker it looks like real code
changes will be needed.

gnome-shell 42 is in experimental and will be entering unstable soon,
at which point this will become a RC bug.

During the GNOME Shell 42 transition, this extension will be removed from
testing if it continues to be incompatible.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-vertical-overview
Source-Version: 8-3
Done: Tobias Frost 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 29 Mar 2022 17:46:19 +0200
Source: gnome-shell-extension-vertical-overview
Architecture: source
Version: 8-3
Distribution: unstable
Urgency: medium
Maintainer: Tobias Frost 
Changed-By: Tobias Frost 
Closes: 1008560
Changes:
 gnome-shell-extension-vertical-overview (8-3) unstable; urgency=medium
 .
   * Cherry-pick a PR from upstream, in the hope for fix it for Gnome 42.
 (Closes: #1008560), amended with updated metadata.json.
   * Update d/control for tighter Depends on gnome-shell.
Checksums-Sha1:
 6d6382350f79145cd5a8494451e88ad42c82507a 2164 
gnome-shell-extension-vertical-overview_8-3.dsc
 a80ffce8551570e6956a27843b78357da31adac5 4408 
gnome-shell-extension-vertical-overview_8-3.debian.tar.xz
 3c97d82061e9363808fb111ac7f56a42cfb0482a 5798 
gnome-shell-extension-vertical-overview_8-3_source.buildinfo
Checksums-Sha256:
 aefc69cbb7cb440ac5fbaeda2822c940b24156de11abeadd1e8f92602712553e 2164 
gnome-shell-extension-vertical-overview_8-3.dsc
 9de0ac9a86926efee66f4513b010327b592763aa5474e2bd1e2ea4b6abd261ef 4408 
gnome-shell-extension-vertical-overview_8-3.debian.tar.xz
 06bc65f7de2ab8e95a801dd08917113905ec681e308aecde47f0d53c208fea6d 5798 
gnome-shell-extension-vertical-overview_8-3_source.buildinfo
Files:
 e6b3a91103b6b650f1e82c56b4724821 2164 gnome optional 
gnome-shell-extension-vertical-overview_8-3.dsc
 e2cf2a100aef8caf748089e0d3b383e0 4408 gnome optional 
gnome-shell-extension-vertical-overview_8-3.debian.tar.xz
 6c36c20561ca474e7c4986255feb7859 5798 gnome optional 
gnome-shell-extension-vertical-overview_8-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmJDKgIACgkQkWT6HRe9
XTbbfRAAiu3JnmFANDFZVOMaKRKRVRYVynvBJXrKVhVzqGSWXDSSppzjtUY9+ofR
YmYxPf/dgL2Q285Ce9qVH60PdkyG3Xt42cHx7icI6TmF7Bw1oTDPTPrjltaPdxUn
YtkDlH8oBUzPtxTP1Z8oFdKZTLMqw0u029yIbSh5aw8kxALONOR10CpewVsQmlRC
LDvzA6kT4Qx//kT46/7HeFWGINgIeE0NXFLAyCfmlo5mgVImMxnalnB/vq5xnwuA
ONdnLBt3LbPkLAJnMl7JN82DFMWKRZ5vUkwc2JUNI7pv0qeNOf2tT1RuY//tYzhC
0QTvfBrecVooVcoM7v7RV93EjXue0sTBiqP5FvZRxU9B6SU31b/yDSkCWtrZP2hn
HEutYCKe+TMOWwsMwgUDpZWMh/ZJ9PjN0AceCXfd2I1ZcuDbCryHKuDB1dfLVGaD
TxW5nIyzs+PaYqXyew9Gw4G4DFGbmGr1Skm7XUnUlV3yyFc9km1TrIv47Dh4ASTj
vHl8sdmsydbSGYC2aDTnXRcd3QfEOKrjhp3JVMpOl23eBuHUGq1wt+JzWsUgrwLt
0biH+3k2mW8jKDiRv/0Q5OK3LJMs5C8aHWsuzsfbuAdVrpYhh6lSUJRcM7GAJrZh
O8S/SZQMCXlaHMa2i5PWp/lyS6fzgVw1Vr63qlFaVMauraLmmPM=
=rY3N
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 13:00:38 -0300
with message-id <20220329130038.a2f22e8ae0dbc651948e1...@debian.org>
and subject line Re: beancounter: Removal of obsolete debhelper compat 5 and 6 
in bookworm
has caused the Debian Bug report #965432,
regarding beancounter: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.

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

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


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

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Control: fixed 965432 0.8.11

The maintainer bumped the DH level to 11 in the last revision (some months
ago), but he didn't close the bug. So I am closing it now.

Regards,

Eriberto--- End Message ---

Bug#1007915: node-wikibase-cli: incompatible with node-commander >= 8

[Yadd]

Hi Andrius,

you fix is enough for commander 8, I'm currently writing commander 9 patch

Bug#1008613: marked as done (usrmerge: fails to undo the damage on uninstall)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 17:17:35 +0200
with message-id <9976b179eb46e561cf028279fa0c92c1b1e32d8a.ca...@43-1.org>
and subject line Re: usrmerge: fails to undo the damage on uninstall
has caused the Debian Bug report #1008613,
regarding usrmerge: fails to undo the damage on uninstall
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.)


-- 
1008613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: usrmerge
Version: 25
Severity: grave
Justification: causes non-serious data loss

Due to a lacking *rm script that would recover the system back to a
supported scheme, the system remains tainted by aliased-dirs even if the
usrmerge package is uninstalled.

Such a scheme is explicitly unsupported by dpkg.

A proposed solution is to run dpkg-fsys-usrunmess in prerm.


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

Kernel: Linux 5.17.0-00017-g2526ae7adaeb (SMP w/64 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages usrmerge depends on:
ii  debconf [debconf-2.0]   1.5.79
ii  libfile-find-rule-perl  0.34-1
ii  perl5.34.0-3

usrmerge recommends no packages.

usrmerge suggests no packages.
--- End Message ---
--- Begin Message ---
On Tue, 29 Mar 2022 17:11:11 +0200 Adam Borowski wrote:
> Due to a lacking *rm script that would recover the system back to a
> supported scheme, the system remains tainted by aliased-dirs even if
the
> usrmerge package is uninstalled.

Please don't troll.

Ansgar--- End Message ---

Bug#1008613: usrmerge: fails to undo the damage on uninstall

[Adam Borowski]

Package: usrmerge
Version: 25
Severity: grave
Justification: causes non-serious data loss

Due to a lacking *rm script that would recover the system back to a
supported scheme, the system remains tainted by aliased-dirs even if the
usrmerge package is uninstalled.

Such a scheme is explicitly unsupported by dpkg.

A proposed solution is to run dpkg-fsys-usrunmess in prerm.


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

Kernel: Linux 5.17.0-00017-g2526ae7adaeb (SMP w/64 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages usrmerge depends on:
ii  debconf [debconf-2.0]   1.5.79
ii  libfile-find-rule-perl  0.34-1
ii  perl5.34.0-3

usrmerge recommends no packages.

usrmerge suggests no packages.

Bug#1008511: marked as done (FTBFS failures in the upstream test suite)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 15:04:59 +
with message-id 
and subject line Bug#1008511: fixed in node-configurable-http-proxy 
4.5.0+~cs15.1.4-4
has caused the Debian Bug report #1008511,
regarding FTBFS failures in the upstream test suite
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.)


-- 
1008511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-configurable-http-proxy
Version: 4.5.0+~cs15.1.4-3
Severity: serious
Tags: ftbfs

Building the package in an unstable sbuild, I get failures:
Randomized with seed 97263
Started
..F...06:23:50.587 [ConfigProxy]
ESC[31merrorESC[39m: 404 GET /nope 
06:23:50.860 [ConfigProxy] ESC[31merrorESC[39m: 503 GET /missing/prefix
connect ECONNREFUSED 127.0.0.1:54321
...06:23:50.953 [ConfigProxy] ESC[31merrorESC[39m: 404 GET /nope 
06:23:51.227 [ConfigProxy] ESC[31merrorESC[39m: 503 GET /missing/prefix
connect ECONNREFUSED 127.0.0.1:54321
.06:23:51.270 [ConfigProxy] ESC[31merrorESC[39m: 503 GET
/missing/prefix connect ECONNREFUSED 127.0.0.1:54321
06:23:51.273 [ConfigProxy] ESC[31merrorESC[39m: 503 GET /missing/ws
connect ECONNREFUSED 127.0.0.1:54321
...06:23:51.346 [ConfigProxy] ESC[31merrorESC[39m: 404 GET /foo/bar 
...06:23:51.370 [ConfigProxy] ESC[31merrorESC[39m: 500 GET /% URIError:
URI malformed
at decodeURIComponent ()
at ConfigurableProxy.targetForReq
(/<>/lib/configproxy.js:385:27)
at ConfigurableProxy.handleProxy
(/<>/lib/configproxy.js:529:17)
at ConfigurableProxy.handleProxyWeb
(/<>/lib/configproxy.js:613:17)
at Server. (/<>/lib/configproxy.js:198:27)
at Server.emit (events.js:400:28)
at parserOnIncoming (_http_server.js:900:12)
at HTTPParser.parserOnHeadersComplete (_http_common.js:127:17)
.06:23:51.403 [ConfigProxy] ESC[32minfoESC[39m: Adding route / ->
http://127.0.0.1:9001
06:23:51.403 [ConfigProxy] ESC[32minfoESC[39m: Route added / ->
http://127.0.0.1:9001
.

Failures:
1) CLI Tests custom-header
  Message:
Error: Timeout - Async function did not complete within 1ms
(set by jasmine.DEFAULT_TIMEOUT_INTERVAL)
  Stack:
at 
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)
  Message:
Error: Timeout - Async function did not complete within 1ms
(set by jasmine.DEFAULT_TIMEOUT_INTERVAL)
  Stack:
at 
at listOnTimeout (internal/timers.js:557:17)
at processTimers (internal/timers.js:500:7)

58 specs, 1 failure

Cheers,

J.Puydt
--- End Message ---
--- Begin Message ---
Source: node-configurable-http-proxy
Source-Version: 4.5.0+~cs15.1.4-4
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-configurable-http-proxy 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Mar 2022 16:43:50 +0200
Source: node-configurable-http-proxy
Architecture: source
Version: 4.5.0+~cs15.1.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1008511
Changes:
 node-configurable-http-proxy (4.5.0+~cs15.1.4-4) unstable; urgency=medium
 .
   * Team upload
   * Add fix for node-commander 9 (Closes: #1008511)
Checksums-Sha1: 
 fdf2e161e80e7a2e66f9dd293321def9aafda2a3 4255 
node-configurable-http-proxy_4.5.0+~cs15.1.4-4.dsc
 6d99ba6d0fc5969335eab29ff5b4a4f6f208064f 29796 
node-configurable-http-proxy_4.5.0+~cs15.1.4-4.debian.tar.xz
Checksums-Sha256: 
 a618ed4a7c8b63276383e5098623092dfcc2ef8a41221224105a223ecfd3f2db 4255 
node-configurable-http-proxy_4.5.0+~cs15.1.4-4.dsc
 2bb8551c893b193adbb92173155132987c5859141a6f794d0afacfc98645baf0 29796 
node-configurable-http-proxy_4.5.0+~cs15.1.4-4.debian.tar.xz
Files: 
 2c7ecd0f47ac73000e83e939de20c476 4255 javascript optional 
node-configurable-http-proxy_4.5.0+~cs15.1.4-4.dsc
 a5e2d08b9bad874dd50f20ec04699d32 29796 javascript optional 
no

Bug#1008511: marked as pending in node-configurable-http-proxy

[Yadd]

Control: tag -1 pending

Hello,

Bug #1008511 in node-configurable-http-proxy reported by you has been fixed in 
the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/js-team/node-configurable-http-proxy/-/commit/9eb965655715acd00eb8d80425ae7bf5ee2e2dc0


Add fix for node-commander 9

Closes: #1008511


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008511

Processed: Bug#1008511 marked as pending in node-configurable-http-proxy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008511 [node-configurable-http-proxy] FTBFS failures in the upstream test 
suite
Added tag(s) pending.

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

Bug#1008611: bambam autopkgtest failure with pygame 2.1

[peter green]

Package: bambam
Version: 1.1.2+dfsg-1
Severity: serious
Tags: bookworm, sid

Bambam's autopkgtest is failing with the new version of pygame (which is needed 
to fix a FTBFS bug).

https://ci.debian.net/data/autopkgtest/testing/amd64/b/bambam/20441215/log.gz


autopkgtest [05:37:55]: test smoke: xvfb-run -e $AUTOPKGTEST_ARTIFACTS/xvfb-run.stderr -s 
"-screen 0 1024x768x24 -fbdir $AUTOPKGTEST_TMP" ./debian/tests/smoke-meat
autopkgtest [05:37:55]: test smoke: [---
2022-03-29 05:37:55,304 INFO root: Polling to observe a mostly-white screen 
(which means that bambam has started).
2022-03-29 05:37:55,359 INFO root: On attempt 0 the average screen color was 
[0, 0, 0].
ALSA lib confmisc.c:855:(parse_card) cannot find card '0'
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_card_inum 
returned error: No such file or directory
ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_concat returned 
error: No such file or directory
ALSA lib confmisc.c:1334:(snd_func_refer) error evaluating name
ALSA lib conf.c:5178:(_snd_config_evaluate) function snd_func_refer returned 
error: No such file or directory
ALSA lib conf.c:5701:(snd_config_expand) Evaluate error: No such file or 
directory
ALSA lib pcm.c:2664:(snd_pcm_open_noupdate) Unknown PCM default
2022-03-29 05:37:55,660 INFO root: On attempt 1 the average screen color was 
[0, 0, 0].
2022-03-29 05:37:55,960 INFO root: On attempt 2 the average screen color was 
[249, 249, 249].
2022-03-29 05:37:55,960 INFO root: Found mostly white screen, looks like bambam 
started up OK.
2022-03-29 05:37:56,085 INFO root: Took a screenshot to: 
/tmp/autopkgtest-lxc.85c6rb3_/downtmp/smoke-artifacts/startup.png
2022-03-29 05:37:56,086 INFO root: Simulating space and letter keypresses and 
measuring average screen color, to test functionality.
2022-03-29 05:37:56,172 INFO root: On attempt 0 the average screen color was 
too close to white: 249,249,249.

<--snip-->

2022-03-29 05:39:22,535 INFO root: On attempt 999 the average screen color was 
too close to white: 249,249,249.
2022-03-29 05:39:22,660 INFO root: Took a screenshot to: 
/tmp/autopkgtest-lxc.85c6rb3_/downtmp/smoke-artifacts/exception.png
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.85c6rb3_/downtmp/build.G3p/src/./debian/tests/smoke-meat", line 
108, in 
main()
  File 
"/tmp/autopkgtest-lxc.85c6rb3_/downtmp/build.G3p/src/./debian/tests/smoke-meat",
 line 26, in main
test_functionality()
  File 
"/tmp/autopkgtest-lxc.85c6rb3_/downtmp/build.G3p/src/./debian/tests/smoke-meat",
 line 62, in test_functionality
raise Exception('Failed to see a colorful enough screen after %d key 
presses.' % (attempt_count * 2))
Exception: Failed to see a colorful enough screen after 2000 key presses.


Looking at the test artifacts there seems to be no change in the screen content 
between startup.png and exception.png
both are blank other than the menus.

Bug#1008608: r-cran-purrrogress: autopkgtest failure: Error in `is(pb, c("winProgressBar", "tkProgressBar", "txtProgressBar"))`: length(class2) == 1L is not TRUE

[Nilesh Patra]

Package: r-cran-purrrogress
Version: 0.1.1-3
Severity: serious

Dear Maintainer,

r-cran-purrrogress is failing its autopkgtest, some of the output
is pasted below.

| ══ Failed tests 

| ── Error (apply.R:86:5): with_apply_progress 
───
| Error in `is(pb, c("winProgressBar", "tkProgressBar", "txtProgressBar"))`: 
length(class2) == 1L is not TRUE
| Backtrace:
| ▆
|  1. ├─base::sapply(...) at R/apply.R:86:4
|  2. │ └─base::match.fun(FUN)
|  3. └─purrrogress::with_progress(...)
|  4.   └─purrrogress:::with_apply_progress(i, ..., fun = fun)
|  5. └─purrrogress:::push_progress(pb, "with_progress")
|  6.   └─methods::is(pb, c("winProgressBar", "tkProgressBar", 
"txtProgressBar"))
|  7. └─base::stopifnot(length(class2) == 1L)
| ── Error (purrr.R:193:5): with_purrr_progress 
──
| Error in `is(pb, c("winProgressBar", "tkProgressBar", "txtProgressBar"))`: 
length(class2) == 1L is not TRUE

Full log at: 
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-purrrogress/20434057/log.gz

Regards,
Nilesh

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

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

Versions of packages r-cran-purrrogress depends on:
ii  r-base-core [r-api-4.0]  4.1.2-1
ii  r-cran-assertthat0.2.1-2
ii  r-cran-glue  1.5.1-1
ii  r-cran-hms   1.1.1-1
pn  r-cran-pkgcond   
ii  r-cran-purrr 0.3.4-1+b1
ii  r-cran-r62.5.1-1
ii  r-cran-rlang 0.4.12-2
pn  r-cran-testextra 

Versions of packages r-cran-purrrogress recommends:
ii  r-cran-testthat  3.1.0-2

Versions of packages r-cran-purrrogress suggests:
ii  r-cran-covr 3.5.1+dfsg-2
ii  r-cran-stringi  1.7.6-1
ii  r-cran-tibble   3.1.6+dfsg-1

Bug#1007248: marked as done (nodejs: Tries to overwrite a file in a different package)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 12:49:08 +
with message-id 
and subject line Bug#1007248: fixed in nodejs 16.14.2+dfsg-2
has caused the Debian Bug report #1007248,
regarding nodejs: Tries to overwrite a file in a different package
to be marked as done.

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

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


-- 
1007248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007248
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nodejs
Version: 12.22.10~dfsg-1
Severity: serious
Justification: Policy 7.3

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I'm not entirely sure, but I _think_ this issue should be fixed with
some Breaks+Replaces relation and a quick search showed para 7.3.

Got an update to the above package version and that failed (initially):

Unpacking nodejs (12.22.10~dfsg-1) over (12.22.9~dfsg-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-aZNJZq/17-nodejs_12.22.10~dfsg-1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/systemtap/tapset/node.stp', which is also in 
package libnode72:amd64 12.22.9~dfsg-1
Preparing to unpack .../18-libnode72_12.22.10~dfsg-1_amd64.deb ...
Unpacking libnode72:amd64 (12.22.10~dfsg-1) over (12.22.9~dfsg-1) ...
Preparing to unpack .../19-libspice-server1_0.15.0-3_amd64.deb ...
...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-aZNJZq/17-nodejs_12.22.10~dfsg-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
...
Current status: 1 (+1) broken, 1 (-39) upgradable.

Doing another 'aptitude safe-upgrade' run after that succeeded though.

Cheers,
  Diederik

- -- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

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

Versions of packages nodejs depends on:
ii  libc6  2.33-7
ii  libnode72  12.22.10~dfsg-1

Versions of packages nodejs recommends:
ii  ca-certificates  20211016
pn  nodejs-doc   

Versions of packages nodejs suggests:
pn  npm  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCYi9qDQAKCRDXblvOeH7b
bpfWAP937cVfZWJN2MKeEPDcUarx0qTuujNew2Z5dMu1J6JQnAEA5/uT9ciwOw1R
9lZYZEyuvpT1JL/wvWQ1ABLIlViDIgQ=
=AB8j
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: nodejs
Source-Version: 16.14.2+dfsg-2
Done: Jérémy Lal 

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated nodejs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Mar 2022 14:33:32 +0200
Source: nodejs
Architecture: source
Version: 16.14.2+dfsg-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Closes: 1007248
Changes:
 nodejs (16.14.2+dfsg-2) experimental; urgency=medium
 .
   * Update nobuiltin to pkg.nodejs.nobuiltin
   * nodejs breaks: (Closes: #1007248)
 + libnode72 < 12.22.10~dfsg
 + libnode83 < 16.13.2+really14.19.1~dfsg
   * README.source: improve explanations
   * rules: two-stage builds w.r.t. node-acorn
   * watch: remove node-acorn component
Checksums-Sha1:
 b6fa573ae74011ca0d89b771141a80f9b4d71f3a 4145 nodejs_16.14.2+dfsg-2.dsc
 aa429d4050b206455bc547ff4da58a7f31b1b99a 155676 
nodejs_16.14.2+dfsg-2.debian.tar.xz
 2b67edb2f0b17542e28eea48061cf47bfdd0af14 10260 
nodejs_16.14.2+dfsg-2_source.buildinfo
Checksums-Sha256:
 6ddceb4c8704fe047f2ed05a1876727e34bc11f106f55d9818bad0cda667db74 4145 
nodejs_16.14.2+dfsg-2.dsc
 069683dda197b9e9abb6cdc9d7e9a7a147d8eac7f1b6960ba8a07b6f8fff081f 155676 
nodejs_16.14.2+dfsg-2.debian.tar.xz
 545b4044a83b3867405f2336fc5b9c0032800bdcdfb2bcb5686bb51a7c278b90 10260 

Bug#1007234: Test suite fails on all but amd64 arches

[Mathieu Malaterre]

Bryan,

On Tue, Mar 29, 2022 at 1:45 PM Mathieu Malaterre  wrote:
>
> Bryan,
>
> On Sat, Mar 26, 2022 at 2:00 AM Bryan Henderson  
> wrote:
> >
> > I don't know familiar you are with debuggers, C, or C arithmetic, so I'm
> > attaching a diagnostic version of the program and will also explain where I
> > think the problem lies in case you want to investigate on your own.

I am going to discard the test-suite result in Debian package.
Something is not quite right on my side.

Compiling netpbm with gcc-10+ubsan gives odd results on my amd64:

== palm-roundtrip.test ==
pamdepth: promoting from black and white to grayscale
pnmcolormap: making histogram...
pnmcolormap: Scanning image 0
pnmcolormap: 20314 colors so far
pnmcolormap: 20314 colors found
pnmcolormap: choosing 256 colors...
pnmremap: 256 colors found in colormap
pmfileio.c:664:26: runtime error: left shift of 128 by 24 places
cannot be represented in type 'int'
pmfileio.c:664:26: runtime error: left shift of 128 by 24 places
cannot be represented in type 'int'
pmfileio.c:664:26: runtime error: left shift of 128 by 24 places
cannot be represented in type 'int'
pmfileio.c:664:26: runtime error: left shift of 128 by 24 places
cannot be represented in type 'int'
palm-roundtrip.test: FAILURE

I am going to /assume/ code is not tested on arch other than amd64, so
I think this is acceptable behavior.


Thanks for your help.

Bug#1007234: Test suite fails on all but amd64 arches

[Mathieu Malaterre]

Bryan,

On Sat, Mar 26, 2022 at 2:00 AM Bryan Henderson  wrote:
>
> I don't know familiar you are with debuggers, C, or C arithmetic, so I'm
> attaching a diagnostic version of the program and will also explain where I
> think the problem lies in case you want to investigate on your own.
>
> If you put this .c file in converter/other/pnmtopalm/ and rebuild and run the
> 'palmtopnm' executable that results, it should detect the failure and write
> some useful diagnostic messages.  Tell me what happens.

Thanks !

Here is what I see on my local riscv64/chroot

== palm-roundtrip.test ==
pamdepth: promoting from black and white to grayscale
palmtopnm: Invalid Palm image input.  Header says 30 bytes per row
after uncompressing from 8-bit Packbits, but we counted 4294967069
bytes in a row, before we stopped processing the row
pnmcolormap: making histogram...
pnmcolormap: Scanning image 0
pnmcolormap: 20314 colors so far
pnmcolormap: 20314 colors found
pnmcolormap: choosing 256 colors...
pnmremap: 256 colors found in colormap
palmtopnm: Invalid Palm image input.  Header says 228 bytes per row
after uncompressing from 8-bit Packbits, but we counted 4294967044
bytes in a row, before we stopped processing the row
palm-roundtrip.test: FAILURE


Pay attention that I cannot do any kind of gdb locally:

 % gdb ./converter/other/pnmtopalm/palmtopnm
[...]
(gdb) r
Starting program:
/home/mathieu/debian/netpbm/converter/other/pnmtopalm/palmtopnm
warning: Could not trace the inferior process.
warning: ptrace: Function not implemented
During startup program exited with code 127.


>
> The problem is in function 'readPackBitsRow16'.  The variable 'j' is getting
> too large -- absurdly large, apparently because a bit code that is supposed to
> encode a negative signed integer is being interpreted as a positive unsigned
> one somewhere.  It should not be hard to pinpoint where the arithmetic is
> generating such a a large number.
>
> --
> Bryan Henderson   San Jose, California

Bug#1008520: marked as done (cctbx hard-codes the python version in it's local patches)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 11:18:49 +
with message-id 
and subject line Bug#1008520: fixed in cctbx 2021.12+ds1-4
has caused the Debian Bug report #1008520,
regarding cctbx hard-codes the python version in it's local patches
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.)


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

Package: src:cctbx
Version: 2021.12+ds1-3
Severity: serious
Tags: sid bookworm
User: debian-pyt...@lists.debian.org
Usertags: python3.10

cctbx hard-codes the python version in it's local patches, and thus breaks with 
python 3.10 as the default python version. Please don't do that.
--- End Message ---
--- Begin Message ---
Source: cctbx
Source-Version: 2021.12+ds1-4
Done: Neil Williams 

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

Debian distribution maintenance software
pp.
Neil Williams  (supplier of updated cctbx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Mar 2022 10:16:15 +0100
Source: cctbx
Architecture: source
Version: 2021.12+ds1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Neil Williams 
Closes: 1008520
Changes:
 cctbx (2021.12+ds1-4) unstable; urgency=medium
 .
   * Use sysconfig to obtain path to boost_python to avoid needing the
 python version in the system_libs patch in boost_adaptbx/SConsscript
 (Closes: #1008520)
Checksums-Sha1:
 bec86fd8b5fe005b97539c2f215f2c9663e8afa3 2727 cctbx_2021.12+ds1-4.dsc
 053fd12f00a3ba50877071bd17d5ee2cd97a795e 23324 
cctbx_2021.12+ds1-4.debian.tar.xz
 56b51660f5f00ac3724ad51c83a48d6ea667cc4f 13529 
cctbx_2021.12+ds1-4_amd64.buildinfo
Checksums-Sha256:
 e885ed81e96f9b8c6d618461af73e33d20c5bff9b44821278e771050b677c82c 2727 
cctbx_2021.12+ds1-4.dsc
 2a0568782ecdf44f67cdc732c55bec793270908a8e9e986c581a3a58e2a7ee9d 23324 
cctbx_2021.12+ds1-4.debian.tar.xz
 63396177a75cfb2d2dfe9c0bd0b0bf2f76b9c55784cc0faf4f4e1e054c888195 13529 
cctbx_2021.12+ds1-4_amd64.buildinfo
Files:
 19f96d8e554424cb774e2ad8f11ecac3 2727 science optional cctbx_2021.12+ds1-4.dsc
 66549dd570ab95d8fc561aab611738e0 23324 science optional 
cctbx_2021.12+ds1-4.debian.tar.xz
 093430ccc56a0c06bbe42cda08003b5e 13529 science optional 
cctbx_2021.12+ds1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEf3HB6ceOc10DYMbM8WfkPIFDtoIFAmJC3gwACgkQ8WfkPIFD
toKJ1RAAwWNsk2ORpdWoZ0n1TXtieZ8pYZqpTEF1AG/x4YYcfAPcHQnV7Q5w6m6U
XEqSxK9YaES3aiOelbth0su22/qkkP10p5lHtHsGbK3jUmd2OkdXpAQU3EmWVE4W
6IcVYtd6lzSC+fRc/csg/vePYc/wmfdIbKL1v9FwLiaHyKTFFWvk+Zj4nuWjd1wp
Va8kxvuRxOehzFhspbVyMNXS6ySqWBcRTWjF91w3m9OR6nIAQLlX/SKKZBsCqu3h
R+gZluCiX4zAKcuj9sx9pIWpuc4t8cdYmEToSFj4uoJHyPWLwxmtAJsDOobwegpf
+WESEjHgOXmL325RblaRqUV25ehkmEYVAsZBdTrcrChPtRNXTgEP4alyi02lYzYg
hb8sN6zF4XAyCuINekAtGMlgJJK1wk2giw8j2joUcWbRK6Eu4fLbH8yVH/eOTt8x
bcXNz8JDZ/n2/tnbeELm/oELrvaeHSqW8NtX+F1vieb75+dB50TuBbj+aIJYTyGY
DNbu7gtvwKpyJ3uL181lwWwHgG221vBbPwxC7xkNmCosgtp7VGC6Rmu9VrJy/JM1
34EndJdMSbYBA7tfJ62nAQlRWHFUSdxJq0Z2WTpS0WhhQn5tyil2c0rpLe6bc4aH
qZdo4vpMdN+2wY1HbW8W0s6lv+w7X2+7+e0bB0ZSje5wjuj8irU=
=V1Ux
-END PGP SIGNATURE End Message ---

Bug#1008598: marked as done (python3-websockets: Does not work with python3.10)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 10:21:43 +
with message-id 
and subject line Bug#1008598: fixed in python-websockets 10.2-1
has caused the Debian Bug report #1008598,
regarding python3-websockets: Does not work with python3.10
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.)


-- 
1008598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-websockets
Version: 9.1-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: tipos...@tiscali.it

Dear Maintainer,

it seems that this library is calling functions with parameter that were 
deprecated and
are now removed in python3.10

Specifically, it looks like it passes loop= and tries to pass None after a 
certain version of
python.

However that does not work since the parameter does not exist at all.

This is making localslackirc fail to function, since it makes use of this 
library.

Best

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

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

Versions of packages python3-websockets depends on:
ii  python3  3.10.4-1

python3-websockets recommends no packages.

python3-websockets suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: python-websockets
Source-Version: 10.2-1
Done: Piotr Ożarowski 

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

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated python-websockets 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Mar 2022 11:52:05 +0200
Source: python-websockets
Architecture: source
Version: 10.2-1
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Piotr Ożarowski 
Closes: 1008598
Changes:
 python-websockets (10.2-1) unstable; urgency=medium
 .
   * New upstream release
 - supports Python 3.10 (closes: 1008598)
Checksums-Sha1:
 4302f7cb768b9b4b47ff621d0839f121e1729def 2090 python-websockets_10.2-1.dsc
 69388fe70c3f2a6a2ad7b194598af5bcb5ce1ac9 83402 
python-websockets_10.2.orig.tar.gz
 ddf073f099d4cd2cd137f9ac35eaf05f1b2dd632 3268 
python-websockets_10.2-1.debian.tar.xz
 ecc2646c1585a0fbd33cfbf331ac0d1e55671381 6909 
python-websockets_10.2-1_amd64.buildinfo
Checksums-Sha256:
 5ef94127dc09cd2602e89d62b616fe7b9ca4384a5a45ff0a6f27f84d9cd768a2 2090 
python-websockets_10.2-1.dsc
 8351c3c86b08156337b0e4ece0e3c5ec3e01fcd14e8950996832a23c99416098 83402 
python-websockets_10.2.orig.tar.gz
 842ba4b8617148a6d5b6250b8673c4b8b04d42551685d37e6fc09d75892099ab 3268 
python-websockets_10.2-1.debian.tar.xz
 5723dc3defe6ce4119097f5d1e84d08635e751f24ee0f8bda5484602c3b69f43 6909 
python-websockets_10.2-1_amd64.buildinfo
Files:
 9d9a7cb7c1dad8f07109f7bc4e0fd761 2090 python optional 
python-websockets_10.2-1.dsc
 b917be5391934f872145c0473d8d8e41 83402 python optional 
python-websockets_10.2.orig.tar.gz
 8848d68f9343fb0660facffec205bef2 3268 python optional 
python-websockets_10.2-1.debian.tar.xz
 4bf71b7783f01fe9ec3de442a0225e3b 6909 python optional 
python-websockets_10.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHS+omFjar2IXhi33rvbxoqdFdkUFAmJC19MACgkQrvbxoqdF
dkWV9Q/7Bu2zZJm/VJRTKd5IvNtwIZ8zcEkWV6nMgDTaIBlRUDrcjr7AgA2Djite
J5vyJL7TY9zOecB8aH4GwnikEHHK1ljWP2vXTjAGArCSjXra7YUy4OmPJdYD0ery
vBHUABhc2z2bqDCpI9U3X7y4r+sSEdNcb7fIFNTSt4GASwXI7FNwNh3T3pt0M3/v
y192cBDSmKWpOtKdhvwIXpzBBEkv/Da6TXiyif7tqFs6Hu9kku1VO3Nw0SUFWzNc
VbaEycK1k57VA9jtPtLHH1iGtBlFXKfcmD30ENrRFM2Eyg7VxxFNsAdcdO8Sa3IF
q9yGujPuUl8XPvSDhIVbLZHWe8G7zn45Pt7EnQ4yFrSQIHwtwIvC+njt4NKjf4OJ
qpKc89p8w6wajCfIX4/+MXbJWN3AzxVLJ4VAV2nyO7c9WXEwZSLaL8Xw1kE6h/NM
uldE4zX+p8AkCZ00y

Processed: Patch with the fix

[Debian Bug Tracking System]

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

> tags 1008598 + patch
Bug #1008598 [python3-websockets] python3-websockets: Does not work with 
python3.10
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1008598: Patch with the fix

[Salvo Tomaselli]

tags 1008598 + patch
thanks

I attach a patch to fix the issue.

I tested locally and it seems to be working fine for me.

Best.

-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

http://ltworf.github.io/ltworf/
Description: This passes the loop parameter only on the supported versions
 The loop parameter has been deprecated for years.
 .
 This library is buggy, and on the versions where the parameter is deprecated
 it passes a None.
 .
 This actually broke when the parameter was removed for real, since the
 parameter should not be passed at all instead.
Bug-Debian: #1008598
From: Salvo 'LtWorf' Tomaselli 

--- python-websockets-9.1.orig/src/websockets/legacy/protocol.py
+++ python-websockets-9.1/src/websockets/legacy/protocol.py
@@ -151,8 +151,11 @@ class WebSocketCommonProtocol(asyncio.Pr
 self._paused = False
 self._drain_waiter: Optional[asyncio.Future[None]] = None
 
+kwloop = {}
+if sys.version_info[:2] < (3, 8):
+kwloop['loop'] = self.loop
 self._drain_lock = asyncio.Lock(
-loop=loop if sys.version_info[:2] < (3, 8) else None
+**kwloop
 )
 
 # This class implements the data transfer and closing handshake, which
@@ -225,6 +228,9 @@ class WebSocketCommonProtocol(asyncio.Pr
 raise exc
 if self.transport is not None:
 if self.transport.is_closing():
+kwloop = {}
+if sys.version_info[:2] < (3, 8):
+kwloop['loop'] = self.loop
 # Yield to the event loop so connection_lost() may be
 # called.  Without this, _drain_helper() would return
 # immediately, and code that calls
@@ -232,7 +238,7 @@ class WebSocketCommonProtocol(asyncio.Pr
 # in a loop would never call connection_lost(), so it
 # would not see an error when the socket is closed.
 await asyncio.sleep(
-0, loop=self.loop if sys.version_info[:2] < (3, 8) else None
+0, **kwloop
 )
 await self._drain_helper()
 
@@ -399,12 +405,15 @@ class WebSocketCommonProtocol(asyncio.Pr
 pop_message_waiter: asyncio.Future[None] = self.loop.create_future()
 self._pop_message_waiter = pop_message_waiter
 try:
+kwloop = {}
+if sys.version_info[:2] < (3, 8):
+kwloop['loop'] = self.loop
 # If asyncio.wait() is canceled, it doesn't cancel
 # pop_message_waiter and self.transfer_data_task.
 await asyncio.wait(
 [pop_message_waiter, self.transfer_data_task],
-loop=self.loop if sys.version_info[:2] < (3, 8) else None,
 return_when=asyncio.FIRST_COMPLETED,
+**kwloop,
 )
 finally:
 self._pop_message_waiter = None
@@ -596,10 +605,13 @@ class WebSocketCommonProtocol(asyncio.Pr
 
 """
 try:
+kwloop = {}
+if sys.version_info[:2] < (3, 8):
+kwloop['loop'] = self.loop
 await asyncio.wait_for(
 self.write_close_frame(serialize_close(code, reason)),
 self.close_timeout,
-loop=self.loop if sys.version_info[:2] < (3, 8) else None,
+**kwloop,
 )
 except asyncio.TimeoutError:
 # If the close frame cannot be sent because the send buffers
@@ -615,12 +627,15 @@ class WebSocketCommonProtocol(asyncio.Pr
 # Other calls will receive a CancelledError here.
 
 try:
+kwloop = {}
+if sys.version_info[:2] < (3, 8):
+kwloop['loop'] = self.loop
 # If close() is canceled during the wait, self.transfer_data_task
 # is canceled before the timeout elapses.
 await asyncio.wait_for(
 self.transfer_data_task,
 self.close_timeout,
-loop=self.loop if sys.version_info[:2] < (3, 8) else None,
+**kwloop,
 )
 except (asyncio.TimeoutError, asyncio.CancelledError):
 pass
@@ -1039,10 +1054,13 @@ class WebSocketCommonProtocol(asyncio.Pr
 return
 
 try:
+kwloop = {}
+if sys.version_info[:2] < (3, 8):
+kwloop['loop'] = self.loop
 while True:
 await asyncio.sleep(
 self.ping_interval,
-loop=self.loop if sys.version_info[:2] < (3, 8) else None,
+**kwloop,
 )
 
 # ping() raises CancelledError if the connection is closed,
@@ -1055,10 +1073,13 @@ class WebSocketCommonP

Bug#1008598: python3-websockets: Does not work with python3.10

[Salvo "LtWorf" Tomaselli]

Package: python3-websockets
Version: 9.1-1
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: tipos...@tiscali.it

Dear Maintainer,

it seems that this library is calling functions with parameter that were 
deprecated and
are now removed in python3.10

Specifically, it looks like it passes loop= and tries to pass None after a 
certain version of
python.

However that does not work since the parameter does not exist at all.

This is making localslackirc fail to function, since it makes use of this 
library.

Best

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

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

Versions of packages python3-websockets depends on:
ii  python3  3.10.4-1

python3-websockets recommends no packages.

python3-websockets suggests no packages.

-- no debconf information

Processed: limit source to cctbx, tagging 1008520

[Debian Bug Tracking System]

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

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

> tags 1008520 + pending
Bug #1008520 [src:cctbx] cctbx hard-codes the python version in it's local 
patches
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: cloning 1008509, reopening -1, severity of -1 is important ...

[Debian Bug Tracking System]

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

> clone 1008509 -1
Bug #1008509 {Done: Yadd } [node-config] FTBFS - six upstream 
tests failing
Bug 1008509 cloned as bug 1008593
> reopen -1
Bug #1008593 {Done: Yadd } [node-config] FTBFS - six upstream 
tests failing
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions node-config/3.3.7-2.
> severity -1 important
Bug #1008593 [node-config] FTBFS - six upstream tests failing
Severity set to 'important' from 'serious'
> retitle -1 node-config not compatible with ts-node 10
Bug #1008593 [node-config] FTBFS - six upstream tests failing
Changed Bug title to 'node-config not compatible with ts-node 10' from 'FTBFS - 
six upstream tests failing'.
> thanks
Stopping processing here.

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

Bug#1008509: marked as done (FTBFS - six upstream tests failing)

[Debian Bug Tracking System]

Your message dated Tue, 29 Mar 2022 08:43:42 +
with message-id 
and subject line Bug#1008509: fixed in node-config 3.3.7-2
has caused the Debian Bug report #1008509,
regarding FTBFS - six upstream tests failing
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.)


-- 
1008509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008509
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-config
Version: 3.3.7-1
Severity: serious
Tags: ftbfs

While rebuilding your package with an unstable sbuild, it failed at six
points in the upstream test suite, with the same error:

» An unexpected error was caught: TypeError: Cannot set
property offset of [object Object] which has only a getter


Cheers,

J.Puydt
--- End Message ---
--- Begin Message ---
Source: node-config
Source-Version: 3.3.7-2
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-config package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Mar 2022 09:09:31 +0200
Source: node-config
Architecture: source
Version: 3.3.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1008509
Changes:
 node-config (3.3.7-2) unstable; urgency=medium
 .
   * Team upload
   * Drop test that require an old ts-node (Closes: #1008509)
Checksums-Sha1: 
 05af9027be537e6b3041a61b8fb92032569829ee 2128 node-config_3.3.7-2.dsc
 c46ba83968222d3cb1ef3dd69390cb0dcb820469 4472 node-config_3.3.7-2.debian.tar.xz
Checksums-Sha256: 
 958b4cb5fadf49ac2b03183a58fd172398d1c35ad93b7f45f151d93e27b56a8f 2128 
node-config_3.3.7-2.dsc
 0de514e76797a564c5637ff1e8673d5752e1455c39ac4a2201fb783f1aa9 4472 
node-config_3.3.7-2.debian.tar.xz
Files: 
 c3de14e04bc3a1a3423028da207d1117 2128 javascript optional 
node-config_3.3.7-2.dsc
 8c367c2ab52aa085e358e2daf88f9077 4472 javascript optional 
node-config_3.3.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJCvP8ACgkQ9tdMp8mZ
7ukICg//YAXMkPGFPsAVk+33b7OTa67W5vuUoa4M+7D9w/Dajehe+V3Hje2e1VJT
9r/oxa8LvsLkglzPWqYbFRTBffm5NlfgwKj3NWqynLYbZJLjbAeTSQ9gpe0dzMM+
GEEDCETHDTjdN9P1Ow8zY3LjU5UKJfrGncwCmPrTWTuzu/zh2KnzbolFq2m6hvHW
bxbT3y1o+7Z+pThuWaZma11wKpVJ+e9fNYgLdNCti6mNxgAQkJuRPNG+w+1Ea22P
lgFWQCKl2lU+cFp6HWr2xbii84JRVQG3Do9imMSmKY5RRHUDNZ5OMFJH2oM3b5wG
V7+3yaPg/sK1qSAhodWR/a2r98ykMMLOhcR/QhM51C9FPBDSAYoXkZriX4H8b7XK
Hs5/Ss5K9Kb4qgw2TBNrvO8e3E9lFn0vgMkefqakDtgO21wztdVNLVSQJcgG0KNH
bkP8cB0o38zhuNauunAF0NUkLYWOjMm9T93IhfA/FOK2wxjGxtVE/pOi4IhdGosE
UiD5cnkXBXDfEKb3Vh6ggL4T8E/huIUNsbCbqNKsWA2lMiOqCF8qHSROIztUeAbN
1i52MGw/9bdqk8uUQ/gaojBOBOkVEkN3n44Yn7YTQp9BqKmCdpRIb3FBQJFaxdBx
VBP30habSwhpKWqVB2BaqW4OkyU5/zLK+I9/XMopAecZbpySrlc=
=J29I
-END PGP SIGNATURE End Message ---

Processed: Bug#1008509 marked as pending in node-config

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008509 [node-config] FTBFS - six upstream tests failing
Added tag(s) pending.

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

Bug#1008509: marked as pending in node-config

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-config/-/commit/0830e6f8dd116ccd356ca31c9adf2cb7b3ad9f8d


Drop test that require an old ts-node

Closes: #1008509


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008509

Bug#1008520: cctbx hard-codes the python version in it's local patches

[Neil Williams]

On Mon, 28 Mar 2022 12:01:02 +0200 Matthias Klose 
wrote:
> Package: src:cctbx
> Version: 2021.12+ds1-3
> Severity: serious
> Tags: sid bookworm
> User: debian-pyt...@lists.debian.org
> Usertags: python3.10
> 
> cctbx hard-codes the python version in it's local patches, and thus
> breaks with python 3.10 as the default python version. Please don't
> do that.

What is the justification for this severity? Other packages need
patches to support new versions of dependencies.

I will investigate how to get SCons to pick up the boostpython system
libs again but it may be necessary to retain the current patch method
and I don't see why that is against Policy. It's not pretty, I agree,
but I have not (yet) found an alternative.

-- 
Neil Williams
=
https://linux.codehelp.co.uk/


pgp_qW6x49AKO.pgp
Description: OpenPGP digital signature