Bug#990634: thunar: Crashes displaying thumbnail of SSH remote images

[Akbarkhon Variskhanov]

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

Thanks for reporting. However, it would be great if you could get a backtrace.

Bug#1024868: src:rust-kvm-bindings: fails to migrate to testing for too long: FTBFS on i386

[Paul Gevers]

Source: rust-kvm-bindings
Version: 0.1.1-1
Severity: serious
Control: close -1 0.5.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1021316

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:rust-kvm-bindings has been trying to 
migrate for 61 days [2]. Hence, I am filing this bug. Your package 
failed to build from source on i386, which was reported in bug 1021316.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#933683: [Bug 1972833] Re: Merge cacti from Debian unstable for kinetic

[Paul Gevers]

Hi,

On 27-11-2022 00:46, Athos Ribeiro wrote:

Maria DB does not seem to support 'sha256_password' [1]. Still, MySQL
default seems to use sha2 instead of sha1. It seems that removing the
line changing the auth method would be enough to support both DBs. Would
that be enough for us to merge the changes?


I haven't checked recently, but I guess yes.


If so, I can rebase the
latest Rafael's changes and prepare a MR in salsa.


I think it would be good for the Debian/Ubuntu ecosystem to reduce the 
diff between the two, so I'd be in favor of being in sync.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006500: Missing bnx2x firmware 7.13.21.0 renders NIC unusable with Linux 5.16

[Shane St. Savage]

As someone who has bricked multiple servers and weekends trying to work
around this in an iPXE/preseed installer environment, I would also be very
appreciative of a backport release of 20220913-1~deb11u1 (assuming enough
settlement time has passed). Thanks for all your work on Debian!

Bug#1020576: please update sage for pari 2.15.0 and gap 4.12.0

[Nilesh Patra]

Hi Tobias and Bill,

On Wed, 19 Oct 2022 01:05:44 +0200 Bill Allombert  wrote:
> On Mon, Oct 17, 2022 at 08:44:52AM +, Tobias Hansen wrote:
> > Control: block -1 by 1020436 1020456
> > 
> > Before sagemath can be fixed, cypari2 and giac have to be built against 
> > pari 2.15.

There's a new release of cypari2 2.1.3 which has fixes for both, tests with 
pari 2.15 and
also python3.11 fix (Bug#1024064) atleast as per commit messages (the current 
version of
cypari2 is compatible w/ pari2.15 anyway tho)

> OK, is there someone taking care of giac ?

giac has already been uploaded/taken care of[1], and it has built with pari 2.15

Tobias, since this is done, would you consider to check sagemath now and get 
the ball rolling? :-)

[1]: 
https://tracker.debian.org/news/1388406/accepted-giac-19029dfsg2-1-source-into-unstable/

-- 
Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1024867: mercurial: FTBFS on riscv64 (test timeout)

[Eric Long]

Source: mercurial
Version: 6.2.3-1
Severity: important
Tags: ftbfs patch
Justification: fails to build from source (but built successfully in the past)
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: i...@hack3r.moe, debian-ri...@lists.debian.org

Dear maintainer(s),

Some tests time out on riscv64 as seen in buildd log:

```
Failed test-copies-chain-merge.t#pull: timed out
Failed test-copies-chain-merge.t#pull-upgrade: timed out
Failed test-copies-chain-merge.t#push: timed out
Failed test-copies-chain-merge.t#push-upgrade: timed out
Failed test-copies-chain-merge.t#sidedata: timed out
Failed test-copies-chain-merge.t#upgraded: timed out
Failed test-copies-chain-merge.t#upgraded-parallel: timed out
# Ran 892 tests, 80 skipped, 7 failed.
python hash seed: 74757585
# Timout reached for process 2161206 
# Cleaning up HGTMP /tmp/hgtests.3yx9dxu8 
make[2]: *** [Makefile:140: tests] Error 1
```

Full log: 
https://buildd.debian.org/status/fetch.php?pkg=mercurial=riscv64=6.2.3-1=1668895854=0

These timeouts has existed for a long time (about a year), so maybe disable
them is a better idea for more consistent builds on riscv64. Alternatively, we
can increase test timeout further and hopefully let them finish in time.

I've included a patch to disable those tests in debian/rules. Please let me
know if more help is needed.

Cheers,
Eric
diff --git a/debian/mercurial.riscv64.test_blacklist 
b/debian/mercurial.riscv64.test_blacklist
new file mode 100644
index ..76c6c0c6
--- /dev/null
+++ b/debian/mercurial.riscv64.test_blacklist
@@ -0,0 +1,38 @@
+# test-clonebundles.t fails in the reproducible-builds setup due to no
+#  name resolution:
+# --- /build/mercurial-3.7.2/tests/test-clonebundles.t
+# +++ /build/mercurial-3.7.2/tests/test-clonebundles.t.err
+# @@ -52,7 +52,7 @@
+#$ echo 'http://does.not.exist/bundle.hg' > 
server/.hg/clonebundles.manifest
+#$ hg clone http://localhost:$HGPORT 404-url
+#applying clone bundle from http://does.not.exist/bundle.hg
+# -  error fetching bundle: (.* not known|getaddrinfo failed) (re)
+# +  error fetching bundle: Temporary failure in name resolution
+#abort: error applying bundle
+#(if this error persists, consider contacting the server operator or 
disable clone bundles via "--config ui.clonebundles=false")
+#[255]
+#
+# ERROR: test-clonebundles.t output changed
+test-clonebundles.t
+
+# upstream don't run this test and it only fails when pyflakes is installed
+test-check-pyflakes.t
+
+# https://bz.mercurial-scm.org/show_bug.cgi?id=6294
+test-debugcommands.t
+
+# These tests are flaky, still need to investigate why:
+test-commandserver.t
+test-largefiles.t
+
+# We don't ship the git extension yet
+test-git-interop.t
+
+# https://bz.mercurial-scm.org/show_bug.cgi?id=6643
+test-http-bad-server.t
+
+# https://bz.mercurial-scm.org/show_bug.cgi?id=3782
+test-convert-cvs-synthetic.t
+
+# test timeout on riscv64
+test-copies-chain-merge.t
diff --git a/debian/rules b/debian/rules
index 0715cc84..dc85e42c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -31,6 +31,13 @@ ARCH_IS_MIPS := $(if $(subst mips,,$(DEB_HOST_ARCH)),,T)
 ARCH_IS_KFREEBSD-i386 := $(if $(subst kfreebsd-i386,,$(DEB_HOST_ARCH)),,T)
 ARCH_IS_ARMEL := $(if $(subst armel,,$(DEB_HOST_ARCH)),,T)
 ARCH_IS_SPARC := $(if $(subst sparc,,$(DEB_HOST_ARCH)),,T)
+ARCH_IS_RISCV64 := $(if $(subst riscv64,,$(DEB_HOST_ARCH)),,T)
+
+ifneq ($(ARCH_IS_RISCV64),)
+   TEST_BLACKLIST_FILENAME := mercurial.riscv64.test_blacklist
+else
+   TEST_BLACKLIST_FILENAME := mercurial.test_blacklist
+endif
 
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
@@ -45,10 +52,10 @@ ifneq ($(or $(ARCH_IS_MIPS), $(ARCH_IS_KFREEBSD-i386), 
$(ARCH_IS_ARMEL), $(ARCH_
sed -i.deb-backup -e 's/sleep 1/sleep 2/' 
$(CURDIR)/tests/test-pull-pull-corruption.t
 endif
 
-   http_proxy='' dh_auto_test -- PYTHON=python3 TESTFLAGS="--verbose 
--timeout 1440 $(PARALLEL_TEST_JOBS) --blacklist 
$(CURDIR)/debian/mercurial.test_blacklist"
+   http_proxy='' dh_auto_test -- PYTHON=python3 TESTFLAGS="--verbose 
--timeout 1440 $(PARALLEL_TEST_JOBS) --blacklist 
$(CURDIR)/debian/$(TEST_BLACKLIST_FILENAME)"
file-rename 's/\.deb-backup$$//' $(CURDIR)/tests/*
# run blacklisted tests but ignore their results
-   -cd tests && python3 run-tests.py --verbose `grep ^test 
../debian/mercurial.test_blacklist`
+   -cd tests && python3 run-tests.py --verbose `grep ^test 
../debian/$(TEST_BLACKLIST_FILENAME)`
 endif
 
 override_dh_auto_install: $(PYVERS:%=install-python%)

Bug#1024852: nvidia-driver in bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) do not support Linux kernel 6.0 or later

[Michael Tokarev]

On Sat, 26 Nov 2022 12:43:12 -0800 Alex Relis  wrote:

Package: nvidia-driver
Version: 470.103.01-1~bpo11+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

About a week ago, linux-image-6.0.0-0.deb11.2-amd64 was introduced in 
bullseye-backports. The problem is that the nvidia-driver version in both 
bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) 
(for some reason, the version in bullseye is newer which is strange) DO NOT 
support Linux kernel 6.0.
When a user who uses a backported linux kernel and nvidia-driver upgrades their 
system, they will get an error message that looks like this 
https://imgur.com/sEVx1vc (sorry if I couldn't give you the text output; I am 
reporting this on behalf of a friend)

This issue is reproducable and happened on two of my friends' machines. We found a current 
workaround that involves booting to kernel 5.1x in the Grub menu, running sudo apt purge 
linux-image-6.0.0-0.deb11.2-amd64 && sudo apt install -t bullseye-backports 
nvidia-driver && sudo reboot now.


So what is the proposal there?

Just do not install 6.0 kernel from backports if you need nvidia driver?


According to this Phoronix article ( 
https://www.phoronix.com/news/NVIDIA-515.76-Linux-Driver ), nvidia-driver 
515.76 or newer support Linux kernel 6.0. I believe the solution is to upgrade 
nvidia-driver to 515.76 or newer in bullseye-backports so that users can use 
their graphics card on kernel 6.0.


As you state yourself, this bug is already fixed in the more recent version
of the package.

Why are you
a) filing a bug which is already fixed in Debian, and
b) why are you filing it against the bpo version of the package?

It is like installing this version of driver breaks system.
(especially since apt will not install this version, since a more
recent version is available in bullseye already).

It is a very questionable bug report, and for me as a maintainer
(not of this package though) it discourages me from doing more
backports (just a personal opinion/feeling).

/mjt

Bug#1024866: vlock: special passphrase(s) that execute a kill-command

[Philippe Cerfon]

Package: vlock
Version: 2.2.2-11
Severity: wishlist


Hey.

It seems vlock has no longer any upstream?


It would be nice, when one could configure a special passphrase
(or maybe even more) which, when entered, doesn't unlock the
terminal, but instead executes a configurable command (depending
on which passphrase was entered).

Such command could then be used, to forcibly shutdown the machine
or remove any dm-crypt keys from memory.

Regards,
Philippe.


PS: Yes I know that a skilled attacker would rather perform e.g.
a cold boot attack, but still, might help in some cases.

Bug#1024865: grub-pc: enable minimal installation defaults

[Daniel Kahn Gillmor]

Package: grub-pc
Version: 2.06-3~deb11u4

Thanks for pulling in fixes to image and font handling for grub in
2.06-3~deb11u4 -- that additional security is much appreciated.

On many machines, i've been running grub through a serial console for
years, which doesn't exercise any of the image or font-handling code.

On some of those machines, grub lives in its own small (16MiB)
/boot/grub partition.  With the changes from the aforementioned
versions, grub itself (along with unicode.pf2) is significantly larger,
enough so that "dpkg-reconfigure grub-pc" fails with this error message:

```
Installing for i386-pc platform.
grub-install: error: cannot copy `/usr/share/grub/unicode.pf2' to 
`/boot/grub/fonts/unicode.pf2': No space left on device.
```

The failure comes from when the postinst script for grub-pc invokes
grub-install.

In practice, i can make the installation work with the rather janky
command:

grub-install /dev/Xda --fonts ''

(where Xda is the appropriate disk)

It ought to be possible for the grub postinst script to know that it's
being installed in a minimal configuration and omit installing
unicode.pf2.  for example, if /etc/default/grub contains
GRUB_TERMINAL=serial or GRUB_TERMINAL=console then it should be
acceptable to omit the font.

thanks for maintaining grub in debian!

   --dkg


signature.asc
Description: PGP signature

Bug#933683: [Bug 1972833] Re: Merge cacti from Debian unstable for kinetic

[Athos Ribeiro]

On Thu, 14 Jul 2022 17:01:12 +0200 Paul Gevers  wrote:

Hi,


Hi Paul,



On Thu, 12 May 2022 09:00:49 +0200 Paul Gevers  wrote:
> As Debian has MySQL 8+ for some time now, wouldn't it make sense to 
> merge this back into Debian now. Are these changes compatible with 
> MariaDB, and if not, what would it take to make them compatible?


I guess the required changes are not compatible with MariaDB? Can you 
confirm?


paul@mulciber ~/packages/cacti/cacti $ sudo mysql -e "create user 
'bla'@'localhost';"
paul@mulciber ~/packages/cacti/cacti $ sudo mysql -e "alter user 
'bla'@'localhost' identified with 'sha256_password';"
ERROR 1396 (HY000) at line 1: Operation ALTER USER failed for 
'bla'@'localhost'


Paul


Maria DB does not seem to support 'sha256_password' [1]. Still, MySQL
default seems to use sha2 instead of sha1. It seems that removing the
line changing the auth method would be enough to support both DBs. Would
that be enough for us to merge the changes? If so, I can rebase the
latest Rafael's changes and prepare a MR in salsa.

Sorry for the delay on replying on this one :)

[1] https://mariadb.com/kb/en/authentication-plugin-sha-256/
[2]  
https://dev.mysql.com/doc/refman/8.0/en/upgrading-from-previous-series.html#upgrade-caching-sha2-password

--
Athos Ribeiro

Bug#1024540: transition: libpinyin

[Gunnar Hjalmarsson]

On 2022-11-26 15:44, Sebastian Ramacher wrote:

On 2022-11-25 14:52:12 +0100, Gunnar Hjalmarsson wrote:

I notice that libpinyin has not yet migrated, even though the 2
days delay is over. Is that because Britney waits for the
dependencies to be migration ready too, or is it because this bug
is not closed yet?


It has not migrated yet because the shared library packages have
strictly versioned dependency on libpinyin-data. Hence, migrating
libpinyin to testing would currently render some packages
uninstallable in testing.


Thanks for the explanation. I see that you requested a higher urgency 
for maliit-keyboard, so they all show "will attempt migration" now.



Ideally, this dependency would be relaxed if possible so that this
won't be an issue for the next libpinyin transition. For this one,
all the reverse dependencies and libpinyin need to migrate together.


I'll pass that advice to others who are more familiar than me with the 
libpinyin packaging choices.


--
Cheers,

Gunnar Hjalmarsson

Bug#1024863: RFP: amdgpu-opencl -- Open-source OpenCL support for AMD GPUs

[Nick Jacobs]

Package: wnpp
X-Debbugs-Cc: halbtaxabo-...@yahoo.com
Severity: wishlist

* Package name    : amdgpu-open
  Version :
  Upstream Author : 
* URL : https://gpuopen.com
* License : MIT
  Programming Lang:
  Description : Open-source OpenCL support for AMD GPUs

There is a packaged graphics device driver for AMD Radeon graphics
cards, but there doesn't seem to be OpenCL support.
A typical use case would be using
the graphics card to speed up neural-network computation.
There is open-source software developed by AMD but it isn't
packaged.

Bug#1024862: ITP: goldendict-webengine -- feature-rich dictionary lookup program (qtwebengine fork)

[Boyuan Yang]

Package: wnpp
Severity: wishlist
Owner: Boyuan Yang 

* Package name: goldendict-webengine
  Version : 22.11.24-alpha.221124.ff5d82d7
  Upstream Author : Konstantin Isakov 
* URL : https://github.com/xiaoyifang/goldendict
* License : GPL-3.0-or-later
  Programming Lang: C++
  Description : feature-rich dictionary (qtwebengine fork)

 GoldenDict is a feature-rich dictionary lookup program, supporting multiple
 dictionary formats (StarDict/Babylon/Lingvo/Dictd/AARD/MDict/SDict)
 and online dictionaries, featuring perfect article rendering with the
 complete markup, illustrations and other content retained,
 and allowing you to type in words without any accents or correct case.
 .
 This is a forked version that uses QtWebEngine as rendering engine instead
 of QtWebKit.

Thanks,
Boyuan Yang


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

Bug#1024447: Also affects gfxmode

[Ralph Martin]

I'd just note that the bug is not just limited to producing odd 
characters round the border.


Failure to load the font also causes a block of config code to be 
omitted, in my case this is:


if loadfont $font ; then
  set gfxmode=1024x768
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_GB
  insmod gettext
fi

which has a more serious effect - the gfxmode is not set, and if you 
have a high resolution screen, the grub menu becomes too small to read.


Ralph Martin

Bug#1024861: contextlib2: (autopkgtest) needs update for python3.11: 'mycontext' object does not support the context manager protocol

[Paul Gevers]

Source: contextlib2
Version: 0.6.0.post1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
contextlib2 fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
contextlib2from testing0.6.0.post1-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/c/contextlib2/28706379/log.gz

==
ERROR: test_typo_enter 
(test_contextlib2.TestContextDecorator.test_typo_enter)

--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.rcsf_3a_/downtmp/autopkgtest_tmp/test_contextlib2.py", 
line 364, in test_typo_enter

with mycontext():
TypeError: 'mycontext' object does not support the context manager protocol

==
ERROR: test_typo_exit (test_contextlib2.TestContextDecorator.test_typo_exit)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.rcsf_3a_/downtmp/autopkgtest_tmp/test_contextlib2.py", 
line 376, in test_typo_exit

with mycontext():
TypeError: 'mycontext' object does not support the context manager 
protocol (missed __exit__ method)


--
Ran 72 tests in 0.022s

FAILED (errors=2)


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024860: circuits: (autopkgtest) needs update for python3.11: cannot import name 'getargspec' from 'inspect'

[Paul Gevers]

Source: circuits
Version: 3.1.0+ds1-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
circuits fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
circuits   from testing3.1.0+ds1-3
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/c/circuits/28706378/log.gz

Testing with python3.11:
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/circuits/__init__.py", line 22, 
in 

from .core import Event
  File "/usr/lib/python3/dist-packages/circuits/core/__init__.py", line 
12, in 

from .bridge import Bridge
  File "/usr/lib/python3/dist-packages/circuits/core/bridge.py", line 
23, in 

from .handlers import handler
  File "/usr/lib/python3/dist-packages/circuits/core/handlers.py", line 
9, in 

from inspect import getargspec
ImportError: cannot import name 'getargspec' from 'inspect' 
(/usr/lib/python3.11/inspect.py)

autopkgtest [14:13:56]: test autodep8-python3



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024859: cctbx: (autopkgtest) needs update for python3.11: initialization of scitbx_linalg_ext raised unreported exception

[Paul Gevers]

Source: cctbx
Version: 2022.9+ds2+~3.11.2+ds1-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
cctbx fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
cctbx  from testing2022.9+ds2+~3.11.2+ds1-4
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cctbx/28708326/log.gz

Testing cctbx with python3.11:
Discovering pytest tests for smtbx:
refinement/constraints/tests/test_disorder.py: 1
refinement/constraints/tests/test_occupancies.py: 1
refinement/constraints/tests/test_rigid.py: 9
refinement/constraints/tests/test_same_group.py: 2

 ERRORS 

___ ERROR collecting refinement/constraints/tests/test_direction.py 


/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:1206: in _gcd_import
???
:1178: in _find_and_load
???
:1128: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1206: in _gcd_import
???
:1178: in _find_and_load
???
:1128: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1206: in _gcd_import
???
:1178: in _find_and_load
???
:1128: in _find_and_load_unlocked
???
:241: in _call_with_frames_removed
???
:1206: in _gcd_import
???
:1178: in _find_and_load
???
:1149: in _find_and_load_unlocked
???
:690: in _load_unlocked
???
:940: in exec_module
???
:241: in _call_with_frames_removed
???
/usr/lib/python3/dist-packages/smtbx/refinement/__init__.py:2: in 
from cctbx import xray
/usr/lib/python3/dist-packages/cctbx/xray/__init__.py:4: in 
from cctbx.xray.scatterer import *
/usr/lib/python3/dist-packages/cctbx/xray/scatterer.py:3: in 
import cctbx.eltbx.xray_scattering
/usr/lib/python3/dist-packages/cctbx/eltbx/xray_scattering/__init__.py:2: 
in 

import scitbx.math.gaussian # base class for gaussian
/usr/lib/python3/dist-packages/scitbx/math/__init__.py:8: in 
import scitbx.linalg.eigensystem
/usr/lib/python3/dist-packages/scitbx/linalg/__init__.py:2: in 
from scitbx.linalg.ext import *
/usr/lib/python3/dist-packages/scitbx/linalg/ext.py:3: in 
bp.import_ext("scitbx_linalg_ext")
/usr/lib/python3/dist-packages/boost_adaptbx/boost/python.py:22: in 
import_ext

try: mod = __import__(name)
E   SystemError: initialization of scitbx_linalg_ext raised unreported 
exception




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024858: busco: (autopkgtest) needs update for python3.11: cannot import name '_aligners' from partially initialized module 'Bio.Align'

[Paul Gevers]

Source: busco
Version: 5.4.3-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
busco fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
busco  from testing5.4.3-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/b/busco/28706377/log.gz

File series fully applied, ends at patch 
debian/patches/find-bbmap-instead-of-bbtools.patch
Testing with python3.11 in 
/tmp/autopkgtest-lxc.firnv_xg/downtmp/autopkgtest_tmp:

unittest_runner (unittest.loader._FailedTest.unittest_runner) ... ERROR

==
ERROR: unittest_runner (unittest.loader._FailedTest.unittest_runner)
--
ImportError: Failed to import test module: unittest_runner
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 154, in 
loadTestsFromName

module = __import__(module_name)
 ^^^
  File 
"/tmp/autopkgtest-lxc.firnv_xg/downtmp/autopkgtest_tmp/tests/unittest_runner.py", 
line 2, in 

from tests.unittests import run_BUSCO_unittests
  File 
"/tmp/autopkgtest-lxc.firnv_xg/downtmp/autopkgtest_tmp/tests/unittests/run_BUSCO_unittests.py", 
line 2, in 

from busco import run_BUSCO
  File "/usr/lib/python3/dist-packages/busco/run_BUSCO.py", line 25, in 


from busco.BuscoRunner import AnalysisRunner, BatchRunner, SingleRunner
  File "/usr/lib/python3/dist-packages/busco/BuscoRunner.py", line 2, 
in 

from busco.analysis.BuscoAnalysis import BuscoAnalysis
  File 
"/usr/lib/python3/dist-packages/busco/analysis/BuscoAnalysis.py", line 
15, in 

from busco.busco_tools.hmmer import HMMERRunner
  File "/usr/lib/python3/dist-packages/busco/busco_tools/hmmer.py", 
line 7, in 

from Bio import SeqIO
  File "/usr/lib/python3/dist-packages/Bio/SeqIO/__init__.py", line 
374, in 

from Bio.Align import MultipleSeqAlignment
  File "/usr/lib/python3/dist-packages/Bio/Align/__init__.py", line 18, 
in 

from Bio.Align import _aligners
ImportError: cannot import name '_aligners' from partially initialized 
module 'Bio.Align' (most likely due to a circular import) 
(/usr/lib/python3/dist-packages/Bio/Align/__init__.py)



--
Ran 1 test in 0.000s

FAILED (errors=1)
autopkgtest [14:14:42]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024857: beaker: (autopkgtest) needs update for python3.11: python3.11: command not found

[Paul Gevers]

Source: beaker
Version: 1.11.0-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
beaker fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
beaker from testing1.11.0-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. It seems that your tests tries to run against all 
supported python versions but doesn't secure that they are installed.


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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/b/beaker/28706376/log.gz

[*] testing on python3.11:
bash: line 1: python3.11: command not found
autopkgtest [14:13:53]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024856: azure-cli: (autopkgtest) needs update for python3.11: conflicting subparser: configure

[Paul Gevers]

Source: azure-cli
Version: 2.42.0-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
azure-cli fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
azure-cli  from testing2.42.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/a/azure-cli/28706375/log.gz

_ ERROR at teardown of 
ConfigureGlobalDefaultsTest.test_configure_global_defaults _


self = testMethod=test_configure_global_defaults>


def tearDown(self):

  self.cmd('configure --defaults global="" global2=""')


tests_core/test_configure.py:33: _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3/dist-packages/azure/cli/testsdk/base.py:170: in cmd
return execute(self.cli_ctx, command, 
expect_failure=expect_failure).assert_with_checks(checks)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _

self = 
cli_ctx = 
command = 'configure --defaults global="" global2=""', expect_failure = 
False


def __init__(self, cli_ctx, command, expect_failure=False):
self.output = ''
self.applog = ''
self.command_coverage = {}
cli_ctx.data['_cache'] = None
if os.environ.get(ENV_COMMAND_COVERAGE, None):
with open(COVERAGE_FILE, 'a') as coverage_file:
if command.startswith('az '):
command = command[3:]
coverage_file.write(command + '\n')
self._in_process_execute(cli_ctx, command, 
expect_failure=expect_failure)

log_val = ('Logging ' + self.applog) if self.applog else ''
if expect_failure and self.exit_code == 0:
logger.error('Command "%s" => %d. (It did not fail as 
expected). %s\n', command,

 self.exit_code, log_val)
raise AssertionError('The command did not fail as it was 
expected.')

if not expect_failure and self.exit_code != 0:
logger.error('Command "%s" => %d. %s\n', command, 
self.exit_code, log_val)

  raise AssertionError('The command failed. Exit code: 
{}'.format(self.exit_code))

E   AssertionError: The command failed. Exit code: 1

/usr/lib/python3/dist-packages/azure/cli/testsdk/base.py:253: AssertionError
- Captured stderr call 
-
To check existing issues, please visit: 
https://github.com/Azure/azure-cli/issues

To open a new issue, please run `az feedback`
To check existing issues, please visit: 
https://github.com/Azure/azure-cli/issues

To open a new issue, please run `az feedback`
-- Captured log call 
---
INFO az_command_data_logger:azlogging.py:128 command args: configure 
--defaults {}
ERRORcli.azure.cli.core.azclierror:azlogging.py:212 The command 
failed with an unexpected error. Here is the traceback:
ERRORaz_command_data_logger:azlogging.py:213 The command failed with 
an unexpected error. Here is the traceback:
ERRORcli.azure.cli.core.azclierror:azlogging.py:212 argument 
_command_package: conflicting subparser: configure

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
 ^
  File 
"/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", 
line 565, in execute

self.parser.load_command_table(self.commands_loader)
  File "/usr/lib/python3/dist-packages/azure/cli/core/parser.py", line 
100, in load_command_table

command_parser = subparser.add_parser(command_verb,
 ^^
  File "/usr/lib/python3.11/argparse.py", line 1197, in add_parser
raise ArgumentError(self, _('conflicting subparser: %s') % name)
argparse.ArgumentError: argument _command_package: conflicting 

Bug#1024855: augur: (autopkgtest) needs update for python3.11: cannot import name '_aligners' from partially

[Paul Gevers]

Source: augur
Version: 18.1.2-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
augur fails in testing when that autopkgtest is run with the binary 
packages of python3-defaults from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
augur  from testing18.1.2-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be updated.


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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/a/augur/28706374/log.gz

= test session starts 
==
platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack -- 
/usr/bin/python3.11

cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.cskdmo0l/downtmp/build.nDH/src
plugins: mock-3.8.2
collecting ... collected 10 items / 21 errors

 ERRORS 

_ ERROR collecting tests/test_align.py 
_
ImportError while importing test module 
'/tmp/autopkgtest-lxc.cskdmo0l/downtmp/build.nDH/src/tests/test_align.py'.

Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_align.py:10: in 
from Bio import SeqIO
/usr/lib/python3/dist-packages/Bio/SeqIO/__init__.py:374: in 
from Bio.Align import MultipleSeqAlignment
/usr/lib/python3/dist-packages/Bio/Align/__init__.py:18: in 
from Bio.Align import _aligners
E   ImportError: cannot import name '_aligners' from partially 
initialized module 'Bio.Align' (most likely due to a circular import) 
(/usr/lib/python3/dist-packages/Bio/Align/__init__.py)
 ERROR collecting tests/test_clades.py 
_
ImportError while importing test module 
'/tmp/autopkgtest-lxc.cskdmo0l/downtmp/build.nDH/src/tests/test_clades.py'.

Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_clades.py:6: in 
from augur.clades import read_in_clade_definitions
augur/__init__.py:12: in 
from treetime import TreeTimeError, TreeTimeUnknownError
/usr/lib/python3/dist-packages/treetime/__init__.py:32: in 
from .treeanc import TreeAnc
/usr/lib/python3/dist-packages/treetime/treeanc.py:4: in 
from Bio import Phylo
/usr/lib/python3/dist-packages/Bio/Phylo/__init__.py:14: in 
from Bio.Phylo._io import parse, read, write, convert
/usr/lib/python3/dist-packages/Bio/Phylo/_io.py:16: in 
from Bio.Phylo import BaseTree, NewickIO, NexusIO, PhyloXMLIO, NeXMLIO
/usr/lib/python3/dist-packages/Bio/Phylo/PhyloXMLIO.py:24: in 
from Bio.Phylo import PhyloXML as PX
/usr/lib/python3/dist-packages/Bio/Phylo/PhyloXML.py:22: in 
from Bio.Align import MultipleSeqAlignment
/usr/lib/python3/dist-packages/Bio/Align/__init__.py:18: in 
from Bio.Align import _aligners
E   ImportError: cannot import name '_aligners' from partially 
initialized module 'Bio.Align' (most likely due to a circular import) 
(/usr/lib/python3/dist-packages/Bio/Align/__init__.py)
_ ERROR collecting tests/test_dates.py 
_
ImportError while importing test module 
'/tmp/autopkgtest-lxc.cskdmo0l/downtmp/build.nDH/src/tests/test_dates.py'.

Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/test_dates.py:4: in 
from augur import dates
augur/__init__.py:12: in 
from treetime import TreeTimeError, TreeTimeUnknownError
/usr/lib/python3/dist-packages/treetime/__init__.py:32: in 
from .treeanc import TreeAnc
/usr/lib/python3/dist-packages/treetime/treeanc.py:4: in 
from Bio import Phylo
/usr/lib/python3/dist-packages/Bio/Phylo/__init__.py:14: in 
from Bio.Phylo._io import parse, read, write, convert

Bug#1024854: aiotask-context: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine'

[Paul Gevers]

Source: aiotask-context
Version: 0.6.1-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
User: debian-pyt...@lists.debian.org
Usertags: python3.11
Control: affects -1 src:python3-defaults

Dear maintainer(s),

We are in the transition of adding python3.11 as a supported Python 
version [0]. With a recent upload of python3-defaults the autopkgtest of 
aiotask-context fails in testing when that autopkgtest is run with the 
binary packages of python3-defaults from unstable. It passes when run 
with only packages from testing. In tabular form:


   passfail
python3-defaults   from testing3.10.6-3
aiotask-contextfrom testing0.6.1-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of python3-defaults 
to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists 
what's new in Python3.11, it may help to identify what needs to be 
updated.  E.g.:

"""
Removed the @asyncio.coroutine() decorator enabling legacy 
generator-based coroutines to be compatible with async / await code. The 
function has been deprecated since Python 3.8 and the removal was 
initially scheduled for Python 3.10. Use async def instead. (Contributed 
by Illia Volochii in bpo-43216.)

"""

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

Paul

[0] https://bugs.debian.org/1021984
[1] https://qa.debian.org/excuses.php?package=python3-defaults

https://ci.debian.net/data/autopkgtest/testing/amd64/a/aiotask-context/28706372/log.gz

= test session starts 
==
platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack -- 
/usr/bin/python3.11

cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.xpxnssx6/downtmp/autopkgtest_tmp
collecting ... collected 0 items / 1 error

 ERRORS 

__ ERROR collecting tests/test_acceptance.py 
___

tests/test_acceptance.py:11: in 
@asyncio.coroutine
E   AttributeError: module 'asyncio' has no attribute 'coroutine'
=== short test summary info 

ERROR tests/test_acceptance.py - AttributeError: module 'asyncio' has no 
attr...
!! stopping after 1 failures 
!!!
=== 1 error in 0.02s 
===

autopkgtest [14:13:59]: test run-tests



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024836: tootle is archived and replaced by tooth

[Praveen Arimbrathodiyil]

On 27/11/22 12:59 am, Pirate Praveen wrote:

I went ahead and updated tootle with tooth and pushed here
https://salsa.debian.org/debian/tooth

Feel free to take or let me know if I should go ahead and upload it.



Pre built debs are available from 
https://people.debian.org/~praveen/tooth/README (for amd64 and arm64).


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024853: RFS: wxsvg/2:1.5.24+dfsg-1 [RC] -- Development files for wxSVG

[Alec Leamas]

Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for my package "wxsvg":

 * Package name : wxsvg
   Version  : 2:1.5.24+dfsg-1
   Upstream contact : Alex Thuering
 * URL  :http://wxsvg.sourceforge.net/
 * License  : wxWindows
 * Vcs  :https://salsa.debian.org/multimedia-team/wxsvg
   Section  : libs

The source builds the following binary packages:

  libwxsvg3 - SVG library for the wxWidgets toolkit
  libwxsvg-tools - SVG library for the wxWidgets toolkit (tools)
  libwxsvg-dev - Development files for wxSVG

Further information onhttps://mentors.debian.net/package/wxsvg/  or using

  dget 
-xhttps://mentors.debian.net/debian/pool/main/w/wxsvg/wxsvg_1.5.24+dfsg-1.dsc

Changes since the last upload:

 wxsvg (2:1.5.24+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
   * Relinked to wxWidgets 3.2 Closes: #1019765.
   * Drop patch for building against ffmpeg5.
   * Fix renamed tag in lintian overrides.
   * Fix d/copyright and an override, lintian warnings.

Bug#1024852: nvidia-driver in bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) do not support Linux kernel 6.0 or later

[Alex Relis]

Package: nvidia-driver
Version: 470.103.01-1~bpo11+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

About a week ago, linux-image-6.0.0-0.deb11.2-amd64 was introduced in 
bullseye-backports. The problem is that the nvidia-driver version in both 
bullseye (470.141.03-1~deb11u1) and bullseye-backports (470.103.01-1~bpo11+1) 
(for some reason, the version in bullseye is newer which is strange) DO NOT 
support Linux kernel 6.0.
When a user who uses a backported linux kernel and nvidia-driver upgrades their 
system, they will get an error message that looks like this 
https://imgur.com/sEVx1vc (sorry if I couldn't give you the text output; I am 
reporting this on behalf of a friend)

This issue is reproducable and happened on two of my friends' machines. We 
found a current workaround that involves booting to kernel 5.1x in the Grub 
menu, running sudo apt purge linux-image-6.0.0-0.deb11.2-amd64 && sudo apt 
install -t bullseye-backports nvidia-driver && sudo reboot now.

According to this Phoronix article ( 
https://www.phoronix.com/news/NVIDIA-515.76-Linux-Driver ), nvidia-driver 
515.76 or newer support Linux kernel 6.0. I believe the solution is to upgrade 
nvidia-driver to 515.76 or newer in bullseye-backports so that users can use 
their graphics card on kernel 6.0.

Thank you for reading my bug report and I hope you guys have a great day!

--
Alex Relis

Bug#1024851: Regression with 2022.10+dfsg-1 on Pinebook pro : broken keyboard

[Hubert Tonneau]

Package: u-boot-rockchip
Version: 2022.10+dfsg-1

On Pinebook pro,
u-boot-rockchip 2022.04+dfsg-2+b1  works nicely (only 'mem' suspend does not 
work but I don't know if it's a boot loader or kernel issue),
u-boot-rockchip 2022.10+dfsg-1  keyboard does not work anymore, preventing to 
chose non default option in the boot menu.

Bug#1024831: Acknowledgement (xorg: xserver fails to resume after suspend-to-disk)

[Klaus Singvogel]

Hi,

some additional information:

This issue only happens only with linux-image-6.0.0-0.deb11.2-amd64
After I booted the old linux-image-5.19.0-0.deb11.2-amd64, the issue does
not occur.

Best regards,
Klaus.
-- 
Klaus Singvogel
GnuPG-Key-ID: 1024R/5068792D  1994-06-27

Bug#1024836: tootle is archived and replaced by tooth

[Pirate Praveen]

On Sat, 26 Nov 2022 18:21:34 +0530 Praveen Arimbrathodiyil 
 wrote:

> Package: tootle
>
> Looks like tooth [1] has replaced now archived tootle
>
> [1] https://github.com/GeopJr/Tooth
>
> I think we should switch to this fork. May be forking the packaging 
and

> updating watch file and replacing package names is best way and tooth
> can provide tootle for a smooth upgrade experience.
>
> If you are okay with the idea, I can help with packaging.

I went ahead and updated tootle with tooth and pushed here
https://salsa.debian.org/debian/tooth

Feel free to take or let me know if I should go ahead and upload it.

Bug#1024850: bullseye-pu: package spf-engine/2.9.2-1

[Scott Kitterman]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

Negligible risk RC bug fix

[ Reason ]
Currently the pyspf-milter fails to start due to a leftover, invalid
import statement.  This fixes it, backported from the upstream fix.
There is no risk of regression since the milter binary doesn't work at
all.

[ Impact ]
pyspf-milter will continue not to work unless the end user hand edits
the file.

[ Tests ]
Can be tested manually by simply starting the milter.  No automated
tests.

[ Risks ]
None.  Fix is trivial and the package already doesn't work at all, so
can't get worse.

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
Added a patch that removes the bad import.  Same fix as upstream in
2.9.3, which is already in Testing/Unstable.

[ Other info ]
N/A

Scott K
diff -Nru spf-engine-2.9.2/debian/changelog spf-engine-2.9.2/debian/changelog
--- spf-engine-2.9.2/debian/changelog   2019-11-22 19:42:45.0 -0500
+++ spf-engine-2.9.2/debian/changelog   2022-11-26 14:10:35.0 -0500
@@ -1,3 +1,10 @@
+spf-engine (2.9.2-1+deb11u1) bullseye; urgency=medium
+
+  * Add d/p/0002-fix-leftover-import.patch from upstream to fix pyspf-milter
+failing to start due to an invalid import statement (Closes: #1008828)
+
+ -- Scott Kitterman   Sat, 26 Nov 2022 14:10:35 -0500
+
 spf-engine (2.9.2-1) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru spf-engine-2.9.2/debian/patches/0002-fix-leftover-import.patch 
spf-engine-2.9.2/debian/patches/0002-fix-leftover-import.patch
--- spf-engine-2.9.2/debian/patches/0002-fix-leftover-import.patch  
1969-12-31 19:00:00.0 -0500
+++ spf-engine-2.9.2/debian/patches/0002-fix-leftover-import.patch  
2022-11-26 14:10:24.0 -0500
@@ -0,0 +1,23 @@
+From: Scott Kitterman 
+Date: Sat, 26 Nov 2022 14:04:57 -0500
+Subject: fix leftover import
+ Backport from 2.9.3
+Origin: upstream
+Bug-Debian: http://bugs.debian.org/1008828
+
+---
+ spf_engine/milter_spf.py | 1 -
+ 1 file changed, 1 deletion(-)
+
+diff --git a/spf_engine/milter_spf.py b/spf_engine/milter_spf.py
+index 077b75b..eecf4f1 100644
+--- a/spf_engine/milter_spf.py
 b/spf_engine/milter_spf.py
+@@ -37,7 +37,6 @@ import spf_engine.policydspfsupp as config
+ from spf_engine.util import drop_privileges
+ from spf_engine.policydspfsupp import _setExceptHook
+ from spf_engine.util import write_pid
+-from spf_engine.util import own_socketfile
+ from spf_engine.util import fold
+ 
+ __version__ = "2.9.2"
diff -Nru spf-engine-2.9.2/debian/patches/series 
spf-engine-2.9.2/debian/patches/series
--- spf-engine-2.9.2/debian/patches/series  2019-11-22 19:35:53.0 
-0500
+++ spf-engine-2.9.2/debian/patches/series  2022-11-26 14:05:06.0 
-0500
@@ -1 +1,2 @@
 0001-install-conf-fix.patch
+0002-fix-leftover-import.patch

Bug#1024849: RFS: pipes.sh/1.3.0-1 [ITP] -- Animated pipes terminal screensaver

[matthias . geiger1024]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "pipes.sh":

* Package name : pipes.sh
   Version  : 1.3.0-1
   Upstream contact : Yu-Jie Lin 
* URL  : https://github.com/pipeseroni/pipes.sh
* License  : MIT
* Vcs  : https://salsa.debian.org/werdahias/pipes.sh
   Section  : games

The source builds the following binary packages:

  pipes-sh - Animated pipes terminal screensaver

To access further information about this package, please visit the following
URL:

  https://mentors.debian.net/package/pipes.sh/

Alternatively, you can download the package with 'dget' using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/p/pipes.sh/pipes.sh_1.3.0-1.dsc

There hasn't been a new upstream release in quite some time (~ 5 years), so
this would be a low-maintanance package. Furthermore, it's a very lightweight
package.

Changes for the initial release:

pipes.sh (1.3.0-1) unstable; urgency=medium
.
   * Initial release. (Closes: #1024273)

Regards,
--
  Matthias Geiger

 

Bug#1024848: "Operating modes" are nearly identical

[Askar Safin]

Package: reportbug
Version: 11.5.1
Severity: normal
X-Debbugs-Cc: safinas...@gmail.com

In the beginning "reportbug" asks "operating mode": novice, standard, advanced 
and expert.

This is very bad question. Moreover, the answer will not matter. Here is 
reportbug logs when I answered "novice" and
when I answered "expert": https://paste.debian.net/1261952/ , 
https://paste.debian.net/1261953/ . As you can see, changes are
small. So, please, remove this "operating mode" question. Or at very least make 
2 modes, not 4

-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /root/.reportbugrc:
reportbug_version "11.5.1"
mode expert
ui text
realname "Askar Safin"
email "safinas...@gmail.com"
no-check-uid
no-cc
list-cc-me
smtphost reportbug.debian.org

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

Kernel: Linux 5.10.0-0.deb9.17-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages reportbug depends on:
ii  apt2.5.4
ii  python33.10.6-3
ii  python3-reportbug  11.5.1
ii  sensible-utils 0.0.17

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail
ii  debconf   1.5.79
pn  debsums   
pn  default-mta | postfix | exim4 | mail-transport-agent  
pn  dlocate   
pn  emacs-bin-common  
ii  file  1:5.41-4
pn  gnupg | pgp   
pn  python3-urwid 
pn  reportbug-gtk 
pn  xdg-utils 

Versions of packages python3-reportbug depends on:
ii  apt2.5.4
ii  file   1:5.41-4
ii  python33.10.6-3
ii  python3-apt2.3.0+nmu1+b1
ii  python3-debian 0.1.49
ii  python3-debianbts  3.2.4
ii  python3-requests   2.28.1+dfsg-1
ii  sensible-utils 0.0.17

python3-reportbug suggests no packages.

-- no debconf information

Bug#1024561: Unmaintained, keep out of stable

[Sam Trenholme]

[1] RFC8482 responds to ANY in such as way as to not break Qmail

On Sat, Nov 26, 2022 at 10:34 AM Sam Trenholme  wrote:
>
> Upstream here again.  I have released MaraDNS 3.5.0030 and 3.4.09 with
> a security update: MaraDNS now fully supports RFC8482, which means
> MaraDNS no longer supports ANY records. [1] While MaraDNS does not
> have long packet support, this removes one possible denial of service
> amplification path.
>
> If someone can not step up to plate to maintain MaraDNS for Debian, we
> should deprecate and eventually remove the package.
>
> I may end up making my own .deb files for MaraDNS.
>
> -- Sam
>
> On Mon, Nov 21, 2022 at 5:03 AM Moritz Muehlenhoff  wrote:
> >
> > Source: maradns
> > Version: 2.0.13-1.4
> > Severity: serious
> >
> > The last maintainer upload was in 2015 and the version currently in the
> > archive is way behind current upstream releases (which is at 3.4.07),
> > we have plenty of maintained DNS servers, keep it out of testing (
> > and if noone picks it up, remove it from the archive).
> >

Bug#1024561: Unmaintained, keep out of stable

[Sam Trenholme]

Upstream here again.  I have released MaraDNS 3.5.0030 and 3.4.09 with
a security update: MaraDNS now fully supports RFC8482, which means
MaraDNS no longer supports ANY records. [1] While MaraDNS does not
have long packet support, this removes one possible denial of service
amplification path.

If someone can not step up to plate to maintain MaraDNS for Debian, we
should deprecate and eventually remove the package.

I may end up making my own .deb files for MaraDNS.

-- Sam

On Mon, Nov 21, 2022 at 5:03 AM Moritz Muehlenhoff  wrote:
>
> Source: maradns
> Version: 2.0.13-1.4
> Severity: serious
>
> The last maintainer upload was in 2015 and the version currently in the
> archive is way behind current upstream releases (which is at 3.4.07),
> we have plenty of maintained DNS servers, keep it out of testing (
> and if noone picks it up, remove it from the archive).
>

Bug#1023855: TOTP module not enabled in slapd-contrib

[Kees Meijs]

Hello Ryan,

No worries. I'm glad you're helping out (with the backport as well) anyway.

My goal is support for RFC 6238 and the manual page you're referring to 
states this is supported.


So yes: the built-in module should work fine and therefore the contrib 
module is not needed in my use case.


Thanks again!

Cheers,
Kees

On 26-11-2022 03:06, Ryan Tandy wrote:

Hi Kees,

On Tue, Nov 22, 2022 at 11:14:43AM +0100, Kees Meijs wrote:
Unfortunately I didn't have time earlier, but I just managed to 
install a new virtual machine using bookworm. After installing both 
the slapd and slapd-contrib packages, I do not see the TOTP module.


So no, it seems not to be included.


Sorry if I wasn't clear. I agree the contrib totp module is not built.

The slapd-otp(5) module, however, is:

# dpkg-query -W slapd
slapd    2.5.13+dfsg-2+b1
# dpkg-query -L slapd | grep otp
/usr/lib/ldap/otp-2.5.so.0.1.8
/usr/lib/ldap/otp.la
/usr/share/man/man5/slapo-otp.5.gz
/usr/lib/ldap/otp-2.5.so.0
/usr/lib/ldap/otp.so

My understanding is that slapd-otp(5) supersedes and obsoletes the 
contrib module, providing a superset of its features (the man page 
mentions both TOTP and HMAC). That's why I asked if it meets your 
needs, or if you specifically need the contrib totp module. I'm not 
keen on shipping both unless there's a convincing reason.


thanks, and sorry for the back-and-forth,
Ryan

Bug#1024268: (no subject)

[Georges Khaznadar]

Thank you for the additional information, Amy!

A conflict between CloneZilla and whiptail is still an important issue
...

Amy a écrit :
> After some investigation I think I might have filed a bug for the wrong
> package or something. Removing 'whiptail' allows CloneZilla to work
> normally.
> 

Steven Shiau, who is in Cc:, has filed this bug against libpopt0:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022052

@Amy:
Since bug#1022052 is now considered as closed, please can you check
whether the package whiptail_0.52.22-1 is compatible with clonezilla?

You can fetch it from debian/sid, and if you wait one day longer, it
should probably enter debian/testing.

Best regards,   Georges.





-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Bug#1024773: libpresage-doc: missing Breaks+Replaces: libpresage-dev (<< 0.9.1-2.4)

[Guido Günther]

Hi Andreas,
On Thu, Nov 24, 2022 at 05:30:16PM +0100, Andreas Beckmann wrote:
> Package: libpresage-doc
> Version: 0.9.1-2.4
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'testing'.
> It installed fine in 'testing', then the upgrade to 'sid' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
> 
> >From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package libpresage-dev:amd64.
>   Preparing to unpack .../libpresage-dev_0.9.1-2.3_amd64.deb ...
>   Unpacking libpresage-dev:amd64 (0.9.1-2.3) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/libpresage-dev_0.9.1-2.3_amd64.deb (--unpack):
>trying to overwrite 
> '/usr/share/doc/libpresage-dev/getting_started.txt.gz', which is also in 
> package libpresage-doc 0.9.1-2.4
>   Errors were encountered while processing:
>/var/cache/apt/archives/libpresage-dev_0.9.1-2.3_amd64.deb

I'll prepare another NMU to fix that.
 -- Guido

> 
> 
> cheers,
> 
> Andreas

Bug#1024847: VCS

[Martin Dosch]

Dear all,

please ignore the wrong Vcs URL, I pushed to 
https://salsa.debian.org/mdosch/wofi-pass

Best regards,
Martin


signature.asc
Description: PGP signature

Bug#221790: perl: please kick out that annoying locale warning

[Russ Allbery]

Rene Engelhard  writes:

> dpkg-buildpackage: source package is dmake
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
> LANGUAGE = (unset),
> LC_ALL = (unset),
> LANG = "de_DE@euro"
> are supported and installed on your system.

> is _extremely_ annoying. Everytime I build something in a chroot via
> sbuild (which is a clean chroot; so no locales are installed there)
> and I forget to set LANG="C" this message obfuscates everything...

I used to see this warning all the time, but I haven't seen it in years.
I think something may have changed about how locales works or about how
upgrades are sequenced that resolved it?  However that happened, I'm
wondering if this 19-year-old bug should be closed.

-- 
Russ Allbery (r...@debian.org)  

Bug#969657: pcmanfm: relies on xfce4-panel, while LXDE uses lxpanel

[Akbarkhon Variskhanov]

Hello.

Thanks for reporting, Michele.

On Fri, 5 Feb 2021 12:09:19 +0200 Andriy Grytsenko  wrote:
> control: reassign -1 xfce4-panel
>
> This is an issue from file 
> /usr/share/applications/panel-desktop-handler.desktop
> which should contain 'OnlyShowIn=XFCE;' line but it does not have one.

Thank you for identifying the issue, Andriy.

What's weird is that the user has this desktop entry installed and
it's only used by xfce4-panel. So their initial statement was a lie.
They must have had xfce4-panel at some point.

Or perhaps (very unlikely) pcmanfm or one of its dependencies used to
install this file at some point in the past? Could you think of such
packages?
Running `apt-file find
/usr/share/applications/panel-desktop-handler.desktop` on unstable
obviously lists only one:
xfce4-panel: /usr/share/applications/panel-desktop-handler.desktop

> Dear maintainer of xfce4-panel, please, handle this issue. Thank you.

I'll try to get in touch with upstream. In the meantime, I'd suggest
removing that file as a temporary workaround. Just purge xfce4-panel
and its files if you don't need or want it anymore.

Cheers,
Akbar.

Bug#871225: Man.pm: False point size changes

[Russ Allbery]

Bjarni Ingi Gislason  writes:

> "man gcc" with

> MAN_KEEP_STDERR=yes
> MANOPT=--encoding=latin1 --no-hyphenation --warnings=w --no-justification
> MANWIDTH=80

>* What was the outcome of this action?

> :3310: warning: \s escape results in non-positive point size; 
> set to 1
> :3311: warning: \s escape results in non-positive point size; 
> set to 1
> :25: backtrace: string `C+'
[...]

The code that caused these bugs was from minor formatting adjustments
visible only in troff output (and, at least in my opinion, somewhat
dubious).  That code has also been a constant source of bugs and weird
issues for years.

In podlators 5.00, released yesterday, I dropped nearly all of the
troff-only guesswork on the grounds that the minor improvements in
formatting for an output format almost no one uses weren't worth the
maintenance burden.  (I suspect that anyone who wants to print Perl
documentation these days would be better-served by using the rendered
output of one of the excellent POD to HTML converters.)

This bug can therefore be closed once podlators 5.00 is incorporated into
the Perl packages in Debian.  That may still be a bit, since I'm not sure
if it will be pulled into a point release or only the next major release
of Perl.

-- 
Russ Allbery (r...@debian.org)  

Bug#1020574: perl-doc: encoding issue / spelling mistake with "perldoc perlfaq4"

[Russ Allbery]

Vincent Lefevre  writes:

> "perldoc perlfaq4" gives in UTF-8 locales

> [...]
> The trick to this problem is avoiding accidental autovivification. If
> you want to check three keys deep, you might navely try this:

> where  is actually the EF byte as shown by the "less" pager.

This bug has been fixed in podlators 5.00, released yesterday.  It will
still be some time before it's fixed in Debian, since I'm not sure if that
release will be pulled into a Perl point release or will wait for the next
major Perl release, but this bug can be closed once Perl in Debian has
been updated to a version with that release.

-- 
Russ Allbery (r...@debian.org)  

Bug#1024847: RFS: wofi-pass/0.0~git20221028.869c545-1 [ITP] -- pass support for wofi using wtype

[Martin Dosch]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "wofi-pass":

 * Package name : wofi-pass
   Version  : 0.0~git20221028.869c545-1
   Upstream contact : https://github.com/TinfoilSubmarine/wofi-pass/issues
 * URL  : https://github.com/TinfoilSubmarine/wofi-pass
 * License  : GPL-2
 * Vcs  : https://salsa.debian.org/pkg/wofi-pass
   Section  : utils

The source builds the following binary packages:

  wofi-pass - pass support for wofi using wtype

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/wofi-pass/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/w/wofi-pass/wofi-pass_0.0~git20221028.869c545-1.dsc

Changes for the initial release:

 wofi-pass (0.0~git20221028.869c545-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1024838)

Regards,
--
  Martin Dosch


signature.asc
Description: PGP signature

Bug#1024846: Does not start because it cannot create the control socket

[Bernhard Schmidt]

Package: openbgpd
Version: 7.7-1
Severity: normal

Hi Marco,

I'm filing this as severity normal because I stumbled across it on a
local bullseye backport, and I haven't tested it on sid yet. But I think
it should be affected as well.

After upgrading from 7.2 to 7.7 openbgpd does not start anymore.

Nov 26 17:56:51 dns-test bgpd[256654]: PF_KEY not available, disabling ipsec
Nov 26 17:56:51 dns-test bgpd[256654]: control_init: unlink /run/bgpd.sock.0: 
Read-only file system
Nov 26 17:56:51 dns-test bgpd[256654]: fatal in bgpd: control socket setup 
failed

The systemd unit was changed from

ProtectSystem=full

to

ProtectSystem=strict
RuntimeDirectory=openbgpd

A writeable /run/openbgpd is created, but not used in the default
configuration, which creates the socket directly in /run

Adding an override

ReadWritePaths=/run

fixes the issue, but this opens a few more holes. So I think the default
location for the control socket should rather be moved to /run/openbgpd,
possibly by setting --runstatedir and/or --with-runstatedir accordingly.

Bernhard

Bug#1021955: pod2man: runaway italics inside C<>

[Russ Allbery]

Jakub Wilk  writes:

> pod2man misformats I<> inside C<>.

> For example, if you run:

> printf '=head1 FOO\n\nC should be italicized, not the 
> rest>!\n' | pod2man - | man -l -

> not only "foo" is italicized, but also everything up to the closing quote
> character.

This bug has been fixed in podlators 5.00, which was released yesterday.
Hopefully it should make its way into at least the next major upstream
version of Perl, if not the next patch release.  (5.00 has fairly
significant changes, so I'm not sure if it will be pulled in for patch
releases.)

-- 
Russ Allbery (r...@debian.org)  

Bug#738189: perldoc does not respect the user locale

[Russ Allbery]

Klaus Ethgen  writes:

> When I have this small perl file:
> ---
> =head1 TEST

> =over

> =item

> Test

> =item

> Test

> =back
> ---

> And using "perldoc file.pl", I get the output:

>...
>·   Test
>...

> This is the UTF-8 representation of a "·". But I do not have UTF-8 at
> all and also my locales (see below) tells this. Also the file is no
> UTF-8 than latin1. (Well, in this test case it it ASCII 7bit.)

This bug was from quite some time ago (eight years), and I think it dates
from when perldoc was using Pod::Man and nroff by default.  Pod::Man uses
the \(bu character escape, so I think this bug was actually an nroff bug
rather than a Perl or perldoc bug, although it may have been a problem
with the flags that perldoc passed to nroff.

However, more to the point, perldoc was switched to use Pod::Text by
default some time ago, so you now have to use "-n nroff" to get this
behavior.  Pod::Text does not attempt to use any fancy bullets (it just
uses "*"), so you should no longer see this problem by default.  I think
it may therefore be worth closing as fixed by default, although it's still
possible to get the nroff output.

I tried to test whether nroff still did the same thing in an ISO 8859-1
locale, but ran into the fact that non-UTF-8 locales have been deprecated
in Debian and are no longer easily configurable as of locales 2.31-14 from
last year, so I'm no longer sure of the right way to test this on a system
that wasn't already using an ISO 8859-1 locale.

-- 
Russ Allbery (r...@debian.org)  

Bug#941980: pod2man: Please convert zero-width space (u200B) to \:

[Russ Allbery]

Russ Allbery  writes:
> Jean-Michel Vourgère  writes:

>> I'm using pod to generate man files in package rrdtool.

>> I had an issue with long man lines such as:
>> BIvnameE>=IrrdfileE>:Ids-nameE>:ICFE>[:step=IstepE>][:start=ItimeE>][:end=ItimeE>][:reduce=IBE>][:daemon=IaddressE>]
>> that results lintian "manpage-has-errors-from-man": can't break line.

>> That I fixed that by inserting unicode zero-width-space characters 200B:
>> BIvnameE>=IrrdfileE>:Ids-nameE>:ICFE>[:step=IstepE>][:start=ItimeE>]E<0x200B>[:end=ItimeE>]E<0x200B>[:reduce=IBE>]E<0x200B>[:daemon=IaddressE>]

>> I expected pod2man to generate the corect \: escape sequence, but it
>> did not.

[...]

> Unfortunately, \: appears to be a groff extension as far as I can tell.
> It's at least not mentioned in CSTR 54, nor in other older documentation
> I can find for the *roff language.  That means this gets entangled in
> the general design constraint that pod2man tries to produce portable
> *roff output that's not specific to groff.

> I'm not certain this is fully correct because unfortunately it's very
> difficult to search for \: to get more data.

Many years later, I have incorporated this change in podlators 5.00, just
now released.  It will still be a bit before that's incorporated into Perl
and thus into the Debian Perl packages, but I wanted to let you know that
this fix is properly in progress.

I went ahead and did the conversion to \: unconditionally since it's
documented in the mandoc roff reference as well as groff.  That covers
nearly all modern platforms.  It may still not work on a few older nroff
implementations like Solaris or AIX, but this case is obscure enough and
enough other things related to Unicode don't work there anyway that I
don't think it should cause any serious problems.

-- 
Russ Allbery (r...@debian.org)  

Bug#1024845: transition: linphone-stack

[Bernhard Schmidt]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Dear release team,

once again, hopefully for the last time before the release, I'm asking for
permission for a small mostly self-contained transition of the whole linphone
stack. It has been staged in experimental.

Most of these libraries don't change SONAME (except for ortp, mediastreamer2)
but upstream only supports staying within the same minor version. So there is a
(>= | < ) dependency generated with shlibs and the stack will have to migrate
in one go.

bctoolbox 5.0.37-2 -> 5.1.64-1
belr 5.0.37-2 -> 5.1.64-1
bzrtp 5.0.37-2 -> 5.1.64-1
lime 5.0.37+dfsg-5 -> 5.1.64+dfsg-1
bcmatroska2 5.0.37-2 -> 5.1.20-1
ortp 1:5.0.37-2 -> 1:5.1.64-1
belcard 5.0.37-2 -> 5.1.64-1
belle-sip 5.0.37+dfsg-3 -> 5.1.64+dfsg-1
mediastreamer2  1:5.0.37+dfsg-4 -> 1:5.1.64+dfsg-1
linphone 5.0.37-6 -> 5.1.65-1
linphone-desktop 4.3.2-2 -> 4.4.10-1

only ortp has reverse dependencies outside of the linphone stack that will need
a binNMU.

libosmo-abis
trx

All other packages listed in the transition belong to the linphone stack and
will be uploaded by me.

https://release.debian.org/transitions/html/auto-ortp.html

Bernhard

Bug#1024395: CONFIG_INTEGRITY_PLATFORM_KEYRING was missing for mokutil --list-enrolled to work

[Eric Valette]

CONFIG_INTEGRITY_PLATFORM_KEYRING=y

But the bug is still there

-- eric

Bug#1024687: Wrong soversion in libfm-qt11=1.2.0-1

[陳昌倬]

Control: severity -1 serious

Sorry, we did not notice the soversion has been changed. Will initiate a
transition for this.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#1024771: RFP: libnet-dns-resolver-unbound-perl -- Net::DNS resolver based on libunbound

[Thomas Uhle]

On Sat, 26 Nov 2022, gregor herrmann wrote:


Package created (in the Debian Perl Group) and uploaded to the NEW
queue, should be in unstable soon.


Cheers,
gregor



Thanks a lot!

Bug#1024844: notary: FTBFS: cannot use _protobuf.Empty{} (value of type *empty.Empty) as type *emptypb.Empty in argument to s.client.ListFiles

[Mathias Gibbens]

Source: notary
Version: 0.7.0+ds1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

  notary appears to be failing to build due to a protobuf-related
error. In a clean sid schroot:

>   cd _build && go install -trimpath -v -p 16 -tags pkcs11
> github.com/theupdateframework/notary
> github.com/theupdateframework/notary/client
> github.com/theupdateframework/notary/client/changelist
> github.com/theupdateframework/notary/cmd/escrow
> github.com/theupdateframework/notary/cmd/notary
> github.com/theupdateframework/notary/cmd/notary-server
> github.com/theupdateframework/notary/cmd/notary-signer
> github.com/theupdateframework/notary/cryptoservice
> github.com/theupdateframework/notary/passphrase
> github.com/theupdateframework/notary/proto
> github.com/theupdateframework/notary/server
> github.com/theupdateframework/notary/server/errors
> github.com/theupdateframework/notary/server/handlers
> github.com/theupdateframework/notary/server/snapshot
> github.com/theupdateframework/notary/server/storage
> github.com/theupdateframework/notary/server/timestamp
> github.com/theupdateframework/notary/signer
> github.com/theupdateframework/notary/signer/api
> github.com/theupdateframework/notary/signer/client
> github.com/theupdateframework/notary/signer/keydbstore
> github.com/theupdateframework/notary/storage
> github.com/theupdateframework/notary/storage/rethinkdb
> github.com/theupdateframework/notary/trustmanager
> github.com/theupdateframework/notary/trustmanager/remoteks
> github.com/theupdateframework/notary/trustmanager/yubikey
> github.com/theupdateframework/notary/trustpinning
> github.com/theupdateframework/notary/tuf
> github.com/theupdateframework/notary/tuf/data
> github.com/theupdateframework/notary/tuf/signed
> github.com/theupdateframework/notary/tuf/testutils
> github.com/theupdateframework/notary/tuf/testutils/interfaces
> github.com/theupdateframework/notary/tuf/testutils/keys
> github.com/theupdateframework/notary/tuf/utils
> github.com/theupdateframework/notary/tuf/validation
> github.com/theupdateframework/notary/utils
> github.com/theupdateframework/notary/version
> 
> [snip]
> 
> # github.com/theupdateframework/notary/trustmanager/remoteks
> src/github.com/theupdateframework/notary/trustmanager/remoteks/client
> .go:105:37: cannot use _protobuf.Empty{} (value of type
> *empty.Empty) as type *emptypb.Empty in argument to
> s.client.ListFiles


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

Bug#1012162: nodejs: Backports version for Bullseye

[Mohd Bilal]

On Tue, 31 May 2022 07:05:00 + Eerste Laatste  
wrote:



Would it be possible to have a backports version of nodejs for Bullseye?
I am running into problems for example with logical assignment operators
that are supported since NodeJS 15.0.0.



I made a try rebuilding nodejs for bullseye-backports using backported 
build dependencies from 
https://people.debian.org/~praveen/fasttrack-staging .


I tried building with the bundled openssl since openssl 3 wasn't 
available for bullseye


Currently the build fails with 3 test failures which I'm not able to fix 
after countless tries.


not ok 606 parallel/test-dgram-send-cb-quelches-error
  ---
  duration_ms: 11.634
  severity: fail
  exitcode: 1
  stack: |-
node:assert:400
throw err;
^

AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy 
value:


  assert.ok(err)

at callbackOnly 
(/<>/test/parallel/test-dgram-send-cb-quelches-error.js:24:10)

at callbackOnly (/<>/test/common/index.js:437:15)
at process.processTicksAndRejections 
(node:internal/process/task_queues:82:21) {

  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: null,
  expected: true,
  operator: '=='
}

Node.js v18.7.0
  ...

not ok 1689 parallel/test-module-loading-globalpaths
  ---
  duration_ms: 2.220
  severity: fail
  exitcode: 1
  stack: |-
node:internal/modules/cjs/loader:959
  throw err;
  ^

Error: Cannot find module 'foo'
Require stack:
- /<>/test/parallel/test-module-loading-globalpaths.js
at Module._resolveFilename 
(node:internal/modules/cjs/loader:956:15)

at Module._load (node:internal/modules/cjs/loader:804:27)
at Module.require (node:internal/modules/cjs/loader:1022:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. 
(/<>/test/parallel/test-module-loading-globalpaths.js:15:15)

at Module._compile (node:internal/modules/cjs/loader:1120:14)
at Module._extensions..js 
(node:internal/modules/cjs/loader:1174:10)

at Module.load (node:internal/modules/cjs/loader:998:32)
at Module._load (node:internal/modules/cjs/loader:839:12)
at Function.executeUserEntryPoint [as runMain] 
(node:internal/modules/run_main:81:12) {

  code: 'MODULE_NOT_FOUND',
  requireStack: [
'/<>/test/parallel/test-module-loading-globalpaths.js'
  ]
}

Node.js v18.7.0
node:internal/modules/cjs/loader:959

not ok 2035 parallel/test-repl
  ---
  duration_ms: 0.714
  severity: fail
  exitcode: 1
  stack: |-
out: ""
in: ""
out: "message"
in: "'Read, Eval, Print Loop'"

[...]

in: "{ a: 1 }"
out: "{ \"a\": "
in: "... "
out: "1 }"
in: "{ a: 1 }"
out: "class Foo { #private = true "
in: ""
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^

AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

'' !== '... '

at runReplTests (/<>/test/parallel/test-repl.js:91:16)
at process.processTicksAndRejections 
(node:internal/process/task_queues:95:5)

at async /<>/test/parallel/test-repl.js:830:5 {
  generatedMessage: true,
  code: 'ERR_ASSERTION',
  actual: '',
  expected: '... ',
  operator: 'strictEqual'
}

Node.js v18.7.0


You can find my changes here:

 https://salsa.debian.org/rmb/nodejs/-/tree/bullseye-backports

--
╭───╮
│ Mohammed Bilal│
│ 2D65 BC1E B966 5A6E 97F9 730A B3F5 9452 8521 9E1F │
╰───╯


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024771: RFP: libnet-dns-resolver-unbound-perl -- Net::DNS resolver based on libunbound

[gregor herrmann]

On Thu, 24 Nov 2022 16:23:05 +0100, Thomas Uhle wrote:

> Package: wnpp
> Severity: wishlist
> X-Debbugs-CC: Debian Perl Group 
> , Unbound Packagers 
> 
> 
> * Package name: libnet-dns-resolver-unbound-perl
>   Version : 1.20
>   Upstream Author : Dick Francks 
> * URL or Web page : https://metacpan.org/release/Net-DNS-Resolver-Unbound
> * License : MIT
>   Description : Net::DNS resolver based on libunbound

Package created (in the Debian Perl Group) and uploaded to the NEW
queue, should be in unstable soon.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#975407: Moved

[Teus Benschop]

Hi Bastian,

The repository how now been moved to the new location.

An upload was done that, hopefully, closes this bug.

If you feel there’s still something to be done on this bug, please feel free to 
re-open it.

Bug#1021060: apt-clone fails when the lsb_release Python module is not available

[Chris]

UPDATE to my 10/20/22 post.

After a rebuild of my system a month after this post, it turns out (for 
me at least and may not be related), 2 things appeared to have happened.


1. It appears that almost all the apps to be installed using apt-clone 
restore, I am seeing broken packages shortly after starting the process.
The "broken" apps appear to be better than 90% of all apps installed. Of 
course, the process never finishes correctly and the system runs fine 
both before and after since nothing was applied .


2. It appears that apt-clone overwrites the files that are patched - I 
wonder if this could have produced the issue above.


I have tippled checked that patches are applied properly and simply 
running apt-clone without parms runs properly without issues (then 
again, it's not doing anything).
I realize that trying an apt-clone after 30 days that packages may be 
out of sync from the archived file to what would be pulled down, but 
before this bug appeared, I don't recall having this issue going back in 
time even with more than 30 days since the last apt-clone restore.


To date, I have not really found an efficient way to restore from 
something so I continue to keep an eye on this bug and have shelved 
Debian for now.


--
Keep well,
Chris
<><

Bug#1024825: systemd: lots of incorrect "Lid opened" / "Lid closed" messages in the logs

[Vincent Lefevre]

On 2022-11-26 06:16:01 +0100, Vincent Lefevre wrote:
> In the journalctl output since the last reboot, while I'm not
> touching the lid:
> 
> Nov 26 05:43:06 zira systemd-logind[829]: Lid closed.
> Nov 26 05:43:09 zira systemd-logind[829]: Lid opened.
> Nov 26 05:43:36 zira systemd-logind[829]: Lid closed.
> Nov 26 05:43:38 zira systemd-logind[829]: Lid opened.
[...]

These messages stopped after I moved the lid. I'm wondering whether
this is a hardware bug.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1024842: apt: document the /v/l/apt/lists/auxfiles directory

[Patrice Duroux]

Package: apt
Version: 2.5.4
Severity: wishlist

Dear Maintainer,

Information on it is a bit « obscure » to me.
First no trace for it in the /v/l/dpkg/info/apt.list on my system.
Second it is not listed in the FILES section of the apt-get(8).

Thanks to codesearch.d.o and a simple rgrep on /u/b/*, what I understood
is that it can be dynamically (re)created if it is missing and appears to be
referenced externally only by mmdebstrap.

Also, could there be a way to tell if a directory belongs to the content
of any package other than looking into /v/l/dpkg/info/* because for example
'apt-file search' only works for regular files. Isn't it?

Thanks,
Patrice


-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (no /etc/apt/preferences.d/* present) --


-- (/etc/apt/sources.list present, but not submitted) --


-- (/etc/apt/sources.list.d/bouml.list present, but not submitted) --


-- (/etc/apt/sources.list.d/dbeaver.list present, but not submitted) --


-- (/etc/apt/sources.list.d/deb-multimedia.list present, but not submitted) --


-- (/etc/apt/sources.list.d/experimental.list present, but not submitted) --


-- (/etc/apt/sources.list.d/google-chrome.list present, but not submitted) --


-- (/etc/apt/sources.list.d/liveusb.list present, but not submitted) --


-- (/etc/apt/sources.list.d/microsoft-prod.list present, but not submitted) --


-- (/etc/apt/sources.list.d/nilarimogard-ubuntu-webupd8-focal.list present, but 
not submitted) --


-- (/etc/apt/sources.list.d/signal-xenial.list present, but not submitted) --


-- (/etc/apt/sources.list.d/skype-unstable.list present, but not submitted) --


-- (/etc/apt/sources.list.d/sublime-text.list present, but not submitted) --


-- (/etc/apt/sources.list.d/teams.list present, but not submitted) --


-- (/etc/apt/sources.list.d/vivaldi.list present, but not submitted) --


-- (/etc/apt/sources.list.d/waydroid.list present, but not submitted) --


-- (/etc/apt/sources.list.d/wire-desktop.list present, but not submitted) --


-- (/etc/apt/sources.list.d/zerotier.list present, but not submitted) --


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

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

Versions of packages apt depends on:
ii  adduser 3.129
ii  base-passwd 3.6.1
ii  debian-archive-keyring  2021.1.1
ii  gpgv2.2.40-1
ii  libapt-pkg6.0   2.5.4
ii  libc6   2.36-5
ii  libgcc-s1   12.2.0-9
ii  libgnutls30 3.7.8-4
ii  libseccomp2 2.5.4-1+b2
ii  libstdc++6  12.2.0-9
ii  libsystemd0 252.1-1

Versions of packages apt recommends:
ii  ca-certificates  20211016

Versions of packages apt suggests:
pn  apt-doc 
ii  dpkg-dev1.21.9
ii  gnupg   2.2.40-1
ii  powermgmt-base  1.37
ii  synaptic0.91.2

-- Configuration Files:
/etc/apt/apt.conf.d/01autoremove [Errno 2] Aucun fichier ou dossier de ce type: 
'/etc/apt/apt.conf.d/01autoremove'

-- no debconf information

Bug#1024841: parallel: please build with libreoffice-writer-nogui

[Rene Engelhard]

Package: parallel
Severity: wishlist
Tags: patch

Dear Maintainer,

I just looked whether the idlc removal in 7.5 (or other changes...)
would break stuff depending on libreoffice.

While doing this I noticed that parallel does 

[...]
libreoffice --headless --convert-to pdf parallel_cheat_bw.fodt \
|| echo "Warning: libreoffice failed. Using old parallel_cheat_bw.pdf"
[...]

in its tests.

Note the --headless. This is exactly the reason why libreoffice-*-nogui were
introduced. ;)

Admittedly minor, but it doesn't do harm to use it :)

(Since it's arch all and arch all is built on amd64 anyway that 
libreoffice-*-nogui
is available on only a subset of archs is no issue either)

Trivial patch.

diff -Nru parallel-20220722+ds/debian/control 
parallel-20220722+ds/debian/control
--- parallel-20220722+ds/debian/control 2022-07-27 11:26:27.0 +0200
+++ parallel-20220722+ds/debian/control 2022-11-26 15:08:12.0 +0100
@@ -11,7 +11,7 @@
  pod2pdf,
  libpod-pom-view-restructured-perl,
  texinfo,
- libreoffice-writer
+ libreoffice-writer-nogui
 Rules-Requires-Root: no
 Standards-Version: 4.6.1
 Homepage: https://www.gnu.org/software/parallel/

Regards,

Rene

Bug#1024840: msc-generator: please build-depend on libreoffice-impress-nogui only and only for tests

[Rene Engelhard]

Package: msc-generator
Severity: wishlist
Tags: patch

Dear Maintainer,

I just looked whether the idlc removal in 7.5 (or other changes...)
would break stuff depending on libreoffice.

In msc-generator I noticed that it build-depends on libreoffice
completely. I don't think that is needed since the GUI parts shouldn't
be needed. In fact it seems that it just does document conversion where
the libreoffice-*-nogui suffice.

Besides that, do you really need libreoffice-nogui? From looking at the
log I see that it's pptx to png, so libreoffice-impress-nogui should
suffice? (No idea what it contains for fonts libeoffice recommends, but
then again I don't think Recommends are installed anyway on the buildds)

Also, dh_auto_test is not ran if DEB_BUILD_OPTIONS contains nocheck. So
one can skip this alltogether if not running the tests for some reason.

So I suggest the following:

--- msc-generator-8.1/debian/control2022-07-28 13:30:06.0 +0200
+++ msc-generator-8.1/debian/control2022-11-26 15:46:30.0 +0100
@@ -5,7 +5,7 @@
 Build-Depends: debhelper-compat (=13), g++ (>=10), automake, bison, flex,
  libfl-dev, texinfo, libcairo2-dev, libfreetype6-dev, libfontconfig, help2man,
  libgraphviz-dev, texlive, texlive-plain-generic, libglpk-dev, libsdl2-dev,
- libminizip-dev, libtinyxml2-dev, libreoffice [amd64],
+ libminizip-dev, libtinyxml2-dev, libreoffice-impress-nogui [amd64] ,
  fonts-droid-fallback, fonts-urw-base35,
  fonts-dejavu-core
 Standards-Version: 4.6.1

Regards,

Rene

Bug#944757: endless-sky: please package Endless Sky 0.9.10

[Damyan Ivanov]

Hi!

[dropped most of CC]

Sorry it took me so long to respond.

-=| quyykk, 18.11.2022 14:06:02 + |=-
> On Sun, Nov 13, 2022, 14:13 Damyan Ivanov,  
> wrote:
> 
> Hello Zitchas,
> 
> -=| Zitchas Z, 11.11.2022 14:24:57 -0700 |=-
> > Good day everyone,
> >
> > To start off, I have a few questions for you in regards to this.
> Sorry for the
> > quantity, I haven't been part of the process of getting a game into
> Debian
> > before, so I'm not sure on done of the terminology or what it
> entails.
> 
> In short: I am volunteering to maintain the Debian package (plus
> endless-sky-high-dpi) and this doesn't require that you do anything
> but produce the great game you already do :) Maybe answer
> a copyright/license question or respond to a bug report/patch from
> time to time, but that should be business as usual.
> 
> 
> Feel free to CC me for any questions/bugs/etc. (Is there a way to subscribe to
> emails
> from a specific package, or do I have to subscribe to the mailing list?)

There is. You need to register on , then 
go to  and press the 
'Subscribe' button. Same on 
. Alternatively you 
can subscribe using email only, see 


> 
> I looked at the patches you made, and we can upstream them easily, if that's
> fine by you.

Yes, but there is no rush. I will submit them as PRs on github 
eventually.
> Some of the fixes you made to the copyright file have actually 
> already been
> fixed upstream
> (but aren't in an actual release yet).

There are more (minor) problems with the copyright summary. I will 
create issues/PRs about them for easier tracking (one already created 
- #7711).


Best regards,
Damyan

Bug#1024540: transition: libpinyin

[Sebastian Ramacher]

On 2022-11-25 14:52:12 +0100, Gunnar Hjalmarsson wrote:
> On 2022-11-21 20:46, Sebastian Ramacher wrote:
> > On 2022-11-21 08:03:26 +0100, Gunnar Hjalmarsson wrote:
> > > Hello Release Team,
> > > 
> > > libpinyin upstream made a SOVERSION bump from 13 to 15, and the
> > > Debian packaging has been changed accordingly in libpinyin 2.7.92-1
> > > in experimental. These are the packages affected by the
> > > transition:
> > > 
> > >   fcitx-libpinyin
> > >   fcitx5-zhuyin
> > >   ibus-libpinyin
> > >   ibus-libzhuyin
> > >   maliit-keyboard
> > > 
> > > I have changed the sources as appropriate and successfully test
> > > built the packages against the new libpinyin.
> > > 
> > > As regards maliit-keyboard I plan to ping the maintainer (aka
> > > submit a bug) and possibly do an NMU. The other affected packages
> > > are maintained by Debian's IME team, and as a team member I plan to
> > > upload them myself.
> > > 
> > > The autogenerated ben tracker looks as expected:
> > > 
> > > https://release.debian.org/transitions/html/auto-libpinyin.html
> > > 
> > > Please consider libpinyin for transition.
> > 
> > Please go ahead after filing the bug against malitt-keyboard.
> 
> Both libpinyin and the reverse dependencies have built successfully in
> unstable on the official architectures, and the old library packages have
> been deleted.
> 
> I notice that libpinyin has not yet migrated, even though the 2 days delay
> is over. Is that because Britney waits for the dependencies to be migration
> ready too, or is it because this bug is not closed yet?

It has not migrated yet because the shared library packages have
strictly versioned dependency on libpinyin-data. Hence, migrating
libpinyin to testing would currently render some packages uninstallable
in testing.

Ideally, this dependency would be relaxed if possible so that this won't
be an issue for the next libpinyin transition. For this one, all the
reverse dependencies and libpinyin need to migrate together.

Cheers
-- 
Sebastian Ramacher

Bug#1024093: Just broke for me on upgrade as well

[James Bottomley]

mythtv still works fine, but google-chrome (used for streaming)
doesn't.  I'm still using pulseaudio with pipewire-pulse and what
pavucontrol shows me is google-chrome having difficulty connecting to
the audio output (keeps appearing and disappearing in the playback
tab).

Falling back to 0.3.58 fixes everything

Bug#955493: network-manager-fortisslvpn Debian updating and maintenance

[Andreas Henriksson]

Hello Patrice Duroux,

I'm looking over what Debian Maintainer Dashboard (DMD) says is my old
sins that I should fix up (before the upcoming freeze) and apparently
I was sponsoring uploads of nm-fortisslvpn which I did not remember.
Not sure if the current maintainer lost interest in poking me or
what happened. I know nowadays debian-mentors has a nice "new" workflow
of filing bugs for Request for Sponsorship (RFS), so hopefully if it was
me who dropped the ball that was tried instead of asking me directly.
Given there has been no followup on bug reports I assume it wasn't me.

On Sun, Oct 23, 2022 at 11:16:21AM +0200, Patrice Duroux wrote:
> Hi,
> In case that helps: 
> https://salsa.debian.org/Peutch-guest/network-manager-fortisslvpn

Thanks for your work on this! Would you by any chance consider taking
on the official Debian maintainer role for this package?
I would offer to review and sponsor your uploads, but you might also
want to get familiar with how to file an RFS in case I'm
busy/unavailable. Given upstream uses GNOME resources, I think people
on #debian-gnome (irc.debian.org / OFTC) would also lend you a helping
hand if you have any questions about packaging work.

I've already looked over the changes you posted above and it looks good
to me with a couple of nitpicks:
 * Please add `(Closes: #XYZ)` entries for the two open bug reports in
   the bug tracking system your changes fixes (Gtk4 + new upstream rel.).
 * Consider changing Vcs-* fields in debian/control to your fork
   and set yourself as Maintainer, mentioning that you're taking over.
   (If you do take Maintainer, remember to set packaging revision back
   to -1 and remove the Non-maintainer upload entry in the changelog.)
 * Please `dch -r` (UNRELEASED -> unstable) and `gbp tag && gbp push`

I know there's an official procedure to take over a package these days
which you might want to get familiar with here:
https://wiki.debian.org/PackageSalvaging

I hope your salvaging of the package is welcome by all parties and it
would be nice to get the package in a usable shape and migrated to
testing before the freeze.

If you're just interested in doing a single NMU I'd consider sponsoring
that as well!

Regards,
Andreas Henriksson

Bug#1024839: ITP: python3-setuptools-golang -- Build Python extensions written in Go

[Domenico Andreoli]

Package: wnpp
Severity: wishlist
Owner: Domenico Andreoli 
X-Debbugs-Cc: debian-de...@lists.debian.org
X-Debbugs-Cc: debian-pyt...@lists.debian.org

* Package name: python3-setuptools-golang
  Version : 2.7.0
  Upstream Author : Anthony Sottile 
* URL : https://github.com/asottile/setuptools-golang
* License : Expat License
  Programming Lang: Python
  Description : Build Python extensions written in Go

This is a plugin for setuptools, use it to build and package modules
written in Go as you do for regular Python modules and C extensions.


signature.asc
Description: PGP signature

Bug#1024838: ITP: wofi-pass -- pass support for wofi using wtype

[Martin Dosch]

Package: wnpp
Severity: wishlist
Owner: Martin Dosch 

* Package name: wofi-pass
  Version : 0.0~git20221028.869c545-1
  Upstream Author : https://github.com/TinfoilSubmarine
* URL : https://github.com/TinfoilSubmarine/wofi-pass
  License : GPL-2
  Programming Lang: sh
  Description : pass support for wofi using wtype

 A script using wofi and wtype to provide a completely Wayland-native
 way to conveniently use pass.
 It provides the same search that passmenu does, but shows a second
 dialogue that lets the user choose which field to copy/print.




signature.asc
Description: PGP signature

Bug#1024837: lokalize: Issues displaying po files

[Silvério Santos]

Package: lokalize
Version: 4:21.12.3-1
Severity: important

Dear Maintainer,

After opening a po file through File, Open or from a project there are issues
in the surface's behavior, mainly in refreshing content:
- only the translation list's upper half (or less, also cut a part of the line)
is updated when scrolling,
- msgid and msgstr are changed only with a few seconds of delay
  - after selection in the translation list
  - or when editing,
- the cursor is not appearing at all, although text input is accepted when
typing

Sometimes it helps moving the mouse pointer over the msgid or msgstr areas to
get its content updated.

Other tabs are not affected, only opened po files.

When starting Lokalize from the command line, to get informative output,
without parameters or with the platform parameter option working best:

`lokalize -platform wayland`

the following is shown:

QSocketNotifier: Can only be used with threads started with QThread
QStatusBar::insertWidget: Index out of range (5), appending widget
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
org.kde.lokalize: db "default140654407579328" opened 6 "de_DE"
org.kde.lokalize: db "ggi-de140654407579328" opened 19 "de"
org.kde.lokalize: db "Übersetzungen140654407579328" opened 0 "pt"
org.kde.lokalize: db "Public code140654407579328" opened 0 "de_DE"
org.kde.lokalize: db "Downloads140654407579328" opened 0 "pt"
org.kde.lokalize: db "silverio-source140654407579328" opened 0 "de_DE"
org.kde.lokalize: db "publiccode-de140654407579328" opened 1 "de"
org.kde.lokalize: db "publiccode-pt140654407579328" opened 0 "pt"
org.kde.lokalize: db "en_US-pt140654407579328" opened 1 "pt"
org.kde.lokalize: db "Uebersetzungen140654407579328" opened 0 "de_DE"
org.kde.lokalize: db "Übersetzungen-debian-handbook-de140654407579328" opened 0
"de"
org.kde.lokalize: db "en_US-de140654407579328" opened 0 "de"
org.kde.lokalize: db "Standard140654407579328" opened 0 "de_DE"
org.kde.lokalize: db "publicode140654407579328" opened 0 "de"
org.kde.lokalize: db "home-silverio140654407579328" opened 0 "de"
org.kde.lokalize: db "ggi-pt140654407579328" opened 0 "pt"
org.kde.lokalize: alt trans file doesn't exist:
"handbook/translations/de/content/54_activity_43.po"
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
org.kde.lokalize: indexed
"handbook/translations/de/po_files/content/54_activity_43.po" for word
completion in 0 msecs


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

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

Versions of packages lokalize depends on:
ii  kio5.100.0-2
ii  libc6  2.36-5
ii  libhunspell-1.7-0  1.7.1-1
ii  libkf5completion5  5.100.0-1
ii  libkf5configcore5  5.100.1-1
ii  libkf5configgui5   5.100.1-1
ii  libkf5configwidgets5   5.100.0-1
ii  libkf5coreaddons5  5.100.0-1
ii  libkf5crash5   5.100.0-1
ii  libkf5dbusaddons5  5.100.0-1
ii  libkf5i18n55.100.0-1
ii  libkf5itemviews5   5.100.0-1
ii  libkf5kiocore5 5.100.0-2
ii  libkf5kiofilewidgets5  5.100.0-2
ii  libkf5kiowidgets5  5.100.0-2
ii  libkf5notifications5   5.100.0-1
ii  libkf5sonnetcore5  5.100.0-1
ii  libkf5sonnetui55.100.0-1
ii  libkf5textwidgets5 5.100.0-1
ii  libkf5widgetsaddons5   5.100.0-2
ii  libkf5xmlgui5  5.100.0-1
ii  libqt5core5a   5.15.6+dfsg-2+b1
ii  libqt5dbus55.15.6+dfsg-2+b1
ii  libqt5gui5 5.15.6+dfsg-2+b1
ii  libqt5network5 5.15.6+dfsg-2+b1
ii  libqt5sql5 5.15.6+dfsg-2+b1
ii  libqt5sql5-sqlite  5.15.6+dfsg-2+b1
ii  libqt5widgets5 5.15.6+dfsg-2+b1
ii  libqt5xml5 5.15.6+dfsg-2+b1
ii  libstdc++6 12.2.0-9

Versions of packages lokalize recommends:
ii  gettext0.21-10
ii  sonnet-plugins 5.100.0-1
ii  translate-toolkit  3.7.4-1

Versions of packages lokalize suggests:
ii  khelpcenter  4:22.04.1-1
pn  poxml

-- debconf-show failed

Bug#977739: progress of golang-github-texttheater-golang-levenshtein packaging

[陳昌倬]

On Thu, Nov 24, 2022 at 07:51:44AM +0100, Cyril Brulebois wrote:
> ChangZhuo Chen  (2022-06-26):
> This ITP has been opened close to two years ago, and we haven't heard
> back in the last 5 months about possible progress. Since the packaging
> is rather straightforward, I'm tempted to “steal” this ITP and just
> upload the package I've prepared locally (required for crowdsec 1.4.2).
> 
> 
> ChangZhuo Chen, I see you have created a repository on Salsa[1], but the
> debian/sid branch doesn't contain any debian/ directory at this point,
> do I have your permission to push my work in this repository, force
> pushing if required?

No problem. Please “steal” this ITP.

> 
>  1. 
> https://salsa.debian.org/go-team/packages/golang-github-texttheater-golang-levenshtein/-/tree/debian/sid/
> 
> 
> Cheers,
> -- 
> Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#1024480: libvncserver 0.9.13+dfsg-2+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1024480 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: libvncserver
Version: 0.9.13+dfsg-2+deb11u1

Explanation: fix memory leak [CVE-2020-29260]; support larger screen sizes

Bug#1024385: openvpn-auth-radius 2.1-7+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1024385 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: openvpn-auth-radius
Version: 2.1-7+deb11u1

Explanation: support verify-client-cert directive

Bug#1023602: xfig 3.2.8-3+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1023602 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: xfig
Version: 3.2.8-3+deb11u1

Explanation: fix buffer overflow issue [CVE-2021-40241]

Bug#1023798: node-loader-utils 2.0.0-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1023798 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: node-loader-utils
Version: 2.0.0-1+deb11u1

Explanation: fix prototype pollution issue [CVE-2022-37599 CVE-2022-37601], 
regular expression-based denial of service issue [CVE-2022-37603]

Bug#1023423: pysubnettree 0.33-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1023423 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: pysubnettree
Version: 0.33-1+deb11u1

Explanation: fix module build

Bug#1023263: clickhouse 18.16.1+ds-7.2+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1023263 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: clickhouse
Version: 18.16.1+ds-7.2+deb11u1

Explanation: fix out-of-bounds read issues [CVE-2021-42387 CVE-2021-42388], 
buffer overflow issues [CVE-2021-43304 CVE-2021-43305]

Bug#1023261: libtasn1-6 4.16.0-2+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1023261 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: libtasn1-6
Version: 4.16.0-2+deb11u1

Explanation: fix out-of-bounds read issue [CVE-2021-46848]

Bug#1023105: tinyxml 2.6.2-4+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1023105 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: tinyxml
Version: 2.6.2-4+deb11u1

Explanation: fix infinite loop [CVE-2021-42260]

Bug#1022307: python3-biopython: incompatible with muscle >= 5

[Étienne Mollier]

Control: severity 1022307 normal

Hi Andreas,

Andreas Tille, on 2022-11-25:
> Am Thu, Nov 24, 2022 at 10:35:06PM +0100 schrieb Étienne Mollier:
> > 
> > python-biopython 1.80 is uploaded to experimental and should
> > build soon[1], if this is not the case already.  I haven't had a
> > lot of opportunities to extensively test interactions between
> > muscle3 and 5; I guess the situation will be clearer when
> > muscle3 makes it through NEW.  It would be nice that people
> > using biopython and muscle give this a try as early as possible.
> 
> Thanks a lot for this.
> 
> I've just reverted the version of t-coffee and have uploaded
> t-coffee_13.45.0.4846264+really13.41.0.28bdc39+dfsg-1 - not proud about
> this name, but well, it should do the trick without an epoch. 
> 
> Hope this will settle the situation with biopython soonish.

Thanks, this should reduce the noise on the t_coffee front.
Since python-biopython 1.79 doesn't fail to build from source
anymore, I reduce the severity already.  I don't close just yet
to avoid forgetting to bring back t-coffee in the build time
test dependencies when migrating biopython 1.80 to unstable.
There is also a FIXME item related to muscle3 support, that can
be brought back once muscle3 passes through the NEW queue.

Speaking of biopython 1.80, pseudo-excuses are looking good[1].
I fixed the autopkgtest regression in python-faidx yesterday.
When trying to rebuild reverse dependencies, I also noted an
issue in python-pauvre[2], which I forwarded upstream, since it
didn't look easy to fix on first sight.  Once sorted, I suppose
it would be feasible to upgrade biopython 1.80 in unstable.

[1]: https://qa.debian.org/excuses.php?experimental=1=python-biopython
[2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024835

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/3, please excuse my verbosity.
On air: Chicago - Make Me Smile


signature.asc
Description: PGP signature

Bug#1022122: node-minimatch 3.0.4+~3.0.3-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1022122 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: node-minimatch
Version: 3.0.4+~3.0.3-1+deb11u1

Explanation: improve protection against regular expression-based denial of 
service [CVE-2022-3517]

Bug#1021963: dcfldd 1.7-3+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1021963 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: dcfldd
Version: 1.7-3+deb11u1

Explanation: fix SHA1 output on big-endian architectures

Bug#1021838: binfmt-support 2.2.1-1+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1021838 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: binfmt-support
Version: 2.2.1-1+deb11u1

Explanation: run binfmt-support.service after systemd-binfmt.service

Bug#1021645: postfix 3.5.17-0+deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1021645 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: postfix
Version: 3.5.17-0+deb11u1

Explanation: new upstream stable release

Bug#1024835: [Debian-med-packaging] Bug#1024835: python-pauvre: ftbfs with biopython 1.80

[Étienne Mollier]

Control: forwarded -1 https://github.com/conchoecia/pauvre/issues/45

I informed python-pauvre upstream.  Replacing Bio.SubsMat usage
doesn't look necessary easy to fix on first sight, but I haven't
had a in depth look to this yet.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/3, please excuse my verbosity.
On air: Jonas Lindberg & The Other Side - Leaving The World Beh…


signature.asc
Description: PGP signature

Bug#1024836: tootle is archived and replaced by tooth

[Praveen Arimbrathodiyil]

Package: tootle

Looks like tooth [1] has replaced now archived tootle

[1] https://github.com/GeopJr/Tooth

I think we should switch to this fork. May be forking the packaging and 
updating watch file and replacing package names is best way and tooth 
can provide tootle for a smooth upgrade experience.


If you are okay with the idea, I can help with packaging.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#834724: Wyświetl mój profil w Mapach Google

[Rafal Franczak]

Google





Rafal Franczak


Rafal Franczak

Udostępniam Ci swój profil






Zobacz w Mapach Google




Google

© 2018 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043

Wysłane przez: Rafal Franczak w Mapach Google

Bug#989361: netcdf-parallel: Multiple security issues in ezxml

[Philip Rinn]

Hi,

as netcdf-parallel doesn't use the bundled copy of ezxml anymore, but links 
against libxml2 since 1:4.9.0-1, I guess it's not _that_ relevant.


Should this bug just be marked as fixed in 1:4.9.0-1?

Best regards
Philip


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1024395: The mokutil --list-enrolled is due to kernel config or version

[Eric Valette]

I tested with 6.0.0-4-amd kernel version, and there mokutil 
--list-enrolled works.


So either it is a missing config item in my own generated kernel (what 
is needed beside all *EFI* config items, something in keyring or crypto 
algo?) or a kernel incompatibilty (5.10.155).


But that has nothing to do with the grub bug it is just for the sake of 
completeness


-- eric

Bug#1024835: python-pauvre: ftbfs with biopython 1.80

[Étienne Mollier]

Source: python-pauvre
Version: 0.2.3-1
Severity: important
Tags: ftbfs

Dear Maintainer,

python-pauvre fails its build time test suite when built against
biopython 1.80 in experimental but builds successfully against
biopython 1.79.  The relevant part of the log in case of failure
shows:

I: pybuild base:240: cd 
/<>/.pybuild/cpython3_3.10_pauvre/build; python3.10 -m unittest 
discover -v 
test_normal_plotting_scenario 
(pauvre.tests.test_synplot.libSeq_test_case)
This verifies that the LibSeq class is constructed with all of the ... 
+ export PYTHONPATH=/<>/.pybuild/cpython3_3.10_pauvre/build
+ PYTHONPATH=/<>/.pybuild/cpython3_3.10_pauvre/build
+ exec python3 
/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/pauvre_main.py 
synplot --aln_dir 
/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/tests/testdata/alignments/
 --fileform pdf --gff_paths 
/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/tests/testdata/gff_files/Bf201706.gff
 
/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/tests/testdata/gff_files/JN392469.gff
 
/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/tests/testdata/gff_files/NC016117.gff
 --center_on COX1 --gff_labels 'B. forskalii' 'P. bachei' 'M. leidyi'
Traceback (most recent call last):
  File 
"/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/pauvre_main.py", 
line 636, in 
main()
  File 
"/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/pauvre_main.py", 
line 630, in main
args.func(parser, args)
  File 
"/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/pauvre_main.py", 
line 62, in run_subtool
import pauvre.synplot as submodule
  File 
"/<>/.pybuild/cpython3_3.10_pauvre/build/pauvre/synplot.py", line 
46, in 
import Bio.SubsMat.MatrixInfo as MI
ModuleNotFoundError: No module named 'Bio.SubsMat'

Have a nice day,  :)
Étienne.

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

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


signature.asc
Description: PGP signature

Bug#1024160: adding lib version

[graeme vetterlein]

I realised I did not include the library name and version

in the base text of my original report (it was in links) I keep

checking my version against the "broken" version , so I end up having to

follow links :-(


So the failing version is :


|libwnck-3-0:amd64 43.0-2|

Bug#1024834: dia: Properties dialog is grapically currupted

[waxhead]

Package: dia
Version: 0.97.3+git20220525-4
Severity: normal
X-Debbugs-Cc: waxh...@dirtcellar.net

Dear Maintainer,


   * What led up to the situation?

I tried to create a diagram. Inserting a 42U rack.
then I accessed the properties via the RMB.
The properties dialog is grapically corrupted, the corruption changes when I 
resize the dialog.
the corruption is that widgets are sometimes not/or less visible. Sometimes 
partly overdrawn.
Hovering the mouse over a widget make it show up again.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I tried to update via aptitude. Also tried to change themes without effect.
Other than that I did nothing.

   * What was the outcome of this action?

No improvement.

   * What outcome did you expect instead?

Not much to be honest ;) Hope this will be fixed!



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

Kernel: Linux 6.0.0-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=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dia depends on:
ii  dia-common   0.97.3+git20220525-4
ii  gir1.2-gtk-2.0   2.24.33-2
ii  libc62.36-5
ii  libcairo21.16.0-6
ii  libgcc-s112.2.0-9
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libglib2.0-0 2.74.1-2
ii  libgraphene-1.0-01.10.8-1
ii  libgtk2.0-0  2.24.33-2
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libpoppler12322.08.0-2.1
ii  libpython3.103.10.8-3
ii  libstdc++6   12.2.0-9
ii  libxml2  2.9.14+dfsg-1.1+b2
ii  zlib1g   1:1.2.11.dfsg-4.1

Versions of packages dia recommends:
ii  dia-shapes0.6.0-5
ii  fonts-urw-base35  20200910-6

dia suggests no packages.

-- no debconf information

Bug#1024780: msxpertsuite: FTBFS with new qcustomplot

[Filippo Rusconi]

Greetings, 


On Thu, Nov 24, 2022 at 09:06:31PM +0100, Sebastian Ramacher wrote:

Source: msxpertsuite
Version: 5.8.9-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


Yes, that was expected but I am planning to write to FTPMasters to remove that
package since it is now fully superseded by the two massxpert/minexpert2
packages. 


I'll do that. Tank you for your *hardwork* on our distribution!

Sincerely,
Filippo

--

⢀⣴⠾⠻⢶⣦⠀  Filippo Rusconi, PhD
⣾⠁⢠⠒⠀⣿⡁   Research scientist at CNRS
⢿⡄⠘⠷⠚⠋⠀   Debian Developer
⠈⠳⣄  http://msxpertsuite.org
  http://www.debian.org

Bug#1024833: python3-bleach: add a Recommends: python3-tinycss2

[Denis Laxalde]

Package: python3-bleach
Version: 3.2.1-2.1
Severity: normal

Dear Maintainer,

Since version 5, bleach has an optional dependency on tinycss2 (through
the setuptools extra 'css') for CSS sanitization:

  
https://github.com/mozilla/bleach/commit/cb6dca73d0d15f8c26acb28e7cc53482526bbe1b#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7

>>> import bleach
>>> bleach.__version__
'5.0.0'
>>> import bleach.css_sanitizer
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/bleach/css_sanitizer.py", line 1, in 

import tinycss2
ModuleNotFoundError: No module named 'tinycss2'

Maybe a "Recommends: python3-tinycss2" could be added?

Thanks for considering,
Denis

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

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

Versions of packages python3-bleach depends on:
ii  python3   3.9.2-3
ii  python3-html5lib  1.1-3
ii  python3-packaging 20.9-2
ii  python3-six   1.16.0-2
ii  python3-webencodings  0.5.1-2

python3-bleach recommends no packages.

Versions of packages python3-bleach suggests:
pn  python-bleach-doc  

-- no debconf information

Bug#1024278: libgssglue: autopkgtest failure with pkgconf

[Simon Josefsson]

Thanks, I have reported this to pkgconf upstream:

https://github.com/pkgconf/pkgconf/issues/278

/Simon


signature.asc
Description: PGP signature

Bug#1024831: xorg: xserver fails to resume after suspend-to-disk

[Klaus Singvogel]

Package: xorg
Version: 1:7.7+22
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

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

   * What led up to the situation?
 Suspend-to-disk, resume and the screen keeps been blank
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 - acpitool -S
 - switch PC on
 - but ssh is working
   * What was the outcome of this action?
 The monitors keep being blank, they try to go into sleep mode, as
 they find no signal
   * What outcome did you expect instead?
 I want to see the old content on the monitor

 In the logfile Xorg.0.log I noticed many times the log message (but:
 (WW) AMDGPU(0): get vblank counter failed: Invalid argument

 Don't know, if related, but noticed this only after my Debian stable
 (bullseye) switched to linux kernel version 6.0.0:
 linux-image-6.0.0-0.deb11.2-amd64

 suspend-to-ram is not affected, the wake up there is still working as
 expected.

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


-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Cezanne [1002:1638] (rev c8)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 0

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 6.0.0-0.deb11.2-amd64 (debian-ker...@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 
SMP PREEMPT_DYNAMIC Debian 6.0.3-1~bpo11+1 (2022-10-29)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 20794 Dec 12  2021 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 60759 Nov 26 09:37 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[40.971] 
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[40.971] Build Operating System: linux Debian
[40.971] Current Operating System: Linux dipper 6.0.0-0.deb11.2-amd64 #1 
SMP PREEMPT_DYNAMIC Debian 6.0.3-1~bpo11+1 (2022-10-29) x86_64
[40.971] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-6.0.0-0.deb11.2-amd64 
root=UUID=ca445dcc-b878-4c62-939b-e40721fa00a0 ro quiet
[40.971] Build Date: 11 November 2022  12:37:52PM
[40.971] xorg-server 2:1.20.11-1+deb11u3 (https://www.debian.org/support) 
[40.971] Current version of pixman: 0.40.0
[40.971]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[40.971] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[40.971] (==) Log file: "/var/log/Xorg.0.log", Time: Sat Nov 26 09:36:55 
2022
[40.971] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[40.972] (==) No Layout section.  Using the first Screen section.
[40.972] (==) No screen section available. Using defaults.
[40.972] (**) |-->Screen "Default Screen Section" (0)
[40.972] (**) |   |-->Monitor ""
[40.972] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[40.972] (==) Automatically adding devices
[40.972] (==) Automatically enabling devices
[40.972] (==) Automatically adding GPU devices
[40.972] (==) Max clients allowed: 256, resource mask: 0x1f
[40.973] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[40.973]Entry deleted from font path.
[40.974] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[40.974] (==) ModulePath set to "/usr/lib/xorg/modules"
[40.974] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[40.974] (II) Loader magic: 0x55fd3c1e0e40
[40.974] (II) Module ABI versions:
[40.974]X.Org ANSI C Emulation: 0.4
[40.974]X.Org Video Driver: 24.1
[40.974]X.Org XInput driver : 24.1
[40.974]X.Org Server Extension : 10.0
[40.974] (++) using VT number 7

[40.974] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[40.975] (II) xfree86: Adding drm device (/dev/dri/card0)
[40.999] 

Bug#966101: hachoir/parser/misc/pdf.py:395: SyntaxWarning: 'str' object is not callable; perhaps you missed a comma?

[Jakub Wilk]

Control: tags -1 + fixed-upstream

* Paul Wise , 2020-07-23 11:03:

/usr/lib/python3/dist-packages/hachoir/parser/misc/pdf.py:395: SyntaxWarning: 
'str' object is not callable; perhaps you missed a comma?


This was fixed upstream in 3.1.2:
https://github.com/vstinner/hachoir/commit/fa5fc556066851d2

--
Jakub Wilk

Bug#1024699: [Pkg-utopia-maintainers] Bug#1024699: Bug#1024699: volume-key: Testsuite error on local rebuild

[Michael Biebl]

Control: reassign -1 libgpgme11

Am 26.11.22 um 08:53 schrieb Michael Biebl:

Am 26.11.22 um 07:47 schrieb Andreas Metzler:

Control: tags: -1 - moreinfo - unreproducible

On 2022-11-24 Michael Biebl  wrote:

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



Am 23.11.22 um 13:18 schrieb Andreas Metzler:

Source: volume-key
Version: 0.3.12-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in 
the past)

Hello,
volume-key FTBFS on current sid:
FAIL: packet_roundtrips.sh



Please provide instructions how this issue can be reproduced


Good morning Michael,

I see this in a straightforward rebuild on up-to-date sid chroot.

(sid)ametzler@argenau:/tmp$ rm -rf /tmp/VOL ; mkdir /tmp/VOL ; cd 
/tmp/VOL ; apt source volume-key ; cd volume-key-0.3.12

[...]
(sid)ametzler@argenau:/tmp/VOL/volume-key-0.3.12$ dpkg-buildpackage 
-uc -us -B

[...]
make[5]: Entering directory '/tmp/volume-key-0.3.12/tests'
FAIL: packet_roundtrips.sh
[...]


Looking at the buildlog we find:
GPGME 20221123T121533 13EBF  _gpgme_io_read: enter: fd=8 
buffer=0x7fff89fd5cf0 count=4096
GPGME 20221123T121533 13EBF  _gpgme_io_read: check: gpg: error 
running '/usr/bin/gpg-agent': probabl
GPGME 20221123T121533 13EBF  _gpgme_io_read: check: y not 
installed
GPGME 20221123T121533 13EBF  _gpgme_io_read: check: gpg: failed to 
start agent '/usr/bin/gpg-agent':


And indeed manually installing gpg-agent lets the testsuite succeed.

cu Andreas




Interesting, gpg-agent is automatically in the build chroot because of 
the libgpgme-dev Build-Depends it seems:


# aptitude why gpg-agent
i   libgpgme-dev Depends libgpgme11 (= 1.18.0-3)
i A libgpgme11   Depends gnupg (>= 2.1.21-4) | gpg
i A gnupg    Depends gpg-agent (< 2.2.40-1.1~)

See attached build log

That said, this sounds more like a libgpgme11 issue. If it strictly 
requires gpg-agent, then it should probably ensure that it's installed.

It's not volume-key which spawns gpg-agent after all.


reassigning accordingly.



OpenPGP_signature
Description: OpenPGP digital signature