Bug#996540: Post install fails when run as non-root user and does not respect PKG_ROOT

[Johannes Schauer Marin Rodrigues]

Quoting Hilmar Preuße (2022-01-14 23:57:32)
> > The post install is failing when dpkg is configured with a root and run as
> > an unprivileged user. This is an issue partly with packaging and partly
> > with the upstream package (I think). The upstream issue can be remedied
> > with a patch in the packaging.
> > 
> Did you test of texinfo 6.8 eventually solves the issue?
> 
> Further I don't understand the use case: under which situations will a
> configuration script will be run as non-privileged user?

None. Glenn also filed #996435, #996438 and #996542 and my answer to the latter
also holds for this bug:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996542#25

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1003759: src:libnetconf2: fails to migrate to testing for too long: (Build-)Depends on new package that's not migrating

[Paul Gevers]

Source: libnetconf2
Version: 1.1.16-1.1
Severity: serious
Control: close -1 2.0.24-3
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

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:libnetconf2 has been trying to migrate for 
61 days [2]. Hence, I am filing this bug.


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=libnetconf2



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003758: src:fastjet: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: fastjet
Version: 3.0.6+dfsg-3
Severity: serious
Control: close -1 3.4.0-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 999761

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:fastjet has been trying to migrate for 61 
days [2]. Hence, I am filing this bug.


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=fastjet



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1001545: [Pkg-opencl-devel] Bug#1001545: pyopencl, build-depends on package that is no longer in testing

[Paul Gevers]

On Wed, 12 Jan 2022 19:33:11 + "Rebecca N. Palmer" 
 wrote:
Probably just Build-Depends: pocl-opencl-icd [amd64 arm64 armel armhf 
i386 hurd-i386] and skip the tests on the other architectures.  (Linking 
uses libopencl1, not *-opencl-icd.)


As a slightly unrelated note, if that Build-Depends is only used during 
testing, than please also mark it with the  build profile to 
document that fact. That makes reasoning about these kind of things 
easier for non-experts.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003757: busybox ip ignores peer name on veth pair creation

[mc36]

Package: busybox
Version: 1:1.30.1-7+b2
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

i need to create multiple veth pair interfaces, preferably from busybox...

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

mc36@noti:~$
mc36@noti:~$ sudo ip link add veth9a type veth peer name veth9b
mc36@noti:~$ ip link show veth9a
9: veth9a@veth9b:  mtu 1500 qdisc noop state DOWN
mode DEFAULT group default qlen 1000
link/ether 42:65:ad:1b:c4:da brd ff:ff:ff:ff:ff:ff
mc36@noti:~$ sudo ip link del veth9a
mc36@noti:~$ sudo /bin/busybox ip link add veth9a type veth peer name veth9b
mc36@noti:~$ ip link show veth9a
11: veth9a@veth0:  mtu 1500 qdisc noop state DOWN
mode DEFAULT group default qlen 1000
link/ether 42:65:ad:1b:c4:da brd ff:ff:ff:ff:ff:ff
mc36@noti:~$ sudo ip link del veth9a
mc36@noti:~$


   * What was the outcome of this action?

as you can see when i used iproute2 then it freates veth9a-veth9b pair, but
when i used busybox, it created veth9a-veth0 pair

   * What outcome did you expect instead?

busybox's ip should honor peer name as iproute2's ip does

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


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

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

Versions of packages busybox depends on:
ii  libc6  2.33-2

busybox recommends no packages.

busybox suggests no packages.

-- no debconf information

Bug#1003704: bugs.debian.org: error compiling kernel 5.16

[Don Armstrong]

Control: severity -1 important
Control: reassign -1 binutils
Control: found -1 binutils/2.35.2-2
Control: tag -1 moreinfo


On Thu, 13 Jan 2022, gdaniel1358 wrote:
> Package: bugs.debian.org
> Severity: grave
> Justification: can not compile kernel 5.16
> X-Debbugs-Cc: gdaniel1...@hotmail.com
> 
> Dear Maintainer,
> 
> Hi, tried to compile kernel 5.16.0 from kernel.org.
> At linking point I get:
> 
>  CHK include/generated/compile.h
>   LD  vmlinux.o
>   MODPOST vmlinux.symvers
>   MODINFO modules.builtin.modinfo
>   GEN modules.builtin
>   LD  .tmp_vmlinux.btf
> ld: BFD (GNU Binutils for Debian) 2.35.2 internal error, aborting at 
> ../../bfd/merge.c:939 in _bfd_merged_section_offset
> 
> ld: Please report this bug.


This looks like a bug in ld (part of binutils), not a bug in
bugs.debian.org. I'm guessing that this is binutils 2.35.2-2.

Please confirm the version and the architecture that you are seeing this
bug in.

-- 
Don Armstrong  https://www.donarmstrong.com

The whole modern world has divided itself into Conservatives and
Progressives. The business of Progressives is to go on making
mistakes. The business of the Conservatives is to prevent the mistakes
from being corrected.
 -- G. K. Chesterton "Illustrated London News (1924-04-19)"

Bug#1003756: squeekboard, build-depends unsatisfiable

[peter green]

Package: squeekboard
Version:  1.14.0-3
Severity: serious
x-debbugs-cc: deb...@nilux.be

squeekboard's build-dependencies are unsatisfiable in unstable due to the
new version of the rust gtk stack. I tried relaxing the depenencies
(on both the Debian side and cargo side), but it failed with the following

error[E0432]: unresolved import `gtk::WidgetExt`
  --> /remap-pwd/src/drawing.rs:13:5
   |
13 | use gtk::WidgetExt;
   | ^-
   | ||
   | |help: a similar name exists in the module: `Widget`
   | no `WidgetExt` in the root

error[E0432]: unresolved import `gio::ActionMapExt`
  --> /remap-pwd/src/popover.rs:16:5
   |
16 | use gio::ActionMapExt;
   | ^
   | ||
   | |help: a similar name exists in the module: `ActionMap`
   | no `ActionMapExt` in the root

error[E0432]: unresolved import `gio::SettingsExt`
  --> /remap-pwd/src/popover.rs:17:5
   |
17 | use gio::SettingsExt;
   | ^---
   | ||
   | |help: a similar name exists in the module: `Settings`
   | no `SettingsExt` in the root

error[E0432]: unresolved import `gtk::BuilderExtManual`
  --> /remap-pwd/src/popover.rs:23:5
   |
23 | use gtk::BuilderExtManual;
   | ^ no `BuilderExtManual` in the root

error[E0432]: unresolved import `gtk::PopoverExt`
  --> /remap-pwd/src/popover.rs:24:5
   |
24 | use gtk::PopoverExt;
   | ^--
   | ||
   | |help: a similar name exists in the module: `Popover`
   | no `PopoverExt` in the root

error[E0432]: unresolved import `gtk::WidgetExt`

It seems to me that the new version of the rust gtk stack has changed the
API quite substantially. I haven't looked deeper into porting this myself

Debdiff adjusting the dependencies is attatched.


diff -Nru squeekboard-1.14.0/debian/changelog 
squeekboard-1.14.0/debian/changelog
--- squeekboard-1.14.0/debian/changelog 2021-11-16 18:41:52.0 +
+++ squeekboard-1.14.0/debian/changelog 2022-01-15 05:09:34.0 +
@@ -1,3 +1,12 @@
+squeekboard (1.14.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop dependencies on obsolete cargo features in rust gtk stack.
+  * Use -f in rm command in clean target so it doesn't fail if the file
+is already gone.
+
+ -- Peter Michael Green   Sat, 15 Jan 2022 05:09:34 +
+
 squeekboard (1.14.0-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru squeekboard-1.14.0/debian/patches/relax-dep.patch 
squeekboard-1.14.0/debian/patches/relax-dep.patch
--- squeekboard-1.14.0/debian/patches/relax-dep.patch   1970-01-01 
00:00:00.0 +
+++ squeekboard-1.14.0/debian/patches/relax-dep.patch   2022-01-15 
05:09:34.0 +
@@ -0,0 +1,53 @@
+Description: relax cargo dependencies
+Author: Peter Michael Green 
+
+Index: squeekboard-1.14.0/Cargo.deps
+===
+--- squeekboard-1.14.0.orig/Cargo.deps
 squeekboard-1.14.0/Cargo.deps
+@@ -1,22 +1,19 @@
+ # Dependencies which change based on build flags
+-bitflags = "1.2.*"
++bitflags = "^1.2"
+ clap = { version = "2.33.*", default-features = false }
+-regex = { version = "1.3.*", default-features = false, features = ["std", 
"unicode-case"] }
++regex = { version = "^1.3", default-features = false, features = ["std", 
"unicode-case"] }
+ 
+ [dependencies.cairo-rs]
+-version = "0.7.*"
++version = "0.14.*"
+ 
+ [dependencies.gdk]
+-version = "0.11.*"
++version = "0.14.*"
+ 
+ [dependencies.gio]
+-version = "0.7.*"
+-features = ["v2_44"]
++version = "0.14.*"
+ 
+ [dependencies.glib]
+-version = "0.8.*"
+-features = ["v2_44"]
++version = "0.14.*"
+ 
+ [dependencies.gtk]
+-version = "0.7.*"
+-features = ["v3_22"]
++version = "0.14.*"
+Index: squeekboard-1.14.0/Cargo.toml.in
+===
+--- squeekboard-1.14.0.orig/Cargo.toml.in
 squeekboard-1.14.0/Cargo.toml.in
+@@ -27,11 +27,9 @@ version = "*"
+ 
+ [dependencies.glib-sys]
+ version = "*"
+-features = ["v2_44"]
+ 
+ [dependencies.gtk-sys]
+ version = "*"
+-features = ["v3_22"]
+ 
+ [dependencies]
+ maplit = "1.0.*"
diff -Nru squeekboard-1.14.0/debian/patches/series 
squeekboard-1.14.0/debian/patches/series
--- squeekboard-1.14.0/debian/patches/series2021-11-16 17:09:40.0 
+
+++ squeekboard-1.14.0/debian/patches/series2022-01-15 05:09:34.0 
+
@@ -1,2 +1,3 @@
 fix_cargo_error.patch
 fix_meson_ftbfs.patch
+relax-dep.patch
diff -Nru squeekboard-1.14.0/debian/rules squeekboard-1.14.0/debian/rules
--- squeekboard-1.14.0/debian/rules 2021-11-16 16:18:30.0 +
+++ squeekboard-1.14.0/debian/rules 2022-01-15 05:09:25.0 +
@@ -24,7 +24,7 @@
 # The Debian version of linked-hash-map doesn't provide any hash,
 # causing Cargo to refuse to build with a crates.io copy
 build-arch:
-   rm Cargo.lock
+   rm -f Cargo.lock
dh $@ --builddirectory=_build 

Bug#1003631: dlocate: update-dpkg-list can deadlock

[Craig Sanders]

On Thu, Jan 13, 2022 at 09:45:31PM -0500, Aaron M. Ucko wrote:
> I am comfortable with Perl, and having taken another look at the code, was
> able to resolve the deadlock by arranging to feed xargs from a dedicated
> subprocess, per the attached patch.
>
> Could you please consider applying it?

TBH, it's been 6 years since I wrote that script and I can't remember why I
thought it was even necessary to run "apt-cache show". apt-cache doesn't have
access to any relevant data that grep-dctrl doesn't have.  It's quite possible
(very likely) that I was pre-emptively trying to handle a situation that could
never happen.

Can you test something for me?

Delete all the code from the "# as a last resort..." comment to the end of the
"if (@unknown) {...}" loop, and verify that it produces the same output on
your system (or, at least, that any differences are either insignificant or an
improvement)

It does on my system, but I don't have 2 unknown virtual packages. The
only difference on my system was that the script now outputs the correct
version number for the transitional libsane:i386 package (the version being
output previously was just ":i386" rather than "1.0.32-4:i386")

I have dlocate 1.10 almost ready to upload but just want to verify that it
will work properly in a context I'm unable to test myself.

craig

Bug#987781: libcrypt-dev violates Multi-Arch: same

[Helmut Grohne]

Control: tags -1 + pending

On Thu, Apr 29, 2021 at 01:14:45PM +0200, Helmut Grohne wrote:
> libcrypt-dev is declared Multi-Arch: same, but coinstalling it for
> architectures where libxcrypt uses different sonames breaks. For
> example:
> 
> | dpkg: error processing archive 
> /tmp/repo/pool/main/libx/libxcrypt/libcrypt-dev_4.4.18-4_musl-linux-i386.deb 
> (--unpack):
> |  trying to overwrite shared '/usr/share/doc/libcrypt-dev', which is 
> different from other instances of package libcrypt-dev:musl-linux-i386
> 
> This is due to the use of --link-doc with varying symlink targets. I
> fear that there is no good solution beyond simply not using --link-doc,
> so the attached patch converts the doc directory to a plain directory.

In accordance with devref 5.11.1 I have uploaded a slightly updated
patch (updated versions and changelog) to delayed/5. Please let me know
if this should be deferred any longer.

Helmut
diff --minimal -Nru libxcrypt-4.4.27/debian/changelog 
libxcrypt-4.4.27/debian/changelog
--- libxcrypt-4.4.27/debian/changelog   2021-12-17 23:48:21.0 +0100
+++ libxcrypt-4.4.27/debian/changelog   2022-01-14 20:10:07.0 +0100
@@ -1,3 +1,11 @@
+libxcrypt (1:4.4.27-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix M-A:same violation in libcrypt-dev by removing --link-doc.
+(Closes: #987781)
+
+ -- Helmut Grohne   Fri, 14 Jan 2022 20:10:07 +0100
+
 libxcrypt (1:4.4.27-1) unstable; urgency=medium
 
   * New upstream release.
diff --minimal -Nru libxcrypt-4.4.27/debian/libcrypt-dev.maintscript 
libxcrypt-4.4.27/debian/libcrypt-dev.maintscript
--- libxcrypt-4.4.27/debian/libcrypt-dev.maintscript1970-01-01 
01:00:00.0 +0100
+++ libxcrypt-4.4.27/debian/libcrypt-dev.maintscript2022-01-14 
20:04:09.0 +0100
@@ -0,0 +1 @@
+symlink_to_dir /usr/share/doc/libcrypt-dev libcrypt1 1:4.4.27-1.1~
diff --minimal -Nru libxcrypt-4.4.27/debian/rules libxcrypt-4.4.27/debian/rules
--- libxcrypt-4.4.27/debian/rules   2021-12-17 22:55:02.0 +0100
+++ libxcrypt-4.4.27/debian/rules   2022-01-14 20:04:09.0 +0100
@@ -146,16 +146,8 @@
--owner=root --group=root --numeric-owner \
| tar xf - -C $(DS)/usr/src/libxcrypt/
 
-override_dh_installdocs:
+execute_before_dh_installdocs:
cat debian/copyright.in LICENSING > debian/copyright
-   dh_installdocs -plibcrypt-dev --link-doc=libcrypt$(BUILD_DEV_VER)
-ifdef BUILD_DEB1
-   dh_installdocs -plibcrypt1
-endif
-ifdef BUILD_DEB2
-   dh_installdocs -plibcrypt2
-endif
-   dh_installdocs -plibxcrypt-source
 
 override_dh_installchangelogs:
dh_installchangelogs -XChangeLog NEWS

Bug#1003754: a typo in gpg --help zh_CN output

[肖盛文]

Package: gpg
Version: 2.2.12-1+deb10u1
Severity: minor
Tags: patch upstream l10n

Hi,

  There is a typo in gpg --help zh_CN output:

export LANG=zh_CN.UTF8;gpg --help|grep send-key
 --send-keys 个密钥导出到一个公钥服务器上

This patch fix the typo:

diff --git a/po/zh_CN.po b/po/zh_CN.po
index e85e23df0..2bf6f3588 100644
--- a/po/zh_CN.po
+++ b/po/zh_CN.po
@@ -2577,7 +2577,7 @@ msgstr "导出密钥"

 #: g10/gpg.c:505
 msgid "export keys to a keyserver"
-msgstr "个密钥导出到一个公钥服务器上"
+msgstr "导出密钥到一个公钥服务器上"

 #: g10/gpg.c:506
 msgid "import keys from a keyserver"

I'm the Debian Contributor, also a member of Debian Chinese team.
My Debian QA page:
https://qa.debian.org/developer.php?login=atzlinux%40sina.com



-- System Information:
Debian Release: 10.11
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), 
(500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-0.bpo.9-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=[proxychains] DLL init: 
proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
UTF-8), LANGUAGE=zh_CN.UTF-8 (charmap=[proxychains] DLL init: proxychains-ng 
4.13
[proxychains] DLL init: proxychains-ng 4.13
UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gpg depends on:
ii  gpgconf2.2.12-1+deb10u1
ii  libassuan0 2.5.2-1
ii  libbz2-1.0 1.0.6-9.2~deb10u1
ii  libc6  2.28-10
ii  libgcrypt201.8.4-5+deb10u1
ii  libgpg-error0  1.35-1
ii  libreadline7   7.0-5
ii  libsqlite3-0   3.27.2-3+deb10u1
ii  zlib1g 1:1.2.11.dfsg-1

Versions of packages gpg recommends:
ii  gnupg  2.2.12-1+deb10u1

gpg suggests no packages.

-- debconf information excluded

-- debsums errors found:
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13
[proxychains] DLL init: proxychains-ng 4.13

Bug#1003753: chromium: chromium --temp-profile window displays only as a white box

[Karl O. Pinc]

Package: chromium
Version: 97.0.4692.71-0.1~deb11u1
Severity: normal
X-Debbugs-Cc: t...@security.debian.org

Hello,

After upgrading chromium (and there were no other updates, only
chromium), chromium fails when started with --temp-profile.

When started with --temp-profile a white box is displayed in X instead
of a window.

I am using X, over a network; the X client and server are 2 different
boxes.

Regardless of whether started with --temp-profile or not, chromium
produces at least 1 "*** stack smashing detected ***: terminated"
messages.  These messages are repeated (forever?) every now and then
when started with --temp-profile.

FYI: I suspect that chromium has lately (sometime in the last few
months?)  been "running" when left open with a blank window (no url)
after startup.  If I switch to a different xfce4 desktop then I get a
dialog every few minutes about a window not responding and do I want
to terminate it or wait.  I believe this has been the chromium window.
Now, with the update, I notice (when started without --temp-profile)
that the little spinning icon on the left side of the tab spins
forever, or until I put a url in the address bar and go to a website.

On my system chromium has always displayed some errors when started
with --temp-profile.  Here are the before and after errors.


Before the upgrade:

$ chromium --temp-profile
Using temporary profile: /tmp/tmp.rt5PMS7VFH
libGL error: failed to authenticate magic 1
libGL error: failed to load driver: radeonsi
libva error: vaGetDriverNameByIndex() failed with unknown libva error, 
driver_name = (null)
[221529:221529:0114/123427.359380:ERROR:gpu_init.cc(426)] Passthrough is not 
supported, GL is desktop
[221529:221529:0114/123427.580913:ERROR:gl_context_glx.cc(172)] Failed to 
create GL context with glXCreateContextAttribsARB.
[221529:221529:0114/123427.581195:ERROR:gpu_info_collector.cc(81)] 
gl::init::CreateGLContext failed
[221529:221529:0114/123427.581332:ERROR:gpu_info_collector.cc(285)] Could not 
create context for info collection.
[221529:221529:0114/123427.581549:ERROR:gpu_init.cc(77)] CollectGraphicsInfo 
failed.
[221529:221529:0114/123427.586203:ERROR:viz_main_impl.cc(150)] Exiting GPU 
process due to errors during initialization
[221617:221617:0114/123427.635648:ERROR:gpu_init.cc(426)] Passthrough is not 
supported, GL is disabled


After the upgrade:

$ chromium --temp-profile&
Using temporary profile: /tmp/tmp.sLkvqeAASq
libGL error: failed to authenticate magic 1
libGL error: failed to load driver: radeonsi
[232438:232438:0114/204828.389040:ERROR:angle_platform_impl.cc(44)] 
Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not 
create a backing OpenGL context.
[232438:232438:0114/204828.389223:ERROR:gl_surface_egl.cc(783)] EGL Driver 
message (Critical) eglInitialize: Could not create a backing OpenGL context.
[232438:232438:0114/204828.389300:ERROR:gl_surface_egl.cc(1391)] eglInitialize 
OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[232438:232438:0114/204828.391912:ERROR:angle_platform_impl.cc(44)] 
Display.cpp:894 (initialize): ANGLE Display::initialize error 12289: Could not 
create a backing OpenGL context.
[232438:232438:0114/204828.391990:ERROR:gl_surface_egl.cc(783)] EGL Driver 
message (Critical) eglInitialize: Could not create a backing OpenGL context.
[232438:232438:0114/204828.392033:ERROR:gl_surface_egl.cc(1391)] eglInitialize 
OpenGLES failed with error EGL_NOT_INITIALIZED
[232438:232438:0114/204828.392073:ERROR:gl_ozone_egl.cc(20)] 
GLSurfaceEGL::InitializeOneOff failed.
[232438:232438:0114/204828.394380:ERROR:viz_main_impl.cc(161)] Exiting GPU 
process due to errors during initialization
[232506:232506:0114/204828.435430:ERROR:gpu_init.cc(457)] Passthrough is not 
supported, GL is disabled, ANGLE is 
[232403:232425:0114/204852.913999:ERROR:object_proxy.cc(642)] Failed to call 
method: org.freedesktop.DBus.Properties.Get: object_path= 
/org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.NoReply: Did not 
receive a reply. Possible causes include: the remote application did not send a 
reply, the message bus security policy blocked the reply, the reply timeout 
expired, or the network connection was broken.
[232403:232425:0114/204852.914036:ERROR:select_file_dialog_impl_portal.cc(243)] 
Failed to read portal version property
[232403:232531:0114/204859.116708:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)]
 START: ReportBluetoothAvailability(). If you don't see the END: message, this 
is crbug.com/1216328.
[232403:232531:0114/204859.116739:ERROR:chrome_browser_main_extra_parts_metrics.cc(230)]
 END: ReportBluetoothAvailability()
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack 

Bug#927673: new upstream version

[Christoph Anton Mitterer]

Hey.

I've tried to upgrade the package locally to 3.7.x ... but
unfortunately there seem to be considerable changes, the whole source
structure seem to have changed.

Right now we have all in:
src

but apparently already with 3.5.x things changed and no there's:
bin
conf
dev
tools
zookeeper-assembly
zookeeper-client
zookeeper-compatibility-tests
zookeeper-contrib
zookeeper-docs
zookeeper-it
zookeeper-jute
zookeeper-metrics-providers
zookeeper-recipes
zookeeper-server

Did you remove the other stuff previously from the orig tarball? Or did
that really change upstream?

gbp import-orig works of course fine, but reapplying the patch queue
gives quite some conflicts which I had no idea how to resolve (I'm not
really a java person).


So seems like upgrading this is a much bigger effort.


Cheers,
Chris.

Bug#980432: ITP: golang-github-jhump-protoreflect -- Reflection (Rich Descriptors) for Go Protocol Buffers

[陳昌倬]

Hi,

Do you need any help for golang-github-jhump-protoreflect package?

Currently I am working on kafkactl 
which also requires golang-github-jhump-protoreflect.


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


signature.asc
Description: PGP signature

Bug#1003650: firejail-profiles: Chromium running under the current profile cannot play sound

[Mad Horse]

Hi Reine,

I do not have any custom setup on my pipewire, nor custom firejail 
profile for chromium.


Started within firejail, chromium reported:

[10:46:0115/104317.720203:ERROR:bus.cc(397)] Failed to connect to the 
bus: Failed to connect to socket /run/firejail/mnt/dbus/system: 
Permission denied

libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
[56:56:0115/104317.772250:ERROR:sandbox_linux.cc(378)] 
InitializeSandbox() called with multiple threads in process gpu-process.
[10:85:0115/104317.887055:ERROR:bus.cc(397)] Failed to connect to the 
bus: Failed to connect to socket /run/firejail/mnt/dbus/system: 
Permission denied
[10:85:0115/104317.887112:ERROR:bus.cc(397)] Failed to connect to the 
bus: Failed to connect to socket /run/firejail/mnt/dbus/system: 
Permission denied
[10:85:0115/104317.887169:ERROR:bus.cc(397)] Failed to connect to the 
bus: Failed to connect to socket /run/firejail/mnt/dbus/system: 
Permission denied
[10:85:0115/104317.887206:ERROR:bus.cc(397)] Failed to connect to the 
bus: Failed to connect to socket /run/firejail/mnt/dbus/system: 
Permission denied
[10:85:0115/104317.887235:ERROR:bus.cc(397)] Failed to connect to the 
bus: Failed to connect to socket /run/firejail/mnt/dbus/system: 
Permission denied

/run/firejail/mnt/dbus/system do have permission 600, owned by root.

When trying to play sound, chromium in firejail reported:

Failed to create secure directory (/run/user/1000/pulse): Operation 
not permitted
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared 
library libasound_module_pcm_pulse.so 
(/usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_pulse.so: 
cannot open shared object file: Permission denied)
[307:307:0115/104404.402900:ERROR:alsa_util.cc(204)] PcmOpen: 
default,No such device or address
ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared 
library libasound_module_pcm_pulse.so 
(/usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_pulse.so: 
cannot open shared object file: Permission denied)
[307:307:0115/104404.404678:ERROR:alsa_util.cc(204)] PcmOpen: 
plug:default,No such device or address


but there is a unix domain socket /run/user/1000/pulse/native, owned by 
UID 1000, with permission 666,
and the permission of 
/usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_pulse.so is 
root,644.

Both were inspected inside firejail for chromium.

Do you have any idea about these?

Kind regards,

Mad Horse

On 2022/1/15 04:47, Reiner Herrmann wrote:

Hi Mad Horse,

On Thu, Jan 13, 2022 at 05:07:38PM +0800, Mad Horse wrote:

After upgraded to 97.0.4692.71-0.1, Chromium running inside firejail can no
longer play sound (e.g. when playing an online video), while bare Chromium
can. It is shown with PulseAudio Manager that the Chromium running inside
firejail cannot connect to the sound server while the bare Chromium can.

I had a similar issue initially as well. But it turned out to be related
to my custom sound setup (using pipewire with run directory in ~/pipewire).
There are also no sound-related Chromium issue known in the upstream
firejail bug tracker.

So I think it also has to be related to your setup.
It might be related to some whitelist in the chromium{-common}.profile,
as this causes the parent directory to get blocked.
Can you please try to figure out which path needs to be whitelisted
on your system to get it working again?

Kind regards,
   Reiner

Bug#670860: spell: diff for NMU version 1.0-24.2

[gregor herrmann]

Control: tags 670860 + pending


Dear maintainer,

I've prepared an NMU for spell (versioned as 1.0-24.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  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
   `-   
diff -Nru spell-1.0/debian/changelog spell-1.0/debian/changelog
--- spell-1.0/debian/changelog	2022-01-15 03:00:29.0 +0100
+++ spell-1.0/debian/changelog	2022-01-15 02:58:06.0 +0100
@@ -1,3 +1,13 @@
+spell (1.0-24.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "[PATCH] spell: Helping to update to packaging format 3.0":
+Convert to source format 3.0 from 1.0+dpatch.
+Based on a patch by Jari Aalto from 2012.
+(Closes: #670860)
+
+ -- gregor herrmann   Sat, 15 Jan 2022 02:58:06 +0100
+
 spell (1.0-24.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru spell-1.0/debian/control spell-1.0/debian/control
--- spell-1.0/debian/control	2022-01-15 03:00:29.0 +0100
+++ spell-1.0/debian/control	2022-01-15 02:47:33.0 +0100
@@ -2,7 +2,7 @@
 Section: text
 Priority: optional
 Maintainer: Giacomo Catenazzi 
-Build-Depends: debhelper (>= 7), dpatch, texinfo
+Build-Depends: debhelper (>= 7), texinfo
 Standards-Version: 3.8.2
 Homepage: http://directory.fsf.org/project/spell/
 
diff -Nru spell-1.0/debian/patches/00list spell-1.0/debian/patches/00list
--- spell-1.0/debian/patches/00list	2022-01-15 03:00:29.0 +0100
+++ spell-1.0/debian/patches/00list	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-01-conglomeration.dpatch
diff -Nru spell-1.0/debian/patches/01-conglomeration.dpatch spell-1.0/debian/patches/01-conglomeration.dpatch
--- spell-1.0/debian/patches/01-conglomeration.dpatch	2022-01-15 03:00:29.0 +0100
+++ spell-1.0/debian/patches/01-conglomeration.dpatch	1970-01-01 01:00:00.0 +0100
@@ -1,599 +0,0 @@
-#!/bin/sh /usr/share/dpatch/dpatch-run
-## 01-conglomeration.dpatch
-##
-## DP: Needs to be broken out (FIXME).
-
-@DPATCH@
-
-diff -Naur spell-1.0.orig/spell.c spell-1.0/spell.c
 spell-1.0.orig/spell.c	1996-04-10 04:41:09.0 +
-+++ spell-1.0/spell.c	2006-09-08 18:49:47.0 +
-@@ -71,17 +71,17 @@
- struct pipe
-   {
- /* File descriptors used by the parent process.  */
--int pin;			/* Input channel.  */
--int pout;			/* Output channel.  */
--int perr;			/* Error channel (for reading).  */
-+int pin;/* Input channel.  */
-+int pout;   /* Output channel.  */
-+int perr;   /* Error channel (for reading).  */
- 
- /* File descriptors used by the child process.  */
--int cin;			/* Input channel.  */
--int cout;			/* Output channel.  */
--int cerr;			/* Error channel (for writing).  */
-+int cin;/* Input channel.  */
-+int cout;   /* Output channel.  */
-+int cerr;   /* Error channel (for writing).  */
- 
--fd_set error_set;		/* Descriptor set used to check for
--   errors (contains perr).  */
-+fd_set error_set;   /* Descriptor set used to check for
-+   errors (contains perr).  */
-   };
- typedef struct pipe pipe_t;
- 
-@@ -116,6 +116,7 @@
-   {"ispell", required_argument, NULL, 'i'},
-   {"ispell-version", no_argument, NULL, 'I'},
-   {"number", no_argument, NULL, 'n'},
-+  {"ispell-dictionary", required_argument, NULL, 'D'},
-   {"print-file-name", no_argument, NULL, 'o'},
-   {"print-stems", no_argument, NULL, 'x'},
-   {"stop-list", required_argument, NULL, 's'},
-@@ -130,9 +131,12 @@
- /* Ispell's location.  */
- char *ispell_prog = NULL;
- 
--/* Dictionary to use.  Just use the default if NULL.  */
-+/* Personal dictionary to use.  Just use the default if NULL.  */
- char *dictionary = NULL;
- 
-+/* Ispell dictionary to use via ispell's -d argument */
-+char *idict = NULL;
-+
- /* Display Ispell's version (--ispell-version, -I). */
- int show_ispell_version = 0;
- 
-@@ -159,69 +163,75 @@
- int
- main (int argc, char **argv)
- {
--  char opt = 0;			/* Current option.  */
--  int opt_error = 0;		/* Whether an option error occurred.  */
--  int show_help = 0;		/* Display help (--help, -h).  */
--  int show_version = 0;		/* Display the version (--version, -V).  */
--  pid_t pid = 0;		/* Child's pid.  */
--  pipe_t ispell_pipe;		/* The descriptors for our pipe.  */
-+  int opt = 0;  /* Current option.  */
-+  int opt_error = 0;/* Whether an option error occurred.  */
-+  int show_help = 0;/* Display help (--help, -h).  */
-+  int show_version = 0; /* Display the version (--version, -V).  */
-+  pid_t pid = 0;/* Child's pid.  */
-+  pipe_t ispell_pipe;   /* The 

Bug#987395: media-types: Add image/jxl as a mime type

[Charles Plessy]

Le Fri, Jan 14, 2022 at 09:43:39AM +0100, Mathieu Malaterre a écrit :
> Odd, there is still nothing today:
> 
> https://www.iana.org/assignments/media-types/image/jxl

Hi Mathieu,

I checked on the ISO website and 3 parts out of 4 of the standard are
still reported to be in development, maybe that is the reason.

I see that many image/jx* have been registered to the IANA by
sc29-sec maybe you can ask that person if they have
a plan to do so for JPEG XL ?

Have a nice week-end,

Charles

-- 
Charles Plessy Nagahama, Yomitan, Okinawa, Japan
Tooting from work,   https://mastodon.technology/@charles_plessy
Tooting from home, https://framapiaf.org/@charles_plessy

Bug#1003752: Confirming bug 927219

[Twilight Sparkle]

Package: amdgpu
Version: unknown (all versions tested)

I've encountered bug 927219 several times in completely independent
hardware. It's some kind of configuration issue buried somewhere I can't
find. If you reinstall/uninstall GPU drivers enough times it seems possible
to reproduce, but horribly tedious. Once this issue occurs, I have never
been able to regain working X11 without reinstalling Debian.

Bug#1003710: stardict crash in gnome with message Segmentation fault

[肖盛文]

Hi,

    Thansk for your report.

在 2022/1/14 11:29, Quanlin Jie 写道:
> Package: stardict
> Version: 3.0.7+git20211225+dfsg-1
> Severity: normal
> X-Debbugs-Cc: ql...@whu.edu.cn
>
> Dear Maintainer,
>
> stardict does not start in gnome wayland. Every time I start it, I
> crashes with
> a message "Segmentation fault". However, I does start in gnome for
> xorg. But it
>
> crashes when scan option is turned on with the same "Segmentation
> fault" message. This is true for every user.
>
>
> It works well when I log in as another user both in wayland and xorg,
> i.e., another user logs into my gnome environment , or I log into
> other's desktop environment, to start stardict.

Another user is OK?

How about create a new user then login into  gnome wayland? Is it still
crashes with
a message "Segmentation fault"?


>
>
> -- System Information:
> Debian Release: bookworm/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.15.0-1-amd64 (SMP w/12 CPU threads)
> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages stardict depends on:
> ii stardict-gtk 3.0.7+git20211225+dfsg-1
>
> stardict recommends no packages.
>
> stardict suggests no packages.
>
> -- no debconf information

-- 
肖盛文 xiao sheng wen Faris Xiao 
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003751: ITP: kickoff -- Generalized job scheduler (with runners) for the Debian archive

[Felix Lechner]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-lint-ma...@lists.debian.org

* Package name: kickoff
  Version : 0.1.0
  Upstream Author : Felix Lechner 
* URL : https://salsa.debian.org/lintian/kickoff
* License : GPL-3.0-or-later
  Programming Lang: Haskell2010
  Description : Generalized job scheduler (with runners) for the
Debian archive

This package provides a generalized job scheduler. It supports fully
configurable processing actions on local copies of the Debian archive.

The programs herein generate the contents of the Lintian website.

This software falls under Lintian's umbrella and will be updated,
managed and serviced by the Lintian maintainers.

Bug#1003750: certmonger: FTBFS with OpenSSL 3.0

[Steve Langasek]

Package: certmonger
Version: 0.79.14+git20211010-2
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu jammy ubuntu-patch

Hi Timo,

In Ubuntu, the certmonger package is failing to build from source due to
missing linkage against -lssl.  This is probably related to the fact that
Ubuntu has migrated to OpenSSL 3, though I don't understand exactly why
these particular failures are happening only with OpenSSL 3.

The attached patch fixes the build failures in Ubuntu and will probably be
needed in Debian in the near future.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru 
certmonger-0.79.14+git20211010/debian/patches/missing-library-linkage.patch 
certmonger-0.79.14+git20211010/debian/patches/missing-library-linkage.patch
--- certmonger-0.79.14+git20211010/debian/patches/missing-library-linkage.patch 
1969-12-31 16:00:00.0 -0800
+++ certmonger-0.79.14+git20211010/debian/patches/missing-library-linkage.patch 
2022-01-14 15:42:06.0 -0800
@@ -0,0 +1,54 @@
+Description: Add missing linkage to -lssl
+ These commands use libssl but fail to link to it.
+Author: Steve Langasek 
+Last-Update: 2022-01-14
+Forwarded: no
+
+Index: certmonger-0.79.14+git20211010/src/Makefile.am
+===
+--- certmonger-0.79.14+git20211010.orig/src/Makefile.am
 certmonger-0.79.14+git20211010/src/Makefile.am
+@@ -182,11 +182,11 @@
+ certmonger_getcert_CFLAGS = $(getcert_CFLAGS)
+ certmonger_SOURCES = main.c env-system.c tm.c tm.h
+ certmonger_LDADD = libcm.a \
+- $(OPENSSL_LIBS) $(CERTMONGER_LIBS) $(KRB5_LIBS) $(IDN_LIBS) \
++ $(OPENSSL_SSL_LIBS) $(CERTMONGER_LIBS) $(KRB5_LIBS) 
$(IDN_LIBS) \
+  $(GMP_LIBS) $(UUID_LIBS) $(POPT_LIBS) $(LTLIBICONV) 
$(LDAP_LIBS)
+ certmonger_session_SOURCES = main.c env-session.c tm.c tm.h
+ certmonger_session_LDADD = libcm.a \
+- $(OPENSSL_LIBS) $(CERTMONGER_LIBS) $(KRB5_LIBS) $(IDN_LIBS) \
++ $(OPENSSL_SSL_LIBS) $(CERTMONGER_LIBS) $(KRB5_LIBS) 
$(IDN_LIBS) \
+  $(GMP_LIBS) $(UUID_LIBS) $(POPT_LIBS) $(LTLIBICONV) 
$(LDAP_LIBS)
+ noinst_PROGRAMS = tdbusm-check serial-check nl-check toklist
+ if WITH_XMLRPC
+@@ -264,14 +264,14 @@
+   pkcs7.c pkcs7.h store.h store-gen.c tm.c tm.h prefs.c prefs.h \
+   prefs-o.c prefs-o.h scep-o.c scep-o.h env.h env-system.c
+ scep_submit_LDADD = $(CURL_LIBS) $(XML_LIBS) $(NSS_LIBS) \
+-$(OPENSSL_LIBS) $(TALLOC_LIBS) \
++$(OPENSSL_SSL_LIBS) $(TALLOC_LIBS) \
+ $(GMP_LIBS) $(UUID_LIBS) $(LTLIBICONV) $(POPT_LIBS)
+ local_submit_CFLAGS = $(AM_CFLAGS) $(NSS_CFLAGS)
+ local_submit_SOURCES = local.c env.h store.h store-gen.c submit-o.c 
submit-o.h \
+  submit-u.c submit-u.h env-system.c env-shared.c log.c \
+  log.h prefs.c prefs.h prefs-o.c prefs-o.h tm.c tm.h \
+  util.c util.h util-o.c util-o.h pin.c pin.h
+-local_submit_LDADD = $(NSS_LIBS) $(OPENSSL_LIBS) $(TALLOC_LIBS) $(UUID_LIBS) \
++local_submit_LDADD = $(NSS_LIBS) $(OPENSSL_SSL_LIBS) $(TALLOC_LIBS) 
$(UUID_LIBS) \
+$(POPT_LIBS)
+ submit_d_CFLAGS = $(AM_CFLAGS) $(CURL_CFLAGS) $(XML_CFLAGS) -DCM_SUBMIT_D_MAIN
+ submit_d_SOURCES = submit-d.c submit-d.h submit-h.c submit-h.h \
+Index: certmonger-0.79.14+git20211010/tests/tools/Makefile.am
+===
+--- certmonger-0.79.14+git20211010.orig/tests/tools/Makefile.am
 certmonger-0.79.14+git20211010/tests/tools/Makefile.am
+@@ -2,7 +2,7 @@
+   $(XMLRPC_CFLAGS) $(IDN_CFLAGS) $(UUID_CFLAGS) $(LDAP_CFLAGS) \
+   $(POPT_CFLAGS) -I$(top_builddir)/src -I$(top_srcdir)/src
+ LDADD = libtools.a $(top_builddir)/src/libcm.a $(top_srcdir)/src/env-system.c 
\
+-  libtools.a $(OPENSSL_LIBS) $(CERTMONGER_LIBS) $(KRB5_LIBS) $(IDN_LIBS) \
++  libtools.a $(OPENSSL_SSL_LIBS) $(CERTMONGER_LIBS) $(KRB5_LIBS) 
$(IDN_LIBS) \
+   $(GMP_LIBS) $(UUID_LIBS) $(RESOLV_LIBS) $(POPT_LIBS) $(LTLIBICONV) \
+   $(LDAP_LIBS)
+ 
diff -Nru certmonger-0.79.14+git20211010/debian/patches/series 
certmonger-0.79.14+git20211010/debian/patches/series
--- certmonger-0.79.14+git20211010/debian/patches/series2021-10-10 
09:31:12.0 -0700
+++ certmonger-0.79.14+git20211010/debian/patches/series2022-01-14 
15:39:00.0 -0800
@@ -1,3 +1,4 @@
 fix-keythi-h-path.diff
 fix-service-environment.diff
 use-dbus-run-session.diff
+missing-library-linkage.patch

Bug#1003736: chromium: Casting via website provided app causes crash

[Andres Salomon]

On Fri, 14 Jan 2022 19:45:16 +0200 Kyle Robbertze wrote:
> Package: chromium
> Version: 97.0.4692.71-0.1
> Severity: normal
>
> Dear Maintainer,
>
> When casting a webpage to a Chromecast, Chromium crashes with the
> following error:
>
> free(): double free detected in tcache 2
> [0114/193804.521131:ERROR:elf_dynamic_array_reader.h(64)] tag not found
> [2928:2948:0114/193804.608997:ERROR:broker_posix.cc(40)] Recvmsg 
error: Connection reset by peer (104)

> fish: Job 1, 'chromium' terminated by signal SIGABRT (Abort)
>
> This is a new issue since the last update to unstable. Casting the tab
> works, however using the website-provided app triggers the crash. It can
> be replicated by opening a YouTube video, click on the cast icon and 
select

> a Chromecast. It will crash after connecting (i.e. YouTube's dashboard
> is displayed on the TV) while trying to start playing the video.
>

I can't reproduce this, since I don't have a device to cast to. Can you 
please "sudo apt-get install gdb", run "chromium -g", type "run" in gdb, 
do your youtube app casting, and then "bt" in gdb when it crashes. The 
backtrace may show us some more useful info.

Bug#1003622: chromium: microphone stopped working after upgrade

[Andres Salomon]

On 1/14/22 17:53, Francesco Poli wrote:

On Wed, 12 Jan 2022 15:30:19 -0500 Andres Salomon wrote:

[...]

Hi,

Hello Andres,
thanks for your prompt followup!

I was unfortunately unable to reply earlier than now.


Thanks for the bug report. Can you please start chromium from a terminal
and then go to your videoconferencing site and see if there are any
error messages that it outputs?

Well, I can try to upgrade again and redirect the stdout/stderr to a
file.
But, to be honest, I am not sure how much it can be useful: I always
start chromium from a terminal and it usually spits out a lot of
warnings/errors, and this happens whatever I do.


Please do. If it's unable to open the device for some reason, it may 
output a very useful error message - even if it's hidden in tons of 
other messages. Also, now I'm also curious what other messages you're 
seeing on the terminal, since I only see 3 different messages when I 
start up chromium and start a Jitsi meeting. :)




Also, is it multiple videoconferencing sites, or just one? I just tried
https://meet.jit.si with the new chromium version, and the mic worked
for me.

This surprises me a lot.

I tried with  and, sigh!, with

They both were unable to use my mic, until I downgraded to
chromium/93.0.4577.82-1


And just to be clear, this works in other browsers, right? If you start 
up firefox-esr and go to https://meet.jit.si/, the mic works? I know you 
said that it works with chromium 93, I just want to rule out that it's 
not due to building against a newer version of some library.

Bug#996540: Post install fails when run as non-root user and does not respect PKG_ROOT

[Hilmar Preuße]

Am 15.10.2021 um 07:42 teilte Glenn Washburn mit:

Hi Glenn,


The post install is failing when dpkg is configured with a root and
run as an unprivileged user. This is an issue partly with packaging
and partly with the upstream package (I think). The upstream issue
can be remedied with a patch in the packaging.


Did you test of texinfo 6.8 eventually solves the issue?

Further I don't understand the use case: under which situations will a 
configuration script will be run as non-privileged user?


Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003749: imagemagick-6.q16: convert foo.png foo.eps security violation leaves empty foo.eps

[Barak A. Pearlmutter]

Package: imagemagick-6.q16
Version: 8:6.9.11.60+dfsg-1.3
Severity: normal

/usr/bin/convert should not generate incorrect output files.  If the
output cannot be correctly generated, the output file should be removed.

The current behaviour is a problem when convert is used in a Makefile,
where the first run of "make" generates an error but also an empty
output file, then a second run of "make" treats that empty output file
as correct and continues later stages of the build.

Example:

$ ls -l stroke-signs-1.eps
ls: cannot access 'stroke-signs-1.eps': No such file or directory

$ convert stroke-signs-1.png stroke-signs-1.eps
convert-im6.q16: attempt to perform an operation not allowed by the
security policy `EPS' @ error/constitute.c/IsCoderAuthorized/421.

$ ls -l stroke-signs-1.eps
-rw-rw-r-- 1 barak barak 0 Jan 14 22:36 stroke-signs-1.eps

Bug#1003748: scoop: ROM; inactive upstream and no popcon

[Christian Kastner]

Package: ftp.debian.org
Severity: normal

Dear ftp-master,

Please remove src:scoop from the archive. It no reverse
build-dependencies, one reverse dependency (which I can remove under
team maintenance), and a very low popcon.

Upstream seems to have become inactive (5 commits in as many years), and
other modules have become the norm for distributed task computing in
Python anyway.

I think I adopted this package because it used to be a reverse
dependency of something I needed, but that no longer seems to be the point.

Thanks,
Christian

Bug#1003747: php-horde-ldap: (autopkgtest) needs update for php8.1: internal LDAP link is invalid

[Paul Gevers]

Source: php-horde-ldap
Version: 2.4.2-4
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults
Control: block 976811 by -1

Dear maintainer(s),

We are in the transition of replacing php7.4 with php8.1 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-ldap fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing92
php-horde-ldap from testing2.4.2-4
versioned deps from testingfrom unstable
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 
7.4 and may help to identify what needs to be updated.


php-commom added a whole set of versioned Breaks to make sure the right 
packages from current unstable are pulled in during testing. If the 
issue is caused by a missing breaks, please reasign this bug to php-common.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-ldap/18284154/log.gz

PHP Deprecated:  Return type of Horde_Ldap_Search::rewind() should 
either be compatible with Iterator::rewind(): void, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in 
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Search.php 
on line 508

..E..EE.EEF..E.. 41 / 41 (100%)

Time: 00:01.573, Memory: 6.00 MB

There were 6 errors:

1) Horde_Ldap_LdapTest::testModify
Horde_Ldap_Exception: Could not modify entry: Could not update entry: 
internal LDAP link is invalid


/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:729
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/test/Horde/Ldap/LdapTest.php:280

2) Horde_Ldap_LdapTest::testGetEntry
Horde_Ldap_Exception: Unable to create connected entry: Parameter $entry 
needs to be a ldap entry resource!


/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Entry.php:186
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Search.php:153
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:1082
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/test/Horde/Ldap/LdapTest.php:475

3) Horde_Ldap_LdapTest::testMove
Horde_Ldap_Exception: Could not update entry: internal LDAP link is invalid

/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Entry.php:637
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:1133
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/test/Horde/Ldap/LdapTest.php:530

4) Horde_Ldap_LdapTest::testRootDSE
Horde_Ldap_Exception: Unable to create connected entry: Parameter $entry 
needs to be a ldap entry resource!


/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Entry.php:186
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Search.php:153
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/RootDse.php:58
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:1305
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/test/Horde/Ldap/LdapTest.php:640

5) Horde_Ldap_LdapTest::testSchema
Horde_Ldap_Exception: Unable to create connected entry: Parameter $entry 
needs to be a ldap entry resource!


/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Entry.php:186
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Search.php:153
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/RootDse.php:58
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:1305
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap/Schema.php:96
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/lib/Horde/Ldap.php:1347
/tmp/autopkgtest-lxc.ounnp2bv/downtmp/build.lqh/src/Horde_Ldap-2.4.2/test/Horde/Ldap/LdapTest.php:649

6) Horde_Ldap_SearchTest::testSPLIterator
Horde_Ldap_Exception: Unable to create connected entry: Parameter $entry 
needs to be a ldap entry resource!

Bug#980990: marked as done (mark golang-github-danverbraganza-varcaser-dev Multi-Arch: foreign)

[Tong Sun]

On Thu, Jan 13, 2022 at 4:09 PM Debian Bug Tracking System
 wrote:
>
> Your message dated Thu, 13 Jan 2022 21:07:44 +
> with message-id 
> and subject line Bug#980990: fixed in golang-github-danverbraganza-varcaser 
> 0.0~git20190207.e3fb03e-2
> has caused the Debian Bug report #980990,
> regarding mark golang-github-danverbraganza-varcaser-dev Multi-Arch: foreign
> to be marked as done.
>
> This means that you claim that the problem has been dealt with.
> If this is not the case it is now your responsibility to reopen the
> Bug report if necessary, and/or fix the problem forthwith.

Hi Helmut,

Sorry for replying late, but it finally got fixed now.

One thing I don't understand about marking a package Multi-Arch:
foreign -- what would the impact be, e.g., would I be seeing anything
different in its build,
https://buildd.debian.org/status/package.php?p=golang-github-danverbraganza-varcaser,
etc?

Can you explain a bit please? thx!

Bug#984114: liblastfm: ftbfs with GCC-11

[Florian Ernst]

forwarded 984114 https://github.com/lastfm/liblastfm/issues/39
tags 984114 + patch
thanks

On Wed, Mar 03, 2021 at 04:14:30PM +, Matthias Klose wrote:
> [...]
> /<>/src/fingerprint/Fingerprint.cpp:97:60: error: ISO C++17 does 
> not allow dynamic exception specifications
>97 | lastfm::Fingerprint::generate( FingerprintableSource* ms ) throw( 
> Error )
>   |^
> /<>/src/fingerprint/Fingerprint.cpp:309:91: error: ISO C++17 
> does not allow dynamic exception specifications
>   309 | lastfm::Fingerprint::decode( QNetworkReply* reply, bool* 
> complete_fingerprint_requested ) throw( Error )
>   |   
> ^
> make[4]: *** 
> [src/fingerprint/CMakeFiles/lastfm_fingerprint5.dir/build.make:111: 
> src/fingerprint/CMakeFiles/lastfm_fingerprint5.dir/Fingerprint.cpp.o] Error 1
> [...]

FWIW, I can confirm that 1.0.9-1.1 still FTBFS in the manner originally
reported in this bug, but with the attached debdiff implementing the fix
from upstream I was able to build it again.

This is referenced in https://github.com/lastfm/liblastfm/issues/39 from
where I extracted the patch.

HTH, and please feel free to adjust to your liking.

Cheers,
Florian
diff -Nru liblastfm-1.0.9/debian/changelog liblastfm-1.0.9/debian/changelog
--- liblastfm-1.0.9/debian/changelog2019-08-23 23:37:23.0 +0200
+++ liblastfm-1.0.9/debian/changelog2022-01-14 22:30:53.0 +0100
@@ -1,3 +1,11 @@
+liblastfm (1.0.9-1.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with GCC-11 by removing dynamic exception specifications,
+patch taken from upstream. (Closes: #984114)
+
+ -- Florian Ernst   Fri, 14 Jan 2022 22:30:53 +0100
+
 liblastfm (1.0.9-1.1) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch 
liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch
--- liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch1970-01-01 
01:00:00.0 +0100
+++ liblastfm-1.0.9/debian/patches/fix_gcc11_ftbfs.patch2022-01-14 
22:30:47.0 +0100
@@ -0,0 +1,46 @@
+Description: Fix GCC-11 build issue
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984114
+Index: liblastfm-1.0.9/src/fingerprint/Fingerprint.cpp
+===
+--- liblastfm-1.0.9.orig/src/fingerprint/Fingerprint.cpp
 liblastfm-1.0.9/src/fingerprint/Fingerprint.cpp
+@@ -94,7 +94,7 @@ lastfm::Fingerprint::data() const
+
+
+ void
+-lastfm::Fingerprint::generate( FingerprintableSource* ms ) throw( Error )
++lastfm::Fingerprint::generate( FingerprintableSource* ms )
+ {
+ //TODO throw if we can't get required metadata from the track object
+
+@@ -306,7 +306,7 @@ lastfm::Fingerprint::submit() const
+
+
+ void
+-lastfm::Fingerprint::decode( QNetworkReply* reply, bool* 
complete_fingerprint_requested ) throw( Error )
++lastfm::Fingerprint::decode( QNetworkReply* reply, bool* 
complete_fingerprint_requested )
+ {
+ // The response data will consist of a number and a string.
+ // The number is the fpid and the string is either FOUND or NEW
+Index: liblastfm-1.0.9/src/fingerprint/Fingerprint.h
+===
+--- liblastfm-1.0.9.orig/src/fingerprint/Fingerprint.h
 liblastfm-1.0.9/src/fingerprint/Fingerprint.h
+@@ -71,7 +71,7 @@ namespace lastfm
+ };
+
+ /** This is CPU intensive, do it in a thread in your GUI application 
*/
+-void generate( FingerprintableSource* ) throw( Error );
++void generate( FingerprintableSource* );
+
+ /** Submits the fingerprint data to Last.fm in order to get a 
FingerprintId
+   * back. You need to wait for the QNetworkReply to finish before you 
can
+@@ -82,7 +82,7 @@ namespace lastfm
+   * will be valid. Otherwise we will throw. You always get a valid id
+   * or a throw.
+   */
+-void decode( QNetworkReply*, bool* 
lastfm_needs_a_complete_fingerprint = 0 ) throw( Error );
++void decode( QNetworkReply*, bool* 
lastfm_needs_a_complete_fingerprint = 0 );
+ };
+
+
diff -Nru liblastfm-1.0.9/debian/patches/series 
liblastfm-1.0.9/debian/patches/series
--- liblastfm-1.0.9/debian/patches/series   2015-11-20 16:42:23.0 
+0100
+++ liblastfm-1.0.9/debian/patches/series   2022-01-14 22:27:26.0 
+0100
@@ -1,2 +1,3 @@
 change_target-name.patch
 strip_README.patch
+fix_gcc11_ftbfs.patch

Bug#1003746: php-horde-imp: (autopkgtest) needs update for php8.1: Failed asserting that 'This action is not supported. horde.warning' contains "Reply Sent."

[Paul Gevers]

Source: php-horde-imp
Version: 6.2.27-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults
Control: block 976811 by -1

Dear maintainer(s),

[In contrast to horde bugs filed yesterday, this issue seems to really 
break functionality.]


We are in the transition of replacing php7.4 with php8.1 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-imp fails in 
testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing92
php-horde-imp  from testing6.2.27-2
versioned deps from testingfrom unstable
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 
7.4 and may help to identify what needs to be updated.


php-commom added a whole set of versioned Breaks to make sure the right 
packages from current unstable are pulled in during testing. If the 
issue is caused by a missing breaks, please reasign this bug to php-common.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-imp/18284144/log.gz

PHP Deprecated:  DateTime::__construct(): Passing null to parameter #1 
($datetime) of type string is deprecated in 
/usr/share/php/Horde/Date.php on line 558
PHP Deprecated:  DateTime::__construct(): Passing null to parameter #1 
($datetime) of type string is deprecated in 
/usr/share/php/Horde/Date.php on line 558
PHP Deprecated:  DateTime::__construct(): Passing null to parameter #1 
($datetime) of type string is deprecated in 
/usr/share/php/Horde/Date.php on line 558

F. 49 / 49 (100%)

Time: 00:00.086, Memory: 12.00 MB

There were 40 failures:

1) 
Imp_Unit_Mime_Viewer_ItipTest::testAcceptingAnInvitationResultsInReplySent
Failed asserting that 'This action is not supported. horde.warning' 
contains "Reply Sent.".


/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:235

2) 
Imp_Unit_Mime_Viewer_ItipTest::testAcceptingAnInvitationResultsInMimeMessageSent

Missing second message part!

/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617
/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:260

3) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageContainsProductId
Missing second message part!

/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617
/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:266

4) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageIndicatesMethodReply
Missing second message part!

/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617
/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:272

5) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageContainsVevent
Missing second message part!

/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617
/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:626
/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:278

6) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageContainsCopiedUid
Missing second message part!

/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617
/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:626
/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:284

7) Imp_Unit_Mime_Viewer_ItipTest::testResultMessageContainsCopiedSummary
Missing second message part!

/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:617
/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:626
/tmp/autopkgtest-lxc.mpr6l7on/downtmp/build.hGZ/src/imp-6.2.27/test/Imp/Unit/Mime/Viewer/ItipTest.php:304

8) 
Imp_Unit_Mime_Viewer_ItipTest::testResultMessageContainsEmptySummaryIfNotAvailable

Missing second message part!

Bug#1003090: RFS: ffcvt/1.7.5-1

[Tong Sun]

Trying again.

On Thu, Jan 6, 2022 at 1:16 PM Tong Sun
 wrote:
>
> On Mon, Jan 3, 2022 at 3:45 PM Tong Sun wrote:
> >
> > On Mon, Jan 3, 2022 at 3:20 PM Tong Sun
> >  wrote:
> > >
> > > Package: sponsorship-requests
> > > Severity: normal
> > >
> > > Dear mentors,
> > >
> > > I updated my ffcvt to a newer version, and am now looking for a sponsor.
> > >
> > > Here is from the d/changelog
> > >
> > > ffcvt (1.7.5-1) unstable; urgency=medium
> > >
> > >   * New upstream version 1.7.5
> > > - add --Speed for speeding up playback (v1.7.5)
> > > - add a copy target type that can speed up operations (v1.7.4)
> > > - add option -S,Seg -- split video into multiple segments (v1.7.3)
> > > - add option -sel, subtitle encoding language (v1.7.2)
> > > - add option -C which allows cutting multiple segments (v1.7.1)
> > > - add wx type for weixin (v1.7.0)
> > > - x264-mp3 type set ext to .mp4 (v1.6.2)
> > >   * fix "source: out-of-date-standards-version" problem
> > >   * fix "source: update-debian-copyright" problem
> > >   * fix "source: prefer-uscan-symlink filenamemangle" problem
> > >
> > > Note
> > >
> > > 1) My GPG key expired a few days ago, and I've already submit the
> > > update to keyring.debian.org, yet I understand it might take a while
> > > to really get updated, so please
> > >
> > > go directly to
> > > https://salsa.debian.org/go-team/packages/ffcvt/-/commits/master
> > >
> > > 2) Please disregard the .gitlab-ci.yml build failure as I'm not
> > > supposed to touch it.
> >
> > Ops, please hold off reviewing it, as I've found out where the problem
> > is -- ffcvt depends on the latest easygen to build yet I haven't
> > upgraded easygen in Debian yet. and my expired GPG key is preventing
> > me from fixing it promptly.
> >
> > Will update when the situation is fixed.
> >
> > Sorry & thanks
> >
> > > The build is fine, check out here --
> > > https://github.com/suntong/ffcvt/runs/4687405723?check_suite_focus=true
>
> Hi,
>
> The situation should have been fixed with the new upload of easygen.
>
> However, the CI build is still failing in salsa. This is something
> that I don't understand as it builds OK on github.
>
> Sorry I've run out of ideas why it is happening like this, and am now
> thinking to remove the build dependency of easygen, to fix this and to
> make things easier...

I still don't have a clue why it builds OK on github but fails in
salsa CI build, and I still hope that somebody can help.

I'll wait for one or two weeks more, and if still nobody can help,
I'll remove the build dependency of easygen as planned, as I know for
sure it can fix the issue.

> Somebody help please.

thanks

Bug#1003745: cmark-gfm: manpage is outdated: option --safe now fails with exitcode 1

[Jonas Smedegaard]

Package: cmark-gfm
Version: 0.29.0.gfm.0-6
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

manpage documents an option --safe.

Since release 0.28.3.gfm.18 that option does not exist,
and instead an option --unsafe is supported.

Please update manpage to reflect currently supported options.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHh6TgACgkQLHwxRsGg
ASGBJRAAqLjs4Lfw0I82I9G3MF4fhwfvYCK65OZXQCd3AdfxXV7hoUjIReLcG8m8
2toz63BbHGaO8IBBJqsXQkWDSSi2vXC/N5OC2PMYYN8GM8zFJYZkZvhVKomkTBsc
Dip2mb4LF0jpOpyEt2gLUDzbCT59l/Tg0VIoMmVWIu4lCkYqWrOtzg05YbokdIRW
ndVWT19eLfB8pH1s7RJwyuWtCwuiqzqxaBRfO031iRTP/zlPYOJJh3Q8ScbxQ6gl
n5qQ+171JcTFm76eYTkOkyvmpCXs7GpeFOWIj5wSRIeNNq7+b4iVqOIXlrA1wn4H
KZF4DEnTG5pN0VRFeCRMmhA4g5LW92GVY4+rmKc80Ng4mkr2/FrAFbxJCspgNUmE
YZZdCPHqeo0gckYJamfQP1DYhrWbGCtPrVuieyu+UFebr5q/tFam3p6ALeForwR3
kwU/ee03KC7vX+qGR0h+7sOol6pB8IELOL5LDi7Sz2E3/WPFmz+rrLYyScDeNbw8
3Gix3PdkmyYwuSTM2Q88a1N+J0uaNgtKBl1J00CHj4Qvv/MIloRSH+Aru3r+JADy
E/5WKx1iNDV37TFuW8EOG2PE3Z3A/uk7ACLot9HP+Ha4CHPVw1gQCbnMDaLRhiuw
1vt/Iy8O+ILAQEYQbvEDWNV9aSLyI/BDHPZw9+8bzyyvVLijrTE=
=nr7U
-END PGP SIGNATURE-

Bug#984014: clementine: ftbfs with GCC-11

[Florian Ernst]

forwarded 984014 https://github.com/clementine-player/Clementine/issues/6865
tags 984014 + patch
thanks

On Wed, Oct 27, 2021 at 11:05:04PM +0300, Alexander Kernozhitsky wrote:
> It's worth noting that the upstream has already fixed this bug:
>
> https://github.com/clementine-player/Clementine/commit/cfcd0a956e6758624fab0ff20aee9eb08b3df0b3

Indeed, and this is tracked in
https://github.com/clementine-player/Clementine/issues/6865 where that
patch is referenced.

FWIW, I can confirm that 1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1 still FTBFS
in the manner originally reported in this bug, but with the attached
debdiff implementing the fix from upstream I was able to build it again.

HTH, and please feel free to adjust to your liking.

Cheers,
Florian
diff -Nru clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
--- clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
2020-10-27 11:30:27.0 +0100
+++ clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/changelog
2022-01-14 21:44:24.0 +0100
@@ -1,3 +1,11 @@
+clementine (1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with GCC-11 by dropping -std=c++0x and -U__STRICT_ANSI__,
+patch taken from upstream. (Closes: #984014)
+
+ -- Florian Ernst   Fri, 14 Jan 2022 21:44:24 +0100
+
 clementine (1.4.0~rc1+git347-gfc4cb6fc7+dfsg-1) unstable; urgency=medium

   * New upstream snapshot.
diff -Nru 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/patches/fix_gcc11_ftbfs.patch
 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/patches/fix_gcc11_ftbfs.patch
--- 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/patches/fix_gcc11_ftbfs.patch
1970-01-01 01:00:00.0 +0100
+++ 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/debian/patches/fix_gcc11_ftbfs.patch
2022-01-14 21:44:24.0 +0100
@@ -0,0 +1,52 @@
+Description: Fix GCC-11 build issue
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984014
+Index: 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/ext/clementine-spotifyblob/CMakeLists.txt
+===
+--- 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg.orig/ext/clementine-spotifyblob/CMakeLists.txt
 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/ext/clementine-spotifyblob/CMakeLists.txt
+@@ -7,7 +7,7 @@ include_directories(${CMAKE_SOURCE_DIR}/
+ include_directories(${CMAKE_SOURCE_DIR}/ext/libclementine-common)
+ include_directories(${CMAKE_SOURCE_DIR}/src)
+
+-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Woverloaded-virtual -Wall 
-Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-local-typedefs 
-Wno-unused-private-field -Wno-unknown-warning-option --std=c++0x 
-U__STRICT_ANSI__")
++set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Woverloaded-virtual -Wall 
-Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-local-typedefs 
-Wno-unused-private-field -Wno-unknown-warning-option")
+
+ link_directories(${SPOTIFY_LIBRARY_DIRS})
+
+Index: 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/ext/clementine-tagreader/CMakeLists.txt
+===
+--- 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg.orig/ext/clementine-tagreader/CMakeLists.txt
 
clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/ext/clementine-tagreader/CMakeLists.txt
+@@ -7,7 +7,7 @@ include_directories(${CMAKE_BINARY_DIR}/
+ include_directories(${CMAKE_SOURCE_DIR}/src)
+ include_directories(${CMAKE_BINARY_DIR}/src)
+
+-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} --std=c++0x -U__STRICT_ANSI__")
++set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS}")
+
+ set(EXECUTABLE_OUTPUT_PATH ${CMAKE_BINARY_DIR})
+
+Index: clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/src/CMakeLists.txt
+===
+--- clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg.orig/src/CMakeLists.txt
 clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/src/CMakeLists.txt
+@@ -1,6 +1,6 @@
+
+ set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -Wall")
+-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Woverloaded-virtual -Wall 
-Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-local-typedefs 
--std=c++0x -U__STRICT_ANSI__")
++set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Woverloaded-virtual -Wall 
-Wno-sign-compare -Wno-deprecated-declarations -Wno-unused-local-typedefs")
+
+ option(BUILD_WERROR "Build with -Werror" ON)
+
+Index: clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/tests/CMakeLists.txt
+===
+--- clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg.orig/tests/CMakeLists.txt
 clementine-1.4.0~rc1+git347-gfc4cb6fc7+dfsg/tests/CMakeLists.txt
+@@ -1,6 +1,6 @@
+ cmake_minimum_required(VERSION 2.8.11)
+
+-set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++0x -fpermissive 
-Wno-c++11-narrowing -U__STRICT_ANSI__")
++set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -fpermissive -Wno-c++11-narrowing")
+

Bug#1003744: php-horde-crypt: (autopkgtest) needs update for php8.1: errorHandler(), 4 passed and exactly 5 expected

[Paul Gevers]

Source: php-horde-crypt
Version: 2.7.12-6
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:php-defaults
Control: block 976811 by -1

Dear maintainer(s),

[In contrast to earlier bugs filed, this issue seems to really break 
functionality.]


We are in the transition of replacing php7.4 with php8.1 [0]. With a 
recent upload of php-defaults the autopkgtest of php-horde-crypt fails 
in testing when that autopkgtest is run with the binary packages of 
php-defaults from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
php-defaults   from testing92
php-horde-cryptfrom testing2.7.12-6
versioned deps from testingfrom unstable
all others from testingfrom testing

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

Currently this regression is blocking the migration of php-defaults to 
testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 
7.4 and may help to identify what needs to be updated.


php-commom added a whole set of versioned Breaks to make sure the right 
packages from current unstable are pulled in during testing. If the 
issue is caused by a missing breaks, please reasign this bug to php-common.


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/php-horde-crypt/18284133/log.gz

PHP Deprecated:  Horde_Stream implements the Serializable interface, 
which is deprecated. Implement __serialize() and __unserialize() instead 
(or in addition, if support for old PHP versions is necessary) in 
/usr/share/php/Horde/Stream.php on line 27
PHP Deprecated:  Horde_Stream_Temp implements the Serializable 
interface, which is deprecated. Implement __serialize() and 
__unserialize() instead (or in addition, if support for old PHP versions 
is necessary) in /usr/share/php/Horde/Stream/Temp.php on line 23

PHPUnit 9.5.11 by Sebastian Bergmann and contributors.

Runtime:   PHP 8.1.1
Configuration: 
/tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/phpunit.xml


Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/Pgp/BinaryTest.php
   Class name was 'Horde_Crypt_Pgp_BinaryTest', expected 
'BinaryTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/PgpKeyserverTest.php
   Class name was 'Horde_Crypt_PgpKeyserverTest', expected 
'PgpKeyserverTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/PgpParseTest.php
   Class name was 'Horde_Crypt_PgpParseTest', expected 
'PgpParseTest'

Warning:   Test case class not matching filename is deprecated
   in 
/tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/test/Horde/Crypt/SmimeTest.php

   Class name was 'Horde_Crypt_SmimeTest', expected 'SmimeTest'

PHP Deprecated:  Function strftime() is deprecated in 
/tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php 
on line 247
PHP Deprecated:  Function strftime() is deprecated in 
/tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php 
on line 248
..PHP Deprecated:  Function strftime() is deprecated in 
/tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php 
on line 247
PHP Deprecated:  Function strftime() is deprecated in 
/tmp/autopkgtest-lxc.vs9_spwp/downtmp/build.e5w/src/Horde_Crypt-2.7.12/lib/Horde/Crypt/Pgp.php 
on line 247
.PHP Deprecated:  strlen(): Passing null to parameter #1 
($string) of type string is deprecated in /usr/share/php/Horde/Url.php 
on line 269
EPHP Deprecated:  strlen(): Passing null to parameter #1 ($string) of 
type string is deprecated in /usr/share/php/Horde/Url.php on line 269
EPHP Deprecated:  strlen(): Passing null to parameter #1 ($string) of 
type string is deprecated in /usr/share/php/Horde/Url.php on line 269
PHP Deprecated:  Return type of 
Horde_Support_CaseInsensitiveArray::offsetExists($offset) should either 
be compatible with ArrayIterator::offsetExists(mixed $key): bool, or the 
#[\ReturnTypeWillChange] attribute should be used to temporarily 
suppress the notice in 
/usr/share/php/Horde/Support/CaseInsensitiveArray.php on line 47
PHP Deprecated:  

Bug#1003743: glusterfs: incorrect /etc/default path

[Andreas Hasenack]

Package: glusterfs
Version: 10.0-2
Severity: normal

Dear Maintainer,

version 10.0-2 introduced the patch 03-systemd-environment-file.diff
which changes the glusterd systemd service file to source
/etc/default/glusterd. At the same time, it changes
debian/glusterfs-server.install to copy said file in place:
  debian/glusterfs-server.install:
  extras/glusterd-sysconfig etc/default/glusterd

This, however, produces /etc/default/glusterd/glusterd-sysconfig:

  # dpkg -L glusterfs-server | grep /etc/default/glusterd
  /etc/default/glusterd
  /etc/default/glusterd/glusterd-sysconfig


Here is a suggested fix (note the chmod +x debian/glusterfs-server.install):
diff --git a/debian/control b/debian/control
index 1799c61bd3..508cf2196b 100644
--- a/debian/control
+++ b/debian/control
@@ -26,6 +26,7 @@ Build-Depends: debhelper-compat (= 13),
  pkg-config,
  dh-python,
  dh-sequence-python3,
+ dh-exec,
  python3-dev
 Standards-Version: 4.6.0
 Rules-Requires-Root: no
diff --git a/debian/glusterfs-server.install b/debian/glusterfs-server.install
old mode 100644
new mode 100755
index 1afe46dfc1..cfd255bfc8
--- a/debian/glusterfs-server.install
+++ b/debian/glusterfs-server.install
@@ -1,7 +1,8 @@
+#!/usr/bin/dh-exec
 usr/sbin/glusterd
 usr/sbin/gluster-eventsapi
 usr/sbin/glustereventsd
-extras/glusterd-sysconfig etc/default/glusterd
+extras/glusterd-sysconfig => /etc/default/glusterd
 etc/glusterfs/glusterd.vol
 etc/glusterfs/gsyncd.conf
 etc/glusterfs/logger.conf.example

Bug#1003650: firejail-profiles: Chromium running under the current profile cannot play sound

[Reiner Herrmann]

Hi Mad Horse,

On Thu, Jan 13, 2022 at 05:07:38PM +0800, Mad Horse wrote:
> After upgraded to 97.0.4692.71-0.1, Chromium running inside firejail can no
> longer play sound (e.g. when playing an online video), while bare Chromium
> can. It is shown with PulseAudio Manager that the Chromium running inside
> firejail cannot connect to the sound server while the bare Chromium can.

I had a similar issue initially as well. But it turned out to be related
to my custom sound setup (using pipewire with run directory in ~/pipewire).
There are also no sound-related Chromium issue known in the upstream
firejail bug tracker.

So I think it also has to be related to your setup.
It might be related to some whitelist in the chromium{-common}.profile,
as this causes the parent directory to get blocked.
Can you please try to figure out which path needs to be whitelisted
on your system to get it working again?

Kind regards,
  Reiner


signature.asc
Description: PGP signature

Bug#1002298: bullseye-pu: package clamav/0.103.4+dfsg-0+deb11u1

[Sebastian Andrzej Siewior]

On 2022-01-12 20:44:46 [+0100], To Adam D. Barratt wrote:
> > I wasn't really sure which of the changes made sense to mention, but
> > had a go at an initial draft for an announcement. Tweaks, updates or
> > complete rewrites welcome:
> > 
> > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> > ClamAV is an AntiVirus toolkit for Unix.
> > 
> > Upstream published version 0.103.4.
> > 
> > This is a bug-fix release and an upstream LTS release. The changes are not
> > currently required for operation, but upstream strongly recommends that 
> > users
> > update.
> 
> Maybe adding something like
>   ", but upstream strongly recommends that users update for continued
>   support."
> 
> Upstream asks to use latest patch level version for support which
> includes access to the signature database.
> 
> Speaking of latest patch version: Upstream released today .5. Would you
> prefer to wait with this until I upload .5 to unstable and
> stable/oldstable for this (and avoiding a second announcement)?

I assume a direct update to .5 is preferred so I attached it here.
Regarding the wording: in [0] upstream says that they are going to
block 0.102 and earlier from database updates so we should be good. That
means they did not mention to block previous 0.103 releases so there is
probably no need to add stronger wording as I suggested.
The NEWS file mentions a CVE which looks harmless in typical mail server
setup since it requires an additional option for scanning.

I have it in unstable since the 12th and deployed the Buster version on
a server and had the regular testing for Bullseye.

[0] https://blog.clamav.net/2022/01/clamav-01035-and-01042-security-patch.html

> > Regards,
> > 
> > Adam

Sebastian
diff -Nru clamav-0.103.4+dfsg/clamav-milter/clamav-milter.c clamav-0.103.5+dfsg/clamav-milter/clamav-milter.c
--- clamav-0.103.4+dfsg/clamav-milter/clamav-milter.c	2021-11-02 16:47:46.0 +0100
+++ clamav-0.103.5+dfsg/clamav-milter/clamav-milter.c	2022-01-11 00:17:45.0 +0100
@@ -1,5 +1,5 @@
 /*
- *  Copyright (C) 2013-2021 Cisco Systems, Inc. and/or its affiliates. All rights reserved.
+ *  Copyright (C) 2013-2022 Cisco Systems, Inc. and/or its affiliates. All rights reserved.
  *  Copyright (C) 2008-2013 Sourcefire, Inc.
  *
  *  Author: aCaB 
@@ -96,7 +96,7 @@
 
 sigset_t sigset;
 struct sigaction act;
-const char * user_name = NULL;
+const char *user_name = NULL;
 
 cl_initialize_crypto();
 
@@ -122,7 +122,7 @@
 printf("\n");
 printf("   Clam AntiVirus: Milter Mail Scanner %s\n", get_version());
 printf("   By The ClamAV Team: https://www.clamav.net/about.html#credits\n;);
-printf("   (C) 2021 Cisco Systems, Inc.\n");
+printf("   (C) 2022 Cisco Systems, Inc.\n");
 printf("\n");
 printf("%s [-c ]\n\n", argv[0]);
 printf("\n");
@@ -158,7 +158,7 @@
 }
 free(pt);
 
-if ((opt = optget(opts, "User"))->enabled){
+if ((opt = optget(opts, "User"))->enabled) {
 user_name = opt->strarg;
 }
 
@@ -419,7 +419,7 @@
 if ((opt = optget(opts, "PidFile"))->enabled) {
 FILE *fd;
 mode_t old_umask = umask(0002);
-int err = 0;
+int err  = 0;
 
 if ((fd = fopen(opt->strarg, "w")) == NULL) {
 logg("!Can't save PID in file %s\n", opt->strarg);
@@ -434,14 +434,14 @@
 umask(old_umask);
 
 #ifndef _WIN32
-if (0 == err){
+if (0 == err) {
 /*If the file has already been created by a different user, it will just be
  * rewritten by us, but not change the ownership, so do that explicitly.
  */
-if (0 == geteuid()){
-struct passwd * pw = getpwuid(0);
-int ret = lchown(opt->strarg, pw->pw_uid, pw->pw_gid);
-if (ret){
+if (0 == geteuid()) {
+struct passwd *pw = getpwuid(0);
+int ret   = lchown(opt->strarg, pw->pw_uid, pw->pw_gid);
+if (ret) {
 logg("!Can't change ownership of PID file %s '%s'\n", opt->strarg, strerror(errno));
 err = 1;
 }
@@ -449,7 +449,7 @@
 }
 #endif /*_WIN32*/
 
-if (err){
+if (err) {
 localnets_free();
 whitelist_free();
 logg_close();
@@ -460,7 +460,7 @@
 
 #ifndef _WIN32
 dropPrivRet = drop_privileges(user_name, logg_file);
-if (dropPrivRet){
+if (dropPrivRet) {
 optfree(opts);
 return dropPrivRet;
 }
@@ -468,7 +468,7 @@
 /* We have been daemonized, and initialization is done.  Signal
  * the parent process so that it can exit cleanly.
  */
-if (parentPid != getpid()){ //we have been daemonized
+if (parentPid != getpid()) { //we have been daemonized
 daemonize_signal_parent(parentPid);
 }
 #endif
diff -Nru clamav-0.103.4+dfsg/clamd/clamd.c 

Bug#1003742: ocaml-ca-certs FTBFS on bytecode architectures

[Adrian Bunk]

Source: ocaml-ca-certs
Version: 0.2.2-1
Severity: important
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=ocaml-ca-certs=0.2.2-1

...
   dh_missing -a
dh_missing: warning: usr/lib/ocaml/ca-certs/libca_certs_stubs.a exists in 
debian/tmp but is not installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: libca-certs-ocaml (3), libca-certs-ocaml-dev (7)
 * dh_installdocs: libca-certs-ocaml (0), libca-certs-ocaml-dev (2)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:8: binary-arch] Error 25

Bug#1003737: tech-ctte: Call for votes on TC membership of Helmut Grohne

[Sean Whitton]

On Fri 14 Jan 2022 at 11:55AM -07, Sean Whitton wrote:

> ===BEGIN
> The Technical Committee recommends that Helmut Grohne  be
> appointed by the Debian Project Leader to the Technical Committee.
>
> H: Recommend to Appoint Helmut Grohne 
> F: Further Discussion
> ===END

I vote

H > F

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1003738: tech-ctte: Call for votes on TC membership of Matthew Vernon

[Sean Whitton]

On Fri 14 Jan 2022 at 11:56AM -07, Sean Whitton wrote:

> ===BEGIN
> The Technical Committee recommends that Matthew Vernon  be
> appointed by the Debian Project Leader to the Technical Committee.
>
> H: Recommend to Appoint Matthew Vernon 
> F: Further Discussion
> ===END

I vote

H > F

(Sorry for copy/pasting the wrong initial, Matthew!)

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1003741: ocaml-conduit FTBFS on bytecode architectures

[Adrian Bunk]

Source: ocaml-conduit
Version: 4.0.2-2
Severity: important
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=ocaml-conduit=4.0.2-2

...
   dh_install -a
dh_install: warning: Cannot find (any matches for) "/usr/lib/ocaml/conduit/*.a" 
(tried in ., debian/tmp)

dh_install: warning: libconduit-ocaml-dev missing files: 
/usr/lib/ocaml/conduit/*.a
dh_install: warning: Cannot find (any matches for) "/usr/lib/ocaml/*lwt*/*.a" 
(tried in ., debian/tmp)

dh_install: warning: libconduit-lwt-ocaml-dev missing files: 
/usr/lib/ocaml/*lwt*/*.a
dh_install: error: missing files, aborting
make: *** [debian/rules:9: binary-arch] Error 25

Bug#1003430: gkrellm-leds: reproducible-builds: /bin/sh dependent behavior in Makefile

[Christoph Biedl]

Control: tags 1003430 pending

Vagrant Cascadian wrote...

> The path that gkrellm-leds installs plugins into differs depending on
> weather /bin/sh points to bash or dash:
> 
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/gkrellm-leds.html

Ups. Thanks for spotting this. Will be fixed in the next upload which
might take some time. Ping me if you want that story resolved faster.

Christoph


signature.asc
Description: PGP signature

Bug#912836: closed by Debian FTP Masters (reply to Christoph Biedl ) (Bug#912836: fixed in gkrellm-leds 0.8.0-2)

[Christoph Biedl]

Control: tags 912836 pending
Control: tags 914827 pending

Helmut Grohne wrote...

> Not quite. Please also apply the other half of the patch:

Yeah, noticed too late something was missing. Will be part of the
next upload which might take some time. Ping me if you want that
story resolved faster.

Christoph


signature.asc
Description: PGP signature

Bug#1003740: RM: abyss [armel armhf hppa i386 m86k mipsel sh4 x32] -- ROM; Upstream droped support for 32 bit architectures

[Andreas Tille]

Package: ftp.debian.org
Severity: normal

Hi,

upstream droped support for 32 bit architectures.  Thus I've set

   Architecture: any-amd64 arm64 mips64el ppc64el s390x ia64 ppc64 riscv64 
sparc64 alpha

in latest upload of version 2.3.4+dfsg-1.  Please remove the other
architectures to enable testing migration.

Thanks a lot for working as ftpmaster

  Andreas.

Bug#1003739: O: waylandpp -- wayland compositor infrastructure - C++ bindings

[Bálint Réczey]

Package: wnpp
Severity: normal

Orphaning the package.

Thanks,
Balint

Bug#1003738: tech-ctte: Call for votes on TC membership of Matthew Vernon

[Christoph Berg]

> ===BEGIN
> The Technical Committee recommends that Matthew Vernon  be
> appointed by the Debian Project Leader to the Technical Committee.
> 
> H: Recommend to Appoint Matthew Vernon 
> F: Further Discussion
> ===END

I vote M = H > F.

Christoph


signature.asc
Description: PGP signature

Bug#1003737: tech-ctte: Call for votes on TC membership of Helmut Grohne

[Christoph Berg]

Re: Sean Whitton
> ===BEGIN
> The Technical Committee recommends that Helmut Grohne  be
> appointed by the Debian Project Leader to the Technical Committee.
> 
> H: Recommend to Appoint Helmut Grohne 
> F: Further Discussion
> ===END

I vote H > F.

Christoph


signature.asc
Description: PGP signature

Bug#1003738: tech-ctte: Call for votes on TC membership of Matthew Vernon

[Sean Whitton]

Package: tech-ctte
X-debbugs-cc: matt...@debian.org, lea...@debian.org

I call for votes on the following ballot to fill a vacant seat on the
Debian Technical Committee.  The voting period starts immediately and
lasts for up to one week, or until the outcome is no longer in doubt.

===BEGIN
The Technical Committee recommends that Matthew Vernon  be
appointed by the Debian Project Leader to the Technical Committee.

H: Recommend to Appoint Matthew Vernon 
F: Further Discussion
===END

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive

[Paul Gevers]

Hi,

On 14-01-2022 13:06, Sebastian Ramacher wrote:

The ocaml dependencies are installable again after a round of binNMUs.
guestfs-tools however fails almost everywhere:
https://buildd.debian.org/status/package.php?p=guestfs-tools


A new upload fixed most of that, it failed on arm64 (and not yet built 
on mips*el).


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003727: debian-edu-config: exim4 on TJENER does not accept system mails from Debian Edu clients

[Petter Reinholdtsen]

[Mike Gabriel]
> @Petter: btw, do you have an idea, why things fail on a Debian Edu  
> bullseye TJENER? My exim4 competence is zero. Postfix would be easy.  
> Some help is much appreciated.

No idea, too long since I looked at SMTP stuff. :)
-- 
Happy hacking
Petter Reinholdtsen

Bug#1003737: tech-ctte: Call for votes on TC membership of Helmut Grohne

[Sean Whitton]

Package: tech-ctte
X-debbugs-cc: hel...@subdivi.de, lea...@debian.org

I call for votes on the following ballot to fill a vacant seat on the
Debian Technical Committee.  The voting period starts immediately and
lasts for up to one week, or until the outcome is no longer in doubt.

===BEGIN
The Technical Committee recommends that Helmut Grohne  be
appointed by the Debian Project Leader to the Technical Committee.

H: Recommend to Appoint Helmut Grohne 
F: Further Discussion
===END

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1003020: openblas breaks hypre autopkgtest on armhf: test times out after 2:47h

[Paul Gevers]

Hi,

On 14-01-2022 18:16, Drew Parsons wrote:
The passing machine was ci-worker-armel-01, but it was also the host for 
failing tests.  So it's not a simple as some difference between 
different CPU variants of armhf.


We only have one host for our armhf testing. (We did change host in the 
middle of 2021).


If I can be of any help, I can try to run explicitly given commands in 
or extract information from the testbed of a (passing) test run (I'm not 
sure if I can do the same from a failing test as that may be shortcutted 
somehow, but I can try).


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1003736: chromium: Casting via website provided app causes crash

[Kyle Robbertze]

Package: chromium
Version: 97.0.4692.71-0.1
Severity: normal

Dear Maintainer,

When casting a webpage to a Chromecast, Chromium crashes with the
following error:

free(): double free detected in tcache 2
[0114/193804.521131:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[2928:2948:0114/193804.608997:ERROR:broker_posix.cc(40)] Recvmsg error: 
Connection reset by peer (104)
fish: Job 1, 'chromium' terminated by signal SIGABRT (Abort)

This is a new issue since the last update to unstable. Casting the tab
works, however using the website-provided app triggers the crash. It can
be replicated by opening a YouTube video, click on the cast icon and select
a Chromecast. It will crash after connecting (i.e. YouTube's dashboard
is displayed on the TV) while trying to start playing the video.

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

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

Versions of packages chromium depends on:
ii  chromium-common 97.0.4692.71-0.1
ii  libasound2  1.2.6.1-1
ii  libatk-bridge2.0-0  2.38.0-2
ii  libatk1.0-0 2.36.0-3
ii  libatomic1  11.2.0-13
ii  libatspi2.0-0   2.42.0-2
ii  libc6   2.33-2
ii  libcairo2   1.16.0-5
ii  libcups22.3.3op2-7
ii  libdbus-1-3 1.12.20-3
ii  libdrm2 2.4.109-2
ii  libevent-2.1-7  2.1.12-stable-1
ii  libexpat1   2.4.2-1
ii  libflac81.3.3-2
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.11.1+dfsg-1
ii  libgbm1 21.3.3-1
ii  libgcc-s1   11.2.0-13
ii  libglib2.0-02.70.2-1
ii  libharfbuzz0b   2.7.4-1
ii  libicu6767.1-7
ii  libjpeg62-turbo 1:2.1.2-1
ii  libjsoncpp251.9.5-2
ii  liblcms2-2  2.12~rc1-2
ii  libminizip1 1.1-8+b1
ii  libnspr42:4.32-3
ii  libnss3 2:3.73.1-1
ii  libopenjp2-72.4.0-3
ii  libopus01.3.1-0.1
ii  libpango-1.0-0  1.48.10+ds1-1
ii  libpng16-16 1.6.37-3
ii  libpulse0   15.0+dfsg1-3
ii  libre2-920211101+dfsg-1
ii  libsnappy1v51.1.8-1
ii  libstdc++6  11.2.0-13
ii  libwebp60.6.1-2.1
ii  libwebpdemux2   0.6.1-2.1
ii  libwebpmux3 0.6.1-2.1
ii  libx11-62:1.7.2-2+b1
ii  libxcb1 1.14-3
ii  libxcomposite1  1:0.4.5-1
ii  libxdamage1 1:1.1.5-2
ii  libxext62:1.3.4-1
ii  libxfixes3  1:5.0.3-2
ii  libxkbcommon0   1.3.1-1
ii  libxml2 2.9.12+dfsg-5+b1
ii  libxrandr2  2:1.5.2-1
ii  libxslt1.1  1.1.34-4
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium recommends:
ii  chromium-sandbox  97.0.4692.71-0.1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  libc6   2.33-2
ii  libstdc++6  11.2.0-13
ii  libx11-62:1.7.2-2+b1
ii  libxext62:1.3.4-1
ii  x11-utils   7.7+5
ii  xdg-utils   1.1.3-4.1
ii  zlib1g  1:1.2.11.dfsg-2

Versions of packages chromium-common recommends:
ii  chromium-sandbox97.0.4692.71-0.1
ii  dunst [notification-daemon] 1.5.0-1+b1
ii  fonts-liberation1:1.07.4-11
ii  libgl1-mesa-dri 21.3.3-1
ii  libu2f-udev 1.1.10-3
ii  mako-notifier [notification-daemon] 1.6-2
ii  plasma-workspace [notification-daemon]  4:5.23.5-1
ii  system-config-printer   1.5.14-1
ii  upower  0.99.13-1

Versions of packages chromium-sandbox depends on:
ii  libc6  2.33-2

-- no debconf information

Bug#1003735: ITP: dnswire -- DNS encapsulations and transporting

[Daniel Baumann]

Package: wnpp

  * Package name : dnswire
  * Upstream Author : DNS-OARC (https://www.dns-oarc.net)
  * License : LGPL-3+
  * Homepage : https://github.com/DNS-OARC/dnswire

dnswire is a C library for encoding/decoding different DNS 
encapsulations and transporting them over different protocols.


Regards,
Daniel

Bug#1003546: ncurses: rin@ patch for screen-256color superfluous for this release cycle?

[Sven Joachim]

On 2022-01-11 19:16 +0100, наб wrote:

> Source: ncurses
> Version: 6.3-1
> Severity: minor
>
> Dear Maintainer,
>
> I was reading through the patches, when I noticed
> debian/patches/02-debian-drop-rin-from-screen-256color.diff,
> which reads:
>   Description: Remove "rin" from screen-256color
>[...] So drop "rin" from screen-256color, at least until tmux
>3.0 is released.
>   Bug-Debian: https://bugs.debian.org/933572
>   Last-Update: 2019-09-06
>
> It's been two years since then, during which bullseye dropped;
> according to packages.d.o, tmux 3 is available for every codename since
> bullseye, and even exists in buster-backports.
>
> In #933572, no-one seems to have noted any objections, and all upstream
> issues with "rin" in seem to be closed.
> Perhaps it's time to drop this patch?

There is still the possibility that someone remotely connects to a
Debian system running an older tmux on their host.  But that is probably
not such a common use case, and I guess we can tell these users to set
their TERM variable to something else than screen-256color if for some
reason they cannot upgrade their tmux version.

I intend to drop this patch in the next upload, thanks for the
suggestion.

Cheers,
   Sven

Bug#1003734: ITP: libcrypt-bcrypt-perl -- modern bcrypt implementation

[gregor herrmann]

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

* Package name: libcrypt-bcrypt-perl
  Version : 0.005
  Upstream Author : Leon Timmermans 
* URL : https://metacpan.org/release/Crypt-Bcrypt
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : modern bcrypt implementation

Crypt::Bcrypt provides a modern and user-friendly implementation of the
bcrypt password hash.

Note that in bcrypt passwords may only contain 72 characters. It may seem
tempting to prehash the password before bcrypting it but that may make it
vulnerable to password shucking, a salted solution (for example using a MAC)
should be used instead if one wants to support large passwords.

The password is always expected to come as a (utf8-encoded) byte-string.

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#1003020: openblas breaks hypre autopkgtest on armhf: test times out after 2:47h

[Drew Parsons]

On 2022-01-14 14:50, Sébastien Villemot wrote:

Le dimanche 02 janvier 2022 à 21:19 +0100, Paul Gevers a écrit :


With a recent upload of openblas the autopkgtest of hypre fails in
testing when that autopkgtest is run with the binary packages of
openblas from unstable on armhf due to a timeout after 2:47 h. It 
passes

when run with only packages from testing in about 9-12 minutes. In
tabular form:

passfail
openblas   from testing0.3.19+ds-1
hypre  from testing2.22.1-3
all others from testingfrom testing

...

First note that there has been no change to the ARM32-specific code of
openblas between 0.3.18+ds-1 and 0.3.19+ds-1.

Also, I tried to replicate the problem on a porterbox (abel), but the
autopkgtest succeeds (with hypre 2.22.1-3 and openblas 0.3.19+ds-2, in
an armhf chroot):

...

So at this point I don’t know how to tackle this issue.

Drew, any idea?



No clear ideas at this point.  I ran a battery of tests on debci.  One 
armhf test passed on unstable, but 10 or so failed. So there's some 
random irreproducibility of the problem.


The passing machine was ci-worker-armel-01, but it was also the host for 
failing tests.  So it's not a simple as some difference between 
different CPU variants of armhf.


There's a new version waiting in NEW (actually there are 2 versions 
waiting in NEW). There's not much more constructive testing I can do 
until they get processed. Once they're cleared we'll be able to compare 
the new version from experimental.


Drew

Bug#980443: dovecot-imapd: segfault at 8 ip 000055c38b20f97c sp 00007ffe4baaaa40 error 4 in imap[55c38b1f7000+24000]

[Pierre Bernhardt]

On Tue, 19 Jan 2021 09:28:58 +0100 Simon Josefsson  
wrote:> Package: dovecot-imapd
> Version: 1:2.3.4.1-5+deb10u5
>
> Hi.  I noticed the following in my log recently.  Any ideas?
>
> Jan  6 14:55:54 uggla kernel: [145284.855936] imap[18530]: segfault at 8 ip 
55c38b20f97c sp 7ffe4b40 error 4 in imap[55c38b1f7000+24000]
> Jan  6 14:55:54 uggla kernel: [145284.855945] Code: 5d 41 5c 41 5d e9 2b ca fe ff 
0f 1f 40 00 45 89 ec 48 89 df 48 39 eb 75 bd 48 8b 45 00 48 8d 35 da f4 00 00 41 bc ff 
ff ff ff <48> 8b 78 08 e8 8b 77 ff ff 48 83 c4 08 44 89 e0 5b 5d 41 5c 41 5d
> Jan  6 14:55:54 uggla dovecot: imap(simon)<18530><7bj6fTy4vsof0Co6>: Fatal: 
master: service(imap): child 18530 killed with signal 11 (core dumps disabled - 
https://dovecot.org/bugreport.html#coredumps)
Same here if found on my console, today:

[2592106.354939] imap[27643]: segfault at 8 ip 56014e2b297c sp 
7ffee6f53280 error 4 in imap[56014e29a000+24000]
[2592106.354958] Code: 5d 41 5c 41 5d e9 2b ca fe ff 0f 1f 40 00 45 89 ec 48 89 df 48 
39 eb 75 bd 48 8b 45 00 48 8d 35 da f4 00 00 41 bc ff ff ff ff <48> 8b 78 08 e8 
8b 77 ff ff 48 83 c4 08 44 89 e0 5b 5d 41 5c 41 5d

> The 1:2.3.4.1-5+deb10u5 packages were installed on 2021-01-04:
Mine is:
[2592106.354939] imap[27643]: segfault at 8 ip 56014e2b297c sp 
7ffee6f53280 error 4 in imap[56014e29a000+24000]
[2592106.354958] Code: 5d 41 5c 41 5d e9 2b ca fe ff 0f 1f 40 00 45 89 ec 48 89 df 48 
39 eb 75 bd 48 8b 45 00 48 8d 35 da f4 00 00 41 bc ff ff ff ff <48> 8b 78 08 e8 
8b 77 ff ff 48 83 c4 08 44 89 e0 5b 5d 41 5c 41 5d

The second line matches with the message above.

Now I set ALLOW_COREDUMPS=1 to get coredump next time, hopefully.

Cheers,
Pierre

Bug#995616: dh-make: create debian/upstream/medatada template

[Agathe Porte]

Hi,

On Tue, 12 Oct 2021 19:16:33 +0200 Romain Porte  wrote:

> Hi,
>
> 12/10/2021 05:49, Craig Small :
> > Hi,
> >   I tried looking at http://upstream-metadata.debian.net/
>  but its down, is this a 
current need?

>
> For the website being down, see:
> https://lists.debian.org/debian-qa/2014/06/msg00022.html
>
> This is mentioned at the top of the wiki page [1]:
>
> > Help! there is a bug that I do not manage to solve by myself. -- 
Charles

>
> The requirement is still there and independent of the website working or
> not in my opinion: lintian will check for it, and DDs will also check
> for its presence during code review of packages from mentorees (my
> case). Adding debian-qa in Cc of this answer if further clarification is
> needed.
>
> [1] https://wiki.debian.org/UpstreamMetadata

Any news about this issue? As quoted above, this feature is needed even 
if the mentioned website is down.


Bests

Bug#906149: Confirmation

[Nicola Mingotti]

On Tue, 04 Feb 2020 18:38:23 -0800 aidan.sojour...@gmail.com wrote:
> Can confirm that this bug still exists in version 3.2.5-1.3+b2
>
>
>

the Bug still exists today in Debian Stable Bullseye and makes the 
software unusable unfortunately.


$> apt-cache show gnu-smalltal

Source: gnu-smalltalk (3.2.5-1.3)
Version: 3.2.5-1.3+b2
...


$> gst
GNU Smalltalk ready

st> 12.12
Object: 1 error: The program attempted to divide a number by zero
ZeroDivide(Exception)>>signal (ExcHandling.st:254)
SmallInteger(Number)>>zeroDivide (SysExcept.st:1426)

hope it can be fixed.

bye
Nicola


--

---
Dr. Phd. Nicola Mingotti
Systems & New Technologies
Borghi Srl
---

--



Borghi s.r.l.
Via Paradello, 7 - 45037 Melara (Ro) Italy
Tel. +39 0425 
89689 - Fax +39 0425 89636
e-mail: i...@borghigroup.it 
 web: www.borghigroup.it 




*Il contenuto di questa comunicazione ha 
natura riservata ed è destinato esclusivamente alla persona o ente cui essa 
è indirizzata.
Qualsiasi forma di utilizzo non autorizzato del contenuto di 
questo messaggio non è consentito. Se non siete il destinatario designato 
di questo messaggio e del suo contenuto siete tenuti a comunicarlo 
immediatamente al mittente e di distruggere il messaggio ed i suoi 
eventuali allegati.


This comunication is confidential and intended for the 
addressee(s) only. Any form of unauthorized use of the content of this 
e-mail is not permitted. If you are not the intended recipent of this 
message and its contents, please notify the sender immediately and delete 
this message and all its attachments.*

Bug#1001466: [Pkg-dpdk-devel] Bug#1001466: uhd: FTBFS with DPDK LTS 21.11

[Luca Boccassi]

Control: tags -1 patch

On Fri, 2021-12-10 at 16:32 +, Luca Boccassi wrote:
> Source: uhd
> Version: 4.1.0.4-7
> Severity: normal
> Tags: ftbfs experimental
> X-Debbugs-Cc: pkg-dpdk-de...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> DPDK LTS 21.11 is now available in experimental, and we'd like to start
> the transition sometimes in February. During a rebuild of the reverse
> build-deps, we noticed uhd fails to build. The error is inlined below.
> You can reproduce it by installing libdpdk-dev from experimental.
> 
> It would be great if this could be fixed in the next couple of months.
> 
> Thank you!

Fix forwarded upstream and backported, MR open on Salsa:

https://salsa.debian.org/bottoms/pkg-uhd/-/merge_requests/1

I will do an NMU on Monday to unblock our progress on updating DPDK
unless there are any objections. Thanks!

-- 
Kind regards,
Luca Boccassi


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

Bug#941480: Please package the new version of mediathekview

[Oswald Buddenhagen]

two+ more years later, current version is 13.8.1, build system is still 
maven-based.

Bug#1003733: ITP: tinyframe -- Minimalistic Frame Streams library

[Daniel Baumann]

Package: wnpp

  * Package name : dnsmeter
  * Upstream Author : DNS-OARC (https://www.dns-oarc.net)
  * License : LGPL-3+
  * Homepage : https://github.com/DNS-OARC/tinyframe

tinyframe is a minimalistic library for reading and writing the Frame 
Streams protocol.


Regards,
Daniel

Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))

[YunQiang Su]

在 2022/1/14 23:30, Sandro Tosi 写道:

On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su  wrote:


On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel
 wrote:
  > Built with gcc-11 and -fno-lto it doesn not work.
  >
  >
(sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$
../../../test.py
  > Segmentation fault
  >
(sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$
PYTHONPATH=. ../../../test.py
  > Segmentation fault
  >
  >

It seems due to gcc-11.

I tried to build with gcc-10 on sid, it works again.


yes, that's what PICCA found and reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72

are you going to look into a fix for gcc-11?



Sure, I will dig it, since it may effect lots of other packages.


Thanks,

Bug#1003108: Dependency on python3-cachecontrol has an odd alternative

[Sandro Tosi]

> python3-cachecontrol (>= 0.12.6) | python3 (>> 3.6)
>
> So, python3-cachecontrol don't get installed. Dunno who is generating
> this dependency. Checked cachecontrol repository, but nothing odd
> here. And in dh-python, nothing odd here either.

it's coming from
https://salsa.debian.org/python-team/packages/poetry/-/blob/debian/master/pyproject.toml#L34-37
but it sounds like that is not parsed properly, either by poetry or
dh-python

Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))

[Sandro Tosi]

On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su  wrote:
>
> On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel
>  wrote:
>  > Built with gcc-11 and -fno-lto it doesn not work.
>  >
>  >
> (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$
> ../../../test.py
>  > Segmentation fault
>  >
> (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$
> PYTHONPATH=. ../../../test.py
>  > Segmentation fault
>  >
>  >
>
> It seems due to gcc-11.
>
> I tried to build with gcc-10 on sid, it works again.

yes, that's what PICCA found and reported at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72

are you going to look into a fix for gcc-11?

Thanks,
-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#1003732: node-duration: Package node-duration isn't published in js-team repo

[Yadd]

Package: node-duration
Severity: important

Package node-duration is marked as owned by JS Team but not available in
JS Team salsa area. It shouldn't owned JS-Team in this case.

Bug#896946: ITP: cplay-ng -- Curses front-end for various audio

[Nilson Silva]

I talked with Diego Sarzi and he doesn't have interest in packaging this 
package.
Regards.


Nilson F. Silva

Bug#896946: ITP: cplay-ng -- Curses front-end for various audio

[Nilson Silva]

I talked with Diego Sarzi and he doesn't have interest in packaging this 
package.
Regards.

Nilson F. Silva

Bug#1003344: restfuldb: FTBFS with SQLite3 3.37.0+

[Andrius Merkys]

Hi,

On 2022-01-08 19:46, László Böszörményi (GCS) wrote:
> SQLite3 3.37.0 and onwards changed its inner working. Now table column
> data types are stored as a value and always returned as uppercase
> text. This breaks your package as it relies on the old behavior, when
> this was stored as text and returned in a case it was defined.
> As I broke it, I've created a fix for you, patch is attached. Couldn't
> make it work with older SQLite3 versions thus you will need to build
> depend on SQLite3 3.37.0 and newer.

Thanks a lot for the patch. Since I am one of the upstream developers I
will see how this could be fixed upstream. My priority would be to
support both SQLite3 << 3.37.0 and >= 3.37.0, but I can see that for
Debian your patch is sufficient.

> Sorry for the inconvenience,

No problem, such breakages sometimes happen with dependency updates.

Thanks,
Andrius

Bug#632960: bluetooth: Bluetoothd dies after restoring from hibernate PM

[brambil]

During boot I have this message:
[    5.691087] Bluetooth: hci0: unexpected event for opcode 0xfc2f

When bluetooth end to work the only solution is to reboot. If during the 
boot there is the error bluetooth works, if error doesn't appear the 
bluetooth will not work and the possible solutions are:
- Enter in BIOS, disable all wifi chips, reboot, reboot entering bios, 
enable wifi, reboot and bluetooth works until first power save.
- Reboot in Windows, make logon in windows, connect a bluetooth device 
(in my case, the mouse), reboot in linux.


This is the dmesg of a boot with working bluetooth:
root@lenovo:/home/nicola# dmesg | grep Bluetooth
[    5.001610] Bluetooth: Core ver 2.22
[    5.001646] Bluetooth: HCI device and connection manager initialized
[    5.001650] Bluetooth: HCI socket layer initialized
[    5.001653] Bluetooth: L2CAP socket layer initialized
[    5.001658] Bluetooth: SCO socket layer initialized
[    5.248726] Bluetooth: hci0: Legacy ROM 2.5 revision 1.0 build 3 week 
17 2014
[    5.249164] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq

[    5.303813] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.303817] Bluetooth: BNEP filters: protocol multicast
[    5.303821] Bluetooth: BNEP socket layer initialized
[    5.691087] Bluetooth: hci0: unexpected event for opcode 0xfc2f
[    5.709161] Bluetooth: hci0: Intel BT fw patch 0x32 completed & activated
[    9.179064] Bluetooth: RFCOMM TTY layer initialized
[    9.179081] Bluetooth: RFCOMM socket layer initialized
[    9.179088] Bluetooth: RFCOMM ver 1.11


This is the dmesg of a boot with Bluetooth not working:

gen 14 15:37:59 lenovo kernel: Bluetooth: Core ver 2.22
gen 14 15:37:59 lenovo kernel: Bluetooth: HCI device and connection 
manager initialized

gen 14 15:37:59 lenovo kernel: Bluetooth: HCI socket layer initialized
gen 14 15:37:59 lenovo kernel: Bluetooth: L2CAP socket layer initialized
gen 14 15:37:59 lenovo kernel: Bluetooth: SCO socket layer initialized
gen 14 15:38:00 lenovo kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
gen 14 15:38:00 lenovo kernel: Bluetooth: BNEP filters: protocol multicast
gen 14 15:38:00 lenovo kernel: Bluetooth: BNEP socket layer initialized
gen 14 15:38:02 lenovo kernel: Bluetooth: hci0: Reading Intel version 
command failed (-110)

gen 14 15:38:02 lenovo kernel: Bluetooth: hci0: command tx timeout




-- Original Message --
From: Nicola 
To: Debian Bug Tracking System <632...@bugs.debian.org>
Date: Fri, 14 Jan 2022 12:39:27 +0100
M-ID: 
<164216036710.35866.5086530836768427074.report...@lenovo.homenet.telecomitalia.it>
Subject: Bug#632960: bluetooth: Bluetoothd dies after restoring from 
hibernate PM



Package: bluetooth
Version: 5.62-2
Followup-For: Bug #632960

Dear Maintainer,
Same situation.

When any powerreduce act (p.e. display shutoff) the Bluetooth goes off, as
WiFi, but on resume WiFi restarts normally, bluetooth no.
bluetoothctl reports no controller on list command.
blueman fails to start.
blueman-adapters 12.39.01 ERRORAdapter:54 __init__  : No adapter(s) found

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

* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
  ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?

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


-- System Information:
Debian Release: bookworm/sid
   APT prefers testing
   APT policy: (950, 'testing'), (400, 'unstable'), (300, 'experimental'), (10, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 bluetooth depends on:
ii  bluez  5.62-2

bluetooth recommends no packages.

Versions of packages bluetooth suggests:
pn  bluez-cups   
pn  bluez-meshd  
ii  bluez-obexd  5.62-2

-- no debconf information



P
Please consider the enviroment before printing.
Pensa all'ambiente prima di stampare.

This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error please notify the 
originator of the message. Any views expressed in this message are those 
of the individual sender. This footer also confirms that this email 
message has been scanned for the presence of computer viruses.

Bug#1003727: debian-edu-config: exim4 on TJENER does not accept system mails from Debian Edu clients

[Petter Reinholdtsen]

[Mike Gabriel]
> When a client on the Debian Edu network (.intern, 10.0.0.0/8) tries to send
> system mails to postoffice.intern aka TJENER, then exim4 on TJENER won't
> accept these SMTP connects without proper authentication:

[Holger Levsen]
> and how is this a serious bug in debian-edu-config?

Because it fill up /var/, breaking the system completely for everyone?

-- 
Vennlig hilsen
Petter Reinholdtsen

Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))

[YunQiang Su]

On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel 
 wrote:

> Built with gcc-11 and -fno-lto it doesn not work.
>
> 
(sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ 
../../../test.py

> Segmentation fault
> 
(sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ 
PYTHONPATH=. ../../../test.py

> Segmentation fault
>
>

It seems due to gcc-11.

I tried to build with gcc-10 on sid, it works again.

Bug#1001147: syncthing.service appears to be enabled for all users

[Brendon Higgins]

Hi,

I just noticed the symptoms of this on my own system. Does every installation 
affected by this bug need manual intervention to undo the automatically-enabled 
user unit, or should the fixed package do that itself? If the former, for those 
not familiar (myself included), could you suggest the appropriate incantation 
to remove the user unit?

Thanks,
Brendon

Bug#1003731: linux-base:[INTL:fr] updated French man page translation

[bubub]

Package: linux-base
Version: 4.6
Severity: wishlist
Tags: patch l10n

Dear mainteners,
Please find the updated french translation for linux-base attached,
proofread by the debian-l10n-french mailing list contributors.

This file should be put as debian/po/fr.po in your package build tree.

Kind Regards

x

linux-base_4.6_fr.po.xz
Description: application/xz

Bug#998018: atril: does not support PDF bookmarks encoded in UTF-16

[Vincent Lefevre]

On 2021-10-28 17:44:43 +0200, Vincent Lefevre wrote:
> Most bookmarks from
> 
>   http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2731.pdf
> 
> appear as "þÿ" (see attached png file), which is actually
> U+FEFF ZERO WIDTH NO-BREAK SPACE, i.e. the BOM in UTF-16BE,
> interpreted as ISO-8859-1.

According to https://bugzilla.mozilla.org/show_bug.cgi?id=1750123
(as Firefox has a similar issue), the bug would be in the PDF file.

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

Bug#1003020: openblas breaks hypre autopkgtest on armhf: test times out after 2:47h

[Sébastien Villemot]

Hi,

Le dimanche 02 janvier 2022 à 21:19 +0100, Paul Gevers a écrit :
> Source: openblas, hypre
> Control: found -1 openblas/0.3.19+ds-1
> Control: found -1 hypre/2.22.1-3
> Severity: serious
> Tags: sid bookworm
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: breaks needs-update
> 
> With a recent upload of openblas the autopkgtest of hypre fails in 
> testing when that autopkgtest is run with the binary packages of 
> openblas from unstable on armhf due to a timeout after 2:47 h. It passes 
> when run with only packages from testing in about 9-12 minutes. In 
> tabular form:
> 
> passfail
> openblas   from testing0.3.19+ds-1
> hypre  from testing2.22.1-3
> all others from testingfrom testing
> 
> I copied some of the output at the bottom of this report, but as the 
> test times out, I suspect it just hangs and there's not much useful to see.
> 
> Currently this regression is blocking the migration of openblas to 
> testing [1]. Due to the nature of this issue, I filed this bug report 
> against both packages. Can you please investigate the situation and 
> reassign the bug to the right package?

First note that there has been no change to the ARM32-specific code of
openblas between 0.3.18+ds-1 and 0.3.19+ds-1.

Also, I tried to replicate the problem on a porterbox (abel), but the
autopkgtest succeeds (with hypre 2.22.1-3 and openblas 0.3.19+ds-2, in
an armhf chroot):

Running tests for HYPRE
testing began at Fri Jan 14 13:24:29 UTC 2022
running TEST_ams ... ok
test TEST_ams for HYPRE completed in 54 s
skipping TEST_bench
skipping TEST_examples
running TEST_fac ... ok
test TEST_fac for HYPRE completed in 106 s
skipping TEST_fei
running TEST_ij ... ok
test TEST_ij for HYPRE completed in 256 s
running TEST_lobpcg ... ok
test TEST_lobpcg for HYPRE completed in 116 s
running TEST_longdouble ... ok
test TEST_longdouble for HYPRE completed in 136 s
running TEST_single ... ok
test TEST_single for HYPRE completed in 78 s
running TEST_sstruct ... ok
test TEST_sstruct for HYPRE completed in 271 s
running TEST_struct ... ok
test TEST_struct for HYPRE completed in 186 s
running TEST_superlu ... ok
test TEST_superlu for HYPRE completed in 58 s
skipping TEST_timing
all tests for  HYPRE completed at Fri Jan 14 13:45:30 UTC 2022 in 1261s

So at this point I don’t know how to tackle this issue.

Drew, any idea?

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Bug#1003612: RFS: libview/0.6.6-3 [ITA] -- VMware's Incredibly Exciting Widgets

[Bastian Germann]

On 14.01.22 14:18, Ileana Dumitrescu wrote:

I did not originally notice #956789. The upstream code has not been updated 
since 2010, so it looks like nobody is maintaining it. I ran this through 
apt-rdepends, and no other package depends on libview to build. It should be 
removed since it appears that nobody is using it.


So you do not use it? Why would you then adopt it?

Should this RFS then be closed and the ITA set back to orphaned?

Bug#1003730: O: slowmovideo -- create slow-motion videos from your footage

[Gürkan Myczko]

Package: wnpp
Severity: normal

I intend to orphan the slowmovideo package. It doesn't receive much 
activity upstream...


Best,

Bug#1003610: libc6 crashes with VIA C7 and VIA Eden processors starting with 2.33

[Wolfgang Walter]

Am 2022-01-13 23:07, schrieb Aurelien Jarno:

On 2022-01-13 14:20, Wolfgang Walter wrote:

Am 2022-01-12 16:46, schrieb Aurelien Jarno:
> On 2022-01-12 16:14, Wolfgang Walter wrote:
> > Package: libc6
> > Version: 2.33-2
> > Severity: important
> >
> > After upgrading from libc6 2.32 to 2.33 all machines with a VIA C7
> > or VIA
> > Eden show segfaults in libc (i.e. hostname fails to work, or rebooting
> > fails). Machines with VIA Nehemiah work fine.
>
> Could you please provide more details? At least the content of dmesg
> when it happens or ideally a core dump or a backtrace.

Not easy. These machines just boot into a initramfs (which is a very 
minimal
debian sid) from an usb-stick and nothing survives a reboot. /bin/sh 
points

to bash.

The system does not use systemd but sysv.

The login prompt is:

(none) login:


I cannot log into the machine, login seems also be broken, it always 
says

"login incorrect".

If I try to reboot by entering ctrl-alt-del the reboot fails with:

INIT: Switching to runlevel: 6
INIT: No inittab.d directory found
INIT: Sending processes configured via /etc/inittab the TERM signal
[  305.550677][ T1235] rc[1235]: segfault at 1c81000 ip b7ebf634 sp 
bfb5ce78

error 6 in libc-2.33.so[b7d8e000+158000]
[  305.550791][ T1235] Code: 95 04 00 03 1c 8b 01 ca ff e3 29 d9 8d b4 
26 00
00 00 00 8d 76 00 0f 18 8a c0 03 00 00 0f 18 8a 80 03 00 00 81 eb 80 
00 00

00 <66> 0f 7f 02 66 0f 7f 42 10 66 0f 7f 42 20 66 0f 7f 42 30 66 0f 7f
Give root password for maintenance
(or press Control-D to continue):


Thanks. This codes corresponds to memset_sse2:

  14e607:   81 c3 69 95 04 00   add$0x49569,%ebx
  14e60d:   03 1c 8badd(%ebx,%ecx,4),%ebx
  14e610:   01 ca   add%ecx,%edx
  14e612:   ff e3   jmp*%ebx
  14e614:   29 d9   sub%ebx,%ecx
  14e616:   8d b4 26 00 00 00 00lea0x0(%esi,%eiz,1),%esi
  14e61d:   8d 76 00lea0x0(%esi),%esi
  14e620:   0f 18 8a c0 03 00 00prefetcht0 0x3c0(%edx)
  14e627:   0f 18 8a 80 03 00 00prefetcht0 0x380(%edx)
  14e62e:   81 eb 80 00 00 00   sub$0x80,%ebx
=>14e634:   66 0f 7f 02 movdqa %xmm0,(%edx)
  14e638:   66 0f 7f 42 10  movdqa %xmm0,0x10(%edx)
  14e63d:   66 0f 7f 42 20  movdqa %xmm0,0x20(%edx)
  14e642:   66 0f 7f 42 30  movdqa %xmm0,0x30(%edx)
  14e647:   66 0f 7f 42 40  movdqa %xmm0,0x40(%edx)

But I cannot login (Login incorrect). If I enter control-d instead, I 
get

"sulogin: cannot read /dev/tty1: Operation not permitted".

The very same usb stick boots just fine with non VIA 7 / VIA Eden
processors.


I modified it a bit an set --autologin for one getty. This did not 
worḱ, I

get a lot of things like

[   ..][ T1231] login[1231]: segfault at bfd3d000 ip b7eb5656 sp
bfd36978 error 6 in libc-2.33.so[b7d84000+158000]

or

[ ][ T1241] sh[1241]: segfault at 12ac000 ip b7e03638 sp 
bff99ff8

error 6 in libc-2.33.so[b7cd2000+158000]


Now I tried  getty -n -l /bin/dash. This worked.

If I try to start bash, bash crashes with a segmentation fault. I have 
no
debugger and no debugging symbols in this image at the moment, only 
strace


If I strace -f bash I get:

The last thing done is reading the first line of passwd, closing the 
file.

Then there is a SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR,
si_addr=0x12d9000}

When I do a strace -f bash 2> /tmp/blub the last system call is 
uname(),

then again a SEGV_MAPPERR

When bash segfaults I get no log that it crashed in libc6.

ls, rm, mount  etc seem to work.

But vim crashes in libc6, again at +158000 and with Code "1c 8b 01 ca 
ff e3
29 d9 8d b4 26 00 00 00 00 8d 76 00 0f 18 8a c0 03 00 00 0f 18 8a 80 
03 00
00 81 eb 80 00 00 00 <66> 0f 7f 02 66 0f 7f 42 10 66 0f 7f 42 20 66 0f 
7f 42

30 66 0f"

Also ip link ls crashes, again in libc6, again at +158000 and with 
Code "0f
18 8a 80 03 00 00 81 eb 80 00 00 00 00 66 0f 7f 02 66 0f 7f 42 10 66 
0f 7f
42 20 66 0f 7f 42 30 66 0f 7f 42 40 66 0f 7f 42 50 <66> 0f 7f 02 66 0f 
7f 42

70 71 c2 80 00 00 00 81 fb 80 00 00 00"

or ip addr ls

or less, perl, ssh, sshd, rsyslogd

The Code is not always the same, but <66> 0f 7f 42 seems to be and the 
crash

in libc-2.33.so[x+158000]



The above crashes are in memset_sse2 or bzero_sse2, I do not have 
enough

details to confirm, but that's not that important.


Thanks a lot for those details, they definitely help to understand
things a bit better, although things are not fully clear yet.

The memset_sse2 and bzero_sse2 are called only on a SSE2 capable CPU,
which is the case of the VIA C7, and that matches the fact the crash is
a segmentation fault and not an illegal instruction. The addresses
seems to be correctly aligned as required by SSE2 instructions.

I do not (yet?) understand why upgrading from 2.32 to 2.33 causes such
an issue, as the code of those functions 

Bug#1003729: packages.debian.org: missing buster-backports-sloppy suite

[Simon Richter]

Package: www.debian.org
Severity: normal
X-Debbugs-Cc: s...@debian.org

Hi,

the "buster-backports-sloppy" suite is missing from the package search.

   Simon

Bug#1003707: nvidia-legacy-340xx-driver

[Andreas Beckmann]

On 14/01/2022 02.03, Сергей Petrov wrote:

Package: nvidia-legacy-340xx-driver
Version: 340.108-12


There is not much infomation in this bug report. I'll try to guess, if 
I'm wrong please install reportbug and run

  reportbug -N 1003707
to collect additional information about your setup and have it sent to 
the bug report. (Creating the initial bug report with reportbug is 
recommended.)


So you want to use the unsupported 340xx legacy driver?

But there are also some packages from the current driver installed?
You can probably remove them (unless you really want to have both 
drivers installed). That might already fix your problem.


It it doesn't, what are the nvidia and glx alternatives pointing to?
  update-glx --display glx
  update-glx --display nvidia
(that information would have been collected by reportbug)
if glx is not pointing to nvidia or nvidia is not pointing to the legacy 
driver, you can change that with

  update-glx --config glx
  update-glx --config nvidia

Andreas

Bug#1003598: nvidia-legacy-340xx-driver bug

[Andreas Beckmann]

On 12/01/2022 13.41, Сергей Petrov wrote:

Package: nvidia-legacy-340xx-driver
Version: 340.108-12

after upgrade:
Jan  2 20:59:40 debian-home kernel: [   12.651966] nvidia: loading
out-of-tree module taints kernel.
Jan  2 20:59:40 debian-home kernel: [   12.651981] nvidia: module license
'NVIDIA' taints kernel.
Jan  2 20:59:40 debian-home kernel: [   12.651983] Disabling lock debugging
due to kernel taint
Jan  2 20:59:40 debian-home kernel: [   12.668265] nvidia: module
verification failed: signature and/or required key missing - tainting kernel


Yes. That's expected when using a proprietary out-of-tree kernel module. 
I don't see a bug here.
(The last message is about signing the kernel and its modules, but 
that's something requiring local configuration, nothing the nvidia 
packages are responsible for.)


Andreas

Bug#1003727: debian-edu-config: exim4 on TJENER does not accept system mails from Debian Edu clients

[Holger Levsen]

control: severity -1 important
thanks

On Fri, Jan 14, 2022 at 11:54:12AM +, Mike Gabriel wrote:
> When a client on the Debian Edu network (.intern, 10.0.0.0/8) tries to send
> system mails to postoffice.intern aka TJENER, then exim4 on TJENER won't
> accept these SMTP connects without proper authentication:

and how is this a serious bug in debian-edu-config?

I've pointed you at the severity documentation several times already, I won't
do it again here.


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

If a monkey hoarded more bananas than it could eat, while most of the other
monkeys starved, scientists would study that monkey to figure out what the
heck was wrong with it. When humans do it, we put them on the cover of Forbes.


signature.asc
Description: PGP signature

Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive

[Sebastian Ramacher]

Hi

On 2022-01-13 13:06:21, Paul Gevers wrote:
> Hi,
> 
> guestfs-tools was accepted in the archive, but it can't be (re)built
> anywhere because it requires:
> libcamomile-ocaml-dev- that isn't provided by
> libcamomile-ocaml-dev. I have no idea how ocaml packages work, but this
> needs to be fixed.

The ocaml dependencies are installable again after a round of binNMUs.
guestfs-tools however fails almost everywhere:
https://buildd.debian.org/status/package.php?p=guestfs-tools

Cheers
-- 
Sebastian Ramacher

Bug#632960: bluetooth: Bluetoothd dies after restoring from hibernate PM

[Nicola]

Package: bluetooth
Version: 5.62-2
Followup-For: Bug #632960

Dear Maintainer,
Same situation.

When any powerreduce act (p.e. display shutoff) the Bluetooth goes off, as
WiFi, but on resume WiFi restarts normally, bluetooth no.
bluetoothctl reports no controller on list command.
blueman fails to start.
blueman-adapters 12.39.01 ERRORAdapter:54 __init__  : No adapter(s) found

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (950, 'testing'), (400, 'unstable'), (300, 'experimental'), (10, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 bluetooth depends on:
ii  bluez  5.62-2

bluetooth recommends no packages.

Versions of packages bluetooth suggests:
pn  bluez-cups   
pn  bluez-meshd  
ii  bluez-obexd  5.62-2

-- no debconf information

Bug#933096: libsane-common: Not possible to scan from remote clients

[MAG4 Piemonte]

Dear Maintainer, we also confirm the bug looks 
solved upgrading to Debian 11 (that use libsane-
common 1.0.31-4.1) ...
Regards!

Guido

Bug#1003726: ITP: node-uvu -- Extremely fast and lightweight test runner for Node.js and the browser

[Yadd]

Package: wnpp
Severity: wishlist
Owner: Yadd 
X-Debbugs-Cc: debian-de...@lists.debian.org, 
pkg-javascript-de...@alioth-lists.debian.net

* Package name: node-uvu
  Version : 0.5.3
  Upstream Author : Luke Edwards 
* URL : https://github.com/lukeed/uvu
* License : Expat
  Programming Lang: JavaScript
  Description : Extremely fast and lightweight test runner for Node.js and 
the browser

There are many JavaScript test frameworks, most popular are tap, tape,
mocha and jest (packaged). Only jest is able to test browser libraries
in this list.
Some upstream authors prefer to switch to uvu because this one is faster
and able to testbrowser libraries. To avoid having to many untested
packages, I'm going to package uvu. It will be used quickly
(to test new node-postcss for example).
I packaged also node-jasmine which is able to test browser libraries
(only).

Note also that test written for one of these frameworks are not
compatible with another except jest that understand partially mocha
tests.

Package will be maintained under Pkg-JS Team umbrella.

Bug#1003725: python3-prettytable: Advertises version as 0.0.0

[Marc Glisse]

Package: python3-prettytable
Version: 2.5.0-1
Severity: normal

Dear Maintainer,

when some tool (like pip3) checks the version of prettytable, it gets
0.0.0. And indeed manually

$ ipython3
Python 3.9.9 (main, Jan 10 2022, 10:55:59)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.31.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import prettytable

In [2]: prettytable.__version__
Out[2]: '0.0.0'


If I install the pip version with pip3 install -U prettytable, the same
code properly reports '3.0.0'.

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'testing'), (500, 'stable'), (50, 'unstable-debug'), 
(50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.15.0-2-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 python3-prettytable depends on:
ii  python3 3.9.7-1
ii  python3-importlib-metadata  4.6.4-1
ii  python3-wcwidth 0.1.9+dfsg1-2

python3-prettytable recommends no packages.

python3-prettytable suggests no packages.

-- no debconf information

Bug#1003696: prosody: CVE-2022-0217: Unauthenticated Remote Denial of Service Attack in the WebSocket interface

[Matthew Wild]

Hi folks,

This is a link to the upstream patch for our 0.11.x series:
https://hg.prosody.im/0.11/raw-rev/783056b4e448

Let me know if you have any questions!

Regards,
Matthew (Prosody developer)

Bug#1003724: libpqxx: Please update package to version 7.7.0

[Stephan Lachnit]

Source: libpqxx
Version: 6.4.5-2
Severity: wishlist
X-Debbugs-Cc: stephanlach...@debian.org, deb...@kulisz.net

Dear maintainer,

please update the package to the latest version, as there are some interface
changes which newer software might require.

Regards,
Stephan


-- 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.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1003723: ITP: inotifyrecursive -- Simple way to watch a directory-tree recursively for file changes

[Mechtilde Stehmann]

Package: wnpp
Severity: wishlist
Owner: Mechtilde Stehmann 
X-Debbugs-Cc: Debian Python Team , 
mechti...@debian.org

* Package name: python3-inotifyrecursive
  Version : 0.3.5
  Upstream Author : Torben Haase 
* URL : https://github.com/letorbi/inotifyrecursive/
* License : GPL-3.0+
  Programming Lang: Python
  Description : Simple way to watch a directory-tree recursively for file
changes

It is a dependency of paperless (RFP #986227)

I want to package it inside the python-team

Bug#1003469: ceph: FTBFS with fmtlib/8.1.1

[Thomas Goirand]

On 1/14/22 05:19, Shengjing Zhu wrote:

Control: tags -1 patch

Please see the patch in attachment.

Thanks.


Hi ShengJing,

Thanks a lot for your patch, I'm rebuilding (and uploading) Ceph right away.

Cheers,

Thomas Goirand (zigo)

Bug#1003722: jupyter-notebook: blank page in firefox

[Jörg-Volker Peetz]

Package: jupyter-notebook
Version: 6.4.5-3
Severity: normal
X-Debbugs-Cc: none, J-V Peetz 

Dear Debian Python Team,

with firefox  (96.0-1 or 95.0.1-1) just a blank page is shown when calling the 
URL of the notebook server startet with `jupyter notebook --port=8177 --no-browser`.


Any suggestions?

Regards,
Jörg.


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

Kernel: Linux 5.15.13 (SMP w/8 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages jupyter-notebook depends on:
ii  init-system-helpers  1.61
ii  jupyter-core 4.9.1-1
ii  python3  3.9.8-1
ii  python3-notebook 6.4.5-3

jupyter-notebook recommends no packages.

jupyter-notebook suggests no packages.

-- no debconf information

Bug#1003719: stund: killed with assertion failed message

[Yann Droneaud]

Package: stun-server
Version: 0.97~dfsg-2.1+b1
Severity: normal
Tags: upstream

Dear Maintainer,

Through fuzzing with AFL++, a STUN request raising the following
assertion in stund was found:

stund: stun.cxx:791: void stunCreateUserName(const StunAddress4&, 
StunAtrString*): Assertion `l%4 == 0' failed.

One UDP datagram that triggers the assertion is:

$ echo AAIAAGS0zoCspgAAAGS0tM6ArPc= | base64 -d | hexdump -C
  00 02 00 00 64 b4 ce 80  ac a6 00 00 00 64 b4 b4  
|dd..|
0010  ce 80 ac f7   ||
0014

This packet can be sent with:

$ echo AAIAAGS0zoCspgAAAGS0tM6ArPc= | base64 -d | socat - 
UDP-DATAGRAM:10.0.2.15:3478

Stacktrace:

$ gdb /usr/sbin/stund
(gdb) run -v -h 10.0.2.15
Starting program: /usr/sbin/stund -v -h 10.0.2.15
STUN server version 0.97
If your machine does not have exactly two ethernet interfaces, you must 
specify the server and alt server
Running with on interface 10.0.2.15:3478 with alternate 0.0.0.0:3479
Warning - no alternate ip address STUN will not work
Binding to interface 0xf02000a
Opened port 3478 with fd 3
Binding to interface 0xf02000a
Opened port 3479 with fd 4
received on A1:P1
Got a request (len=20) from 10.0.2.15:47005
Received stun message: 20 bytes
Request parsed ok
Received SharedSecretRequestMsg on udp. send error 433.
stund: stun.cxx:791: void stunCreateUserName(const StunAddress4&, 
StunAtrString*): Assertion `l%4 == 0' failed.

Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x77af7535 in __GI_abort () at abort.c:79
#2  0x77af740f in __assert_fail_base (fmt=0x77c59ee0 
"%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0xe76d "l%4 == 
0", 
file=0xe705 "stun.cxx", line=791, function=) at 
assert.c:92
#3  0x77b05102 in __GI___assert_fail 
(assertion=assertion@entry=0xe76d "l%4 == 0", 
file=file@entry=0xe705 "stun.cxx", 
line=line@entry=791, 
function=function@entry=0xf5c0  "void stunCreateUserName(const 
StunAddress4&, StunAtrString*)") at assert.c:101
#4  0x6a30 in stunCreateUserName (source=..., 
username=username@entry=0x7fff9dbe) at stun.cxx:791
#5  0x97bd in stunCreateSharedSecretResponse (response=..., 
source=..., request=...) at stun.cxx:1007
#6  stunServerProcessMsg (buf=buf@entry=0x7fffa230 "", 
bufLen=, from=..., secondary=..., myAddr=..., altAddr=..., 
resp=, 
destination=, hmacPassword=, 
changePort=, changeIp=, verbose=)
at stun.cxx:1058
#7  0xb532 in stunServerProcess (info=..., verbose=) at stun.cxx:1566
#8  0x622c in main (argc=, argv=) 
at server.cxx:222

The problem is found in stunCreateUserName() in stun.cxx:

762 void
763 stunCreateUserName(const StunAddress4& source, StunAtrString* username)
[...] 
770char buffer[1024];
771sprintf(buffer,
772"%08x:%08x:%08x:",
773UInt32(source.addr),
774UInt32(stunRand()),
775UInt32(lotime));
[...]
783char hmacHex[41];
784toHex(hmac, 20, hmacHex );
785hmacHex[40] =0;
786
787strcat(buffer,hmacHex);
788
789int l = strlen(buffer);
790assert( l+1 < STUN_MAX_STRING );
791assert( l%4 == 0 );

buffer's length is always a multiple of 3, not 4, due to the number
of colons specified in sprintf()'s format string.

Remark:

buffer's length must be a multiple of 4, as STUN message attributes
must be aligned on 4 byte boundary.

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

Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages stun-server depends on:
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libstdc++6  8.3.0-6

Versions of packages stun-server recommends:
ii  stun-client  0.97~dfsg-2.1+b1

stun-server suggests no packages.

-- no debconf information

Bug#1003720: stund: buffer overflow parsing error attribute

[Yann Droneaud]

Package: stun-server
Version: 0.97~dfsg-2.1+b1
Severity: normal
Tags: upstream

Dear Maintainer,

Through fuzzing with AFL++, a STUN request triggering a buffer overflow
was found.

One UDP datagram that triggers the buffer overflow is:

$ echo EAAAEAEAAAEAAImJiYmJiYmJiQAACQEA | base64 -d | 
hexdump -C
  10 00 00 10 01 00 00 01  00 00 89 89 89 89 89 89  
||
0010  89 89 89 00 00 09 00 00  00 00 00 00 00 00 00 00  
||
0020  00 00 01 00   ||
0024

The packet can be sent with:

$ echo EAAAEAEAAAEAAImJiYmJiYmJiQAACQEA | base64 -d | socat 
- UDP-DATAGRAM:10.0.2.15:3478

On x86_64, stund crashes, not due to the buffer overflow itself, but
because memcpy() is trying to read after the stack:

$ gdb /usr/sbin/stund
(gdb) run -v -h 10.0.2.15
Starting program: /usr/sbin/stund -v -h 10.0.2.15
STUN server version 0.97
If your machine does not have exactly two ethernet interfaces, you must 
specify the server and alt server
Running with on interface 10.0.2.15:3478 with alternate 0.0.0.0:3479
Warning - no alternate ip address STUN will not work
Binding to interface 0xf02000a
Opened port 3478 with fd 3
Binding to interface 0xf02000a
Opened port 3479 with fd 4
received on A1:P1
Got a request (len=36) from 10.0.2.15:47185
Received stun message: 36 bytes

Program received signal SIGSEGV, Segmentation fault.
__memmove_avx_unaligned_erms () at 
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:262
262 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: No such file 
or directory.
(gdb) bt
#0  __memmove_avx_unaligned_erms () at 
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:262
#1  0x7bab in memcpy (__len=65532, __src=0x7fffa24c, 
__dest=0x7fff986e) at /usr/include/x86_64-linux-gnu/bits/string3.h:53
#2  stunParseAtrError (result=..., hdrLen=0, body=0x7fffa24c 
"\375\367\377\177") at stun.cxx:114
#3  stunParseMessage (buf=buf@entry=0x7fffa230 "", bufLen=, msg=..., verbose=verbose@entry=true) at stun.cxx:344
#4  0x958f in stunServerProcessMsg (buf=0x7fffa230 "", 
bufLen=, from=..., secondary=..., myAddr=..., altAddr=..., 
resp=, destination=, 
hmacPassword=, changePort=, changeIp=, 
verbose=) at stun.cxx:1040
#5  0x in ?? ()

(gdb) disassemble
Dump of assembler code for function __memmove_avx_unaligned_erms:
[...]
   0x77c316fc <+76>:mov%rdx,%rcx
=> 0x77c316ff <+79>:rep movsb %ds:(%rsi),%es:(%rdi)

(gdb) info registers
[...]
rcx0xb248  45640
rdx0xfffc  65532
rsi0x7000  140737488351232
rdi0x7fffe622  140737488348706
rbp0x7fff95f0  0x7fff95f0
rsp0x7fff94e8  0x7fff94e8

(gdb) p $_siginfo._sifields._sigfault.si_addr
$5 = (void *) 0x7000

(gdb) info proc mappings
process 25711
Mapped address spaces:

  Start Addr   End Addr   Size Offset objfile
[...]
  0x7ffde000 0x70000x210000x0 [stack]

The problem is found in stunParseAtrError() in stun.cxx:

 98 static bool 
 99 stunParseAtrError( char* body, unsigned int hdrLen,  StunAtrError& 
result )
100 {
101if ( hdrLen >= sizeof(result) )
102{
103   clog << "head on Error too large" << endl;
104   return false;
105}
106else
107{
108   memcpy(, body, 2); body+=2;
109   result.pad = ntohs(result.pad);
110   result.errorClass = *body++;
111   result.number = *body++;
112 
113   result.sizeReason = hdrLen - 4;
114   memcpy(, body, result.sizeReason);
115   result.reason[result.sizeReason] = 0;
116   return true;
117}
118 }

hdrLen is not checked for being at least 4, thus resulting in
result.sizeReason being greater than the result.reason size
for any hdrLen < 0.

Remark:

There doesn't seems to be any remote code execution possible
as stun-server is compiled with -fstack-protector-strong, thus,
even if stack depth was greater, allowing memcpy() to complete
the buffer overflow, it would still trigger stack protector in
stunServerProcessMsg().

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

Kernel: Linux 4.19.0-16-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#1003689: chromium: Chromium doesn't start

[Andres Salomon]

On 1/14/22 03:10, Martin Dosch wrote:

Dear Andres,

[...]
Also, I'm guessing you're running this under Wayland. If 
--use-gl=desktop doesn't help, can you try deleting lines 61 through 
63 in /usr/bin/chromium? These are the lines to delete:


That's it! Thank you, this fixed it. Chromium starts again.


Interesting. Can you please provide the terminal output when running it 
successfully?


Also, please try running it with "--ozone-platform-hint=auto" (also 
including the terminal output)? I expect it will crash, but if it 
doesn't then maybe we should be using that instead.

Bug#1003718: ITP: golang-gopkg-rethinkdb-rethinkdb-go.v6 -- Go language driver for RethinkDB

[Arnaud Rebillout]

Package: wnpp
Severity: wishlist
Owner: Arnaud Rebillout 

* Package name: golang-gopkg-rethinkdb-rethinkdb-go.v6
  Version : 6.2.1-1
  Upstream Author : RethinkDB
* URL : https://github.com/rethinkdb/rethinkdb-go
* License : Apache-2.0
  Programming Lang: Go
  Description : Go language driver for RethinkDB

This package provides native Golang driver for RethinkDB.

It is a build dependency of Notary v 0.7.x that I intend to package.

This package will be maintained within the Go Team.

Bug#1003717: xserver-xorg-video-nouveau: ttm buffer eviction failed + failed to load nvd9_fuc084 (regression db11-db10)

[Wim Bertels]

Package: xserver-xorg-video-nouveau
Version: 1:1.0.17-1
Severity: serious
Justification: serious

Hello,

This behaviour started with the upgrade from debian 10 to debian 11, 
(regression)
and has gotten worse since,
the graphical interface locks up on frequent base for a long time,
(more than once per hour, locking up from 10minutes to more than a hour, 
rebooting with a hard reset)
rendering the laptop useless

it might be related to the following bugs:
#990662
#989705
#903426

the errors from dmesg,
* [TTM] Buffer eviction failed
* firmware: failed to load nouveau/nvd9_fuc084 (maybe onrelated?)

a file is attached with more background.

hth,
Wim


-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Oct  5  2015 /etc/X11/X -> /usr/bin/Xorg
-rwxr-xr-x 1 root root 274 Dec 16 18:08 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G98M [Quadro NVS 
160M] [10de:06eb] (rev a1)

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

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

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

Kernel version (/proc/version):
---
Linux version 5.10.0-10-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.84-1 (2021-12-08)

Xorg X server log files on system:
--
-rw-r--r-- 1 wim  wim  44389 Mar 27  2019 /home/wim/.local/share/xorg/Xorg.2.log
-rw-r--r-- 1 wim  wim  42624 Nov 12  2019 /home/wim/.local/share/xorg/Xorg.1.log
-rw-r--r-- 1 wim  wim  47577 Nov 12  2019 /home/wim/.local/share/xorg/Xorg.0.log
-rw-r--r-- 1 root root 63438 Nov 23 11:31 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 43325 Jan 14 09:22 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[36.852] 
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
[36.852] Build Operating System: linux Debian
[36.852] Current Operating System: Linux lolifant 5.10.0-10-amd64 #1 SMP 
Debian 5.10.84-1 (2021-12-08) x86_64
[36.852] Kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-10-amd64 
root=/dev/mapper/lolifant--vg-root ro quiet
[36.852] Build Date: 16 December 2021  05:08:23PM
[36.852] xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support) 
[36.852] Current version of pixman: 0.40.0
[36.852]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[36.852] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[36.852] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 14 09:05:05 
2022
[36.956] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[36.989] (==) No Layout section.  Using the first Screen section.
[36.989] (==) No screen section available. Using defaults.
[36.989] (**) |-->Screen "Default Screen Section" (0)
[36.989] (**) |   |-->Monitor ""
[36.996] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[36.996] (==) Automatically adding devices
[36.996] (==) Automatically enabling devices
[36.996] (==) Automatically adding GPU devices
[36.996] (==) Max clients allowed: 256, resource mask: 0x1f
[37.035] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[37.035]Entry deleted from font path.
[37.060] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[37.060] (==) ModulePath set to "/usr/lib/xorg/modules"
[37.060] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[37.060] (II) Loader magic: 0x557d2d752e40
[37.060] (II) Module ABI versions:
[37.060]X.Org ANSI C Emulation: 0.4
[37.060]X.Org Video Driver: 24.1
[37.060]X.Org XInput driver : 24.1
[37.060]X.Org Server Extension : 10.0
[37.061] (++) using VT number 7

[37.061] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[37.062] (II) xfree86: Adding drm device (/dev/dri/card0)
[37.072] (--) PCI:*(1@0:0:0) 10de:06eb:1028:024f rev 161, Mem @ 
0xf500/16777216, 0xe000/268435456, 0xf200/33554432, I/O @ 
0xdf00/128, BIOS @ 0x/131072
[37.079] (II) LoadModule: "glx"
[37.103] (II) 

Bug#1003281: ITP: bakunbak -- Easily .bak a file or folder, then restore it.

[Philip Hands]

Michael Webster  writes:

>  - If there are other packages providing similar functionality,
>how does it compare? I've found no other packages (though
>it's possible something exists in utility/bin package
>bundles that doesn't get mentioned in package descriptions.

Could you perhaps explain why one might want to use this in preference
to any of the alternatives one might think of -- such as:

  mv
  mmv
  borgbackup (or whatever other decent backup system you use anyway)
  git (perhaps along with git-annex or git-lfs)

Also, do you happen to have any impression of how many users there are
of your package at present?  (e.g. download stats, messages regarding
it, issues opened etc.)

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY

Bug#982436: procps: Please allow overriding protect-links.conf settings via /etc/sysctl.conf

[intrigeri]

Hi,

Since then, a duplicate bug report was filed (#1000908) and promptly
fixed in 2:3.3.17-6 ⇒ this bug report can now be closed :)

Cheers!