date:20230403


Source: ruby-rails-assets-blueimp-gallery
Version: 2.33.0-2
Severity: serious
Control: tags -1 bookworm-ignore sid bookworm trixie
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since November 
2021. Can you please investigate the situation and fix it? I copied some 
of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-rails-assets-blueimp-gallery/32420362/log.gz



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033913: partman-auto-lvm: Broken "Guided - use entire disk and set up LVM" in UEFI mode

2023-04-03 Thread Cyril Brulebois

Package: partman-auto-lvm
Version: 87
Severity: serious
Justification: Maintainer says so

TL;DR: Answering “Yes” to the “Force UEFI installation?” makes sure the
installer pulls the right bootloader packages, despite misreading the
situation.

I've discovered this while testing D-I Bookworm RC 1 but also confirmed
it already existed in D-I Bookworm Alpha 2, and I'm therefore filing it
against the version found in the previous release (and deciding not to
block the Bookworm RC 1 release on it).



For baremetal tests on laptops requiring various firmware packages, I've
been using guided partitioning since forever, with one of these:
 - Guided - use entire disk
 - Guided - use entire disk and set up encrypted LVM

The former is used most of the time since it's slightly faster (fewer
prompts), while the latter is only used once in a while, to make sure a
“real” laptop-oriented install works fine (since every laptop should be
encrypted in my opinion).

Since I had just tested “Guided - use entire disk” in a virtual machine,
I decided to pick this instead when switching to the first laptop
(Asus Vivobook S14/S15 but that's very likely not a factor):
 - Guided - use entire disk and set up LVM

And… *WOW!*

The first surprise is this prompt:

Force UEFI installation?

This machine's firmware has started the installer in UEFI mode but
it looks like there may be existing operating systems already
installed using "BIOS compatibility mode". If you continue to
install Debian in UEFI mode, it might be difficult to reboot the
machine into any BIOS-mode operating systems later.

If you wish to install in UEFI mode and don't care about keeping the
ability to boot one of the existing systems, you have the option to
force that here. If you wish to keep the option to boot an existing
operating system, you should choose NOT to force UEFI installation
here.

which defaults to No.

That's very surprising since the only operating system prior to the
installation was a Debian system, which was getting entirely erased (due
to using the full disk), and was installed in UEFI mode anyway.

I went for the default choice, since we expect the installer to make
smart suggestions, and unsuspecting users shouldn't have to know better.

That means we end up with installing grub-pc instead of grub-efi-amd64
and shim, being prompted where to install GRUB, and of course when it's
time to reboot, the UEFI firmware rightfully refuses to boot anything
since there's absolutely no signature whatsoever, which isn't a great
idea under Secure Boot:

Secure Boot Violation

Invalid signature detected. Check Secure Boot Policy in Setup.


Some additional info:
 - As mentioned in TL;DR, this can be worked around by answering Yes to
   “Force UEFI installation?”.
 - It doesn't seem to be dependent on possible traces of an existing
   system prior to the installation: Debian installed on the entire disk
   or with encrypted LVM on the entire disk doesn't seem to make a
   difference. Starting with a wiped disk (writing ~ 2 GB worth of
   zeros at the beginning of the disk) doesn't make a difference either.
 - It very much looks like the intermediary states are slightly
   different when setting up LVM and when setting up encrypted LVM, and
   the LVM case case leads to some confusion in partman-efi's
   /lib/partman/init.d/50efi (which logs to /var/log/partman rather than
   to /var/log/syslog): “Found 0 ESPs, 3 non-ESPs”.
 - I'm filing this issue against partman-auto-lvm though, for
   discoverability purposes.


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

Bug#1033845: u-boot fails to boot on pinebook pro if installed on internal emmc

2023-04-03 Thread Vagrant Cascadian

On 2023-04-03, Wolf wrote:
>> Control: severity 1033845 important
>> 
>> Given that this only affects a single platform, and there are other
>> tested working boot options for this platform, I am downgrading the
>> severity to important.
>
> So far ok if you consider it so.
>
> Actually I thought 'severity' because more or less you brick it if you 
> install on the
> internal emmc due to the boot selection and you have to recover with 
> screwdriver, DIP
> switching off the internal emmc, booting from the microSD and stopping at the 
> u-boot
> prompt, DIP switching on the internal emmc and rescanning the mmc's to be 
> able to boot.

I had not extensively considered that angle...

>> So far I have only ever tested booting from microSD...
>
> Yes, that works, as long as nothing bad is installed on the internal emmc or 
> SPL.

Did you mean SPI? At any rate, yeah, from what I recall the boot order
defined in rom for most rockchip systems is SPI, eMMC, microSD
... (basically from the least removable to the most removable)

>> Did this work on previous versions?
>
> Not with the Debian u-boot package, because I could boot Debian with the 
> pre-installed and
> I just recently upgraded the u-boot, because I wanted the u-boot prompt on 
> LCD.

Ok, so it is not a regression.

>> Does it work on the version in experimental (currently 2023.04~rc5*)?
>
> No, it does not:
> pinebook-pro-rk3399_defconfig of 2023.04~rc5:
> # CONFIG_SPL_MTD_SUPPORT is not set
> # CONFIG_MMC_HS200_SUPPORT is not set
> # CONFIG_SPL_MMC_HS200_SUPPORT is not set

Yeah, I figured that it wouldn't, but sometimes settings change or get
renamed or fixed in some other way. Nevertheless, worth trying.

> However, the SPL settings are just precaution, because I have the intention 
> to try again
> installing u-boot in SPL if I find time enough to do so, also for 
> brick/recover actions.

SPI?

>> Would you consider submitting a patch upstream?
>
> Sure, I can do so however, I was reading that a bug report should be always
> done to the distribution.

As a simple rule, sure, but it is always a judgement call. I do not
think we are patching anything hugely relevent in the Debian packaging
here (slight chance the rockchip USB related patches are relevent, but I
would guess very slight).

> Anyway, should I then report in general u-boot related bugs with patches 
> upstream?

If you are up to it, that can be helpful as it will eventually land in
Debian (and other distros) that way.

It can still be useful to file a bug with Debian in case it make sense
to backport a patch from upstream, too. This way we can track when the
issue is resolved.

So, in some cases, file bugs/patches/etc in both. :)

> Because there is another bug screwing up the LCD on reboot or just a reset 
> command
> from u-boot prompt and if I have time enough I might hunt it.

I have never had reboot work reliably on the pinebook-pro...

Thanks for poking at all this!

live well,
  vagrant

signature.asc
Description: PGP signature

Bug#1033912: ruby-maven-libs: autopkgtest regression: output on stderr


Source: ruby-maven-libs
Version: 3.3.9+ds-3
Severity: serious
Control: tags -1 bookworm-ignore sid bookworm trixie
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since 
September 2022. Can you please investigate the situation and fix it? I 
copied some of the output at the bottom of this report. The test itself 
passes, but it prints on stderr. That is considered failure by 
autopkgtest unless the allow-stderr restriction is declared. (My 
copy/paste seems to be missing a character).


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-maven-libs/32101863/log.gz

autopkgtest [21:15:34]: test command1: ruby -e "require 'maven'"
autopkgtest [21:15:34]: test command1: [---
[0mautopkgtest [21:15:35]: test command1: ---]
autopkgtest [21:15:35]: test command1:  - - - - - - - - - - results - - 
- - - - - - - -

command1 FAIL stderr: [0m


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033524: Simplify the instructions for making bootable media

2023-04-03 Thread Holger Wansing

Hi,

Holger Wansing  wrote (Mon, 3 Apr 2023 21:16:41 +0200): 
> Holger Wansing  wrote (Sat, 1 Apr 2023 20:52:08 +0200):
> > I have added such wiki page under
> > https://wiki.debian.org/DebianInstaller/CreateUSBMedia
> > and overworked my patch a bit, to include a link to this page (amongst 
> > some more minor things).
> > 
> > I will apply it shortly, if noone objects.
> 
> Applied.

FYI: I have also removed the chapter for booting the installer from Windows
(spotted just today), since win32-loader support has been removed from the 
installer as well.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1033714: at runtime, flanker tries to create files under /usr

2023-04-03 Thread Andrey Rakhmatullin

On Thu, Mar 30, 2023 at 12:33:48PM -0700, Daniel Kauffman wrote:
> > Couldn't create 'flanker.addresslib._parser.mailbox_parsetab'. [Errno
> > 13] Permission denied: 
> > '/usr/lib/python3/dist-packages/flanker/addresslib/_parser/mailbox_parsetab.py'
Seems to be explained in https://github.com/ivelum/djangoql/issues/53
(which is about a different project):

> it is created/modified by PLY, the library that is used internally for
> language parsing. This file is updated automatically if you're using a
> different version of the library than the one with which the file was
> created originally. However, even if it fails to update it, it should
> still be working.

Bug#1033676: unblock: xen/4.17.0+74-g3eac216e6e-1

2023-04-03 Thread Maximilian Engelhardt

Control: retitle -1 unblock: xen/4.17.0+74-g3eac216e6e-1

On Sonntag, 2. April 2023 21:51:11 CEST Sebastian Ramacher wrote:
> On 2023-03-29 23:27:11 +0200, Maximilian Engelhardt wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: unblock
> > X-Debbugs-Cc: x...@packages.debian.org, m...@daemonizer.de,
> > t...@security.debian.org Control: affects -1 + src:xen
> > 
> > Please approve an upload of xen to unstable and later unblock package
> > xen. See the "Other info" section below on why this is a pre-approval
> > request.
> 
> Please go ahead
> 
> Cheers

Thanks, xen/4.17.0+74-g3eac216e6e-1 has been uploaded to unstable and already 
built on all architectures.

> > [ Reason ]
> > Xen in bookworm (and unstable) is currently affected by CVE-2022-42331,
> > CVE-2022-42332, CVE-2022-42333 and CVE-2022-42334 (see #1033297).
> > 
> > [ Impact ]
> > The above mentioned CVEs are not fixed.
> > 
> > [ Tests ]
> > The Debian package is based only on upstream commits that have passed
> > the upstream automated tests.
> > The Debian package has been successfully tested by the xen packaging
> > team on their test machines.
> > 
> > [ Risks ]
> > There could be upstream changes unrelated to the above mentioned
> > security fixes that cause regressions. However upstream has an automated
> > testing machinery (osstest) that only allows a commit in the upstream
> > stable branch if all test pass.
> > 
> > [ 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 testing
> > 
> > [ Other info ]
> > This security fix is based on the latest upstream stable-4.17 branch.
> > The branch in general only accepts bug fixes and does not allow new
> > features, so the changes there are mainly security and other bug fixes.
> > This does not exactly follow the "only targeted fixes" release policy,
> > so we are asking for a pre-approval.
> > The package we have prepared is exactly what we would have done as a
> > security update in a stable release, what we have historically done
> > together with the security team and are planning to continue to do.
> > As upstream does extensive automated testing on their stable branches
> > chances for unnoticed regressions are low. We believe this way the risk
> > for bugs is lower than trying to manually pick and adjust patches
> > without all the deep knowledge that upstream has. This approach is
> > similar to what the linux package is doing.
> > 
> > unblock xen/4.17.0+74-g3eac216e6e-1
> > 
> > Thanks
> > 


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

Bug#1033911: please enable the experimental Xtensa backend in LLVM and Clang 16+

2023-04-03 Thread John Scott

Source: llvm-toolchain-16
Version: 1:16.0.0-1~exp5
Severity: normal
X-Debbugs-Cc: debian-ker...@lists.debian.org
Control: affects -1 src:open-ath9k-htc-firmware

Please enable the experimental Xtensa backend in LLVM 16 and newer and
make a new upload to experimental.

A lot of prominent firmware, including free firmware such as my open-
ath9k-htc-firmware package, requires an Xtensa cross toolchain. Using
GCC is a pain because the compiler has to be custom-tailored to the
target, and in ath9k_htc we do this with patches that inevitably get
out-of-date.

We are taking a bold step by enabling a backend deemed experimental, but
it's necessary to advance free software.

This will also be helpful should anyone wish to build Intel's open sound
firmware too (although on most machines that enforces a digital
signature check to my understanding).

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

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



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

Bug#1033910: ruby-kakasi-ffi: autopkgtest regression: Could not find 'kakasi' (>= 0)


Source: ruby-kakasi-ffi
Version: 1.0.2-3
Severity: serious
Control: tags -1 bookworm-ignore sid bookworm trixie
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since March 
2023. Can you please investigate the situation and fix it? I copied some 
of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-kakasi-ffi/32098115/log.gz

GEM_PATH= ruby3.1 -e gem\ \"kakasi\"
/usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:311:in `to_specs': 
Could not find 'kakasi' (>= 0) among 91 total gem(s) (Gem::MissingSpecError)
Checked in 
'GEM_PATH=/home/debci/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' 
, execute `gem env` for more information

from /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:323:in `to_spec'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:62:in 
`gem'
from -e:1:in `'


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033909: apt: [INTL:nl] Dutch translation for the apt package

 
 
Package: apt 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch po file for the apt package. 
A draft has been posted to the debian-l10n-dutch mailing list allowing for
review. 
Please add it to your next package revision. 
It should be put as "po/nl.po" in your package build tree. 
 

-- 
Kind regards,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1033908: ruby-font-awesome-rails: autopkgtest regression: Don't know how to build task 'assets:precompile'

Source: ruby-font-awesome-rails
Version: 4.7.0.7-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails since November
2021 in unstable/testing. Can you please investigate the situation and
fix it? I copied some of the output at the bottom of this report.

The release team has announced [1] that failing autopkgtest on amd64 and
arm64 are considered RC in testing. [Release Team member hat on] Because
we're currently in the hard freeze for bookworm, I have marked this bug
as bookworm-ignore. Targeted fixes are still welcome.

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

Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-font-awesome-rails/32420361/log.gz

autopkgtest [04:11:19]: test smoke-test: [---
+ cd /tmp/autopkgtest-lxc.v350w8iu/downtmp/autopkgtest_tmp
+ mkdir foo
+ cd foo
+ mkdir -p config
+ mkdir -p app/assets/javascripts
+ cat
+ cat
+ bundle install --local
[DEPRECATED] This Gemfile does not include an explicit global source.
Not using an explicit global source may result in a different lockfile
being generated depending on the gems you have installed locally before
bundler is run. Instead, define a global source in your Gemfile like
this: source "https://rubygems.org;.

Resolving dependencies...
Using rake 13.0.6
Using zeitwerk 2.6.1
Using builder 3.2.4
Using erubi 1.9.0
Using mini_portile2 2.8.1
Using crass 1.0.2
Using bundler 2.3.15
Using method_source 1.0.0
Using thor 1.2.1
Using concurrent-ruby 1.1.6
Using minitest 5.15.0
Using racc 1.6.2
Using rack 2.2.4
Using nokogiri 1.13.10
Using i18n 1.10.0
Using tzinfo 2.0.5
Using rack-test 2.0.2
Using loofah 2.19.1
Using activesupport 6.1.7
Using rails-html-sanitizer 1.4.4
Using rails-dom-testing 2.0.3
Using actionview 6.1.7
Using actionpack 6.1.7
Using railties 6.1.7
Using font-awesome-rails 4.7.0.7
Bundle complete! 3 Gemfile dependencies, 25 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
+ cat
+ cat
+ cat
+ cat
+ bundle exec rake assets:precompile
rake aborted!
Don't know how to build task 'assets:precompile' (See the list of
available tasks with `rake --tasks`)

(See full trace by running task with --trace)
autopkgtest [04:11:20]: test smoke-test: ---]

OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033496: scilab: cannot start scilab at all

2023-04-03 Thread Andrey Rakhmatullin

On Sun, Mar 26, 2023 at 10:23:46AM +0200, ryan wrote:
> typed scilab in the terminal
> 
>* What was the outcome of this action?
> ~$ scilab
> [...]
> The configuration file is severely corrupted and cannot be read. It will be
> deleted.
I can confirm this behavior on testing (after `apt install scilab`).

Bug#1033524: Simplify the instructions for making bootable media

2023-04-03 Thread Holger Wansing

Control: tags -1 + pending

Holger Wansing  wrote (Sat, 1 Apr 2023 20:52:08 +0200):
> I have added such wiki page under
> https://wiki.debian.org/DebianInstaller/CreateUSBMedia
> and overworked my patch a bit, to include a link to this page (amongst 
> some more minor things).
> 
> I will apply it shortly, if noone objects.

Applied.

Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1033907: numba: autopkgtest regression: segmentation fault on arm64


Source: numba
Version: 0.56.4+dfsg-2
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, as mentioned in bug 
#1020445 message 19 it fails since around September 2022 everywhere 
except amd64 (where it only finishes before timeout on our most powerful 
host). Can you please investigate the situation and fix it? I copied 
some of the output on arm64 at the bottom of this report, other 
architectures have different issues thought.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/arm64/n/numba/32471152/log.gz

Fatal Python error: Segmentation fault

Current thread 0x946c96e0 (most recent call first):
  File "/usr/lib/python3.11/unittest/case.py", line 579 in _callTestMethod
  File "/usr/lib/python3.11/unittest/case.py", line 623 in run
  File "/usr/lib/python3.11/unittest/case.py", line 678 in __call__
  File "/usr/lib/python3/dist-packages/numba/testing/main.py", line 665 
in __call__

  File "/usr/lib/python3.11/multiprocessing/pool.py", line 125 in worker
  File "/usr/lib/python3.11/multiprocessing/process.py", line 108 in run
  File "/usr/lib/python3.11/multiprocessing/process.py", line 314 in 
_bootstrap
  File "/usr/lib/python3.11/multiprocessing/popen_fork.py", line 71 in 
_launch
  File "/usr/lib/python3.11/multiprocessing/popen_fork.py", line 19 in 
__init__

  File "/usr/lib/python3.11/multiprocessing/context.py", line 281 in _Popen
  File "/usr/lib/python3.11/multiprocessing/process.py", line 121 in start
  File "/usr/lib/python3.11/multiprocessing/pool.py", line 329 in 
_repopulate_pool_static
  File "/usr/lib/python3.11/multiprocessing/pool.py", line 306 in 
_repopulate_pool

  File "/usr/lib/python3.11/multiprocessing/pool.py", line 215 in __init__
  File "/usr/lib/python3.11/multiprocessing/context.py", line 119 in Pool
  File "/usr/lib/python3/dist-packages/numba/testing/main.py", line 742 
in _run_inner

  File "/usr/lib/python3.11/unittest/runner.py", line 217 in run
  File "/usr/lib/python3/dist-packages/numba/testing/main.py", line 796 
in run

  File "/usr/lib/python3.11/unittest/main.py", line 274 in runTests
  File "/usr/lib/python3/dist-packages/numba/testing/main.py", line 326 
in run_tests_real
  File "/usr/lib/python3/dist-packages/numba/testing/main.py", line 341 
in runTests

  File "/usr/lib/python3.11/unittest/main.py", line 102 in __init__
  File "/usr/lib/python3/dist-packages/numba/testing/main.py", line 168 
in __init__
  File "/usr/lib/python3/dist-packages/numba/testing/__init__.py", line 
54 in run_tests
  File "/usr/lib/python3/dist-packages/numba/testing/_runtests.py", 
line 25 in _main
  File "/usr/lib/python3/dist-packages/numba/runtests.py", line 9 in 


  File "", line 88 in _run_code
  File "", line 198 in _run_module_as_main

Extension modules: numpy.core._multiarray_umath, 
numpy.core._multiarray_tests, numpy.linalg._umath_linalg, 
numpy.fft._pocketfft_internal, numpy.random._common, 
numpy.random.bit_generator, numpy.random._bounded_integers, 
numpy.random._mt19937, numpy.random.mtrand, numpy.random._philox, 
numpy.random._pcg64, numpy.random._sfc64, numpy.random._generator, 
numba.core.typeconv._typeconv, numba._helperlib, numba._dynfunc, 
numba._dispatcher, numba.core.runtime._nrt_python, 
numba.np.ufunc._internal, numba.experimental.jitclass._box, 
scipy._lib._ccallback_c, scipy.linalg._fblas, scipy.linalg._flapack, 
scipy.linalg._cythonized_array_utils, scipy.linalg._flinalg, 
scipy.linalg._solve_toeplitz, scipy.linalg._matfuncs_sqrtm_triu, 
scipy.linalg.cython_lapack, scipy.linalg.cython_blas, 
scipy.linalg._matfuncs_expm, scipy.linalg._decomp_update, 
scipy.sparse._sparsetools, _csparsetools, scipy.sparse._csparsetools, 
scipy.sparse.linalg._isolve._iterative, 
scipy.sparse.linalg._dsolve._superlu, 
scipy.sparse.linalg._eigen.arpack._arpack, scipy.sparse.csgraph._tools, 
scipy.sparse.csgraph._shortest_path, scipy.sparse.csgraph._traversal, 
scipy.sparse.csgraph._min_spanning_tree, scipy.sparse.csgraph._flow, 
scipy.sparse.csgraph._matching, scipy.sparse.csgraph._reordering, 
zmq.backend.cython.context, zmq.backend.cython.message, 
zmq.backend.cython.socket, zmq.backend.cython._device, 
zmq.backend.cython._poll, zmq.backend.cython._proxy_steerable, 
zmq.backend.cython._version, zmq.backend.cython.error, 
zmq.backend.cython.utils, tornado.speedups, numpy.core._umath_tests, 
_cffi_backend, scipy.special._ufuncs_cxx,

Bug#1033906: debian-edu-router: [INTL:nl] Dutch translation of debconf messages

 
 
Package: debian-edu-router 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch translation of debian-edu-router
debconf messages. A draft has been posted to the debian-l10n-dutch mailing
list allowing for review. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Kind regards,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1033905: glibc: [INTL:nl] Dutch translation of debconf messages

 
 
Package: glibc 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch translation of glibc debconf
messages. A draft has been posted to the debian-l10n-dutch mailing list
allowing for review. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Kind regards,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1033903: apt-listchanges: [INTL:nl] Dutch translation for the apt-listchanges package's documentation

 
 
Package: apt-listchanges 
Severity: wishlist 
Tags: l10n patch 
 
 
 
 
Dear Maintainer, 
 
 
Please find attached the Dutch po file for the apt-listchanges
package's documentation.
A draft has been posted to the debian-l10n-dutch mailing list allowing for
review. 
Please add it to your next package revision. 
It should be put as "doc/po/nl.po" in your package build tree. 

-- 
Kind regards,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1033902: ulogd2 debian package missing PCAP output plugin from upstream

2023-04-03 Thread Harald Welte

Package: ulogd2
Version: 2.0.8-1
Severity: normal

Today  - for the first time in probably 15+ years - I wanted to capture the 
actual packets
dropped within netfilter in a pcap file.  The method I developed during my 
netfilter days
20 year ago for this is the PCAP output plugin of ulogd.

To my knowledge it's the only method which allows you to capture the actual 
binary packet
violating your iptables or nftables policy for later analysis in wireshark or 
other pcap
related tools.

However, I was surprised to see that the ulogd2 package both in Debian stable 
as well
as unstable doesn't contain the PCAP output plugin.  Is that a conscious 
decision? I would
think it's a rather useful feature to have.

Also, the example config file contains PCAP related sections, making this even 
more confusing.  So you
uncomment parts of the example config that gets installed 
(stack=log2:NFLOG,base1:BASE,pcap1:PCAP) and then it
fails due to not finding the PCAP plugin with either with

Apr 03 19:02:11 lakshmi1 ulogd[3579]: can't find requested plugin PCAP

(in the plugin auto-load case , or with

Apr 03 19:02:38 lakshmi1 ulogd[3607]: load_plugin: 
'/usr/lib/x86_64-linux-gnu/ulogd/ulogd_output_PCAP.so': 
/usr/lib/x86_64-linux-gnu/ulogd/ulogd_output_PCAP.so: cannot open shared object 
file: No such file or directory

(in the case one explicitly wants to load the plugin via the commented-out line 
from the sample config file.

Given that building the pcap plugin is enabled by default, I guess it must be 
explicitly disabled with
--disable-pcap in the debian package, so I guess it's a conscious decision and 
not an accident?

Thanks for looking into this.

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

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

Versions of packages ulogd2 depends on:
ii  adduser3.132
ii  init-system-helpers1.65.2
ii  libc6  2.36-8
ii  libmnl01.0.4-3
ii  libnetfilter-acct1 1.0.3-3
ii  libnetfilter-conntrack31.0.9-3
ii  libnetfilter-log1  1.0.2-3
ii  libnfnetlink0  1.0.2-2
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.06-3

ulogd2 recommends no packages.

Versions of packages ulogd2 suggests:
pn  ulogd2-dbi  
pn  ulogd2-json 
pn  ulogd2-mysql
pn  ulogd2-pcap 
pn  ulogd2-pgsql
pn  ulogd2-sqlite3  

-- Configuration Files:
/etc/ulogd.conf [Errno 13] Permission denied: '/etc/ulogd.conf'

-- no debconf information

Bug#1033888: ITP: usbscale -- read weight data from a USB scale

2023-04-03 Thread John Paul Adrian Glaubitz

Hi John!


> Package: wnpp
> Severity: wishlist
> Owner: John Scott 
> Tags: newcomer
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name: usbscale
>   Upstream Contact: Eric Jiang
> * URL : https://github.com/erjiang/usbscale
> * License : GPL 3.0 or any later version
>   Programming Lang: C
>   Description : read weight data from a USB scale
> 
> This package provides a utility one can use to read data from various
> USB scales, ones which are sold as postage scales in particular.

I'm actually about to buy such a scale with USB and I would therefore
be interested in sponsoring this package. Let me know if you're interested.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1020474: Ready to Implement

2023-04-03 Thread Soren Stoutner

The dependencies are finally in place so this can be implemented.

To make things simpler for dictionary packagers, we are using a virtual package 
and an 
unversioned path for the conversion tool so that dictionary packagers don’t 
have to make 
modifications to their packages when the versions of Qt change in Debian.

All you should need to do is the following:

1.  Build-depend on `convert-bdic`.
2.  Use /usr/bin/convert-bdic to do the dictionary conversion.
3.  Place the .bdic files in /usr/share/hunspell-bdic.

More detailed information can be found in the dictionary packager documentation 
at:

file:///usr/share/doc/dictionaries-common-dev/dsdt-policy.html#hunspell-bdic

Thanks,

Soren

-- 
Soren Stoutner
so...@stoutner.com


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

Bug#1033901: Acknowledgement (unblock: castle-game-engine/7.0~alpha.2+dfsg1-4)

2023-04-03 Thread Abou Al Montacir

This ticket should be seen as an add
on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033840 which was accepted.
-- 
Cheers,
Abou Al Montacir


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

Bug#1033901: unblock: castle-game-engine/7.0~alpha.2+dfsg1-4

2023-04-03 Thread Abou Al Montacir

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

Please unblock package castle-game-engine

[ Reason ]
Fix compilation on mipsel architecture (Closes: Bug#891683)

[ Impact ]
No impact on other architectures. Fixes the compilation on mipsel.

[ Tests ]
The test suite was running on other architectures and will run on mipsel.

[ Risks ]
Probably none.

[ 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 testing

[ Other info ]
This will allow to bring mipsel to the supported architectures while not
impacting at all any other architecture.

The changes are just fixing compilation directives that are specific to mips
and mipsel.

unblock castle-game-engine/7.0~alpha.2+dfsg1-4
diff -Nru castle-game-engine-7.0~alpha.2+dfsg1/debian/changelog 
castle-game-engine-7.0~alpha.2+dfsg1/debian/changelog
--- castle-game-engine-7.0~alpha.2+dfsg1/debian/changelog   2023-04-02 
16:44:18.0 +0200
+++ castle-game-engine-7.0~alpha.2+dfsg1/debian/changelog   2023-04-03 
15:07:29.0 +0200
@@ -1,3 +1,11 @@
+castle-game-engine (7.0~alpha.2+dfsg1-4) unstable; urgency=medium
+
+  * Fixed compilation on mipsel.
+On mipsel both CPUmips and CPUmipsel are defined by the compiler.
+(Closes: Bug#891683)
+
+ -- Abou Al Montacir   Mon, 03 Apr 2023 15:07:29 +0200
+
 castle-game-engine (7.0~alpha.2+dfsg1-3) unstable; urgency=medium
 
   * Removed unused binary files to fix lintian reported errors.
diff -Nru 
castle-game-engine-7.0~alpha.2+dfsg1/debian/patches/Fixed-compilation-on-mipsel.patch
 
castle-game-engine-7.0~alpha.2+dfsg1/debian/patches/Fixed-compilation-on-mipsel.patch
--- 
castle-game-engine-7.0~alpha.2+dfsg1/debian/patches/Fixed-compilation-on-mipsel.patch
   1970-01-01 01:00:00.0 +0100
+++ 
castle-game-engine-7.0~alpha.2+dfsg1/debian/patches/Fixed-compilation-on-mipsel.patch
   2023-04-03 15:04:37.0 +0200
@@ -0,0 +1,22 @@
+Description: Fixed compilation on mipsel
+ This patch fixes a bug causing CGE not compile on mipsel architecture.
+ .
+ The issue was that on mipsel both CPUmips and CPUmipsel are defined by the
+ compiler.
+Author: Abou Al Montacir 
+
+diff --git a/tools/common-code/toolarchitectures.pas 
b/tools/common-code/toolarchitectures.pas
+index 905fa46..9ae4e07 100644
+--- a/tools/common-code/toolarchitectures.pas
 b/tools/common-code/toolarchitectures.pas
+@@ -138,8 +138,8 @@ const
+ {$ifdef CPUpowerpc64} powerpc64 {$endif}
+ {$ifdef CPUavr} avr {$endif}
+ {$ifdef CPUarmeb} armeb {$endif}
+-{$ifdef CPUmips} mips {$endif}
+-{$ifdef CPUmipsel} mipsel {$endif}
++{$ifdef CPUmipsel} mipsel {$else}
++{$ifdef CPUmips} mips {$endif}{$endif}
+ {$ifdef CPUjvm} jvm {$endif}
+ {$ifdef CPUi8086} i8086 {$endif}
+ {$ifdef CPUsparc64} sparc64 {$endif}
diff -Nru castle-game-engine-7.0~alpha.2+dfsg1/debian/patches/series 
castle-game-engine-7.0~alpha.2+dfsg1/debian/patches/series
--- castle-game-engine-7.0~alpha.2+dfsg1/debian/patches/series  2022-10-24 
20:06:20.0 +0200
+++ castle-game-engine-7.0~alpha.2+dfsg1/debian/patches/series  2023-04-03 
08:43:08.0 +0200
@@ -7,3 +7,4 @@
 77c97ef135eb5ad95c05d90edae11fa3d2863359.patch
 Fix-UTF-8-BOM.patch
 f0fe0583dded3d0c27ae46fde59a00f58a777e46.patch
+Fixed-compilation-on-mipsel.patch

Bug#1033820: [Pkg-javascript-devel] Bug#1033820: node-snapdragon: autopkgtest regression: Cannot find module 'snapdragon-node'


Hi yadd,

On 03-04-2023 05:42, Yadd wrote:
I'm unable to reproduce this issue: there is a link that provides 
snapdragon-node inside snapdragon-capture-set:


I could by running the following on my laptop:
paul@mulciber ~ $ autopkgtest --no-built-binaries node-snapdragon -- lxc 
--sudo autopkgtest-unstable-amd64


What did you try?


$ debc|grep '> '
lrwxrwxrwx root/root 0 2022-12-01 17:20 
./usr/share/nodejs/snapdragon-capture-set/node_modules -> 
../snapdragon/node_modules


and snamdragon has snapdragon/node_modules/snapdragon-node


To avoid confusion, I assume you mean node-snapdragon.

https://packages.debian.org/sid/all/node-snapdragon/filelist
confirms
/usr/share/nodejs/snapdragon/node_modules/snapdragon-node/

In a failing testbed:
root@autopkgtest-lxc-xulhyp:/ # ls -al 
/usr/share/nodejs/snapdragon-capture-set

total 20
drwxr-xr-x  2 root root 4096 Apr  3 19:50 .
drwxr-xr-x 52 root root 4096 Apr  3 19:50 ..
-rw-r--r--  1 root root 4283 Nov 28 20:25 index.js
-rw-r--r--  1 root root 1460 Nov 28 20:25 package.json

Am I missing something?

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033879: widelands: Clicking options in Widelands cause the program to quit with an exception (file not found)

2023-04-03 Thread Tobias Frost

Control: tags -1 -moreinfo

Hi waxhead,

thanks for the info! I think I now understand what's happening:
This seems to be #1018966…

/usr/share/games/widelands/data/i18n/fonts/Culmus is supposed to be a
symlink to ../../../../../fonts/truetype/culmus-fancy, it seems so
that the widelands-data.maintscript is not correct, possibly the
version specifier. I'll need to debug that (and get a reproducer) and verifiy 
this.

-- 
Cheers,
tobi


On Mon, Apr 03, 2023 at 07:06:50PM +0200, waxhead wrote:
> Done - see below. As expected the font file does not exist in my system.
> I can probably (re-) install it, but I would rather help fix the problem
> unless the issue is (for some reason) only on my system in the whole world
> :)
> 
> Tobias Frost wrote:
> > Control: tags -1 moreinfo
> > 
> > Hi waxhead,
> > 
> > thanks for the report!
> > 
> > Unfortunatly I cannot reproduce the issue…
> > The font should be pulled in, by the package culmus-fancy, through 
> > dependency.
> > 
> > 
> > Can you do on a console:
> > 
> > namei 
> > /usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> 
> f:
> /usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
>  d /
>  d usr
>  d share
>  d games
>  d widelands
>  d data
>  d i18n
>  d fonts
>  d Culmus
>TaameyFrankCLM-Medium.ttf - No such file or directory
> 
> > 
> > dpkg -l 'widelands*'
> 
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name   Version  Architecture Description
> +++-==---
> ii  widelands  2:1.1-2  amd64fantasy real-time strategy game
> ii  widelands-data 2:1.1-2  all  fantasy real-time strategy game
> (data files)
> 
> > dpkg -l culmus-fancy
> 
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name   VersionArchitecture Description
> +++-==-==--=
> ii  culmus-fancy   0.0.20140315-1 all  Type1 Fancy Hebrew Fonts for
> X11
> 
> > 
> > and let me know the output.
> > 
> > (You can also retry re-installing culmus-fancy ans see if that improves 
> > things.)
> > 
> > 
> > Cheers,
> > tobi
> > 
> > 
> > 
> > On Mon, Apr 03, 2023 at 02:11:30PM +0200, waxhead wrote:
> > > Package: widelands
> > > Version: 2:1.1-2
> > > Severity: important
> > > X-Debbugs-Cc: waxh...@dirtcellar.net
> > > 
> > > Dear Maintainer,
> > > 
> > > *** Reporter, please consider answering these questions, where 
> > > appropriate ***
> > > 
> > > * What led up to the situation?
> > > 
> > > Started up widelands (version 1.1 Release), clicked the option button. 
> > > This is the output
> > > 
> > > [00:00:08.059 real] WARNING: Font file not found. Falling back to sans: 
> > > Culmus/TaameyFrankCLM-Medium.ttf
> > > [00:00:08.059 real] WARNING: LayeredFileSystem: Could not load file: 
> > > could not find file or directory: 
> > > i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> > > [00:00:08.059 real] WARNING: I have tried the following path(s):
> > > [00:00:08.059 real] WARNING: 
> > > /home/waxhead/.local/share/widelands/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> > > [00:00:08.059 real] WARNING: 
> > > /usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> > > [00:00:08.059 real] WARNING: 
> > > /home/waxhead/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> > > 
> > > Caught exception (of type '17FileNotFoundError') in outermost handler!
> > > The exception said: LayeredFileSystem: Could not load file: could not 
> > > find file or directory: i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> > > I have tried the following path(s):
> > >  
> > > /home/waxhead/.local/share/widelands/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> > >  
> > > /usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> > >  /home/waxhead/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> > > 
> > > This should not happen. Please file a bug report on version 1.1 Release.
> > > and remember to specify your operating system.
> > > 
> > > [00:00:08.098 real] INFO: SoundHandler: Closing 1 time, 44100 Hz, format 
> > > 32784, 2 channels
> > > [00:00:08.098 real] INFO: SoundHandler: SDL_AUDIODRIVER pulseaudio
> > > 
> > > 
> > > * What exactly did you do (or not do) that was effective (or
> > >   ineffective)?
> > > 
> > > I did not try to copy a font to any of the locations. I expect widelands 
> > > to depend on the required font.
> > > 
> > > * What was the outcome of this action?
> > > 
> > > Not much since I did not do anything
> > > 
> > > * What outcome did you expect instead?
> > > 
> > > I expect

Bug#1033833: unknown-horizons: Fails to start Couldn't open content/fonts/Unifont.ttf

2023-04-03 Thread Tobias Frost

Control: reassign -1 unknown-horizons
Control: found -1 2019.1-5

Hi Hideki Yamane,

On Mon, 3 Apr 2023 09:16:14 +0900 Hideki Yamane  wrote:
> On Sun, 2 Apr 2023 18:33:34 +0200
> Tobias Frost  wrote:
> > it seems so that the fonts package unifont dropped unifont.ttf in
> > 1:15.0.01-1:
> 
>  Yes, and upstream plans to drop ttf. So I do not want to revert
>  this change in Debian package.
> 
> > Unifont 15.0.01 installs OpenType fonts alongside the TrueType fonts
> > that are installed in Unifont 14.0.x and previous releases.
> > The current plan is for Unifont 16.0.01 to no longer install TrueType
> > fonts that have OpenType equivalents. This will allow a period of
> > approximately one year for Unifont users to switch from TrueType to
> > OpenType files. 
> 

thanks for your feedback and the hint to look into otf.
It seems that the fife engine of unknown-horizons can read otf fonts as well,
so redirecting the symlink to that version works \o/

So I'm reassigning this bug back to unknown horizons and will fix it there.

Again thanks for the hint!

PS: Long description of the fonts-unifont package is still mentioning truetype 
fonts…
Maybe that needs s/truetype/opentype/ ?

-- 
tobi

signature.asc
Description: PGP signature

Bug#1033900: pre-approval: dkms/3.0.10-10

2023-04-03 Thread Andreas Beckmann

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

Hi,

I'd like to ask for pre-approval for adding a new binary package to
bookworm: dkms-test-dkms. This is a trivial dkms module that will only
be used for autopkgtests, s.t. we can model some failing scenarios as
autopkgtests without relying on some other -dkms packages not in our
control. I've added some new autopkgtests using it. The corresponding
failures are already fixed by the patches in -8.

The new package is available in -9 in experimental.
The attached patch shows only the diff between sid and experimental.

Should -8 migrate first? Does that need unblocking first and maybe some
aging? It comes with a lot of bugfixes, some RC, and an dkms-autopkgtest
fix needed by nvidia-cuda-toolkit/nvidia-cuda-samples (the
nvidia-fs-dkms package uses a dkms feature not used by any other packages
in the archive and thus never before tested with dkms-autopkgtest).

For an upload of -10 to sid I'll pick some more bugfixes ... or maybe a
new upstream bugfix release that incorporates all the patches we
currently carry (including a large extension to the testsuite covering
most of the new fixes, the testsuite I've so far stripped from the
cherry-picked patches). I'll come back with a full debdiff once -10 is
ready (and this pre-approval request was granted).


Andreas
diff --git a/debian/changelog b/debian/changelog
index 24da0ec..206519e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+dkms (3.0.10-9) experimental; urgency=medium
+
+  * Add dkms-test-dkms package with trivial kernel module for dkms tests.
+  * New autopkgtest: Install some-dkms after linux-headers.
+  * New autopkgtest: Install linux-headers after some-dkms.
+  * New autopkgtest: Install some-dkms after linux-image w/o linux-headers.
+  * New autopkgtest: Install linux-image after some-dkms w/o linux-headers.
+  * Upload to experimental.
+
+ -- Andreas Beckmann   Fri, 31 Mar 2023 14:19:59 +0200
+
 dkms (3.0.10-8) unstable; urgency=medium
 
   * Disable tests broken by fix-builtin-archive-dkms-coinstallation.patch.
diff --git a/debian/control b/debian/control
index 73a13db..51455a8 100644
--- a/debian/control
+++ b/debian/control
@@ -13,6 +13,7 @@ Homepage: https://github.com/dell/dkms
 Vcs-Git: https://salsa.debian.org/debian/dkms.git
 Vcs-Browser: https://salsa.debian.org/debian/dkms
 Rules-Requires-Root: no
+Testsuite: autopkgtest-pkg-dkms
 
 Package: dkms
 Architecture: all
@@ -54,3 +55,13 @@ Description: debhelper addon for the Dynamic Kernel Module 
System (DKMS)
  .
  This package provides a debhelper add-on 'dkms' that simplifies packaging of
  dkms kernel module source packages.
+
+Package: dkms-test-dkms
+Architecture: all
+Depends:
+ ${misc:Depends},
+Description: trivial dkms test kernel module
+ This package provides the dkms source code for the dkms-test kernel module.
+ .
+ This package is only intended for ci tests and not expected to be installed
+ on regular systems
diff --git a/debian/dkms-test-dkms.dkms b/debian/dkms-test-dkms.dkms
new file mode 100644
index 000..f1876da
--- /dev/null
+++ b/debian/dkms-test-dkms.dkms
@@ -0,0 +1 @@
+test/dkms_test-1.0/dkms.conf
diff --git a/debian/dkms-test-dkms.install b/debian/dkms-test-dkms.install
new file mode 100644
index 000..3cad773
--- /dev/null
+++ b/debian/dkms-test-dkms.install
@@ -0,0 +1 @@
+test/dkms_test-1.0 usr/src/
diff --git a/debian/rules b/debian/rules
index 2588aa9..e2ae425 100755
--- a/debian/rules
+++ b/debian/rules
@@ -21,3 +21,6 @@ override_dh_auto_build: debian/scripts/dh_dkms.1
 
 override_dh_auto_install:
$(MAKE) install-debian DESTDIR=$(CURDIR)/debian/dkms
+
+execute_after_dh_install:
+   DH_AUTOSCRIPTDIR=debian/scripts debian/scripts/dh_dkms
diff --git a/debian/tests/control b/debian/tests/control
index 352610d..2e016a3 100644
--- a/debian/tests/control
+++ b/debian/tests/control
@@ -9,3 +9,49 @@ Restrictions:
  needs-root,
  breaks-testbed,
  skip-not-installable,
+
+# install some-dkms after linux-headers
+Test-Command: apt-get install -yf dkms-test-dkms
+Features: test-name=install_some-dkms_after_linux-headers
+Architecture: amd64
+Depends:
+ dkms,
+ linux-headers-generic,
+Restrictions:
+ allow-stderr,
+ needs-root,
+ breaks-testbed,
+
+# install linux-headers after some-dkms
+Test-Command: apt-get install -yf linux-headers-generic
+Features: test-name=install_linux-headers_after_some-dkms
+Architecture: amd64
+Depends:
+ dkms-test-dkms,
+Restrictions:
+ allow-stderr,
+ needs-root,
+ breaks-testbed,
+
+# install some-dkms after linux-image w/o linux-headers
+Test-Command: apt-get install -yf dkms-test-dkms
+Features: test-name=install_some-dkms_after_linux-image_without_linux-headers
+Architecture: amd64
+Depends:
+ dkms,
+ linux-image-generic,
+Restrictions:
+ allow-stderr,
+ needs-root,
+ breaks-testbed,
+
+# install linux-image after some-dkms w/o linux-headers
+Test-Command: apt-get install -yf

Bug#1033879: widelands: Clicking options in Widelands cause the program to quit with an exception (file not found)

2023-04-03 Thread waxhead


Done - see below. As expected the font file does not exist in my system.
I can probably (re-) install it, but I would rather help fix the problem 
unless the issue is (for some reason) only on my system in the whole 
world :)


Tobias Frost wrote:

Control: tags -1 moreinfo

Hi waxhead,

thanks for the report!

Unfortunatly I cannot reproduce the issue…
The font should be pulled in, by the package culmus-fancy, through dependency.


Can you do on a console:

namei 
/usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf


f: 
/usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf

 d /
 d usr
 d share
 d games
 d widelands
 d data
 d i18n
 d fonts
 d Culmus
   TaameyFrankCLM-Medium.ttf - No such file or directory



dpkg -l 'widelands*'


Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---
ii  widelands  2:1.1-2  amd64fantasy real-time strategy game
ii  widelands-data 2:1.1-2  all  fantasy real-time strategy 
game (data files)



dpkg -l culmus-fancy


Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionArchitecture Description
+++-==-==--=
ii  culmus-fancy   0.0.20140315-1 all  Type1 Fancy Hebrew Fonts 
for X11




and let me know the output.

(You can also retry re-installing culmus-fancy ans see if that improves things.)


Cheers,
tobi



On Mon, Apr 03, 2023 at 02:11:30PM +0200, waxhead wrote:

Package: widelands
Version: 2:1.1-2
Severity: important
X-Debbugs-Cc: waxh...@dirtcellar.net

Dear Maintainer,

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

* What led up to the situation?

Started up widelands (version 1.1 Release), clicked the option button. This is 
the output

[00:00:08.059 real] WARNING: Font file not found. Falling back to sans: 
Culmus/TaameyFrankCLM-Medium.ttf
[00:00:08.059 real] WARNING: LayeredFileSystem: Could not load file: could not 
find file or directory: i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
[00:00:08.059 real] WARNING: I have tried the following path(s):
[00:00:08.059 real] WARNING: 
/home/waxhead/.local/share/widelands/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
[00:00:08.059 real] WARNING: 
/usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
[00:00:08.059 real] WARNING: 
/home/waxhead/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf

Caught exception (of type '17FileNotFoundError') in outermost handler!
The exception said: LayeredFileSystem: Could not load file: could not find file 
or directory: i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
I have tried the following path(s):
 
/home/waxhead/.local/share/widelands/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
 /usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
 /home/waxhead/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf

This should not happen. Please file a bug report on version 1.1 Release.
and remember to specify your operating system.

[00:00:08.098 real] INFO: SoundHandler: Closing 1 time, 44100 Hz, format 32784, 
2 channels
[00:00:08.098 real] INFO: SoundHandler: SDL_AUDIODRIVER pulseaudio


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

I did not try to copy a font to any of the locations. I expect widelands to 
depend on the required font.

* What was the outcome of this action?

Not much since I did not do anything

* What outcome did you expect instead?

I expect widelands to be supplied with the needed fonts.

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


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

Kernel: Linux 6.1.0-7-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 widelands depends on:
ii  libc62.36-8
ii  libgcc-s112.2.0-14
ii  libglew2.2   2.2.0-4+b1
ii  libglx0  1.6.0-1
ii  libicu72 72.1-3
ii  libminizip1  1.1-8+b1
ii  libopengl0   1.6.0-1
ii  libpng16-16  1.6.39-2
ii  libsdl2-2.0-02.26.4+dfsg-1
ii  libsdl2-image-2.0-0  2.6.3+dfsg-1
ii

Bug#1010519: marked as done (g++-12: compilation fails on riscv64 because of always_inline when using fmtlib)

2023-04-03 Thread No reply

Здравствуйте!

Сообщения, пришедшие на адрес no-re...@decast.com не обрабатываются.
Пожалуйста, уточните получателя и повторно отправьте ему Ваше сообщение.

С уважением,
Decast group

-
Hello!

Messages that delivered to the address no-re...@decast.com not processed.

Please check the recipient's address and send them your message again.

Sincerely,
Decast group

Bug#1033899: pipewire: Pipewire fails to sart, "Main process exited, code=killed, satus=31/SYS".

2023-04-03 Thread Itai Shaked

Package: pipewire
Version: 0.3.65-3
Severity: normal

Dear Maintainer,

No audio, pipewire fails to start. Logs contain no real information. Following
is the result of "journalctl --user -u pipewire.service":

Started pipewire.service - PipeWire Multimedia Service.
pipewire.service: Main process exited, code=killed, status=31/SYS
pipewire.service: Failed with result 'signal'.
pipewire.service: Scheduled restart job, restart counter is at 1.
Stopped pipewire.service - PipeWire Multimedia Service.

The following repeats with counter up to 6, then:

Failed to start pipewire.service - PipeWire Multimedia Service.

In Gnome sound settings no sound device is shown.
Sound was working flawlessly until a few months ago. No hardware changes since.

I am at a loss since there seems to be zero usable information in the logs,
just that the service is killed for some (unspecified?) reason.


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

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

Versions of packages pipewire depends on:
ii  adduser  3.131
ii  init-system-helpers  1.65.2
ii  libpipewire-0.3-modules  0.3.65-3
ii  pipewire-bin 0.3.65-3

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information

Bug#1033898: gnome-text-editor: Scroll bar disappears after entering invalid char with compose key

2023-04-03 Thread xMax

Package: gnome-text-editor
Version: 43.2-1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
Using keyboard layout English (Macintosh), one of the layouts offered by a
standard Debian install. The AltGr key acts as the Compose key. I believe this
is set by the keyboard layout, but system Settings > Keyboard > Special
Character Entry > Compose Key also shows "Right Alt". But when using other
keyboard layouts the AltGr key does not function as Compose key and this bug
doesn't apply.


   * What exactly did you do (or not do) that was effective (or
 ineffective)?
In new Text Editor window, open a document long enough to trigger the scroll
bar.
Place cursor at the beginning of an empty line.
Press AltGr
An underline with a dot above it appears.
Press s (or any key that doesn't immediately lead to a valid final character)
Dot changes to an s, you now have an underlined s.
Press space.
The underlined s disappears.
Press backspace.


   * What was the outcome of this action?
The scrollbar stops functioning.
If /org/gnome/desktop/interface/overlay-scrolling is set to false in dconf
Editor, the movable marker in the scrollbar disappears and it becomes equally
inoperable.

The scrollbar will come back if another document is open in another tab, that
other tab is brought to the front and then switched back to the original tab


   * What outcome did you expect instead?
AltGr not having any effect on scroll bar.


   * Debug Info from Text Editor:
Text Editor (43.2)

GLib: 2.74.6 (2.74.4)
GTK: 4.8.3 (4.8.3)
GtkSourceView: 5.6.2 (5.6.2)
Libadwaita: 1.2.2 (1.2.1)
Enchant2: 2.3.3

gtk-theme-name: Adwaita-empty
GTK_THEME: unset

org.gnome.TextEditor restore-session = true
org.gnome.TextEditor recolor-window = true
org.gnome.TextEditor show-map = false
org.gnome.TextEditor custom-font = 'Monospace 11'
org.gnome.TextEditor show-line-numbers = true [default=false]
org.gnome.TextEditor style-scheme = 'kate' [default='Adwaita']
org.gnome.TextEditor wrap-text = true
org.gnome.TextEditor style-variant = 'follow'
org.gnome.TextEditor indent-style = 'tab'
org.gnome.TextEditor show-right-margin = false
org.gnome.TextEditor spellcheck = true
org.gnome.TextEditor auto-indent = true
org.gnome.TextEditor use-system-font = true
org.gnome.TextEditor keybindings = 'default'
org.gnome.TextEditor highlight-current-line = false
org.gnome.TextEditor last-save-directory = 'file:///home//Documents'
[default='']
org.gnome.TextEditor auto-save-delay = uint32 3
org.gnome.TextEditor discover-settings = true
org.gnome.TextEditor enable-snippets = false
org.gnome.TextEditor line-height = 1.2
org.gnome.TextEditor indent-width = -1
org.gnome.TextEditor show-grid = false
org.gnome.TextEditor draw-spaces = @as []
org.gnome.TextEditor right-margin-position = uint32 80
org.gnome.TextEditor tab-width = uint32 8

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


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

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

Versions of packages gnome-text-editor depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  libadwaita-1-0   1.2.2-1
ii  libc62.36-8
ii  libcairo21.16.0-7
ii  libeditorconfig0 0.12.6-0.1
ii  libenchant-2-2   2.3.3-2
ii  libglib2.0-0 2.74.6-1
ii  libgtk-4-1   4.8.3+ds-2
ii  libgtksourceview-5-0 5.6.2-1
ii  libicu72 72.1-3
ii  libpango-1.0-0   1.50.12+ds-1

gnome-text-editor recommends no packages.

gnome-text-editor suggests no packages.

-- no debconf information

Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault

2023-04-03 Thread jim_p

Package: nvidia-legacy-340xx-driver
Version: 340.108-18
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com

Honest question to the maintainers, and to the qt5 maintainers too:

What if someone wants to install/run a package that explicitly depends on
libqt5gui5?
I wanted to try corectrl that reached the repo a few days ago, but installing
it removes the -gles version of the above lib, thus breaking all my installed
qt5 apps.

p.s. I would not care for corectrl if the maintainer of cpupower-gui had
updated the package in order to fix both its open bugs. But it will remain
abandoned as it seems.


-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages nvidia-legacy-340xx-driver depends on:
ii  nvidia-installer-cleanup 20220217+2
ii  nvidia-legacy-340xx-alternative  340.108-18
ii  nvidia-legacy-340xx-driver-bin   340.108-18
ii  nvidia-legacy-340xx-driver-libs  340.108-18
ii  nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340  340.108-18
.108]
ii  nvidia-legacy-340xx-vdpau-driver 340.108-18
ii  nvidia-support   20220217+2
ii  xserver-xorg-video-nvidia-legacy-340xx   340.108-18

Versions of packages nvidia-legacy-340xx-driver recommends:
pn  nvidia-persistenced   
ii  nvidia-settings-legacy-340xx  340.108-7

Versions of packages nvidia-legacy-340xx-driver suggests:
ii  nvidia-legacy-340xx-kernel-dkms  340.108-18

Versions of packages nvidia-legacy-340xx-driver-libs:amd64 depends on:
ii  libegl1-nvidia-legacy-340xx 340.108-18
ii  libgl1-nvidia-legacy-340xx-glx  340.108-18

Versions of packages nvidia-legacy-340xx-driver-libs:amd64 recommends:
ii  libgles1-nvidia-legacy-340xx  340.108-18
ii  libgles2-nvidia-legacy-340xx  340.108-18
pn  libnvidia-legacy-340xx-cfg1   
pn  libnvidia-legacy-340xx-encode1
pn  nvidia-legacy-340xx-driver-libs-i386  

Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 depends on:
ii  libc62.36-8
ii  libnvidia-legacy-340xx-glcore340.108-18
ii  libx11-6 2:1.8.4-2
ii  libxext6 2:1.3.4-1+b1
ii  nvidia-installer-cleanup 20220217+2
ii  nvidia-legacy-340xx-alternative  340.108-18
ii  nvidia-support   20220217+2

Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 recommends:
ii  nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340  340.108-18
.108]

Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 suggests:
ii  nvidia-legacy-340xx-kernel-dkms  340.108-18

Versions of packages xserver-xorg-video-nvidia-legacy-340xx depends on:
ii  libc6  2.36-8
ii  libnvidia-legacy-340xx-glcore  340.108-18
ii  nvidia-installer-cleanup   20220217+2
ii  nvidia-legacy-340xx-alternative340.108-18
ii  nvidia-support 20220217+2
ii  xserver-xorg-core [xorg-video-abi-25]  2:21.1.7-2

Versions of packages xserver-xorg-video-nvidia-legacy-340xx recommends:
ii  nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340  340.108-18
.108]
ii  nvidia-legacy-340xx-vdpau-driver 340.108-18
ii  nvidia-settings-legacy-340xx 340.108-7

Versions of packages xserver-xorg-video-nvidia-legacy-340xx suggests:
ii  nvidia-legacy-340xx-kernel-dkms  340.108-18

Versions of packages nvidia-legacy-340xx-alternative depends on:
ii  dpkg1.21.21
ii  glx-alternative-nvidia  1.2.2

Versions of packages nvidia-legacy-340xx-kernel-dkms depends on:
ii  dkms 3.0.10-6
ii  nvidia-installer-cleanup 20220217+2
ii  nvidia-legacy-340xx-kernel-support [nvidia-legacy-340xx-kernel-  340.108-18
support--v1]

nvidia-legacy-340xx-kernel-dkms recommends no packages.

Versions of packages glx-alternative-nvidia depends on:
ii  dpkg  1.21.21
ii  glx-alternative-mesa  1.2.2
ii  glx-diversions1.2.2
ii  update-glx1.2.2

Versions of packages glx-alternative-nvidia suggests:
ii  nvidia-legacy-340xx-driver [nvidia-driver-any]  340.108-18

Versions of packages nvidia-legacy-340xx-driver is related to:
pn  bumblebee  
pn

Bug#1033868: linphone-desktop: cannot use any account, without agreeing to terms

2023-04-03 Thread Dennis Filder

X-Debbugs-CC: Martin , Jonas Smedegaard 

On Mon, Apr 03, 2023 at 07:29:44AM +, Martin wrote:
> IMHO, agree to terms only makes sense, if using their linphone SIP
> service, but not when using any other SIP account. I really hope (but
> did not yet check), that linphone does not interchange any data with
> Belledonne, if I don't use their linphone SIP service, right?
>
> Suggested solution: The buttons "Use SIP account" and "Fetch remote
> configuration" must not be greyed out, even if user does not agree to
> the terms. The other two buttons ("Create a linphone account" and "Use a
> linphone account") should remain as they arey.

I had already patched this out of the 5.0 version of linphone-desktop
that unfortunately didn't make it into Bookworm in time.  I'll look
into backporting that patch.

> Also, the two documents might not be available, e.g. because using
> linphone-desktop in an internal setup without web access or in a country
> where outside web access is blocked. Maybe the documents could be copied
> and linked to /usr/share/doc/linphone-desktop/?

That thought occurred to me, too, but IIRC I opted against it because
I couldn't figure out if those documents are actually redistributable.
Also, they might be subject to change, and users could unknowingly
agree to terms/conditions that were not yet in the outdated version of
the agreement.

Regards.

Bug#1033897: Firefox and thunderbird fail to launch under sysvinit

2023-04-03 Thread Matthias Geiger

Package: gnome-shell
Version: 43.3-3
Severity: important
X-Debbugs-Cc: debian-init-divers...@chiark.greenend.org.uk, 
matthias.geiger1...@tutanota.de

Hello dear Maintainers.

I encountered a strange bug with the GNOME Shell. 
To reproduce:

1) Set up a debian/devuan testing/sid vm with sysvinit.
2) Install gnome-core
3) Try to launch firefox(-esr) or thunderbird from a GNOME wayland session

Nothing happens. The process opens and terminates instantly. Neither KDE Plasma 
(wayland) exhibits this bug, nor GNOME on xorg, nor a wayfire session launched 
via dbus.
Strangely firefox launches fine when MOZ_ENABLE_WAYLAND=1 is set. ktrip and 
kgeotag also fail to launch when forced on x11 with QT_QPA_PLATFORM=xcb.
My guess: Some weird xwayland quirk ? Xwayland is running. 

Happy to provide more debugging. For now, it can be worked around by explicitly 
setting said env vars to force wayland
I haven't tested another init system. Sending this from my systemd machine in 
case you're wondering.

Regards,

Matthias Geiger



-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.2.8-surface (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-accountsservice-1.0   22.08.8-6
ii  gir1.2-adw-1 1.2.2-1
ii  gir1.2-atk-1.0   2.46.0-5
ii  gir1.2-atspi-2.0 2.46.0-5
ii  gir1.2-freedesktop   1.74.0-3
ii  gir1.2-gcr-3 3.41.1-1+b1
ii  gir1.2-gdesktopenums-3.0 43.0-1
ii  gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1
ii  gir1.2-gdm-1.0   43.0-3
ii  gir1.2-geoclue-2.0   2.6.0-2
ii  gir1.2-glib-2.0  1.74.0-3
ii  gir1.2-gnomebluetooth-3.042.5-3
ii  gir1.2-gnomedesktop-3.0  43.2-2
ii  gir1.2-graphene-1.0  1.10.8-1
ii  gir1.2-gstreamer-1.0 1.22.0-2
ii  gir1.2-gtk-3.0   3.24.37-2
ii  gir1.2-gtk-4.0   4.8.3+ds-2
ii  gir1.2-gweather-4.0  4.2.0-2
ii  gir1.2-ibus-1.0  1.5.27-5
ii  gir1.2-mutter-11 43.3-5
ii  gir1.2-nm-1.01.42.0-1
ii  gir1.2-nma-1.0   1.10.6-1
ii  gir1.2-pango-1.0 1.50.12+ds-1
ii  gir1.2-polkit-1.0122-3
ii  gir1.2-rsvg-2.0  2.54.5+dfsg-1
ii  gir1.2-soup-3.0  3.2.2-2
ii  gir1.2-upowerglib-1.00.99.20-2
ii  gir1.2-webkit2-4.1   2.40.0-3
ii  gnome-backgrounds43.1-1
ii  gnome-settings-daemon43.0-4
ii  gnome-shell-common   43.3-3
ii  gsettings-desktop-schemas43.0-1
ii  gstreamer1.0-pipewire0.3.65-3
ii  libatk-bridge2.0-0   2.46.0-5
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-8
ii  libcairo21.16.0-7
ii  libecal-2.0-23.46.4-2
ii  libedataserver-1.2-273.46.4-2
ii  libgcr-base-3-1  3.41.1-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgirepository-1.0-11.74.0-3
ii  libgjs0g 1.74.2-1
ii  libgles2 1.6.0-1
ii  libglib2.0-0 2.74.6-1
ii  libglib2.0-bin   2.74.6-1
ii  libgnome-autoar-0-0  0.4.3-1
ii  libgnome-desktop-3-2043.2-2
ii  libgraphene-1.0-01.10.8-1
ii  libgtk-3-0   3.24.37-2
ii  libgtk-4-1   4.8.3+ds-2
ii  libical3 3.0.16-1+b1
ii  libjson-glib-1.0-0   1.6.6-1
ii  libmutter-11-0   43.3-5
ii  libnm0   1.42.0-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libpolkit-agent-1-0  122-3
ii  libpolkit-gobject-1-0

Bug#1033896: ITP: ruby-aliyun-sdk -- Aliyun OSS SDK for Ruby

2023-04-03 Thread Pirate Praveen


Package: wnpp
Severity: wishlist
Owner: Pirate Praveen 

Packaging of https://rubygems.org/gems/aliyun-sdk

Bug#1032642: iproute2: ip tunnel change ip6gre to gre crashes with stack smash

2023-04-03 Thread Stephen Hemminger

ted
> 
> This happens because iproute2 just assumes the tunnel is ipv4, but the
> kernel "knows" it's actually ip6gre so when calling the SIOCGETTUNNEL
> ioctl it writes back a struct ip6_tnl_parm2 into the struct
> ip_tunnel_parm which is smaller, so the stack gets overwritten. Is
> there any way to tell from userspace whether a gre is v4 or v6 before
> doing an ioctl? The ioctls don't take/return a size parameter as far
> as I can see...

Ip uses and IPv4 UDP socket when it thinks it is talking to GRE.
And a IPv6 UDP socket when it is talking to GRE6.

So the kernel could check and error out?

Bug#1033879: widelands: Clicking options in Widelands cause the program to quit with an exception (file not found)

2023-04-03 Thread Tobias Frost

Control: tags -1 moreinfo

Hi waxhead,

thanks for the report!

Unfortunatly I cannot reproduce the issue…
The font should be pulled in, by the package culmus-fancy, through dependency.


Can you do on a console:

namei 
/usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf

dpkg -l 'widelands*'
dpkg -l culmus-fancy

and let me know the output.

(You can also retry re-installing culmus-fancy ans see if that improves things.)


Cheers,
tobi



On Mon, Apr 03, 2023 at 02:11:30PM +0200, waxhead wrote:
> Package: widelands
> Version: 2:1.1-2
> Severity: important
> X-Debbugs-Cc: waxh...@dirtcellar.net
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
> 
> Started up widelands (version 1.1 Release), clicked the option button. This 
> is the output
> 
> [00:00:08.059 real] WARNING: Font file not found. Falling back to sans: 
> Culmus/TaameyFrankCLM-Medium.ttf
> [00:00:08.059 real] WARNING: LayeredFileSystem: Could not load file: could 
> not find file or directory: i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> [00:00:08.059 real] WARNING: I have tried the following path(s):
> [00:00:08.059 real] WARNING: 
> /home/waxhead/.local/share/widelands/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> [00:00:08.059 real] WARNING: 
> /usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> [00:00:08.059 real] WARNING: 
> /home/waxhead/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> 
> Caught exception (of type '17FileNotFoundError') in outermost handler!
> The exception said: LayeredFileSystem: Could not load file: could not find 
> file or directory: i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> I have tried the following path(s):
> 
> /home/waxhead/.local/share/widelands/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> 
> /usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> /home/waxhead/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
> 
> This should not happen. Please file a bug report on version 1.1 Release.
> and remember to specify your operating system.
> 
> [00:00:08.098 real] INFO: SoundHandler: Closing 1 time, 44100 Hz, format 
> 32784, 2 channels
> [00:00:08.098 real] INFO: SoundHandler: SDL_AUDIODRIVER pulseaudio
> 
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> I did not try to copy a font to any of the locations. I expect widelands to 
> depend on the required font.
> 
>* What was the outcome of this action?
> 
> Not much since I did not do anything
> 
>* What outcome did you expect instead?
> 
> I expect widelands to be supplied with the needed fonts.
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- System Information:
> Debian Release: 12.0
>   APT prefers testing-security
>   APT policy: (500, 'testing-security'), (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.1.0-7-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 widelands depends on:
> ii  libc62.36-8
> ii  libgcc-s112.2.0-14
> ii  libglew2.2   2.2.0-4+b1
> ii  libglx0  1.6.0-1
> ii  libicu72 72.1-3
> ii  libminizip1  1.1-8+b1
> ii  libopengl0   1.6.0-1
> ii  libpng16-16  1.6.39-2
> ii  libsdl2-2.0-02.26.4+dfsg-1
> ii  libsdl2-image-2.0-0  2.6.3+dfsg-1
> ii  libsdl2-mixer-2.0-0  2.6.2+dfsg-2
> ii  libsdl2-ttf-2.0-02.20.1+dfsg-2
> ii  libstdc++6   12.2.0-14
> ii  widelands-data   2:1.1-2
> 
> widelands recommends no packages.
> 
> widelands suggests no packages.
> 
> -- no debconf information
>

Bug#1033895: unblock: elasticsearch-curator/5.8.1-4.1


Package: release.debian.org
Control: affects -1 + src:elasticsearch-curator
X-Debbugs-Cc: elasticsearch-cura...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package elasticsearch-curator.

[ Reason ]
Fixes FTBFS bugs #1022015 and #1026566.

[ Impact ]
The package will be auto-removed from bookworm without unblock.

[ Tests ]
package build fails in unit tests.

[ Risks ]
Upstream patch; no changes except for the yaml.load calls.

[ 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 testing

unblock elasticsearch-curator/5.8.1-4.1diff -Nru elasticsearch-curator-5.8.1/debian/changelog 
elasticsearch-curator-5.8.1/debian/changelog
--- elasticsearch-curator-5.8.1/debian/changelog2022-10-16 
18:58:04.0 +0200
+++ elasticsearch-curator-5.8.1/debian/changelog2023-03-04 
17:17:29.0 +0100
@@ -1,3 +1,11 @@
+elasticsearch-curator (5.8.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream fix for compatibility with newer pyyaml.
+(Closes: #1022015)
+
+ -- Adrian Bunk   Sat, 04 Mar 2023 18:17:29 +0200
+
 elasticsearch-curator (5.8.1-4) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru 
elasticsearch-curator-5.8.1/debian/patches/0001-Version-bump-to-pyyaml-5.4.1-1596.patch
 
elasticsearch-curator-5.8.1/debian/patches/0001-Version-bump-to-pyyaml-5.4.1-1596.patch
--- 
elasticsearch-curator-5.8.1/debian/patches/0001-Version-bump-to-pyyaml-5.4.1-1596.patch
 1970-01-01 01:00:00.0 +0100
+++ 
elasticsearch-curator-5.8.1/debian/patches/0001-Version-bump-to-pyyaml-5.4.1-1596.patch
 2023-03-04 17:16:49.0 +0100
@@ -0,0 +1,155 @@
+From e2c3983c04bb91d0a1367e1f16ebf081e3a00658 Mon Sep 17 00:00:00 2001
+From: Tero Saarni 
+Date: Wed, 21 Apr 2021 16:40:43 +0300
+Subject: Version bump to pyyaml 5.4.1 (#1596)
+
+diff --git a/curator/utils.py b/curator/utils.py
+index 3af2c78..0309a4f 100644
+--- a/curator/utils.py
 b/curator/utils.py
+@@ -56,7 +56,7 @@ def get_yaml(path):
+ yaml.add_constructor('!single', single_constructor)
+ 
+ try:
+-return yaml.load(read_file(path))
++return yaml.load(read_file(path), Loader=yaml.FullLoader)
+ except yaml.scanner.ScannerError as err:
+ print('Unable to read/parse YAML file: {0}'.format(path))
+ print(err)
+diff --git a/test/unit/test_class_index_list.py 
b/test/unit/test_class_index_list.py
+index 1cf20f4..cfc4621 100644
+--- a/test/unit/test_class_index_list.py
 b/test/unit/test_class_index_list.py
+@@ -800,7 +800,7 @@ class TestIterateFiltersIndex(TestCase):
+ client.cluster.state.return_value = testvars.clu_state_four
+ client.indices.stats.return_value = testvars.stats_four
+ ilo = curator.IndexList(client)
+-config = yaml.load(testvars.pattern_ft)['actions'][1]
++config = yaml.load(testvars.pattern_ft, 
Loader=yaml.FullLoader)['actions'][1]
+ ilo.iterate_filters(config)
+ self.assertEqual(['a-2016.03.03'], ilo.indices)
+ def test_age_filtertype(self):
+@@ -810,7 +810,7 @@ class TestIterateFiltersIndex(TestCase):
+ client.cluster.state.return_value = testvars.clu_state_two
+ client.indices.stats.return_value = testvars.stats_two
+ ilo = curator.IndexList(client)
+-config = yaml.load(testvars.age_ft)['actions'][1]
++config = yaml.load(testvars.age_ft, 
Loader=yaml.FullLoader)['actions'][1]
+ ilo.iterate_filters(config)
+ self.assertEqual(['index-2016.03.03'], ilo.indices)
+ def test_space_filtertype(self):
+@@ -821,7 +821,7 @@ class TestIterateFiltersIndex(TestCase):
+ client.indices.stats.return_value = testvars.stats_four
+ client.field_stats.return_value = testvars.fieldstats_four
+ ilo = curator.IndexList(client)
+-config = yaml.load(testvars.space_ft)['actions'][1]
++config = yaml.load(testvars.space_ft, 
Loader=yaml.FullLoader)['actions'][1]
+ ilo.iterate_filters(config)
+ self.assertEqual(['a-2016.03.03'], ilo.indices)
+ def test_forcemerge_filtertype(self):
+@@ -832,7 +832,7 @@ class TestIterateFiltersIndex(TestCase):
+ client.indices.stats.return_value = testvars.stats_one
+ client.indices.segments.return_value = testvars.shards
+ ilo = curator.IndexList(client)
+-config = yaml.load(testvars.forcemerge_ft)['actions'][1]
++config = yaml.load(testvars.forcemerge_ft, 
Loader=yaml.FullLoader)['actions'][1]
+ ilo.iterate_filters(config)
+ self.assertEqual([testvars.named_index], ilo.indices)
+ def test_allocated_filtertype(self):
+@@ -842,7 +842,7 @@ class TestIterateFiltersIndex(TestCase):
+ client.cluster.state.return_value = testvars.clu_state_two
+ client.indices.stats.return_value = testvars.stats_two
+ ilo =

Bug#1032642: iproute2: ip tunnel change ip6gre to gre crashes with stack smash

2023-04-03 Thread Luca Boccassi

On Mon, 3 Apr 2023 at 15:56, Stephen Hemminger
 wrote:
>
> On Sun, 2 Apr 2023 23:58:52 +0100
> Luca Boccassi  wrote:
>
> > On Sat, 25 Mar 2023 at 00:39, Bernhard Übelacker  
> > wrote:
> > >
> > > Dear Maintainer,
> > > I tried to find out where exactly the stack smashing takes place.
> > > And found the ioctl SIOCCHGTUNNEL did write more than the 52 bytes
> > > allocated in variable old_p, by that overwriting the stack canary.
> > >
> > > Kind regards,
> > > Bernhard
> > >
> > >
> > > (gdb)
> > > 0x5557589f  62  {
> > > 1: x/i $pc
> > > => 0x5557589f :  mov%fs:0x28,%rax
> > > (gdb)
> > > 0x555758a8  62  {
> > > 1: x/i $pc
> > > => 0x555758a8 :  mov%rax,0x68(%rsp)
> > > (gdb) print/x $rax
> > > $1 = 0xbf9b77d893accd00
> > > (gdb) print/x $rsp + 0x68
> > > $2 = 0x7fffea28
> > >
> > >
> > > (gdb)
> > > 0x77e575f5  120 in ../sysdeps/unix/syscall-template.S
> > > 1: x/i $pc
> > > => 0x77e575f5 :syscall
> > > 2: /x *(uint64_t*)0x7fffea28 = 0xbf9b77d893accd00
> > > (gdb) bt
> > > #0  0x77e575f5 in ioctl () at 
> > > ../sysdeps/unix/syscall-template.S:120
> > > #1  0x55578230 in tnl_get_ioctl (basedev=0x7fffee8f "gre1", 
> > > p=) at tunnel.c:77
> > > #2  0x55576243 in parse_args (argc=9, argv=0x7fffec50, 
> > > cmd=35315, p=0x7fffea70) at iptunnel.c:181
> > > #3  0x555762fb in do_add (cmd=35315, argc=, 
> > > argv=) at iptunnel.c:260
> > > #4  0x5556258b in do_cmd (argv0=0x7fffee81 "tunnel", argc=11, 
> > > argv=0x7fffec40) at ip.c:133
> > > #5  0x55561fc2 in main (argc=12, argv=0x7fffec38) at ip.c:344
> > > (gdb) stepi
> > > 0x77e575f7  120 in ../sysdeps/unix/syscall-template.S
> > > 1: x/i $pc
> > > => 0x77e575f7 :cmp$0xf001,%rax
> > > 2: /x *(uint64_t*)0x7fffea28 = 0x200
> > >
> > > (gdb) print _p
> > > $7 = (struct ip_tunnel_parm *) 0x7fffe9f0
> > > (gdb) print sizeof(old_p)
> > > $8 = 52
> > > (gdb) print/x 0x7fffe9f0 + 52
> > > $9 = 0x7fffea24
> > >
> > > (gdb) list iptunnel.c:181
> > > 178 if (cmd == SIOCCHGTUNNEL && count == 0) {
> > > 179 struct ip_tunnel_parm old_p = {};
> > > 180
> > > 181 if (tnl_get_ioctl(*argv, _p))
> > > 182 return -1;
> >
> > Hi David and Stephen,
> >
> > To reproduce, build iproute2 with -fstack-protector-strong in CFLAGS, and 
> > run:
> >
> > ip tunnel add gre1 mode ip6gre local 2001:db8::1 remote 2001:db8::2 ttl 255
> > ip tunnel change gre1 mode gre local 192.168.0.0 remote 192.168.0.1 ttl 255
> >
> > You'll get:
> >
> > *** stack smashing detected ***: terminated
> > Aborted
> >
> > This happens because iproute2 just assumes the tunnel is ipv4, but the
> > kernel "knows" it's actually ip6gre so when calling the SIOCGETTUNNEL
> > ioctl it writes back a struct ip6_tnl_parm2 into the struct
> > ip_tunnel_parm which is smaller, so the stack gets overwritten. Is
> > there any way to tell from userspace whether a gre is v4 or v6 before
> > doing an ioctl? The ioctls don't take/return a size parameter as far
> > as I can see...
>
> Is setting IPv4 addresses on an IPv6 tunnel even a valid operation?
> Assuming the ioctl to get is fixed, is there a reason to allow it?
>
> One more reason netlink is better than ioctl.

I don't know, I don't really know anything about GRE, but if it isn't,
it should be rejected earlier, rather than overwriting the stack,
which seems dangerous.

Bug#1032642: iproute2: ip tunnel change ip6gre to gre crashes with stack smash

2023-04-03 Thread Stephen Hemminger

On Sun, 2 Apr 2023 23:58:52 +0100
Luca Boccassi  wrote:

> On Sat, 25 Mar 2023 at 00:39, Bernhard Übelacker  
> wrote:
> >
> > Dear Maintainer,
> > I tried to find out where exactly the stack smashing takes place.
> > And found the ioctl SIOCCHGTUNNEL did write more than the 52 bytes
> > allocated in variable old_p, by that overwriting the stack canary.
> >
> > Kind regards,
> > Bernhard
> >
> >
> > (gdb)
> > 0x5557589f  62  {
> > 1: x/i $pc  
> > => 0x5557589f :  mov%fs:0x28,%rax  
> > (gdb)
> > 0x555758a8  62  {
> > 1: x/i $pc  
> > => 0x555758a8 :  mov%rax,0x68(%rsp)  
> > (gdb) print/x $rax
> > $1 = 0xbf9b77d893accd00
> > (gdb) print/x $rsp + 0x68
> > $2 = 0x7fffea28
> >
> >
> > (gdb)
> > 0x77e575f5  120 in ../sysdeps/unix/syscall-template.S
> > 1: x/i $pc  
> > => 0x77e575f5 :syscall  
> > 2: /x *(uint64_t*)0x7fffea28 = 0xbf9b77d893accd00
> > (gdb) bt
> > #0  0x77e575f5 in ioctl () at ../sysdeps/unix/syscall-template.S:120
> > #1  0x55578230 in tnl_get_ioctl (basedev=0x7fffee8f "gre1", 
> > p=) at tunnel.c:77
> > #2  0x55576243 in parse_args (argc=9, argv=0x7fffec50, 
> > cmd=35315, p=0x7fffea70) at iptunnel.c:181
> > #3  0x555762fb in do_add (cmd=35315, argc=, 
> > argv=) at iptunnel.c:260
> > #4  0x5556258b in do_cmd (argv0=0x7fffee81 "tunnel", argc=11, 
> > argv=0x7fffec40) at ip.c:133
> > #5  0x55561fc2 in main (argc=12, argv=0x7fffec38) at ip.c:344
> > (gdb) stepi
> > 0x77e575f7  120 in ../sysdeps/unix/syscall-template.S
> > 1: x/i $pc  
> > => 0x77e575f7 :cmp$0xf001,%rax  
> > 2: /x *(uint64_t*)0x7fffea28 = 0x200
> >
> > (gdb) print _p
> > $7 = (struct ip_tunnel_parm *) 0x7fffe9f0
> > (gdb) print sizeof(old_p)
> > $8 = 52
> > (gdb) print/x 0x7fffe9f0 + 52
> > $9 = 0x7fffea24
> >
> > (gdb) list iptunnel.c:181
> > 178 if (cmd == SIOCCHGTUNNEL && count == 0) {
> > 179 struct ip_tunnel_parm old_p = {};
> > 180
> > 181 if (tnl_get_ioctl(*argv, _p))
> > 182 return -1;  
> 
> Hi David and Stephen,
> 
> To reproduce, build iproute2 with -fstack-protector-strong in CFLAGS, and run:
> 
> ip tunnel add gre1 mode ip6gre local 2001:db8::1 remote 2001:db8::2 ttl 255
> ip tunnel change gre1 mode gre local 192.168.0.0 remote 192.168.0.1 ttl 255
> 
> You'll get:
> 
> *** stack smashing detected ***: terminated
> Aborted
> 
> This happens because iproute2 just assumes the tunnel is ipv4, but the
> kernel "knows" it's actually ip6gre so when calling the SIOCGETTUNNEL
> ioctl it writes back a struct ip6_tnl_parm2 into the struct
> ip_tunnel_parm which is smaller, so the stack gets overwritten. Is
> there any way to tell from userspace whether a gre is v4 or v6 before
> doing an ioctl? The ioctls don't take/return a size parameter as far
> as I can see...

Is setting IPv4 addresses on an IPv6 tunnel even a valid operation?
Assuming the ioctl to get is fixed, is there a reason to allow it?

One more reason netlink is better than ioctl.

Bug#1033894: lintian: bad-distribution-in-changes-file bookworm

2023-04-03 Thread Andreas Beckmann

Package: lintian
Version: 2.116.3
Severity: normal

Lintian does not like my t-p-u upload:

https://salsa.debian.org/opencl-team/pocl/-/jobs/4107810/raw
E: pocl changes: bad-distribution-in-changes-file bookworm

TTBOMK, $codename is the recommended distribution value for uploads to
{testing,(old)*stable}-proposed-updates.


Andreas

Bug#1033893: unblock: mailutils/1:3.15-4

2023-04-03 Thread Jordi Mallach

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: mailut...@packages.debian.org
Control: affects -1 + src:mailutils

Please unblock package mailutils

I tried getting this before the start of the freeze, but apparently was
a few hours late.

This revision just fixes a long standing crash in mail(1), which is
related to certain locale setting.

The patch to the actual fix is a two-liner, but this upload also
included some other minor packaging tweaks like updating
Standards-Version or lintian overrides.

[ 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 testing

unblock mailutils/1:3.15-4
diff -Nru mailutils-3.15/debian/changelog mailutils-3.15/debian/changelog
--- mailutils-3.15/debian/changelog 2022-09-13 23:16:02.0 +0200
+++ mailutils-3.15/debian/changelog 2023-03-03 17:00:20.0 +0100
@@ -1,3 +1,16 @@
+mailutils (1:3.15-4) unstable; urgency=medium
+
+  [ Debian Janitor ]
+  * Update lintian override info to new format on line 1.
+  * Update standards version to 4.6.1, no changes needed.
+
+  [ Jordi Mallach ]
+  * Add patch from Dave Love to fix a locale-related crash
+(closes: #944372, #1031702).
+  * Update Standards-Version to 4.6.2, with no changes needed.
+
+ -- Jordi Mallach   Fri, 03 Mar 2023 17:00:20 +0100
+
 mailutils (1:3.15-3) unstable; urgency=medium
 
   [ Jordi Mallach ]
diff -Nru mailutils-3.15/debian/control mailutils-3.15/debian/control
--- mailutils-3.15/debian/control   2022-09-13 21:34:33.0 +0200
+++ mailutils-3.15/debian/control   2023-03-03 16:52:35.0 +0100
@@ -30,7 +30,7 @@
python3-dev,
texinfo,
zlib1g-dev
-Standards-Version: 4.6.0
+Standards-Version: 4.6.2
 Vcs-Git: https://salsa.debian.org/debian/mailutils.git
 Vcs-Browser: https://salsa.debian.org/debian/mailutils
 Homepage: https://www.gnu.org/software/mailutils/
diff -Nru mailutils-3.15/debian/mailutils.lintian-overrides 
mailutils-3.15/debian/mailutils.lintian-overrides
--- mailutils-3.15/debian/mailutils.lintian-overrides   2022-04-18 
16:45:34.0 +0200
+++ mailutils-3.15/debian/mailutils.lintian-overrides   2023-03-03 
15:26:36.0 +0100
@@ -1 +1 @@
-mailutils: elevated-privileges usr/bin/dotlock.mailutils 2755 root/root
+mailutils: elevated-privileges 2755 root/root [usr/bin/dotlock.mailutils]
diff -Nru mailutils-3.15/debian/patches/locale_crash.patch 
mailutils-3.15/debian/patches/locale_crash.patch
--- mailutils-3.15/debian/patches/locale_crash.patch1970-01-01 
01:00:00.0 +0100
+++ mailutils-3.15/debian/patches/locale_crash.patch2023-03-03 
15:31:36.0 +0100
@@ -0,0 +1,35 @@
+From f7fa005e21c56aae550c71d1ebc43030e1063601 Mon Sep 17 00:00:00 2001
+From: Sergey Poznyakoff 
+Date: Tue, 21 Feb 2023 14:18:34 +0200
+Subject: Fix coredump in mail.
+
+Patch proposed by Dave Love 
+
+* mail/util.c (util_get_charset): Check if charset is not NULL
+before strdup'ing it.
+---
+ mail/util.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/mail/util.c b/mail/util.c
+index b7a8e07..710b2af 100644
+--- a/mail/util.c
 b/mail/util.c
+@@ -1218,12 +1218,12 @@ util_get_charset (void)
+ {
+   struct mu_lc_all lc_all = { .flags = 0 };
+   char *tmp = getenv ("LC_ALL");
+-  if (!tmp)
++  if (!tmp || !*tmp)
+   tmp = getenv ("LANG");
+ 
+   if (tmp && mu_parse_lc_all (tmp, _all, MU_LC_CSET) == 0)
+   {
+-charset = mu_strdup (lc_all.charset);
++charset = lc_all.charset ? mu_strdup (lc_all.charset) : NULL;
+ mu_lc_all_free (_all);
+   }
+   else
+-- 
+cgit v1.1
+
diff -Nru mailutils-3.15/debian/patches/series 
mailutils-3.15/debian/patches/series
--- mailutils-3.15/debian/patches/series2022-04-18 16:45:34.0 
+0200
+++ mailutils-3.15/debian/patches/series2023-03-03 15:32:42.0 
+0100
@@ -1,3 +1,4 @@
 set_mu_sieve_moddir.patch
 guile-3.0.patch
 fix_libpq_include.patch
+locale_crash.patch

Bug#1033892: stoken: Request to update to v0.93

2023-04-03 Thread Sudip Mukherjee

Source: stoken
Version: 0.92-1
Severity: wishlist
X-Debbugs-Cc: sudipm.mukher...@gmail.com

Dear Maintainer,

stoken source is now available at https://github.com/stoken-dev/stoken
and upstream has released v0.93 last month. It will be good to have it
in Debian.


-- 
Regards
Sudip

Bug#1033891: RM: sakia -- ROM (team); upstream abandoned; only in experimental


Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

sakia has never seen an unstable upload. Its upstream says it is "UNMAINTAINED".
Please remove sakia from the archive.

Bug#1033888: ITP: usbscale -- read weight data from a USB scale

2023-04-03 Thread No reply

Здравствуйте!

Сообщения, пришедшие на адрес no-re...@decast.com не обрабатываются.
Пожалуйста, уточните получателя и повторно отправьте ему Ваше сообщение.

С уважением,
Decast group

-
Hello!

Messages that delivered to the address no-re...@decast.com not processed.

Please check the recipient's address and send them your message again.

Sincerely,
Decast group

Bug#1033657: grub-efi-arm64-signed: Secure Boot not working on arm64

2023-04-03 Thread Emanuele Rocca

Control: tags -1 + patch

Proposed fix:
https://salsa.debian.org/grub-team/grub/-/merge_requests/32

Bug#1032984:

2023-04-03 Thread Julien Cristau

On Sun, Mar 26, 2023 at 22:03:25 +0200, Stefan Schippers wrote:

> I have closed upstream bug:
> https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/186
> since i got no feedback at all and it seems affecting only the specific
> libX11 1.8.4 - fvwm2 combination that very few people use, I think.
> 
Expecting a response within a few days was probably unrealistic in the
first place...

Cheers,
Julien

Bug#1033890: unblock: safeeyes/2.1.5-0.1

2023-04-03 Thread Julian Gilbey

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: safee...@packages.debian.org
Control: affects -1 + src:safeeyes

Please unblock package safeeyes

[ Reason ]
The version of safeeyes in testing is very broken: (i) it
does not appear in the notification bar for (at least) KDE/Plasma and
XFCE4, making it impossible to control or defer (bug #1006942, though
for some reason that bug was not recorded as RC); (ii) it fails to
load any plugins with Python 3.11, meaning that it fails to function
correctly (most of the package runs via a plugins mechanism, loading
internal plugins; bug #1033106).

Unfortunately, though, I wasn't thinking clearly when I uploaded, and
the diff is rather bigger than it ought to have been (though the vast
majority of it is translation updates).  I'll explain more below in
the "Other info" section.

[ Impact ]
The package will only lock the screen at the chosen intervals with no
ability to control it, defer it, take account of user idle time

[ Tests ]
Unfortunately there are no autopkgtests in this package.  I did an NMU
for it recently, but have been happily running a local copy of my code
for several weeks.

[ Risks ]
It's a leaf package, and while the current diff is substantial (see
"Other info" below), the changes are all essentially trivial.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
v  [x] attach debdiff against the package in testing

[ Other info ]
I fixed #1006942 by upgrading to a new upstream version.  Given that
it was targeted for bookworm, I should have cherry-picked the relevant
patch.  If this is deemed too much for bookworm, what would you
suggest to fix it?  Should I perhaps upload a version
2.1.5+really2.1.3-0.1 which only has cherry-picked patches?

To assist, here is a list of all changed files in the debdiff and
comments on them:

safeeyes-2.1.5/debian/changelog
safeeyes-2.1.5/debian/control

  This fixes the dependencies to match the packages currently in
  testing (gir1.2-appindicator3-0.1 is no longer present, and
  gir1.2-notify-0.7 is required for the notifications to work)

safeeyes-2.1.5/debian/patches/series
safeeyes-2.1.5/debian/patches/support-python311.patch

  These introduce a one-line patch for the Python 3.11 bug; I
  haven't included DEP-3 headers in this patch, but could do if you
  would like me to.

safeeyes-2.1.5/.github/FUNDING.yml
safeeyes-2.1.5/.github/ISSUE_TEMPLATE/bug_report.md
safeeyes-2.1.5/.github/ISSUE_TEMPLATE/feature_request.md
safeeyes-2.1.5/.github/ISSUE_TEMPLATE/plugin-request.md
safeeyes-2.1.5/.github/workflows/release.yml
safeeyes-2.1.5/.gitignore

  All of these are in the upstream version but it turns out weren't
  included in the previous Debian version.  None of them are used in the
  build or end up in the binary package.

safeeyes-2.1.5/LICENSE
safeeyes-2.1.5/README.md

  URLs updated to use https rather than http

safeeyes-2.1.5/safeeyes/config/locale/*/LC_MESSAGES/safeeyes.po

  Updated translation files (this accounts for most of the bulk of the
  debdiff)

safeeyes-2.1.5/safeeyes/glade/about_dialog.glade

  URLs changed from http to https, and version number update

safeeyes-2.1.5/safeeyes/__main__.py

  A safety check to prevent crashing in case locale does not support
  bindtextdomain (though why it would not, I don't know)

safeeyes-2.1.5/safeeyes/plugins/donotdisturb/plugin.py

  This is a small bug fix.

safeeyes-2.1.5/safeeyes/plugins/smartpause/dependency_checker.py
safeeyes-2.1.5/safeeyes/plugins/smartpause/plugin.py

  This is new code to support the "sway" desktop environment.

safeeyes-2.1.5/safeeyes/plugins/trayicon/plugin.py

  This is the code which fixes Debian bug #1006942

safeeyes-2.1.5/safeeyes/safeeyes.py

  Updated version number

safeeyes-2.1.5/safeeyes/utility.py

  Support "sawy"; new check for using Wayland

safeeyes-2.1.5/setup.py

  New version number

safeeyes-2.1.5/validate_po.py

  Unused script, not included in final binary package; presumably it
  is used by the developers to check the .po files are OK.

unblock safeeyes/2.1.5-0.1
diff -Nru safeeyes-2.1.3/debian/changelog safeeyes-2.1.5/debian/changelog
--- safeeyes-2.1.3/debian/changelog 2021-09-04 19:00:04.0 +0100
+++ safeeyes-2.1.5/debian/changelog 2023-03-24 12:32:08.0 +
@@ -1,3 +1,12 @@
+safeeyes (2.1.5-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * New upstream version makes icon appear in KDE/Plasma and XFCE4 system
+tray once again (Closes: #1006942)
+  * Support Python 3.11 (Closes: #1033106)
+
+ -- Julian Gilbey   Fri, 24 Mar 2023 12:32:08 +
+
 safeeyes (2.1.3-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru safeeyes-2.1.3/debian/control safeeyes-2.1.5/debian/control
--- safeeyes-2.1.3/debian/control   2021-09-04 19:00:04.0 +0100
+++ safeeyes-2.1.5/debian/control   2023-03-24 12:32:08.0

Bug#1033889: unblock: arriero/0.7~20161228-1.2

2023-04-03 Thread Josef Schneider


Package: release.debian.org
Control: affects -1 + src:arriero
X-Debbugs-Cc: josef81...@gmail.com, t...@debian.org, m...@debian.org
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package arriero.

[ Reason ]
This update allows the program to run without error by importing the 
collections.abc python package and using it in replacement of the 
collections python package with the MutableSet attribute (see #1032380).


[ Impact ]
With this fix, the program does not throw an AttributeError when running 
the arriero --help command or other commands. arriero has no 
reverse-dependencies, so there is no impact on other packages.


[ Tests ]
dh_auto_test runs during the build and would fail the build if tests 
failed. I installed the new .deb and ran arriero --help with the 
expected output, and the updates were reviewed by the DD who signed and 
uploaded the package. I have an autopkgtest ready if needed but I kept 
the upload minimal.


[ Risks ]
arriero has no reverse-dependencies so there are no risks.

[ 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 testing

unblock: arriero/0.7~20161228-1.2

--
Josef Schneider

GPG Fingerprint 3267 0331 DB61 A817 7D25 4D05 5A44 BC12 F2A8 E58F
diff -Nru arriero-0.7~20161228/debian/changelog 
arriero-0.7~20161228/debian/changelog
--- arriero-0.7~20161228/debian/changelog   2022-04-29 01:44:11.0 
+0200
+++ arriero-0.7~20161228/debian/changelog   2023-03-24 13:10:39.0 
+0100
@@ -1,3 +1,10 @@
+arriero (0.7~20161228-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to import collections.abc in util.py (Closes: #1032380).
+
+ -- Josef Schneider   Fri, 24 Mar 2023 13:10:39 +0100
+
 arriero (0.7~20161228-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru arriero-0.7~20161228/debian/patches/0001-import-collections-abc.patch 
arriero-0.7~20161228/debian/patches/0001-import-collections-abc.patch
--- arriero-0.7~20161228/debian/patches/0001-import-collections-abc.patch   
1970-01-01 01:00:00.0 +0100
+++ arriero-0.7~20161228/debian/patches/0001-import-collections-abc.patch   
2023-03-24 13:10:39.0 +0100
@@ -0,0 +1,33 @@
+From 409dd804c2abb119582378cd6fa098ad8df01f3d Mon Sep 17 00:00:00 2001
+From: Josef Schneider 
+Date: Fri, 17 Mar 2023 13:16:43 +0100
+Subject: [PATCH] import collections.abc
+
+---
+ arriero/util.py | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/arriero/util.py b/arriero/util.py
+index 91e4121..07f877a 100644
+--- a/arriero/util.py
 b/arriero/util.py
+@@ -17,6 +17,7 @@
+ # Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
+ 
+ import collections
++import collections.abc
+ import fcntl
+ import io
+ import itertools
+@@ -185,7 +186,7 @@ def chain_map(*ds, **kw):
+ return ChainMap(*itertools.chain(ds, [kw]))
+ 
+ 
+-class OrderedSet(deb822.OrderedSet, collections.MutableSet):
++class OrderedSet(deb822.OrderedSet, collections.abc.MutableSet):
+ 
+ discard = deb822.OrderedSet.remove
+ 
+-- 
+2.38.1
+
diff -Nru arriero-0.7~20161228/debian/patches/series 
arriero-0.7~20161228/debian/patches/series
--- arriero-0.7~20161228/debian/patches/series  1970-01-01 01:00:00.0 
+0100
+++ arriero-0.7~20161228/debian/patches/series  2023-03-24 13:10:39.0 
+0100
@@ -0,0 +1 @@
+0001-import-collections-abc.patch


OpenPGP_0x5A44BC12F2A8E58F.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1033024: lios hangs when opening Preferences

2023-04-03 Thread Gunnar Hjalmarsson


On 2023-04-03 00:14, Samuel Thibault wrote:

Gunnar Hjalmarsson, le mer. 15 mars 2023 22:06:23 +0100, a ecrit:

The question to you is if you would like me to add it to the repo
and upload to experimental.


Yes, you're welcome to do it!


Ok, then I'm going to upload what I have. Hopefully it is an overall 
improvement. The patch I added isn't pretty, but proved to be needed for 
me when testing.



Or do you possibly think that the release team would approve also
this for Debian 12?


It depends on the changes size :)


Unfortunately the diff is rather big. Personally I wouldn't want to 
justify it towards the release team...


--
Rgds,
Gunnar

Bug#1033415: micro: syntax highlighting doesn't work

2023-04-03 Thread Sebastian Hörberg


Hi Nilesh,

It does indeed work as expected.

Thank you for your work!

Den 01/04/2023 kl. 21:33, skrev Nilesh Patra:

Hi Sebastian,

On Fri, 24 Mar 2023 18:33:28 +0100 =?UTF-8?Q?Sebastian_H=c3=b6rberg?= 
 wrote:

Package: micro
Version: 2.0.11-1+b1
Severity: normal
The static binary from upstream's github works as expected.

Could the debian package be missing the resource files?

I have tried to fix this with a new upload 2.0.11-2. It works fine
for me locally. Could you please consider to test with this release?

Also, if you find more bugs please in the micro debian package feel free to 
ping.

Bug#1032990: podman: Better reproducer

2023-04-03 Thread Matej Marusak

Package: podman
Version: 4.3.1+ds1-6
Followup-For: Bug #1032990
X-Debbugs-Cc: mmaru...@redhat.com

Dear Maintainer,

The original reproducer was not clear how important this failure is. It
efectively means that rootless podman is unusable on any system with
sssd.

This is easily reproducible by:
- Download newest image, e.g. 
https://cloud.debian.org/images/cloud/bullseye/daily/20230403-1339/debian-11-genericcloud-amd64-daily-20230403-1339.qcow2
- Install podman and sssd-tools and sssd-dbus. It works fine without sssd
- Login as 'admin' user
- podman pull debian

This command fails with:
ERRO[0004] While applying layer: ApplyLayer stdout:  stderr: potentially 
insufficient UIDs or GIDs available in user namespace (requested 0:42 for 
/etc/gshadow): Check /etc/subuid and /etc/subgid if configured locally and run 
podman-system-migrate: lchown /etc/gshadow: invalid argument exit status 1
Error: copying system image from manifest list: writing blob: adding layer with 
blob "sha256:3e440a7045683e27f8e2fa04000e0e078d8dfac0c971358ae0f8c65c13321c8e": 
ApplyLayer stdout:  stderr: potentially insufficient UIDs or GIDs available in 
user namespace (requested 0:42 for /etc/gshadow): Check /etc/subuid and 
/etc/subgid if configured locally and run podman-system-migrate: lchown 
/etc/gshadow: invalid argument exit status 1

It worked with some previos version. It is now broken, here is what has
changed since the working version:

Removed:
  liblua5.3-0:amd64 (5.3.6-2)
  libmpdec3:amd64 (2.5.1-2)
  libossp-uuid-perl (1.6.2-1.5+b11)
  libossp-uuid16:amd64 (1.6.2-1.5+b11)
  linux-image-6.1.0-3-cloud-amd64 (6.1.8-1)
  ncat (7.93+dfsg1-1)

Added:
  libdigest-md5-file-perl (0.08-1.1)
  libswitch-perl (2.17-3)
  linux-image-6.1.0-7-cloud-amd64 (6.1.20-1)

Changed:
  apparmor (3.0.8-2+b1 -> 3.0.8-3)
  apt (2.5.6 -> 2.6.0)
  apt-utils (2.5.6 -> 2.6.0)
  autopoint (0.21-11 -> 0.21-12)
  base-files (12.3 -> 12.4)
  bind9-dnsutils (1:9.18.11-2 -> 1:9.18.12-1)
  bind9-host (1:9.18.11-2 -> 1:9.18.12-1)
  bind9-libs:amd64 (1:9.18.11-2 -> 1:9.18.12-1)
  bsdextrautils (2.38.1-4 -> 2.38.1-5+b1)
  bsdutils (1:2.38.1-4 -> 1:2.38.1-5+b1)
  buildah (1.28.2+ds1-1+b1 -> 1.28.2+ds1-1+b2)
  busybox (1:1.35.0-4+b1 -> 1:1.35.0-4+b2)
  ca-certificates (20211016 -> 20230311)
  cloud-initramfs-growroot (0.18.debian11 -> 0.18.debian12)
  cockpit (284-1 -> 287-1)
  cockpit-bridge (284-1 -> 287-1)
  cockpit-system (284-1 -> 287-1)
  cockpit-ws (284-1 -> 287-1)
  conmon (2.1.3+ds1-1 -> 2.1.6+ds1-1)
  containernetworking-plugins (1.1.1+ds1-3+b2 -> 1.1.1+ds1-3+b3)
  cron (3.0pl1-156 -> 3.0pl1-162)
  cron-daemon-common (3.0pl1-156 -> 3.0pl1-162)
  crun (1.8-1 -> 1.8.1-1)
  cryptsetup (2:2.6.1-1 -> 2:2.6.1-3~deb12u1)
  cryptsetup-bin (2:2.6.1-1 -> 2:2.6.1-3~deb12u1)
  curl (7.87.0-2 -> 7.88.1-7)
  debian-archive-keyring (2021.1.1 -> 2023.2)
  devscripts (2.22.2 -> 2.23.2)
  dirmngr (2.2.40-1 -> 2.2.40-1.1)
  distro-info-data (0.56 -> 0.57)
  dpkg (1.21.20 -> 1.21.21)
  dpkg-dev (1.21.20 -> 1.21.21)
  eject (2.38.1-4 -> 2.38.1-5+b1)
  fakeroot (1.29-1 -> 1.31-1.1)
  fdisk (2.38.1-4 -> 2.38.1-5+b1)
  fonts-dejavu-core (2.37-2 -> 2.37-6)
  fuse3 (3.13.0-2 -> 3.14.0-2)
  gawk (1:5.1.0-1 -> 1:5.2.1-2)
  gdb (12.1-4+b1 -> 13.1-2)
  gettext (0.21-11 -> 0.21-12)
  gettext-base (0.21-11 -> 0.21-12)
  git (1:2.39.1-0.1 -> 1:2.39.2-1.1)
  git-man (1:2.39.1-0.1 -> 1:2.39.2-1.1)
  glib-networking-common (2.74.0-2 -> 2.74.0-4)
  glib-networking-services (2.74.0-2 -> 2.74.0-4)
  glib-networking:amd64 (2.74.0-2 -> 2.74.0-4)
  gnupg (2.2.40-1 -> 2.2.40-1.1)
  gnupg-l10n (2.2.40-1 -> 2.2.40-1.1)
  gnupg-utils (2.2.40-1 -> 2.2.40-1.1)
  gnutls-bin (3.7.8-5 -> 3.7.9-1)
  gpg (2.2.40-1 -> 2.2.40-1.1)
  gpg-agent (2.2.40-1 -> 2.2.40-1.1)
  gpg-wks-client (2.2.40-1 -> 2.2.40-1.1)
  gpg-wks-server (2.2.40-1 -> 2.2.40-1.1)
  gpgconf (2.2.40-1 -> 2.2.40-1.1)
  gpgsm (2.2.40-1 -> 2.2.40-1.1)
  gpgv (2.2.40-1 -> 2.2.40-1.1)
  groff-base (1.22.4-9 -> 1.22.4-10)
  gstreamer1.0-plugins-good:amd64 (1.22.0-4 -> 1.22.0-5)
  gtk-update-icon-cache (3.24.36-3 -> 3.24.37-2)
  intel-media-va-driver:amd64 (23.1.0+dfsg1-1 -> 23.1.1+dfsg1-1)
  iproute2 (6.1.0-1 -> 6.1.0-2)
  ipset (7.15-1+b1 -> 7.17-1)
  iso-codes (4.12.0-1 -> 4.13.0-1)
  klibc-utils (2.0.11-1 -> 2.0.12-1)
  less (590-1.1 -> 590-1.2)
  libann0 (1.1.2+doc-9 -> 1.1.2+doc-9+b1)
  libaom3:amd64 (3.5.0-1 -> 3.6.0-1)
  libapparmor1:amd64 (3.0.8-2+b1 -> 3.0.8-3)
  libapt-pkg6.0:amd64 (2.5.6 -> 2.6.0)
  libass9:amd64 (1:0.17.0-2 -> 1:0.17.1-1)
  libavahi-client3:amd64 (0.8-8 -> 0.8-9)
  libavahi-common-data:amd64 (0.8-8 -> 0.8-9)
  libavahi-common3:amd64 (0.8-8 -> 0.8-9)
  libavcodec59:amd64 (7:5.1.2-2 -> 7:5.1.2-3)
  libavfilter8:amd64 (7:5.1.2-2 -> 7:5.1.2-3)
  libavformat59:amd64 (7:5.1.2-2 ->

Bug#1005272: NMU: libxt6: out-of-date copyright file


I am uploading the d/copyright change as a NMU. debdiff is attached.diff -u libxt-1.2.1/debian/changelog libxt-1.2.1/debian/changelog
--- libxt-1.2.1/debian/changelog
+++ libxt-1.2.1/debian/changelog
@@ -1,3 +1,12 @@
+libxt (1:1.2.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Timo Aaltonen ]
+  * copyright: Synced with upstream. (Closes: #1005272)
+
+ -- Bastian Germann   Mon, 03 Apr 2023 15:51:04 +0200
+
 libxt (1:1.2.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -u libxt-1.2.1/debian/copyright libxt-1.2.1/debian/copyright
--- libxt-1.2.1/debian/copyright
+++ libxt-1.2.1/debian/copyright
@@ -1,6 +1,25 @@
 This package was downloaded from
 http://xorg.freedesktop.org/releases/individual/lib/
 
+Copyright © 2003,2019 Thomas E. Dickey
+
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL THE
+ABOVE LISTED COPYRIGHT HOLDER(S) BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
 
 Copyright © 2001,2003 Keith Packard

Bug#1033888: ITP: usbscale -- read weight data from a USB scale

2023-04-03 Thread John Scott

Package: wnpp
Severity: wishlist
Owner: John Scott 
Tags: newcomer
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name    : usbscale
  Upstream Contact: Eric Jiang
* URL : https://github.com/erjiang/usbscale
* License : GPL 3.0 or any later version
  Programming Lang: C
  Description : read weight data from a USB scale

This package provides a utility one can use to read data from various
USB scales, ones which are sold as postage scales in particular.

Even though the program is very small, I still think it belongs in
Debian. As far as I know, there are no applications in Debian that are
capable of reading this sort of data. With usbscale, it's easy for
medium-volume mailers to have scripts or utilities that talk to usbscale
and, say, do automatic postage price computation. I use this application
sometimes.

I'm not a Debian Developer and will need a sponsor. I can't think of any
pertinent teams to maintain it in, but since it's a small package, I see
no problem with maintaining it on my own.

I am familiar with Debian Packaging and will probably be able to get
this out in the next few days.


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

Bug#1033887: libcurl 7.74.0-1.3+deb11u7 regression

2023-04-03 Thread Blaise Vogel

Package: amanda-common
Version: 1:3.5.1-7
Severity: important

Since version 7.74.0-1.3+deb11u7 of libcurl, we can no longer use S3 or 
Openstack changer.
Following error occurs, by example with amlabel:

Error writing label: While writing amanda header: The request signature we 
calculated does not match the signature you provided. Check your key and 
signing method. (SignatureDoesNotMatch) (HTTP 403).

Returning to the previous version solve the problem.

apt install libcurl4=7.74.0-1.3+deb11u3 

Debian Bullseye - Kernel 5.10.0-21-amd64

Bug#1033886: unblock: mdbtools/1.0.0+dfsg-1.1


Package: release.debian.org
Control: affects -1 + src:mdbtools
X-Debbugs-Cc: mdbto...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package mdbtools.

[ Reason ]
Fixes RC bug #1001144.

[ Impact ]
The package will be auto-removed from bookworm without unblock.

[ Tests ]
postinst and prerm fail without odbcinst installed.

[ Risks ]
Only a Depends is added; trivial.

[ 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 testing

unblock mdbtools/1.0.0+dfsg-1.1diff -Nru mdbtools-1.0.0+dfsg/debian/changelog 
mdbtools-1.0.0+dfsg/debian/changelog
--- mdbtools-1.0.0+dfsg/debian/changelog2021-10-31 15:01:12.0 
+0100
+++ mdbtools-1.0.0+dfsg/debian/changelog2023-04-03 14:53:52.0 
+0200
@@ -1,3 +1,11 @@
+mdbtools (1.0.0+dfsg-1.1) unstable; urgency=medium
+
+  [ Wookey ]
+  * Non-maintainer upload.
+  * Add dependency on obdcinst for odbc-mdbtools. (Closes:#1001144)
+
+ -- Bastian Germann   Mon, 03 Apr 2023 14:53:52 +0200
+
 mdbtools (1.0.0+dfsg-1) unstable; urgency=medium
 
   * New upstream release:
diff -Nru mdbtools-1.0.0+dfsg/debian/control mdbtools-1.0.0+dfsg/debian/control
--- mdbtools-1.0.0+dfsg/debian/control  2021-10-31 14:56:49.0 +0100
+++ mdbtools-1.0.0+dfsg/debian/control  2023-04-03 14:52:12.0 +0200
@@ -76,7 +76,7 @@
 Multi-Arch: same
 Section: libs
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, odbcinst
 Recommends: libodbc1
 Breaks: libiodbc2 (<< 3.52.7-2+deb7u1),
 libmdbodbc1 (<< 0.7.1-1~),

Bug#1033885: unblock: pydevd/2.9.5+ds-4

2023-04-03 Thread Julian Gilbey

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: pyd...@packages.debian.org
Control: affects -1 + src:pydevd

Please unblock package pydevd

[ Reason ]
This is a small tweak to the autopkgtests to prevent them from failing
on a number of architectures not in the released architectures.  It
closes #1029718, but I don't know whether it is appropriate for
transitioning to testing (it not being an RC bug).

[ Impact ]
It is not currently buildable on those architectures.

[ Tests ]
The autopkgtests cover everything; this patch just excludes some which
fail with Python 3.11.

[ Risks ]
Code is trivial and only in the autopkgtest code.

[ 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 testing

[ Other info ]
None

unblock pydevd/2.9.5+ds-4
diff -Nru pydevd-2.9.5+ds/debian/changelog pydevd-2.9.5+ds/debian/changelog
--- pydevd-2.9.5+ds/debian/changelog2023-02-11 21:30:07.0 +
+++ pydevd-2.9.5+ds/debian/changelog2023-03-12 12:36:38.0 +
@@ -1,3 +1,10 @@
+pydevd (2.9.5+ds-4) unstable; urgency=medium
+
+  * Exclude failing tests on a wider variety of architectures
+(closes: #1029718)
+
+ -- Julian Gilbey   Sun, 12 Mar 2023 12:36:38 +
+
 pydevd (2.9.5+ds-3) unstable; urgency=medium
 
   * Update README.Debian
diff -Nru pydevd-2.9.5+ds/debian/get_test_exclusions 
pydevd-2.9.5+ds/debian/get_test_exclusions
--- pydevd-2.9.5+ds/debian/get_test_exclusions  2023-02-11 21:30:07.0 
+
+++ pydevd-2.9.5+ds/debian/get_test_exclusions  2023-03-12 12:36:38.0 
+
@@ -91,10 +91,25 @@
 tests_python/test_debugger_json.py::test_function_breakpoints_async
 )
 
-# s390x fails even more disastrously
-if [ $arch = s390x ]
+# failing tests on 32-bit big-endian targets and riscv64
+if [ $arch = hppa -o $arch = m68k -o $arch = powerpc -o $arch = riscv64 ]
 then
-   EXCLUDES+=(
+EXCLUDES+=(
+tests_python/test_debugger.py::test_gevent
+tests_python/test_debugger.py::test_gevent_remote
+tests_python/test_debugger_json.py::test_wait_for_attach_gevent
+
tests_python/test_debugger_json.py::test_gevent_show_paused_greenlets
+
tests_python/test_debugger_json.py::test_gevent_subprocess_not_python
+tests_python/test_debugger_json.py::test_gevent_subprocess_python
+tests_python/test_debugger_json.py::test_notify_gevent
+tests_python/test_utilities.py::test_gevent_notify
+)
+fi
+
+# failing tests on 64-bit big-endian targets
+if [ $arch = s390x -o $arch = s390x -o $arch = sparc64 ]
+then
+EXCLUDES+=(
 tests_python/test_debugger.py::test_case_13
 tests_python/test_debugger.py::test_check_tracer_with_exceptions
 tests_python/test_debugger.py::test_unhandled_exceptions_basic
@@ -106,7 +121,19 @@
 
tests_python/test_debugger_json.py::test_case_unhandled_exception[_debugger_case_unhandled_exceptions.py]
 
tests_python/test_debugger_json.py::test_case_unhandled_exception[_debugger_case_unhandled_exceptions_custom.py]
 tests_python/test_utilities.py::test_tracing_basic
-   )
+)
+fi
+
+# Further failing tests on riscv64 (see bug#1024680)
+if [ $arch = riscv64 ]
+then
+EXCLUDES+=(
+tests_python/test_debugger.py::test_attach_to_pid_no_threads[False]
+tests_python/test_debugger.py::test_attach_to_pid_halted
+tests_python/test_debugger.py::test_case_16_resolve_numpy_array
+
tests_python/test_debugger.py::test_gevent_show_paused_greenlets[False]
+tests_python/test_debugger_json.py::test_attach_to_pid[False]
+)
 fi
 fi
 
@@ -127,7 +154,7 @@
 
tests_python/test_debugger.py::test_case_django_template_inherits_no_exception
 tests_python/test_debugger.py::test_case_flask
 tests_python/test_debugger_json.py::test_attach_to_pid[True]
-   tests_python/test_debugger_json.py::test_case_django_line_validation
+tests_python/test_debugger_json.py::test_case_django_line_validation
 
tests_python/test_debugger_json.py::test_case_django_no_attribute_exception_breakpoint
 tests_python/test_debugger_json.py::test_case_flask_line_validation
 tests_python/test_debugger_json.py::test_code_reload
@@ -138,30 +165,10 @@
 )
 fi
 
-# Further failing tests on riscv64 (see bug#1024680)
-if [ $arch = riscv64 ]
-then
-EXCLUDES+=(
-tests_python/test_debugger.py::test_attach_to_pid_no_threads[False]
-tests_python/test_debugger.py::test_attach_to_pid_halted
-tests_python/test_debugger.py::test_case_16_resolve_numpy_array
-tests_python/test_debugger.py::test_gevent
-

Bug#1033406: licensecheck: scan-copyrights fails to create copyright file for texlive-extra

2023-04-03 Thread Vignesh Raman


On Sun, 02 Apr 2023 17:41:19 +0200 Dominique Dumont  wrote:
> On Thu, 30 Mar 2023 08:15:44 +0530 Vignesh Raman 
 wrote:
> > Could you please look into this issue with the details provided? 
Thank you.

>
> With the setup you mentionned, I get this error message:
>
> Invalid year range: 2012-11-06 at 
/home/domi/private/debian-dev/perl-stuff/libconfig-model-dpkg-perl/lib/Dpkg/Copyright/Scanner.pm 
line 723.
> Invalid year range: 2015-01-11 at 
/home/domi/private/debian-dev/perl-stuff/libconfig-model-dpkg-perl/lib/Dpkg/Copyright/Scanner.pm 
line 723.
> Can't call method "consolidate" on an undefined value at 
/home/domi/private/debian-dev/perl-stuff/libconfig-model-dpkg-perl/lib/Dpkg/Copyright/Scanner.pm 
line 731.

>
> Are you getting this error message as well ?
>

Yes. I'm getting the same error messages.

Invalid year range: 2012-11-06 at 
/usr/share/perl5/Dpkg/Copyright/Scanner.pm line 724.
Invalid year range: 2015-01-11 at 
/usr/share/perl5/Dpkg/Copyright/Scanner.pm line 724.
Can't call method "consolidate" on an undefined value at 
/usr/share/perl5/Dpkg/Copyright/Scanner.pm line 732.


Regards,
Vignesh

Bug#1032948: linux-image-6.1.0-5-amd64: oops in ucsi_acpi_notify

2023-04-03 Thread Diederik de Haas

On Saturday, 18 March 2023 23:10:39 CEST Diederik de Haas wrote:
On Monday, 3 April 2023 14:57:02 CEST Julien Cristau wrote:
> > Not sure why patchwork still shows v2 of the patch as v4 is available
> > here:
> > https://lore.kernel.org/all/20230308154244.722337-1-hdego...@redhat.com/
> I'll give the patch series you linked in the other reply a go now.

FTR: 2 out of the 3 patches have landed in 6.1.22

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

Bug#1001144: NMU: Bug#1001144: Info received (odbc-mdbtools: Missing dependency on odbcinst)


I have uploaded a NMU to fix this. The change is also available in the git 
repository.diff -Nru mdbtools-1.0.0+dfsg/debian/changelog 
mdbtools-1.0.0+dfsg/debian/changelog
--- mdbtools-1.0.0+dfsg/debian/changelog2021-10-31 15:01:12.0 
+0100
+++ mdbtools-1.0.0+dfsg/debian/changelog2023-04-03 14:53:52.0 
+0200
@@ -1,3 +1,11 @@
+mdbtools (1.0.0+dfsg-1.1) unstable; urgency=medium
+
+  [ Wookey ]
+  * Non-maintainer upload.
+  * Add dependency on obdcinst for odbc-mdbtools. (Closes:#1001144)
+
+ -- Bastian Germann   Mon, 03 Apr 2023 14:53:52 +0200
+
 mdbtools (1.0.0+dfsg-1) unstable; urgency=medium
 
   * New upstream release:
diff -Nru mdbtools-1.0.0+dfsg/debian/control mdbtools-1.0.0+dfsg/debian/control
--- mdbtools-1.0.0+dfsg/debian/control  2021-10-31 14:56:49.0 +0100
+++ mdbtools-1.0.0+dfsg/debian/control  2023-04-03 14:52:12.0 +0200
@@ -76,7 +76,7 @@
 Multi-Arch: same
 Section: libs
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, odbcinst
 Recommends: libodbc1
 Breaks: libiodbc2 (<< 3.52.7-2+deb7u1),
 libmdbodbc1 (<< 0.7.1-1~),

Bug#1032948: linux-image-6.1.0-5-amd64: oops in ucsi_acpi_notify

2023-04-03 Thread Julien Cristau

On Thu, Mar 16, 2023 at 20:39:51 +0100, Diederik de Haas wrote:

> On Thursday, 16 March 2023 18:11:27 CET Julien Cristau wrote:
> > > I rebooted on 6.1.15-1 last night and things are still looking good so
> > > I'll call this fixed.  Thanks.
> > 
> > Spoke too soon:
> > > [84564.498495] BUG: kernel NULL pointer dereference, address:
> > > 0398 [84564.498502] #PF: supervisor write access in kernel
> > > mode
> > > [84564.498504] #PF: error_code(0x0002) - not-present page
> > > [84564.498506] PGD 4c9444067 P4D 4c9444067 PUD 0
> > > [84564.498510] Oops: 0002 [#1] PREEMPT SMP NOPTI
> > > [84564.498512] CPU: 0 PID: 140651 Comm: kworker/0:0 Not tainted
> > > 6.1.0-6-amd64 #1  Debian 6.1.15-1 [84564.498516] Hardware name: LENOVO
> > > 20XW00ABUS/20XW00ABUS, BIOS N32ET82W (1.58 ) 12/05/2022 [84564.498518]
> > > Workqueue: kacpi_notify acpi_os_execute_deferred
> 
> Bummer.
> 
> Since 6.1.8 I found the following 2 commits in drivers/usb/typec/ucsi:
> 
> 3d7f77e55da3455c8844b651e37779c90e201f48 titled
> "usb: ucsi: Ensure connector delayed work items are flushed"
> 
> fdd11d7136fd070b3a74d6d8799d9eac28a57fc5 titled
> "usb: typec: ucsi: Don't attempt to resume the ports before they exist"
> 
> Especially the first one looks 'promising'.
> Can you make a patch which reverts that commit and use 'test-patches' from
> https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html
> to build a kernel and test that?

Reverting "usb: ucsi: Ensure connector delayed work items are flushed"
doesn't fix the crash, pretty much instant upon unplugging my monitor.

I'll give the patch series you linked in the other reply a go now.

Cheers,
Julien

> [   34.956155] usb 3-6: USB disconnect, device number 4
> [   34.956164] usb 3-6.1: USB disconnect, device number 6
> [   34.956167] usb 3-6.1.4: USB disconnect, device number 8
> [   34.995650] usb 2-3: USB disconnect, device number 2
> [   34.995654] usb 2-3.1: USB disconnect, device number 3
> [   34.995655] usb 2-3.1.2: USB disconnect, device number 4
> [   34.995778] cdc_ncm 2-3.1.2:2.0 enxc84bd6b0b3e0: unregister 'cdc_ncm' 
> usb-:00:0d.0-3.1.2, CDC NCM (NO ZLP)
> [   35.449317] usb 3-6.5: USB disconnect, device number 7
> [   35.843033] BUG: kernel NULL pointer dereference, address: 0388
> [   35.843040] #PF: supervisor write access in kernel mode
> [   35.843041] #PF: error_code(0x0002) - not-present page
> [   35.843043] PGD 0 P4D 0 
> [   35.843046] Oops: 0002 [#1] PREEMPT SMP NOPTI
> [   35.843048] CPU: 0 PID: 2704 Comm: kworker/0:3 Tainted: GE 
>  6.1.0-7-amd64 #1  Debian 6.1.20-1a~test
> [   35.843051] Hardware name: LENOVO 20XW00ABUS/20XW00ABUS, BIOS N32ET82W 
> (1.58 ) 12/05/2022
> [   35.843052] Workqueue: kacpi_notify acpi_os_execute_deferred
> [   35.843058] RIP: 0010:queue_work_on+0x15/0x40
> [   35.843063] Code: ff ff ff e9 9a fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 
> 66 90 0f 1f 44 00 00 53 9c 58 0f 1f 40 00 48 89 c3 fa 0f 1f 44 00 00  48 
> 0f ba 2a 00 73 15 31 c9 80 e7 02 74 06 fb 0f 1f 44 00 00 89
> [   35.843065] RSP: 0018:b4a50467be38 EFLAGS: 00010002
> [   35.843067] RAX: 0202 RBX: 0202 RCX: 
> 
> [   35.843069] RDX: 0388 RSI: 8a0640051000 RDI: 
> 2000
> [   35.843070] RBP: 0004 R08: 8a06fa490a38 R09: 
> 8a06fa490a20
> [   35.843071] R10: 000f R11: b4a50467bc20 R12: 
> 8a0d7f639b00
> [   35.843072] R13:  R14: 8a06c642a9c0 R15: 
> 8a06bc057918
> [   35.843074] FS:  () GS:8a0d7f60() 
> knlGS:
> [   35.843075] CS:  0010 DS:  ES:  CR0: 80050033
> [   35.843076] CR2: 0388 CR3: 00039d410004 CR4: 
> 00770ef0
> [   35.843078] PKRU: 5554
> [   35.843079] Call Trace:
> [   35.843082]  
> [   35.843087]  ucsi_acpi_notify+0xa8/0xc0 [ucsi_acpi]
> [   35.843092]  acpi_ev_notify_dispatch+0x42/0x60
> [   35.843096]  acpi_os_execute_deferred+0x13/0x20
> [   35.843099]  process_one_work+0x1c4/0x380
> [   35.843102]  worker_thread+0x4d/0x380
> [   35.843105]  ? _raw_spin_lock_irqsave+0x23/0x50
> [   35.843109]  ? rescuer_thread+0x3a0/0x3a0
> [   35.843111]  kthread+0xe6/0x110
> [   35.843114]  ? kthread_complete_and_exit+0x20/0x20
> [   35.843116]  ret_from_fork+0x1f/0x30
> [   35.843121]  
> [   35.843122] Modules linked in: xt_conntrack(E) nft_chain_nat(E) 
> xt_MASQUERADE(E) nf_nat(E) nf_conntrack_netlink(E) nf_conntrack(E) 
> nf_defrag_ipv6(E) nf_defrag_ipv4(E) xfrm_user(E) xfrm_algo(E) xt_addrtype(E) 
> nft_compat(E) nf_tables(E) libcrc32c(E) nfnetlink(E) br_netfilter(E) 
> bridge(E) stp(E) llc(E) ctr(E) ccm(E) rfcomm(E) cmac(E) algif_hash(E) 
> algif_skcipher(E) af_alg(E) snd_seq_dummy(E) snd_hrtimer(E) snd_seq(E) 
> snd_seq_device(E) qrtr(E) overlay(E) bnep(E) ipmi_devintf(E) 
> ipmi_msghandler(E) binfmt_misc(E) nls_ascii(E) nls_cp437(E) vfat(E) fat(E) 
> snd_ctl_led(E)

Bug#1033883: plasma-nm dont show network activity in plasma monitor

2023-04-03 Thread didier


Package: plasma-nm
Version: 4:5.27.3-1
Severity: normal

Dear Maintainer,

I dont use a networkmanager to configure my wired connection. I only use the
interfaces file;
and plasma-nm dont shows the eth0 interface, so nothing appears in plasma
monitor


-- System Information:
Debian Release: 12.0
APT prefers testing
APT policy: (985, 'testing'), (530, 'stable'), (500, 
'testing-security'), (500, 'stable-updates'), (500, 'stable-security'), 
(98, 'unstable'), (96, 'experimental')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages plasma-nm depends on:
ii kio 5.103.0-1
ii libc6 2.36-8
ii libglib2.0-0 2.74.6-1
ii libkf5completion5 5.103.0-1
ii libkf5configcore5 5.103.0-1
ii libkf5configwidgets5 5.103.0-1
ii libkf5coreaddons5 5.103.0-1
ii libkf5dbusaddons5 5.103.0-1
ii libkf5i18n5 5.103.0-1
ii libkf5kiogui5 5.103.0-1
ii libkf5kiowidgets5 5.103.0-1
ii libkf5modemmanagerqt6 5.103.0-1
ii libkf5networkmanagerqt6 5.103.0-1
ii libkf5notifications5 5.103.0-1
ii libkf5solid5 5.103.0-1
ii libkf5wallet-bin 5.103.0-1
ii libkf5wallet5 5.103.0-1
ii libkf5widgetsaddons5 5.103.0-1
ii libkf5windowsystem5 5.103.0-1
ii libnm0 1.42.0-1
ii libopenconnect5 9.01-3
ii libqca-qt5-2 2.3.5-2
ii libqt5core5a 5.15.8+dfsg-3
ii libqt5dbus5 5.15.8+dfsg-3
ii libqt5gui5 5.15.8+dfsg-3
ii libqt5network5 5.15.8+dfsg-3
ii libqt5qml5 5.15.8+dfsg-3
ii libqt5quickwidgets5 5.15.8+dfsg-3
ii libqt5widgets5 5.15.8+dfsg-3
ii libqt5xml5 5.15.8+dfsg-3
ii libstdc++6 12.2.0-14
ii mobile-broadband-provider-info 20221107-1
ii network-manager 1.42.0-1
ii plasma-framework 5.103.0-1
ii qml-module-org-kde-kcoreaddons 5.103.0-1
ii qml-module-org-kde-kirigami2 5.103.0-1
ii qml-module-org-kde-prison 5.103.0-1

Versions of packages plasma-nm recommends:
ii systemsettings 4:5.27.2-1

Versions of packages plasma-nm suggests:
pn network-manager-fortisslvpn 
pn network-manager-iodine 
pn network-manager-l2tp 
pn network-manager-openconnect 
pn network-manager-openvpn 
pn network-manager-pptp 
pn network-manager-ssh 
pn network-manager-strongswan 
pn network-manager-vpnc 

-- no debconf information

Bug#1033882: kde-plasma-desktop: Fail to start plasma-kded.service

2023-04-03 Thread Jose

Package: kde-plasma-desktop
Version: 5:142
Severity: important
X-Debbugs-Cc: j...@zeroc.com

Dear Maintainer,

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

With a fresh install of debian 12, KDE login fails all the time, looking throw 
the logs I see

Apr 03 14:19:18 debian systemd[1229]: Starting plasma-kded.service - KDE 
Daemon...
Apr 03 14:19:18 debian kded5[1477]: qt.qpa.xcb: could not connect to display
Apr 03 14:19:18 debian kded5[1477]: qt.qpa.plugin: Could not load the Qt 
platform plugin "xcb" in "" even though it was found.
Apr 03 14:19:18 debian kded5[1477]: This application failed to start because no 
Qt platform plugin could be initialized. Reinstalling the application may fix 
this problem.
Apr 03 14:19:18 debian kded5[1477]: Available platform plugins are: eglfs, 
linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, 
wayland-xcomposite-egl, wayland-xc>
Apr 03 14:19:18 debian systemd[1]: Started systemd-coredump@25-1478-0.service - 
Process Core Dump (PID 1478/UID 0).
Apr 03 14:19:18 debian systemd-coredump[1479]: [] Process 1477 (kded5) of user 
0 dumped core.
   
   Module libsystemd.so.0 from deb 
systemd-252.6-1.amd64
   Module libudev.so.1 from deb 
systemd-252.6-1.amd64
   Stack trace of thread 1477:
   #0  0x7f8a1f4a9ccc n/a 
(libc.so.6 + 0x8accc)
   #1  0x7f8a1f45aef2 raise 
(libc.so.6 + 0x3bef2)
   #2  0x7f8a1f445472 abort 
(libc.so.6 + 0x26472)
   #3  0x7f8a1f690c79 
_ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x90c79)
   #4  0x7f8a1fd34503 
_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 
0x134503)
   #5  0x7f8a1fd349b0 
_ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x1349b0)
   #6  0x7f8a1f8b7f15 
_ZN23QCoreApplicationPrivate4initEv (libQt5Core.so.5 + 0x2b7f15)
   #7  0x7f8a1fd3786c 
_ZN22QGuiApplicationPrivate4initEv (libQt5Gui.so.5 + 0x13786c)
   #8  0x7f8a20768519 
_ZN19QApplicationPrivate4initEv (libQt5Widgets.so.5 + 0x168519)
   #9  0x556b56b5b473 n/a 
(kded5 + 0x7473)
   #10 0x7f8a1f44618a n/a 
(libc.so.6 + 0x2718a)
   #11 0x7f8a1f446245 
__libc_start_main (libc.so.6 + 0x27245)
   #12 0x556b56b5b5c1 n/a 
(kded5 + 0x75c1)
   ELF object binary architecture: 
AMD x86-64

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


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

Kernel: Linux 6.1.0-7-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=C.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 kde-plasma-desktop depends on:
ii  kde-baseapps  4:22.12.3+5.142
ii  plasma-desktop4:5.27.2-1
ii  plasma-workspace  4:5.27.2-1
ii  udisks2   2.9.4-4
ii  upower0.99.20-2

Versions of packages kde-plasma-desktop recommends:
ii  kwin-x11  4:5.27.2-1
ii  sddm  0.19.0-5
ii  xserver-xorg  1:7.7+23

Versions of packages kde-plasma-desktop suggests:
ii  kdeconnect  22.12.3-1

-- no debconf information

Bug#1019977: Please add pipewire-pulse as alternative dependency

2023-04-03 Thread Kevin Otte

Package: python3-pulsectl
Followup-For: Bug #1019977

Rather than adding another dep on pipewire-pulse, it probably makes sense to 
change the dependency to the client library libpulse0, which is what this 
module is using for 
its bindings anyway.


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

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

Versions of packages python3-pulsectl depends on:
pn  pulseaudio  
ii  python3 3.11.2-1

python3-pulsectl recommends no packages.

python3-pulsectl suggests no packages.

Bug#1033881: RM: cgminer -- RoQA; Unmaintained upstream and package; RC-buggy


Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

cgminer is obviously abandoned both upstream and by its Debian maintainer.
stretch is the last release that contained it. Please consider removing it from 
the archive.

Bug#1033880: O: cgminer -- multi-pool Bitcoin miner


Package: wnpp

cgminer is obviously abandoned both upstream and by its Debian maintainer.
stretch is the last release that contained it. Therefore, I orphan the package.

Bug#1033879: widelands: Clicking options in Widelands cause the program to quit with an exception (file not found)

2023-04-03 Thread waxhead

Package: widelands
Version: 2:1.1-2
Severity: important
X-Debbugs-Cc: waxh...@dirtcellar.net

Dear Maintainer,

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

   * What led up to the situation?

Started up widelands (version 1.1 Release), clicked the option button. This is 
the output

[00:00:08.059 real] WARNING: Font file not found. Falling back to sans: 
Culmus/TaameyFrankCLM-Medium.ttf
[00:00:08.059 real] WARNING: LayeredFileSystem: Could not load file: could not 
find file or directory: i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
[00:00:08.059 real] WARNING: I have tried the following path(s):
[00:00:08.059 real] WARNING: 
/home/waxhead/.local/share/widelands/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
[00:00:08.059 real] WARNING: 
/usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
[00:00:08.059 real] WARNING: 
/home/waxhead/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf

Caught exception (of type '17FileNotFoundError') in outermost handler!
The exception said: LayeredFileSystem: Could not load file: could not find file 
or directory: i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
I have tried the following path(s):

/home/waxhead/.local/share/widelands/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
/usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
/home/waxhead/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf

This should not happen. Please file a bug report on version 1.1 Release.
and remember to specify your operating system.

[00:00:08.098 real] INFO: SoundHandler: Closing 1 time, 44100 Hz, format 32784, 
2 channels
[00:00:08.098 real] INFO: SoundHandler: SDL_AUDIODRIVER pulseaudio


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

I did not try to copy a font to any of the locations. I expect widelands to 
depend on the required font.

   * What was the outcome of this action?

Not much since I did not do anything

   * What outcome did you expect instead?

I expect widelands to be supplied with the needed fonts.

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


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

Kernel: Linux 6.1.0-7-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 widelands depends on:
ii  libc62.36-8
ii  libgcc-s112.2.0-14
ii  libglew2.2   2.2.0-4+b1
ii  libglx0  1.6.0-1
ii  libicu72 72.1-3
ii  libminizip1  1.1-8+b1
ii  libopengl0   1.6.0-1
ii  libpng16-16  1.6.39-2
ii  libsdl2-2.0-02.26.4+dfsg-1
ii  libsdl2-image-2.0-0  2.6.3+dfsg-1
ii  libsdl2-mixer-2.0-0  2.6.2+dfsg-2
ii  libsdl2-ttf-2.0-02.20.1+dfsg-2
ii  libstdc++6   12.2.0-14
ii  widelands-data   2:1.1-2

widelands recommends no packages.

widelands suggests no packages.

-- no debconf information

Bug#1033878: python3-brial: Missing runtime dependency