Bug#996068: gnome-shell-extension-panel-osd: does not declare compatibility with GNOME Shell 41

[Tobias Frost]

Source: gnome-shell-extension-panel-osd
Version: 1.0.50.gc032923-1
Followup-For: Bug #996068

Possibly a patch: 
https://gitlab.com/jenslody/gnome-shell-extension-panel-osd/-/merge_requests/32

(At least some commenter says it works with 41. Did not test myself.)

-- 
tobi

Bug#990428: Info received (Add fixed package to upcoming 11.3?)

[Frank Liu]

Debian 11.3 was released over the weekend, and the ifenslave fix in this
bug report is still not included.

Bug#1006999: marked as done (python-plac: Non-determinstically FTBFS on amd64/unstable due to timing in tests)

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 03:04:03 +
with message-id 
and subject line Bug#1006999: fixed in python-plac 1.3.5-1
has caused the Debian Bug report #1006999,
regarding python-plac: Non-determinstically FTBFS on amd64/unstable due to 
timing in tests
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.)


-- 
1006999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-plac
Version: 1.3.4-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
Tags: fbtfs

Dear maintainer,

python-plac will randomly fail to build because the testsuite performs
timing/benchmarking. This will vary on (for example) CPU and I/O load.

   test3 
_
  
  def test3():
  t0 = time.time()
  plac.runp([gen(9), gen(9)])
  >   assert int(time.time() - t0) == 1 # it must take 1 second, not 2
  E   assert 2 == 1
  E +2
  E -1
  
  
/build/1st/python-plac-1.3.4/.pybuild/cpython3_3.9_plac/build/doc/test_runp.py:26:
 AssertionError
  === short test summary info 

  FAILED doc/test_runp.py::test3 - assert 2 == 1
  = 1 failed, 28 passed in 6.12s 
=

  […]

The full build log is attached or can be viewed here:

  
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/python-plac_1.3.4-1.rbuild.log.gz


Regards,

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


python-plac.1.3.4-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: python-plac
Source-Version: 1.3.5-1
Done: Paul Wise 

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

Debian distribution maintenance software
pp.
Paul Wise  (supplier of updated python-plac package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Mar 2022 10:54:48 +0800
Source: python-plac
Architecture: source
Version: 1.3.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Paul Wise 
Closes: 1006999
Changes:
 python-plac (1.3.5-1) unstable; urgency=medium
 .
   * New upstream release.
   * - Removes non-deterministic test (Closes: #1006999)
Checksums-Sha1:
 ee80433e01b346376bbd15b414e5a39dfac4da66 2062 python-plac_1.3.5-1.dsc
 d4f7d07b656f6a1b4c1abbcd5e2946c5496b9d23 61539 python-plac_1.3.5.orig.tar.gz
 8b82a7937f20d8d56d9da582f2b0fbad60fda892 3176 python-plac_1.3.5-1.debian.tar.xz
 1c8117a026e1c83ceee4c8eff1bd39a6da922321 6944 
python-plac_1.3.5-1_amd64.buildinfo
Checksums-Sha256:
 6540f62ff77aeefd6f9f38800c2ced183750ed5faf3eb7d1b83810a5757f26d0 2062 
python-plac_1.3.5-1.dsc
 78a2bbef78c6463366d4b48692a86af00d4d4f7dfbe233583ca36fc5918f7ac6 61539 
python-plac_1.3.5.orig.tar.gz
 cf0a5f0806fd89ca6c2b7bfb50176d9d3a0279acb09471bafd5a9b26d8bd2a01 3176 
python-plac_1.3.5-1.debian.tar.xz
 bb86ea168de345f726e0832c6c2653beb1f88abb36a73d47309d13d351e57d87 6944 
python-plac_1.3.5-1_amd64.buildinfo
Files:
 bad720c8c57b5ceda992d0dbc27c3854 2062 python optional python-plac_1.3.5-1.dsc
 effc9d1ab3a2c072991a71541550e69f 61539 python optional 
python-plac_1.3.5.orig.tar.gz
 a067449ef61409f58b98941f6a7c62cf 3176 python optional 
python-plac_1.3.5-1.debian.tar.xz
 49d14d1481796e81716632b1dfd8a251 6944 python optional 
python-plac_1.3.5-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAmJFGRgACgkQMRa6Xp/6
aaOy0g/+K7xX54Wq8+nlo850ARaiqu14A8zt5HviQIaU4rwyAs6bueVbepjGrLDm
WJ2mkwPTrdwt3HKBqB8KyPhHU0aPMCo0/eU+rwiwpRVRNX+/eoqPynVxMfqHoRsH
2Z28AtOM1tt/5MG8Sy27Ggouj+MnFgbaiSYX+1zh9ViNm0nD+6Ikomdx6m5HImiX
p3aVCuqxmf7971K7RmjhPxGF2bmrzu9udTXSYAjsXYnFlqQgX/6X3cnwP06qMhD+
b/q51Szwmu3NJvnpwYvp8YtJ7qj1Vw1ViPhMEqVJYVvu8bSR76KU8ymnaBFaW795

Processed: gnome-icon-theme-yasis: diff for NMU version 0.4.2-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 965560 + patch
Bug #965560 [src:gnome-icon-theme-yasis] gnome-icon-theme-yasis: Removal of 
obsolete debhelper compat 5 and 6 in bookworm
Added tag(s) patch.
> tags 965560 + pending
Bug #965560 [src:gnome-icon-theme-yasis] gnome-icon-theme-yasis: Removal of 
obsolete debhelper compat 5 and 6 in bookworm
Added tag(s) pending.

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

Bug#965560: gnome-icon-theme-yasis: diff for NMU version 0.4.2-1.2

[Guilherme de Paula Xavier Segundo]

Control: tags 965560 + patch
Control: tags 965560 + pending

Dear maintainer,

I've prepared an NMU for gnome-icon-theme-yasis (versioned as 0.4.2-1.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.
diff -u gnome-icon-theme-yasis-0.4.2/debian/changelog gnome-icon-theme-yasis-0.4.2/debian/changelog
--- gnome-icon-theme-yasis-0.4.2/debian/changelog
+++ gnome-icon-theme-yasis-0.4.2/debian/changelog
@@ -1,3 +1,19 @@
+gnome-icon-theme-yasis (0.4.2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Using new DH level format. Consequently:
+  - debian/compat: removed.
+  - debian/control: changed from 'debhelper' to 'debhelper-compat' in
+Build-Depends field and bumped level to 13.
+  - Closes: #965560
+  * Dropped CDBS in favor of the debhelper to allow the build system to use
+DH level greater than 11. Consequently:
+  - debian/control: removed no longer needed cdbs from Build-Depends
+field.
+  - debian/rules: changed from CBDS to DH.
+
+ -- Guilherme de Paula Xavier Segundo   Wed, 30 Mar 2022 17:09:43 -0300
+
 gnome-icon-theme-yasis (0.4.2-1.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.

Bug#1008670: marked as done (librust-structopt+lints-dev uninstallable due to change in clap 2.34)

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 23:20:01 +
with message-id 
and subject line Bug#1008670: fixed in rust-structopt 0.3.26-2
has caused the Debian Bug report #1008670,
regarding librust-structopt+lints-dev uninstallable due to change in clap 2.34
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.)


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

Package: librust-structopt+lints-dev
Version: 0.3.26-1
Severity: serious

clap 2.34 dropped the "lints" feature, this has left librust-structopt+lints-dev
uninstallable in unstable and is blocking the migration to testing of the new
versions of clap and textwrap.

Since rust-structopt+lints-dev has no reverse dependencies I would propose 
simply
dropping it. Any objections?
--- End Message ---
--- Begin Message ---
Source: rust-structopt
Source-Version: 0.3.26-2
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-structopt, 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.
Peter Michael Green  (supplier of updated rust-structopt 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Mar 2022 22:52:55 +
Source: rust-structopt
Architecture: source
Version: 0.3.26-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1008670
Changes:
 rust-structopt (0.3.26-2) unstable; urgency=medium
 .
   * Team upload.
   * Package structopt 0.3.26 from crates.io using debcargo 2.5.0
   * Disable "lint" feature, it's dependencies are no longer satisfiable
 with clap 2.34 (Closes: 1008670)
Checksums-Sha1:
 b60fe8ae5cd9b746972ebb87093c199dc6708eac 3266 rust-structopt_0.3.26-2.dsc
 e9e41e88dbbcd4920f3af579dd882fad658110f6 4584 
rust-structopt_0.3.26-2.debian.tar.xz
 095a5958b51aceca3afa35be0682a8bb6186d8ce 9092 
rust-structopt_0.3.26-2_source.buildinfo
Checksums-Sha256:
 bced2d0b7e1b0327284c6481ca608edd4985b61b06dfea4d12f022484e98cdae 3266 
rust-structopt_0.3.26-2.dsc
 a1262900137a13ec2d71d9dbc77dd9e466f5578ce9e019131876f8a7952952b6 4584 
rust-structopt_0.3.26-2.debian.tar.xz
 515d0a47af8d96e8cbf731ff82c8ff458b4d526dfa3642f2a2038c47f711f081 9092 
rust-structopt_0.3.26-2_source.buildinfo
Files:
 1e53b336e650db1335438a4acb32dcb1 3266 rust optional rust-structopt_0.3.26-2.dsc
 04cf7b4868b1b409cbfa3a98737527e3 4584 rust optional 
rust-structopt_0.3.26-2.debian.tar.xz
 7e0322a0ba06cb906ab6bca6ce545be0 9092 rust optional 
rust-structopt_0.3.26-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmJE3+kUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XuWDw//U4uQf6zWwQ4SCH3rI8XnSF6676P8
r2sXA1F5vnrhXNl592ZDAA1T8Lh76kpSy4zCtuj9XwoSlZRf29lDS+9MfNMVG8A9
zlwZD6ngaVYfa0jd0onGr6msTZiPPAi6Bu1763n+UZxzLNpRRJmJ0tGKAyX77KuG
ox1dViCCkJGaHlPcc5BZtuEmg6JqVYgVcn85wQF5UCva4eXq2vs5lE2WWS/U6qPk
m5JqgJGVcAkA7SWsLDm5ifGrd89Dj0v68Y+o8nlykeUs2tC1LK2FkEBNxNPourPH
J/ggu1wbbgpqB+TEkMXLL3d6HSMNoXYJ/o/2zB97JlIZR6a5mFzmZUIiXLbYFPyk
8g8ua+sI5tN+tDz+mNQzOP8bRykC+tAeAxVHaU5j6lgL0pN8pFZDKlDf94VSuZjf
Yo6FIKS97niEVgM5g9POYmP0WrED63kWypQ7W5fwKWmyEx8vbwgeV9pUWV0jp8Y3
GeLAJ6Z6MDmTfaz7VYeUX78Oa41MQgM2RsaGeOSA4XQClEGo1Z6eW20Fu5xBMQDF
7yLrHGVwZqkovjO1VlqYtaJILsyejHR4tjzmdq6hmCqVXatf5dFwDoODR/TfUikA
Jf7rlgviXXTmfhFEaC3NemjYk3YiQcblvvL0n0zBUKRuJAw+6G3Ara0zBBJzTeLY
BBWzQOuyHd5LVZY=
=EmTp
-END PGP SIGNATURE End Message ---

Bug#1008669: marked as done (libsbml FTBFS with Python 3.10)

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 22:50:47 +
with message-id 
and subject line Bug#1008669: fixed in libsbml 5.19.0+dfsg-2
has caused the Debian Bug report #1008669,
regarding libsbml FTBFS with Python 3.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.)


-- 
1008669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsbml
Version: 5.19.0+dfsg-1
Severity: serious
Tags: ftbfs bookworm sid

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

...
[ 99%] Swig Python source
Traceback (most recent call last):
  File "/<>/src/bindings/python/doc-converter/rewrite_pydoc.py", 
line 121, in 
from formatter import NullWriter, AbstractFormatter
ModuleNotFoundError: No module named 'formatter'
make[4]: *** 
[src/bindings/python/CMakeFiles/binding_python_swig.dir/build.make:633: 
src/bindings/python/libsbml_wrap.cpp] Error 1


The Ubuntu patch seems to contain a fix.
--- End Message ---
--- Begin Message ---
Source: libsbml
Source-Version: 5.19.0+dfsg-2
Done: Étienne Mollier 

We believe that the bug you reported is fixed in the latest version of
libsbml, 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 libsbml 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 22:25:04 +0200
Source: libsbml
Architecture: source
Version: 5.19.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1008669
Changes:
 libsbml (5.19.0+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Add python3.10.patch from Frank T. Bergmann to fix FTBFS with python3.10.
 Thanks to Adrian Bunk (Closes: #1008669)
   * Standards-Version: 4.6.0 (routine-update)
Checksums-Sha1:
 3cce6d9982f8a03c7144b1b84e9fd2920d34c785 3704 libsbml_5.19.0+dfsg-2.dsc
 e49f80d3aab567d7a4b9f0bfbe23b89efc672fdb 32696 
libsbml_5.19.0+dfsg-2.debian.tar.xz
 44b0d0c40c8001a6ae53f0f1c32e53b6ccf45416 39086 
libsbml_5.19.0+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 14718416ed263ae2fa5b00da4072156f6d407a8c34595b0fd7074099f46a459a 3704 
libsbml_5.19.0+dfsg-2.dsc
 d432898914718a23cd2812a3359038f27a1f82af43d887e459327aea6c00afab 32696 
libsbml_5.19.0+dfsg-2.debian.tar.xz
 0da865bb914cdbe9faffdad0e9d3d6e3fb9efa39b13b67210a1fb8267a2d62ec 39086 
libsbml_5.19.0+dfsg-2_amd64.buildinfo
Files:
 5f05aac802cfde44cf5a0d680b978a23 3704 science optional 
libsbml_5.19.0+dfsg-2.dsc
 020c55696b0ed8a7673b9a7caf194fb0 32696 science optional 
libsbml_5.19.0+dfsg-2.debian.tar.xz
 af81feae4eb103b594298ba1dc54f8e3 39086 science optional 
libsbml_5.19.0+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmJE1KMUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdp/rBAAu7pmI70JD/pKm/Smn9YFjJeFBqq5
5+acxC5jl0rZCvKAmbG1WiWQaLgiosq98omQnOt2p2o1Etvz/UzINvYvtHUKIqp4
QiciWm8ePKS87Ds+S4sPPraplBaS92pfPyDmxZUANLXRhQB9zr4cWnjRTAAWjHdQ
kqGO2pmSPPNT5+2DoyBFPQzI+tigib+lY1gguQ2lAXnDbokKAkkD5yyGDg21nG94
5o9MyViJy6y5J1zC15i+R9oNlLOaMTaj/UMRWM8XHspsAHcmrjXZw/k0MsCfyy1M
EykDqvMAUd4tK2ZUN4Nhbe5619YhXfQZLrIlaUePxytpTP1vBiwUo7wFm3PvwZrG
lErQOFvJY8VrphU3dQid7cT0zFF/W35zMgTMLKAPEb2D9myZhSmNrteHfe20MtaZ
XhG4IZ4ZMEEMjx1H8SxAiFqOUtP3158Vq4SH7K2HPa42BbI4hHVn6qbSuWEx50/y
JCy6fE3aojOz2p0cLCdMtNjBMYCyEAaCY8XSprkMJQYwoaISo2lbLC8JLkD9H6Dy
lUiJ4IC51PcP6oY1JvWS4OrIe5LP0bA2413scvSueYhH4q3gSnCNZOBPTCIFAMhA
lXcyQopAxqUyK9ZmtdJ9LKUQsiRLs+fvvcQBdVAOlmMUa42x2fRIX85Jg/lLV28d
j3xlC0qB6wXipg8=
=leIp
-END PGP SIGNATURE End Message ---

Bug#1008700: [Pkg-electronics-devel] Bug#1008700: Should geda-gaf be removed?

[Bdale Garbee]

Moritz Muehlenhoff  writes:

> Source: geda-gaf
> Version: 1:1.8.2-11
> Severity: serious
>
> Your package came up as a candidate for removal from Debian:

For the record, I've previously indicated that I consider lepton-eda a
complete replacement for geda-gaf in Debian.  It was forked some years
ago, is actively maintained, and still reads existing geda-gaf designs
and library files perfectly.  I contribute to lepton-eda upstream, and
actively maintain the lepton-eda package in Debian.

I do wonder if there's some action we can/should take when removing
geda-gaf to ease the transition for existing users of the package to
lepton-eda?  Perhaps replace the package content with dependency
information causing the replacement to be more or less automatic on
upgrades?  [shrug]

Bdale


signature.asc
Description: PGP signature

Processed: tagging 1008708

[Debian Bug Tracking System]

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

> tags 1008708 + sid bookworm
Bug #1008708 [pysolfc] pysolfc: After installing python3.10, pysolfc cannot 
start
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#1008708: pysolfc: After installing python3.10, pysolfc cannot start

[Roger D. Cook]

Package: pysolfc
Version: 2.6.4-3
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer,

1. Attempted to start pysolfc through the menus; it failed to start.
2. Attempted to start from the command line; it failed to start with
   the following messaging:

$ pysolfc
Traceback (most recent call last):
  File "/usr/games/pysolfc", line 36, in 
from pysollib.main import main  # noqa: E402,I202
  File "/usr/share/games/pysolfc/pysollib/main.py", line 30, in 
from pysollib.app import Application
  File "/usr/share/games/pysolfc/pysollib/app.py", line 32, in 
from pysollib.images import Images, SubsampledImages
  File "/usr/share/games/pysolfc/pysollib/images.py", line 28, in 
from pysollib.pysoltk import copyImage, createBottom, createImage, loadImage
  File "/usr/share/games/pysolfc/pysollib/pysoltk.py", line 35, in 
from pysollib.tile.tkhtml import *  # noqa: F401,F403
  File "/usr/share/games/pysolfc/pysollib/tile/tkhtml.py", line 29, in 
from pysollib.ui.tktile.tkhtml import Base_HTMLViewer
  File "/usr/share/games/pysolfc/pysollib/ui/tktile/tkhtml.py", line 24, in 

import formatter
ModuleNotFoundError: No module named 'formatter'
$

Expected result is that the game starts.

After researching, I came across https://github.com/shlomif/PySolFC/issues/217
and https://github.com/shlomif/PySolFC/pull/218, which:
a) explained that the formatter module was deprecated in Python 3.4 and
   removed in 3.10, and
b) fixed the issue upstream in PySolFC version 2.14, released September 9,
   2021.

I believe the best fix is to import the newest version of pysolfc to the
Debian ecosystem.

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

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

Versions of packages pysolfc depends on:
ii  python33.10.4-1
ii  python3-configobj  5.0.6-5
ii  python3-pygame 2.1.2+dfsg-3
ii  python3-random21.0.1-2.1
ii  python3-six1.16.0-3
ii  python3-tk 3.9.12-1

Versions of packages pysolfc recommends:
ii  python3-pil.imagetk  9.0.1-1

Versions of packages pysolfc suggests:
ii  freecell-solver-bin  5.0.0-2+b1
ii  pysolfc-cardsets 2.0+dfsg2-2.1

-- no debconf information

Processed: Bug#1008669 marked as pending in libsbml

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008669 [src:libsbml] libsbml FTBFS with Python 3.10
Added tag(s) pending.

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

Bug#1008639: marked as done (libsigrokdecode: FTBFS: ./.libs/libsigrokdecode.so: undefined reference to `PyList_Insert')

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 21:23:56 +
with message-id 
and subject line Bug#1008639: fixed in libsigrokdecode 0.5.3-3
has caused the Debian Bug report #1008639,
regarding libsigrokdecode: FTBFS: ./.libs/libsigrokdecode.so: undefined 
reference to `PyList_Insert'
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.)


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

Bug#1008669: marked as pending in libsbml

[Étienne Mollier]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/libsbml/-/commit/4651e5beb95a3cb6ad64199f6d3907f895f9ebab


Add python3.10.patch from Frank T. Bergmann

Closes: #1008669
Thanks: Adrian Bunk


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008669

Bug#1008611: marked as done (bambam autopkgtest failure with pygame 2.1)

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 21:18:58 +
with message-id 
and subject line Bug#1008611: fixed in bambam 1.1.2+dfsg-2
has caused the Debian Bug report #1008611,
regarding bambam autopkgtest failure with pygame 2.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.)


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

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.
--- End Message ---
--- Begin Message ---
Source: bambam
Source-Version: 1.1.2+dfsg-2
Done: Marcin Owsiany 

We believe that the bug you reported is fixed in the latest version of
bambam, 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.
Marcin Owsiany  (supplier of updated bambam 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 17:16:14 +0200
Source: bambam
Binary: bambam
Architecture: source all
Version: 1.1.2+dfsg-2
Distribution: sid
Urgency: medium
Maintainer: Marcin Owsiany 
Changed-By: Marcin Owsiany 
Description:
 bambam - keyboard mashing and doodling game for babies
Closes: 

Bug#1008704: Sould astk be removed?

[Moritz Muehlenhoff]

Source: astk
Version: 1.13.1-2.1
Severity: serious

Your package came up as a candidate for removal from Debian:

- Still depends on Python 2 and thus removed from testing since 2019
- Last maintainer upload in 2014

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1008703: Should sortsmill-tools be removed?

[Moritz Muehlenhoff]

Source: sortsmill-tools
Version: 0.4-2
Severity: serious

Your package came up as a candidate for removal from Debian:

- Still depends on Python and thus removed from testing since 2019
- Last upload in 2013

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1008702: Should ketchup be removed?

[Moritz Muehlenhoff]

Source: ketchup
Version: 1.0.1+git20111228+e1c62066-2
Severity: serious

Your package came up as a candidate for removal from Debian:

- Still depends on Python 2 and thus removed from testing since 2019
- Last upload in 2017
- Seems dead upstream (last commit from eight years ago)
- Per #946203 doesn't even suppport kernels using 5.x.x

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1008701: Should broctl be removed?

[Moritz Muehlenhoff]

Source: broctl
Version: 1.4-1
Severity: serious

Your package came up as a candidate for removal from Debian:

- Still uses Python 2.7 and thus removed from testing since 2019
- Last upload in 2015

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1008700: Should geda-gaf be removed?

[Moritz Muehlenhoff]

Source: geda-gaf
Version: 1:1.8.2-11
Severity: serious

Your package came up as a candidate for removal from Debian:

- Still depends on Python 2 and thus removed from testing since 2019
- Also uses outdated Guile
- Last upload in 2018

If you disagree and want to continue to maintain this package,
please just close this bug (and fix the open issues).

If you agree with the removal, please reassign to ftp.debian.org
by sending the following commands to cont...@bugs.debian.org:

--
severity $BUGNUM normal
reassign $BUGNUM ftp.debian.org
retitle $BUGNUM RM:  -- RoM; 
thx
--

Otherwise I'll move forward and request it's removal in a month.

Cheers,
Moritz

Bug#1008698: libprelude-dev: Depends on unavailable package libltdl3-dev

[Florian Ernst]

JFTR:

On Wed, Mar 30, 2022 at 10:00:26PM +0200, Florian Ernst wrote:
> libtool 2.4.7-2 started to not provide the virtual package libltdl3-dev
> anymore, and as such this package here is now uninstallable due to a
> Depends on it. [...]

Some more background can be found in
.

Best regards,
Flo


signature.asc
Description: PGP signature

Bug#1008695: nvidia-cuda-toolkit: CVE-2022-21821

[Andreas Beckmann]

Control: severity -1 important

On 30/03/2022 21.55, Salvatore Bonaccorso wrote:

Ha, nice race :) (#1008695 and 1008696).


;-)

I'll take your choice of severity.


Andreas

Processed: Re: Bug#1008695: nvidia-cuda-toolkit: CVE-2022-21821

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1008695 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821
Bug #1008696 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE‑2022‑21821
Severity set to 'important' from 'serious'
Severity set to 'important' from 'serious'

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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 965511 0.3-4
Bug #965511 {Done: Guilherme Xavier } 
[src:etherpuppet] etherpuppet: Removal of obsolete debhelper compat 5 and 6 in 
bookworm
Marked as fixed in versions etherpuppet/0.3-4.
>
End of message, stopping processing here.

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

Processed: reassign 1008695 to src:nvidia-cuda-toolkit, tagging 1008695, forcibly merging 1008695 1008696 ...

[Debian Bug Tracking System]

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

> reassign 1008695 src:nvidia-cuda-toolkit 4.0.13-1
Bug #1008695 [nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821
Bug reassigned from package 'nvidia-cuda-toolkit' to 'src:nvidia-cuda-toolkit'.
No longer marked as found in versions nvidia-cuda-toolkit/4.0.13-1.
Ignoring request to alter fixed versions of bug #1008695 to the same values 
previously set
Bug #1008695 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821
Marked as found in versions nvidia-cuda-toolkit/4.0.13-1.
> tags 1008695 + upstream security
Bug #1008695 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821
Added tag(s) upstream.
> forcemerge 1008695 1008696
Bug #1008695 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821
Bug #1008695 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821
Marked as found in versions nvidia-cuda-toolkit/11.4.3-2.
Bug #1008696 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE‑2022‑21821
Severity set to 'serious' from 'important'
Marked as found in versions nvidia-cuda-toolkit/4.0.13-1.
Merged 1008695 1008696
> found 1008695 11.4.3-2
Bug #1008695 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821
Bug #1008696 [src:nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE‑2022‑21821
Ignoring request to alter found versions of bug #1008695 to the same values 
previously set
Ignoring request to alter found versions of bug #1008696 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1008698: libprelude-dev: Depends on unavailable package libltdl3-dev

[Florian Ernst]

Package: libprelude-dev
Version: 5.2.0-5+b2
Severity: grave
Justification: renders package unusable

Hello there,

libtool 2.4.7-2 started to not provide the virtual package libltdl3-dev
anymore, and as such this package here is now uninstallable due to a
Depends on it.

For reference, libtool migrated to just providing libltdl3-dev from
libltdl-dev starting with 2.2.6a-2 from 30 Mar 2009, but now libltdl-dev
does not provide any such compatibility provides anymore.

Best regards,
Flo


signature.asc
Description: PGP signature

Processed (with 1 error): forcibly merging 1008695 1008696

[Debian Bug Tracking System]

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

> forcemerge 1008695 1008696
Bug #1008695 [nvidia-cuda-toolkit] nvidia-cuda-toolkit: CVE-2022-21821
Unable to merge bugs because:
package of #1008696 is 'src:nvidia-cuda-toolkit' not 'nvidia-cuda-toolkit'
Failed to forcibly merge 1008695: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#1008695: nvidia-cuda-toolkit: CVE-2022-21821

[Salvatore Bonaccorso]

Hi,

On Wed, Mar 30, 2022 at 09:35:16PM +0200, Andreas Beckmann wrote:
> Package: nvidia-cuda-toolkit
> Version: 4.0.13-1
> Severity: serious
> Tags: security
> 
> https://nvidia.custhelp.com/app/answers/detail/a_id/5334
> 
> CVE-2022-21821NVIDIA CUDA Toolkit SDK contains an integer overflow
> vulnerability in cuobjdump.To exploit this vulnerability, a remote attacker
> would require a local user to download a specially crafted, corrupted file
> and locally execute cuobjdump against the file. Such an attack may lead to
> remote code execution that causes complete denial of service and an impact
> on data confidentiality and integrity.
> 
> Affected Versions
> All versions prior to CUDA Toolkit 11.6 Update 2

Ha, nice race :) (#1008695 and 1008696).

Let's merge then.

Regards,
Salvatore

Processed: found 1008170 in 2.0.10+~2.0.2-3

[Debian Bug Tracking System]

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

> found 1008170 2.0.10+~2.0.2-3
Bug #1008170 [node-openid] FTBFS: randomly test failures
Marked as found in versions node-openid/2.0.10+~2.0.2-3.
> thanks
Stopping processing here.

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

Processed: tagging 1008688

[Debian Bug Tracking System]

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

> tags 1008688 + sid bookworm
Bug #1008688 [src:cwiid] cwiid: FTBFS with Python 3.10
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 16:42:18 -0300
with message-id 

and subject line Re: etherpuppet: Removal of obsolete debhelper compat 5 and 6 
in bookworm
has caused the Debian Bug report #965511,
regarding etherpuppet: 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.)


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

Hi,

The package etherpuppet 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 965511 0.3-5

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

Regards,
Guilherme Xavier--- End Message ---

Processed: reassign 1008650 to src:unbound, forcibly merging 1008641 1008650

[Debian Bug Tracking System]

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

> # … now with the correct package name
> reassign 1008650 src:unbound 1.13.1-1
Bug #1008650 [src:unbund] python3-unbound: Cannot install because of Python 
dependencies
Warning: Unknown package 'src:unbund'
Bug reassigned from package 'src:unbund' to 'src:unbound'.
No longer marked as found in versions unbund/1.13.1-1.
Ignoring request to alter fixed versions of bug #1008650 to the same values 
previously set
Bug #1008650 [src:unbound] python3-unbound: Cannot install because of Python 
dependencies
Marked as found in versions unbound/1.13.1-1.
> forcemerge 1008641 1008650
Bug #1008641 [src:unbound] unbound: FTBFS: ./pythonmod/pythonmod.c:338: 
undefined reference to `_Py_fopen'
Bug #1008650 [src:unbound] python3-unbound: Cannot install because of Python 
dependencies
Added tag(s) bookworm, sid, and ftbfs.
Merged 1008641 1008650
> thanks
Stopping processing here.

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

Bug#1008695: nvidia-cuda-toolkit: CVE-2022-21821

[Andreas Beckmann]

Package: nvidia-cuda-toolkit
Version: 4.0.13-1
Severity: serious
Tags: security

https://nvidia.custhelp.com/app/answers/detail/a_id/5334

CVE-2022-21821  NVIDIA CUDA Toolkit SDK contains an integer overflow
vulnerability in cuobjdump.To exploit this vulnerability, a remote attacker
would require a local user to download a specially crafted, corrupted file
and locally execute cuobjdump against the file. Such an attack may lead to
remote code execution that causes complete denial of service and an impact
on data confidentiality and integrity.

Affected Versions
All versions prior to CUDA Toolkit 11.6 Update 2


Andreas

Processed (with 1 error): Re: Bug#1008650: python3-unbound: Cannot install because of Python dependencies

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:unbund 1.13.1-1
Bug #1008650 [python3-unbound] python3-unbound: Cannot install because of 
Python dependencies
Bug reassigned from package 'python3-unbound' to 'src:unbund'.
Warning: Unknown package 'src:unbund'
Warning: Unknown package 'src:unbund'
No longer marked as found in versions unbound/1.13.1-1.
Warning: Unknown package 'src:unbund'
Warning: Unknown package 'src:unbund'
Ignoring request to alter fixed versions of bug #1008650 to the same values 
previously set
Warning: Unknown package 'src:unbund'
Bug #1008650 [src:unbund] python3-unbound: Cannot install because of Python 
dependencies
Warning: Unknown package 'src:unbund'
The source 'unbund' and version '1.13.1-1' do not appear to match any binary 
packages
Marked as found in versions unbund/1.13.1-1.
Warning: Unknown package 'src:unbund'
> severity -1 serious
Bug #1008650 [src:unbund] python3-unbound: Cannot install because of Python 
dependencies
Warning: Unknown package 'src:unbund'
Severity set to 'serious' from 'grave'
Warning: Unknown package 'src:unbund'
> forcemerge 1008641 -1
Bug #1008641 [src:unbound] unbound: FTBFS: ./pythonmod/pythonmod.c:338: 
undefined reference to `_Py_fopen'
Unable to merge bugs because:
package of #1008650 is 'src:unbund' not 'src:unbound'
Failed to forcibly merge 1008641: Did not alter merged bugs.


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

Bug#1008650: python3-unbound: Cannot install because of Python dependencies

[Sebastian Ramacher]

Control: reassign -1 src:unbund 1.13.1-1
Control: severity -1 serious
Control: forcemerge 1008641 -1

On 2022-03-30 06:55:21 +, Stephane Bortzmeyer wrote:
> Package: python3-unbound
> Version: 1.13.1-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> % sudo apt install python3-unbound
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  python3-unbound : Depends: python3 (< 3.10) but 3.10.4-1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> 
> Indeed, Python version on sid is:
> 
> % python3 --version
> Python 3.10.4

unbound currently FTBFS with Python 3.10. See #1008641.

Cheers

> 
> But:
> 
> % apt-cache show python3-unbound
> Package: python3-unbound
> Source: unbound
> Version: 1.13.1-1
> Installed-Size: 394
> Maintainer: unbound packagers 
> Architecture: armhf
> Depends: python3 (<< 3.10), python3 (>= 3.9~), python3:any, libc6 (>= 2.28), 
> libunbound8 (>= 1.9.0)
> ...
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: armhf (armv7l)
> 
> Kernel: Linux 4.14.269 (SMP w/2 CPU threads)
> Locale: LANG=C, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> Versions of packages python3-unbound depends on:
> ii  libc62.33-7
> ii  libunbound8  1.13.1-1
> ii  python3  3.10.4-1
> 
> python3-unbound recommends no packages.
> 
> python3-unbound suggests no packages.

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1008694: kdevelop-python: Build-Depends: python3.9-dev

[Graham Inggs]

Source: kdevelop-python
Version: 5.6.2-2
Severity: serious
Tags: ftbfs
Forwarded: https://bugs.kde.org/show_bug.cgi?id=438206
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

kdevelop-python has a hardcoded build-dependency on python3.9-dev.

Changing this to the generic python3-dev doesn't help now since the
package is not ready for 3.10, although there is some recent activity
in the forwarded bug.

Regards
Graham

Bug#1008691: mkdocs-material: Depends: python3-pymdownx but it is not installable

[Sebastian Ramacher]

Package: mkdocs-material
Version: 8.2.5-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

mkdocs-material cannot be installed in unsable:

$ apt install mkdocs-material
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mkdocs-material : Depends: python3-pymdownx but it is not installable
E: Unable to correct problems, you have held broken packages.


Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#1008690: cadabra2: FTBFS with Python 3.10

[Sebastian Ramacher]

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

cadabra2 FTBFS:

[  2%] Building CXX object core/CMakeFiles/cadabra2-cli.dir/cadabra2-cli.cc.o
cd /<>/obj-x86_64-linux-gnu/core && /usr/bin/c++ 
-DCDBPYTHON_NO_NOTEBOOK -I/usr/include/glibmm-2.4 
-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/<>/core/. 
-I/<>/libs/internal/include -I/<>/libs/whereami 
-I/<>/libs/base64 -I/<>/libs/dbg 
-I/<>/libs/linenoise -I/<>/libs/nlohmann 
-I/usr/include/python3.9 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -Wall -fvisibility=hidden 
-Wno-unused-but-set-variable -std=gnu++14 -MD -MT 
core/CMakeFiles/cadabra2-cli.dir/cadabra2-cli.cc.o -MF 
CMakeFiles/cadabra2-cli.dir/cadabra2-cli.cc.o.d -o 
CMakeFiles/cadabra2-cli.dir/cadabra2-cli.cc.o -c 
/<>/core/cadabra2-cli.cc
In file included from /<>/core/cadabra2-cli.cc:15:
/<>/core/cadabra2-cli.hh:9:10: fatal error: Python.h: No such file 
or directory
9 | #include 
  |  ^~
compilation terminated.


See
https://buildd.debian.org/status/fetch.php?pkg=cadabra2=amd64=2.3.6.8-1%2Bb1=1648450866=0

Cheers
-- 
Sebastian Ramacher

Bug#1008688: cwiid: FTBFS with Python 3.10

[Sebastian Ramacher]

Source: cwiid
Version: 0.6.91-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

cwiid FTBFS:

gcc -o wmgui main.o interface.o support.o -Wl,-z,relro -L../libcwiid 
-lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0 
-lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lharfbuzz -lfontconfig 
-lfreetype -lgthread-2.0 -pthread -lglib-2.0 -lm -lcwiid -lbluetooth
make[2]: Leaving directory '/<>/wmgui'
make  -C wminput
make[2]: Entering directory '/<>/wminput'
bison -y -d parser.y 
parser.y:44.1-14: warning: POSIX Yacc does not support %error-verbose [-Wyacc]
   44 | mawk -f action_enum.awk action_enum.txt > action_enum.c
%error-verbose
  | ^~
parser.y:44.1-14: warning: deprecated directive: ‘%error-verbose’, use ‘%define 
parse.error verbose’ [-Wdeprecated]
   44 | %error-verbose
  | ^~
  | %define parse.error verbose
py_plugin.c:38:10: fatal error: Python.h: No such file or directory
   38 | #include "Python.h"
  |  ^~
compilation terminated.
In file included from uinput.c:44:
conf.h:56:10: fatal error: y.tab.h: No such file or directory
   56 | #include "y.tab.h"
  |  ^
compilation terminated.
In file included from c_plugin.c:33:
conf.h:56:10: fatal error: y.tab.h: No such file or directory
   56 | #include "y.tab.h"
  |  ^
compilation terminated.
In file included from conf.c:56:
conf.h:56:10: fatal error: y.tab.h: No such file or directory
   56 | #include "y.tab.h"
  |  ^
compilation terminated.
parser.y: warning: fix-its can be applied.  Rerun with option '--update'. 
[-Wother]
mv -f y.tab.c parser.c


See
https://buildd.debian.org/status/fetch.php?pkg=cwiid=amd64=0.6.91-2%2Bb3=1648451564=0

Cheers
-- 
Sebastian Ramacher

Bug#1008689: getfem++: FTBFS with Python 3.10

[Sebastian Ramacher]

Source: getfem++
Version: 5.3+dfsg1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

getfem++ 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=getfem%2B%2B=amd64=5.3%2Bdfsg1-4%2Bb1=1648454264=0

Cheers
-- 
Sebastian Ramacher

Processed: biabam: diff for NMU version 0.9.7-7.3

[Debian Bug Tracking System]

Processing control commands:

> tags 965435 + patch
Bug #965435 [src:biabam] biabam: Removal of obsolete debhelper compat 5 and 6 
in bookworm
Added tag(s) patch.
> tags 965435 + pending
Bug #965435 [src:biabam] biabam: Removal of obsolete debhelper compat 5 and 6 
in bookworm
Added tag(s) pending.

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

Bug#965435: biabam: diff for NMU version 0.9.7-7.3

[Marcos Talau]

Control: tags 965435 + patch
Control: tags 965435 + pending

Dear maintainer,

I've prepared an NMU for biabam (versioned as 0.9.7-7.3) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru biabam-0.9.7/debian/changelog biabam-0.9.7/debian/changelog
--- biabam-0.9.7/debian/changelog   2019-04-04 21:14:31.0 -0300
+++ biabam-0.9.7/debian/changelog   2022-03-30 14:40:12.0 -0300
@@ -1,3 +1,14 @@
+biabam (0.9.7-7.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Using new DH level format. Consequently:
+- debian/compat: Remove.
+- debian/control: Change from 'debhelper' to 'debhelper-compat' in
+  Build-Depends field and bump level to 13.
+- Closes: #965435.
+
+ -- Marcos Talau   Wed, 30 Mar 2022 14:40:12 -0300
+
 biabam (0.9.7-7.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru biabam-0.9.7/debian/compat biabam-0.9.7/debian/compat
--- biabam-0.9.7/debian/compat  2019-04-04 21:12:21.0 -0300
+++ biabam-0.9.7/debian/compat  1969-12-31 21:00:00.0 -0300
@@ -1 +0,0 @@
-5
diff -Nru biabam-0.9.7/debian/control biabam-0.9.7/debian/control
--- biabam-0.9.7/debian/control 2019-04-04 21:14:31.0 -0300
+++ biabam-0.9.7/debian/control 2022-03-30 13:46:07.0 -0300
@@ -2,7 +2,7 @@
 Section: mail
 Priority: optional
 Maintainer: Thierry Randrianiriana 
-Build-Depends: debhelper (>= 5), quilt (>= 0.40)
+Build-Depends: debhelper-compat (= 13), quilt (>= 0.40)
 Standards-Version: 3.8.4
 Homepage: http://mmj.dk/biabam/
 


signature.asc
Description: PGP signature

Bug#1008433: marked as done (golang-honnef-go-tools: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 honnef.co/go/tools/analysis/code honnef.co/go/tools/analysis/edit honnef.co/go/to

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 18:04:20 +
with message-id 
and subject line Bug#1008433: fixed in golang-honnef-go-tools 2022.1-1
has caused the Debian Bug report #1008433,
regarding golang-honnef-go-tools: FTBFS: dh_auto_test: error: cd _build && go 
test -vet=off -v -p 8 honnef.co/go/tools/analysis/code 
honnef.co/go/tools/analysis/edit honnef.co/go/tools/analysis/facts 
honnef.co/go/tools/analysis/facts/nilness 
honnef.co/go/tools/analysis/facts/typedness honnef.co/go/tools/analysis/lint 
honnef.co/go/tools/analysis/report honnef.co/go/tools/cmd/keyify [...] 
honnef.co/go/tools/unused/typemap 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.)


-- 
1008433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-honnef-go-tools
Version: 2021.1.2-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 
> honnef.co/go/tools/analysis/code honnef.co/go/tools/analysis/edit 
> honnef.co/go/tools/analysis/facts honnef.co/go/tools/analysis/facts/nilness 
> honnef.co/go/tools/analysis/facts/typedness honnef.co/go/tools/analysis/lint 
> honnef.co/go/tools/analysis/report honnef.co/go/tools/cmd/keyify 
> honnef.co/go/tools/cmd/staticcheck honnef.co/go/tools/cmd/structlayout 
> honnef.co/go/tools/cmd/structlayout-optimize 
> honnef.co/go/tools/cmd/structlayout-pretty honnef.co/go/tools/config 
> honnef.co/go/tools/debug honnef.co/go/tools/go/ast/astutil 
> honnef.co/go/tools/go/callgraph honnef.co/go/tools/go/callgraph/cha 
> honnef.co/go/tools/go/callgraph/rta honnef.co/go/tools/go/callgraph/static 
> honnef.co/go/tools/go/gcsizes honnef.co/go/tools/go/ir 
> honnef.co/go/tools/go/ir/irutil honnef.co/go/tools/go/loader 
> honnef.co/go/tools/go/types/typeutil honnef.co/go/tools/internal/cache 
> honnef.co/go/tools/internal/cmd/ast-to-pattern 
> honnef.co/go/tools/internal/cmd/gogrep honnef.co/go/tools/internal/cmd/irdump 
> honnef.co/go/tools/internal/go/gcimporter honnef.co/go/tools/internal/gosmith 
> honnef.co/go/tools/internal/passes/buildir 
> honnef.co/go/tools/internal/renameio honnef.co/go/tools/internal/robustio 
> honnef.co/go/tools/internal/sharedcheck honnef.co/go/tools/internal/sync 
> honnef.co/go/tools/internal/testenv honnef.co/go/tools/knowledge 
> honnef.co/go/tools/lint/testutil honnef.co/go/tools/lintcmd 
> honnef.co/go/tools/lintcmd/runner honnef.co/go/tools/lintcmd/version 
> honnef.co/go/tools/pattern honnef.co/go/tools/printf 
> honnef.co/go/tools/quickfix honnef.co/go/tools/sarif 
> honnef.co/go/tools/simple honnef.co/go/tools/staticcheck 
> honnef.co/go/tools/staticcheck/fakejson 
> honnef.co/go/tools/staticcheck/fakereflect 
> honnef.co/go/tools/staticcheck/fakexml honnef.co/go/tools/structlayout 
> honnef.co/go/tools/stylecheck honnef.co/go/tools/unused 
> honnef.co/go/tools/unused/typemap
> internal/goarch
> internal/unsafeheader
> internal/goexperiment
> runtime/internal/atomic
> internal/goos
> internal/cpu
> runtime/internal/syscall
> internal/race
> sync/atomic
> unicode
> internal/abi
> runtime/internal/math
> runtime/internal/sys
> unicode/utf8
> internal/itoa
> math/bits
> internal/goversion
> internal/bytealg
> encoding
> unicode/utf16
> golang.org/x/xerrors/internal
> honnef.co/go/tools/internal/sync
> honnef.co/go/tools/sarif
> math
> honnef.co/go/tools/knowledge
> internal/nettrace
> container/list
> crypto/internal/subtle
> crypto/subtle
> vendor/golang.org/x/crypto/cryptobyte/asn1
> vendor/golang.org/x/crypto/internal/subtle
> runtime
> internal/reflectlite
> sync
> internal/testlog
> internal/singleflight
> internal/sysinfo
> math/rand
> runtime/cgo
> errors
> sort
> io
> internal/oserror
> strconv
> path
> vendor/golang.org/x/net/dns/dnsmessage
> crypto/elliptic/internal/fiat
> syscall
> container/heap
> golang.org/x/mod/semver
> strings
> bytes
> text/tabwriter
> hash
> reflect
> crypto
> hash/adler32
> hash/crc32
> crypto/internal/randutil
> crypto/hmac
> 

Bug#1008686: Puddletag: name 'operatorPrecedence' is not defined

[Javier Barroso]

Package:puddletag
Version:2.0.1-3
Severity: critical
Hello,

Running Debian sid, it is not possible to launch puddletag

Debian Forums has a possible fix:
https://forums.debian.net/viewtopic.php?f=6=151493

sudo sed -i 's/operatorPrecedence/infixNotation/g'
/usr/lib/python3/dist-packages/puddlestuff/audio_filter.py

Thanks!

Processed: tagging 953530

[Debian Bug Tracking System]

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

> tags 953530 + pending
Bug #953530 [samba-common-bin] samba-common-bin: post-install fails with "lock 
directory /run/samba does not exist"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: ruby2.7: ftbfs with autoconf 2.70

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #978900 [src:ruby2.7] ruby2.7: ftbfs with autoconf 2.70
Added tag(s) moreinfo.
> severity -1 normal
Bug #978900 [src:ruby2.7] ruby2.7: ftbfs with autoconf 2.70
Severity set to 'normal' from 'serious'

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

Bug#978900: ruby2.7: ftbfs with autoconf 2.70

[Andrej Shadura]

Control: tags -1 moreinfo
Control: severity -1 normal

On Thu, 31 Dec 2020 14:28:58 + Matthias Klose  wrote:

./configure: line 3496: syntax error near unexpected token `fi'
./configure: line 3496: `fi ;; #('
make[1]: *** [debian/rules:75: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:70: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



I cannot reproduce this failure.

--
Cheers,
  Andrej

Processed: fixed 995115 in 2.7.4-1+b1

[Debian Bug Tracking System]

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

> fixed 995115 2.7.4-1+b1
Bug #995115 [libruby2.7] /usr/bin/ruby: symbol lookup error: 
/lib/x86_64-linux-gnu/libruby-2.7.so.2.7: undefined symbol: rb_st_numhash
Marked as fixed in versions ruby2.7/2.7.4-1.
> thanks
Stopping processing here.

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

Bug#1008680: scipy: FTBFS with Python 3.10 as default

[Graham Inggs]

Source: scipy
Version: 1.7.3-2
Severity: serious
Tags: ftbfs patch
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], scipy FTBFS with Python
3.10 as the default version.  I've copied what I hope is the relevant
part of the log below.

I've also attached a patch against scipy 1.8.0-1exp2 that works for me.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/scipy.html


LANG=C python3 -msphinx -b html -d build/doctrees   source build/html
Running Sphinx v4.3.2

Exception occurred:
  File "/usr/lib/python3.10/distutils/__init__.py", line 19, in 
warnings.warn(_DEPRECATION_MESSAGE,
DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12. Use setuptools or check PEP 632 for potential
alternatives
The full traceback has been saved in /tmp/sphinx-err-9djw0js6.log, if
you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error
message can be provided next time.
A bug report can be filed in the tracker at
. Thanks!
SciPy (VERSION 1.7.3)
make[2]: *** [Makefile:122: html-build] Error 2
Description: Ignore distutils deprecation warnings in doc build
Author: Graham Inggs 
Last-Update: 2022-03-30

--- a/doc/source/conf.py
+++ b/doc/source/conf.py
@@ -149,6 +149,7 @@
 r"OpenSSL\.rand is deprecated",  # OpenSSL package in linkcheck
 r"Using or importing the ABCs from",  # 3.5 importlib._bootstrap
 r"'contextfunction' is renamed to 'pass_context'",  # Jinja
+r"distutils package is deprecated",
 ):
 warnings.filterwarnings(  # deal with other modules having bad imports
 'ignore', message=".*" + key, category=DeprecationWarning)

Bug#1008665: marked as done (node-react-popper: Package unusable due to missing build)

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 14:56:10 +
with message-id 
and subject line Bug#1008665: fixed in node-react-popper 2.2.5-5
has caused the Debian Bug report #1008665,
regarding node-react-popper: Package unusable due to missing build
to be marked as done.

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

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


-- 
1008665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-react-popper
Severity: grave
Justification: renders package unusable

This package was pushed without any care. Needed files aren't build
which render package unusable (as reported by autopkgtest!)
--- End Message ---
--- Begin Message ---
Source: node-react-popper
Source-Version: 2.2.5-5
Done: Yadd 

We believe that the bug you reported is fixed in the latest version of
node-react-popper, 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-react-popper 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 15:39:35 +0200
Source: node-react-popper
Architecture: source
Version: 2.2.5-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1008665
Changes:
 node-react-popper (2.2.5-5) unstable; urgency=medium
 .
   * Team upload
   * Build needed files (Closes: #1008665)
   * Add missing dependency to node-react
   * Drop crazy test
   * Drop useless build dependencies
Checksums-Sha1: 
 c68ec27129409536651fed6de693120379b5cb95 2244 node-react-popper_2.2.5-5.dsc
 fdaf20fb9adbdb66c9e028d66c896487d4b231f5 2944 
node-react-popper_2.2.5-5.debian.tar.xz
Checksums-Sha256: 
 a0ea91c42ffcd910bc185e3fe2547d1d134f29ac60b57a710823b7e584c0fa41 2244 
node-react-popper_2.2.5-5.dsc
 c82d4a6a73da99e0f19c38cbc3e82e0d6610d1cb3692a0eb821f34f25160863d 2944 
node-react-popper_2.2.5-5.debian.tar.xz
Files: 
 10d6a13be5ec096c173dd9b60d177b9e 2244 javascript optional 
node-react-popper_2.2.5-5.dsc
 fed605f3db3f8716f693797f94ad3dd2 2944 javascript optional 
node-react-popper_2.2.5-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJEXe8ACgkQ9tdMp8mZ
7ukinw/+MqPUg6AWkzQE7cYS5DJneG+29Mc24hp3EXgJ4qXs84H/DZrzBuJsr97w
mLJGZQyQaKUfVq6/CEhXyx0wXdR2EMh7Bc1mGowfRIMeRNsNQX/xlwrDnjcNgAhg
5CILwiSMnjTqtKoffS+W7uYj2fpEl827dfWteKun450LTQnX7EiKp7AodHyawq2C
mhCG72NsRQtaNFYh63TK/nxhsMko66Mn72lpygscGRySAZNJyj7Fw8rgIOigBLxY
5g8oiQMH6b39USHOp9o2PXMhfI8D+kD6YdR5jtApNnSfP8/6JNoFMKOqWghp6kqu
v7gf6oTTMxcpAvMTtKTl/LEFpFJRrgycfSQhTM0JGvuHsdo6V8KhESkPEDhPnJ4i
wjpdhS+bmAJZvXahTQEEtWo6tIBQRpbSzJe7CDwvoA5WLyBhv8G0E/IkRSNUESRL
YZ7sxWeDlKqf7X77RWjWQhrsGSYuvRaiKHfmO6ciPI4s35V1TAl8teJu5JrMUb3U
6vH+inmwDVjJt9sKS7I0OQO2441lN5OT07oOvY90q9VaktuINSmG7F7ZTiXqxbPu
FxnATCqGollBMdThG6fKD5+MyUY8CBI97ZFruO/MjWxcvIqLnDYAolvCExUdFfmr
gVJtL5AsIHwO16T/pXnAfvlgyhzlk/yDwTON/OWWKRbXxP0RkC8=
=a7K5
-END PGP SIGNATURE End Message ---

Bug#1008666: marked as done (node-popper2: Package unusable due to missing build)

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 13:53:51 +
with message-id 
and subject line Bug#1008666: fixed in node-popper2 2.11.2-2
has caused the Debian Bug report #1008666,
regarding node-popper2: Package unusable due to missing build
to be marked as done.

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

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


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

Another package pushed without building needed files...

$ dpkg -L node-popper2
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/node-popper2
/usr/share/doc/node-popper2/README.md.gz
/usr/share/doc/node-popper2/changelog.Debian.gz
/usr/share/doc/node-popper2/copyright
/usr/share/nodejs
/usr/share/nodejs/@popperjs
/usr/share/nodejs/@popperjs/core
/usr/share/nodejs/@popperjs/core/index.d.ts
/usr/share/nodejs/@popperjs/core/package.json
--- End Message ---
--- Begin Message ---
Source: node-popper2
Source-Version: 2.11.2-2
Done: Yadd 

We believe that the bug you reported is fixed in the latest version of
node-popper2, 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-popper2 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 15:25:08 +0200
Source: node-popper2
Architecture: source
Version: 2.11.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1008666
Changes:
 node-popper2 (2.11.2-2) unstable; urgency=medium
 .
   * Team upload
   * Build files using rollup and babel (Closes: #1008666)
   * Provides libjs-popper2
   * Drop crazy test
Checksums-Sha1: 
 40b05b71fa5af25d5e4e7f4a78f0aaded0a8bbda 2111 node-popper2_2.11.2-2.dsc
 bf121b7b04bf5f3f759fa7729cdf163580e75e2c 8404 
node-popper2_2.11.2-2.debian.tar.xz
Checksums-Sha256: 
 cf4eb27e11f49cead0501e4637326f28002dc1377bd712447b123ed655e60f2d 2111 
node-popper2_2.11.2-2.dsc
 00d7c0ffb9d1fe1e31c52efd9ecf8f615db4652cd110eb03cf1df91fbafdb46d 8404 
node-popper2_2.11.2-2.debian.tar.xz
Files: 
 ffba8bfc0063a0038670b64b44513f32 2111 javascript optional 
node-popper2_2.11.2-2.dsc
 df6149d1224ad7e37dec71a922398ff9 8404 javascript optional 
node-popper2_2.11.2-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmJEWpwACgkQ9tdMp8mZ
7umSVw//fXBrOCFYrIE1nIxOD7HG86xdKdWaljxHK4+Vv1T8B1sJlYD3YYd3+I9S
7n9qO5bnoQ0Fwh27aqIuhmcGrvikJ1Wvu0WpFt7Zfp2KzURhwaDEi/PYO+Couys1
hqfFgX8v19o/zwHY7wB+Ye64dpkr79uWcDeze/ZVcWfBpLBb0JpStaEFzJjRg5vr
SktSLqGJx0bD2O4CdlCst6OdWrndkveVWf/lSSLmSV9wi88zwu5VJKg0cqcsyH04
TLHJx8Sz57Ywv/S77gangGuYWK4O0ARAIIfYIDMH8lczA2TyU+BRF6+7zZfI8wcm
FXvZrFG64WCsePpZBRiAQCRk7nVRDIXzbxMeoryfgVhm44izrki/sRqKMjKevC4s
W4cpyjK4qDVdIUwAAR4pznsaJs/u1aQXdePiS5eiBgIkMSOwzj9AJVEt93Uz+vI/
q+SratJ5qPvE1cmv+qPfTjWLnprOKjcyd0f7GBrW7FNC3gWM28VPoE5+b4paasYG
6gL8JzJd2HM9Cv4OIUuUc1fJ3SqJ3B7eR0Lnr+f6dzNoISGtVVjqmdkMGRSClhzL
ZaTCxX8BLAocN/PRYxNjgB8oXTbpZS4bXFg8MquNLVmn4qsq4GikqVeTtyVfCVBh
zAp4vtFBJ/NwVOaeWhvPkN/+4vLPOCzlZmunnGGPqs3T07T0AU0=
=/FKO
-END PGP SIGNATURE End Message ---

Bug#1008666: marked as pending in node-popper2

[Yadd]

Control: tag -1 pending

Hello,

Bug #1008666 in node-popper2 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-popper2/-/commit/130262715d243845edec75c3e2fc4e5aa52ac97a


Build files using rollup and babel * Provides libjs-popper2

Closes: #1008666


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008666

Processed: Bug#1008666 marked as pending in node-popper2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008666 [node-popper2] node-popper2: Package unusable due to missing build
Added tag(s) pending.

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

Bug#1008670: [Pkg-rust-maintainers] Bug#1008670: librust-structopt+lints-dev uninstallable due to change in clap 2.34

[Sylvestre Ledru]

Le 30/03/2022 à 13:04, peter green a écrit :

Package: librust-structopt+lints-dev
Version: 0.3.26-1
Severity: serious

clap 2.34 dropped the "lints" feature, this has left librust-structopt+lints-dev
uninstallable in unstable and is blocking the migration to testing of the new
versions of clap and textwrap.

Since rust-structopt+lints-dev has no reverse dependencies I would propose 
simply
dropping it. Any objections?


Sounds good
Thanks,
S

Bug#1008380: marked as done (macromoleculebuilder: FTBFS: DensityMap.cpp:476:64: error: ‘gemmi::GridSetup’ has not been declared)

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 12:03:57 +
with message-id 
and subject line Bug#1008380: fixed in macromoleculebuilder 3.5+dfsg-5
has caused the Debian Bug report #1008380,
regarding macromoleculebuilder: FTBFS: DensityMap.cpp:476:64: error: 
‘gemmi::GridSetup’ has not been declared
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.)


-- 
1008380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: macromoleculebuilder
Version: 3.5+dfsg-4
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):
> /usr/bin/c++ -DBuildNtC -DLEPTON_BUILDING_STATIC_LIBRARY -DLepton_USAGE 
> -DMMBlib_EXPORTS -DUSE_MMB_CONSTEXPR -DUSE_OPENMM -isystem 
> /<>/include -isystem /usr/include/simbody -isystem 
> /usr/include/openmm -isystem /usr/include/openmm/reference -isystem /include 
> -isystem /<>/3rdparty/Lepton1.3/include -D BuildNtC -D 
> USE_OPENMM -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -O0 
> -fvisibility=hidden -O3 -DNDEBUG -fPIC -DMMB_BUILDING_SHARED_LIBRARY 
> -std=c++14 -MD -MT CMakeFiles/MMBlib.dir/src/CifOutput.cpp.o -MF 
> CMakeFiles/MMBlib.dir/src/CifOutput.cpp.o.d -o 
> CMakeFiles/MMBlib.dir/src/CifOutput.cpp.o -c 
> /<>/src/CifOutput.cpp
> In file included from /usr/include/gemmi/to_mmcif.hpp:80,
>  from /<>/src/CifOutput.cpp:10:
> /usr/include/gemmi/sprintf.hpp:26:4: warning: #warning "Using system 
> stb_sprintf.h, not the bundled one. It may not work." [-Wcpp]
>26 | #  warning "Using system stb_sprintf.h, not the bundled one. It may 
> not work."
>   |^~~
> /<>/src/DensityMap.cpp: In member function ‘void 
> DensityMap::loadParametersAndDensity_CCP4MAP()’:
> /<>/src/DensityMap.cpp:476:64: error: ‘gemmi::GridSetup’ has not 
> been declared
>   476 | map.setup ( 
> gemmi::GridSetup::ReorderOnly, NAN );
>   |
> ^
> [ 68%] Building CXX object CMakeFiles/MMBlib.dir/src/ProgressWriter.cpp.o
> /usr/bin/c++ -DBuildNtC -DLEPTON_BUILDING_STATIC_LIBRARY -DLepton_USAGE 
> -DMMBlib_EXPORTS -DUSE_MMB_CONSTEXPR -DUSE_OPENMM -isystem 
> /<>/include -isystem /usr/include/simbody -isystem 
> /usr/include/openmm -isystem /usr/include/openmm/reference -isystem /include 
> -isystem /<>/3rdparty/Lepton1.3/include -D BuildNtC -D 
> USE_OPENMM -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -O0 
> -fvisibility=hidden -O3 -DNDEBUG -fPIC -DMMB_BUILDING_SHARED_LIBRARY 
> -std=c++14 -MD -MT CMakeFiles/MMBlib.dir/src/ProgressWriter.cpp.o -MF 
> CMakeFiles/MMBlib.dir/src/ProgressWriter.cpp.o.d -o 
> CMakeFiles/MMBlib.dir/src/ProgressWriter.cpp.o -c 
> /<>/src/ProgressWriter.cpp
> [ 71%] Building CXX object 
> CMakeFiles/MMBlib.dir/src/NTC_PARAMETER_READER.cpp.o
> /usr/bin/c++ -DBuildNtC -DLEPTON_BUILDING_STATIC_LIBRARY -DLepton_USAGE 
> -DMMBlib_EXPORTS -DUSE_MMB_CONSTEXPR -DUSE_OPENMM -isystem 
> /<>/include -isystem /usr/include/simbody -isystem 
> /usr/include/openmm -isystem /usr/include/openmm/reference -isystem /include 
> -isystem /<>/3rdparty/Lepton1.3/include -D BuildNtC -D 
> USE_OPENMM -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -O0 
> -fvisibility=hidden -O3 -DNDEBUG -fPIC -DMMB_BUILDING_SHARED_LIBRARY 
> -std=c++14 -MD -MT CMakeFiles/MMBlib.dir/src/NTC_PARAMETER_READER.cpp.o -MF 
> CMakeFiles/MMBlib.dir/src/NTC_PARAMETER_READER.cpp.o.d -o 
> CMakeFiles/MMBlib.dir/src/NTC_PARAMETER_READER.cpp.o -c 
> /<>/src/NTC_PARAMETER_READER.cpp
> make[3]: *** [CMakeFiles/MMBlib.dir/build.make:345: 
> CMakeFiles/MMBlib.dir/src/DensityMap.cpp.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/03/26/macromoleculebuilder_3.5+dfsg-4_unstable.log

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

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

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

Processed: Bug#1008400 marked as pending in golang-github-prometheus-common

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008400 [src:golang-github-prometheus-common] 
golang-github-prometheus-common: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 8 
github.com/prometheus/common/config github.com/prometheus/common/expfmt 
github.com/prometheus/common/internal/bitbucket.org/ww/goautoneg 
github.com/prometheus/common/model github.com/prometheus/common/promlog 
github.com/prometheus/common/promlog/flag github.com/prometheus/common/route 
github.com/prometheus/common/server github.com/prometheus/common/sigv4 returned 
exit code 1
Added tag(s) pending.

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

Bug#1008400: marked as pending in golang-github-prometheus-common

[Martina Ferrari]

Control: tag -1 pending

Hello,

Bug #1008400 in golang-github-prometheus-common 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/go-team/packages/golang-github-prometheus-common/-/commit/8a1e20b21722ab31c1a00078b3fcacc961b13e6e


debian/rules: Avoid test failures with new crypto/x509. Closes: #1008400


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008400

Processed: affects 1008666

[Debian Bug Tracking System]

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

> affects 1008666 node-react-popper
Bug #1008666 [node-popper2] node-popper2: Package unusable due to missing build
Added indication that 1008666 affects node-react-popper
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 11:38:31 +
with message-id 
and subject line Bug#999125: fixed in yale 5.0.95-3
has caused the Debian Bug report #999125,
regarding yale: 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.)


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: yale
Source-Version: 5.0.95-3
Done: Javier Fernández-Sanguino Peña 

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

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

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated yale 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 27 Mar 2022 21:44:00 +0200
Source: yale
Architecture: source
Version: 5.0.95-3
Distribution: unstable
Urgency: medium
Maintainer: Francisco Manuel Garcia Claramonte 
Changed-By: Javier Fernández-Sanguino Peña 
Closes: 869335 999125
Changes:
 yale (5.0.95-3) unstable; urgency=medium
 .
   * debian/control:
 - Updated Standards version
 - Remove retired comaintainer (Closes: #869335)
 - Add VCS information pointing to new Salsa repository
 - Update to debian compatibility version 13, remove debian/compat
   * debian/rules:
 - Simplify to use debhelper (Closes: #999125)
   * debian/install: Create to install the files
   * debian/source/format: Declare version 3.0 (no patches currently for this
  package)
Checksums-Sha1:
 ed5fb181ebbbcf5866a64833d7b08fa200a57572 1918 yale_5.0.95-3.dsc
 58bcf0c2a7189a9f3de78ded612dd1110963e08d 5080 yale_5.0.95-3.debian.tar.xz
 882edbc2d52241756e29c5ec7abff58c57b128c3 6739 yale_5.0.95-3_i386.buildinfo
Checksums-Sha256:
 1c089456dea450e2e8ab401c3ee7dc8010eee1d7f14902c16f56b3868291e077 1918 
yale_5.0.95-3.dsc
 23813840935fc555da8ee85bee93b9e44bc364f0a413641ba83c7dfe43163293 5080 
yale_5.0.95-3.debian.tar.xz
 ad7187ef2a537ebab65c917297b8eb106e30f37878e17ad3a512b3d090b28f00 6739 
yale_5.0.95-3_i386.buildinfo
Files:
 5b0adc57af60069c730716ee6765fba0 1918 non-free/science optional 
yale_5.0.95-3.dsc
 b228398832426808bff614f18f3ee3e0 5080 non-free/science optional 
yale_5.0.95-3.debian.tar.xz
 29f7f8b2ce8d1e8faed27f8294240e99 6739 non-free/science optional 
yale_5.0.95-3_i386.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEFQ8Kq6ttIR3DT+AOix9vSKslf5gFAmJEPIQACgkQix9vSKsl
f5jEGBAAg9kwvDOh9kUcRSdUH5TsB58U/+4xJggFSPgHjBe6T2T9Q1/EkSX+Ree+
7RYXOzEA/nybiDlW9/upsDKLq7hRvsxgZXe0mHY/AO7hU/7UBxwn4fj+xRkED0Gj
EJXYdw3wkJOiGq9UNmbBCbhax+qsMoajAdEieLTYKZ6aLvi7d4Lj48ttaaDsSz2l
4GfH/LMwZeKlzglPAM9zWbCl/bAEt+MbiyuBV6l3P0e/GLlVi2J5YXSoKayrmLla
zLEsUf5igAe1TcWI+7dqDLDfjywYWGLui5I0cncqzUolIA+B2Zk15oCXkdDoCe6t
4BbLHzQQi6PyYK6G8bhVr3ssdXuRRLOX/s3CH39aB7AQ3oE1B+CLwOnPt0Hjp0yv
/DBEv5EZLvkRMGhtMrIJwiFd0P1ek6XLZ2AhIwwtPbXg68OIVugnSu8ORIZoJBhf
cwTWzMgGvS4lu5q+LFNFD8Hs+fSRnPyeBC8tXjtU3xukT1x3fVvrui3/h3XUdCbI
fLOPczmViQmRMLbsQU3XiEhGfJwnT16aN3bOh9TmHyV/cGwMqHgub+amBqUw0Ojj
hN7H40iF9dhCCcmnlG70eZeVv+aBUNlNjjZkox5MjjbwvBBtQo4I5TEvWkFajTO0
SsMbMxdiDBsVnLdhi7sj/et1146ab9i6ya+vr2qqf56yuvQbzpc=
=r8iq
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 11:34:13 +
with message-id 
and subject line Bug#999146: fixed in gliese 3.0.95-3
has caused the Debian Bug report #999146,
regarding gliese: 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.)


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

Dear maintainer,

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

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

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

Best,

Lucas
--- End Message ---
--- Begin Message ---
Source: gliese
Source-Version: 3.0.95-3
Done: Javier Fernández-Sanguino Peña 

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

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

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated gliese 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 27 Mar 2022 20:56:20 +0200
Source: gliese
Architecture: source
Version: 3.0.95-3
Distribution: unstable
Urgency: medium
Maintainer: Francisco Manuel Garcia Claramonte 
Changed-By: Javier Fernández-Sanguino Peña 
Closes: 869334 999146
Changes:
 gliese (3.0.95-3) unstable; urgency=medium
 .
   * debian/control:
 - Update to Debian Policy 4.6.0.1 (no changes required)
 - Update to debhelper compability version 13
 - Change primary maintainer and remove Kevin McCarty from Uploader list
   (Closes: #869334)
 - Added package to autobuild and add some headers to keep lintian happy
   * debian/rules: Simplify debian/rules to use debhelper (Closes: #999146)
   * debian/source/format: Added as 3.0
 - Removed the changes to the Makefile (which are not required anyway)
 - Convert the gliese.spec changes into a patch
Checksums-Sha1:
 0fa7e6e51defa75c56429bd58e6ad6e758e9202d 1943 gliese_3.0.95-3.dsc
 453f1147f4431bb418c65b9bcccdde5c90f8cf2a 5300 gliese_3.0.95-3.debian.tar.xz
 443fb1400155641c4e44e499620c5b6e8f43755a 6755 gliese_3.0.95-3_i386.buildinfo
Checksums-Sha256:
 e86593b8cbf34cc77d8688983475f1e58a55cdd8414295c1ccc584a7c871f4a6 1943 
gliese_3.0.95-3.dsc
 a1b9ebe1cfdba43015bcf7ecd9e33917a32b3cbf40397162818328c0c2660dfa 5300 
gliese_3.0.95-3.debian.tar.xz
 83440d6fcc23abae1380ec7166e672496f14dcd9e01ffc90f8e2718792c94112 6755 
gliese_3.0.95-3_i386.buildinfo
Files:
 d7dd7d76ca875f06445a0f1fcc5990cf 1943 non-free/science optional 
gliese_3.0.95-3.dsc
 37517eb69935ae108f5917a99ee38cad 5300 non-free/science optional 
gliese_3.0.95-3.debian.tar.xz
 b0556d2d11a1833e03c441ffd9bcf81b 6755 non-free/science optional 
gliese_3.0.95-3_i386.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEFQ8Kq6ttIR3DT+AOix9vSKslf5gFAmJEPB4ACgkQix9vSKsl
f5jYtA//e6lulpCAJn7P7mbc6Mewwji4+0r1+0yEOg2vUScughTFAYiMwjKhaTOw
dyD9oZaJSCSbNovSDBCzM4Tcg6CU6GQQDgfiIyCC35RuDfrSMJploDD8VWxJO45q
qjJM/6KZYVU5PY4Xa7oOC5RYUpoAo3zFoOsousqUwSevyif4dWHKbAU4ExOx9WlV
BZhLH2m2FYCrSKFBmBYltIraEeuTf4W676Z15dIH9QN2jdB9FEHKHJbUDljC0kls
O2UyRLXPhRJsxECQpocdIul2V6tYYMPi1C8rGZy8Gnft1omoLsl+z08a5lTf5pcK
pSivWw8tEaM77OvPf+vpcMDrnbUlM9pMxfGCT1K+ZLPaXPvVWzpK/hJiD++yYDh9
rC4JakmF0wsBbHXsjAekn2Auo11WNaY+uVkrPnIiuPVOr+C504AGi6psyymsV2lX
FzxzpcPG0muhp7YwPFBHZRIEKgxBvb4V5Blx7MhVsJJFIvF+NqbjtSXj52c26tuN
48azSVjNAm1mjFRGpehlUl5VJYZqxlhrgMFAPlql+/XQ9tfZIKa9Vf3DEzZGQAEx
ZE/7TKiOcKhmciRj6T+/9rEJELVJIvB6JRJQ+cf5SMdIp08VfxYhKpulBR2gm1wo

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

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 11:37:51 +
with message-id 
and subject line Bug#1002884: fixed in titantools 4.0.11+notdfsg1-7
has caused the Debian Bug report #1002884,
regarding titantools: 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.)


-- 
1002884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: titantools
Version: 4.0.11+notdfsg1-6
Severity: serious
Tags: sid bookworm
User: nthyk...@master.debian.org
Usertags: compat-5-6-removal

Hi,

The package titantools uses debhelper with a compat level of 5 or 6,
which is no longer supported [1].

Please bump the debhelper compat at your earliest convenience

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

  * Compat 7 is the bare minimum


Thanks,
Andreas

[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html
--- End Message ---
--- Begin Message ---
Source: titantools
Source-Version: 4.0.11+notdfsg1-7
Done: Javier Fernández-Sanguino Peña 

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

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

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

Debian distribution maintenance software
pp.
Javier Fernández-Sanguino Peña  (supplier of updated 
titantools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 27 Mar 2022 20:14:22 +0200
Source: titantools
Architecture: source
Version: 4.0.11+notdfsg1-7
Distribution: unstable
Urgency: medium
Maintainer: Javier Fernandez-Sanguino Peña 
Changed-By: Javier Fernández-Sanguino Peña 
Closes: 1002884
Changes:
 titantools (4.0.11+notdfsg1-7) unstable; urgency=medium
 .
   * Move to Debhelper compatibility version 13 (Closes: #1002884)
   * debian/control:
 - Updated Standards version (no changes required)
 - Add debhelper-compat = 13, remove debian/comat
   * debian/source/format - add and declare the format in use (1.0)
Checksums-Sha1:
 df3576e371d39bac197d1de0ac505f5e7cb10f72 1932 titantools_4.0.11+notdfsg1-7.dsc
 d88c58818a50f7cb69160d9c4a033bd45f007231 9404 
titantools_4.0.11+notdfsg1-7.diff.gz
 87961f6a1e32470ee094d5bcf2e87aad086bc62e 7442 
titantools_4.0.11+notdfsg1-7_i386.buildinfo
Checksums-Sha256:
 fa154dd259c8dec9d3058d547794533d7e5cef3581874a42a17dc6db6e88aeae 1932 
titantools_4.0.11+notdfsg1-7.dsc
 40cae53054883667a0e0352212bc4b2fe6a765fec0c72cf940b534530e6bc5e0 9404 
titantools_4.0.11+notdfsg1-7.diff.gz
 b3cf101bf203b721e8b5494b2882f99087abe46245857e311e1a9f0bf0ef39af 7442 
titantools_4.0.11+notdfsg1-7_i386.buildinfo
Files:
 e0532fe627f87bf543dc66695be5c8e2 1932 non-free/admin optional 
titantools_4.0.11+notdfsg1-7.dsc
 f4a48920d345b434e9ad90843ffadb1c 9404 non-free/admin optional 
titantools_4.0.11+notdfsg1-7.diff.gz
 b4834c7b9c2a1f4d40af6030c1520743 7442 non-free/admin optional 
titantools_4.0.11+notdfsg1-7_i386.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEFQ8Kq6ttIR3DT+AOix9vSKslf5gFAmJEO4cACgkQix9vSKsl
f5gdUA//aIHIbN3EhI6JHgKOoKok8E+DMBheMeSukW6IJ78cV8r+mij/xRrhg5c5
MrmQnQR4XD9l6icmBtBtKhGI3pRJkmKLS2Pf+LPuXE7McTGaIhHfZ2HT8T224sYl
LbPpOCpuT7Kcl6PGduV814gml6wsSuUJyZevqqLSLln+xWPiLk+0II8q7VXogoY1
HXfZSzOTmR1aQU5HhCZ58wzh8O7rJxcAI6kIzuUQXEM0V9zyBcaKDQcPpTt8p6d/
tk2He8C3jpEjJOp6XiHLOWTepBJKLriqCsnWz5UjjHFhz3Qm8xenl7uAtvnACEDI
/eS2vOBzzowZb/LHDdk2hYTSKYY3RBrHfm3c2JKMB4a9Hteop3moeBQP8kQxnCC7
3KoBq0N48WrCkgXp3f7qA2DPl7fbvJIG5hPwMfYGc2RMDfKLAoswOYIxFm/qgrVx
DKFVIAv16sPNHNC2TCMAvA2mWaU4tsVXzu0kBw5D7kvfSrr+6CRf5T9AIPStzQ58
HQSqoc6voUPlcbvPccKN9o4+FZK5v6F3Rcj1TMHoy3YOaM4ESX1SCGjuyOyBwZCy
+S0LEzoh7AmCQXTnzdzgV6oIYfD8r3cfjd/PfiX9F68a0A+IKlJb+gWTaRdqfDD0
pgnEk2XWUIauMM681kX2ZGrXbTX3dRPaKZlLX4jFc7HuaE6kZp0=
=5bDA
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 11:19:19 +
with message-id 
and subject line Bug#1008550: fixed in gnome-shell-extension-hide-activities 
42-1
has caused the Debian Bug report #1008550,
regarding gnome-shell-extension-hide-activities: 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.)


-- 
1008550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-hide-activities
Version: 41-1
Severity: normal
Tags: bookworm sid fixed-upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-42
Forwarded: https://github.com/zeten30/HideActivities/pull/5

The metadata.json for this extension doesn't declare compatibility with
GNOME 42. According to the upstream pull request, no actual code changes
are necessary (I haven't tested it myself).

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

To keep better track of which extensions have and haven't been updated for
each new GNOME version, it would be useful if this extension had a
dependency of the form

gnome-shell (>= x), gnome-shell (<< y)

where x is the oldest version in metadata.json, and y is the next major
version after the newest version in metadata.json (at the moment y = 43).
See g-s-e-caffeine for an example of this setup.

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-hide-activities
Source-Version: 42-1
Done: Jonathan Carter 

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-hide-activities, 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.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-hide-activities 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 12:57:14 +0200
Source: gnome-shell-extension-hide-activities
Architecture: source
Version: 42-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Jonathan Carter 
Closes: 1008550
Changes:
 gnome-shell-extension-hide-activities (42-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1008550)
Checksums-Sha1:
 f24b16834fdc3537b236aa7f8ce260f12de1adc0 2188 
gnome-shell-extension-hide-activities_42-1.dsc
 f5237e2d5965552434541f9976707d672013c1da 2005 
gnome-shell-extension-hide-activities_42.orig.tar.gz
 808e35ddfb1c14ac9c49d6597c28ead9df8fe391 2008 
gnome-shell-extension-hide-activities_42-1.debian.tar.xz
 f633d91a40b18497a45d0b09f0c4cffa0b2e9e61 5908 
gnome-shell-extension-hide-activities_42-1_source.buildinfo
Checksums-Sha256:
 dcffeb41a48feceeb747a0913b7f1be9abdabc2b896debab4d7263d4ad1800cc 2188 
gnome-shell-extension-hide-activities_42-1.dsc
 9603c3fcc45e8940a9b646fd0e9998bd14d76af47f369f0cd4ffa16bf3bdd1af 2005 
gnome-shell-extension-hide-activities_42.orig.tar.gz
 0f9319874a9e50d9152b9c32b603e14b8d00c7e912863c847ca246c5fa3e491f 2008 
gnome-shell-extension-hide-activities_42-1.debian.tar.xz
 d56e39dbf491a832058fa68c2d5e22931991f6b7d0ad9aca2d5a8d372ef94628 5908 
gnome-shell-extension-hide-activities_42-1_source.buildinfo
Files:
 6ae087ae221300d760becc002beabc3b 2188 gnome optional 
gnome-shell-extension-hide-activities_42-1.dsc
 ab2a1b53a94c18f9ad8d7ba1f176b225 2005 gnome optional 
gnome-shell-extension-hide-activities_42.orig.tar.gz
 83ad528ab50651119cf37a4d9bfbc24b 2008 gnome optional 
gnome-shell-extension-hide-activities_42-1.debian.tar.xz
 14daf86115c56de51aabc2ebd413fe36 5908 gnome optional 
gnome-shell-extension-hide-activities_42-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmJEN9wPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmhe7MQAL6acTLvWFXMfH6ycGgg1tv++/OVyHHIVAEe
OpLmF67pY7uK1r6j63LpZn/4HqLbjlB2K8ncDmP+STubc9tty0YA4AgvmOyk89po
ij/bWJuNk3x26/J9aa7CrIB6KjL8DCYA8XwjAcSB1W3pIc2D7DFpgFV+G7DC26m4

Bug#1008357: marked as done (squeekboard: FTBFS: ninja: build stopped: subcommand failed.)

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 11:07:21 +
with message-id 
and subject line Bug#1008357: fixed in squeekboard 1.17.0-2
has caused the Debian Bug report #1008357,
regarding squeekboard: FTBFS: ninja: build stopped: subcommand failed.
to be marked as done.

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

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


-- 
1008357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squeekboard
Version: 1.17.0-1
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):
> make[2]: Entering directory '/<>'
> dh_auto_configure -- -Dnewer=true
>   cd _build && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload 
> --buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var 
> --libdir=lib/x86_64-linux-gnu -Dnewer=true
> The Meson build system
> Version: 0.62.0
> Source dir: /<>
> Build dir: /<>/_build
> Build type: native build
> Project name: squeekboard
> Project version: 1.17.0
> C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-19) 
> 11.2.0")
> C linker for the host machine: cc ld.bfd 2.38
> Rust compiler for the host machine: rustc -C linker=cc (rustc 1.57.0)
> Rust linker for the host machine: rustc -C linker=cc ld.bfd 2.38
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> ../meson.build:48: WARNING: Consider using the built-in werror option instead 
> of using "-Werror".
> Message: 
> --
> squeekboard 1.17.0
> 
> --
> 
> Configuring Cargo.toml.base using configuration
> Program cat found: YES (/bin/cat)
> Program cargo found: YES (/usr/bin/cargo)
> Program cargo.sh found: YES (/<>/cargo.sh)
> Program cargo_build.py found: YES (/usr/bin/python3 
> /<>/cargo_build.py)
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Program glib-compile-resources found: YES (/usr/bin/glib-compile-resources)
> Configuring sm.puri.Squeekboard.desktop.in using configuration
> Program msgfmt found: YES (/usr/bin/msgfmt)
> Program msginit found: YES (/usr/bin/msginit)
> Program msgmerge found: YES (/usr/bin/msgmerge)
> Program xgettext found: YES (/usr/bin/xgettext)
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency wayland-protocols found: YES 1.25
> Program wayland-scanner found: YES (/usr/bin/wayland-scanner)
> Program gdbus-codegen found: YES (/usr/bin/gdbus-codegen)
> Configuring config.h using configuration
> Run-time dependency gio-2.0 found: YES 2.72.0
> Run-time dependency gio-unix-2.0 found: YES 2.72.0
> Run-time dependency gnome-desktop-3.0 found: YES 42.0
> Run-time dependency gtk+-3.0 found: YES 3.24.33
> Run-time dependency libfeedback-0.0 found: YES 0.0.0
> Run-time dependency wayland-client found: YES 1.20.0
> Run-time dependency xkbcommon found: YES 1.4.0
> Library m found: YES
> Library rt found: YES
> Library dl found: YES
> Library pthread found: YES
> Build targets in project: 27
> NOTICE: Future-deprecated features used:
>  * 0.56.0: {'dependency.get_pkgconfig_variable', 'meson.source_root', 
> 'meson.build_root'}
> 
> squeekboard 1.17.0
> 
>   User defined options
> buildtype: plain
> libdir   : lib/x86_64-linux-gnu
> localstatedir: /var
> prefix   : /usr
> sysconfdir   : /etc
> wrap_mode: nodownload
> newer: true
> 
> Found ninja-1.10.1 at /usr/bin/ninja
> make[2]: Leaving directory '/<>'
>dh_auto_build -a -O--builddirectory=_build -O--buildsystem=meson
>   cd _build && LC_ALL=C.UTF-8 ninja -j8 -v
> [1/71] /usr/bin/glib-compile-resources ../data/squeekboard.gresources.xml 
> --sourcedir ../data --c-name squeekboard --internal --generate --target 
> data/squeekboard-resources.h
> xml-stripblanks preprocessing requested, but XMLLINT is not set, and xmllint 
> is not in PATH
> [2/71] /usr/bin/msgfmt ../po/ca.po -o po/ca/LC_MESSAGES/squeekboard.mo
> [3/71] /usr/bin/msgfmt ../po/de.po -o po/de/LC_MESSAGES/squeekboard.mo
> [4/71] /usr/bin/msgfmt ../po/fa.po -o po/fa/LC_MESSAGES/squeekboard.mo
> [5/71] /usr/bin/glib-compile-resources ../data/squeekboard.gresources.xml 
> --sourcedir ../data --c-name squeekboard --internal --generate --target 
> data/squeekboard-resources.c --dependency-file data/squeekboard-resources.c.d
> xml-stripblanks preprocessing requested, but XMLLINT is not set, and xmllint 
> is not in PATH
> [6/71] /usr/bin/msgfmt ../po/fi.po -o po/fi/LC_MESSAGES/squeekboard.mo
> [7/71] /usr/bin/msgfmt ../po/fur.po -o 

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

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 11:04:10 +
with message-id 
and subject line Bug#1008554: fixed in gnome-shell-extension-pixelsaver 1.28-2
has caused the Debian Bug report #1008554,
regarding gnome-shell-extension-pixelsaver: 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.)


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

The metadata.json for this extension declares compatibility with
GNOME 42, but in debian/control it still Depends: gnome-shell (<< 42).

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-pixelsaver
Source-Version: 1.28-2
Done: Jonathan Carter 

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-pixelsaver, 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.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-pixelsaver 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 12:40:15 +0200
Source: gnome-shell-extension-pixelsaver
Architecture: source
Version: 1.28-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jonathan Carter 
Closes: 1008554
Changes:
 gnome-shell-extension-pixelsaver (1.28-2) unstable; urgency=medium
 .
   * Update dependencies to be inclusive of gnome-shell 42 (Closes: #1008554 )
Checksums-Sha1:
 221a52c9838f61873a5e661ac62de62e7afc09a2 2231 
gnome-shell-extension-pixelsaver_1.28-2.dsc
 a6bf03f6a8d35a1d8cba53872430e33f2568fd69 143740 
gnome-shell-extension-pixelsaver_1.28.orig.tar.xz
 b723a137e2caa87e653720449987640c37913f49 9848 
gnome-shell-extension-pixelsaver_1.28-2.debian.tar.xz
 945c4a3c1e77a1bb596e086c4f9423d55d7de7ff 5879 
gnome-shell-extension-pixelsaver_1.28-2_source.buildinfo
Checksums-Sha256:
 a58c08c2ecc30ff8d8a1ddf205f9fd2b394f6b29456d6f5fbded56823f68ab65 2231 
gnome-shell-extension-pixelsaver_1.28-2.dsc
 8507e22e08c12e572135038b407d94c19efffa1f2ecc691bd63e1780ca0f37d7 143740 
gnome-shell-extension-pixelsaver_1.28.orig.tar.xz
 38f7c4df2efb0be8fcc4eb22eb666ba05c2004930124db6aba457a8f8db97874 9848 
gnome-shell-extension-pixelsaver_1.28-2.debian.tar.xz
 fd707bafa490b1a2312b87d744bfc3b6637102e4e5ec4a7e225d5e59e47a4154 5879 
gnome-shell-extension-pixelsaver_1.28-2_source.buildinfo
Files:
 d0a3fa41b0e0e27069c1422f2c9c9fd0 2231 gnome optional 
gnome-shell-extension-pixelsaver_1.28-2.dsc
 1e3c044c924b1284274eadeb113531d9 143740 gnome optional 
gnome-shell-extension-pixelsaver_1.28.orig.tar.xz
 3bcee82633e237884ed5053d5afdb567 9848 gnome optional 
gnome-shell-extension-pixelsaver_1.28-2.debian.tar.xz
 6ec09f66477f244d60509fa208ab7f4c 5879 gnome optional 
gnome-shell-extension-pixelsaver_1.28-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmJEM8YPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmhXU8P/ib1tHhDoRXz+oX8zCI/Oz13pCgDTbjip94v
FTFdBV0oUh7ekiVjqPpjngv/pc/tmTFX0nrfIV4LEH8e8utpHrddc42QkzzTU8YW
nfBGbZKnH/htF9ZdwCl4E9IRHoIQ0okVFXx6ZeBJXWh9VJYR7hl8dmwdEUupr7vd
1KWy5cWo/L7f/EgHn7y8OYBBpOdYqrKdUSSmDvjq3fxCxxAH1LSlkdYSMawe0IJ8
BqZDzOgVM13ch67jdbHZlEZWfh1gOPlusEr0gIy8q0hcLfmTcICsnlR8KeSvc2HH
1edWlOuMoeFaSqvGnadqMZjqI4krlPOrzPFplnDvF4PcgypkTo6aiR2tqnyg23+J
vnuWGsln36aqbK0+CQUoxi2gTAlQDfj1PpOGhdmu7lOy0IC+D4I+XmvBIpWyT5Gk
5uRn64DxFXM3jOMNpQzaTG/yhzfABzpy9sd66SMesy6yAgwwuq6BNAz0VfT6Kec7
KoLDykiEUQjXG/NIFDL7N69XBpNwyNsyg06pkAMrXZTJwuxTd7i5+xlTlj5ooJmb
FTcnfhBrhHjxneHtIRwEpxM5kHPMS4Nn+Fqx0QnD1l8H248IKoKwTMqJr51axGsb
OrJliNo4Bs9d7PkAYyTEPoz23aNH0wZsYAMgGKg1aQ1D1ai9h2+LS1UwoTDwUg3h
ToLNMh3p
=Fw/+
-END PGP 

Bug#1008670: librust-structopt+lints-dev uninstallable due to change in clap 2.34

[peter green]

Package: librust-structopt+lints-dev
Version: 0.3.26-1
Severity: serious

clap 2.34 dropped the "lints" feature, this has left librust-structopt+lints-dev
uninstallable in unstable and is blocking the migration to testing of the new
versions of clap and textwrap.

Since rust-structopt+lints-dev has no reverse dependencies I would propose 
simply
dropping it. Any objections?

Bug#1008669: libsbml FTBFS with Python 3.10

[Adrian Bunk]

Source: libsbml
Version: 5.19.0+dfsg-1
Severity: serious
Tags: ftbfs bookworm sid

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

...
[ 99%] Swig Python source
Traceback (most recent call last):
  File "/<>/src/bindings/python/doc-converter/rewrite_pydoc.py", 
line 121, in 
from formatter import NullWriter, AbstractFormatter
ModuleNotFoundError: No module named 'formatter'
make[4]: *** 
[src/bindings/python/CMakeFiles/binding_python_swig.dir/build.make:633: 
src/bindings/python/libsbml_wrap.cpp] Error 1


The Ubuntu patch seems to contain a fix.

Bug#1008665: marked as pending in node-react-popper

[Yadd]

Control: tag -1 pending

Hello,

Bug #1008665 in node-react-popper 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-react-popper/-/commit/acfcc683f390c03a6af40269f582ea913caa8c29


Build needed files

Closes: #1008665


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008665

Processed: Bug#1008665 marked as pending in node-react-popper

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008665 [node-react-popper] node-react-popper: Package unusable due to 
missing build
Added tag(s) pending.

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

Bug#1008666: node-popper2: Package unusable due to missing build

[Yadd]

Package: node-popper2
Version: 2.11.2-1
Severity: grave
Justification: renders package unusable

Another package pushed without building needed files...

$ dpkg -L node-popper2
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/node-popper2
/usr/share/doc/node-popper2/README.md.gz
/usr/share/doc/node-popper2/changelog.Debian.gz
/usr/share/doc/node-popper2/copyright
/usr/share/nodejs
/usr/share/nodejs/@popperjs
/usr/share/nodejs/@popperjs/core
/usr/share/nodejs/@popperjs/core/index.d.ts
/usr/share/nodejs/@popperjs/core/package.json

Bug#1008357: marked as pending in squeekboard

[Arnaud Ferraris]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/DebianOnMobile-team/squeekboard/-/commit/d9e01226476122b043ac1c6e193cf1ae324775fa


d/patches: fix build failure due to newer crate version

Crate `clap` has been upgraded to 2.34 in Debian, so make sure this
package still builds fine.

Closes: #1008357


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008357

Processed: Bug#1008357 marked as pending in squeekboard

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008357 [src:squeekboard] squeekboard: FTBFS: ninja: build stopped: 
subcommand failed.
Added tag(s) pending.

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

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 1007234 test suite fails on all but amd64 arches
Bug #1007234 [src:netpbm-free] netpbm-free: FTBFS almost everywhere
Changed Bug title to 'test suite fails on all but amd64 arches' from 
'netpbm-free: FTBFS almost everywhere'.
> severity 1007234 important
Bug #1007234 [src:netpbm-free] test suite fails on all but amd64 arches
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Bug#1008665: node-react-popper: Package unusable due to missing build

[Yadd]

Package: node-react-popper
Severity: grave
Justification: renders package unusable

This package was pushed without any care. Needed files aren't build
which render package unusable (as reported by autopkgtest!)

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

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 10:19:37 +
with message-id 
and subject line Bug#1008536: fixed in gnome-shell-extension-arc-menu 
49+forkv29-1
has caused the Debian Bug report #1008536,
regarding gnome-shell-extension-arc-menu: 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.)


-- 
1008536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-arc-menu
Version: 49+forkv20-1
Severity: normal
Tags: bookworm sid
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. 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 42 is in experimental and will be entering unstable soon,
at which point this will become a RC bug.

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.

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-arc-menu
Source-Version: 49+forkv29-1
Done: Jonathan Carter 

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-arc-menu, 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.
Jonathan Carter  (supplier of updated 
gnome-shell-extension-arc-menu 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 11:52:48 +0200
Source: gnome-shell-extension-arc-menu
Architecture: source
Version: 49+forkv29-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan 
Changed-By: Jonathan Carter 
Closes: 1008536
Changes:
 gnome-shell-extension-arc-menu (49+forkv29-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1008536)
   * Bump required gnome-shell version to 42
Checksums-Sha1:
 f536bc2804b3a0e14a66336f2c4d1865d98debe0 2203 
gnome-shell-extension-arc-menu_49+forkv29-1.dsc
 5994912379b97519b9d37070f172c8e66b3934d6 668093 
gnome-shell-extension-arc-menu_49+forkv29.orig.tar.gz
 70c262065fc7f8f056ffcf3448a40daabbd3bfc7 2448 
gnome-shell-extension-arc-menu_49+forkv29-1.debian.tar.xz
 93945ddcf84b2c60fdd42fba1e94820b4530bbb8 5664 
gnome-shell-extension-arc-menu_49+forkv29-1_source.buildinfo
Checksums-Sha256:
 39625804d7ed0b372f9d1ac1f1ae52c109c07a06c8e16cf42147bb1497c09100 2203 
gnome-shell-extension-arc-menu_49+forkv29-1.dsc
 2ed95cb7b58f4cc29db7bf1bd37cf6cfd7f805d9c3b8d9d354b85b3b53575b8d 668093 
gnome-shell-extension-arc-menu_49+forkv29.orig.tar.gz
 37a3344b6bb92b6f2c09df72b6ab77f9bd1f7a86a37fa8bb8f0f3549237963c6 2448 
gnome-shell-extension-arc-menu_49+forkv29-1.debian.tar.xz
 3e9d7ebe0f71f89d7afbb3096b4b7f1eadee6f1e8c5e38b8ece44859e3accc3d 5664 
gnome-shell-extension-arc-menu_49+forkv29-1_source.buildinfo
Files:
 d752ab5dd187205edc2c8ea88f4e8844 2203 gnome optional 
gnome-shell-extension-arc-menu_49+forkv29-1.dsc
 8daf854b9cdfb65a672c0913fde5c5b2 668093 gnome optional 
gnome-shell-extension-arc-menu_49+forkv29.orig.tar.gz
 f0fa43ed27db85ffaf7440e771a749d8 2448 gnome optional 
gnome-shell-extension-arc-menu_49+forkv29-1.debian.tar.xz
 a7d1914ef27d9bbe50934dd5442fa945 5664 gnome optional 
gnome-shell-extension-arc-menu_49+forkv29-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAmJEKPYPHGpjY0BkZWJp

Bug#965434: barada-pam: diff for NMU version 0.5-3.2

[Guilherme de Paula Xavier Segundo]

Control: tags 965434 + patch
Control: tags 965434 + pending

Dear maintainer,

I've prepared an NMU for barada-pam (versioned as 0.5-3.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru barada-pam-0.5/debian/changelog barada-pam-0.5/debian/changelog
--- barada-pam-0.5/debian/changelog	2012-05-31 14:55:25.0 -0300
+++ barada-pam-0.5/debian/changelog	2022-03-29 14:08:27.0 -0300
@@ -1,3 +1,14 @@
+barada-pam (0.5-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Using new DH level format. Consequently:
+  - debian/compat: removed.
+  - debian/control: changed from 'debhelper' to 'debhelper-compat' in
+Build-Depends field and bumped level to 13.
+  - Closes: #965434
+
+ -- Guilherme de Paula Xavier Segundo   Tue, 29 Mar 2022 14:08:27 -0300
+
 barada-pam (0.5-3.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru barada-pam-0.5/debian/compat barada-pam-0.5/debian/compat
--- barada-pam-0.5/debian/compat	2012-05-31 14:42:44.0 -0300
+++ barada-pam-0.5/debian/compat	1969-12-31 21:00:00.0 -0300
@@ -1 +0,0 @@
-5
diff -Nru barada-pam-0.5/debian/control barada-pam-0.5/debian/control
--- barada-pam-0.5/debian/control	2012-05-31 14:42:44.0 -0300
+++ barada-pam-0.5/debian/control	2022-03-29 14:07:31.0 -0300
@@ -1,7 +1,7 @@
 Source: barada-pam
 Priority: extra
 Maintainer: Andrew Pollock 
-Build-Depends: debhelper (>= 6.0.7~), autotools-dev, libboost-serialization-dev, libpam-dev, libssl-dev, libboost-filesystem-dev
+Build-Depends: debhelper-compat (= 13), autotools-dev, libboost-serialization-dev, libpam-dev, libssl-dev, libboost-filesystem-dev
 Standards-Version: 3.9.2
 Section: libs
 Homepage: http://barada.sourceforge.net/

Processed: barada-pam: diff for NMU version 0.5-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 965434 + patch
Bug #965434 [src:barada-pam] barada-pam: Removal of obsolete debhelper compat 5 
and 6 in bookworm
Added tag(s) patch.
> tags 965434 + pending
Bug #965434 [src:barada-pam] barada-pam: Removal of obsolete debhelper compat 5 
and 6 in bookworm
Added tag(s) pending.

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

Bug#1008654: nvidia-modprobe version in bullseye-backports behind the stable update version

[René Krell]

Package: nvidia-modprobe
Version: 470.94-1~bpo11+1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Using bullyeye-backports - the version of the package
 470.94-1~bpo11+1
is behind the version of the table update repository
 470.103.01-1~deb11u1.

This leads to an inconsistency in teh installed packages when installing the 
nvidia driver from bullseye-backports.

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

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

Versions of packages nvidia-modprobe depends on:
ii  libc6  2.31-13+deb11u3

nvidia-modprobe recommends no packages.

nvidia-modprobe suggests no packages.

-- no debconf information

Bug#1005636: marked as done (python-tooz: FTBFS: TypeError: retry..() got an unexpected keyword argument 'retry_state')

[Debian Bug Tracking System]

Your message dated Wed, 30 Mar 2022 09:13:34 +0200
with message-id <001f6af1-779b-6918-bab9-c5cca7bfd...@debian.org>
and subject line This is fixed
has caused the Debian Bug report #1005636,
regarding python-tooz: FTBFS: TypeError: retry..() got an 
unexpected keyword argument 'retry_state'
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> for i in 3.10 3.9 ; do \
>   python3 setup.py install -f --install-layout=deb 
> --root=/<>/debian/tmp ; \
> done
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'python-requires' will not be supported in future versions. 
> Please use the underscore name 'python_requires' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:158: 
> EasyInstallDeprecationWarning: easy_install command is deprecated. Use build 
> and pip and other standards-based tools.
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/command/install.py:34: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and 
> pip and other standards-based tools.
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'author-email' will not be supported in future versions. 
> Please use the underscore name 'author_email' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'description-file' will not be supported in future versions. 
> Please use the underscore name 'description_file' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'home-page' will not be supported in future versions. Please 
> use the underscore name 'home_page' instead
>   warnings.warn(
> /usr/lib/python3/dist-packages/setuptools/dist.py:723: UserWarning: Usage of 
> dash-separated 'python-requires' will not be supported in future versions. 
> Please use the underscore name 'python_requires' instead
>   warnings.warn(
> running install
> [pbr] Generating AUTHORS
> [pbr] AUTHORS complete (0.0s)
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/tooz
> creating build/lib/tooz/tests
> copying tooz/tests/__init__.py -> build/lib/tooz/tests
> copying tooz/tests/test_etcd.py -> build/lib/tooz/tests
> copying tooz/tests/test_memcache.py -> build/lib/tooz/tests
> copying tooz/tests/test_mysql.py -> build/lib/tooz/tests
> copying tooz/tests/test_coordination.py -> build/lib/tooz/tests
> copying tooz/tests/test_utils.py -> build/lib/tooz/tests
> copying tooz/tests/test_postgresql.py -> build/lib/tooz/tests
> copying tooz/tests/test_hashring.py -> build/lib/tooz/tests
> copying tooz/tests/test_partitioner.py -> build/lib/tooz/tests
> creating build/lib/tooz/tests/drivers
> copying tooz/tests/drivers/__init__.py -> build/lib/tooz/tests/drivers
> copying tooz/tests/drivers/test_etcd3.py -> build/lib/tooz/tests/drivers
> copying tooz/tests/drivers/test_etcd3gw.py -> build/lib/tooz/tests/drivers
> copying tooz/tests/drivers/test_file.py -> build/lib/tooz/tests/drivers
> creating build/lib/tooz/drivers
> copying tooz/drivers/__init__.py -> build/lib/tooz/drivers
> copying tooz/drivers/zake.py -> build/lib/tooz/drivers
> copying 

Processed: severity of 1008497 is important

[Debian Bug Tracking System]

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

> severity 1008497 important
Bug #1008497 [src:linux] linux-image-5.10.0-13-arm64: 5.10.0-13-arm64 gets 
stuck after loading ramdisk on VMWareFusion under M1. 5.10.0-12-arm64 works.
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Processed: fixed 1005636 2.10.1-1

[Debian Bug Tracking System]

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

> fixed 1005636 2.10.1-1
Bug #1005636 [src:python-tooz] python-tooz: FTBFS: TypeError: 
retry..() got an unexpected keyword argument 'retry_state'
Marked as fixed in versions python-tooz/2.10.1-1.
>
End of message, stopping processing here.

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

Bug#1008650: python3-unbound: Cannot install because of Python dependencies

[Stephane Bortzmeyer]

Package: python3-unbound
Version: 1.13.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

% sudo apt install python3-unbound
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3-unbound : Depends: python3 (< 3.10) but 3.10.4-1 is to be installed
E: Unable to correct problems, you have held broken packages.

Indeed, Python version on sid is:

% python3 --version
Python 3.10.4

But:

% apt-cache show python3-unbound
Package: python3-unbound
Source: unbound
Version: 1.13.1-1
Installed-Size: 394
Maintainer: unbound packagers 
Architecture: armhf
Depends: python3 (<< 3.10), python3 (>= 3.9~), python3:any, libc6 (>= 2.28), 
libunbound8 (>= 1.9.0)
...

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: armhf (armv7l)

Kernel: Linux 4.14.269 (SMP w/2 CPU threads)
Locale: LANG=C, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-unbound depends on:
ii  libc62.33-7
ii  libunbound8  1.13.1-1
ii  python3  3.10.4-1

python3-unbound recommends no packages.

python3-unbound suggests no packages.

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