Bug#1016831: libminc: FTBFS on mipsel, mips64el

[Sebastian Ramacher]

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


1: Test command: 
/<>/obj-mips64el-linux-gnuabi64/ezminc/tests/ezminc_rw_test 
"/<>/obj-mips64el-linux-gnuabi64/ezminc/tests"
1: Working Directory: /<>/obj-mips64el-linux-gnuabi64/ezminc/tests
1: Test timeout computed to be: 1500
 1/52 Test  #1: ezminc_rw_test ...   Passed0.09 sec
test 2
  Start  2: minc_types-1

2: Test command: /<>/testdir/run_test_cmake.sh 
"/<>/obj-mips64el-linux-gnuabi64/testdir/minc_types" 
"/<>/testdir/minc_types.out"
2: Working Directory: /<>/obj-mips64el-linux-gnuabi64/testdir
2: Test timeout computed to be: 1500
2: 364c364
2: image[1] = 0
2: 373c373
2: image[1] = -128
2: 382c382
2: image[1] = 0
2: 391c391
2: image[1] = -32768
2: 400c400
2: image[1] = 0
2: 409c409
2: image[1] = -2.14748e+09
2: 418c418
2: image[1] = -2.14748e+09
2: 427c427
2: image[1] = -2.14748e+09
2: 481c481
2: image[1] = -2.14748e+09
2: 553c553
2: image[1] = -2.14748e+09
 2/52 Test  #2: minc_types-1 .***Failed0.09 sec
364c364
image[1] = 0
373c373
image[1] = -128
382c382
image[1] = 0
391c391
image[1] = -32768
400c400
image[1] = 0
409c409
image[1] = -2.14748e+09
418c418
image[1] = -2.14748e+09
427c427
image[1] = -2.14748e+09
481c481
image[1] = -2.14748e+09
553c553
image[1] = -2.14748e+09

test 3
  Start  3: minc_types-2

3: Test command: /<>/testdir/run_test2_cmake.sh 
"/<>/obj-mips64el-linux-gnuabi64/testdir/minc_types" 
"/<>/testdir/minc_types.out"
3: Working Directory: /<>/obj-mips64el-linux-gnuabi64/testdir
3: Test timeout computed to be: 1500
3: 364c364
3: image[1] = 0
3: 373c373
3: image[1] = -128
3: 382c382
3: image[1] = 0
3: 391c391
3: image[1] = -32768
3: 400c400
3: image[1] = 0
3: 409c409
3: image[1] = -2.14748e+09
3: 418c418
3: image[1] = -2.14748e+09
3: 427c427
3: image[1] = -2.14748e+09
3: 481c481
3: image[1] = -2.14748e+09
3: 553c553
3: image[1] = -2.14748e+09
 3/52 Test  #3: minc_types-2 .***Failed0.27 sec
364c364
image[1] = 0
373c373
image[1] = -128
382c382
image[1] = 0
391c391
image[1] = -32768
400c400
image[1] = 0
409c409
image[1] = -2.14748e+09
418c418
image[1] = -2.14748e+09
427c427
image[1] = -2.14748e+09
481c481
image[1] = -2.14748e+09
553c553
image[1] = -2.14748e+09

...

96% tests passed, 2 tests failed out of 52

Total Test time (real) = 126.06 sec

The following tests FAILED:
  2 - minc_types-1 (Failed)
  3 - minc_types-2 (Failed)
Errors while running CTest
make[2]: *** [Makefile:94: test] Error 8

https://buildd.debian.org/status/fetch.php?pkg=libminc&arch=mips64el&ver=2.4.03-5%2Bb1&stamp=1659928672&raw=0

Cheers
-- 
Sebastian Ramacher

Bug#1016685: v4l2loopback: CVE-2022-2652 - leaking kernel memory via crafted card labels

[Neil Williams]

On Fri, 5 Aug 2022 11:22:30 +0200
=?UTF-8?Q?IOhannes_m_zm=c3=b6lnig_=28Debian_GNU=7cLinux=29?=
 wrote:
> On Fri, 05 Aug 2022 09:41:46 +0100 Neil Williams
>  wrote:
> > The following vulnerability was published for v4l2loopback (and is
> > not included in the recent v0.12.7 git tag).
> 
> how so?

I got confused during the triage. My mistake. I initially marked the
CVE as fixed in 0.12.7.

> 
> > 
> > For further information see:
> > 
> > [0] https://security-tracker.debian.org/tracker/CVE-2022-2652
> > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2652
> > 
> > Please adjust the affected versions in the BTS as needed.
> 
> as upstream, i strongly believe that the v0.12.7 release includes the 
> relevant fix.
> is it enough t to just change the affected version or do I have to do 
> something else as well?

The normal fix would be to mark the bug as notfound 0.12.7-1 and then
close it without version information. The Debian Security Tracker
provides the relevant information on which versions remain vulnerable.

https://security-tracker.debian.org/tracker/source-package/v4l2loopback

The Tracker has been changed to show 0.12.7-1 as the first version in
Debian containing the fix for this CVE.

No changes are required in the misfiled bug report.

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


pgp0Aun1WdBSd.pgp
Description: OpenPGP digital signature

Bug#1016830: insighttoolkit5: FTBFS on amd64

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=insighttoolkit5&arch=amd64&ver=5.2.1-5%2Bb2&stamp=1659928626&raw=0


ITKPolynomials =   0.03 sec*proc

ITKQuadEdgeMesh =   1.34 sec*proc

ITKQuadEdgeMeshFiltering =  26.18 sec*proc

ITKRegionGrowing =   0.53 sec*proc

ITKRegistrationCommon =  87.72 sec*proc

ITKRegistrationMethodsv4 =  70.63 sec*proc

ITKReview =  48.79 sec*proc

ITKSignedDistanceFunction =   0.08 sec*proc

ITKSmoothing =   1.09 sec*proc

ITKSpatialFunction =   0.04 sec*proc

ITKSpatialObjects =   1.25 sec*proc

ITKStatistics =   7.16 sec*proc

ITKSuperPixel =   1.24 sec*proc

ITKTestKernel =   0.17 sec*proc

ITKThresholding =   4.59 sec*proc

ITKTransform =  20.72 sec*proc

ITKTransformFactory =   0.10 sec*proc

ITKVideoCore =   0.30 sec*proc

ITKVideoFiltering =   0.40 sec*proc

ITKVideoIO =   0.33 sec*proc

ITKVoronoi =   0.57 sec*proc

ITKWatersheds =   2.08 sec*proc

RUNS_LONG = 517.95 sec*proc

Test log end =:
make[1]: *** [debian/rules:93: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:77: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


Cheers
-- 
Sebastian Ramacher

Bug#1016829: cross-toolchain-base: autopkgtest hardcodes glibc version which is transitioning now

[Paul Gevers]

Source: cross-toolchain-base
Version: 59
Severity: serious

Dear all,

The glibc 2.34 transition started yesterday. However, the autopkgtest
of cross-toolchain-base fails because it hardcodes:
glibc-source (>= 2.33-1~), glibc-source (<< 2.34)
which isn't available anymore.

Please adapt your test for the new (and ideally future) glibc.

Paul

Bug#1016827: (linux-image-amd64: __dma_async_device_channel_unregister called while 2 clients hold a reference)

[ng]

Forgot to attach dmesg
[0.00] Linux version 5.10.0-16-amd64 (debian-ker...@lists.debian.org) 
(gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 
2.35.2) #1 SMP Debian 5.10.127-2 (2022-07-23)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-5.10.0-16-amd64 
root=UUID=e2621cc7-952f-4003-a3eb-60c1d6b188cd ro acpi_osi=Linux 
ccp.dmaengine=0 drm.edid_firmware=HDMI-A-1:edid/edid.bin quiet
[0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, 
using 'compacted' format.
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009efff] usable
[0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0x09bf] usable
[0.00] BIOS-e820: [mem 0x09c0-0x09d80fff] reserved
[0.00] BIOS-e820: [mem 0x09d81000-0x09ef] usable
[0.00] BIOS-e820: [mem 0x09f0-0x09f0afff] ACPI NVS
[0.00] BIOS-e820: [mem 0x09f0b000-0xb8d8dfff] usable
[0.00] BIOS-e820: [mem 0xb8d8e000-0xbbd7dfff] reserved
[0.00] BIOS-e820: [mem 0xbbd7e000-0xbdd7dfff] ACPI NVS
[0.00] BIOS-e820: [mem 0xbdd7e000-0xbddfdfff] ACPI data
[0.00] BIOS-e820: [mem 0xbddfe000-0xbeff] usable
[0.00] BIOS-e820: [mem 0xbf00-0xbfff] reserved
[0.00] BIOS-e820: [mem 0xfd20-0xfd2f] reserved
[0.00] BIOS-e820: [mem 0xfed8-0xfed80fff] reserved
[0.00] BIOS-e820: [mem 0x0001-0x0002beff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] e820: update [mem 0xb3ff1018-0xb3fff057] usable ==> usable
[0.00] e820: update [mem 0xb3ff1018-0xb3fff057] usable ==> usable
[0.00] e820: update [mem 0xb3fe3018-0xb3ff0457] usable ==> usable
[0.00] e820: update [mem 0xb3fe3018-0xb3ff0457] usable ==> usable
[0.00] extended physical RAM map:
[0.00] reserve setup_data: [mem 0x-0x0009efff] 
usable
[0.00] reserve setup_data: [mem 0x0009f000-0x0009] 
reserved
[0.00] reserve setup_data: [mem 0x000e-0x000f] 
reserved
[0.00] reserve setup_data: [mem 0x0010-0x09bf] 
usable
[0.00] reserve setup_data: [mem 0x09c0-0x09d80fff] 
reserved
[0.00] reserve setup_data: [mem 0x09d81000-0x09ef] 
usable
[0.00] reserve setup_data: [mem 0x09f0-0x09f0afff] 
ACPI NVS
[0.00] reserve setup_data: [mem 0x09f0b000-0xb3fe3017] 
usable
[0.00] reserve setup_data: [mem 0xb3fe3018-0xb3ff0457] 
usable
[0.00] reserve setup_data: [mem 0xb3ff0458-0xb3ff1017] 
usable
[0.00] reserve setup_data: [mem 0xb3ff1018-0xb3fff057] 
usable
[0.00] reserve setup_data: [mem 0xb3fff058-0xb8d8dfff] 
usable
[0.00] reserve setup_data: [mem 0xb8d8e000-0xbbd7dfff] 
reserved
[0.00] reserve setup_data: [mem 0xbbd7e000-0xbdd7dfff] 
ACPI NVS
[0.00] reserve setup_data: [mem 0xbdd7e000-0xbddfdfff] 
ACPI data
[0.00] reserve setup_data: [mem 0xbddfe000-0xbeff] 
usable
[0.00] reserve setup_data: [mem 0xbf00-0xbfff] 
reserved
[0.00] reserve setup_data: [mem 0xfd20-0xfd2f] 
reserved
[0.00] reserve setup_data: [mem 0xfed8-0xfed80fff] 
reserved
[0.00] reserve setup_data: [mem 0x0001-0x0002beff] 
usable
[0.00] efi: EFI v2.70 by Lenovo
[0.00] efi: ACPI=0xbddfd000 ACPI 2.0=0xbddfd014 TPMFinalLog=0xbdc2d000 
SMBIOS=0xba72c000 SMBIOS 3.0=0xba71f000 MEMATTR=0xb6a92018 ESRT=0xb92c9000 
MOKvar=0xb6a83000 RNG=0xba839598 TPMEventLog=0xb418 
[0.00] efi: seeding entropy pool
[0.00] random: crng init done
[0.00] Kernel is locked down from EFI Secure Boot; see man 
kernel_lockdown.7
[0.00] secureboot: Secure boot enabled
[0.00] SMBIOS 3.1.1 present.
[0.00] DMI: LENOVO 20NECTO1WW/20NECTO1WW, BIOS R11ET45P (1.25 ) 
07/04/2022
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 2096.078 MHz processor
[0.15] e820: updat

Bug#1016828: poc-streamer: flaky autopkgtest: regularly times out on i386

[Paul Gevers]

Source: poc-streamer
Version: 0.4.2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky timeout

Dear maintainer(s),

I looked at the results of the autopkgtest of you package because it was 
showing up on our "slow" page [1]. I noticed that there were several 
runs that took 8:21 (our timeout time per test times 3), while 
successful runs more in the order of a minute.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

On top of that, when a test just hangs that's not good for our 
infrastructure. I'll put your package on our reject_list for i386.


Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[1] https://ci.debian.net/status/slow/


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016826: src:libsbig: fails to migrate to testing for too long: not installable on armel, mips64el, ppc64el and s390x

[Paul Gevers]

Source: libsbig
Version: 4.9.9-1
Severity: serious
Control: close -1 4.9.9-2
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1014499

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016825: src:r-cran-rsconnect: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: r-cran-rsconnect
Version: 0.8.25-1
Severity: serious
Control: close -1 0.8.27-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1016824

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-rsconnect has been trying to 
migrate for 61 days [2]. Hence, I am filing this bug. It fails to 
migrate because of the autopkgtest issue on i386 that I just filed, see 
bug #1016824.


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


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


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


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


Paul

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


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016824: r-cran-rsconnect: autopkgtest regression on i386: test times out

[Paul Gevers]

Source: r-cran-rsconnect
Version: 0.8.27-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression timeout

Dear maintainer(s),

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


   passfail
r-cran-rsconnect   from testing0.8.27-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test times 
out after 2:47 hours while on other architectures and in the past, the 
test succeeded in about 1 minute.


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


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

Paul

[1] https://qa.debian.org/excuses.php?package=r-cran-rsconnect

https://ci.debian.net/data/autopkgtest/testing/i386/r/r-cran-rsconnect/24435951/log.gz

BEGIN TEST testthat.R

R version 4.2.1 (2022-06-23) -- "Funny-Looking Kid"
Copyright (C) 2022 The R Foundation for Statistical Computing
Platform: i686-pc-linux-gnu (32-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.


library(testthat)
library(rsconnect)

run_tests <- function() {

+   # set temp config dir so the tests don't pollute it
+   temp_config_dir <- file.path(tempdir(), "rsconnect-test-config")
+   Sys.setenv(R_USER_CONFIG_DIR = temp_config_dir)
+ +   # clean up temp dir after tests are run
+   on.exit({
+ unlink(temp_config_dir, recursive = TRUE)
+   }, add = TRUE)
+ +   # perform tests
+   test_check("rsconnect")
+ }


run_tests()
autopkgtest [15:59:42]: ERROR: timed out on command "su -s /bin/bash 
debci -c set -e; export USER=`id -nu`; . /etc/profile >/dev/null 2>&1 || 
true;  . ~/.profile >/dev/null 2>&1 || true; 
buildtree="/tmp/autopkgtest-lxc.pjgtqe6l/downtmp/build.swe/src"; mkdir 
-p -m 1777 -- 
"/tmp/autopkgtest-lxc.pjgtqe6l/downtmp/run-unit-test-artifacts"; export 
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.pjgtqe6l/downtmp/run-unit-test-artifacts"; 
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755 
"/tmp/autopkgtest-lxc.pjgtqe6l/downtmp/autopkgtest_tmp"; export 
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.pjgtqe6l/downtmp/autopkgtest_tmp"; 
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive; 
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE 
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES 
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT 
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo 
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f 
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod 
+x 
/tmp/autopkgtest-lxc.pjgtqe6l/downtmp/build.swe/src/debian/tests/run-unit-test; 
touch /tmp/autopkgtest-lxc.pjgtqe6l/downtmp/run-unit-test-stdout 
/tmp/autopkgtest-lxc.pjgtqe6l/downtmp/run-unit-test-stderr; 
/tmp/autopkgtest-lxc.pjgtqe6l/downtmp/build.swe/src/debian/tests/run-unit-test 
2> >(tee -a /tmp/autopkgtest-lxc.pjgtqe6l/downtmp/run-unit-test-stderr 
>&2) > >(tee -a 
/tmp/autopkgtest-lxc.pjgtqe6l/downtmp/run-unit-test-stdout);" (kind: test)

autopkgtest [15:59:42]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Bug#984205:

[Michael Hudson-Doyle]

This is because upstream builds with -Werror -Wall by default, and that's
usually a bad idea for distro packages. I fixed this like this:


 .PHONY: override_dh_auto_build
 override_dh_auto_build: $(MAINT_SCRIPTS)
-dh_auto_build
+dh_auto_build -- WERROR=

Not really sure if this is appropriate for Debian or not!

Bug#1011640: libhowardhinnant-date-dev: CMake library name problems

[Michael Welsh Duggan]

Andrea Pappacoda  writes:

> Hi, sorry for my late reply. For whatever reason I don't receive bug
> reports when sent to the Debian Bug Tracking System, so please make
> sure to Cc me in your future replies.

No problem.  I'm happy with the changes you are making.  Thank you!

-- 
Michael Welsh Duggan
(m...@md5i.com)

Bug#1016823: Thunar: add Lens Model to Image tab [patch attached]

[José Luis González]

Package: thunar
Version: 4.16.8-1
Severity: wishlist
Tags: patch

Hi,

Patch for including Lens ("Lens Model" is the actual EXIF tag name) in
Image tab, just after camera model is included at the bottom. A Spanish 
translation for the field text is also included in the patch.

Please, forward to upstream and include as a patch in the meantime for
sid.

Thanks in advance.

Regards,
José Luis


--- thunar-4.16.8/po/es.po  2021-05-07 15:29:31.0 +0200
+++ thunar-4.16.8.new/po/es.po  2022-08-08 04:19:37.690410704 +0200
@@ -3322,2 +3322,5 @@ msgstr "Modelo de la cámara:"
 
+msgid "Lens Model:"
+msgstr "Modelo del objetivo:"
+
 #: ../plugins/thunar-apr/thunar-apr-image-page.c:50
--- thunar-4.16.8/plugins/thunar-apr/thunar-apr-image-page.c2021-05-07 
13:50:34.0 +0200
+++ thunar-4.16.8.new/plugins/thunar-apr/thunar-apr-image-page.c
2022-08-08 04:03:43.126388054 +0200
@@ -49,2 +49,3 @@ static const struct
   { N_ ("Camera Model:"),  EXIF_TAG_MODEL,   },
+  { N_ ("Lens Model:"),EXIF_TAG_LENS_MODEL,  },
   { N_ ("Exposure Time:"), EXIF_TAG_EXPOSURE_TIME,   },

Bug#627463: texlive-latex-base: link to PDF is not made properly

[Osamu Aoki]

Hi,

> -Original Message-
> From: Hilmar Preuße 
> To: Osamu Aoki 
> Cc: 627...@bugs.debian.org
> Subject: Re: Bug#627463: texlive-latex-base: link to PDF is not made properly
> Date: Sat, 3 Aug 2019 21:45:09 +0200
> 
> Am 20.05.2011 um 21:30 teilte Osamu Aoki mit:
> 
> Hi Osamu,
> 
> I'm going through some old bugs and check if they are still valid.
> 

Thanks.

> 
> Then I tried evince, which behaves differently, e.g. by clicking on the
> first link, the full document path expands to:
> 
> /home/hille/devel/TeXLive/open_bugs/627463/usr/share/doc/developers-
> reference/developers-reference.pdf
> 
> , where "/home/hille/devel/TeXLive/open_bugs/627463" is the $PWD, when I
> started evince.
> 
> So my impression is that one should speak to the developers of the pdf
> readers one by one. The links itself in the pdf files seem to be OK; at
> least when hovering over the links.
> 
> Let me know if the bug can be closed from the TeX Live side.

I agree with your assessment and closing this bug.  Thanks.

Osamu

Bug#872735: orage: VEVENT starting before 'DT...;VALUE=DATE:20000101' aren't shown

[Paul Wise]

On Sun, 20 Aug 2017 18:10:32 +0200 Jens Schmidt wrote:

> orage doesn't show birthdays, anniversaries etc. which are starting before
> 1970. And there are also no alarms. This seems to be an old bug which affects 
> a
> lot of calendar programms.

orage 4.16.0-1 has been reintroduced into Debian unstable.

Please try it and see if the issue has been fixed.

If the issue has been fixed, please let us know on this bug.

If the issue has not been fixed, please search the upstream bug
database for orage to see if the issue is already reported and if it is
not reported, then report a new issue upstream. Please let us know
about any new or existing upstream bugs you file or find.

https://docs.xfce.org/apps/orage/bugs

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#950993: orage: calendar window doesn't work anymore

[Paul Wise]

On Sun, 09 Feb 2020 12:12:06 + Jiff wrote:

> - a click on the orage clock opens the calendar window for ~500ms
>(just the frame, no text) and it closes at once.

orage 4.16.0-1 has been reintroduced into Debian unstable.

Please try it and see if the crash has been fixed.

If the crash has been fixed, please let us know on this bug.

If the crash has not been fixed, please search the upstream bug
database for orage to see if the crash is already reported and if it is
not reported, then report a new issue upstream. Please let us know
about any upstream bugs you file.

https://docs.xfce.org/apps/orage/bugs

I note that there is one segfault bug mentioned, so please try to see
if that bug report matches the behaviour on your system and if it is
then you can subscribe to that upstream bug report. Please let us know
if this bug matches the behaviour on your system.

https://gitlab.xfce.org/apps/orage/-/issues/2

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#656073: Orage - some very strange bug

[Paul Wise]

On Mon, 16 Jan 2012 10:49:11 +0100 Daniel Albrecht wrote:

> If I try open "view selected day" while "today" is selected or
> if I try openning day-view from week view for "today" it crashes orage.
> For all other days except "today" it opens without any problem.

orage 4.16.0-1 has been reintroduced into Debian unstable.

Please try it and see if the issue has been fixed.

If the issue has been fixed, please let us know on this bug.

If the issue has not been fixed, please search the upstream bug
database for orage to see if the issue is already reported and if it is
not reported, then report a new issue upstream. Please let us know
about any new or existing upstream bugs you file or find.

https://docs.xfce.org/apps/orage/bugs

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#646768: orage: panel display preferences do not persist

[Paul Wise]

On Thu, 27 Oct 2011 00:58:36 +0100 cfr wrote:

> I would expect the customised colour selection to "stick", persisting
> between logins, restarts etc. That is, I would expect it to be
> remembered in the same way as the customised background colour.

orage 4.16.0-1 has been reintroduced into Debian unstable.

Please try it and see if the issue has been fixed.

If the issue has been fixed, please let us know on this bug.

If the issue has not been fixed, please search the upstream bug
database for orage to see if the issue is already reported and if it is
not reported, then report a new issue upstream. Please let us know
about any new or existing upstream bugs you file or find.

https://docs.xfce.org/apps/orage/bugs

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#754461: xfce4-orageclock-plugin: zombie process when exiting orage

[Paul Wise]

On Fri, 11 Jul 2014 14:14:58 +0300 Nikolay Mitev wrote:

> When clicking on the systray the orage calendar appears. When you select exit
> from the calender the process becomes a zombie. Every time this happens a new
> zombie process is created.

orage 4.16.0-1 has been reintroduced into Debian unstable.

Please try it and see if the issue has been fixed.

If the issue has been fixed, please let us know on this bug.

If the issue has not been fixed, please search the upstream bug
database for orage to see if the issue is already reported and if it is
not reported, then report a new issue upstream. Please let us know
about any new or existing upstream bugs you file or find.

https://docs.xfce.org/apps/orage/bugs

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1011421: python3-clevercsv,python3-clevercsv-doc: both ship /usr/share/man/man1/clevercsv*.1.gz

[Louis-Philippe Véronneau]

On Sun, 22 May 2022 15:00:26 +0200 Andreas Beckmann  wrote:

Package: python3-clevercsv,python3-clevercsv-doc
Version: 0.7.4+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package python3-clevercsv-doc.
  Preparing to unpack .../6-python3-clevercsv-doc_0.7.4+ds-1_all.deb ...
  Unpacking python3-clevercsv-doc (0.7.4+ds-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-8i4axm/6-python3-clevercsv-doc_0.7.4+ds-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man1/clevercsv-code.1.gz', which is also 
in package python3-clevercsv 0.7.4+ds-1
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-8i4axm/6-python3-clevercsv-doc_0.7.4+ds-1_all.deb

These manpages are shipped in both packages:

usr/share/man/man1/clevercsv-code.1.gz
usr/share/man/man1/clevercsv-detect.1.gz
usr/share/man/man1/clevercsv-explore.1.gz
usr/share/man/man1/clevercsv-help.1.gz
usr/share/man/man1/clevercsv-standardize.1.gz
usr/share/man/man1/clevercsv-view.1.gz
usr/share/man/man1/clevercsv.1.gz


cheers,

Andreas


Oops, sorry for not taking care of this (pretty dumb) bug. I wasn't 
subscribed for this package on tracker.d.o and I never got the bug :)


I'm preparing a fix.

--
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016195:

[V O]

I don't know why, but the problem seems to be fixed after a reboot and I'm
no longer able to reproduce it.

I guess this bug can be closed.

Bug#1016708: thunderbird: Thunderbird 102 doesn't recognize installed hunspell and myspell dictionaries

[Michael Meier]

hi Carsten

On 05.08.22 14:51, Carsten Schoenert wrote:

Hello Michael,

Am 05.08.22 um 21:14 schrieb Michael Meier:


I've just installed Thunderbird 102.
Now it doesn't recognize anymore the installed hunspell and myspell
dictionaries for spellchecking. If they aren't supported anymore by
thunderbird, then they should be removed from the recommended list.


an Add-ons installed? What happens if you disable all Add-ons?
Is that happen too if you start with a new profile?
Does this behavior also happen if you use pre-build upstream binary?

Please note also the hints within the Debian wiki.

https://wiki.debian.org/Thunderbird#Bug_Reporting_.2F_Issues

Thanks for your reply. Actually I've took a look at the wiki, but when I 
saw the first thing beeing mentioned is icedove I've assumed it's 
completely outdated, and didn't continue reading, sorry.


As it seems the problems are no add ons or anything. But maybe it has to 
do with KDE.


I'm using kde plasma. When I pin thunderbird to the task bar, and start 
it up from there, then the only dictionary available is the english one. 
When I start it from the console, application launcher or krunner 
(alt+f2) all the installed dictionaries are available.


No idea what is different when it's pinned to the task bar. Maybe some 
environment variables? no idea how to find out. In previous versions of 
thunderbird that wasn't an issue.


To get it there right click on the application in the task bar, choose 
"pin to task manager".

Bug#1015222: downgrading sublime-music playlist

[Louis-Philippe Véronneau]

severity 1015222 normal
forwarded 1015222 https://gitlab.com/sublime-music/sublime-music/-/issues/340
thanks

Hello. Thanks for reporting this bug.

I see that you've also reported it upstream.

I'm downgrading this bug to "normal", as I don't think it breaks sublime-music
enough to remove it from testing.

Cheers,

--
   ⢀⣴⠾⠻⢶⣦⠀
   ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
   ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
   ⠈⠳⣄



OpenPGP_0xE1E5457C8BAD4113.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016822: intel-media-va-driver: segfault in mos_bo_wait_rendering()

[Marc Bevand]

Package: intel-media-va-driver
Version: 22.4.3+dfsg1-1
Severity: normal

Hi all, on my system when I try to play an H.264 file with VLC, it crashes with 
a Segmentation Fault in iHD_drv_video.so.
With debug symbols, the stack trace reported by gdb is:

#0  mos_bo_wait_rendering(mos_linux_bo*) (bo=0x0) at 
./media_driver/linux/common/os/i915/mos_bufmgr_api.c:138
#1  0x7fff15a4e3b1 in DdiMediaDecode::CreateBuffer(VABufferType, unsigned 
int, unsigned int, void*, unsigned int*)
(this=0x7fff543aab10, type=VASliceDataBufferType, size=, 
numElements=1, data=0x7fffc019dc73, bufId=0x7fff65f49a9c)
at ./media_driver/linux/common/codec/ddi/media_ddi_decode_base.cpp:1099
#2  0x7fff15a0e279 in DdiMedia_CreateBuffer(VADriverContext*, unsigned int, 
VABufferType, unsigned int, unsigned int, void*, unsigned int*)
(bufId=0x7fff65f49a9c, data=0x7fffc019dc73, num_elements=1, size=16175, 
type=VASliceDataBufferType, context=268435456, ctx=0x7fff54237160)
at ./media_driver/linux/common/ddi/media_libva.cpp:3247
#3  DdiMedia_CreateBuffer(VADriverContext*, unsigned int, VABufferType, 
unsigned int, unsigned int, void*, unsigned int*)
(ctx=0x7fff54237160, context=268435456, type=VASliceDataBufferType, 
size=16175, num_elements=1, data=0x7fffc019dc73, bufId=0x7fff65f49a9c)
at ./media_driver/linux/common/ddi/media_libva.cpp:3215
#4  0x7fff6c193193 in vaCreateBuffer () at /lib/x86_64-linux-gnu/libva.so.2
#5  0x7fff4074cb85 in  () at 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_va_gl.so.1
#6  0x7fff4074d2ac in  () at 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_va_gl.so.1
#7  0x7fff4074d879 in  () at 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_va_gl.so.1
#8  0x7fff6e911808 in  () at /lib/x86_64-linux-gnu/libavcodec.so.59
#9  0x7fff6e911c68 in  () at /lib/x86_64-linux-gnu/libavcodec.so.59
#10 0x7fff6e4b25e6 in  () at /lib/x86_64-linux-gnu/libavcodec.so.59
#11 0x7fff6e4c78e1 in  () at /lib/x86_64-linux-gnu/libavcodec.so.59
#12 0x7fff6e782f3b in  () at /lib/x86_64-linux-gnu/libavcodec.so.59
#13 0x77f6dd80 in start_thread (arg=0x7fff65f4b640) at 
pthread_create.c:481
#14 0x77e81baf in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

I interpret this as "buf->bo" being NULL on line 1117 in 
media_ddi_decode_base.cpp:
https://github.com/intel/media-driver/blob/a47db3905e6f77b0666c6f10e3b9642cac9fafc8/media_driver/linux/common/codec/ddi/media_ddi_decode_base.cpp#L1117

1115  if( true == buf->bCFlushReq )
1116  {
1117  mos_bo_wait_rendering(buf->bo);
1118  }

Since mos_bo_wait_rendering() is passed the NULL argument, a SIGSEGV is raised 
when "bo" is dereferenced on line 116 in mos_bufmgr_api_mock.c:
https://github.com/intel/media-driver/blob/master/media_driver/linux/ult/libdrm_mock/mos_bufmgr_api_mock.c#L116

114   mos_bo_wait_rendering(struct mos_linux_bo *bo)
115   {
116  bo->bufmgr->bo_wait_rendering(bo);
117   }

My system info:

CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz

$ vainfo
libva info: VA-API version 1.15.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.15 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.4.3 ()
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointVLD

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

Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE

  Note: my kernel is tainted because I install the ZFS kernel module via 
zfs-dkms

Locale: LANG=C, 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 intel-media-va-driver depends on:
ii  libc6   2.33-8
ii  libgcc-s1   12.1.0-7
ii  libigdgmm12 22.

Bug#1016821: libspf2: FTBFS with glibc 2.34

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=libspf2&arch=arm64&ver=1.2.10-7.1%2Bb2&stamp=1659915050&raw=0

/bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall  -Wl,-z,relro 
-Wl,--version-script=/<>/debian/libspf2.ver -o spfquery spfquery.o 
../../src/libspf2/libspf2.la -lpthread -lnsl -lresolv 
libtool: link: gcc -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z 
-Wl,relro -Wl,--version-script=/<>/debian/libspf2.ver -o 
.libs/spfquery spfquery.o  ../../src/libspf2/.libs/libspf2.so -lpthread -lnsl 
-lresolv
/usr/bin/ld: ../../src/libspf2/.libs/libspf2.so: undefined reference to 
`__dn_expand'
/usr/bin/ld: ../../src/libspf2/.libs/libspf2.so: undefined reference to 
`__dn_skipname'
collect2: error: ld returned 1 exit status
make[5]: *** [Makefile:442: spfquery] Error 1
make[5]: Leaving directory '/<>/src/spfquery'

Cheers
-- 
Sebastian Ramacher

Bug#1016820: libnss-db: FTBFS with glibc 2.34

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=libnss-db&arch=arm64&ver=2.2.3pre1-6%2Bb13&stamp=1659914807&raw=0

/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -version-info 2 
-Wl,--version-script=../../src/libnss_db.map -Wl,-z,relro -o libnss_db.la 
-rpath /lib/aarch64-linux-gnu db-alias.lo db-ethers.lo db-netgrp.lo db-grp.lo 
db-proto.lo db-pwd.lo db-rpc.lo db-service.lo db-spwd.lo db-compat.lo 
db-open.lo -lnss_files -ldb 
libtool: link: gcc -shared  -fPIC -DPIC  .libs/db-alias.o .libs/db-ethers.o 
.libs/db-netgrp.o .libs/db-grp.o .libs/db-proto.o .libs/db-pwd.o .libs/db-rpc.o 
.libs/db-service.o .libs/db-spwd.o .libs/db-compat.o .libs/db-open.o   
-lnss_files -ldb  -g -O2 -fstack-protector-strong 
-Wl,--version-script=../../src/libnss_db.map -Wl,-z -Wl,relro   -Wl,-soname 
-Wl,libnss_db.so.2 -o .libs/libnss_db.so.2.0.0
/usr/bin/ld: cannot find -lnss_files: No such file or directory
collect2: error: ld returned 1 exit status
make[4]: *** [Makefile:516: libnss_db.la] Error 1
make[4]: Leaving directory '/<>/build/src'


Cheers
-- 
Sebastian Ramacher

Bug#1016311: raft: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

[Mathias Gibbens]

Control: tags -1 + confirmed
Control: forwarded -1 https://github.com/canonical/raft/issues/292

  This has been reported by others to the upstream developers already,
and seems to be caused by an update to libuv1.

Mathias


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

Bug#1016806: request-tracker5: FTBFS with Perl 5.36: Subroutine JSON::PP::Boolean::(0+ redefined

[gregor herrmann]

On Sun, 07 Aug 2022 21:09:49 +0300, Niko Tyni wrote:

> Excerpt:
> 
>#   Failed test 'no warnings'
>#   at /<>/lib/RT/Test.pm line 1796.
># There were 3 warning(s)
># Previous test 0 ''
># Subroutine JSON::PP::Boolean::(++ redefined at 
> /usr/lib/x86_64-linux-gnu/perl-base/overload.pm line 52.
>#  at /usr/lib/x86_64-linux-gnu/perl-base/overload.pm line 52.
>#  overload::OVERLOAD("JSON::PP::Boolean", "0+", CODE(0x561a9651eee0), 
> "++", CODE(0x561a9651ef40), "--", CODE(0x561a9651efd0), "\"\"", ...) called 
> at /usr/lib/x86_64-linux-gnu/perl-base/overload.pm line 61
>#  overload::import("overload", "0+", CODE(0x561a9651eee0), "++", 
> CODE(0x561a9651ef40), "--", CODE(0x561a9651efd0), "\"\"", ...) called at 
> /usr/lib/x86_64-linux-gnu/perl5/5.36/Cpanel/JSON/XS.pm line 2365
>#  Cpanel::JSON::XS::BEGIN() called at 
> /usr/lib/x86_64-linux-gnu/perl5/5.36/Cpanel/JSON/XS.pm line 2366

Could this be https://github.com/rurban/Cpanel-JSON-XS/issues/198 in
libcpanel-json-xs-perl?

When I update libcpanel-json-xs-perl's debian/control to
Build-Depends: debhelper-compat (= 13),
   libjson-perl (>= 4.09000) ,
   libjson-pp-perl (>= 4.11000) ,
[…]

(but only when forcing libjson-pp-perl 4.11000 in)

and build in my experimental+perl5.36 chroot I get the same error:

# prove --blib --verbose t/20_unknown.t
t/20_unknown.t .. Subroutine JSON::PP::Boolean::(++ redefined at 
/usr/lib/x86_64-linux-gnu/perl-base/overload.pm line 52.
Subroutine JSON::PP::Boolean::(0+ redefined at 
/usr/lib/x86_64-linux-gnu/perl-base/overload.pm line 52.
Subroutine JSON::PP::Boolean::(-- redefined at 
/usr/lib/x86_64-linux-gnu/perl-base/overload.pm line 52.

1..32
ok 1 - encountered CODE(0x55da10d9a560), but JSON can only represent references 
to arrays or hashes at (eval 49) line 1.
# 
ok 2 - cannot encode reference to scalar 'SCALAR(0x55da10d8ebd8)' unless the 
scalar is 0 or 1 at (eval 50) line 1.
# 
ok 3 - cannot encode reference to scalar 'SCALAR(0x55da104944e0)' unless the 
scalar is 0 or 1 at (eval 51) line 1.
# 
ok 4 - cannot encode reference to scalar 'REF(0x55da10d8ef38)' unless the 
scalar is 0 or 1 at (eval 52) line 1.
# 
ok 5 - cannot encode reference to scalar 'SCALAR(0x55da10d8e7a0)' unless the 
scalar is 0 or 1 at (eval 53) line 1.
# 
ok 6 - cannot encode reference to scalar 'SCALAR(0x55da104944f8)' unless the 
scalar is 0 or 1 at (eval 54) line 1.
# 
ok 7 - cannot encode reference to scalar at (eval 55) line 1.
# 
ok 8 - cannot encode reference to scalar at (eval 56) line 1.
# 
ok 9
ok 10
ok 11
ok 12
ok 13 - pp unknown
ok 14 - pp unknown
not ok 15 - pp sv_yes

#   Failed test 'pp sv_yes'
#   at t/20_unknown.t line 53.
not ok 16 - pp sv_no
not ok 17 - pp sv_no
ok 18 - pp \sv_yes
ok 19 - pp \sv_no

#   Failed test 'pp sv_no'
#   at t/20_unknown.t line 54.
#  got: '{"false":false}'
# expected: '{"false":""}'

#   Failed test 'pp sv_no'
#   at t/20_unknown.t line 55.
#  got: '{"false":false}'
# expected: '{"false":""}'
ok 20 - pp \sv_no
ok 21 - js unknown
ok 22 - js unknown
ok 23 - js sv_yes
ok 24 - js sv_no
ok 25 - js sv_no
ok 26 - js \sv_yes
ok 27 - js \sv_no
ok 28 - js \sv_no
ok 29 - pp encountered GLOB(0x55da10db8c10), but JSON can only represent 
references to arrays or hashes at (eval 76) line 1.
# 
ok 30 - js encountered GLOB(0x55da10db8c10), but JSON can only represent 
references to arrays or hashes at (eval 77) line 1.
# 
ok 31
ok 32
# Looks like you failed 3 tests of 32.
Dubious, test returned 3 (wstat 768, 0x300)
Failed 3/32 subtests 

Test Summary Report
---
t/20_unknown.t (Wstat: 768 (exited 3) Tests: 32 Failed: 3)
  Failed tests:  15-17
  Non-zero exit status: 3
Files=1, Tests=32,  0 wallclock secs ( 0.04 usr  0.00 sys +  0.07 cusr  0.00 
csys =  0.11 CPU)
Result: FAIL


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1016801: 22.2.0~rc1-1 breaks Blender/llvm on AMD gpus

[Yuri D'Elia]

Package: mesa-common-dev
Version: 22.2.0~rc1-1
Followup-For: Bug #1016801

Upstream bug report: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6976

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

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

Versions of packages mesa-common-dev:amd64 depends on:
ii  libdrm-dev  2.4.112-3
ii  libgl-dev   1.4.0-1
ii  libglx-dev  1.4.0-1
ii  libx11-dev  2:1.8.1-2

mesa-common-dev:amd64 recommends no packages.

mesa-common-dev:amd64 suggests no packages.

Bug#914945: separate vm does not work with xemacs21

[Ian Jackson]

Control: severity -1 normal

I have removed the passlisting of xemacs21 from the postinst so I
think vm.deb and xemacs21 ought now to be coinstallable, even though
you'll get the xemacs21's builtin copy of vm.

I note that xemacs21 appears to be slated for (auto)removal.

Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1016809: [UEFI] Installed (minimal) bookworm system hangs at boot

[Steve McIntyre]

Hey Holger!

On Sun, Aug 07, 2022 at 09:36:43PM +0200, Holger Wansing wrote:
>Package: installation-reports
>Severity: normal
>
>Boot method: netinst image on QEMU
>Image version: debian-testing-amd64-netinst.iso from today
>Date: 2022-08-07
>
>Machine: UEFI-driven qemu VM
>
>Booted with
>qemu-system-x86_64 -boot order=d -vga vmware -bios OVMF.fd -L . -m 1024M 
>--enable-kvm -hda ~/qemu-img-disk-10G.img -cdrom 
>/home/ned/installation-images/debian-daily_2022-08-07_amd64-netinst.iso
>
>Installing Debian on an UEFI-driven QEMU machine (minimal installation, only
>standard system task) leads to a successful installation, but the newly 
>installed system cannot complete its boot process.
>It hangs forever (here on linux 5.18.0-3) with this messages
>
>
>[  OK  ] Activated swap /dev/disk/by-uuid/f10f20e2-b6b6b-428f-8dbe-257e8d097a04
>[  OK  ] Reached target Swaps.
>[  OK  ] Mounted /boot/efi.
>[  OK  ] Reached target Local File Systems
>   4.720864 random: crng init done
>  Starting Load AppArmor profiles...
>  Starting Create Volatile Files and Directories...
>
>
>When installing from an older installation-image and then booting the
>older kernel linux 5.15.0-2, this leads to the same problem, so it's at least
>not somehow kernel related.
>
>I'm unable to access more logs on the qemu machine, unfortunately.

Have you had this particular qemu command line work for you in the
last? What you have there specifies that the machine should use the
OVMF code as a "bios" image, but doesn't give an extra storage area
for the firmware settings. What I use in scripts here uses the pflash
image interface to add both:

 "-pflash OVMF.fd -pflash storage.fd"

This really isn't well documented in terms of driving stuff - most
people end up using libvirt and its tools to drive qemu/kvm.

My own dirty, hacky script for testing d-i images is at [1] in case
that helps.

[1] https://git.einval.com/cgi-bin/gitweb.cgi?p=efitest.git;a=blob;f=efitest

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Managing a volunteer open source project is a lot like herding
 kittens, except the kittens randomly appear and disappear because they
 have day jobs." -- Matt Mackall

Bug#1012097: NIS broken in sid

[Aurelien Jarno]

control: reassign 1012097 libc6
control: forcemerge 1003342 1012097
control: affects 1012097 libnss-nis

On 2022-05-30 09:38, Francesco Paolo Lovergine wrote:
> Package: libnssswitch-nis
> Version: 3.1-4
> Severity: grave
> 
> It seems that currently unstable has a totally not working NIS binding for 
> users. I
> performed my trials using an existing setup (bullseye-based NIS master+slaves 
> and
> clients network in the real life).
> 
> I recently upgraded a bullseye NIS client box to sid for testing and 
> discovered that while
> ypbind-mt is regularly working, the usual mapping of NIS users has gone.
> To be sure of the issue I prepared a vagrant bullseye VM and bound that to 
> the regular bullseye NIS master as usual: perfectly working. 
> 
> Then I full-upgraded to sid with the same broken result:
> 
> vagrant@debian:/etc$ ypcat passwd
> [...]
> lovergine:x:2003:2000:Francesco Lovergine (trial),,,:/home/lovergine:/bin/bash
> [...]
> {sorry, I stripped the full output for privacy)
> 
> vagrant@debian:/etc$ id lovergine
> id: ‘lovergine’: no such user
> 
> vagrant@debian:/etc$ cat /etc/nsswitch.conf 
> # /etc/nsswitch.conf
> #
> # Example configuration of GNU Name Service Switch functionality.
> # If you have the `glibc-doc-reference' and `info' packages installed, try:
> # `info libc "Name Service Switch"' for information about this file.
> 
> passwd: compat systemd
> group:  compat systemd
> shadow: compat
> gshadow:compat
> 
> hosts:  files dns
> networks:   files
> 
> protocols:  db files
> services:   db files
> ethers: db files
> rpc:db files
> 
> netgroup:   nis
> 
> vagrant@debian:/etc$ cat /etc/passwd
> root:x:0:0:root:/root:/bin/bash
> daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
> bin:x:2:2:bin:/bin:/usr/sbin/nologin
> sys:x:3:3:sys:/dev:/usr/sbin/nologin
> sync:x:4:65534:sync:/bin:/bin/sync
> games:x:5:60:games:/usr/games:/usr/sbin/nologin
> man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
> lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
> mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
> news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
> uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
> proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
> www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
> backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
> list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
> irc:x:39:39:ircd:/run/ircd:/usr/sbin/nologin
> gnats:x:41:41:Gnats Bug-Reporting System 
> (admin):/var/lib/gnats:/usr/sbin/nologin
> nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
> _apt:x:100:65534::/nonexistent:/usr/sbin/nologin
> systemd-timesync:x:101:101:systemd Time 
> Synchronization,,,:/run/systemd:/usr/sbin/nologin
> systemd-network:x:102:103:systemd Network 
> Management,,,:/run/systemd:/usr/sbin/nologin
> systemd-resolve:x:103:104:systemd Resolver,,,:/run/systemd:/usr/sbin/nologin
> messagebus:x:104:105::/nonexistent:/usr/sbin/nologin
> _chrony:x:105:112:Chrony daemon,,,:/var/lib/chrony:/usr/sbin/nologin
> sshd:x:106:65534::/run/sshd:/usr/sbin/nologin
> vagrant:x:1000:1000::/home/vagrant:/bin/bash
> systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
> _rpc:x:107:65534::/run/rpcbind:/usr/sbin/nologin
> +::
> 
> 
> My next step will be running a full-sid setup for a test network, but I don't
> see any reason why the working NIS maps could be broken, my guess is that
> the problem is connected to some inner libnss/libc issue. 

This was actually a bug in libc6, which affected the compat module,
while explicitly using the nis module worked. This has been introduced
in glibc 2.33 and fixed in glibc 2.34 that just landed in sid.

Merging this bug with the existing one on the libc6 side.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#999850: ITP: maturin -- Build and publish crates with pyo3, rust-cpython and cffi bindings as well as rust binaries as python packages.

[Thomas Goirand]

Hi Jelmer,

Any progress here? It'd be nice if you could update the status if this 
package. FYI, it's needed by orjson, which I would also need for 
home-assistant (which I'm attempting to package, but not ITP for this yet).


Cheers,

Thomas Goirand (zigo)

Bug#1016576: transition: glibc 2.34

[Aurelien Jarno]

On 2022-08-07 21:40, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> Control: forwarded -1 
> https://release.debian.org/transitions/html/glibc-2.34.html
> 
> On 2022-08-03 11:49:20 +0200, Aurelien Jarno wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > X-Debbugs-Cc: debian-gl...@lists.debian.org
> > 
> > Dear release team,
> > 
> > I would like to get a transition slot for glibc 2.34. It has been
> > available in experimental for a few months, and does not have any known
> > major issue. It has been built successfully on all release architectures
> > and many ports architectures.
> 
> Please go ahead.

Thanks, I have just uploaded it.

Cheers
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#1016812: [Pkg-javascript-devel] Bug#1016812: nodex-expat: autopkgtest failure with nodejs 18.6

[Yadd]

Control: tags -1 + moreinfo

On 07/08/2022 22:25, Sebastian Ramacher wrote:

Source: node-expat
Version: 2.4.0+ds-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-expat/24419068/log.gz


autopkgtest [20:11:40]: test command2: vows --spec ./test/**/*.js
autopkgtest [20:11:40]: test command2: [---
/usr/share/nodejs/bindings/bindings.js:121
 throw e;
 ^

Error: The module 
'/usr/lib/x86_64-linux-gnu/nodejs/node-expat/build/Release/node_expat.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 93. This version of Node.js requires
NODE_MODULE_VERSION 108. Please try re-compiling or re-installing


Hi,

this package should simply be rebuilt (+b1), isn't it ? Local 
rebuild+autopkgtest succeeds


Cheers,
Yadd

Bug#1016815: Updating proofgeneral to recent upstream

[julien . puydt]

Package: proofgeneral
Version: 4.4.1~pre170114-1.2
Severity: wishlist

Hi,

upstream released version 4.5 less than a month ago:
https://github.com/ProofGeneral/PG/tags

would it be possible to update the package?

Thanks,

J.Puydt

Bug#1016811: libwebkit2gtk-4.0-37: bullseye backport crashes a lot on arm64

[Sebastian Krzyszkowiak]

For the record, I've just realized that the system I reported it from
was lacking bullseye-security updates, but I've checked it now on a
fully up-to-date arm64 system with webkit2gtk 2.36.4-1~deb11u1 and
it's still crashing in the same way.

Bug#1016814: libqt5gui5:amd64: Conditional jump or move depends on uninitialised value(s)

[Thorsten Glaser]

Package: libqt5gui5
Version: 5.15.2+dfsg-9
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de

Running a Qt application (musescore3) against Valgrind shows:

==27770== Conditional jump or move depends on uninitialised value(s)
==27770==at 0x7470A2E: __vfprintf_internal (vfprintf-internal.c:1687)
==27770==by 0x74839C5: __vsnprintf_internal (vsnprintf.c:114)
==27770==by 0x7511D30: __snprintf_chk (snprintf_chk.c:38)
==27770==by 0xB50DA79: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
==27770==by 0xB50F232: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
==27770==by 0xB50FC92: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
==27770==by 0xB50A403: QXcbConnection::QXcbConnection(QXcbNativeInterface*, 
bool, unsigned int, char const*) (in 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
==27770==by 0xB50D112: QXcbIntegration::QXcbIntegration(QStringList const&, 
int&, char**) (in /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)
==27770==by 0x485346E: ??? (in 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so)
==27770==by 0x67438FB: QGuiApplicationPrivate::createPlatformIntegration() 
(in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
==27770==by 0x6744D4F: QGuiApplicationPrivate::createEventDispatcher() (in 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.15.2)
==27770==by 0x6F86A55: QCoreApplicationPrivate::init() (in 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.2)
==27770==  Uninitialised value was created by a stack allocation
==27770==at 0xB50E7A0: ??? (in 
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.15.2)

I don’t always see this. In this example, $DISPLAY points to Xtightvnc
from tightvncserver (= 1:1.3.10-3).


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

Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages libqt5gui5:amd64 depends on:
ii  fontconfig2.13.1-4.2
ii  libc6 2.31-13+deb11u3
ii  libdrm2   2.4.104-1
ii  libegl1   1.3.2-1
ii  libfontconfig12.13.1-4.2
ii  libfreetype6  2.10.4+dfsg-1+deb11u1
ii  libgbm1   20.3.5-1
ii  libgcc-s1 10.2.1-6
ii  libgl11.3.2-1
ii  libglib2.0-0  2.66.8-1
ii  libharfbuzz0b 2.7.4-1
ii  libice6   2:1.0.10-1
ii  libinput101.16.4-3
ii  libjpeg62-turbo   1:2.0.6-4
ii  libmd4c0  0.4.7-2
ii  libmtdev1 1.1.6-1
ii  libpng16-16   1.6.37-3
ii  libqt5core5a [qtbase-abi-5-15-2]  5.15.2+dfsg-9
ii  libqt5dbus5   5.15.2+dfsg-9
ii  libqt5network55.15.2+dfsg-9
ii  libsm62:1.2.3-1
ii  libstdc++610.2.1-6
ii  libudev1  247.3-7
ii  libx11-6  2:1.7.2-1
ii  libx11-xcb1   2:1.7.2-1
ii  libxcb-glx0   1.14-3
ii  libxcb-icccm4 0.4.1-1.1
ii  libxcb-image0 0.4.0-1+b3
ii  libxcb-keysyms1   0.4.0-1+b2
ii  libxcb-randr0 1.14-3
ii  libxcb-render-util0   0.3.9-1+b1
ii  libxcb-render01.14-3
ii  libxcb-shape0 1.14-3
ii  libxcb-shm0   1.14-3
ii  libxcb-sync1  1.14-3
ii  libxcb-xfixes01.14-3
ii  libxcb-xinerama0  1.14-3
ii  libxcb-xinput01.14-3
ii  libxcb-xkb1   1.14-3
ii  libxcb1   1.14-3
ii  libxkbcommon-x11-01.0.3-2
ii  libxkbcommon0 1.0.3-2
ii  libxrender1   1:0.9.10-1
ii  zlib1g1:1.2.11.dfsg-2+deb11u1

Versions of packages libqt5gui5:amd64 recommends:
ii  libqt5svg5 5.15.2-3
pn  qt5-gtk-platformtheme  

Versions of packages libqt5gui5:amd64 suggests:
pn  qt5-image-formats-plugins  
pn  qtwayland5 

-- no debconf information

Bug#1016813: swupdate: FTBFS on armhf

[Sebastian Ramacher]

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

https://buildd.debian.org/status/fetch.php?pkg=swupdate&arch=armhf&ver=2022.05-1%2Bb1&stamp=1659901160&raw=0

/usr/bin/ld: 
suricatta/lib.a(server_hawkbit.o):./suricatta/server_hawkbit.c:1260: more 
undefined references to `notify' follow
/usr/bin/ld: suricatta/lib.a(server_hawkbit.o): in function 
`server_process_update_artifact':
./suricatta/server_hawkbit.c:1114: undefined reference to `loglevel'
/usr/bin/ld: suricatta/lib.a(server_hawkbit.o): in function 
`server_install_update':
./suricatta/server_hawkbit.c:1458: undefined reference to `notify'
/usr/bin/ld: ./suricatta/server_hawkbit.c:1471: undefined reference to `notify'
/usr/bin/ld: ./suricatta/server_hawkbit.c:1474: undefined reference to `notify'
/usr/bin/ld: ./suricatta/server_hawkbit.c:1353: undefined reference to `notify'
/usr/bin/ld: ./suricatta/server_hawkbit.c:1366: undefined reference to `notify'
/usr/bin/ld: 
suricatta/lib.a(server_hawkbit.o):./suricatta/server_hawkbit.c:1377: more 
undefined references to `notify' follow
/usr/bin/ld: suricatta/lib.a(server_hawkbit.o): in function `snprintf':
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:71: undefined reference to 
`loglevel'
/usr/bin/ld: fs/lib.a(diskformat.o): in function `diskformat_fs_detect':
./fs/diskformat.c:60: undefined reference to `notify'
/usr/bin/ld: ./fs/diskformat.c:53: undefined reference to `notify'
/usr/bin/ld: fs/lib.a(diskformat.o): in function `snprintf':
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:71: undefined reference to 
`loglevel'
/usr/bin/ld: fs/lib.a(diskformat.o): in function `diskformat_mkfs':
./fs/diskformat.c:106: undefined reference to `notify'
/usr/bin/ld: ./fs/diskformat.c:110: undefined reference to `notify'
/usr/bin/ld: ./fs/diskformat.c:102: undefined reference to `notify'
/usr/bin/ld: fs/lib.a(diskformat.o): in function `snprintf':
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:71: undefined reference to 
`loglevel'
/usr/bin/ld: fs/lib.a(diskio.o): in function `fatfs_init':
./fs/diskio.c:39: undefined reference to `notify'
/usr/bin/ld: fs/lib.a(diskio.o): in function `snprintf':
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:71: undefined reference to 
`loglevel'
/usr/bin/ld: fs/lib.a(diskio.o): in function `disk_ioctl':
./fs/diskio.c:152: undefined reference to `notify'
/usr/bin/ld: fs/lib.a(diskio.o): in function `snprintf':
/usr/include/arm-linux-gnueabihf/bits/stdio2.h:71: undefined reference to 
`loglevel'
/usr/bin/ld: link errors found, deleting executable `test/test_server_hawkbit'
collect2: error: ld returned 1 exit status
make[3]: *** [/<>/test/Makefile:72: test/test_server_hawkbit.lnk] 
Error 1
make[3]: *** Waiting for unfinished jobs
make[2]: *** [Makefile:498: test] Error 2


Cheers
-- 
Sebastian Ramacher

Bug#1016812: nodex-expat: autopkgtest failure with nodejs 18.6

[Sebastian Ramacher]

Source: node-expat
Version: 2.4.0+ds-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-expat/24419068/log.gz


autopkgtest [20:11:40]: test command2: vows --spec ./test/**/*.js
autopkgtest [20:11:40]: test command2: [---
/usr/share/nodejs/bindings/bindings.js:121
throw e;
^

Error: The module 
'/usr/lib/x86_64-linux-gnu/nodejs/node-expat/build/Release/node_expat.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 93. This version of Node.js requires
NODE_MODULE_VERSION 108. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Module._extensions..node (node:internal/modules/cjs/loader:1204:18)
at Module.load (node:internal/modules/cjs/loader:998:32)
at Module._load (node:internal/modules/cjs/loader:839:12)
at Module.require (node:internal/modules/cjs/loader:1022:19)
at require (node:internal/modules/cjs/helpers:102:18)
at bindings (/usr/share/nodejs/bindings/bindings.js:112:48)
at Object. 
(/usr/lib/x86_64-linux-gnu/nodejs/node-expat/lib/node-expat.js:4:34)
at Module._compile (node:internal/modules/cjs/loader:1120:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
at Module.load (node:internal/modules/cjs/loader:998:32) {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.6.0
bash: line 1:  1832 Aborted bash -ec 'vows --spec 
./test/**/*.js' 2> >(tee -a 
/tmp/autopkgtest-lxc.ny14wys2/downtmp/command2-stderr >&2) > >(tee -a 
/tmp/autopkgtest-lxc.ny14wys2/downtmp/command2-stdout)
autopkgtest [20:11:40]: test command2: ---]
autopkgtest [20:11:40]: test command2:  - - - - - - - - - - results - - - - - - 
- - - -
command2 FAIL non-zero exit status 134
autopkgtest [20:11:40]: test command2:  - - - - - - - - - - stderr - - - - - - 
- - - -
/usr/share/nodejs/bindings/bindings.js:121
throw e;
^

Error: The module 
'/usr/lib/x86_64-linux-gnu/nodejs/node-expat/build/Release/node_expat.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 93. This version of Node.js requires
NODE_MODULE_VERSION 108. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
at Module._extensions..node (node:internal/modules/cjs/loader:1204:18)
at Module.load (node:internal/modules/cjs/loader:998:32)
at Module._load (node:internal/modules/cjs/loader:839:12)
at Module.require (node:internal/modules/cjs/loader:1022:19)
at require (node:internal/modules/cjs/helpers:102:18)
at bindings (/usr/share/nodejs/bindings/bindings.js:112:48)
at Object. 
(/usr/lib/x86_64-linux-gnu/nodejs/node-expat/lib/node-expat.js:4:34)
at Module._compile (node:internal/modules/cjs/loader:1120:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
at Module.load (node:internal/modules/cjs/loader:998:32) {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.6.0
autopkgtest [20:11:41]:  summary
command1 FAIL non-zero exit status 134
command2 FAIL non-zero exit status 134


Cheers
-- 
Sebastian Ramacher

Bug#991113: libpam-chroot: pam_chroot.so installed in wrong place - Not able to login after upgrade

[M. Buecher]

The pam-chroot source code from Ed Schmollinger is currently at: 
https://github.com/gpjt/pam-chroot


Maybe he is willing to create an GitHub Organization and add you as a 
developer.

Or he even is willing switch to Salsa.

Kind regards
Matthias "Maddes" Bücher

Bug#1016811: libwebkit2gtk-4.0-37: bullseye backport crashes a lot on arm64

[Sebastian Krzyszkowiak]

Package: libwebkit2gtk-4.0-37
Version: 2.36.3-1~deb11u1
Severity: important
X-Debbugs-Cc: d...@dosowisko.net, t...@security.debian.org

Dear Maintainer,

since 2.36.0-3~deb11u1, webkit2gtk in bullseye has been almost unusable on
arm64 computers, crashing a lot when navigating between pages.

An easy way to reproduce is to navigate to https://news.ycombinator.com/
and click some link (for example, "new" or "login"); or navigate to
https://mobile.twitter.com/ which makes it crash right away. Crashes
are reproducible in both GNOME Web and in MiniBrowser shipped by
webkit2gtk package.

This has been seen on various machines and in downstream distros like PureOS
as well (https://source.puri.sm/Librem5/debs/epiphany/-/issues/38)

Example backtrace:

[🡕] Process 14397 (WebKitNetworkPr) of user 1000 dumped core.
   
Stack trace of thread 14397:
#0  0x914f92ac __GI_raise (libc.so.6 + 0x372ac)
#1  0x914e5ea0 __GI_abort (libc.so.6 + 0x23ea0)
#2  0x93f89c50 _Z16WTFCrashWithInfoiPKcS0_i 
(libjavascriptcoregtk-4.0.so.18 + 0x198c50)
#3  0x94f2a138 _ZN3WTF10StackTrace17captureStackTraceEii 
(libjavascriptcoregtk-4.0.so.18 + 0x1139138)
#4  0x94f05a30 WTFReleaseLogStackTrace (libjavascriptcoregtk-4.0.so.18 
+ 0x1114a30)
#5  0x97f02988 _ZN7WebCore13internalErrorERKN3WTF3URLE 
(libwebkit2gtk-4.0.so.37 + 0x214a988)
#6  0x966038e0 
_ZN6WebKit29NetworkConnectionToWebProcess12preconnectToESt8optionalIN3WTF16ObjectIdentifierIN7WebCore14ResourceLoaderONS_29NetworkResourceLoadParametersE
 (libwebkit2gtk-4.0.so.37 + 0x84b8e0)
#7  0x964e0eb8 
_ZN6WebKit29NetworkConnectionToWebProcess46didReceiveNetworkConnectionToWebProcessMessageERN3IPC10ConnectionERNS1_7DecoderE
 (libwebkit2gtk-4.0.so.37 + 0x728eb8)
#8  0x9676eb70 
_ZN3IPC10Connection15dispatchMessageESt10unique_ptrINS_7DecoderESt14default_deleteIS2_EE
 (libwebkit2gtk-4.0.so.37 + 0x9b6b70)
#9  0x9676ef08 _ZN3IPC10Connection26dispatchOneIncomingMessageEv 
(libwebkit2gtk-4.0.so.37 + 0x9b6f08)
#10 0x94f28ad0 _ZN3WTF7RunLoop11performWorkEv 
(libjavascriptcoregtk-4.0.so.18 + 0x1137ad0)
#11 0x94f819f4 _ZZN3WTF7RunLoopC1EvEN3$_18__invokeEPv 
(libjavascriptcoregtk-4.0.so.18 + 0x11909f4)
#12 0x94f80d88 _ZN3WTF7RunLoop3$_08__invokeEP8_GSourcePFiPvES4_ 
(libjavascriptcoregtk-4.0.so.18 + 0x118fd88)
#13 0x91a53ab4 g_main_dispatch (libglib-2.0.so.0 + 0x53ab4)
#14 0x91a53e5c g_main_context_iterate (libglib-2.0.so.0 + 0x53e5c)
#15 0x91a541b0 g_main_loop_run (libglib-2.0.so.0 + 0x541b0)
#16 0x94f81384 _ZN3WTF7RunLoop3runEv (libjavascriptcoregtk-4.0.so.18 + 
0x1190384)
#17 0x9674287c 
_ZN6WebKit20AuxiliaryProcessMainINS_22NetworkProcessMainSoupEEEiiPPc 
(libwebkit2gtk-4.0.so.37 + 0x98a87c)
#18 0x914e6218 __libc_start_main (libc.so.6 + 0x24218)
#19 0x00400874 $x (WebKitNetworkProcess + 0x874)
#20 0x00400874 $x (WebKitNetworkProcess + 0x874)

[🡕] Process 14382 (WebKitWebProces) of user 1000 dumped core.
   
Stack trace of thread 2:
#0  0x854082ac __GI_raise (libc.so.6 + 0x372ac)
#1  0x853f4ea0 __GI_abort (libc.so.6 + 0x23ea0)
#2  0x87e98c50 _Z16WTFCrashWithInfoiPKcS0_i 
(libjavascriptcoregtk-4.0.so.18 + 0x198c50)
#3  0x88e39138 _ZN3WTF10StackTrace17captureStackTraceEii 
(libjavascriptcoregtk-4.0.so.18 + 0x1139138)
#4  0x88e14a30 WTFReleaseLogStackTrace (libjavascriptcoregtk-4.0.so.18 
+ 0x1114a30)
#5  0x8be11988 _ZN7WebCore13internalErrorERKN3WTF3URLE 
(libwebkit2gtk-4.0.so.37 + 0x214a988)
#6  0x8a9c1824 
_ZN6WebKit17WebLoaderStrategy30internallyFailedLoadTimerFiredEv 
(libwebkit2gtk-4.0.so.37 + 0xcfa824)
#7  0x88e90aa0 _ZZN3WTF7RunLoop9TimerBaseC1ERS0_EN3$_38__invokeEPv 
(libjavascriptcoregtk-4.0.so.18 + 0x1190aa0)
#8  0x88e8fd88 _ZN3WTF7RunLoop3$_08__invokeEP8_GSourcePFiPvES4_ 
(libjavascriptcoregtk-4.0.so.18 + 0x118fd88)
#9  0x85962ab4 g_main_dispatch (libglib-2.0.so.0 + 0x53ab4)
#10 0x85962e5c g_main_context_iterate (libglib-2.0.so.0 + 0x53e5c)
#11 0x859631b0 g_main_loop_run (libglib-2.0.so.0 + 0x541b0)
#12 0x88e90384 _ZN3WTF7RunLoop3runEv (libjavascriptcoregtk-4.0.so.18 + 
0x1190384)
#13 0x8aa7b2b4 
_ZN6WebKit20AuxiliaryProcessMainINS_17WebProcessMainGtkEEEiiPPc 
(libwebkit2gtk-4.0.so.37 + 0xdb42b4)
#14 0x853f5218 __libc_start_main (libc.so.6 + 0x24218)
#15 0x00400874 $x (WebKitWebProcess + 0x874)
#16 0x00400874 $x (WebKitWebProcess + 0x874)


-- System Information:
Debian Release: 11.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'stable-security')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

Kernel: Linux 5.15.52-rockchip64 (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),

Bug#938638: telepathy-glib: Python2 removal in sid/bullseye

[Paul Gevers]

Control: tag -1 fixed-upstream

Hi,

On Fri, 30 Aug 2019 07:55:19 + Matthias Klose  wrote:

Package: src:telepathy-glib



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

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


This seems to have happened upstream if I look at the history of the 
latest release:

https://cgit.freedesktop.org/telepathy/telepathy-glib/log/?h=telepathy-glib-0.24

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016416: Coq-related packages transition - coq-elpi

[julien . puydt]

Le dimanche 07 août 2022 à 21:15 +0200, Sebastian Ramacher a écrit :
> On 2022-08-07 11:01:30 +0200, julien.pu...@gmail.com wrote:
> > Hi,
> > 
> > Le mardi 02 août 2022 à 21:43 +0200, Sebastian Ramacher a écrit :
> > > On 2022-07-31 13:23:38 +0200, julien.pu...@gmail.com wrote:
> > > > Package: release.debian.org
> > > > 
> > > > Some Coq-related packages need a rebuild:
> > > > 
> > > > coq-hierarchy-builder
> > > > mathcomp-algebra-tactics mathcomp-analysis
> > > > 
> > > > where packages on the same line can be handled in parallel.
> > > > 
> > > > I can't give a nice ben script because the abi checksum varies
> > > > with
> > > > the
> > > > architecture (see today's mail on debian-devel where I'm trying
> > > > to
> > > > find
> > > > ideas for a better approach).
> > > 
> > > From the discussion on -devel, a permanent tracker like the one
> > > for
> > > Haskell
> > > (https://release.debian.org/transitions/html/haskell.html)
> > > could
> > > help with the rebuilds for coq-* and related packages. Do all
> > > affected
> > > packages depends on some package that we can use as a basis for
> > > the
> > > permapermanent tracker?
> > 
> > Short answer: no.
> 
> What about build-dependencies on dh-coq? Is
> https://release.debian.org/transitions/html/coq.html missing any
> coq-related packages?
> 

The idea to use dh-coq as a marker for Coq-related packages is indeed a
good one, and means no list needs to get updated. Your list does
contain everything in Debian. [Notice: I also have two packages more,
coq-libhyps and coq-relation-algebra -- I have them locally but didn't
upload yet because of pending licensing issues.]

Here is what my script testing installed packages prints ; it should
give an idea of what a full tracker should consider:

Hauteur 1
coq... ok
Hauteur 2
aac-tactics... ok
coq-bignums... ok
coq-dpdgraph... ok
coq-elpi... ok
coq-ext-lib... ok
coq-hammer... ok
coq-hott... ok
coq-libhyps... ok
coq-menhirlib... ok
coq-record-update... ok
coq-reduction-effects... ok
coq-stdpp... ok
coq-unicoq... ok
coq-unimath... ok
flocq... ok
ott... ok
paramcoq... ok
ssreflect... ok
Hauteur 3
coq-deriving... ok
coq-equations... ok
coq-gappa... ok
coq-hierarchy-builder... ok
coq-iris... ok
coq-math-classes... ok
coq-mtac2... ok
coqprime... ok
coq-reglang... ok
coq-relation-algebra... ok
coq-simple-io... ok
coquelicot... ok
mathcomp-bigenough... ok
mathcomp-finmap... ok
mathcomp-zify... ok
Hauteur 4
coq-corn... ok
coq-extructures... ok
coq-interval... ok
coq-quickchick... ok
mathcomp-algebra-tactics... ok
mathcomp-analysis... ok
mathcomp-multinomials... ok
mathcomp-real-closed... ok
Hauteur 5
coqeal... ok


So checking for dh-coq should give a whole-tree tracker, but does that
help with partial updates?

Cheers,

J.Puydt

Bug#1016810: i386 package should ship x86_64 binfmt

[VA]

Package: qemu-user-binfmt
Version: 1:7.0+dfsg-7

Architectures that are not i386 or amd64 ship files like
/usr/lib/binfmt.d/qemu-x86_64.conf and /usr/lib/binfmt.d/qemu-i386.conf

However, i386 and amd64 flavours of the package ship neither.
The i386 flavour should ship x86_64 related files, and conversely.

Not having them prevents from using mmdebstrap to install an amd64 
system from a i386 system:


I: automatically chosen mode: root
update-binfmts: warning: qemu-x86_64 not in database of installed binary 
formats.

update-binfmts: exiting due to previous errors
W: qemu-x86_64 is not a supported binfmt name
E: amd64 can neither be executed natively nor via qemu user emulation 
with binfmt_misc

Bug#1016576: transition: glibc 2.34

[Sebastian Ramacher]

Control: tags -1 confirmed
Control: forwarded -1 
https://release.debian.org/transitions/html/glibc-2.34.html

On 2022-08-03 11:49:20 +0200, Aurelien Jarno wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: debian-gl...@lists.debian.org
> 
> Dear release team,
> 
> I would like to get a transition slot for glibc 2.34. It has been
> available in experimental for a few months, and does not have any known
> major issue. It has been built successfully on all release architectures
> and many ports architectures.

Please go ahead.

Cheers

> 
> This transition is a bit more complex than the previous ones, as this
> version merges a few libraries (libpthread, libdl, libutil, libanl) into
> libc. This handled transparently at runtime.
> 
> This is also supposed to be handled transparently at link time by
> providing empty static archives for libpthread.a, libdl.a, libutil.a,
> libanl.a. That said it appears that the path to libpthread.so and
> libdl.so is encoded in a few cmake files). Breaks against the affected
> -dev packages have been added, and they will need to be binNMUed. Here
> is the list:
> 
> assimp
> deal.ii
> dolfin
> eckit
> fclib
> fltk1.3
> insighttoolkit4
> insighttoolkit5
> ismrmrd
> libminc
> log4cplus
> mathgl
> mimalloc
> mongo-c-driver
> mrpt
> netcdf
> netcdf-parallel
> ns3
> openms
> trilinos
> visp
> votca
> vtk6
> vtk7
> 
> In addition some symbols from libresolv symbols also got moved to libc,
> and their __ prefix dropped at the same time. While there compatibility
> symbols for dynamic linking, it it not the case for static linking.
> Static libraries with reference to those symbols needs to be binNMUed.
> Breaks against the affected -dev packages have been added, and they will
> need to be binNMUed. Here is the list:
> 
> boinc
> cups
> dante
> glib2.0
> gloox
> haskell-resolv
> heimdal
> hesiod
> libasyncns
> libaws
> libdkim
> libinfinity
> libpg-query
> libre
> libspf2
> libstrophe
> linux-atm
> loudmouth
> mongo-c-driver
> mysql-8.0
> ncbi-igblast
> nfs-utils
> ola
> openafs
> opendkim
> opendmarc
> openldap
> open-vm-tools
> openzwave
> pidgin-librvp
> proftpd-dfsg
> shishi
> slurm-wlm
> taningia
> 
> A few issues found through the autopkgtest pseudo excuses for
> experimental have been fixed. Most of the remaining are either due to
> the added breaks (see above), britney bugs or packages parts of the
> transition. There are a few remaining though, but at this stage it's
> probably better to move forward and get them fixed later, otherwise new
> ones keep appearing. Here is the list:
> 
> castle-game-engine: #1016556
> dash: #1016554
> fpc: #1016556
> scalpel: #1016560
> securefs: #993515
> wmanager: #1016540 
> wcc: #1014729 (A binNMU fixes the issue, but not sure why)
> 
> A tracker is already setup at:
> https://release.debian.org/transitions/html/glibc-2.34.html
> 
> Thanks for considering.
> 
> Regards
> Aurelien
> 

-- 
Sebastian Ramacher

Bug#1016416: Coq-related packages transition - coq-elpi

[Sebastian Ramacher]

On 2022-08-07 11:01:30 +0200, julien.pu...@gmail.com wrote:
> Hi,
> 
> Le mardi 02 août 2022 à 21:43 +0200, Sebastian Ramacher a écrit :
> > On 2022-07-31 13:23:38 +0200, julien.pu...@gmail.com wrote:
> > > Package: release.debian.org
> > > 
> > > Some Coq-related packages need a rebuild:
> > > 
> > > coq-hierarchy-builder
> > > mathcomp-algebra-tactics mathcomp-analysis
> > > 
> > > where packages on the same line can be handled in parallel.
> > > 
> > > I can't give a nice ben script because the abi checksum varies with
> > > the
> > > architecture (see today's mail on debian-devel where I'm trying to
> > > find
> > > ideas for a better approach).
> > 
> > From the discussion on -devel, a permanent tracker like the one for
> > Haskell (https://release.debian.org/transitions/html/haskell.html)
> > could
> > help with the rebuilds for coq-* and related packages. Do all
> > affected
> > packages depends on some package that we can use as a basis for the
> > permapermanent tracker?
> 
> Short answer: no.

What about build-dependencies on dh-coq? Is
https://release.debian.org/transitions/html/coq.html missing any
coq-related packages?

Cheers
-- 
Sebastian Ramacher

Bug#1016756: transition: meshoptimizer

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2022-08-06 18:37:55 +0200, Timo Röhling wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> I'd like to transition meshoptimizer after a SONAME bump.
> The only reverse dependency, filament, builds fine on amd64.
> 
> The auto-generated transition
> https://release.debian.org/transitions/html/auto-meshoptimizer.html
> also looks good.

Please go ahead

Cheers
-- 
Sebastian Ramacher

Bug#1016763: transition: foonathan-memory

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2022-08-06 21:11:43 +0200, Timo Röhling wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear Release Team,
> 
> I'd like to transition foonathan-memory after a SONAME bump.
> Its reverse dependency fastdds builds fine on amd64.
> 
> The auto-generated transition
> https://release.debian.org/transitions/html/auto-foonathan-memory.html
> also looks good.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#1016808: debcargo does not handle extra features for dev-dependencies declared in the features section.

[Peter Michael Green]

Package: debcargo
Version: 2.5.0-3

Alexander Kjäll was working on packaging wl-clipboard-rs when he ran 
into an autopkgtest failure.

debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/tmp/tmp.Zo0aVr3cJs/registry/
debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', '-j4', 
'--target', 'x86_64-unknown-linux-gnu', '--all-targets', 
'--no-default-features', '--features', 'native_lib'],) {}
error: no matching package named `parking_lot` found
location searched: registry `crates-io`
required by package `wayland-server v0.29.4`
 ... which satisfies dependency `wayland-server = "^0.29.4"` of package 
`wl-clipboard-rs v0.6.0 (/usr/share/cargo/registry/wl-clipboard-rs-0.6.0)`


Investigating showed that Cargo.toml contains the following


[dev-dependencies.wayland-server]
version = "0.29.4"

[features]
dlopen = ["native_lib", "wayland-client/dlopen", "wayland-server/dlopen"]
native_lib = ["wayland-client/use_system_lib", 
"wayland-server/use_system_lib"]
If I am reading this correctly this means that when running tests with 
the "native_lib" feature enabled, the "use_system_lib" feature of the 
wayland-server package will be enabled.


However debcargo does not generate a test dependency on 
librust-wayland-server+use-system-lib-dev


I believe this is the result of the error Alexander encountered (and I 
reproduced)


The packaging for wl-clipboard-rs ia available in the 
WIP-wl-clipboard-rs branch of debcargo-conf.

Bug#1016807: linux-image-5.18.0-3-arm64: Please enable CONFIG_SPI_GPIO, CONFIG_SPI_SUN6I for arm64 (Allwinner A64)

[Jonathan Hettwer (bauen1)]

Source: linux
Severity: wishlist
X-Debbugs-Cc: j24...@gmail.com

Dear Linux Maintainers,

I have a pine a64-lts SBC running arm64 debian unstable.
A SPI NOR flash and a TPM2.0 are connected over SPI, but the
kernel is currently build without the modules required to access them.

To access both, I need the CONFIG_SPI_SUN6I as module for the builtin
SPI bus, and CONFIG_SPI_GPIO for accessing the TPM connected over a
non-standard SPI bus.

Thanks in advance.

-- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-2-amd64 (SMP w/8 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: SELinux: enabled - Mode: Enforcing - Policy name: bauen1-policy

Bug#1008082: How to --lock an account

[Marc Haber]

On Sun, Aug 07, 2022 at 01:05:13PM -0400, Jason Franklin wrote:
> On Wed, Jul 27, 2022 at 03:21:08PM +0200, Marc Haber wrote:
> > > Before I start, I want to make sure we agree on what should be done.
> > > 
> > > I asserted that two things were sufficient:
> > >   1. Put a '!' in front of the user's password in /etc/shadow
> > >   2. Expire the account
> > > 
> > > This makes it trivial to unlock an account with all of its attributes
> > > intact, including login shell.
> > 
> > I think that having nologin as a shell has the advantage of giving a
> > clear error message IF somebody manages to log in to the expired account
> > with an invalid password.
> 
> The message with /usr/sbin/nologin is indeed nice. On my system, I get
> something like...
> 
> | $ su --login foo
> | Password:
> | This account is currently not available.

Yes, that's what I'd like to have, but of course, if the account is
password-locked and expired, getting at this point is already a bug.

> With password locking plus account expiration, I get...
> 
> | $ su --login fish
> | Password: 
> | su: Authentication failure
> 
> I find it odd that I get a password prompt for an account that is
> expired, but so it is.

I think that the idea is not to give information that an account is
expired, indicating an unused accout.

> My only reason for saying it's not necessary is that someone being able
> to log in to an expired account would indicate a bug somewhere else that
> should be fixed (in shadow, maybe?). If account expiration cannot be
> relied upon, we have a bigger security concern, I think.

I think so, and it's not our bug anyway, but it would probably be nice
to implement Defense in Depth.

> > For a normal user account, I am undecided whether:
> > 
> > - leave login shell intact, leaving a possible security hole
> 
> Again, this is where I am not so sure.
> 
> If there is a security hole, it would be someone else's, right?

Right.

> Account expiration is either reliable or it is not.

If a system account is migrated to a directory service (which is
possible), we might not have write access to the account expiration data
and to the hashed password.

> > - set login shell back to the default when the account gets reenabled
> > - save login shell somewhere to reinstate if on reenabling.
> > 
> > I'd say, do it as you see fit, changing that at a later time would be a
> > rather isolated change so I'm fine with going ahead either way here,
> > while still having a personal preference for the third possibility, but
> > I am not the one who decides that.
> 
> This is fair.
> 
> As soon as I'm done with the other bug I'm working on, I'll move to this
> one and proceed with the stateless implementation.
> 
> Saving and restoring a user's shell can be added later if needed.
> 
> Sound good?

Proceed, but please document that we are still considering to change
login shell at a later time.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#1016806: request-tracker5: FTBFS with Perl 5.36: Subroutine JSON::PP::Boolean::(0+ redefined

[Niko Tyni]

Source: request-tracker5
Version: 5.0.3+dfsg-1
Severity: important
Tags: ftbfs
User: debian-p...@lists.debian.org
Usertags: perl-5.36-transition

This package fails its test suite with Perl 5.36 (currently in experimental.)

All the test failures seem to be about the same warning:

  # Subroutine JSON::PP::Boolean::(++ redefined at 
/usr/lib/x86_64-linux-gnu/perl-base/overload.pm line 52.

which obviously doesn't trigger on sid.

I haven't got to the bottom of this yet and I don't have a standalone
test case.  It doesn't seem to be anything simple like a newer version
of JSON::PP. Search engines refer to old issues with similar diagnostics
which should be long fixed.

Could you ask upstream if they can at least reproduce it?


Build log at

  
http://perl.debian.net/rebuild-logs/perl-5.36-throwaway/request-tracker5_5.0.3+dfsg-1/request-tracker5_5.0.3+dfsg-1_amd64-2022-07-21T09:33:03Z.build

Excerpt:

   #   Failed test 'no warnings'
   #   at /<>/lib/RT/Test.pm line 1796.
   # There were 3 warning(s)
   # Previous test 0 ''
   # Subroutine JSON::PP::Boolean::(++ redefined at 
/usr/lib/x86_64-linux-gnu/perl-base/overload.pm line 52.
   #  at /usr/lib/x86_64-linux-gnu/perl-base/overload.pm line 52.
   #overload::OVERLOAD("JSON::PP::Boolean", "0+", CODE(0x561a9651eee0), 
"++", CODE(0x561a9651ef40), "--", CODE(0x561a9651efd0), "\"\"", ...) called at 
/usr/lib/x86_64-linux-gnu/perl-base/overload.pm line 61
   #overload::import("overload", "0+", CODE(0x561a9651eee0), "++", 
CODE(0x561a9651ef40), "--", CODE(0x561a9651efd0), "\"\"", ...) called at 
/usr/lib/x86_64-linux-gnu/perl5/5.36/Cpanel/JSON/XS.pm line 2365
   #Cpanel::JSON::XS::BEGIN() called at 
/usr/lib/x86_64-linux-gnu/perl5/5.36/Cpanel/JSON/XS.pm line 2366

[...]

   Test Summary Report
   ---
   t/api/initialdata-roundtrip.t(Wstat: 256 (exited 1) 
Tests: 28 Failed: 1)
 Failed test:  28
 Non-zero exit status: 1
   t/rest2/articles.t   (Wstat: 256 (exited 1) 
Tests: 77 Failed: 1)
 Failed test:  77
 Non-zero exit status: 1
   t/rest2/article-customfields.t   (Wstat: 256 (exited 1) 
Tests: 147 Failed: 1)
 Failed test:  147
 Non-zero exit status: 1
   t/rest2/asset-customfields.t (Wstat: 256 (exited 1) 
Tests: 155 Failed: 1)
 Failed test:  155
 Non-zero exit status: 1
   t/rest2/asset-watchers.t (Wstat: 256 (exited 1) 
Tests: 78 Failed: 1)
 Failed test:  78
 Non-zero exit status: 1
   t/rest2/attachments.t(Wstat: 256 (exited 1) 
Tests: 100 Failed: 1)
 Failed test:  100
 Non-zero exit status: 1
   t/rest2/assets.t (Wstat: 256 (exited 1) 
Tests: 129 Failed: 1)
 Failed test:  129
 Non-zero exit status: 1
   t/rest2/catalogs.t   (Wstat: 256 (exited 1) 
Tests: 102 Failed: 1)
 Failed test:  102
 Non-zero exit status: 1
   t/rest2/cf-image.t   (Wstat: 256 (exited 1) 
Tests: 8 Failed: 1)
 Failed test:  8
 Non-zero exit status: 1
   t/rest2/classes.t(Wstat: 256 (exited 1) 
Tests: 94 Failed: 1)
 Failed test:  94
 Non-zero exit status: 1
   t/rest2/customfields.t   (Wstat: 256 (exited 1) 
Tests: 182 Failed: 1)
 Failed test:  182
 Non-zero exit status: 1
   t/rest2/conflict.t   (Wstat: 256 (exited 1) 
Tests: 73 Failed: 1)
 Failed test:  73
 Non-zero exit status: 1
   t/rest2/customfieldvalues.t  (Wstat: 256 (exited 1) 
Tests: 68 Failed: 1)
 Failed test:  68
 Non-zero exit status: 1
   t/rest2/groups.t (Wstat: 256 (exited 1) 
Tests: 9 Failed: 1)
 Failed test:  9
 Non-zero exit status: 1
   t/rest2/local-custom-fields.t(Wstat: 256 (exited 1) 
Tests: 19 Failed: 1)
 Failed test:  19
 Non-zero exit status: 1
   t/rest2/group-members.t  (Wstat: 256 (exited 1) 
Tests: 72 Failed: 1)
 Failed test:  72
 Non-zero exit status: 1
   t/rest2/organization.t   (Wstat: 256 (exited 1) 
Tests: 30 Failed: 1)
 Failed test:  30
 Non-zero exit status: 1
   t/rest2/not_found.t  (Wstat: 256 (exited 1) 
Tests: 49 Failed: 1)
 Failed test:  49
 Non-zero exit status: 1
   t/rest2/pagination.t (Wstat: 256 (exited 1) 
Tests: 84 Failed: 1)
 Failed test:  84
 Non-zero exit status: 1
   t/rest2/queues.t (Wstat: 256 (exited 1) 
Tests: 148 Failed: 1)
 Failed test:  148
 Non-zero exit status: 1
   t/rest2/search-simple.t  (Wstat: 256 (exited 1) 
Tests: 22 Failed: 1)
 Failed test:  22
 Non-z

Bug#916202: ITP: golang-github-mmarkdown-mmark -- Mmark: a powerful markdown processor in Go geared towards the IETF

[Scott Kitterman]

On Sun, 10 Nov 2019 23:22:21 -0700 Anthony Fok  wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Anthony Fok 
> X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org
> 
> * Package name: golang-github-mmarkdown-mmark
>   Version : 2.2.0-1
>   Upstream Author : Miek Gieben
> * URL : https://github.com/mmarkdown/mmark
> * License : BSD-2-Clause
>   Programming Lang: Go
>   Description : Mmark: a powerful markdown processor in Go geared 
towards the IETF
> 
> Rationale: There has been interests to see Mmark v2.0.0 packaged.

It would be really great to see this in Debian.  The defaults have changed 
between the older version last in Debian and the current package, so I'm 
running into problems using the old Debian version with Makefiles people are 
writing based on the current defaults.

Thanks for considering,

Scott K

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

Bug#1016369: IO::Handle ->error does not work, always saying "fine"

[Niko Tyni]

On Sat, Aug 06, 2022 at 08:44:18PM +0100, Ian Jackson wrote:

> > The second issue (writing to /dev/full) is indeed fixed in sid / Perl
> > 5.34.  It was https://github.com/Perl/perl5/issues/6799 and reportedly
> > only affects things like character devices (including /dev/full) and
> > sockets. I've verified that trying to write to a normal file on a full
> > filesystem does set the error() flag on stable / Perl 5.32.
> 
> I wonder what is different about plain files.  I suspect the fact that
> it "works" (correctly returning errors) for you in this case may be
> due to luck (the precise series of calls).

You might want to read the bug then, particularly Tony Cook's comment at

  https://github.com/Perl/perl5/issues/6799#issuecomment-626511037

Quoting:

Perl's I/O objects (that is the IO SV , not PerlIO) can have both an
input (PerlIO) file handle and an output file handle. For files that
output handle is the same as the input handle [...] For a character
device (like /dev/full) or a socket, perl creates a second PerlIO
object on the same fd to use as the output handle, and that causes
the behaviour this ticket documents.

So I don't think luck has anything to do with it.

> > Downgrading the severity, but let me know what you think based on the above.
> 
> I still think this is a data loss bug.  (Two bugs.)

I think it's at most one but whatever.

I've just reported https://github.com/Perl/perl5/issues/20060 about the
read errors. You might want to do your convincing there if needed :)
Obviously it's not going to be fixed on Debian side without upstream
involvement, whatever the severity.

> > while ( ! eof($fh) ) {
> > defined( $_ = readline $fh ) or die "readline failed: $!";
> > ...
> > }
> 
> I don't find this particularly convincing.  This argument seems to be
> saying "never use <> to read lines" which is pretty strange.  Surely
> it should be possible to use "<>" in its line-reading mode, without
> data loss.

Yeah, I agree.
-- 
Niko

Bug#1016805: retext crashes at start

[VA]

Package: retext
Version: 8.0.0-1
Severity: grave
Justification: renders package unusable

When starting retext:

qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be 
initialized. Reinstalling the application may fix this problem.


zsh: IOT instruction  retext

It seems qt6-qpa-plugins is only a "Recommends" dependency but retext 
does not work **at all** without it, so it should be a plain "Depends".

Bug#1016799: libreoffice-calc: Failed to copy multiple cells in seperate rows and columns

[Rene Engelhard]

found 1016799 1:5.0.0~rc5-1

tag 1016799 + upstream

forwarded 1016799 https://bugs.documentfoundation.org/show_bug.cgi?id=141907

severity 1016799 wishlist

retitle 1016799 please allow copy ofmultiple cells in seperate rows and 
columns


thanks


Hi,

Am 07.08.22 um 19:08 schrieb Vangelis Skarmoutsos:

Severity: normal
I disagree. This is a wish for a feature. I think the upstream bug (see 
below) is correct that it's an enhancement. I'd consider it as wishlist...

I was trying to select some cells from one sheet and copy them to another sheet

While using automatic filter at my first sheet, I selected D5, K5 and also D7,
K7 cells. Then I clicked the copy button (or pressed CTRL+C).

A dialog box appeared saying: This function can not be applied with multiple
selections (translation from the respective Greek message)
Sounds like 
https://bugs.documentfoundation.org/show_bug.cgi?id=141907[1]. Someting 
for upstream to fix.



Regards,


Rene

Bug#1016804: ksh93u+m_1.0.1-1_all-buildd.changes REJECTED

[Aurelien Jarno]

Source: ksh93u+m
Version: 1.0.1-1
Severity: serious

On 2022-08-07 16:04, Debian FTP Masters wrote:
> Version check failed:
> Your upload included the binary package ksh, version 20211217, for all,
> however unstable already has version 20211217.
> Uploads to unstable must have a higher version than present in unstable.
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 

Bug#1016803: Generates unusable resolv.conf

[Mark Brown]

Package: network-manager
Version: 1.30.6-1+deb11u1
Severity: important

On one of my systems whenever network-manager connects to a WiFi
network it generates an unusable resov.conf:

# Generated by NetworkManager
search example.org

Other devices on the same network manage to acquire a sensible
nameserver from DHCP, and this has manifested on every network
I've tried with recently.  The networks are set to use automatic
network configuration and DNS for both IPv4 and IPv6, and
resolv.conf does get updated automatically.  Setting an explicit
DNS server does generate a useful network configuration.

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

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

Versions of packages network-manager depends on:
ii  adduser  3.118
ii  dbus 1.12.20-2
ii  libaudit11:3.0-2
ii  libbluetooth35.55-3.1
ii  libc62.31-13+deb11u3
ii  libcurl3-gnutls  7.74.0-1.3+deb11u1
ii  libglib2.0-0 2.66.8-1
ii  libgnutls30  3.7.1-5+deb11u1
ii  libjansson4  2.13.1-1.1
ii  libmm-glib0  1.14.12-0.2
ii  libndp0  1.6-1+b1
ii  libnewt0.52  0.52.21-4+b3
ii  libnm0   1.30.6-1+deb11u1
ii  libpsl5  0.21.0-1.2
ii  libreadline8 8.1-1
ii  libselinux1  3.1-3
ii  libsystemd0  247.3-7
ii  libteamdctl0 1.31-1
ii  libudev1 247.3-7
ii  libuuid1 2.36.1-8+deb11u1
ii  policykit-1  0.105-31+deb11u1
ii  udev 247.3-7
ii  wpasupplicant2:2.9.0-21

Versions of packages network-manager recommends:
ii  dnsmasq-base [dnsmasq-base]  2.85-1
ii  iptables 1.8.7-1
ii  libpam-systemd   247.3-7
ii  modemmanager 1.14.12-0.2
ii  ppp  2.4.9-1+1
ii  wireless-regdb   2022.04.08-2~deb11u1

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2.3
pn  libteam-utils

-- no debconf information

Bug#1016802: reportbug: Random unnecesary space characters inside words

[Vangelis Skarmoutsos]

Package: reportbug
Version: 11.5.0
Severity: normal

Dear Maintainer,

While filing a bug report, I noticed that some of Reportbug messages are
including space characters between the letters of some words.

I was expecting the text to be more readable without extra spaces.


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

** /home/vaggelis/.reportbugrc:
reportbug_version "6.6.6"
mode standard
ui gtk2
realname "Vangelis Skarmoutsos"
email "skarmouts...@gmail.com"
smtphost "smtp.gmail.com:587"
smtpuser "skarmouts...@gmail.com"
smtppasswd 
smtptls

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

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

Versions of packages reportbug depends on:
ii  apt2.5.2
ii  python33.10.5-3
ii  python3-reportbug  11.5.0
ii  sensible-utils 0.0.17

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
ii  debconf1.5.79
pn  debsums
pn  dlocate
ii  emacs-bin-common   1:27.1+1-3.1+b1
ii  exim4  4.96-3
ii  exim4-daemon-light [mail-transport-agent]  4.96-3
ii  file   1:5.41-4
ii  gnupg  2.2.35-3
pn  python3-urwid  
ii  reportbug-gtk  11.5.0
ii  xdg-utils  1.1.3-4.1

Versions of packages python3-reportbug depends on:
ii  apt2.5.2
ii  file   1:5.41-4
ii  python33.10.5-3
ii  python3-apt2.3.0+b2
ii  python3-debian 0.1.46
ii  python3-debianbts  3.2.3
ii  python3-requests   2.27.1+dfsg-1
ii  sensible-utils 0.0.17

python3-reportbug suggests no packages.

-- no debconf information

Bug#1016801: 22.2.0~rc1-1 breaks Blender/llvm on AMD gpus

[Yuri D'Elia]

Package: libgl1-mesa-dri
Version: 22.2.0~rc1-1
Severity: important

Upgrading from 22.1.3-1 to 22.2.0~rc1-1 makes blender crash on
startup inside libllvm, I guess due to llvmpipe.

Thread 24 "blender:sh4" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff96eff640 (LWP 1240082)]
0x7fffb151aae6 in llvm::AMDGPUArgumentUsageInfo::print(llvm::raw_ostream&, 
llvm::Module const*) const () from /lib/x86_64-linux-gnu/libLLVM-14.so.1
(gdb) where
#0  0x7fffb151aae6 in 
llvm::AMDGPUArgumentUsageInfo::print(llvm::raw_ostream&, llvm::Module const*) 
const () at /lib/x86_64-linux-gnu/libLLVM-14.so.1
#1  0x7fffa1ae5318 in  ()
#2  0x7fffa19af4d0 in  ()
#3  0x7fffaf9e6e24 in llvm::AnalysisResolver::addAnalysisImplsPair(void 
const*, llvm::Pass*) () at /lib/x86_64-linux-gnu/libLLVM-14.so.1
#4  0x7fffa19af488 in  ()
#5  0x7fff96252c60 in  ()
#6  0x002f in  ()
#7  0x in  ()

While keeping libllvm14 the same, I downgraded mesa back to 22.1.3 and
the problem is gone.

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

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

Versions of packages libgl1-mesa-dri:amd64 depends on:
ii  libc62.33-8
ii  libdrm-amdgpu1   2.4.112-3
ii  libdrm-nouveau2  2.4.112-3
ii  libdrm-radeon1   2.4.112-3
ii  libdrm2  2.4.112-3
ii  libelf1  0.187-1
ii  libexpat12.4.8-1
ii  libgcc-s112.1.0-7
ii  libglapi-mesa22.1.3-1
ii  libllvm141:14.0.6-2
ii  libsensors5  1:3.6.0-7
ii  libstdc++6   12.1.0-7
ii  libvulkan1   1.3.216.0-1
ii  libxcb-dri3-01.15-1
ii  libzstd1 1.5.2+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4

libgl1-mesa-dri:amd64 recommends no packages.

libgl1-mesa-dri:amd64 suggests no packages.

Bug#1016800: libgit2: please package version 1.5.x

[Timo Röhling]

Source: libgit2
Version: 1.3.0+dfsg.1-3
Severity: wishlist

Dear maintainers,

I would like to have the latest libgit2 release and its
corresponding pygit2 bindings in bookworm. I'm happy to help with
the packaging work and the required transition.


Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Bug#1016799: libreoffice-calc: Failed to copy multiple cells in seperate rows and columns

[Vangelis Skarmoutsos]

Package: libreoffice-calc
Version: 1:7.4.0~rc2-3
Severity: normal

Dear Maintainer,

I was trying to select some cells from one sheet and copy them to another sheet

While using automatic filter at my first sheet, I selected D5, K5 and also D7,
K7 cells. Then I clicked the copy button (or pressed CTRL+C).

A dialog box appeared saying: This function can not be applied with multiple
selections (translation from the respective Greek message)

I was expecting to be able to copy the cells

Selecting only D5 and K5 does not produce the above message.
Also selecting only D7 and K7 works as expected.




-- Package-specific info:

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

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

Versions of packages libreoffice-calc depends on:
ii  coinor-libcoinmp1v5  1.8.3-3
ii  libc62.33-8
ii  libetonyek-0.1-1 0.1.10-3
ii  libgcc-s112.1.0-7
ii  libicu71 71.1-3
ii  libmwaw-0.3-30.3.21-1
ii  libodfgen-0.1-1  0.1.8-2
ii  liborcus-0.17-0  0.17.2-2+b1
ii  liborcus-parser-0.17-0   0.17.2-2+b1
ii  libreoffice-base-core1:7.4.0~rc2-3
ii  libreoffice-common   1:7.4.0~rc2-3
ii  libreoffice-core 1:7.4.0~rc2-3
ii  librevenge-0.0-0 0.0.4-6+b1
ii  libstaroffice-0.0-0  0.0.7-1
ii  libstdc++6   12.1.0-7
ii  libuno-cppu3 1:7.4.0~rc2-3
ii  libuno-cppuhelpergcc3-3  1:7.4.0~rc2-3
ii  libuno-sal3  1:7.4.0~rc2-3
ii  libuno-salhelpergcc3-3   1:7.4.0~rc2-3
ii  libwps-0.4-4 0.4.12-2
ii  libxml2  2.9.14+dfsg-1+b1
ii  lp-solve 5.5.2.5-2
ii  ucf  3.0043
ii  uno-libs-private 1:7.4.0~rc2-3

libreoffice-calc recommends no packages.

Versions of packages libreoffice-calc suggests:
ii  ocl-icd-libopencl1  2.2.14-3

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.13.1-4.4
ii  fonts-opensymbol2:102.12+LibO7.4.0~rc2-3
ii  libabsl20210324 0~20210324.2-4
ii  libboost-locale1.74.0   1.74.0-16.1
ii  libc6   2.33-8
ii  libcairo2   1.16.0-6
ii  libclucene-contribs1v5  2.3.3.4+dfsg-1.1
ii  libclucene-core1v5  2.3.3.4+dfsg-1.1
ii  libcups22.4.2-1
ii  libcurl3-gnutls 7.84.0-2
ii  libdbus-1-3 1.14.0-2
ii  libdconf1   0.40.0-3
ii  libepoxy0   1.5.10-1
ii  libexpat1   2.4.8-1
ii  libexttextcat-2.0-0 3.4.5-1
ii  libfontconfig1  2.13.1-4.4
ii  libfreetype62.12.1+dfsg-3
ii  libgcc-s1   12.1.0-7
ii  libglib2.0-02.72.3-1
ii  libgpgmepp6 1.17.1-4
ii  libgraphite2-3  1.3.14-1
ii  libgstreamer-plugins-base1.0-0  1.20.3-2
ii  libgstreamer1.0-0   1.20.3-1
ii  libharfbuzz-icu02.7.4-1+b1
ii  libharfbuzz0b   2.7.4-1+b1
ii  libhunspell-1.7-0   1.7.0-4
ii  libhyphen0  2.8.8-7
ii  libice6 2:1.0.10-1
ii  libicu7171.1-3
ii  libjpeg62-turbo 1:2.1.2-1
ii  liblcms2-2  2.13.1-1
ii  libldap-2.5-0   2.5.12+dfsg-2
ii  libmythes-1.2-0 2:1.2.4-4
ii  libnspr42:4.34-1
ii  libnss3 2:3.79-1
ii  libnumbertext-1.0-0 1.0.10-1
ii  libopenjp2-72.5.0-1
ii  liborcus-0.17-0 0.17.2-2+b1
ii  liborcus-parser-0.17-0  0.17.2-2+b1
ii  libpng16-16 1.6.37-5
ii  libpoppler118   22.02.0-3
ii  libraptor2-02.0.15-2
ii  librdf0 1.0.17-1.2
ii  libreoffice-common  1:7.4.0~rc2-3
ii  librevenge-0.0-00.0.4-6+b1
ii  libsm6  2:1.2.3-1
ii  libstdc++6  12.1.0-7
ii  libtiff54.4.0-3+b1
ii  libuno-cppu31:7.4.0~rc2-3
ii  libuno-cppuhelpergcc3-3 1:7.4.0~rc2-3
ii  libuno-sal3 1:7.4.0~rc2-3
ii  libuno-salhelpergcc3-3  1:7.4.0~rc2-3
ii  libwebp71.2.2-2+b1
ii  libx11-62:1.7.5-1
ii  libx11-xcb1 2:1.7.5-1
ii  libxext62:1.3.4-1
ii  libxinerama12:1.1.4-3
ii  libxml2 2.9.14+dfsg-1+b1
ii  libxmlsec1  1.2.34-2
ii  libxmlsec1-nss

Bug#1008082: How to --lock an account

[Jason Franklin]

On Wed, Jul 27, 2022 at 03:21:08PM +0200, Marc Haber wrote:
> > Before I start, I want to make sure we agree on what should be done.
> > 
> > I asserted that two things were sufficient:
> >   1. Put a '!' in front of the user's password in /etc/shadow
> >   2. Expire the account
> > 
> > This makes it trivial to unlock an account with all of its attributes
> > intact, including login shell.
> 
> I think that having nologin as a shell has the advantage of giving a
> clear error message IF somebody manages to log in to the expired account
> with an invalid password.

The message with /usr/sbin/nologin is indeed nice. On my system, I get
something like...

| $ su --login foo
| Password:
| This account is currently not available.

With password locking plus account expiration, I get...

| $ su --login fish
| Password: 
| su: Authentication failure

I find it odd that I get a password prompt for an account that is
expired, but so it is.

Changing the shell won't hurt, of course.

My only reason for saying it's not necessary is that someone being able
to log in to an expired account would indicate a bug somewhere else that
should be fixed (in shadow, maybe?). If account expiration cannot be
relied upon, we have a bigger security concern, I think.

> For a normal user account, I am undecided whether:
> 
> - leave login shell intact, leaving a possible security hole

Again, this is where I am not so sure.

If there is a security hole, it would be someone else's, right?

Account expiration is either reliable or it is not.

> - set login shell back to the default when the account gets reenabled
> - save login shell somewhere to reinstate if on reenabling.
> 
> I'd say, do it as you see fit, changing that at a later time would be a
> rather isolated change so I'm fine with going ahead either way here,
> while still having a personal preference for the third possibility, but
> I am not the one who decides that.

This is fair.

As soon as I'm done with the other bug I'm working on, I'll move to this
one and proceed with the stateless implementation.

Saving and restoring a user's shell can be added later if needed.

Sound good?

-- 
Jason Franklin

Bug#1016798: ifupdown: ship Ubuntu's integration scripts for systemd-resolved

[Luca Boccassi]

Package: ifupdown
Severity: wishlist
X-Debbugs-CC: pkg-systemd-maintain...@lists.alioth.debian.org

Dear Maintainer(s),

We have uploaded a new systemd-resolved package, currently in
experimental, that configures itself to be the default resolver.
This works out of the box with NetworkManager and systemd-networkd,
but requires integration scripts for ifupdown.

Ubuntu has been shipping said integration scripts in their version of
the package, see debian/if-up.d/resolved and debian/if-down.d/resolved
in :

https://patches.ubuntu.com/i/ifupdown/ifupdown_0.8.36+nmu1ubuntu4.patch

Would you please consider adopting those two scripts?

Thank you!

Kind regards,
Luca Boccassi

Bug#1016796: RFS: cdist/7.0.0-1 [QA] -- Usable Configuration Management System

[Leandro Cunha]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: cdist
   Version : 7.0.0-1
   Upstream Author : Nico Schottelius 
 * URL : https://cdi.st
 * License : GPL-3+, GPL-3
 * Vcs : https://salsa.debian.org/debian/cdist
   Section : admin

The source builds the following binary packages:

  cdist - Usable Configuration Management System
  cdist-doc - Usable Configuration Management System (html documentation)

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

  https://mentors.debian.net/package/cdist/

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

  dget -x https://mentors.debian.net/debian/pool/main/c/cdist/cdist_7.0.0-1.dsc

Changes since the last upload:

 cdist (7.0.0-1) unstable; urgency=medium
 .
   * QA upload.
   * New upstream version.
   * debian/control:
 - Bump Standards-Version to 4.6.1, no changes needed.
   * debian/patches:
 - Refresh.
 - Drop debian/patches/collections-abc.patch applied by upstream.
   * Add debian/upstream/metadata.
   * debian/copyright: Add myself.

[0] 
https://salsa.debian.org/leandrocunha/cdist/-/commit/962d1b247765ea2a7a40d0deb4f4e5d626bd1308

Regards,
-- 
  Leandro Cunha
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN
pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh
0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR
gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd
A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas
sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb
RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7
ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD
w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S
eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm
hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB
tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT
AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL
AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3
k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L
F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni
julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD
Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C
s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y
sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV
dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx
/m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z
doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j
Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C
+DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy
q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo
D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4
hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08
iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY
xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn
sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X
7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00
4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug
q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX
xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz
bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g
Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa
hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw
gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud
lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9
WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO
jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd
CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF
fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e
Wue4h/+mJiuEzuZcmzOcwq3HGMUXO0jZDgLEmlnenO9czhrLuGZaMXGdwnIk0G3O
+SqH36v7blnDh96RXpgaa+ifTHd0qKeoVXVwSq/9jNtHSQrI+NJcTpMhu73xtxhX
UFPr/31+IFLWepC5GDwdu/gQm5E6ntGyxE2p2v76pcjz7SGdXjPFZjqekBveEJuW
fNdY6Ns=
=rdCA
-END PGP PUBLIC KEY BLOCK-

Bug#1016795: RM: perl6-readline -- ROM; obsolete, replaced by raku-readline

[Dominique Dumont]

Package: ftp.debian.org
Severity: normal

Hello

Following Perl6 rename to Raku, all raku modules are renamed with the
pattern raku-.

raku-readline is now in unstable, so it's time to remove perl6-readline.

All the best

Bug#1003255: No

[Peter Müller]

tags 1003255 - wontfix
severity 1003255 normal
thanks


It's not the presence or absence of any such check that makes it into a 
bug.  It's the resulting behavior that has a bug.


E.g., you could implement this by checking at the beginning of the 
document whether the information in the aux file says the opacity code 
should be emitted.  If so, emit the code and set a Boolean macro, say, 
“\transparencyCodeWritten” to “true”, otherwise to “false”.  Then, 
whenever a transparency/opacity-related operation is encountered, test 
whether “\transparencyCodeWritten” is still “false” and if so, emit the 
transparency/opacity-related code to the output if possible immediately 
(I don't now Postscript enough to say this) and set 
“\transparencyCodeWritten” to “true”.  If not possible immediately, 
write a flag info the aux file to be read at the next LaTeX run.


There might be other ways to repair this.

If a user such as you or me or (or even user187802, even if they are the 
current maintainer) refuses to implement this, it's his or her right 
(since it's all done in free, unpaid time, and only very few people 
worldwide have it), but this doesn't make the current behavior less 
erroneous.  Maintainers and users come and go, and PStricks stays.


P.

Bug#1016794: mcomix: outdated package information

[michel]

Package: mcomix
Version: 1.2.1mcomix3+git20200206-1
Severity: minor
X-Debbugs-Cc: okgomdjgbm...@gmail.com

Dear Maintainer,



missing
Suggests: unzip, lhasa
according to wikipedia lha was popular in Japan. A bit like mp3. Other wise the 
user can't guess that it can use these.

can be removed:
Provides: comix ,Conflicts: comix
That was 13 years ago...

Maybe remove:
 MComix is a fork of the Comix project, and aims to add bug fixes
 and stability improvements after Comix development came to a halt in late
 2009.
 
Not accurate. It was a temporary mod. The dev never intended to start a fork:
 MComix3 is a fork of the MComix project (of gtk3 branch), which port MComix
 to python3.

Bug#1016793: RFS: dh-nss/1.1 -- debhelper addon to inject NSS services into /etc/nsswitch.conf

[Gioele Barabucci]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "dh-nss":

 * Package name: dh-nss
   Version : 1.1
   Upstream Author : Gioele Barabucci
 * URL : https://salsa.debian.org/gioele/dh-nss
 * License : 0BSD, GPL-2+
 * Vcs : https://salsa.debian.org/gioele/dh-nss
   Section : devel

The source builds the following binary packages:

  dh-nss - debhelper addon to inject NSS services into /etc/nsswitch.conf

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


  https://mentors.debian.net/package/dh-nss/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/d/dh-nss/dh-nss_1.1.dsc


Changes since the last upload:

 dh-nss (1.1) unstable; urgency=medium
 .
   * dh_installnss: Properly handle comments in db lines
   * autoscripts/postrm-nss: Remove services during `remove` or `purge`
   * d/control: Add Enhances: debhelper
   * d/control: Add Perl dependencies
   * d/control: Mark package as Multi-Arch: foreign
   * d/copyright: Change license to 0BSD
   * d/copyright: Mark vendored t/Test/* as GPL-2+
   * d/gitlab-ci: Add standard CI instructions
   * d/install: wrap-and-sort -ast
   * d/tests: Add autopkgtest tests
   * d/watch: Remove watch for native package

Regards,

--
  Gioele Barabucci

Bug#1006794: mcomix: conflicts with configuration

[michel]

Package: mcomix
Followup-For: Bug #1006794
X-Debbugs-Cc: okgomdjgbm...@gmail.com

Dear Maintainer,




Actually, there's a problem The configuration files aren't 100% compatible 
whille there's little to gain. So it shouldn't be backported to stable.

Bug#1016792: ITP: libcircle-fe-term-perl -- terminal frontend for the Circle application host

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libcircle-fe-term-perl
  Version : 0.222060
  Upstream Author : Paul Evans 
* URL : https://metacpan.org/release/circle-fe-term
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : terminal frontend for the Circle application host

The circle-fe-term script and the Circle::FE::Term module provide a terminal
frontend to the Circle application host, packaged as circle-backend.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Bug#942288: Wish for tar2squashfs

[Trent W. Buck]

FYI,

squashfs-tools-ng/bullseye has tar2sqfs and I've been using it for ages.
This unprivileged command already uses it internally:

$ mmdebstrap bullseye bullseye.squashfs

Bug#1016791: kivy: New upstream release available

[Michael Fladischer]

Source: kivy
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

upstream has release 2.1.0 and it would be nice to have this rleease in Debian
as it officially supports Python 3.10.

Best regards,
Michael

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

Kernel: Linux 5.15.35-rockchip64 (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_DK.UTF-8), LANGUAGE=en_DK.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmLvydQRHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90WqjuQf/aihWPUVaUTyUVQoTiL362avvWLF4rh40
ZUdGjlgkO+1ynwePIDQcFQOrlvq+0YBvVFeCDMqpo3HkB4Wk8vlY1INRVfB3dsb7
plA/2tj3jDSjYEItSaOe3sx0aC9fz4FqMpJ4vwZXTXJRaoy1ryEtkOvpgDfmx8Qd
PkpE6iMX3hrGGpItOwIb/xOH9NS7TEq873jMKtPcydtVFX22tZiGhUSyyrOdUo1G
b0JPGS/9MHzf0+cGR28pv0v0QYlc1CVI5Va4J/k0LsuI9l2zy/uKU8AI8+/UM7sQ
wvbTdb1sr2Hnq+hfVmaM1pVXIiAaKB28C6ZgZPDRZjcXTSsU14Ayzw==
=+f82
-END PGP SIGNATURE-

Bug#1016790: lldb is not upgraded during dist-upgrade

[Jeffrey Walton]

Package: lldb
Version: 1:14.0-55.1
Tags: unstable

Hi Everyone. I' working on a GCC 12 specific bug present in Debian
Unstable. I am also using LLVM's tools to investigate the bug.

Running dist-upgrade results in lldb being held back:

# apt-get update
...
# apt-get upgrade
...
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  lldb
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

I think there may be something wrong with the lldb package at the moment.

-

# apt-cache show lldb
Package: lldb
Source: llvm-defaults (0.55.1)
Version: 1:14.0-55.1
Installed-Size: 23
Maintainer: LLVM Packaging Team 
Architecture: amd64
Depends: lldb-14 (>= 14~)
Description-en: Next generation, high-performance debugger
...
This is a dependency package providing the default version of lldb.
Description-md5: ead6eb91f74bd6143cb488df627284c1
Multi-Arch: same
Section: devel
Priority: optional
Filename: pool/main/l/llvm-defaults/lldb_14.0-55.1_amd64.deb
Size: 9344
MD5sum: 7f5a61adfe6837cd29001fae18f98b9a
SHA256: f97706b38c0d7293b9b9529584101854b035bf6fe013083a51411a2c0d34bdba

Package: lldb
Status: install ok installed
Priority: optional
Section: devel
Installed-Size: 22
Maintainer: LLVM Packaging Team 
Architecture: amd64
Source: llvm-defaults (0.51+nmu5)
Version: 1:11.0-51+nmu5
Depends: lldb-11 (>= 11~)
Description-en: Next generation, high-performance debugger
...
This is a dependency package providing the default version of lldb.
Description-md5: ead6eb91f74bd6143cb488df627284c1

Bug#1016789: ITP: libtickit-widget-entry-plugin-completion-perl -- word-completion plugin for Tickit::Widget::Entry

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libtickit-widget-entry-plugin-completion-perl
  Version : 0.01
  Upstream Author : Paul Evans 
* URL : 
https://metacpan.org/release/Tickit-Widget-Entry-Plugin-Completion
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : word-completion plugin for Tickit::Widget::Entry

Tickit::Widget::Entry::Plugin::Completion applies code to a
Tickit::Widget::Entry instance to implement word-completion logic while
editing. This logic is activated by pressing the  key.

If the word currently being edited has a unique match in the list of words,
then the word is completed entirely, followed by a space.

If there are multiple words that could complete from the word at the cursor,
then a popup menu is presented showing the next available characters or
matches. The user can continue typing more characters to narrow down the
choice until a unique match is found.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Bug#1016788: ITP: libtickit-app-plugin-escapeprefix-perl -- Tickit application plugin for Escape-prefixed shortcut keys

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libtickit-app-plugin-escapeprefix-perl
  Version : 0.02
  Upstream Author : Paul Evans 
* URL : https://metacpan.org/release/Tickit-App-Plugin-EscapePrefix
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Tickit application plugin for Escape-prefixed shortcut keys

Tickit::App::Plugin::EscapePrefix applies code to a Tickit instance to let it
handle -prefixed shortcut keys, by converting them into the
equivalent  modified keys instead.

Once applied using the /apply method, the plugin will consume any plain
 keys typed at the terminal. If another key arrives soon afterwards,
this key will be consumed and instead a new keypress event emitted that adds
the "meta" modifier to it. For example, typing   will instead emit
the modified key  to the application. If no subsequent key arrives after
a timeout of 3 seconds then the modification will not apply.

While the plugin is still pending anothey keypress to modify, a small
indicator window will appear in the bottom left of the display, showing ESC-
in a reverse-video style, to remind the user the keypress is pending.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Bug#1016139: (net-snmp: CVE-2022-24810 CVE-2022-24809 CVE-2022-24808 CVE-2022-24807 CVE-2022-24806 CVE-2022-24805)

[Salvatore Bonaccorso]

Hi Craig,

On Fri, Jul 29, 2022 at 04:36:56PM +0200, Moritz Mühlenhoff wrote:
> Am Thu, Jul 28, 2022 at 09:25:44PM +1000 schrieb Craig Small:
> > I said:
> > 
> > > I had uploaded net-snmp 5.9.3 anyway but I'll add those CVEs to the
> > > changelog.
> > > I'm trying to find where they've made the changes to see if it is possible
> > > to get at least bullseye fixed.
> > >
> > I've had a look and believe these two commits are the fixes:
> > 
> > snmpd: fix bounds checking in NET-SNMP-AGENT-MIB, NET-SNMP-VACM-MIB,
> > SNMP-VIEW-BASED-ACM-MIB, SNMP-USER-BASED-SM-MIB
> > https://github.com/net-snmp/net-snmp/commit/67ebb43e9038b2dae6e74ae8838b36fcc10fc937
> > 
> > snmpd: recover SET status from delegated request
> > https://github.com/net-snmp/net-snmp/commit/9a0cd7c00947d5e1c6ceb54558d454f87c3b8341
> > 
> > Both sets of commits look pretty clear and simple to implement. I've asked
> > upstream to confirm these are the only two patches.

Did you got confirmation from upstream back if those are the only two
needed ones?

Do you have capacity to prepare updates for bullseye?

Regards,
Salvatore

Bug#1016786: bullseye-pu: package systemd/247.3-7+deb11u1

[Michael Biebl]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org

Hi,

I'd like to make a stable upload for systemd fixing two issues in
systemd-detect-virt

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013342
 systemd - Please backport support for Hyper-V on arm64 to stable

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016157
 systemd-detect-virt fails to detect Openstack on arm64

All changes are cherry-picks from upstream Git and are already in
unstable/testing.


While at it, I also pulled a patch to fix build failures when systemd is
built against newer kernel headers (>= 5.14).

debdiff is attached.

Regards,
Michael
diff --git a/debian/changelog b/debian/changelog
index ddb3701..b1b7f43 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+systemd (247.3-7+deb11u1) bullseye; urgency=medium
+
+  * Drop bundled copy of linux/if_arp.h.
+Fixes build failures with newer kernel headers.
+  * virt: support detection for ARM64 Hyper-V guests (Closes: #1013342)
+  * virt: detect OpenStack instance as KVM on arm (Closes: #1016157)
+
+ -- Michael Biebl   Sun, 07 Aug 2022 15:25:09 +0200
+
 systemd (247.3-7) bullseye; urgency=medium
 
   * Switch debian-branch to debian/bullseye
diff --git a/debian/patches/Drop-bundled-copy-of-linux-if_arp.h.patch 
b/debian/patches/Drop-bundled-copy-of-linux-if_arp.h.patch
new file mode 100644
index 000..83a6f2c
--- /dev/null
+++ b/debian/patches/Drop-bundled-copy-of-linux-if_arp.h.patch
@@ -0,0 +1,219 @@
+From: =?utf-8?q?Zbigniew_J=C4=99drzejewski-Szmek?= 
+Date: Wed, 15 Sep 2021 16:33:05 +0200
+Subject: Drop bundled copy of linux/if_arp.h
+MIME-Version: 1.0
+Content-Type: text/plain; charset="utf-8"
+Content-Transfer-Encoding: 8bit
+
+As far as I can see, we use this to get a list of ARPHRD_* defines (used in
+particular for Type= in .link files). If we drop our copy, and build against
+old kernel headers, the user will have a shorter list of types available.  This
+seems OK, and I don't think it's worth carrying our own version of this file
+just to have newest possible entries.
+
+7c5b9952c4f6e2b72f90edbe439982528b7cf223 recently updated this file, but we'd
+have to update it every time the kernel adds new entries. But if we look at
+the failure carefully:
+
+src/basic/arphrd-from-name.gperf:65:16: error: ‘ARPHRD_MCTP’ undeclared (first 
use in this function); did you mean ‘ARPHRD_FCPP’?
+   65 | MCTP, ARPHRD_MCTP
+  |^~
+  |ARPHRD_FCPP
+
+we see that the list we were generating was from the system headers, so it was
+only as good as the system headers anyway, without the newer entries in our
+bundled copy, if there were any. So let's make things simpler by always using
+system headers.
+
+And if somebody wants to fix things so that we always have the newest list,
+then we should just generate and store the converted list, not the full header.
+
+(cherry picked from commit e7f46ee3ae1cc66a94b293957721d68dc09d7449)
+---
+ src/basic/linux/if_arp.h | 164 ---
+ src/basic/meson.build|   1 -
+ 2 files changed, 165 deletions(-)
+ delete mode 100644 src/basic/linux/if_arp.h
+
+diff --git a/src/basic/linux/if_arp.h b/src/basic/linux/if_arp.h
+deleted file mode 100644
+index c3cc5a9..000
+--- a/src/basic/linux/if_arp.h
 /dev/null
+@@ -1,164 +0,0 @@
+-/* SPDX-License-Identifier: GPL-2.0+ WITH Linux-syscall-note */
+-/*
+- * INET   An implementation of the TCP/IP protocol suite for the 
LINUX
+- *operating system.  INET is implemented using the  BSD Socket
+- *interface as the means of communication with the user level.
+- *
+- *Global definitions for the ARP (RFC 826) protocol.
+- *
+- * Version:   @(#)if_arp.h1.0.1   04/16/93
+- *
+- * Authors:   Original taken from Berkeley UNIX 4.3, (c) UCB 1986-1988
+- *Portions taken from the KA9Q/NOS (v2.00m PA0GRI) source.
+- *Ross Biro
+- *Fred N. van Kempen, 
+- *Florian La Roche,
+- *Jonathan Layes 
+- *Arnaldo Carvalho de Melo  ARPHRD_HWX25
+- *
+- *This program is free software; you can redistribute it and/or
+- *modify it under the terms of the GNU General Public License
+- *as published by the Free Software Foundation; either version
+- *2 of the License, or (at your option) any later version.
+- */
+-#ifndef _UAPI_LINUX_IF_ARP_H
+-#define _UAPI_LINUX_IF_ARP_H
+-
+-#include 
+-
+-/* ARP protocol HARDWARE identifiers. */
+-#define ARPHRD_NETROM 0   /* from KA9Q: NET/ROM pseudo*/
+-#define ARPHRD_ETHER  1   /* Ethernet 10Mbps  */
+-#define   ARPHRD_EETHER   2   /* Experimental Ethernet
*/
+-#define   ARPHRD_AX25 3   /* AX.25 Level 2  

Bug#1016334: dvdisaster: FTBFS: make[2]: *** [GNUmakefile:209: manual] Error 2

[dvdisaster support]

> Source: dvdisaster
> Version: 0.79.5-10
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220728 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> [..]
> > ! Argument of ? has an extra }.
> >  
> > \par 
> > l.49 }

Please comment out lines 3 and 4 in manual.tex and codecs.tex, e.g.

%\usepackage{ucs}
%\usepackage[utf8x]{inputenc}

The ucs and utf8x packages break hyperref and are no longer needed
since LaTeX is now UTF-8 aware by default.

The upstream will update soon.

Greetings,
  cg

-- 
dvdisaster support
upstream site : https://dvdisaster.jcea.es/
src repository: https://hg.jcea.es/dvdisaster
release key FP: E3AF E703 96CC C0D9 E5D8  381C B0DB CA7D 64F7 70B2

Bug#1002993: systemd: Setting access ACL: invalid argument (Upgrade to 247.3-6 from buster to bullseye in container)

[Michael Biebl]

On Sun, 2 Jan 2022 16:12:16 +0100 Tobias Frost  wrote:

On Sun, Jan 02, 2022 at 03:24:57PM +0100, Michael Biebl wrote:
> 
> Control: tags -1 + moreinfo unreproducible
> 
> On 02.01.22 14:52, Tobias Frost wrote:
> 
> > Please let me know if there are additional details I could supply.
> > 
> 
> 
> Can you provide steps how to reproduce the issue?


> More details how the container is constructed, which fs is used etc. might
> help as well.

When I find a way to reproduce, I'll let you know.




Any news here?


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016475: tmux sessions do not persist through logout

[Richard Lewis]

On Mon, 1 Aug 2022 20:34:27 +0200 Romain Francoise
 wrote:

> There’s nothing tmux can do right now about systemd killing user
> sessions without lingering enabled; just run `sudo loginctl
> enable-linger $USER`.

I start tmux with

$ systemd-run --scope --user tmux -2 # etc

and it seems to work for me - advantage being no 'sudo' needed

Perhaps 'tmux'  should be a script that invokes the real tmux binary
with systemd-run (if running under systemd) and solve this problem for
everyone.

Bug#1016785: Can't change user password on a "System Settings" (polkit dialog doesn't appear)

[xalt7x]

Package: systemsettings
Version: 4:5.25.4-1
Severity: normal

I'm unable to change password on "System Settings > Users" because dialog which 
asks elevated rights (sudo/root password) doesn't appear

How to reproduce:
1) Go to System Settings > Users
2) Click "Change password" and enter new password

What should happen:
1) After click on button "Set Password" user is asked for administrator password
2) User is notified that it's better to change Kwaller password as well

What currently happens:
1) Dialog closes
2) No warning about KWallet
3) Password doesn't change

If I launch systemsettings with elevated rights
Like
pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY KDE_SESSION_VERSION=5 
KDE_FULL_SESSION=true systemsettings5 kcm_users
or
sudo systemsettings5 kcm_users
Password changes but KWallet warning doesn't appear

I tested other Debian-based distros:
- Kubuntu 22.04 - broken
- Kubuntu 22.10/kinetic daily build (2022-08-06) - broken
- Debian Testing (weekly build from 2022-08-01) - broken
- KDE Neon (build from 2022-08-04, based on Ubuntu 20.04) - dialog appears
- Debian 11.4 - dialog appears. Debian 11 with latest KDE packages (Norbert 
Preining backports) - still works


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

Kernel: Linux 5.18.0-3-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 systemsettings depends on:
ii  kio 5.96.0-3
ii  kpackagetool5   5.96.0-1
ii  libc6   2.33-8
ii  libkf5activities5   5.96.0-2
ii  libkf5activitiesstats1  5.96.0-1
ii  libkf5auth5 5.96.0-1
ii  libkf5authcore5 5.96.0-1
ii  libkf5completion5   5.96.0-1
ii  libkf5configcore5   5.96.0-1
ii  libkf5configgui55.96.0-1
ii  libkf5configwidgets55.96.0-1
ii  libkf5coreaddons5   5.96.0-1
ii  libkf5crash55.96.0-1
ii  libkf5dbusaddons5   5.96.0-1
ii  libkf5i18n5 5.96.0-1
ii  libkf5iconthemes5   5.96.0-1
ii  libkf5itemmodels5   5.96.0-1
ii  libkf5itemviews55.96.0-1
ii  libkf5kcmutils5 5.96.0-1
ii  libkf5kiogui5   5.96.0-3
ii  libkf5kiowidgets5   5.96.0-3
ii  libkf5notifications55.96.0-1
ii  libkf5package5  5.96.0-1
ii  libkf5runner5   5.96.0-1
ii  libkf5service-bin   5.96.0-1
ii  libkf5service5  5.96.0-1
ii  libkf5widgetsaddons55.96.0-1
ii  libkf5windowsystem5 5.96.0-1
ii  libkf5xmlgui5   5.96.0-1
ii  libkworkspace5-54:5.25.4-1
ii  libqt5core5a5.15.4+dfsg-4
ii  libqt5gui5  5.15.4+dfsg-4
ii  libqt5qml5  5.15.4+dfsg-4
ii  libqt5quick55.15.4+dfsg-4
ii  libqt5quickwidgets5 5.15.4+dfsg-4
ii  libqt5widgets5  5.15.4+dfsg-4
ii  libstdc++6  12.1.0-7
ii  qml-module-org-kde-kcm  5.96.0-3
ii  qml-module-org-kde-kcmutils 5.96.0-1
ii  qml-module-org-kde-kirigami25.96.0-2
ii  qml-module-org-kde-kitemmodels  5.96.0-1
ii  qml-module-org-kde-newstuff 5.96.0-1
ii  qml-module-qtquick-controls 5.15.4-2
ii  qml-module-qtquick-layouts  5.15.4+dfsg-4
ii  qml-module-qtquick-shapes   5.15.4+dfsg-4
ii  qml-module-qtquick2 5.15.4+dfsg-4

systemsettings recommends no packages.

systemsettings suggests no packages.

-- no debconf information

Bug#987941: buster-pu: package pacemaker/2.0.1-5+deb10u2

[Ferenc Wágner]

"Adam D. Barratt"  writes:

> I'm not hugely happy that this has ended up not being in stretch, to
> be quite honest.

Agreed.  I was pushing for it in vain, unfortunately.

> We're in the process of organising the final point release for buster,
> as support for it moves over to the LTS team, so please go ahead.

Uploaded.

> +A new upstream release instroduced as security update 1.1.24-
> 0+deb9u1 in
>
> s/instroduced/introduced/

With this fix included.
-- 
Thanks,
Feri

Bug#1016783: emacs-pdf-tools: switch to new fork?

[David Bremner]

Source: emacs-pdf-tools
Version: 1.0~20200512-2
Severity: wishlist
X-Debbugs-Cc: debian-emac...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

According to the current upstream,

  PDF Tools is dead, long live PDF Tools. Development
  continues with this fork:
  https://github.com/vedang/pdf-tools .

There is a tag 0.91 on that repo that seems newer than what we have.

unfortunately someone (me?) chose 1.0~date as version scheme for the
existing package, so that's a mess that would need to be cleaned up.

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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmLvr8gACgkQA0U5G1Wq
FSHwOw/5AWK5/niZ3FT2pY9VIwtnoInToD9FD63ZWL+uJuyeDRQoxxvdrndyTWIc
m//XcT8dIDzZD9ZqJlezdPZoDmacqvb6By4o2BlmveuI60hXphPy5YOlXbze4DKf
RrKF6Eu5SpBxDZh1pb4aB5voO+phMIyD/7zFZo1TrOeg2sJRN9HC3t5Hsdysoa2D
7qiZBGn70njTQ8gCTRTX81MhMSRDgfnfTbN8F08F+kg74tO+prcxUFJnwOMDwLVA
PuJCvZdgtPAafUmFCx9PNtd2aVAspht+Yptv6/pGdS9n1Po2rL8l3zfuOwR4LdCw
fMYbsfhyyrynTrOXYScXX7OfF9ExnSLMILLqehNgALDYhWZyvuhD0hxFD3RC0hIS
1FYlVJwda99gdjPuQY3L+H3elxyC8QTJTFQVr18nW8M5bel3HJ7jyeQ1HL0UjR/V
wfDk6BapKR709fToHPozwcrZZiEsI8lg9DGO7H2gE7jyEVWkUwKCXaKqoVjBr2Nw
S5qTD18XTKGIpANEPSvXLcyU31pls3QYUtmV/R23hYCeJTDKxkYyFDIghEbKl2kP
72EO0goZdj1gTbbU40ZC5fydhbBG3ZbHUdmC/bm2vbha/f6C6whfVBQvRSiepgQD
27wn1if8kKuWddKkhnhz5Cfy7OVerQjNtrewZdh6w4OK6PBYkYk=
=VnXb
-END PGP SIGNATURE-

Bug#1016782: linux-image-5.18.0-3-amd64: no output on consoles tty2-tty6 when using systemd's graphical target

[Peter Marschall]

Package: src:linux
Version: 5.18.14-1
Severity: important

Hi,

with the upgrade to 5.18.14-1 no output is shown on consoles tty2 - tty4 [in my 
case] in systemd's graphical target

Systemd creates the getty.slice and starts the getty@service for tty2 - tty4
   │ ├─system-getty.slice
   │ │ ├─getty@tty2.service
   │ │ │ └─7311 /sbin/agetty -o "-p -- \\u" --noclear - linux
   │ │ ├─getty@tty3.service
   │ │ │ └─7117 /sbin/agetty -o "-p -- \\u" --noclear - linux
   │ │ └─getty@tty4.service
   │ │   └─6680 /sbin/agetty -o "-p -- \\u" --noclear - linux

Blingdly logging wuithout visual feedback also seems to be possible:

journalctl excerpt:
Aug 07 14:05:28 moth login[7112]: pam_unix(login:session): session 
opened for user peter(uid=1000) by LOGIN(uid=0)
Aug 07 14:05:28 moth systemd-logind[919]: New session 18 of user peter.
Aug 07 14:05:28 moth systemd[1]: Started Session 18 of User peter.

systemctl status excerpts
   │ ├─system-getty.slice
   │ │ ├─getty@tty3.service
   │ │ │ └─7117 /sbin/agetty -o "-p -- \\u" --noclear - linux
   │ │ └─getty@tty4.service
   │ │   └─6680 /sbin/agetty -o "-p -- \\u" --noclear - linux

 └─user-1000.slice
   ├─session-18.scope
   │ ├─7112 /bin/login -p --
   │ └─7142 -bash

After blindly logging out of tty2, systemctl status shows again all 
getty@sessions


The issue appears on two separate installations on the same HW.
Rebooting with an earlier version of the kernel makes the issue disappear in 
both installations.
(tested with kernekl 5.18.5-1 from linux-image-5.18.0-3-amd64)




-- Package-specific info:
** Version:
Linux version 5.18.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.3.0-5) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP 
PREEMPT_DYNAMIC Debian 5.18.14-1 (2022-07-23)

** Command line:
BOOT_IMAGE=/vmlinuz-5.18.0-3-amd64 
root=UUID=edb11cba-524f-4c12-b334-be64713e04c0 ro noapic consoleblank=600 quiet 
apparmor=1 security=apparmor

** Tainted: C (1024)
 * staging driver was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: EXTRA Computer GmbH
product_name: exone Business S 1301
product_version: Default string
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: F3 EP
board_vendor: Gigabyte Technology Co., Ltd.
board_name: A520M DS3H
board_version: x.x

** Loaded modules:
ses
enclosure
scsi_transport_sas
snd_seq_dummy
snd_hrtimer
snd_seq
xt_MASQUERADE
xt_CHECKSUM
ip6t_REJECT
nf_reject_ipv6
ipt_REJECT
nf_reject_ipv4
nft_compat
nft_chain_nat
nf_nat
nf_tables
nfnetlink
bridge
stp
llc
cpufreq_powersave
cpufreq_conservative
cpufreq_userspace
cpufreq_ondemand
nvme_fabrics
cfg80211
rfkill
qrtr
binfmt_misc
pktcdvd
intel_rapl_msr
intel_rapl_common
snd_hda_codec_realtek
snd_hda_codec_generic
edac_mce_amd
ledtrig_audio
uvcvideo
snd_hda_codec_hdmi
videobuf2_vmalloc
snd_usb_audio
videobuf2_memops
videobuf2_v4l2
snd_hda_intel
videobuf2_common
snd_intel_dspcfg
kvm_amd
snd_usbmidi_lib
snd_intel_sdw_acpi
videodev
snd_rawmidi
snd_hda_codec
snd_seq_device
kvm
snd_hda_core
r8188eu(C)
mc
snd_hwdep
irqbypass
ftdi_sio
snd_pcm
xt_LOG
usbserial
libarc4
nf_log_syslog
rapl
snd_timer
ip6table_filter
ccp
ip6_tables
snd
wmi_bmof
rng_core
soundcore
pcspkr
sp5100_tco
xt_limit
watchdog
k10temp
sg
evdev
acpi_cpufreq
xt_tcpudp
xt_conntrack
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
libcrc32c
iptable_filter
nfsd
nfs_acl
lockd
auth_rpcgss
loop
grace
msr
ecryptfs
sunrpc
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
hid_generic
usbhid
hid
amdgpu
gpu_sched
crc32_pclmul
uas
i2c_algo_bit
crc32c_intel
drm_dp_helper
usb_storage
sr_mod
sd_mod
cec
cdrom
rc_core
drm_ttm_helper
ghash_clmulni_intel
ahci
xhci_pci
ttm
nvme
r8169
libahci
xhci_hcd
drm_kms_helper
aesni_intel
libata
drm
realtek
nvme_core
crypto_simd
mdio_devres
cryptd
t10_pi
usbcore
scsi_mod
libphy
crc64_rocksoft_generic
crc64_rocksoft
crc_t10dif
crct10dif_generic
i2c_piix4
crct10dif_pclmul
crc64
crct10dif_common
scsi_common
usb_common
wmi
video
gpio_amdpt
gpio_generic
button

** PCI devices:
00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne 
Root Complex [1022:1630]
Subsystem: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root 
Complex [1022:1630]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:01.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Renoir PCIe 
Dummy Host Bridge [1022:1632]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort-

Bug#1016781: xfonts-75dpi: DEC terminal fonts do not load

[Ralph Aichinger]

Package: xfonts-75dpi
Version: 1:1.0.4+nmu1.1
Severity: normal
X-Debbugs-Cc: r...@pi.h5.or.at

Dear Maintainer,

I wanted to use after a longer hiatus the very old DEC terminal X11 core fonts,
eg. 

term14.pcf.gz -dec-terminal-medium-r-normal--14-140-75-75-c-80-iso8859-1

The font files are in the right directory /usr/share/fonts/X11/75dpi,
they are listed in a fonts.dir in that directory (above two lines are
from that file), but xlsfonts does not list them, xfontsel does not show 
them (unlike the similarly old schumacher fonts), and xterm shows 

  root@pix:/usr/share/fonts/X11/75dpi# grep dec fonts.dir 
  tech14.pcf.gz -dec-terminal-medium-r-normal--14-140-75-75-c-80-dec-dectech
  techB14.pcf.gz -dec-terminal-bold-r-normal--14-140-75-75-c-80-dec-dectech
  term14.pcf.gz -dec-terminal-medium-r-normal--14-140-75-75-c-80-iso8859-1
  termB14.pcf.gz -dec-terminal-bold-r-normal--14-140-75-75-c-80-iso8859-1
  root@pix:/usr/share/fonts/X11/75dpi# xterm -fn 
-dec-terminal-medium-r-normal--14-140-75-75-c-80-iso8859-1
  xterm: cannot load font 
"-dec-terminal-medium-r-normal--14-140-75-75-c-80-iso8859-1"

Is this a bug in my setup, or a bug in the font, or in some X11 library?
If I open the font in "fontforge", everything seems normal to me (I see
a bitmap font that looks right to me).

Of course this borders on software archeology, but I do like this font,
and would love to use it.

Thanks in advance,
Ralph Aichinger

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

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

Versions of packages xfonts-75dpi depends on:
ii  xfonts-utils  1:7.7+6

xfonts-75dpi recommends no packages.

Versions of packages xfonts-75dpi suggests:
ii  xserver-xephyr [xserver]  2:21.1.4-1
ii  xserver-xorg [xserver]1:7.7+23

-- no debconf information

Bug#1016780: linux-image-5.18.0-3-amd64: repatedly disconnects & reconnects USB drive Sandisk Extreme SSD

[Peter Marschall]

Package: src:linux
Version: 5.18.14-1
Severity: important


With the upgrade to Linux 5.18.14-1, the kernel continues to disconnect & 
reconnect my USB drive Sandisk Extreme SSD within a few seconds.
This behaviour makes using the drive impossible.
When trying to use it nevertheless, it may damage the filee-system, potentially 
risking data los..

This behaviour appear on 2 separate installations running on the same hardware,
and when rebooting the instances with an earlier kernel (tested with 5.18.5-1 
from linux-image-5.18.0-2-amd64 on boith installations),
the issue disappears and the USB disk works absolutely flawlessly.


Journalctl reports the followign messages for the first connections and the 
consecutive de- & re-connections

Aug 07 13:24:04 moth kernel: usb 2-1: new SuperSpeed USB device number 2 using 
xhci_hcd
Aug 07 13:24:04 moth kernel: usb 2-1: New USB device found, idVendor=0781, 
idProduct=558c, bcdDevice=10.12
Aug 07 13:24:04 moth kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
Aug 07 13:24:04 moth kernel: usb 2-1: Product: Extreme SSD
Aug 07 13:24:04 moth kernel: usb 2-1: Manufacturer: SanDisk
Aug 07 13:24:04 moth kernel: usb 2-1: SerialNumber: 323030323744343030313238
Aug 07 13:24:04 moth kernel: scsi host7: uas
Aug 07 13:24:04 moth kernel: scsi 7:0:0:0: Direct-Access SanDisk  Extreme 
SSD  1012 PQ: 0 ANSI: 6
Aug 07 13:24:04 moth kernel: scsi 7:0:0:1: Enclosure SanDisk  SES 
Device   1012 PQ: 0 ANSI: 6
Aug 07 13:24:04 moth kernel: sd 7:0:0:0: Attached scsi generic sg4 type 0
Aug 07 13:24:04 moth kernel: scsi 7:0:0:1: Attached scsi generic sg5 type 13
Aug 07 13:24:04 moth kernel: sd 7:0:0:0: [sdd] Spinning up disk...
Aug 07 13:24:06 moth kernel: ..ready
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] 976773120 512-byte logical 
blocks: (500 GB/466 GiB)
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] 4096-byte physical blocks
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Write Protect is off
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Mode Sense: 67 00 10 08
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Write cache: disabled, read 
cache: enabled, supports DPO and FUA
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Optimal transfer size 33553920 
bytes not a multiple of physical block size (4096 bytes)
Aug 07 13:24:06 moth kernel:  sdd: sdd1
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Write cache: enabled, read 
cache: enabled, supports DPO and FUA
Aug 07 13:24:06 moth kernel: sd 7:0:0:0: [sdd] Attached SCSI disk
Aug 07 13:24:06 moth kernel: scsi 7:0:0:1: Wrong diagnostic page; asked for 1 
got 8
Aug 07 13:24:06 moth kernel: scsi 7:0:0:1: Failed to get diagnostic page 0x1
Aug 07 13:24:06 moth kernel: scsi 7:0:0:1: Failed to bind enclosure -19
Aug 07 13:24:06 moth kernel: ses 7:0:0:1: Attached Enclosure device
Aug 07 13:24:16 moth kernel: EXT4-fs (sdd1): mounted filesystem with ordered 
data mode. Quota mode: none.
Aug 07 13:24:52 moth kernel: usb 2-1: USB disconnect, device number 2
Aug 07 13:24:52 moth kernel: device offline error, dev sdd, sector 0 op 
0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0
Aug 07 13:24:52 moth kernel: Buffer I/O error on dev sdd1, logical block 
60850176, lost sync page write
Aug 07 13:24:52 moth kernel: JBD2: Error -5 detected when updating journal 
superblock for sdd1-8.
Aug 07 13:24:52 moth kernel: Aborting journal on device sdd1-8.
Aug 07 13:24:52 moth kernel: Buffer I/O error on dev sdd1, logical block 
60850176, lost sync page write
Aug 07 13:24:52 moth kernel: JBD2: Error -5 detected when updating journal 
superblock for sdd1-8.
Aug 07 13:24:52 moth kernel: EXT4-fs error (device sdd1): ext4_put_super:1226: 
comm umount: Couldn't clean up the journal
Aug 07 13:24:52 moth kernel: EXT4-fs (sdd1): Remounting filesystem read-only
Aug 07 13:24:52 moth kernel: sd 7:0:0:0: [sdd] Synchronizing SCSI cache
Aug 07 13:24:52 moth kernel: sd 7:0:0:0: [sdd] Synchronize Cache(10) failed: 
Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Aug 07 13:24:52 moth kernel: usb 2-1: new SuperSpeed USB device number 3 using 
xhci_hcd
Aug 07 13:24:52 moth kernel: usb 2-1: New USB device found, idVendor=0781, 
idProduct=558c, bcdDevice=10.12
Aug 07 13:24:52 moth kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
Aug 07 13:24:52 moth kernel: usb 2-1: Product: Extreme SSD
Aug 07 13:24:52 moth kernel: usb 2-1: Manufacturer: SanDisk
Aug 07 13:24:52 moth kernel: usb 2-1: SerialNumber: 323030323744343030313238
Aug 07 13:24:52 moth kernel: scsi host7: uas
Aug 07 13:24:52 moth kernel: scsi 7:0:0:0: Direct-Access SanDisk  Extreme 
SSD  1012 PQ: 0 ANSI: 6
Aug 07 13:24:52 moth kernel: scsi 7:0:0:1: Enclosure SanDisk  SES 
Device   1012 PQ: 0 ANSI: 6
Aug 07 13:24:52 moth kernel: sd 7:0:0:0: Attached scsi generic sg4 type 0
Aug 07 13:24:52 moth kernel: ses 7:0:0:1: Attached Enclosure device
Aug 07 13:24:52 moth kernel: ses 7:0:0:1: Attached scsi generic sg5 type 13
Aug 07 13:24:52 moth kernel: ses 7:

Bug#930850: texlive-latex-extra: Update listings macro separator

[Hilmar Preuße]

Control: notforwarded -1

Am 23.06.2019 um 21:25 teilte Xavier Gendre mit:

Le 23/06/2019 à 17:15, Hilmar Preuße a écrit :


Hi Xavier,


Thanks, I wrote a mail to Martin Scharrer yesterday.


Known @upstream, marking. If you want to provide help, please contact
upstream author.


I just pushed a pull request to fix it on Bitbucket, hope that it will 
be accepted soon.


The bitbucket repo is gone, the code is on 
https://sourceforge.net/p/lstaddons/code/ci/default/tree/ now. Please be 
so kind to open a new issue in the hope to get a fix at any time in the 
future.


Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016779: golang-github-lucas-clemente-quic-go: FTBFS with go1.19

[Shengjing Zhu]

Source: golang-github-lucas-clemente-quic-go
Version: 0.26.0-1
Severity: serious
X-Debbugs-Cc: z...@debian.org

As usual, this package FTBFS every time when golang-defaults bumps Go version...

# github.com/lucas-clemente/quic-go/internal/qtls
src/github.com/lucas-clemente/quic-go/internal/qtls/go119.go:6:13: cannot use 
"quic-go doesn't build on Go 1.19 yet." (untyped string constant) as int value 
in variable declaration
expvar

Bug#1016778: timeshift: app from bullseye-backports can't be installed on bullseye

[Артём Пасько]

Package: timeshift
Version: 22.06.5-1~bpo11+1
Severity: normal

kodi@deb:~$ uname -a
Linux deb 5.10.0-16-amd64 #1 SMP Debian 5.10.127-2 (2022-07-23) x86_64 
GNU/Linux

kodi@deb:~$ sudo apt install -t bullseye-backports timeshift
[sudo] password for kodi:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer 
required:

 accountsservice apg appstream apt-config-icons bolt colord-data
 dns-root-data dnsmasq-base fwupd fwupd-amd64-signed
 gir1.2-accountsservice-1.0 gir1.2-dazzle-1.0 gir1.2-gck-1 gir1.2-gcr-3
 gir1.2-gdm-1.0 gir1.2-gmenu-3.0 gir1.2-gnomebluetooth-1.0
 gir1.2-graphene-1.0 gir1.2-grilo-0.3 gir1.2-handy-0.0 gir1.2-ibus-1.0
 gir1.2-malcontent-0 gir1.2-mediaart-2.0 gir1.2-mutter-7 gir1.2-nm-1.0
 gir1.2-nma-1.0 gir1.2-packagekitglib-1.0 gir1.2-polkit-1.0 
gir1.2-rsvg-2.0

 gir1.2-upowerglib-1.0 gnome-control-center-data gnome-session-bin
 gnome-session-common gnome-settings-daemon-common gnome-shell-common
 gnome-software-common gstreamer1.0-pipewire hyphen-en-us ibus 
ibus-data
 ibus-gtk ibus-gtk3 im-config iptables libaccountsservice0 
libappstream-glib8

 libappstream4 libbluetooth3 libcolord-gtk1 libcolorhug2 libept1.6.0
 libflashrom1 libflatpak0 libfreerdp2-2 libftdi1-2 libfuse3-3 libfwupd2
 libfwupdplugin1 libgail-common libgail18 libgcab-1.0-0 libgdm1
 libgnome-menu-3-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common 
libibus-1.0-5

 libip6tc2 libjcat1 libjim0.79 liblzo2-2 libmalcontent-0-0
 libmalcontent-ui-0-0 libmbim-glib4 libmbim-proxy libmutter-7-0 libndp0
 libnetfilter-conntrack3 libnfnetlink0 libnm0 libnma-common libnma0
 libnss-myhostname libntfs-3g883 libostree-1-1 libpipewire-0.3-0
 libpipewire-0.3-modules libplymouth5 libpulse-mainloop-glib0 
libqmi-glib5
 libqmi-proxy libreoffice-help-common libreoffice-help-en-us 
libsmbios-c2

 libspa-0.2-modules libteamdctl0 libtss2-esys-3.0.2-0 libtss2-mu0
 libtss2-sys1 libtss2-tcti-cmd0 libtss2-tcti-device0 
libtss2-tcti-mssim0

 libtss2-tcti-swtpm0 libvncserver1 libwinpr2-2 libxapian30 libxcb-res0
 libxkbcommon-x11-0 libxmlb1 mobile-broadband-provider-info 
mutter-common
 mythes-en-us node-normalize.css pipewire pipewire-bin 
python3-distro-info

 python3-ibus-1.0 python3-software-properties realmd
 software-properties-common software-properties-gtk switcheroo-control
 tpm-udev unattended-upgrades usb-modeswitch usb-modeswitch-data 
xwayland

Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
 fonts-lato gist initscripts insserv inxi libglew2.1 libjs-jquery
 libmbim-glib4 libmbim-proxy libmm-glib0 libnm0 libqmi-glib5 
libqmi-proxy
 libruby2.7 libsystemd0 libudev1 libxapp1 lm-sensors mesa-utils rake 
rsync
 ruby ruby-json ruby-minitest ruby-net-telnet ruby-power-assert 
ruby-rubygems
 ruby-test-unit ruby-xmlrpc ruby2.7 rubygems-integration startpar 
sysv-rc

 tree udev xapps-common zip
Suggested packages:
 bootchart2 libxml-dumper-perl glew-utils fancontrol read-edid 
i2c-tools ri

 ruby-dev bundler
Recommended packages:
 modemmanager
The following packages will be REMOVED:
 chrome-gnome-shell colord dbus-user-session fuse3 gdm3 gnome
 gnome-color-manager gnome-control-center gnome-core gnome-music
 gnome-remote-desktop gnome-session gnome-settings-daemon gnome-shell
 gnome-shell-extension-prefs gnome-shell-extensions gnome-software
 gnome-tweaks gstreamer1.0-packagekit gvfs-fuse init libnss-systemd
 libpam-systemd malcontent malcontent-gui modemmanager mount 
network-manager
 network-manager-gnome ntfs-3g os-prober packagekit packagekit-tools 
plymouth

 plymouth-label policykit-1 rtkit synaptic systemd systemd-sysv
 systemd-timesyncd task-gnome-desktop util-linux util-linux-locales
 xdg-desktop-portal xdg-desktop-portal-gtk
The following NEW packages will be installed:
 fonts-lato gist initscripts insserv inxi libglew2.1 libjs-jquery 
libruby2.7

 libxapp1 lm-sensors mesa-utils rake rsync ruby ruby-json ruby-minitest
 ruby-net-telnet ruby-power-assert ruby-rubygems ruby-test-unit 
ruby-xmlrpc
 ruby2.7 rubygems-integration startpar sysv-rc timeshift tree 
xapps-common

 zip
The following packages will be upgraded:
 libmbim-glib4 libmbim-proxy libmm-glib0 libnm0 libqmi-glib5 
libqmi-proxy

 libsystemd0 libudev1 udev
WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
 init systemd-sysv (due to init) util-linux
9 upgraded, 29 newly installed, 46 to remove and 101 not upgraded.
Need to get 16.0 MB of archives.
After this operation, 62.5 MB disk space will be freed.
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
?]

Bug#1016777: dh-golang: -fstack-protector-strong no longer works on go1.19/i386

[Shengjing Zhu]

Package: dh-golang
Version: 1.56
Severity: serious
Forwarded: https://github.com/golang/go/issues/54313
X-Debbugs-Cc: z...@debian.org

Lots of regression on i386 when golang-defaults bump Go from go1.18 to go1.19.

The error happens when run `go test`

# github.com/containerd/containerd/snapshots/overlay.test
runtime/cgo(.text): unknown symbol __stack_chk_fail_local in pcrel
runtime/cgo(.text): unknown symbol __stack_chk_fail_local in pcrel
runtime/cgo(.text): unknown symbol __stack_chk_fail_local in pcrel
runtime/cgo(.text): unknown symbol __stack_chk_fail_local in pcrel
runtime/cgo(.text): unknown symbol __stack_chk_fail_local in pcrel
runtime/cgo(.text): relocation target __stack_chk_fail_local not defined
runtime/cgo(.text): relocation target __stack_chk_fail_local not defined

Bug#1016213: You can close this

[Albert Astals Cid]

I figured out i was doing things wrong (compiling with libc++ and them removing 
it manually form compile_commands.josn)  so this is a PBKAC please close the 
bug report.

Bug#884434: nginx: Please include ssl_cert_cb_yield patch for lua-resty-auto-ssl

[Jérémy Lal]

Source: nginx
Version: 1.22.0-1
Followup-For: Bug #884434
X-Debbugs-Cc: Jan Mojzis 

Now that lua-resty-core and probably lua-nginx-module,
the need for ssl_certificate_by_lua to be working will make more sense,
as it allows modules like
https://github.com/fffonion/lua-resty-acme
to use ACME to setup a ssl certificate.

I've been using that patch on many versions of nginx: it is quite easy
to maintain, it touches a part of the code doesn't change much over the years.

On the other hand, ssl_session_fetch_by_lua is doomed, because it also requires
to patch openssl. It's less problematic though, since its use case is much less 
common
(lua-nginx-module documentation mentions setup of distributed ssl sessions).



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

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

Bug#1003255: (no subject)

[Hilmar Preuße]

Control: tags -1 + wontfix

Am 07.01.2022 um 13:50 teilte Peter Mueller mit:

Hi,


but if you don't have transparency or don't know whether you have
transparency (e.g., because your document is huge or written by
someone else), an excessful warning is, well, more bothering than
helpful. I'd prefer that the transparency code doesn't even get into
the Postscript file if transparency isn't used in the source LaTeX
document.
As explained by upstream:


That behaviour will not be changed! PSTricks has no internal check if 
someone uses the opacity or strokeopacity options. You can use instead 
lualatex then you do not need the ghostscript run.


Other methods to avoid the warning were suggested on 
https://tex.stackexchange.com/q/629314/50836


So I tag wontfix.

H.
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1016776: channel 13 broken on b43 (brcmsmac) driver since wireless-regdb-2022.04.08-2~deb11u1

[kolafl...@kolahilft.de]

Package: wireless-regdb
Version: 2022.04.08-2~deb11u1

Since version 2022.04.08-2~deb11u1 of wireless-regdb my Lenovo notebook 
doesn't show up channel 13 wireless networks.


Downgrading to version wireless-regdb-2020.04.29-2 fixes the problem.
https://snapshot.debian.org/archive/debian/20200630T204925Z/pool/main/w/wireless-regdb/wireless-regdb_2020.04.29-2_all.deb


OS: Debian-11 (KDE with NetworkManager)
Notebook: Lenovo G560 (Model: 0679)
CPU: Intel(R) Core(TM) i3 CPU   M 350  @ 2.27GHz


NIC:

06:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4313 
802.11bgn Wireless Network Adapter (rev 01)


product: BCM4313 802.11bgn Wireless Network Adapter

configuration: broadcast=yes driver=brcmsmac 
driverversion=5.10.0-16-amd64 firmware=610.812 ip=192.168.37.15 
latency=0 link=yes multicast=yes wireless=IEEE 802.11



I have no experience with the wireless stack.
But please feel free to tell me what to test or which logs to send.

Maybe related:
  wireless-regdb stable policy
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006127






I'm not sure how this is caused. I guess maybe it's an error in the 
regdb, maybe the b43 driver is interpreting the regdb wrongly.
I got another notebook (HP) with RTL8822BE wireless which is still 
connecting to channel 13 networks with wireless-regdb-2022.04.08-2~deb11u1.



I've tried
  rmmod b43; modprobe b43 allhwsupport=1
but that didn't help.

I picked some interesting dmesg lines. But they also show up when 
rebooting after downgrading to wireless-regdb-2020.04.29-2



 789 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.466425] cfg80211: Loading 
compiled-in X.509 certificates for regulatory database
 790 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.466920] cfg80211: Loaded 
X.509 cert 'b...@debian.org: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
 791 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.467404] cfg80211: Loaded 
X.509 cert 'romain.per...@gmail.com: 3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
 792 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.467890] cfg80211: Loaded 
X.509 cert 'sforshee: 00b28ddf47aef9cea7'
 793 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.740967] platform 
regulatory.0: firmware: direct-loading firmware regulatory.db
 794 Aug  7 08:45:41 AnnaMargaretePC kernel: [   23.763353] platform 
regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
 795 Aug  7 08:45:41 AnnaMargaretePC kernel: [   24.706741] Support for cores 
revisions 0x17 and 0x18 disabled by module param allhwsupport=0. Try 
b43.allhwsupport=1
 796 Aug  7 08:45:41 AnnaMargaretePC kernel: [   24.706756] b43: probe of 
bcma0:1 failed with error -524
 797 Aug  7 08:45:41 AnnaMargaretePC kernel: [   24.706811] Broadcom 43xx 
driver loaded [ Features: PNLS ]

[...]

 804 Aug  7 08:45:41 AnnaMargaretePC kernel: [   25.350732] brcmsmac bcma0:1: 
mfg 4bf core 812 rev 24 class 0 irq 17
 805 Aug  7 08:45:41 AnnaMargaretePC kernel: [   25.351802] ieee80211 phy0: 
Selected rate control algorithm 'minstrel_ht'





rmmod b43; rmmod brcmsmac; rmmod mac80211; rmmod cfg80211; iw reg get; 
iw reg set DE; iw reg get; modprobe -v cfg80211 ieee80211_regdom=DE; iw 
reg get; modprobe -v mac80211; iw reg get; iw reg get; modprobe -v 
brcmsmac; iw reg get; modprobe -v b43; iw reg get



global
country 00: DFS-UNSET
(755 - 928 @ 2), (N/A, 20), (N/A), PASSIVE-SCAN
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
(5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
(5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
(57240 - 63720 @ 2160), (N/A, 0), (N/A)

global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(57000 - 66000 @ 2160), (N/A, 40), (N/A)

global
country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
(5470 - 5725 @ 160), (N/A, 26), (0 ms), DFS
(5725 - 5875 @ 80), (N/A, 13), (N/A)
(5945 - 6425 @ 160), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(57000 - 66000 @ 2160), (N/A, 40), (N/A)

insmod /lib/modules/5.10.0-16-amd64/kernel/net/mac80211/mac80211.ko 
global

country DE: DFS-ETSI
(2400 - 2483 @ 40), (N/A, 20), (N/A)
(5150 - 5250 @ 80), (N/A, 23), (N/A), NO-OUTDOOR, AUTO-BW
(5250 - 5350 @ 80), (N/A, 20), (0 ms), NO-OUTDOOR, DFS, AUTO-BW
 

Bug#1016416: Coq-related packages transition - coq-elpi

[julien . puydt]

Hi,

Le mardi 02 août 2022 à 21:43 +0200, Sebastian Ramacher a écrit :
> On 2022-07-31 13:23:38 +0200, julien.pu...@gmail.com wrote:
> > Package: release.debian.org
> > 
> > Some Coq-related packages need a rebuild:
> > 
> > coq-hierarchy-builder
> > mathcomp-algebra-tactics mathcomp-analysis
> > 
> > where packages on the same line can be handled in parallel.
> > 
> > I can't give a nice ben script because the abi checksum varies with
> > the
> > architecture (see today's mail on debian-devel where I'm trying to
> > find
> > ideas for a better approach).
> 
> From the discussion on -devel, a permanent tracker like the one for
> Haskell (https://release.debian.org/transitions/html/haskell.html)
> could
> help with the rebuilds for coq-* and related packages. Do all
> affected
> packages depends on some package that we can use as a basis for the
> permapermanent tracker?

Short answer: no.

Longer answer: I have some code to manage the Coq-related packages,
which can answer simple questions and might answer complex questions.

For example, if I want to update src:coq-elpi, I can run:

./planif_transition.py coq-elpi
coq-elpi
coq-hierarchy-builder
mathcomp-algebra-tactics mathcomp-analysis

which tells me what packages I can update and in which order ; some can
be parallelized (same line).

Since the thread on debian-devel was started, I tried to write another
script, aptly named wanna-build, but I'm not sure I got everything
right. If I wanted to upload the new upstream of coq-elpi, the plan
would be:

./wanna-build.py coq-elpi 1.15.5-1
 nmu coq-hierarchy-builder_1.3.0-1 . ANY . -m 'Rebuild due to new coq-
elpi 1.15.5-1'
 dw coq-hierarchy-builder_1.3.0-1 . ANY . -m 'coq-elpi => 1.15.5-1'
 nmu mathcomp-algebra-tactics_1.0.0-6+b1 . ANY . -m 'Rebuild due to new
coq-elpi 1.15.5-1'
 dw mathcomp-algebra-tactics_1.0.0-6+b1 . ANY . -m 'coq-elpi => 1.15.5-
1'
 nmu mathcomp-analysis_0.5.2-2 . ANY . -m 'Rebuild due to new coq-elpi
1.15.5-1'
 dw mathcomp-analysis_0.5.2-2 . ANY . -m 'coq-elpi => 1.15.5-1'
 dw mathcomp-analysis_0.5.2-2 . ANY . -m 'coq-hierarchy-builder =>
1.3.0-1+b1'

You might be worried that the planif-transition and wanna-build scripts
don't agree on the right time to build mathcomp-algebra-tactics. The
reason is that the first looks at the whole dependency graph of Coq-
related packages while the second only sees the extracted affected
packages dependency graph: both are right, and guarantee a sane
building order.

Does that look sane?

Cheers,

J.Puydt

Bug#1016775: python-packaging: please drop pypy-packaging to support python2.7 removal

[Paul Gevers]

Source: python-packaging
Version: 21.3-1
Severity: serious
Justification: rt

Dear Matthias,

If I didn't make a mistake, pypy-packaging is keeping pypy in the key
package set because it Build-Depends on it. Again, if I didn't make a
mistake, there are no reverse Build-Depends or Depends anymore of
pypy-packaging, so I think the package can just be dropped. That would
be another step in the python2.7 removal transition.

Paul

Bug#1016625: bart-cuda: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value'

[Martin Uecker]

I will look at this in a couple of days. I think it only
needs a std=c++14 or something aded to the nvcc flags.

Martin


Am Sonntag, den 07.08.2022, 13:06 +0530 schrieb Nilesh Patra:
> Hi Martin,
> 
> [CC'ing both your email addresses since I don't know which one you use]
> 
> Since this is your package, could you consider taking a look please?
> 
> On Thu, 04 Aug 2022 04:31:30 +0200 Andreas Beckmann  wrote:
> > Source: bart-cuda
> > Version: 0.7.00-5
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source
> > 
> > Hi,
> > 
> > bart-cuda recently started to FTBFS in sid, while it still succeeds in
> > testing.
> > 
> > /usr//bin/nvcc -DUSE_CUDA -Xcompiler -fPIC -Xcompiler -fopenmp -O3  
> > -I/build/bart-cuda-
> > 0.7.00/src/ -m64 -ccbin gcc -c 
> > /build/bart-cuda-0.7.00/src/wavelet/wl3-cuda.cu -o /build/bart-
> > cuda-0.7.00/src/wavelet/wl3-cuda.o
> > /usr/include/c++/10/type_traits:71:52: error: redefinition of 'constexpr 
> > const _Tp
> > std::integral_constant<_Tp, __v>::value'
> >71 |   template
> >   |^
> >
> > /usr/include/c++/10/type_traits:59:29: note: 'constexpr const _Tp value' 
> > previously declared
> > here
> >59 |   static constexpr _Tp  value = __v;
> >   | ^
> > make[2]: *** [Makefile:332: /build/bart-cuda-0.7.00/src/wavelet/wl3-cuda.o] 
> > Error 1
> > 
> > Andreas

Bug#1016406: telegram-desktop: Segfault in librlottie.so.0.1.0-1

[piorunz]

Hello Nicholas,

Thanks for prompt reply. Yes this happens as stickers gets populated and
start animating, suddenly it crashes, most likely on same sticker.

Anyway, your fix works. Thank you. After installing your version of the
library telegram does not crash anymore. Well done!

On 06/08/2022 12:31, Nicholas Guriev wrote:

Control: reassign -1 librlottie0-1 0.1+dfsg-2
Control: affects -1 telegram-desktop

Hello!

The segfault definitely occurred because of an animated sticker. But I do not
know how to catch the buggy sticker. The issue is undoubtedly relates to the
librlottie.so library. So reassigning the bug.

I am working on an update of the rlottie package with many crash fixes. It
could help in your case. Can you please check my interim version? There is
pre-built binary package on the Salsa CI.

https://salsa.debian.org/debian/rlottie/-/jobs/2826625/artifacts/file/debian/output/librlottie0-1_0.1+dfsg-2+salsaci_amd64.deb



--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄

Bug#1016774: ldap-account-manager: Not migrating to testing as not all binary packages built on buildds

[Salvatore Bonaccorso]

Source: ldap-account-manager
Version: 8.0.1-1
Severity: serious
Justification: arch all binaries not built on buildds
X-Debbugs-Cc: car...@debian.org

Hi

As not all binary packages were built on buildds an the unstable
upload included arch all binaries ldap-account-manager cannot migrate
to testing.

According to https://tracker.debian.org/pkg/ldap-account-manager so it
will need a new source-only upload to allow migration.

Regards,
Salvatore