Bug#994723: libimath-dev conflicts with libilmbase-dev

[Andrius Merkys]

Hi,

On 2021-10-11 18:05, Matteo F. Vescovi wrote:
> Oh, I guess I never came to that point since I was blocked by pystring
> and sphinx theme in the first place.
> How did you get over the sphinx theme blocker? I'm not going to
> package that too... I'm full for now ;-)

Interestingly, opencolorio build does not seem to check for sphinx theme
for me. I have python3-sphinx installed as per debian/control, and after
running 'gbp buildpackage -uc -us' as usual I get the following output:

[skip]
dh_auto_configure -- \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_CXX_FLAGS="-g -O2
-ffile-prefix-map=/home/andrius/debian-packages/opencolorio=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2" \
-DOCIO_BUILD_DOCS=ON \
-DOCIO_BUILD_NUKE=OFF \
-DOCIO_BUILD_STATIC=OFF \
-DOCIO_BUILD_TESTS=OFF \
-DOCIO_BUILD_TRUELIGHT=OFF \
-DOCIO_INSTALL_EXT_PACKAGES=NONE \
-DOCIO_USE_SSE=OFF \
-Dpystring_INCLUDE_DIR:PATH=/usr/include \
-DPYTHON=python3.9 \
-DUSE_EXTERNAL_TINYXML=ON \
-DUSE_EXTERNAL_YAML=ON
cd debian/cmake && cmake -DCMAKE_INSTALL_PREFIX=/usr
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON
-DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON
-DCMAKE_INSTALL_RUNSTATEDIR=/run -DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=ON
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_BUILD_TYPE=Release
"-DCMAKE_CXX_FLAGS=-g -O2
-ffile-prefix-map=/home/andrius/debian-packages/opencolorio=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2" -DOCIO_BUILD_DOCS=ON -DOCIO_BUILD_NUKE=OFF
-DOCIO_BUILD_STATIC=OFF -DOCIO_BUILD_TESTS=OFF
-DOCIO_BUILD_TRUELIGHT=OFF -DOCIO_INSTALL_EXT_PACKAGES=NONE
-DOCIO_USE_SSE=OFF -Dpystring_INCLUDE_DIR:PATH=/usr/include
-DPYTHON=python3.9 -DUSE_EXTERNAL_TINYXML=ON -DUSE_EXTERNAL_YAML=ON ../..
-- The CXX compiler identification is GNU 11.2.0
-- The C compiler identification is GNU 11.2.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Setting C++ version to '11' as none was specified.
-- Performing Test COMPILER_SUPPORTS_CXX11
-- Performing Test COMPILER_SUPPORTS_CXX11 - Success
-- Found OpenGL: /usr/lib/x86_64-linux-gnu/libOpenGL.so  found
components: OpenGL
-- Found GLEW: /usr/include (found version "2.2.0")
-- Found GLUT: /usr/lib/x86_64-linux-gnu/libglut.so
-- GLVND supported
-- Performing Test HAVE_SSE2
-- Performing Test HAVE_SSE2 - Success
-- Setting SOVERSION to '2.1' as none was specified.
-- Found expat: /lib/x86_64-linux-gnu/libexpat.so.1.8.1 (found suitable
version "2.4.1", minimum required is "2.2.8")
-- Found yaml-cpp: /usr/lib/x86_64-linux-gnu/libyaml-cpp.so.0.6.3 (found
suitable version "0.6.3", minimum required is "0.6.3")
-- Found pystring: /usr/include (Required is at least version "1.1.3")
CMake Error at
/usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230
(message):
  Could NOT find Imath (missing: Imath_INCLUDE_DIR) (Required is at least
  version "3.1.2")
Call Stack (most recent call first):
  /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:594
(_FPHSA_FAILURE_MESSAGE)
  share/cmake/modules/FindImath.cmake:116
(find_package_handle_standard_args)
  share/cmake/modules/FindExtPackages.cmake:45 (find_package)
  CMakeLists.txt:243 (include)

So the blocker for me is the missing imath, not sphinx theme.

Best,
Andrius

Bug#996104: dkms: Fail to remove modules

[S R Wright]

I encountered this error as well,  however manual removal via 'dkms 
remove' is still operational.

Bug#982894:

[Jason Perrin]

I have seen exactly the same problem (on AWS EC2 too), so I'm definitely
interested in a fix for this. Leaving /etc/resolv.conf unmodified if the
disk is full seems perfect as a fix!

Bug#996189: RFS: liesel/5.1.1 -- prepares PDFs to be printed as pamphlets/booklets

[Andrew Rightenburg]

Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: and...@rail5.org

Dear mentors,

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

 * Package name: liesel
   Version : 5.1.1
   Upstream Author : rail5 
 * URL : https://gitlab.com/rail5-bookthief/liesel
 * License : GPL-3.0+ with runtime exception for OpenSSL
 * Vcs : https://salsa.debian.org/rail5/liesel
   Section : misc

It builds this binary package:
  liesel - Command-line utility to prepare PDFs to be printed as 
pamphlets/booklets

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

  https://gitlab.com/rail5-bookthief/liesel

--
Regards,
Andrew S Rightenburg

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

[Craig Small]

Hi,
  I tried looking at http://upstream-metadata.debian.net/ but its down, is
this a current need?

On Sun, 3 Oct 2021 at 21:18, Romain Porte  wrote:

> Package: dh-make
> Version: 2.202102
> Severity: wishlist
> X-Debbugs-Cc: deb...@microjoe.org
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Dear Maintainer,
>
> When calling dh_make on a new project, the file
> `debian/upstream/metadata` is not created by default.
>
> This results in raising the upstream-metadata-file-is-missing
> experimental tag [1] in lintian:
>
> X: mypkg source: upstream-metadata-file-is-missing
>
> - From my experience, upstream metadata files [2] are *strongly suggested*
> during package creation, even if the lintian tag is still marked as
> experimental.
>
> My proposal is that a template for `debian/upstream/metadata` should
> be created when invoking `dh_make`. This template could contain
> most-used flags:
>
> Bug-Database: 
> Repository: 
> Repository-Browse: 
>
> After this is done, lintian flag(s) can be created in order to detect
> this templated values:
>
> E: mypkg source: debian-upstream-metadata-is-dh_make-template
> W: mypkg source: debian-upstream-metadata-has-dh_make-boilerplate
>
> If necessary, I can try to help in the implementation of this new
> feature.
>
> Best regards.
>
> [1] https://lintian.debian.org/tags/upstream-metadata-file-is-missing
> [2] https://wiki.debian.org/UpstreamMetadata
>
>
> - -- System Information:
> Debian Release: bookworm/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.14.0-1-amd64 (SMP w/16 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE
> not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages dh-make depends on:
> ii  debhelper  13.5.2
> ii  dpkg-dev   1.20.9
> ii  make   4.3-4.1
> ii  python33.9.2-3
>
> dh-make recommends no packages.
>
> Versions of packages dh-make suggests:
> ii  build-essential  12.9
>
> - -- no debconf information
>
> -BEGIN PGP SIGNATURE-
>
> iQJIBAEBCgAyFiEE/0vnfqUe7n1fhjM4L/9j9YUbA+IFAmFZgoQUHGRlYmlhbkBt
> aWNyb2pvZS5vcmcACgkQL/9j9YUbA+IVVw/9Ge5UEQoJ86YzTV0p+Cta1jHjCMyF
> g19SlBz08/t6XriElsQdZKVu6DZxCIYLRAih3GI8vh7Re7S2mu8NNDHzBBwmOGO6
> y9F7MRydIMos4H8dsvktv2FLmVYrKcm4wkuNTbB+vjz3XhyMNEDPfubfwyqohasN
> /YcyJDAuuXM9tSAvR+tSH/+sNOPvNTPZba2c1IsR7O4lnwUxjbWWIZY3TO3NOl53
> uFPf2M0iYIBGUAuKXy24bzEoJn09rEjFohVI9KjIHYEED7c5EFVFkM1vCwxiqMOO
> QkA9PryGNwpgCNwmfABh7b7bZrS2yKj5oeWmkp87+wKmO+zHtIRchBsIhQCUczfg
> 0zv0zvBv742tP6pJr0ioLtbqejQCpo+4pFoun4HhCzj4dCWMdem8yJ/aZRRrIW0Q
> QLbScBWq9EZHkCPJdWWvSkB6aY+JuiDNpg7hXq+/4mnIlwxmuyQr6xfDQJ/deS+Y
> hbKDoSIizsOtLOCcLxAaL1sgV4DOysNHB0qnorJhikAwWMgjBOxFFrtV+gWlAaFa
> mB95TH3vA5wLipWfQuvWZ/++eDMP3fP8MxDiers93E5KfnnFAS2DPZpT36FSwiEn
> WLsE6nG3IMn2/+6zF0LEMvBHCAsL9EnQKY9rw5DcyQkLmTDc85vCp3xaw0vSq0qx
> A2njH6frCHBaeB8=
> =H53X
> -END PGP SIGNATURE-
>

Bug#905460: ITP: opencamlib -- C++ library for creating 3D toolpaths for CNC machines

[Petter Reinholdtsen]

[Kurt Kremitzki 2018-08-08]
> Hello all, I've prepared this package and it's ready for
> review/sponsorship for any who would like to take a look:
> 
> https://salsa.debian.org/kkremitzki-guest/opencamlib
> 
> (By the way, could someone create the science-team/opencamlib repository
> on salsa?)

Hm, look like no-one took your offer.  Is it too late?

If not, I would be happy to sponsor the upload, see
http://www.hungry.com/~pere/debian-sponsoring.html > for my
preferences.
-- 
Happy hacking
Petter Reinholdtsen

Bug#953954: python-greenlet: diff for NMU version 0.4.15-4.1

[Sandro Tosi]

>  OK, this package is also a good candidate for DPT maintenance if you
> have time for it. I can't promise much activity.
> I don't have any SCM for the packaging, just the packaging files as-is.

i've imported the history in
https://salsa.debian.org/python-team/packages/python-greenlet and i'm
going to upload it soon to fix the metadata. There are also 1.x
releases, which i'll investigate at a later time

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

Bug#996194: gcc-arm-none-eabi: reproducible builds: embeds path to various binaries

[Vagrant Cascadian]

Source: gcc-arm-none-eabi
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: usrmerge shell
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The paths to various binaries are embedded which differs on a usrmerge
vs. non-usrmerge system.

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/gcc-arm-none-eabi.html

  /usr/lib/gcc/arm-none-eabi/10.3.1/install-tools/fixincl

  /bin/sed
vs.
  /usr/bin/sed

  /usr/lib/gcc/arm-none-eabi/10.3.1/install-tools/mkheaders

  for·shell·in·$CONFIG_SHELL·$SHELL·/bin/bash·/bin/sh·"";·do
vs.
  for·shell·in·$CONFIG_SHELL·$SHELL·/bin/sh·/bin/sh·"";·do

Patch attached which passes variables to configure to use the
non-usrmerge locations, as usrmerge installations typically have
compatibility symlinks, but not vice-versa. The patch also sets
variables to ensure consistent values for bash, which can be triggered
when /bin/sh points to bash.

This patch alone does not fix all reproducibility issues (e.g. build
paths, which are only tested on unstable and experimental), but does
reduce the number of things that vary in the resulting build.

Thanks for maintaining gcc-arm-none-eabi!

live well,
  vagrant
From 4ee144c5271da7ab35e866a8aa84ad4b74b22021 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 12 Oct 2021 02:21:23 +
Subject: [PATCH 1/2] debian/rules: Pass variables to configure to make the
 package build reproducibly regardless of usrmerge.

The variables SED, SHELL, BASH and CONFIG_SHELL should all point to
their non-usrmerge locations.

https://tests.reproducible-builds.org/debian/issues/paths_vary_due_to_usrmerge_issue.html
---
 debian/rules | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index a3d2833a4..07d9a2571 100755
--- a/debian/rules
+++ b/debian/rules
@@ -65,7 +65,11 @@ CONFIGURE_GCC_FLAGS = \
 	--without-newlib \
 	$(MULTILIB_LIST) \
 	$(BUILDFLAGS) \
-	$(TARGET_TOOLS)
+	$(TARGET_TOOLS) \
+	SED=/bin/sed \
+	SHELL=/bin/sh \
+	BASH=/bin/bash \
+	CONFIG_SHELL=/bin/bash \
 
 %:
 	dh $@ -D$(GCC_SOURCE_DIR) -B$(GCC_BUILD_DIR) --parallel --with autoreconf
-- 
2.30.2



signature.asc
Description: PGP signature

Bug#995741: gcc-arm-none-eabi: reproducible builds: embeds path to various binaries

[Vagrant Cascadian]

Source: gcc-arm-none-eabi
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: usrmerge shell
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

The paths to various binaries are embedded which differs on a usrmerge
vs. non-usrmerge system.

  
https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/diffoscope-results/gcc-arm-none-eabi.html

  /usr/lib/gcc/arm-none-eabi/10.3.1/install-tools/fixincl

  /bin/sed
vs.
  /usr/bin/sed


  /usr/lib/gcc/arm-none-eabi/10.3.1/install-tools/mkheaders

  for·shell·in·$CONFIG_SHELL·$SHELL·/bin/bash·/bin/sh·"";·do
vs.
  for·shell·in·$CONFIG_SHELL·$SHELL·/bin/sh·/bin/sh·"";·do

Patch attached which passes variables to configure to use the
non-usrmerge locations, as usrmerge installations typically have
compatibility symlinks, but not vice-versa. The patch also sets
variables to ensure consistent values for bash, which can be triggered
when /bin/sh points to bash.

This patch alone does not fix all reproducibility issues (e.g. build
paths, which are only tested on unstable and experimental), but does
reduce the number of things that vary in the resulting build.


Thanks for maintaining gcc-arm-none-eabi!


live well,
  vagrant
From 4ee144c5271da7ab35e866a8aa84ad4b74b22021 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Tue, 12 Oct 2021 02:21:23 +
Subject: [PATCH 1/2] debian/rules: Pass variables to configure to make the
 package build reproducibly regardless of usrmerge.

The variables SED, SHELL, BASH and CONFIG_SHELL should all point to
their non-usrmerge locations.

https://tests.reproducible-builds.org/debian/issues/paths_vary_due_to_usrmerge_issue.html
---
 debian/rules | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index a3d2833a4..07d9a2571 100755
--- a/debian/rules
+++ b/debian/rules
@@ -65,7 +65,11 @@ CONFIGURE_GCC_FLAGS = \
 	--without-newlib \
 	$(MULTILIB_LIST) \
 	$(BUILDFLAGS) \
-	$(TARGET_TOOLS)
+	$(TARGET_TOOLS) \
+	SED=/bin/sed \
+	SHELL=/bin/sh \
+	BASH=/bin/bash \
+	CONFIG_SHELL=/bin/bash \
 
 %:
 	dh $@ -D$(GCC_SOURCE_DIR) -B$(GCC_BUILD_DIR) --parallel --with autoreconf
-- 
2.30.2



signature.asc
Description: PGP signature

Bug#996189: RFS: liesel/5.1.1 -- prepares PDFs to be printed as pamphlets/booklets

[Nicholas D Steeves]

Dear Andrew,

Andrew Rightenburg  writes:

> Package: sponsorship-requests
> Severity: normal
> X-Debbugs-Cc: and...@rail5.org
>
> Dear mentors,
>
> I am looking for a sponsor for my package "liesel":
>
>  * Package name: liesel
>Version : 5.1.1
>Upstream Author : rail5 
>  * URL : https://gitlab.com/rail5-bookthief/liesel
>  * License : GPL-3.0+ with runtime exception for OpenSSL
>  * Vcs : https://salsa.debian.org/rail5/liesel
>Section : misc
>
> It builds this binary package:
>   liesel - Command-line utility to prepare PDFs to be printed as 
> pamphlets/booklets
>
> To access further information about this package, please visit the following 
> URL:
>
>   https://gitlab.com/rail5-bookthief/liesel
>

This RFS caught my eye because I have a substantial interest in print
culture.  Here are a couple of comments:

Have you read the Upstream Guide:
  https://wiki.debian.org/UpstreamGuide ?

"focal" is not a Debian suite, and the Debian packaging should be on a
separate branch if it's maintained in upstream VCs.  Typically git tags
are then merged to that branch.  IIRC this info (and more) should be in
the debian-mentor mailing list archives, but it will probably be faster
to just read the Upstream Guide.

Next, I don't think that Misc is the right section.  After consulting
the following, I think you will agree that there exists another section
that will make your software more discoverable:

  https://packages.debian.org/unstable/

:-)

A Debian ITP (Intent to Package) bug is also missing, closing that ITP
in the first--and only--changelog entry is also missing.  Also, in your
ITP bug and long description (in debian/control), please compare Liesel
to alternatives that already exist in the archive.  After consulting
https://gitlab.com/rail5-bookthief/bookthief, it looks like liesel
exclusively supports four pages per pamphlet/booklet?

Here are some other docs you'll need to read sooner or later:

  https://www.debian.org/doc/debian-policy
  https://www.debian.org/doc/manuals/developers-reference
  https://www.debian.org/doc/manuals/debmake-doc/index.en.html
  https://www.debian.org/doc/manuals/maint-guide

For Liesel to be become part of Debian it will, at a minimum, need to be
DFSG and Policy-compliant, and you'll definitely want to read the
Upstream Guide.  Your sponsor will also ask you to make the package
"lintian clean".

If all of this sounds like too much work, then you'll want to file an
RFP (Request for Packaging).  For both an ITP and RFP, use the command
"reportbug wnpp".

Take care!
Nicholas


signature.asc
Description: PGP signature

Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols

[YunQiang Su]

Simon McVittie  于2021年10月6日周三 下午11:09写道：
>
> Source: llvm-toolchain-13
> Version: 1:13.0.0-2
> Severity: important
> X-Debbugs-Cc: m...@packages.debian.org, debian-m...@lists.debian.org, 
> debian-...@lists.debian.org
>
> llvm-toolchain-13 has always failed to build on armel, mipsel, mips64el.
> This makes mesa BD-Uninstallable on those release architectures since
> its move to llvm-toolchain-13.
>
> On armel:
> > FAILED: bin/llvm-profdata
> > : && /<>/build-llvm/./bin/clang++ -fPIC 
> > -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC 
> > -fno-semantic-interposition -fvisibility-inlines-hidden -Werror=date-time 
> > -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter 
> > -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic 
> > -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough 
> > -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type 
> > -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override 
> > -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color 
> > -ffunction-sections -fdata-sections -O2 -DNDEBUG -g1 -marm -Wl,-z,relro
> > -Wl,-rpath-link,/<>/build-llvm/tools/clang/stage2-bins/./lib  
> > -Wl,-O3 -Wl,--gc-sections 
> > tools/llvm-profdata/CMakeFiles/llvm-profdata.dir/llvm-profdata.cpp.o -o 
> > bin/llvm-profdata  -Wl,-rpath,"\$ORIGIN/../lib"  lib/libLLVM-13.so.1  
> > -lpthread && :
> > /usr/bin/arm-linux-gnueabi-ld: 
> > tools/llvm-profdata/CMakeFiles/llvm-profdata.dir/llvm-profdata.cpp.o: 
> > undefined reference to symbol '__atomic_fetch_add_4@@LIBATOMIC_1.0'
> > /usr/bin/arm-linux-gnueabi-ld: /usr/lib/arm-linux-gnueabi/libatomic.so.1: 
> > error adding symbols: DSO missing from command line
>
> On mips*el, the failure is in a different place, but might have the same
> root cause (or not, clone this bug if necessary):
> > FAILED: lib/clang/13.0.0/lib/linux/libclang_rt.scudo_standalone-mipsel.so
> > : && /usr/bin/g++-10 -fPIC -fPIC -Wno-unused-command-line-argument 
> > -Wno-unknown-warning-option -fPIC -fno-semantic-interposition 
> > -fno-shrink-wrap -fvisibility-inlines-hidden -Werror=date-time -Wall 
> > -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual 
> > -Wno-missing-field-initializers -pedantic -Wno-long-long 
> > -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess 
> > -Wno-redundant-move -Wno-pessimizing-move -Wno-noexcept-type 
> > -Wdelete-non-virtual-dtor -Wsuggest-override -Wno-comment 
> > -Wmisleading-indentation -fdiagnostics-color -ffunction-sections 
> > -fdata-sections -Wall -std=c++14 -Wno-unused-parameter -O2 -DNDEBUG -g1  
> > -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option 
> > -Wl,--build-id -Wl,-z,defs -Wl,-z,nodelete   -mips32r2 -mabi=32 
> > -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wl,-z,defs,-z,now,-z,relro 
> > -ffunction-sections -fdata-sections -Wl,--gc-sections -pthread 
> > -Wl,-rpath-link,/<>/build-llvm/./lib -shared 
> > -Wl,-soname,libclang_rt.scudo_standalone-mipsel.so -o 
> > lib/clang/13.0.0/lib/linux/libclang_rt.scudo_standalone-mipsel.so 
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/checksum.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/common.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/crc32_hw.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/flags_parser.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/flags.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/fuchsia.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/linux.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/release.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/report.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/string_utils.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o
> >  
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_cpp.cpp.o
> >   -Wl,-rpath,"\$ORIGIN/../lib" && :
> > /usr/bin/ld: 
> > projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o:
> >  in function `scudo::atomic_u64::Type 
> > scudo::atomic_load(scudo::atomic_u64 const volatile*, 
> > scudo::memory_order)':
> > /<>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: 
> > undefined reference to `__atomic_load_8'
> > 

Bug#996193: SyntaxWarning: "is" with a literal.

[Joseph Nahmias]

Package: pithos
Version: 1.1.2-1.1
Severity: normal
File: /usr/share/pithos/pithos/SearchDialog.py


Hello,

While upgrading one of my systems from buster to bullseye, I saw the following 
in the output:

Setting up python3 (3.9.2-3) ...
running python rtupdate hooks for python3.9...
/usr/share/pithos/pithos/SearchDialog.py:83: SyntaxWarning: "is" with a 
literal. Did you mean "=="?
  if i.resultType is 'song':
/usr/share/pithos/pithos/SearchDialog.py:85: SyntaxWarning: "is" with a 
literal. Did you mean "=="?
  elif i.resultType is 'artist':
running python post-rtupdate hooks for python3.9...


Seems like an easy enough fix.
Hope this helps,
--Joe

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

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

Versions of packages pithos depends on:
ii  gir1.2-gst-plugins-base-1.0  1.18.4-2
ii  gir1.2-gstreamer-1.0 1.18.4-2.1
ii  gir1.2-gtk-3.0   3.24.24-4
ii  gstreamer1.0-plugins-bad 1.18.4-3
ii  gstreamer1.0-plugins-good1.18.4-2
ii  python3  3.9.2-3
ii  python3-gi   3.38.0-2
ii  python3-gi-cairo 3.38.0-2
ii  python3-pkg-resources52.0.0-4

Versions of packages pithos recommends:
ii  adwaita-icon-theme [gnome-icon-theme-symbolic]  3.38.0-1
ii  gir1.2-appindicator3-0.10.4.92-7
ii  gir1.2-keybinder-3.00.3.2-1.1
ii  gir1.2-notify-0.7   0.7.9-3
ii  python3-dbus1.2.16-5
ii  python3-pylast  4.1.0-1

pithos suggests no packages.

-- no debconf information

Bug#996192: unblock: net-snmp/5.9.1+dfsg-3

[Craig Small]

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

Please unblock package net-snmp

[ Reason ]
net-snmp is not moving into bookworm due to a regression with
pyagentx. However there is reason to believe this is due to 
a race condition in pyagentx test script
https://salsa.debian.org/python-team/packages/pyagentx/-/merge_requests/2

[ Impact ]
net-snmp will stay at 5.9, specifically the AES improvements 
will not be there and anything else that was added in the
last year.

[ Tests ]
net-snmp passes all its autopkg tests see
https://qa.debian.org/excuses.php?package=net-snmp

[ Risks ]
I see no risk, the issue is pyagentx failing its tests.
It's not a linking issue, pyagentx is pure python but
uses snmpd to test itself. The problem is that if
the agentx starts faster than snmpd the test fails
because it cannot connect to the socket.

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

[ Other info ]

unblock net-snmp/5.9.1+dfsg-3

Bug#995829: ITP: itk5 -- extensive suite of software tools for image analysis

[Steven Robbins]

On Wednesday, October 6, 2021 10:18:15 A.M. CDT Ghislain Vaillant wrote:

> * Package name: itk5
>   Version : 5.2.1

Hi Ghislain.  You surely know that ITK v4 is already in Debian.  The salsa 
project is called "insighttoolkit" and was where we had intended to put the 
ITK v5 packaging.  Feel free to use it.

-Steve

Bug#995827: llvm-toolchain-13: FTBFS on armel, mipsel, mips64el: undefined references to __atomic_foo symbols

[Nicholas D Steeves]

Hi Sylvestre,

Sylvestre Ledru  writes:

> Le 06/10/2021 à 17:05, Simon McVittie a écrit :
>>> /usr/bin/ld: 
>>> projects/compiler-rt/lib/scudo/standalone/CMakeFiles/clang_rt.scudo_standalone-dynamic-mipsel.dir/wrappers_c.cpp.o:
>>>  in function `scudo::atomic_u64::Type 
>>> scudo::atomic_load(scudo::atomic_u64 const volatile*, 
>>> scudo::memory_order)':
>>> /<>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: 
>>> undefined reference to `__atomic_load_8'
>>> /usr/bin/ld: 
>>> /<>/compiler-rt/lib/scudo/standalone/atomic_helpers.h:66: 
>>> undefined reference to `__atomic_load_8'
> Yeah, I saw, it guess it is a -latomic missing again :)
>

I've subscribed to this bug, since I just noticed llvm-toolchain-13 was
available, and irony-mode users always want to use the latest Clang.
Most irony-mode users are on amd64, so I'm thinking about switching now
(for the greatest good), but I'm wondering this: Given that you know
what the cause is, do you think this bug will soon be resolved?

Thanks!
Nicholas


signature.asc
Description: PGP signature

Bug#980957: llvm-toolchain-12 autopkgtest segfaults on armhf

[Nicholas D Steeves]

Hi Gianfranco,

On Sun, Mar 28, 2021 at 09:11:49PM +0200, Gianfranco Costamagna wrote:
> control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=27659
> control: affects -1 src:binutils
> 
> Invoking the clang with -V shows a failure in ld.bdf linker, a failure that 
> doesn't happen with gold linker and with object files (crt*.o) copied on 
> local directory.
> 
> I opened a bug against binutils people to track it down, hopefully they can 
> sort what is segfaulting there.
> 

Thank you for opening this upstream :-)  I'm a bit confused about the
resolution at the forwarded bug, because the accidental buggy commit
to the master branch doesn't appear on the binutils-2_37
branch...which seems to indicate that the issue is distinct from the
one in that upstream bug.

Does the following log indicates that the arm64 ftbfs is due to a
binfmt problem?

Job for binfmt-support.service failed because the control process
exited with error code.

https://ci.debian.net/data/autopkgtest/testing/arm64/l/llvm-toolchain-12/15347075/log.gz

But this failure also exists on amd64, so I have no clue

https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-12/15341122/log.gz

Regards,
Nicholas

Bug#996111: lintian: Incorrect warnings for HTML files

[Felix Lechner]

Hi,

On Mon, Oct 11, 2021 at 6:16 PM Hugh McMaster  wrote:
>
> I'll look into enabling Salsa CI for the repo.

With some luck, you can simply add a file like this one [1] to your repo.

Kind regards
Felix Lechner

[1] 
https://salsa.debian.org/lechner/mdadm/-/blob/debian/master/debian/salsa-ci.yml

Bug#995850: lintian: more context is not always a good thing

[Felix Lechner]

Hi Hugh,

On Mon, Oct 11, 2021 at 5:48 PM Hugh McMaster  wrote:
>
> To avoid specifying the tag override four times, I tried "line 35 41
> 57 132" but that didn't work at all.

I am not opposed to the idea (or to making overrides easier to use in
other ways) but isn't the array as susceptible to new upstream
versions as four separate lines?

BTW, Lintian's test suite has an automatic hint adjuster. (No editor
required.) Would that be helpful to the public for use on their
overrides?

Kind regards
Felix Lechner

Bug#996191: ITP: python-halo -- Beautiful terminal spinners library for Python3

[Nobuhiro Iwamatsu]

Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-halo
  Version : 0.0.31
  Upstream Author : Manraj Singh 
* URL : https://github.com/manrajgrover/halo
* License : Expat
  Programming Lang: Python
  Description : Beautiful terminal spinners library for Python3

 Library that displays spinner (loading, processing during processing,
 etc.) on terminal in Python3.

Bug#996190: ITP: python-log-symbols -- Colored symbols for various log levels in Python3

[Nobuhiro Iwamatsu]

Package: wnpp
Severity: wishlist
Owner: Nobuhiro Iwamatsu 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-log-symbols
  Version : 0.0.14
  Upstream Author : Manraj Singh 
* URL : https://github.com/manrajgrover/py-log-symbols
* License : Expat
  Programming Lang: Python
  Description : Colored symbols for various log levels in Python3

 Library that displays colored symbols for various log levels on terminal
 in Python3.

Bug#538217: Informativo Webmail 21:14:55

[Cadastro Webmail]

Prezado Cliente,
Por motivos de segurança precisamos efetuar uma identificação para confirmar
autenticidade de utilização da nossa plataforma do Webmail.
caso não seja efetuado, está verificação seu acesso poderá ser bloqueado ou até
mesmo ocasionar a perda de suas informações e todos os serviços, agradecemos
pela sua colaboração para que possamos sempre melhorar a nossa segurança.

Confirmar https://cutt.ly/9E7Cyzm

Bug#996177: cryptsetup: please report fatal errors without having to use -v

[Guilhem Moulin]

Control: found -1 2:2.1.0-5+deb10u2

On Tue, 12 Oct 2021 at 00:33:32 +0200, Guilhem Moulin wrote:
> On Mon, 11 Oct 2021 at 22:09:07 +0200, Marc Lehmann wrote:
>> Specifically, the machine didn't have enough ram, probably because the
>> default algorithm (argon) requires more ram than the machine had.
> 
> Could you please share the memory cost of the PBKDF, and also the output
> of `free` just before running cryptsetup?  That would help us trying to
> reproduce this and forward the issue upstream.  I tried to reproduce
> this but only managed to trigger the OOM killer.
> 
> Also did you run luksFormat on that same machine (and didn't remove
> memory sticks afterwards)?

I was actually able to reproduce this with buster's 2.1.0, but doing the
same thing after upgrading to bullseye or sid yields

(initramfs) cryptsetup luksOpen /dev/vda5 test_crypt
Enter passphrase for /dev/vda5: 
[5.236310] device-mapper: uevent: version 1.0.3
[5.240230] device-mapper: ioctl: 4.43.0-ioctl (2020-10-01) initialised: 
dm-de...@redhat.com
Not enough available memory to open a keyslot.

which sounds alright.  Did you run reportbug(1) from the affected system
or from an older one?

Looking at the upstream git log, I found 
206b70c837f29c8b34cb0d80ae496870550ec50c
which fixes https://gitlab.com/cryptsetup/cryptsetup/-/issues/488 which looks
really familiar :-)

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#995689: [Debian-med-packaging] Bug#995689: python-reportlab breaks autopkgtest of python-biopython

[Étienne Mollier]

Control: reassign -1 src:python-biopython 1.78+dfsg-5
Control: affects -1 src:python-reportlab 3.5.67-2
Control: tags -1 confirmed

Hi there,

Graham Inggs, on 2021-10-04:
> I noticed that python-biopython already has a Recommends on
> python3-renderpm.  One solution would be to bump this to a Depends.
> Alternatively, python3-renderpm could be added to python3-reportlab as
> a Depends.

Thanks Graham for your report and analysis!  I have been
assessing the situation on my end, and assuming reportlab can be
used without renderpm, I think that this is a probably a bug on
python3-biopython control information.

As far as I could see, the test suite can run either with both
packages, or none of them, so demoting python3-reportlab to
Suggests, same as python3-renderpm, could also do the trick.
That being said the issue would also be at risk to propagate to
users of biopython if python3-reportlab is installed without
python3-renderpm on their hosts.  Thus, bumping python3-renderpm
to Depends sounds to me to be the most appropriate approach as
well.

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


signature.asc
Description: PGP signature

Bug#994902: To be fixed again shortly

[Felix Lechner]

Control: reopen -1

Hi,

A recent commit [1] gave rise to a different fix, which is coming soon. Thanks!

Kind regards
Felix Lechner

[1] 
https://salsa.debian.org/lintian/lintian/-/commit/93b4e49c805ccf767f948ada5993318ab711120c

Bug#996188: RuntimeError: populate() isn't reentrant

[Kevin Otte]

Package: graphite-web
Version: 1.1.8-1
Severity: grave

Dear Maintainer,

Installed graphite-web on a fresh bullseye machine and migrated the apache 
virtualhost configuration from a running buster machine.

Attempting to load the page results in the error listed in the subject.

Full traceback:
[Mon Oct 11 23:04:53.039528 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] mod_wsgi (pid=12645): 
Failed to exec Python script file '/usr/share/graphite-web/graphite.wsgi'.
[Mon Oct 11 23:04:53.039710 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] mod_wsgi (pid=12645): 
Exception occurred processing WSGI script 
'/usr/share/graphite-web/graphite.wsgi'.
[Mon Oct 11 23:04:53.040057 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] Traceback (most recent 
call last):
[Mon Oct 11 23:04:53.040169 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254]   File 
"/usr/share/graphite-web/graphite.wsgi", line 15, in 
[Mon Oct 11 23:04:53.040190 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] application = 
get_wsgi_application()
[Mon Oct 11 23:04:53.040217 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254]   File 
"/usr/lib/python3/dist-packages/django/core/wsgi.py", line 12, in 
get_wsgi_application
[Mon Oct 11 23:04:53.040232 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] 
django.setup(set_prefix=False)
[Mon Oct 11 23:04:53.040257 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254]   File 
"/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup
[Mon Oct 11 23:04:53.040271 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] 
apps.populate(settings.INSTALLED_APPS)
[Mon Oct 11 23:04:53.040295 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254]   File 
"/usr/lib/python3/dist-packages/django/apps/registry.py", line 83, in populate
[Mon Oct 11 23:04:53.040309 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] raise 
RuntimeError("populate() isn't reentrant")
[Mon Oct 11 23:04:53.040389 2021] [wsgi:error] [pid 12645:tid 140670772766464] 
[remote 2603:6080:a201:f403:c2d6:3266:d138:be92:40254] RuntimeError: populate() 
isn't reentrant

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.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 graphite-web depends on:
ii  adduser 3.118
ii  python3 3.9.2-3
ii  python3-cairo   1.16.2-4+b2
ii  python3-cairocffi   1.2.0-1
ii  python3-django  2:2.2.24-1
ii  python3-django-tagging  1:0.4.5-3
ii  python3-pyparsing   2.4.7-1
ii  python3-simplejson  3.17.2-1
ii  python3-six 1.16.0-2
ii  python3-tz  2021.1-1
ii  python3-urllib3 1.26.5-1~exp1
ii  python3-whisper 1.1.4-2.1

graphite-web recommends no packages.

Versions of packages graphite-web suggests:
pn  graphite-carbon  
ii  libapache2-mod-wsgi-py3  4.7.1-3+b1
pn  python3-ldap 
pn  python3-memcache 
pn  python3-mysqldb  

-- no debconf information

Bug#996177: cryptsetup: please report fatal errors without having to use -v

[Guilhem Moulin]

Control: tag -1 moreinfo

Hi,

On Mon, 11 Oct 2021 at 22:09:07 +0200, Marc Lehmann wrote:
> Specifically, the machine didn't have enough ram, probably because the
> default algorithm (argon) requires more ram than the machine had.

Could you please share the memory cost of the PBKDF, and also the output
of `free` just before running cryptsetup?  That would help us trying to
reproduce this and forward the issue upstream.  I tried to reproduce
this but only managed to trigger the OOM killer.

Also did you run luksFormat on that same machine (and didn't remove
memory sticks afterwards)?

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#995125: linux: Realtek ethernet driver r8169 lacks support for chip chip XID 54b

[rwright]

The same sequence of patches that I applied to linux-source version
5.10.46 in message 31 will also apply cleanly and enable the device
using linux-source version 5.10.70.

[0.00] Linux version 5.10.70-rfw (rfw@pd400) (gcc (Debian 10.2.1-6) 
10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Sat Oct 9 
13:33:41 MDT 2021
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.70-rfw 
root=UUID=85ed9906-0d36-41ca-bfdf-9434fe5ecd2c ro loglevel=9 efi=debug 
nohibernate noresume panic=30 systemd.unit=multi-user.target
[0.015814] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10.70-rfw 
root=UUID=85ed9906-0d36-41ca-bfdf-9434fe5ecd2c ro loglevel=9 efi=debug 
nohibernate noresume panic=30 systemd.unit=multi-user.target
[1.866334] rtc_cmos 00:01: setting system clock to 2021-10-11T10:14:47 UTC 
(1633947287)
[2.022716] BOOT_IMAGE=/boot/vmlinuz-5.10.70-rfw
...
[   10.439020] r8169 :04:00.1: can't disable ASPM; OS doesn't have ASPM 
control
[   10.459843] libphy: r8169: probed
[   10.462187] r8169 :04:00.1 eth0: RTL8168fp/RTL8117, b0:22:7a:22:c7:e7, 
XID 54b, IRQ 83
[   10.466378] r8169 :04:00.1 eth0: jumbo features [frames: 9194 bytes, tx 
checksumming: ko]
[   10.783196] r8169 :04:00.1 eno1: renamed from eth0
[   12.095444] Generic FE-GE Realtek PHY r8169-0-401:00: attached PHY driver 
[Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-0-401:00, irq=IGNORE)
[   12.218876] r8169 :04:00.1 eno1: Link is Down
[   14.654147] r8169 :04:00.1 eno1: Link is Up - 1Gbps/Full - flow control 
rx/tx

-- 
Randy WrightHewlett Packard Enterprise
Phone: (970) 898-0998   Mail: rwri...@hpe.com

Bug#996187: ITP: libmime-ecoencode-perl -- MIME encoding (economical)

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Perl Group 


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: libmime-ecoencode-perl
  Version : 0.95
  Upstream Author : MURATA Yasuhisa 
* URL : https://metacpan.org/release/MIME-EcoEncode
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : MIME encoding (economical)

 MIME::EcoEncode implements MIME encoded-word syntax
 as defined in RFC 2047.
 .
 MIME encoded-word syntax uses a string of ASCII characters
 indicating both the original character encoding (the "charset")
 and the content-transfer-encoding
 used to map the bytes of the charset into ASCII characters.

This package will be team-maintained by the Debian Perl team.

It is needed by libhttp-link-perl.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFktHIACgkQLHwxRsGg
ASFZ7Q//WwdSvr5EbjRC6OPRCO8SbyZY17+jLfGsDwbOFBSwGdH5fW2Pz0RzKgv2
6a1g/IJ0vWc6jUgB4NP7fcaY+nahtooLn9jv4UR2UY1R2b/MmSX+0FUNijlOcIZC
YM/Ob3Cimrl63U579Yhjji5IkvActpdOPytJUCk6GC2co9TrC8sNhtIWCymSD4GS
5nnHWJYk3iu4iXxgd/RF8OELwwNOv4AO/005e416TiSFmNYVXynfz2h3LYfSSR0n
uZ4JTEtvGeTU0yJGJ4fG/RAMFsdRJoRQSFt/gE3iJ3WB8TpJUYAbV0W/vxo3BjuK
nq6aS/7kf1c4TccIAcECKzdiJ8vfbzivRacqOyn91zm+nrH7JFbCBYippeLxfP0w
JrnDl+IDYJgDApLgwH5BSLckXLisowui/GdI0gPU5oClS06KjUWWYDkFisvVBrO3
uH+IoX4j8KF2VsPiAO5/ge8GRMUp65CzTVr4Y9B86a/gqo25QcvJ6uMTcjZTeK29
mS5DAPPNRujt9XYCrkAx9pwH/rUBUanNIamMswlRh16yGFavebBifPGJFse47+zu
u7humZGXcZjgaQFsji0I4pV8bKaIWppJzkWRxDAb+7mNavepKC4H8+Nx3fPakWLR
c1dd5W0pRpFK+wOKJKZ0jQhfgXs4VHa7EOF290DqpAajnky+dJM=
=E25G
-END PGP SIGNATURE-

Bug#994127: libvirt-daemon: Error creating virtual network - iptables (nf_tables) table `nat' is incompatible, use 'nft'

[James Youngman]

Package: libvirt-daemon
Version: 7.0.0-3
Followup-For: Bug #994127

I also find (after upgrade from buster to bullseye) that my default
network will no longer start:

jupiter:~$ sudo virsh net-list --all
 Name   State  Autostart   Persistent
---
 defaultinactive   yes yes
 ipv6-net   inactive   yes yes

jupiter:~$ sudo virsh net-info default
Name:   default
UUID:   b5472d74-d362-4d85-900c-14959e3dfd35
Active: no
Persistent: yes
Autostart:  yes
Bridge: virbr0

jupiter:~$ sudo virsh net-start default
error: Failed to start network default
error: internal error: Failed to apply firewall rules /usr/sbin/iptables -w 
--table filter --list-rules: iptables v1.8.7 (nf_tables): table `filter' is 
incompatible, use 'nft' tool.


jupiter:~$ dpkg -l nftables iptables
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---==
ii  iptables   1.8.7-1  amd64administration tools for packet 
filtering and NAT
ii  nftables   0.9.8-3.1amd64Program to control packet 
filtering rules by Netfilter project
jupiter:~$ readlink -f /usr/sbin/iptables
/usr/sbin/xtables-nft-multi
jupiter:~$  update-alternatives --display iptables
iptables - auto mode
  link best version is /usr/sbin/iptables-nft
  link currently points to /usr/sbin/iptables-nft
  link iptables is /usr/sbin/iptables
  slave iptables-restore is /usr/sbin/iptables-restore
  slave iptables-save is /usr/sbin/iptables-save
/usr/sbin/iptables-legacy - priority 10
  slave iptables-restore: /usr/sbin/iptables-legacy-restore
  slave iptables-save: /usr/sbin/iptables-legacy-save
/usr/sbin/iptables-nft - priority 20
  slave iptables-restore: /usr/sbin/iptables-nft-restore
  slave iptables-save: /usr/sbin/iptables-nft-save
jupiter:~$ ls -l /usr/sbin/iptables   /etc/alternatives/iptables 
/usr/sbin/iptables-nft /usr/sbin/xtables-nft-multi
lrwxrwxrwx 1 root root 22 Jul 10  2019 /etc/alternatives/iptables -> 
/usr/sbin/iptables-nft
lrwxrwxrwx 1 root root 26 Jul 10  2019 /usr/sbin/iptables -> 
/etc/alternatives/iptables
lrwxrwxrwx 1 root root 17 Jan 17  2021 /usr/sbin/iptables-nft -> 
xtables-nft-multi
-rwxr-xr-x 1 root root 220232 Jan 17  2021 /usr/sbin/xtables-nft-multi

It appears that moving the alternative doesn't fix the problem.   A
bit confusingly, the command shown, if I run it manually, appears to
work:

jupiter:~$ sudo virsh net-start default
error: Failed to start network default
error: internal error: Failed to apply firewall rules /usr/sbin/iptables -w 
--table filter --list-rules: iptables v1.8.7 (nf_tables): table `filter' is 
incompatible, use 'nft' tool.



jupiter:~$ sudo /usr/sbin/iptables -w --table filter --list-rules
-P INPUT ACCEPT
-P FORWARD ACCEPT
-P OUTPUT ACCEPT
jupiter:~$ echo $?
0

Though of course, that doesn't get my VMs booted.  None of my guest
VMs can start.  This is a significant problem for me.

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

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

Versions of packages libvirt-daemon depends on:
ii  libblkid1   2.36.1-8
ii  libc6   2.31-13+deb11u2
ii  libdevmapper1.02.1  2:1.02.175-2.1
ii  libgcc-s1   10.2.1-6
ii  libglib2.0-02.66.8-1
ii  libnetcf1   1:0.2.8-1.1
ii  libparted2  3.4-1
ii  libpcap0.8  1.10.0-2
ii  libpciaccess0   0.16-1
ii  libselinux1 3.1-3
ii  libudev1247.3-6
ii  libvirt-daemon-driver-qemu  7.0.0-3
ii  libvirt07.0.0-3
ii  libxml2 2.9.10+dfsg-6.7

Versions of packages libvirt-daemon recommends:
ii  libvirt-daemon-driver-lxc   7.0.0-3
ii  libvirt-daemon-driver-vbox  7.0.0-3
ii  libvirt-daemon-driver-xen   7.0.0-3
ii  libxml2-utils   2.9.10+dfsg-6.7
ii  netcat-openbsd  1.217-3
ii  qemu-system-x86 [qemu-kvm]  1:5.2+dfsg-11+deb11u1

Versions of packages libvirt-daemon suggests:
pn  libvirt-daemon-driver-storage-gluster   
pn  libvirt-daemon-driver-storage-iscsi-direct  
pn  libvirt-daemon-driver-storage-rbd   
pn  libvirt-daemon-driver-storage-zfs   
ii  libvirt-daemon-system   

Bug#995644: lebiniou: Fails to upgrade: trying to overwrite '/usr/share/lebiniou/etc/schemes.json'

[Olivier Girondel]

On Sun, 3 Oct 2021 17:10:22 +0200 Kurt Roeckx  wrote:

Package: lbeibiou
Version: 3.61.2-1
Severity: serious

Hi,

During an upgrade, I get the following:
dpkg: considering deconfiguration of lebiniou-data, which would be broken by 
installation of lebiniou ...
dpkg: yes, will deconfigure lebiniou-data (broken by lebiniou)
Preparing to unpack .../110-lebiniou_3.61.2-1+b1_amd64.deb ...
De-configuring lebiniou-data (3.54.1-1) ...
Unpacking lebiniou (3.61.2-1+b1) over (3.54.1-1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-dU3HYR/110-lebiniou_3.61.2-1+b1_amd64.deb (--unpack):
 trying to overwrite '/usr/share/lebiniou/etc/schemes.json', which is also in 
package lebiniou-data 3.54.1-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
dpkg: considering deconfiguration of lebiniou, which would be broken by 
installation of lebiniou-data ...
dpkg: yes, will deconfigure lebiniou (broken by lebiniou-data)
Preparing to unpack .../111-lebiniou-data_3.61.1-1_all.deb ...
De-configuring lebiniou (3.54.1-1) ...
Unpacking lebiniou-data (3.61.1-1) over (3.54.1-1) ...



Hi Kurt,

lebiniou-3.62.1-1 has been recently uploaded to unstable, does the 
problem still occur ?



This looks like it's missing a Replaces. A Breaks is not enough.


Not sure what to do, what would you suggest ?


Trying again, it works because lebiniou-data got updated.

I'm not sure why the file moved from lebiniou-data to lebiniou.


We decided that for some cases (e.g: non debian-based systems) the 
schemes.json should be part of lebiniou, not lebiniou-data.


Thanks for your answers,

Best regards,

--
Olivier

Bug#995961: libapache2-mpm-itk: Error "AH00052: child pid exit signal Segmentation fault" after update to apache 2.4.51-1~deb11u1

[Cool Fire]

On Mon, 11 Oct 2021 20:54:38 +0200 "Steinar H. Gunderson" 
 wrote:
> It seems to me that this is only in bullseye-proposed-updates, not 
actually a

> security update yet? If it breaks mpm-itk and nobody really knows why,
> I would say that's a good reason to stop the proposal process of the 
package.


It is already a security update: 
https://www.debian.org/security/2021/dsa-4982
For some reason it's not showing up in the listing on 
packages.debian.org, but that might be expected behavior. I don't know 
the packages site well enough to say for sure.


Just to double-confirm I'm getting it from stable-security repos:
$ apt list --upgradable

Listing... Done
apache2-bin/stable-security 2.4.51-1~deb11u1 amd64 [upgradable from: 
2.4.48-3.1]
apache2-data/stable-security 2.4.51-1~deb11u1 all [upgradable from: 
2.4.48-3.1]
apache2-utils/stable-security 2.4.51-1~deb11u1 amd64 [upgradable from: 
2.4.48-3.1]

apache2/stable-security 2.4.51-1~deb11u1 amd64 [upgradable from: 2.4.48-3.1]

Bug#996181: cryptsetup-initramfs: Unable to use keyfile to decrypt rootfs

[Guilhem Moulin]

Control: severity -1 wishlist

Hi,

On Mon, 11 Oct 2021 at 22:28:31 +0200, Mateusz Jończyk wrote:
> Currently, it is not possible to use a keyfile to decrypt the root
> file system. I would like to use such a setup, so I'm attaching a
> short patch for crypttab to make this work.

IMHO this is too use-case specific and on most setups it'd just lock
users out of their system, so I'm reluctant to adopt this.

> Using a keyfile on the first volume to decrypt the second one does not
> make it necessary to type the password twice on boot.
> […]
> Probably the best solution would be to allow decrypting more then one
> LUKS container with a single password. This will also make converting
> existing systems to encrypted storage easier. I'll try to add relevant
> support to cryptsetup-initramfs and post a separate patch.

We already have solutions for this, see
/usr/share/doc/cryptsetup-initramfs/README.initramfs.gz §9 and §10, as
well /usr/share/doc/cryptsetup/README.keyctl.  (For LUKS2 one can also
use the builtin kernel keyring support, but one one need to workaround
the password prompt.)

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#996030: transition: libsidplayfp

[GCS]

On Mon, Oct 11, 2021 at 9:45 PM Sebastian Ramacher  wrote:
> On 2021-10-10 17:25:10 +0200, László Böszörményi wrote:
> >  Small transition of libsidplayfp, affecting audacious-plugins, mpd and 
> > qmmp.
> > I will upload its counterpart, sidplayfp when the transition is
> > allowed to start.
>
> Please go ahead and while you're at it please also remove the
> unnecessary Breaks+Replaces from libsidplayfp6.
 Correct, removed and uploaded.

Thanks,
Laszlo/GCS

Bug#996186: ITP: libweb-solid-auth-perl -- Solid authentication perl library

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Perl Group 


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: libweb-solid-auth-perl
  Version : 0.5
  Upstream Author : Patrick Hochstenbach
* URL : https://metacpan.org/release/Web-Solid-Auth
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : Solid authentication perl library

 Web::Solid::Auth is a Solid-OIDC implementation
 of a connection class for the Solid server.
 .
 Solid is a specification
 that lets people store their data securely
 in decentralized data stores called Pods.
 Pods are like secure personal web servers for data.
 When data is stored in someone's Pod,
 they control which people and applications can access it.

This package will be team-maintained in the Debian Perl team.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFkpWoACgkQLHwxRsGg
ASFyVw/9G8VYNjiP5EQgXCY/JWp7uQVUbjtszjOSZO9un9UGnQI9dZEwnK+VGM1G
U/C1FSShhTR6Zqa194SnJ7UEOkwp1PzlmJtiue9Nj0zGtj6MvfPrZMXchkiERYIZ
HrstTwEqURihqWy4eCypUXslqJzXt9g3s1GEfiYPXivvr048tqHj5RVC/Sz5HptW
hQ1AQo3UKDWdpiLbYmdvZmr1tQD2pQvJBFU2yhL6e+LoeYmEOVwbGQr3s+2sr9zD
Pn+QrPnVO2AxgxZFaOwq7+7aDdvzt5VWTaSpuK4XGW5Pabj8/sOP5WRgmE+fa12H
8IKroBg5GfZHSrie59Q1k/N/I25d66vimJ2i2yrTcir4REThoysL35CxiO5p7Pkl
pVODnHYvXbVWdayMSHWSy8vqIFQ84caY3HQZ1VCO0RlED90wmzV0xIoS5ctYwBCS
HCzPmFOZA+lrqtzp9BJKyEuIuEIBxaoLc6ODGFmE3vUHYOhQoGryVR65K8Pfm+KW
2OG7TSJQmt2ApMQhOGg34aN0kkT1RCG2ccz63QUsI+JnbuwMWizQJIGJdy1L1Kv8
+jC8bFkI+TB5/mtzNebVISynrSRLebSBUuw//DzxT3F4/d8RbvnEf1Tda7LZrxK9
GdfjqXSFdYzKJtp3EeVz756sng8vmNYy4RdPrOvvND9/+YgBoXU=
=U5bB
-END PGP SIGNATURE-

Bug#989777: Severity: High / Debian 10 11 with Kernel 5.10.x-amd64 = Intel AX210 Wifi Bluetooth not work

[pham...@bluewin.ch]

Hello Vincent,
I installed the 5.14.9-2 kernel: amd64 from testing.
After reboot I still have to install your old package for my wifi card to be 
detected :
https://snapshot.debian.org/archive/debian/20210313T203823Z/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20210208-4_all.deb
As with the 5.10 kernel there is only the Wifi which does not work and the 
Bluetooth ?!
I understood that Wifi worked from kernel 5.10 and Bluetooth worked from kernel 
5.10 ?!
Can you give me some good advice on how to get this damn Intel AX210 card 
working under Debian 11 Bullseye ??
Thanks in advance.
Meilleures salutations.
Philippe

Bug#994682: cryptsetup-initramfs: Poweroff timeout for cryptroot

[Christoph Anton Mitterer]

Just adding my two cents here, since Guilhem referenced that bug on the
mailing list:

a) How does a laptop turn on unintentionally? ;-)

b) Adding such feature (and enabling it by default) has IMO also some
dangers.

Consider that such a system would constantly be powered on
automatically (Wake-On-LAN or similar features of servers)... in such a
case, if cryptroot keyscript wouldn't finish in due time (e.g. because
no one enters the passphrase or so), it might end up in a
powerup/powerdown cycle... which is probably of no good for the
hardware.


Cheers,
Chris.

Bug#996185: ITP: libhttp-link-perl -- RFC 5988 web linking

[Jonas Smedegaard]

Package: wnpp
Severity: wishlist
Owner: Jonas Smedegaard 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Perl Group 


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: libhttp-link-perl
  Version : 0.001
  Upstream Author : David Zurborg 
* URL : 
* License : ISC
  Programming Lang: Perl
  Description : RFC 5988 web linking

 HTTP::Link is a perl library
 implementing resolving and parsing  HTTP link relations
 as defined in RFC 5988.
 .
 A link relation is a descriptive attribute
 attached to a hyperlink
 in order to define the type of the link,
 or the relationship between the source and destination resources.

This package will be team-maintained in the Debian Perl team.

It is needed for libweb-solid-auth-perl.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmFkrmwACgkQLHwxRsGg
ASH/DBAArrMdq227ppfIz+Pwt2gLoxy3p0NA2JLKqCjez+GwhkXSqUWe468W75Tm
SgGRtHCvE5PxKlhigNMGGJNl2whrBIE9nv9Bg/ijZZZVVTD9IULXBNXdI/zMHygh
a5G0B0yURJLsGTEDzHpn+utEXiYCA2EMaZ1bmfn55vgT3PdBTjbElKheypHwQ4FB
qs3dxFPWxA7TJZtoL+tlqoOAWspb/jNXhCR5pT69iyVFDLhbDWiEyCSrss8yLLod
2tLHAKZ2haDNlO89QHU1ry5XoJRfThTS6odeUrlYapzF3/deARp0+aR8Z1Zy5NcE
KcdfeDI8tNO7e6wP3CE8cHQh2j0um/42ulCsOfK+b1M77yKjBxyX1vaDIkS4P27W
ajYZ4PD4mpWsZ6LlYig66RfYZeOFYgneQ3xtfcrnSPRi5f1WlCd4hcy0zFkzlk/t
C2/a77KMDCU44w06n7dM6lfnWt4XKKb9RY1j5RRkLxMe3lb2TKqJsgsv+qesAvjN
PioecoLsB7E+ng/oCBxBWJtleJLFS+iF+PjmNYqlZaurFymN1ndW/bZSOz3TZZbI
aoR1STjZA+ajkr1SOHuyV6vVieWkhtpFplMdnrZihugWTakzov424eHVzEy545Zc
fx1KSL/+jhFwwBcozfj2/nO3IZh8MUswjq7tbTvv+k0jJlV7bRU=
=sNqr
-END PGP SIGNATURE-

Bug#996184: binutils-or1k-elf: reproducible builds: Enable deterministic archives

[Vagrant Cascadian]

Package: binutils-or1k-elf
Severity: normal
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain
Control: affects -1 gcc-or1k-elf
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

binutils-or1k-elf is not built with deterministic archives enabled,
which causes reproducibility issues in packages using it:

  
https://tests.reproducible-builds.org/debian/issues/unstable/timestamps_in_static_libraries_issue.html

The attached patch adds --enable-deterministic-archives to the configure
arguments in debian/rules.

FWIW, the --enable-deterministic-archives feature was enabled Debian's 
"binutils"
package in 2015.

With this feature enabled in binutils-or1k-elf, I've been able to
reproducibly build gcc-or1k-elf when using a stable build path.


Thanks for maintaining binutils-or1k-elf!


live well,
  vagrant
From 19ad976d637a6fe4276babec19d74b91e03130e1 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian 
Date: Mon, 11 Oct 2021 21:17:17 +
Subject: [PATCH] debian/rules: Pass --enable-deterministic-archives to
 configure.

https://tests.reproducible-builds.org/debian/issues/unstable/timestamps_in_static_libraries_issue.html
---
 debian/rules | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/debian/rules b/debian/rules
index 0f6b868..97b68a9 100755
--- a/debian/rules
+++ b/debian/rules
@@ -48,6 +48,9 @@ confargs += --with-pkgversion='$(pkgversion)+$(DEB_VERSION)'
 
 confargs += --disable-nls
 
+# https://tests.reproducible-builds.org/debian/issues/unstable/timestamps_in_static_libraries_issue.html
+confargs += --enable-deterministic-archives
+
 override_dh_auto_configure:
   # Imitate dh_auto_configure -- $(confargs), but without
   # --runstatedir as long as libiberty/configure cannot be refreshed.
-- 
2.30.2



signature.asc
Description: PGP signature

Bug#996051: gnome-shell-extension-desktop-icons: does not declare compatibility with GNOME Shell 41

[Gunnar Hjalmarsson]

Want to mention that gnome-shell-extension-desktop-icons-ng has been 
accepted into unstable at last.


https://tracker.debian.org/pkg/gnome-shell-extension-desktop-icons-ng

It's a successor of gnome-shell-extension-desktop-icons with more 
features often desired by users. The -ng (new generation) project is 
well maintained so far, and Ubuntu's desktop team participates actively 
upstream since Ubuntu ships the -ng package by default (already in 21.04 
and 21.10).


This speaks for giving up on gnome-shell-extension-desktop-icons in 
Debian. Maybe turn it into a dummy which depends on 
gnome-shell-extension-desktop-icons-ng.


--
Gunnar Hjalmarsson

Bug#996181: cryptsetup-initramfs: Unable to use keyfile to decrypt rootfs

[Christoph Anton Mitterer]

On Mon, 2021-10-11 at 22:28 +0200, Mateusz Jończyk wrote:
> Currently, it is not possible to use a keyfile to decrypt the root
> file system.

I guess the reason is, that currently such key file would be simply
added into the initramfs, from where everyone on the system could read
it (and also from the temporary directories used when creating the
initramfs image).

Cheers,
Chris.

Bug#995645: RFS: python-certbot-dns-standalone/1.0.3-1 [ITP] -- Standalone DNS plugin for Certbot with an integrated DSN server

[Linus Vanas]

Control: tags -1 - moreinfo

Jeroen Ploemen kirjoitti 11.10.2021 klo 20.30:

hi Linus,


Hello Jeroen and thanks for the review!

I have now addressed your points (hopefully in a satisfying manner)
and uploaded the updated packaging to Mentors and Salsa.

Particularly,


The package doesn't build or install any documentation, although
upstream provides both sphinx docs and a readme file. End users
would definitely benefit from having those available to them.


I included the upstream README into the package. I don't think
the Sphinx documentation provides any additional information or
value.

Lintian in unstable is unhappy due to #995490, but otherwise the
package should be clean now.


Linus Vanas

Bug#996183: RM: node-lodash-compat -- ROM; Unmaintained, unused and should have been built directly from node-lodash

[Yadd]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org

Hi,

node-lodash-compat is a rebuild of (old) node-lodash in UMD format. It
has no reverse dependencies in Debian, orphaned upstream 7 years ago,
not well packaged (minified file not rebuilt),...

I think it should be removed from Debian archive.

Cheers,
Yadd

Ref: https://github.com/lodash-archive/lodash-compat

Bug#996177: cryptsetup: please report fatal errors without having to use -v

[Milan Broz]

On 11/10/2021 22:09, Marc Lehmann wrote:
> 
> Specifically, the machine didn't have enough ram, probably because the
> default algorithm (argon) requires more ram than the machine had.
> 
> Unfortunately, cryptsetup silently fails - you get a password prompt, youc
> an enter any password, your shell prompt appears without any message but
> nothing happened.

If the process was killed by OOM (out of memory daemon), then it cannot
print anything - it is simply stopped by the kernel.

But if it really fails with return code 3 (out of memory), then it should print
a visible error - if not, we have to fix it.
(Verbose option only translates return code to something readable but there 
should
be an error message much earlier.)

Is it simple cryptsetup open activation (no systemd-cryptsetup magic)?
(If so, please add new issue upstream and link this bug, we will fix that.)

Thanks,
Milan

Bug#996182: ITP: google-api-services-sheets-java -- Google Sheets API Client Library for Java

[Markus Koschany]

Package: wnpp
Severity: wishlist
Owner: Markus Koschany 
X-Debbugs-Cc: debian-de...@lists.debian.org, a...@debian.org, 
debian-j...@lists.debian.org

* Package name: google-api-services-sheets-java
  Version : 1.32.1-1
  Upstream Author : Google
* URL : 
https://github.com/googleapis/google-api-java-client-services
* License : Apache-2.0
  Programming Lang: Java
  Description : Google Sheets API Client Library for Java

Google Sheets is a spreadsheet program included as part of the
web-based Google Docs Editors suite offered by Google. This library
allows developers to read and write Google Sheets.

Bug#996181: cryptsetup-initramfs: Unable to use keyfile to decrypt rootfs

[Mateusz Jończyk]

Package: cryptsetup-initramfs
Version: 2:2.3.5-1
Severity: normal
Tags: patch

Hello,

Currently, it is not possible to use a keyfile to decrypt the root file system. 
I would like to use such a setup, so I'm attaching a short patch for crypttab 
to make this work.

The root filesystem may reside on more then one LUKS volume and it is 
cumbersome to type the password twice on each boot. I'm using such a setup: I 
have two drives in my laptop: on each one of them I have an encrypted LUKS 
partition, on every LUKS partition I have several LVM logical volumes. Two of 
these logical volumes (one from every physical drive) are setup in a RAID1 
array, on which my rootfs resides.

See also bug #928943 for another setup example.

Using a keyfile on the first volume to decrypt the second one does not make it 
necessary to type the password twice on boot.

I'm using Ubuntu 20.04 as the main system on my laptop, but I have reproduced 
and fixed this problem in a Debian 11 virtual machine - to fix it upstream.

Probably the best solution would be to allow decrypting more then one LUKS 
container with a single password. This will also make converting existing 
systems to encrypted storage easier. I'll try to add relevant support to 
cryptsetup-initramfs and post a separate patch.

The output of "lsblk" in the test VM:

NAMEMAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT
sda   8:00   10G  0 disk  
├─sda18:10  487M  0 part  
│ └─md0   9:00  486M  0 raid1 /boot
└─sda28:20  9,5G  0 part  
  └─10Ga253:00  9,5G  0 crypt 
├─10Ga-root 253:10  9,3G  0 lvm   
│ └─md1   9:10  9,3G  0 raid1 /
└─10Ga-key  253:20   12M  0 lvm   
sdb   8:16   0   10G  0 disk  
├─sdb18:17   0  487M  0 part  
│ └─md0   9:00  486M  0 raid1 /boot
└─sdb28:18   0  9,5G  0 part  
  └─10Gb253:30  9,5G  0 crypt 
└─10Gb-root 253:40  9,3G  0 lvm   
  └─md1   9:10  9,3G  0 raid1 /
sr0  11:01 1024M  0 rom   


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.10.0-9-amd64 root=/dev/md1 ro quiet

-- /etc/crypttab
# 
10Ga /dev/sda2 none luks,initramfs
10Gb /dev/sdb2 /dev/mapper/10Ga-key luks,initramfs,keyfile-size=512

-- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
#
# / was on /dev/md1 during installation
UUID=c010b6e7-72b7-4237-acfa-c4071d82a804 /   ext4
errors=remount-ro 0   1
/dev/md0/boot   ext4errors=remount-ro   0   1
/dev/sr0/media/cdrom0   udf,iso9660 user,noauto 0   0
debian  /root/host  9p  nofail  0   0

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

Kernel: Linux 5.10.0-9-amd64 (SMP w/1 CPU thread)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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

-- debconf information excluded
>From 4529b33c3e4c47f9124c7426d5bb9d530954b812 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mateusz=20Jo=C5=84czyk?= 
Date: Sun, 10 Oct 2021 22:27:56 +0200
Subject: [PATCH] debian: allow using key file to decrypt rootfs

There are some cases when someone would like to use a key file to unlock
the root filesystem. One of them is when the key file is a partition on
a pendrive. Another one is when the key file is on an encrypted device
(possibly an LVM logical volume) that was unlocked by a previous
crypttab entry.

In both of these examples, the key file is accessible on /dev, so do
not mangle it with "/FIXME-initramfs-rootmnt" if that's the case.
---
 debian/initramfs/hooks/cryptroot | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/debian/initramfs/hooks/cryptroot b/debian/initramfs/hooks/cryptroot
index 81f65869..9e3d67a8 100644
--- a/debian/initramfs/hooks/cryptroot
+++ b/debian/initramfs/hooks/cryptroot
@@ -82,8 +82,7 @@ crypttab_print_entry() {
 ;;
 *)
 if [ "$usage" = rootfs ]; then
-cryptsetup_message "WARNING: Skipping root target 
$CRYPTTAB_NAME: uses a key file"
-return 1
+cryptsetup_message "WARNING: Root target $CRYPTTAB_NAME 
uses a key file"
 elif [ "$usage" = resume ]; then
 cryptsetup_message "WARNING: Resume target $CRYPTTAB_NAME 
uses a key file"
 fi
@@ -97,8 

Bug#996180: ITP: google-api-services-drive-java -- Google Drive API Client Library for Java

[Markus Koschany]

Package: wnpp
Severity: wishlist
Owner: Markus Koschany 
X-Debbugs-Cc: debian-de...@lists.debian.org, a...@debian.org, 
debian-j...@lists.debian.org

* Package name: google-api-services-drive-java
  Version : 1.32.1-1
  Upstream Author : Google Inc.
* URL : 
https://github.com/googleapis/google-api-java-client-services
* License : Apache-2.0
  Programming Lang: Java
  Description : Google Drive API Client Library for Java

Manages files in Google Drive, a file storage and synchronization
service, including uploading, downloading, searching, detecting
changes, and updating sharing permissions.

This is a new dependency of openrefine.

Bug#996179: ITP: libokhttp-signpost-java -- Signpost extension for signing OkHttp requests

[Markus Koschany]

Package: wnpp
Severity: wishlist
Owner: Markus Koschany 
X-Debbugs-Cc: debian-de...@lists.debian.org, a...@debian.org, 
debian-j...@lists.debian.org

* Package name: libokhttp-signpost-java
  Version : 1.1.0-1
  Upstream Author : Patrik Åkerfeldt
* URL : http://github.com/pakerfeldt/okhttp-signpost/
* License : Apache-2.0
  Programming Lang: Java
  Description : Signpost extension for signing OkHttp requests

Signpost is the easy and intuitive solution for signing HTTP messages
on the Java platform in conformance with the OAuth Core 1.0a standard.
This library is a Signpost extension for the OkHttp HTTP client.

Bug#996178: ITP: libwikidata-toolkit-java -- Wikidata Toolkit

[Markus Koschany]

Package: wnpp
Severity: wishlist
Owner: Markus Koschany 
X-Debbugs-Cc: debian-de...@lists.debian.org, a...@debian.org, 
debian-j...@lists.debian.org

* Package name: libwikidata-toolkit-java
  Version : 0.12.1
  Upstream Author : Markus Kroetzsch, Julian Mendez, Fredo Erxleben,
Michael Guenther, Markus Damm, Antonin Delpeuch,
Thomas Pellissier Tanon and other contributors
* URL : https://www.mediawiki.org/wiki/Wikidata_Toolkit
* License : Apache License 2.0
  Programming Lang: Java
  Description : Wikidata Toolkit

Wikidata Toolkit is a Java library for accessing Wikidata and other
Wikibase installations. It can be used to create bots, to perform data
extraction tasks (e.g., convert all data in Wikidata to a new format),
and to do large-scale analyses that are too complex for using a simple
SPARQL query service.

libwikidata-toolkit-java is a new build-dependency of openrefine.

Bug#996177: cryptsetup: please report fatal errors without having to use -v

[Marc Lehmann]

Package: cryptsetup
Version: 2:2.3.5-1
Severity: wishlist

Dear Maintainer,

I just had a somewhat lengthy initramfs debug issue caused by some
suboptimal cryptsetup behaviour.

Specifically, the machine didn't have enough ram, probably because the
default algorithm (argon) requires more ram than the machine had.

Unfortunately, cryptsetup silently fails - you get a password prompt, youc
an enter any password, your shell prompt appears without any message but
nothing happened.

Only when running cryptsetup with -v did it output an error message akin
to (repeated from memory):

   error -3 not enough memory

I think requiring users to use --verbose to see fatal error messages
is highly suboptimal behaviour. It would be nice if future versions of
cryptsetup would output error messages by default, at least when they are
fatal, i.e. the action could not be executed.

Thanks!

-- Package-specific info:

-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (990, 'stable-updates'), (990, 'stable-security'), (990, 
'stable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'stable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.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 cryptsetup depends on:
ii  cryptsetup-bin 2:2.3.5-1
ii  debconf [debconf-2.0]  1.5.77
ii  dmsetup2:1.02.175-2.1
ii  libc6  2.31-13+deb11u2

Versions of packages cryptsetup recommends:
ii  cryptsetup-initramfs  2:2.3.5-1
ii  cryptsetup-run2:2.3.5-1

Versions of packages cryptsetup suggests:
ii  dosfstools  4.2-1
ii  keyutils1.6.1-2
ii  liblocale-gettext-perl  1.07-4+b1

-- debconf information excluded

Bug#984353: surf-alggeo: ftbfs with GCC-11

[Torrance, Douglas]

Control: tags -1 patch

On Wed, 03 Mar 2021 16:17:45 + Matthias Klose  wrote:
> ../../../yaccsrc/Script.cc: In static member function ‘static void 
> Script::clearScreen()’:
> ../../../yaccsrc/Script.cc:910:23: error: reference to ‘byte’ is ambiguous
>   910 | *intensity = (byte)(-print_background_data);
>   |   ^~~~
> In file included from /usr/include/c++/11/bits/stl_algobase.h:61,
>  from /usr/include/c++/11/bits/char_traits.h:39,

This is due to the introduction of std::byte in C++17, which is default in GCC 
11.  One band-aid fix would be to explicitly drop back to C++14 -- see the 
attached patch.

In the long term, it would probably be good to drop all the various instances 
of "using namespace std".

DougFrom 1c7279785ea154905b33cdcafe79087efff39f44 Mon Sep 17 00:00:00 2001
From: Doug Torrance 
Date: Mon, 11 Oct 2021 16:09:53 -0400
Subject: [PATCH] Compile with C++14 standard to avoid byte v. std::byte
 issues.

---
 debian/rules | 1 +
 1 file changed, 1 insertion(+)

diff --git a/debian/rules b/debian/rules
index 3018e1a..e9aa70a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -2,6 +2,7 @@
 include /usr/share/dpkg/pkg-info.mk
 
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
+export DEB_CPPFLAGS_MAINT_APPEND = -std=gnu++14
 
 DEB_VIRT_SURFALGGEO_LISTOF_VARIANT = nox ##gtk
 
-- 
2.30.2

Bug#995961: libapache2-mpm-itk: Error "AH00052: child pid exit signal Segmentation fault" after update to apache 2.4.51-1~deb11u1

[Jean Weisbuch]

Seems like re-compiling mpm-itk (using the exact same sourcecode as the 
previous time i compiled it) and even without any patch applied to HTTPD 
2.4.51 did also fix the issue for me.

Bug#996174: wget: Spurious SSL_INIT in 1.21.2-1

[Bob Proulx]

I posted an update to the upstream bug tracker.

https://savannah.gnu.org/bugs/?61125

Bug#996176: xrdp: gnome shell crash related to https://github.com/neutrinolabs/xorgxrdp/issues/156, solved upstream please update to 0.9.17

[denis gmail]

Package: xrdp
Version: 0.9.12-1.1
Severity: important
Tags: upstream

Dear Maintainer,

When using Gnome desktop, xrdp is broken, resulting in
gnome crash with "Oh no ! ..."  error.

Upgrading xrdp and xorgxrdp to version 0.9.17 from bookworm
solves the problem.

The problem is probably related to bug
https://github.com/neutrinolabs/xorgxrdp/issues/156. By the way,
as the problem is solved upstream, is it possible to update bullseye
package to 0.9.17 ? This bug prevents any remote use of Bullseye stations.

Altough a quick fix is included in bug above, consisting in reverting to 
0.9.7 version, the author himself says that
it is not the good solution. So backporting all changes related to 
0.9.12 is probably not an option.



-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')

Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/6 CPU threads)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xrdp depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libc6    2.32-4
ii  libfuse2 2.9.9-5
ii  libjpeg62-turbo  1:2.0.6-4
ii  libopus0 1.3.1-0.1
ii  libpam0g 1.4.0-9+deb11u1
ii  libssl1.1    1.1.1k-1+deb11u1
ii  libx11-6 2:1.7.2-1
ii  libxfixes3   1:5.0.3-2
ii  libxrandr2   2:1.5.1-1
ii  lsb-base 11.1.0
ii  ssl-cert 1.1.0+nmu1

Versions of packages xrdp recommends:
ii  fuse3 [fuse]  3.10.3-2
ii  xorgxrdp  1:0.2.17-1

Versions of packages xrdp suggests:
pn  guacamole  

Versions of packages xorgxrdp depends on:
ii  libc6  2.32-4
ii  libepoxy0  1.5.5-1
pn  xorg-input-abi-24  
ii  xserver-xorg-core [xorg-video-abi-24]  2:1.20.11-1

Versions of packages xorgxrdp recommends:
ii  xorg  1:7.7+22

Versions of packages xrdp is related to:
pn  vnc-server   
ii  xserver-xorg-legacy  2:1.20.11-1

-- no debconf information

Bug#996174: wget: Spurious SSL_INIT in 1.21.2-1

[Bob Proulx]

Bob Proulx wrote:
> In today's daily upgrade wget 1.21.2-1 was installed and now emits a
> spurious "SSL_INIT" message.  This is breaking scripts. :-(
> 
> $ wget -q -O/dev/null https://www.example.com/
> SSL_INIT

Already fixed upstream.


https://git.savannah.gnu.org/cgit/wget.git/commit/?id=3ea9658c072fa1dc87aec7af45393b46904b143f

The problematic commit that added the message.


https://git.savannah.gnu.org/cgit/wget.git/commit/src/gnutls.c?id=5fe8d26904880ab59b2343f31ff7399edbbc43f1

However I do note that upstream has not yet made a release since
v1.21.2 that contains the above fix.

Bob

Bug#996030: transition: libsidplayfp

[Sebastian Ramacher]

Control: tags -1 confirmed
Control: forwarded -1 
https://release.debian.org/transitions/html/auto-libsidplayfp.html

On 2021-10-10 17:25:10 +0200, László Böszörményi wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi RMs,
> 
>  Small transition of libsidplayfp, affecting audacious-plugins, mpd and qmmp.
> I will upload its counterpart, sidplayfp when the transition is
> allowed to start.

Please go ahead and while you're at it please also remove the
unnecessary Breaks+Replaces from libsidplayfp6.

Cheers

> 
> Regards,
> Laszlo/GCS
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#996080: transition: pcl

[Sebastian Ramacher]

Control: tags -1 confirmed
Control: forwarded -1 https://release.debian.org/transitions/html/auto-pcl.html

On 2021-10-10 22:45:58 +0200, Jochen Sprickerhof wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Hi release team,
> 
> I would like to transition pcl. The autogenerated ben file looks fine
> and ros-perception-pcl builds against the new version. For python-pcl I
> will upload a fixed version myself.

Please go ahead

Cheers

> 
> Cheers Jochen
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth headphones

[Laurent Bigonville]

Hello,

On Thu, 26 Aug 2021 12:08:03 +0200 Vincent Lefevre  
wrote:


>
> After the upgrade to 15.0+dfsg1-2, pulseaudio no longer detects
> my bluetooth headphones when I switch them on.

As apparently there is a workaround and/or the problem is coming from 
bluez, do you think we should keep this bug RC and prevent the migration 
to unstable?


Kind regards,

Laurent Bigonville

Bug#995961: libapache2-mpm-itk: Error "AH00052: child pid exit signal Segmentation fault" after update to apache 2.4.51-1~deb11u1

[Jean Weisbuch]

I also have the issue on a custom compiled HTTPD and ITK, it's not a 
Debian specific bug ; it appeared between 2.4.48 and 2.4.49.



Here is a basic patch for 2.4.51 that comments the line that provokes 
the segfaults but it might break other things :


--- server/connection.c    2021-09-26 16:11:22.0 +0200
+++ server/connection.c    2021-10-11 17:00:17.868463811 +0200
@@ -156,7 +156,7 @@
 apr_socket_t *csd = ap_get_conn_socket(c);

 if (ap_start_lingering_close(c)) {
-    apr_socket_close(csd);
+//    apr_socket_close(csd);
 return;
 }

A "cleaner" patch, also for 2.4.51, that reverts the changes between 
2.4.48 and 2.4.49 on connection.c but keep the other changes ; i don't 
know what those changes could imply so i advise against using it on a 
production platform :


--- ./server/connection.c    2021-09-26 16:11:22.0 +0200
+++ ./server/connection.c    2021-10-11 17:15:04.232960328 +0200
@@ -139,12 +139,18 @@
 ap_flush_conn(c);

 #ifdef NO_LINGCLOSE
+    apr_socket_close(csd);
 return 1;
 #else
 /* Shut down the socket for write, which will send a FIN
  * to the peer.
  */
-    return (c->aborted || apr_socket_shutdown(csd, APR_SHUTDOWN_WRITE));
+    if (c->aborted
+    || apr_socket_shutdown(csd, APR_SHUTDOWN_WRITE) != 
APR_SUCCESS) {

+    apr_socket_close(csd);
+    return 1;
+    }
+    return 0;
 #endif
 }

@@ -156,7 +162,6 @@
 apr_socket_t *csd = ap_get_conn_socket(c);

 if (ap_start_lingering_close(c)) {
-    apr_socket_close(csd);
 return;
 }

Bug#991367: fail2ban puts its configuration in wrong dir for monit

[Mike Gerber]

found 991367 0.11.2-2

thanks


This is also the case for bullseye/stable.

Bug#995743: RM: hardlink/0.3.2

[Paul Gevers]

Hi Chris,

On 05-10-2021 00:17, Chris Hofstaedtler wrote:
> please RM hardlink from testing, to allow util-linux to migrate.
> src:util-linux now ships the hardlink program, and on upgrades hardlink
> should get deconfigured/removed. See #992498 for additional background.

Let's see if a rm hint works. I fear britney doesn't really understand
the provides/conflicts/breaks combi to mean util-linux can replace it.
Hence not closing this bug yet.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#995796: [Python-modules-team] Bug#995796: python3-websocket: Please package newer upstream version

[Emmanuel Arias]

Hi,

Thanks for reporting it.

You report many things. I'll start working on them

Thanks

Cheers,
Arias Emmanuel
@eamanu
yaerobi.com


On Tue, Oct 5, 2021 at 5:51 PM Witold Baryluk 
wrote:

> Package: python3-websocket
> Version: 0.57.0-1
> Severity: minor
> X-Debbugs-Cc: witold.bary...@gmail.com
>
> Upstream is now at version 1.2.1
>
> https://pypi.org/project/websocket-client/#history
>
> https://github.com/websocket-client/websocket-client/compare/v0.57.0...v1.2.1
>
> It contains number of bugfixes and enhancements, that would be nice to
> have in Debian. There might be some breaking changes, that require
> veryfying reverse dependencies in Debian archive first.
>
> Reverse Depends:
>   Depends: python3-docker (>= 0.32.0~)
>   Depends: python3-streamlink
>   Depends: python3-ripe-atlas-cousteau
>   Depends: python3-zunclient
>   Depends: python3-ibm-watson
>   Depends: python3-socketio-client
>   Depends: python3-kubernetes
>   Depends: docker-compose (>= 0.32.0)
>   Depends: python3-pyocd
>   Depends: psychopy
>   Depends: python3-praw
>   Depends: obs-build
>   Depends: python3-azure-cli
>
>
> For my usage, the current python3-websocket 0.57.0 version, does not work
> properly (SSL related issues), and I needed to manually install 1.2.1
> using pip3. Would be nice to have this in Debian out of the box.
>
> I also noticed that debian/watch file for the package, does not work
> properly, as warned by linian:
>
> In debian/watch no matching files for watch line
>
> https://pypi.debian.net/websocket_client/websocket[-_]client-(.+)\.(?:zip|tgz|tbz|txz|(?:tar\.(?:gz|bz2|xz)))
> 
>
>
> However, from quick inspection of the server directory, it is unclear why
> it does not match any file.
>
> Also the new homepage appears to be
> https://github.com/websocket-client/websocket-client,
> but https://github.com/liris/websocket-client still works, as a redirect.
>
> Thanks.
>
> *** End of the template - remove these template lines ***
>
>
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.10.0-8-amd64 (SMP w/32 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)
> LSM: AppArmor: enabled
>
> Versions of packages python3-websocket depends on:
> ii  python3  3.9.2-3
> ii  python3-six  1.16.0-2
>
> python3-websocket recommends no packages.
>
> python3-websocket suggests no packages.
>
> -- no debconf information
>
> ___
> Python-modules-team mailing list
> python-modules-t...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
>

Bug#996174: wget: Spurious SSL_INIT in 1.21.2-1

[Bob Proulx]

Package: wget
Version: 1.21.2-1
Severity: normal

In today's daily upgrade wget 1.21.2-1 was installed and now emits a
spurious "SSL_INIT" message.  This is breaking scripts. :-(

$ wget -q -O/dev/null https://www.example.com/
SSL_INIT

A temporary workaround is to downgrade to the previous and hold it.

apt-get install wget=1.21-1+b1  # temporary hack
apt-mark hold wget  # temporary hack

Thank you for maintaining wget.

Bob


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

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

Versions of packages wget depends on:
ii  libc6 2.32-4
ii  libgnutls30   3.7.2-2
ii  libidn2-0 2.3.2-2
ii  libnettle83.7.3-1
ii  libpcre2-8-0  10.36-2
ii  libpsl5   0.21.0-1.2
ii  libuuid1  2.37.2-3
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages wget recommends:
ii  ca-certificates  20211004

wget suggests no packages.

-- no debconf information

Bug#988597: trash-cli version too old

[Andrea Francia]

Hi Jonathan,
  thank you for your work.

In order to help I need to be able to reproduce the failures by myself.
Can you explain to me how to do it? For example, which command
do you use for launching the tests under chroot?


Il giorno gio 30 set 2021 alle ore 11:04 Jonathan Dowland 
ha scritto:

> On Tue, Sep 28, 2021 at 11:21:52PM +0100, Jonathan Dowland wrote:
> >I've begun work on updating to 0.21.7.24. I've pushed my in-progress
> >work here:
> >
>
> I've resolved the test_bump issue (remove it) as well as the next
> significant problem, which was the assumption that '/usr/bin/env python'
> will launch a python3 interpreter. This will never be true in Debian.
> I've patched that everywhere, I think. (Note: I was a little surprised
> that I had to patch setup.py *and* the generated binaries, as "python3.9
> setup.py clean" re-generates them)
>
> A huge chunk of tests are failing still, I've attached a list to this
> mail. Feel free to help try and figure out why!
>
>
> --
> Jonathan Dowland
> ✎j...@debian.org
>   https://jmtd.net
>


-- 
Andrea Francia http://andreafrancia.it

Bug#996173: zfsutils-linux: /etc/exports.d/zfs.exports incorrectly generated when dataset has a space in its mountpoint name

[James Youngman]

Package: zfsutils-linux
Version: 2.0.3-9
Severity: important

"zfs share" generates this /etc/exports.d/zfs.exports file:

# !!! DO NOT EDIT THIS FILE MANUALLY !!!

/nas/video/TV/Historical Drama 
192.168.15.0/24(sec=sys,rw,no_subtree_check,mountpoint)
/nas/video/TV/Historical Drama 
192.168.122.0/24(sec=sys,ro,no_subtree_check,mountpoint)


The problem is that spaces are not allowed in the path name.  Per `man
5 exports`:

Blank lines are ignored.  A pound sign ("#") introduces a comment to
the end of the line. En‐ tries may be continued across newlines using
a backslash. If an export name contains spaces it should be quoted
using double quotes. You can also specify spaces or other unusual
character in the export name using a backslash followed by the
character code as three octal digits.

The relevant zfs datasets look like this:

$ sudo zfs list | grep Historical
zpool2/video/TV/Historical_Drama  352G  1.59T  352G  
/nas/video/TV/Historical Drama

$ sudo zfs get all zpool2/video/TV/Historical_Drama
NAME  PROPERTY  VALUE   
  SOURCE
zpool2/video/TV/Historical_Drama  type  filesystem  
  -
zpool2/video/TV/Historical_Drama  creation  Wed Dec 13 15:31 2017   
  -
zpool2/video/TV/Historical_Drama  used  352G
  -
zpool2/video/TV/Historical_Drama  available 1.59T   
  -
zpool2/video/TV/Historical_Drama  referenced352G
  -
zpool2/video/TV/Historical_Drama  compressratio 1.00x   
  -
zpool2/video/TV/Historical_Drama  mounted   yes 
  -
zpool2/video/TV/Historical_Drama  quota none
  default
zpool2/video/TV/Historical_Drama  reservation   none
  default
zpool2/video/TV/Historical_Drama  recordsize128K
  default
zpool2/video/TV/Historical_Drama  mountpoint
/nas/video/TV/Historical Dramalocal
zpool2/video/TV/Historical_Drama  sharenfs  
rw=@192.168.15.0/24,ro=@192.168.122.0/24,rw=192.168.122.100,rw=10.10.1.2  
inherited from zpool2
zpool2/video/TV/Historical_Drama  checksum  on  
  default
zpool2/video/TV/Historical_Drama  compression   on  
  inherited from zpool2
zpool2/video/TV/Historical_Drama  atime on  
  default
zpool2/video/TV/Historical_Drama  devices   on  
  default
zpool2/video/TV/Historical_Drama  exec  on  
  default
zpool2/video/TV/Historical_Drama  setuidon  
  default
zpool2/video/TV/Historical_Drama  readonly  off 
  default
zpool2/video/TV/Historical_Drama  zoned off 
  default
zpool2/video/TV/Historical_Drama  snapdir   hidden  
  default
zpool2/video/TV/Historical_Drama  aclmode   discard 
  default
zpool2/video/TV/Historical_Drama  aclinheritrestricted  
  default
zpool2/video/TV/Historical_Drama  createtxg 14679   
  -
zpool2/video/TV/Historical_Drama  canmount  on  
  default
zpool2/video/TV/Historical_Drama  xattr on  
  default
zpool2/video/TV/Historical_Drama  copies1   
  default
zpool2/video/TV/Historical_Drama  version   5   
   

Bug#995961: libapache2-mpm-itk: Error "AH00052: child pid exit signal Segmentation fault" after update to apache 2.4.51-1~deb11u1

[Steinar H. Gunderson]

On Mon, Oct 11, 2021 at 06:06:04PM +0200, Jean Weisbuch wrote:
> Seems like re-compiling mpm-itk (using the exact same sourcecode as the
> previous time i compiled it) and even without any patch applied to HTTPD
> 2.4.51 did also fix the issue for me.

It seems to me that this is only in bullseye-proposed-updates, not actually a
security update yet? If it breaks mpm-itk and nobody really knows why,
I would say that's a good reason to stop the proposal process of the package.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#931345: nvchecker: autopkgtest regression in June 2019

[Paul Gevers]

Hi Afif,

On 10-10-2021 22:56, Afif Elghraoui wrote:
>> The test if timing out nowadays too, so I'll block it from being tested
>> to avoid stress on our infrastructure until this bug is fixed.
> 
> This bug has been fixed for about a week now but nvchecker still appears
> to be blocked from debci. Does that need to be manually changed? I
> expected it to be removed automatically once the bug was closed.

Ah, sorry, I somehow missed it. I'll lift the block in some minutes.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#996167: dpkg: unrecoverable fatal error, aborting: unknown system group 'plocate' in statoverride file;

[Steinar H. Gunderson]

On Mon, Oct 11, 2021 at 06:17:51PM +, Thorsten Glaser wrote:
>> Is there any good reason why the plocate group would disappear
>> that you know of?
> Not that… wait, doesn’t schroot copy groups? Let me see…
> 
> AH! It does! And since my main system is now
> bullseye, not sid, this is the first time it broke. In this
> case, my sincere apology for the report.

Thanks for the quick reply!

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#994778: closed by Debian FTP Masters (reply to Eduard Bloch ) (Bug#994778: fixed in apt-cacher-ng 3.7.3-1)

[corubba]

Dear Maintainer,

unfortunately the bug is not yet fully fixed.

These do work now as expected:
BindAddress=::   -> binds to [::]:3142
BindAddress=:::1 -> throws an "invalid address" error
BindAddress=[::]:1   -> binds to [::]:1
BindAddress=1::  -> binds to [1::]:3142
BindAddress=::1  -> binds to [::1]:3142
BindAddress=[1::1]   -> binds to [1::1]:3142
BindAddress=[1:2:3:4:5:6:7:8]-> binds to [1:2:3:4:5:6:7:8]:3142
BindAddress=[1:2::7:8]   -> binds to [1:2::7:8]:3142
BindAddress=[1:2:3:4:5:6:7:::8]  -> throws an "invalid address" error
BindAddress=[1:2:3:4:5:6:7:8:9]  -> throws an "invalid address" error

These still don't work as expected:
BindAddress=1::1 -> binds to nothing, should be [1::1]:3142
BindAddress=1:2:3:4:5:6:7:8  -> binds to nothing, should be 
[1:2:3:4:5:6:7:8]:3142
BindAddress=1:2::7:8 -> binds to [1:2::7]:8 but should be 
[1:2::7:8]:3142
BindAddress=1:2:3:4:5:6:7:::8-> binds to [1:2:3:4:5:6:7::]:8 but should throw an 
"invalid address" error
BindAddress=1:2:3:4:5:6:7:8:9-> binds to [1:2:3:4:5:6:7:8]:9 but should throw an 
"invalid address" error

Bug#996172: hexchat: Lua plugin should be included in Recommends and Description

[Jesse Rhodes]

Package: hexchat
Version: 2.14.3-6
Severity: minor
X-Debbugs-Cc: je...@sney.ca

Hello mapreri :) ,

The lua plugin has been included in hexchat since 2.12.1. Since then, it has 
become upstream's preferred language for add-on scripts. 

So, it should be treated the same as the perl and python plugins, and be 
included in both the main hexchat package's long description and Recommends 
field. 

I'm attaching a d/control file with the changes. (The lua plugin's description 
also has my old justification of "previously included in the main hexchat 
package..." for the lua plugin this isn't true, since it didn't exist yet when 
there was only 1 monolithic package. But I didn't change that as I'm not sure 
what should go there instead.)

Best, and thanks for your work,

Jesse (sney)

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

Kernel: Linux 5.14.0-1-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.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 hexchat depends on:
ii  hexchat-common   2.14.3-6
ii  libc62.32-4
ii  libcanberra0 0.30-8
ii  libdbus-glib-1-2 0.112-2
ii  libgdk-pixbuf-2.0-0  2.42.6+dfsg-2
ii  libglib2.0-0 2.70.0-1+b1
ii  libgtk2.0-0  2.24.33-2
ii  libnotify4   0.7.9-3
ii  libpango-1.0-0   1.48.10+ds1-1
ii  libproxy1v5  0.4.17-1
ii  libssl1.11.1.1l-1
ii  libx11-6 2:1.7.2-2+b1

Versions of packages hexchat recommends:
ii  ca-certificates  20210119
ii  hexchat-perl 2.14.3-6
ii  hexchat-plugins  2.14.3-6
ii  hexchat-python3  2.14.3-6
ii  libglib2.0-bin   2.70.0-1+b1

Versions of packages hexchat suggests:
pn  hexchat-otr  
ii  unifont  1:13.0.06-2

-- no debconf information
Source: hexchat
Section: net
Priority: optional
Maintainer: Mattia Rizzolo 
Build-Depends:
 debhelper-compat (= 13),
 gettext,
 iso-codes,
 libcanberra-dev,
 libdbus-glib-1-dev,
 libglib2.0-dev,
 libgtk2.0-dev,
 liblua5.3-dev,
 libpci-dev,
 libperl-dev,
 libssl-dev,
 meson,
 python3-cffi,
 python3-dev (>= 3.3),
Standards-Version: 4.6.0
Rules-Requires-Root: no
Vcs-Git: https://salsa.debian.org/debian/hexchat.git
Vcs-Browser: https://salsa.debian.org/debian/hexchat
Homepage: https://hexchat.github.io

Package: hexchat
Architecture: any
Provides:
 irc,
Depends:
 hexchat-common (= ${source:Version}),
 ${misc:Depends},
 ${shlibs:Depends},
Recommends:
 ca-certificates,
 hexchat-lua,
 hexchat-perl,
 hexchat-plugins,
 hexchat-python3,
 libglib2.0-bin,
Suggests:
 hexchat-otr,
 unifont,
Description: IRC client for X based on X-Chat 2
 HexChat is a graphical IRC client with a GTK+ GUI. Features include Python,
 Perl, and Lua scripting support, a plugin API, multiple server/channel 
 windows, spell checking, multiple authentication methods including SASL,
 and customizable notifications. For more information on IRC, see 
 http://irchelp.org/.

Package: hexchat-common
Architecture: all
Multi-Arch: foreign
Provides:
 irc,
Depends:
 ${misc:Depends},
Recommends:
 hexchat,
Description: Common files for HexChat
 This package includes documentation, headers, and locale files for the
 Debian HexChat packages that are common for all architectures. Hexchat is a
 popular and featureful IRC client with a GTK+ GUI. For more information on
 IRC, see http://irchelp.org/.

Package: hexchat-perl
Architecture: any
Multi-Arch: same
Depends:
 ${misc:Depends},
 ${shlibs:Depends},
Recommends:
 hexchat,
Description: Perl plugin for HexChat
 This package contains the perl plugin for HexChat. Previously included in the
 main HexChat package, it's now separate as it's not actually required for core
 functionality.

Package: hexchat-python3
Architecture: any
Multi-Arch: same
Depends:
 python3-cffi-backend,
 ${misc:Depends},
 ${shlibs:Depends},
Recommends:
 hexchat,
Description: Python 3 plugin for HexChat
 This package contains the Python 3 plugin for HexChat. Previously included in
 the main HexChat package, it's now separate as it's not actually required for
 core functionality.

Package: hexchat-lua
Architecture: any
Multi-Arch: same
Depends:
 ${misc:Depends},
 ${shlibs:Depends},
Recommends:
 hexchat,
Description: Lua plugin for HexChat
 This package contains the Lua plugin for Hexchat.
 Previously included in the main HexChat package, it's now separate as it's not
 actually required for core functionality.

Package: hexchat-plugins
Architecture: any
Multi-Arch: same
Depends:
 ${misc:Depends},
 ${shlibs:Depends},
Recommends:
 hexchat,
 pci.ids,
Description: Common plugins for HexChat
 This package contains the FiSHLiM, Sysinfo, Do At and Checksum plugins.
 Previously included in the main HexChat package, they're now separate as
 they're not actually required for core functionality.

Package: hexchat-dev
Architecture: any

Bug#996107: budgie-desktop: compatibility with mutter 41

[Simon McVittie]

On Mon, 11 Oct 2021 at 13:20:31 +0100, David Mohammed wrote:
> On Mon, 11 Oct 2021 at 11:27, Simon McVittie  wrote:
> > Please test budgie-desktop against mutter 41 (libmutter-9), and initially
> > upload to experimental.
>
> I can do it ... but it will have to wait until the weekend at a
> minimum since I am preparing for Ubuntu 21.10 release this week.  Hope
> thats ok.

No problem, whenever you have time to work on this is fine! I wanted
to get a bug open so we could keep track of what the blockers are for
finishing GNOME 41 packaging.

Thanks,
smcv

Bug#996171: glibmm2.4: FTBFS on buildds / reproducible builds without network access

[Aurelien Jarno]

Source: glibmm2.4
Version: 2.66.2-1
Severity: serious
Tags: upstream ftbfs
Justification: Debian Policy 4.9 

According to Debian Policy 4.9:

| For packages in the main archive, required targets must not attempt
| network access, except, via the loopback interface, to services on the
| build host that have been started by the build.

However the giomm_tls_client test in glibmm2.4 tries to connect to
https://www.gnome.org and fails to build if that host is not accessible:

| Summary of Failures:
| 
| 34/34 giomm_tls_client_testTIMEOUT30.03s   killed by 
signal 15 SIGTERM
| 
| 
| Ok: 33  
| Expected Fail:  0   
| Fail:   0   
| Unexpected Pass:0   
| Skipped:0   
| Timeout:1   
| dh_auto_test: error: cd obj-riscv64-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=4 meson test returned exit code 1
| make: *** [debian/rules:7: build-arch] Error 25
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

The full build log can be found there:
https://buildd.debian.org/status/fetch.php?pkg=glibmm2.4=riscv64=2.66.2-1=1633924088=0

When instead the build happens with only the localhost interface, it
fails in a slightly different way:

| Summary of Failures:
| 
| 14/34 giomm_tls_client_testFAIL0.15s   killed by 
signal 6 SIGABRT
| 
| 
| Ok: 33  
| Expected Fail:  0   
| Fail:   1   
| Unexpected Pass:0   
| Skipped:0   
| Timeout:0   
| dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=15 meson test returned exit code 1
| make: *** [debian/rules:7: binary] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2
| 
| The full build log can be found there:
| 
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/glibmm2.4_2.66.1-1.rbuild.log.gz

Bug#996167: dpkg: unrecoverable fatal error, aborting: unknown system group 'plocate' in statoverride file;

[Steinar H. Gunderson]

On Mon, Oct 11, 2021 at 07:33:19PM +0200, Thorsten Glaser wrote:
> Package: plocate
> Version: 1.1.12-1
> Severity: critical
> Justification: breaks unrelated software
> X-Debbugs-Cc: t...@mirbsd.de
> 
> I'm encountering this:
> 
> [... apt-get dist-upgrade ...]

Can you say something about what you are upgrading from and to?
Is there any good reason why the plocate group would disappear
that you know of?

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#996170: linux: FTBFS if bpftool detects clang-bpf-co-re

[Nathaniel Wesley Filardo]

Source: linux
Version: 5.10.70-1
Severity: serious
Tags: ftbfs patch upstream
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: nwfila...@gmail.com

Dear Maintainer,

Attempting to build kernel packages using the machinery of
https://salsa.debian.org/kernel-team/linux.git on a host where the
"clang-bpf-co-re" test performed in the tools/bpf/bpftool directory passes will
fail, as the build will attempt to bootstrap the BTF vmlinux.h header
(confusingly, from the kernel in /boot/vmlinux-$(uname -r), as it can't find
anything else); for example:

> /dozer/scratch/nwf/tmp/linux/debian-kernel-linux/debian/build/build-tools/tools/bpf/bpftool/bpftool-bootstrap
>  btf dump file /boot/vmlinux-5.10.0-0.bpo.5-powerpc64le format c > 
> /dozer/scratch/nwf/tmp/linux/debian-kernel-linux/debian/build/build-tools/tools/bpf/bpftool/vmlinux.h
> Error: failed to load BTF from /boot/vmlinux-5.10.0-0.bpo.5-powerpc64le: No 
> such file or directory

The official builders do not pass this test (see, e.g.
https://buildd.debian.org/status/fetch.php?pkg=linux=ppc64el=5.14.9-2=1633298169=0
where the logs say "clang-bpf-co-re: [ OFF ]"), so I believe the correct answer
on Debian systems is to disable the test (making it appear as if it fails)
regardless of the host environment.  The patch below does exactly that and
allows me to build the kernel packages.

Cheers,
--nwf;

--- a/tools/bpf/bpftool/Makefile2021-10-11 01:52:26.625003863 +0100
+++ b/tools/bpf/bpftool/Makefile2021-10-11 03:38:54.006277839 +0100
@@ -62,8 +62,7 @@
 LLVM_STRIP ?= llvm-strip
 
 FEATURE_USER = .bpftool
-FEATURE_TESTS = libbfd disassembler-four-args reallocarray zlib libcap \
-   clang-bpf-co-re
+FEATURE_TESTS = libbfd disassembler-four-args reallocarray zlib libcap
 FEATURE_DISPLAY = libbfd disassembler-four-args zlib libcap \
clang-bpf-co-re
 

Bug#996031: nvidia-driver breaks 'apt-get update' when kernel 5.14.6 is candidate kernel

[js jb]

I should add that making nvidia-driver conflict with later kernel versions for 
which it has not been tested is only an *example* solution,but clearly not the 
only way to keep apt-get upgrade working properly with nvidia-driver.
A more flexible solution would be to create an optional dummy package, 
nvidia-dkms-compat, with the same version as nvidia-kernel-dkmsbut which 
conflicts with later kernel versions than the ones where nvidia-kernel-dkms was 
tested.
Users that want to keep the current informal status can avoid installing 
nvidia-dkms-compat and rely on the description of nvidia-driver to choose newer 
kernel versions.

Users that do install nvidia-dkms-compat will be alerted through the usual apt 
methods that there is an incompatibility with a newer kernel.
Regardless of how this is solved, I think an important goal is that apt-get 
upgrade should work properly when nvidia-kernel-dkms is installed;this means 
that a newer kernel on which nvidia does not build will not be installed by 
default, not appear as a candidate upgrade version.

thanks,--jack

Bug#996167: dpkg: unrecoverable fatal error, aborting: unknown system group 'plocate' in statoverride file;

[Thorsten Glaser]

Dixi quod…

>dpkg: unrecoverable fatal error, aborting:
> unknown system group 'plocate' in statoverride file; the system group got 
> removed
>before the override, which is most probably a packaging bug, to recover you
>can remove the override manually with dpkg-statoverride

Before I do that, its contents:

(sid-amd64)root@tglase:~ # grep . /var/lib/dpkg/statoverride*
/var/lib/dpkg/statoverride:root plocate 2755 /usr/bin/plocate
/var/lib/dpkg/statoverride:root smmsp 2755 /usr/libexec/sendmail/sendmail
/var/lib/dpkg/statoverride:root smmsp 2755 /usr/libexec/sendmail/mailstats
/var/lib/dpkg/statoverride:root messagebus 4754 
/usr/lib/dbus-1.0/dbus-daemon-launch-helper
/var/lib/dpkg/statoverride-old:root plocate 2755 /usr/bin/plocate
/var/lib/dpkg/statoverride-old:root mlocate 2755 /usr/bin/mlocate
/var/lib/dpkg/statoverride-old:root smmsp 2755 /usr/libexec/sendmail/sendmail
/var/lib/dpkg/statoverride-old:root smmsp 2755 /usr/libexec/sendmail/mailstats
/var/lib/dpkg/statoverride-old:root messagebus 4754 
/usr/lib/dbus-1.0/dbus-daemon-launch-helper
(sid-amd64)root@tglase:~ # ll /var/lib/dpkg/statoverride*
-rw-r--r-- 1 root root 195 Oct  7 23:03 /var/lib/dpkg/statoverride
-rw-r--r-- 1 root root 230 Oct  7 23:03 /var/lib/dpkg/statoverride-old

The timestamp matches the previous upgrade.

bye,
//mirabilos
-- 
[...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but
what about xfs, and if only i had waited until reiser4 was ready... in the be-
ginning, there was ffs, and in the middle, there was ffs, and at the end, there
was still ffs, and the sys admins knew it was good. :)  -- Ted Unangst über *fs

Bug#995645: RFS: python-certbot-dns-standalone/1.0.3-1 [ITP] -- Standalone DNS plugin for Certbot with an integrated DSN server

[Jeroen Ploemen]

Control: tags -1 moreinfo

On Sun, 3 Oct 2021 18:24:34 +0300
Linus Vanas  wrote:

> I am looking for a sponsor for my package
> python-certbot-dns-standalone:

hi Linus,

The package doesn't build or install any documentation, although
upstream provides both sphinx docs and a readme file. End users
would definitely benefit from having those available to them.

Lintian identified a minor issue:
  * P: python-certbot-dns-standalone source: trailing-whitespace
debian/changelog (line 3)

Control:
  * Typo in short description? ("dsn")
  * Upstream's very own description of their project ("Standalone DNS
Authenticator plugin for Certbot") looks like a prefect short
description. Implementation details such as an integrated dns
server can go in the long description.

Watch:
  * The uversionmangle seems pointless as it doesn't match any
version ever tagged/released by upstream.

And lastly, please enable the CI on salsa. It is a most useful
quality control tool, and a significant time saver for reviewers too.


Please remove the moreinfo tag (and CC me directly) once you have an
updated package ready.


pgpewp3KGOCHu.pgp
Description: OpenPGP digital signature

Bug#996168: retext does not start: xsettings.py:126 RuntimeError: ffi_prep_cif_var failed

[Renzo Davoli]

Package: retext
Version: 7.2.1-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: re...@cs.unibo.it

Dear Maintainer,

This is the traceback of the error.
~$ retext
Using configuration file: /home/renzo/.config/ReText project/ReText.conf
Traceback (most recent call last):
  File "/usr/bin/retext", line 9, in 
main()
  File "/usr/share/retext/ReText/__main__.py", line 107, in main
window = ReTextWindow()
  File "/usr/share/retext/ReText/window.py", line 76, in __init__
setIconThemeFromSettings()
  File "/usr/share/retext/ReText/config.py", line 76, in 
setIconThemeFromSettings
QIcon.setThemeName(get_icon_theme())
  File "/usr/share/retext/ReText/icontheme.py", line 49, in get_icon_theme
return (get_from_xsettings()
  File "/usr/share/retext/ReText/icontheme.py", line 20, in get_from_xsettings
xsettings = get_xsettings()
  File "/usr/share/retext/ReText/xsettings.py", line 189, in get_xsettings
raw_xsettings = get_raw_xsettings(display)
  File "/usr/share/retext/ReText/xsettings.py", line 126, in get_raw_xsettings
cookie = xcb.xcb_get_property(connection, 0, window, settings_atom, 0, 0, 
0x2000)
RuntimeError: ffi_prep_cif_var failed

If it can be of any help, as a workaround copying the directory icons from the
source to /usr/share/retext/ seems to fix the problem.

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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 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=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages retext depends on:
ii  python3 3.9.2-3
ii  python3-chardet 4.0.0-1
ii  python3-docutils0.16+dfsg-4
ii  python3-markdown3.3.4-1
ii  python3-markups 3.1.2-1
ii  python3-pygments2.7.1+dfsg-2.1
ii  python3-pyqt5   5.15.4+dfsg-4
ii  python3-pyqt5.qtwebkit  5.15.4+dfsg-4

Versions of packages retext recommends:
ii  docutils-common   0.16+dfsg-4
ii  libjs-mathjax 2.7.9+dfsg-1
ii  python3-enchant   3.2.0-1
ii  shared-mime-info  2.0-1

Versions of packages retext suggests:
ii  adwaita-icon-theme 41.0-1
ii  gir1.2-glib-2.01.70.0-2
ii  gsettings-desktop-schemas  41.0-1

-- no debconf information

Bug#996167: dpkg: unrecoverable fatal error, aborting: unknown system group 'plocate' in statoverride file;

[Thorsten Glaser]

Package: plocate
Version: 1.1.12-1
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: t...@mirbsd.de

I'm encountering this:

[... apt-get dist-upgrade ...]

Extracting templates from packages: 100%
dpkg: unrecoverable fatal error, aborting:
 unknown system group 'plocate' in statoverride file; the system group got 
removed
before the override, which is most probably a packaging bug, to recover you
can remove the override manually with dpkg-statoverride
E: Sub-process /usr/bin/dpkg returned an error code (2)


Related log from /var/log/apt/term.log from the PREVIOUS upgrade:


Log started: 2021-10-07  22:55:21
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 270379 files and directories currently installed.)
Preparing to unpack .../base-files_12_amd64.deb ...
Unpacking base-files (12) over (11.1) ...
Setting up base-files (12) ...
Installing new version of config file /etc/debian_version ...
Installing new version of config file /etc/issue ...
Installing new version of config file /etc/issue.net ...
[...]
Preparing to unpack .../107-mlocate_1.1.12-1_all.deb ...
Unpacking mlocate (1.1.12-1) over (0.26-5) ...
Selecting previously unselected package plocate.
Preparing to unpack .../108-plocate_1.1.12-1_amd64.deb ...
Unpacking plocate (1.1.12-1) ...
[...]
Setting up plocate (1.1.12-1) ...
Installing new version of config file /etc/updatedb.conf ...
update-alternatives: warning: alternative /usr/bin/mlocate (part of link group 
locate) doesn't exist; removing from list of alternatives
update-alternatives: warning: /etc/alternatives/locate is dangling; it will be 
updated with best choice
update-alternatives: using /usr/bin/plocate to provide /usr/bin/locate (locate) 
in auto mode
Adding group `plocate' (GID 158) ...
cannot connect to /var/run/nscd/socket
cannot connect to /var/run/nscd/socket
cannot connect to /var/run/nscd/socket
cannot connect to /var/run/nscd/socket
cannot connect to /var/run/nscd/socket
Done.
[...]


Severity accordingly because this breaks dpkg and requires
manual recovery.


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

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

Versions of packages plocate depends on:
ii  libc6   2.32-4
ii  libgcc-s1   11.2.0-8
ii  libstdc++6  11.2.0-8
ii  liburing1   0.7-3
ii  libzstd11.4.8+dfsg-3

plocate recommends no packages.

Versions of packages plocate suggests:
pn  systemd-sysv | nocache 
pn  systemd-sysv | powermgmt-base  

-- no debconf information

Bug#993011: pulseaudio-module-bluetooth: no longer detects bluetooth headphones

[Vincent Lefevre]

Control: severity -1 minor

On 2021-10-11 17:35:04 +0200, Laurent Bigonville wrote:
> On Thu, 26 Aug 2021 12:08:03 +0200 Vincent Lefevre 
> wrote:
> 
> > After the upgrade to 15.0+dfsg1-2, pulseaudio no longer detects
> > my bluetooth headphones when I switch them on.
> 
> As apparently there is a workaround and/or the problem is coming from bluez,
> do you think we should keep this bug RC and prevent the migration to
> unstable?

This was apparently coming from the bluez cache. I haven't seen any
issue after the workaround. Lowering the severity to minor. I'm not
sure whether there's something to be done on the pulseaudio side,
except that if some other users are also affected, something should
be said in the NEWS.Debian file.

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

Bug#995678: Bug#995392: ghostscript: ps2pdf trashes some characters

[Vincent Lefevre]

On 2021-10-12 01:27:22 +0900, Norbert Preining wrote:
> > >   /usr/bin/ps2pdf chartest3.pdf out.pdf
> 
> Honestly, feeding PDF into "ps2pdf" is something new, and I am not
> surprised that this does not work.

I don't understand what you mean by "something new". This has been
mentioned for many years (either with gs directly, or via the ps2pdf
wrapper):

  https://stackoverflow.com/questions/5296667/pdftk-compression-option
  
https://stackoverflow.com/questions/10450120/optimize-pdf-files-with-ghostscript-or-other
  
https://askubuntu.com/questions/113544/how-can-i-reduce-the-file-size-of-a-scanned-pdf-file
  https://askubuntu.com/questions/207447/how-to-reduce-the-size-of-a-pdf-file
  
https://askubuntu.com/questions/589862/how-to-compress-more-than-one-at-a-time-pdf-files-from-terminal

etc.

> The description clearly states
>   ps2pdf - Convert PostScript to PDF using ghostscript
> PDF is **not** PostScript.

The description has not been updated. The gs description is clearer:

  gs - Ghostscript (PostScript and PDF language interpreter and
  previewer)

> Can you explain me what are you trying to do?

Compress PDF files, in particular by converting Type 1 fonts
to Type 1C fonts and including only glyphs that are used,
instead of the full fonts.

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

Bug#996165: Fwd: firmware-sof-signed: Sound/Mic does not work on Dell XPS 17 9710

[Juan Francisco Miranda Aguilar]

Package: firmware-sof-signed
Version: 1.7-1
Severity: important

Dear Maintainer,

I installed the firmware-sof-signed package on a Dell XPS 17 9710 and
still no sound nor mic was detected.
Any advise is welcome!

Thanks!

root@dell:/home/jf# lspci | grep audio
00:1f.3 Multimedia audio controller: Intel Corporation Tiger Lake-H HD
Audio Controller (rev 11)
root@dell:/home/jf# dmesg | egrep "audio|sof|snd"
[0.852738] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[0.852739] software IO TLB: mapped [mem
0x4e601000-0x52601000] (64MB)
[1.040833] integrity: Loaded X.509 cert 'Microsoft Windows
Production PCA 2011: a92902398e16c49778cd90f99e4f9ae17c55af53'
[1.040841] integrity: Loaded X.509 cert 'Microsoft Corporation
UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed522988a1bd4'
[2.470636] snd_hda_intel :00:1f.3: DSP detected with PCI
class/subclass/prog-if info 0x040100
[2.470791] snd_hda_intel :00:1f.3: SoundWire enabled on
CannonLake+ platform, using SOF driver
[2.510153] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with
PCI class/subclass/prog-if info 0x040100
[2.510215] sof-audio-pci-intel-tgl :00:1f.3: SoundWire enabled
on CannonLake+ platform, using SOF driver
[2.510247] sof-audio-pci-intel-tgl :00:1f.3: enabling device
( -> 0002)
[2.510477] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with
PCI class/subclass/prog-if 0x040100
[2.510517] sof-audio-pci-intel-tgl :00:1f.3: bound
:00:02.0 (ops i915_audio_component_bind_ops [i915])
[2.516978] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode
[2.531676] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 4
[2.532987] sof-audio-pci-intel-tgl :00:1f.3: firmware:
direct-loading firmware intel/sof/sof-tgl-h.ri
[2.532992] sof-audio-pci-intel-tgl :00:1f.3: Firmware info:
version 1:7:0-47d07
[2.533026] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI
3:18:1 Kernel ABI 3:18:0
[2.533028] sof-audio-pci-intel-tgl :00:1f.3: unknown
sof_ext_man header type 3 size 0x30
[2.614333] sof-audio-pci-intel-tgl :00:1f.3: Firmware info:
version 1:7:0-47d07
[2.614336] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI
3:18:1 Kernel ABI 3:18:0
[3.691121] sof-audio-pci-intel-tgl :00:1f.3: firmware:
direct-loading firmware intel/sof-tplg/sof-tgl-rt711-rt1308-rt715.tplg
[3.691129] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI
3:18:1 Kernel ABI 3:18:0
[3.710385] sof-audio-pci-intel-tgl :00:1f.3: ASoC: physical
link SDW3-Capture (id 4) not exist
[3.710389] sof-audio-pci-intel-tgl :00:1f.3: ASoC: topology:
could not load header: -22
[3.710526] sof-audio-pci-intel-tgl :00:1f.3: error: tplg
component load failed -22
[3.710531] sof-audio-pci-intel-tgl :00:1f.3: error: failed to
load DSP topology -22
[3.710532] sof-audio-pci-intel-tgl :00:1f.3: ASoC: error at
snd_soc_component_probe on :00:1f.3: -22
[3.710561] sof_sdw sof_sdw: ASoC: failed to instantiate card -22
[3.720900] sof_sdw sof_sdw: snd_soc_register_card failed -22
[3.720901] sof_sdw: probe of sof_sdw failed with error -22

Bug#996148: linux-image-4.19.0-18-amd64: VMware Multi-Writer Shared Disks (via Physical SCSI Bus Sharing) now reported as 512b

[Damian]

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

Dear Maintainer,

an upgrade from linux-image-4.19.0-17-amd64=4.19.194-3 to 
linux-image-4.19.0-18-amd64=4.19.208-1 rendered certain VMware virtual 
disks unusable.
The affected VMware VM utilizes ordinary non-shared disks attached to a 
VMware Paravirtual SCSI controller with no SCSI Bus Sharing. Those disks 
are fine under linux-image-4.19.0-17 as well as linux-image-4.19.0-18.
The system has another set of disks which are shared with a different 
VM, by using a second VMware Paravirtual SCSI controller whose SCSI Bus 
Sharing is set to "Physical". Under linux-image-4.19.0-17, those disks 
work as indended, under linux-image-4.19.0-18, they are reported to be 
512b in size. Those 512b (under linux-image-4.19.0-18-amd64) are 
identical to the first 512b of the full-sized device under 
linux-image-4.19.0-17-amd64.


-- Package-specific info:
** Version:
Linux version 4.19.0-18-amd64 (debian-ker...@lists.debian.org) (gcc 
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.208-1 (2021-09-29)


** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-18-amd64 root=/dev/mapper/vg0-root ro quiet

** Not tainted

** Kernel log (only storage related lines):
[    0.764041] Block layer SCSI generic (bsg) driver version 0.4 loaded 
(major 247)

[    0.940902] SCSI subsystem initialized
[    0.943488] VMware PVSCSI driver - version 1.0.7.0-k
[    0.943748] vmw_pvscsi: using 64bit dma
[    0.943850] vmw_pvscsi: max_id: 16
[    0.943851] vmw_pvscsi: setting ring_pages to 8
[    0.963320] vmw_pvscsi: enabling reqCallThreshold
[    0.963524] vmw_pvscsi: driver-based request coalescing enabled
[    0.963525] vmw_pvscsi: using MSI-X
[    0.963599] scsi host0: VMware PVSCSI storage adapter rev 2, 
req/cmp/msg rings: 8/8/1 pages, cmd_per_lun=254

[    0.963859] vmw_pvscsi :03:00.0: VMware PVSCSI rev 2 host #0
[    0.964092] vmw_pvscsi: using 64bit dma
[    0.964143] vmw_pvscsi: max_id: 16
[    0.964143] vmw_pvscsi: setting ring_pages to 8
[    0.964211] scsi 0:0:0:0: Direct-Access VMware   Virtual disk 
2.0  PQ: 0 ANSI: 6
[    0.964910] scsi 0:0:1:0: Direct-Access VMware   Virtual disk 
2.0  PQ: 0 ANSI: 6

[    0.971186] vmw_pvscsi: enabling reqCallThreshold
[    0.971400] vmw_pvscsi: driver-based request coalescing enabled
[    0.971401] vmw_pvscsi: using MSI-X
[    0.971477] scsi host1: VMware PVSCSI storage adapter rev 2, 
req/cmp/msg rings: 8/8/1 pages, cmd_per_lun=254

[    0.971661] vmw_pvscsi :04:00.0: VMware PVSCSI rev 2 host #1
[    0.972202] ata_piix :00:07.1: version 2.13
[    0.976312] scsi 1:0:0:0: Direct-Access VMware   Virtual disk 
2.0  PQ: 0 ANSI: 6

[    0.976343] scsi host2: ata_piix
[    0.976835] scsi 1:0:1:0: Direct-Access VMware   Virtual disk 
2.0  PQ: 0 ANSI: 6
[    0.984002] sd 0:0:0:0: [sda] 2097152 512-byte logical blocks: (1.07 
GB/1.00 GiB)

[    0.984017] sd 0:0:0:0: [sda] Write Protect is off
[    0.984017] sd 0:0:0:0: [sda] Mode Sense: 31 00 00 00
[    0.984033] sd 0:0:0:0: [sda] Cache data unavailable
[    0.984033] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    0.984205] sd 0:0:1:0: [sdb] 33554432 512-byte logical blocks: (17.2 
GB/16.0 GiB)

[    0.984223] sd 0:0:1:0: [sdb] Write Protect is off
[    0.984224] sd 0:0:1:0: [sdb] Mode Sense: 31 00 00 00
[    0.984236] sd 0:0:1:0: [sdb] Cache data unavailable
[    0.984236] sd 0:0:1:0: [sdb] Assuming drive cache: write through
[    0.985425] scsi host3: ata_piix
[    0.985463] ata1: PATA max UDMA/33 cmd 0x1f0 ctl 0x3f6 bmdma 0x1060 
irq 14
[    0.985464] ata2: PATA max UDMA/33 cmd 0x170 ctl 0x376 bmdma 0x1068 
irq 15

[    0.986026]  sda: sda1
[    0.986203] sd 0:0:0:0: [sda] Attached SCSI disk
[    0.986237] sd 1:0:0:0: [sdc] Sector size 0 reported, assuming 512.
[    0.986381] sd 1:0:0:0: [sdc] 1 512-byte logical blocks: (512 B/512 B)
[    0.986382] sd 1:0:0:0: [sdc] 0-byte physical blocks
[    0.986403] sd 1:0:0:0: [sdc] Write Protect is off
[    0.986404] sd 1:0:0:0: [sdc] Mode Sense: 31 00 00 00
[    0.986418] sd 1:0:0:0: [sdc] Cache data unavailable
[    0.986418] sd 1:0:0:0: [sdc] Assuming drive cache: write through
[    0.986805] sd 1:0:1:0: [sdd] Sector size 0 reported, assuming 512.
[    0.986845] sd 1:0:1:0: [sdd] 1 512-byte logical blocks: (512 B/512 B)
[    0.986846] sd 1:0:1:0: [sdd] 0-byte physical blocks
[    0.986856] sd 1:0:1:0: [sdd] Write Protect is off
[    0.986857] sd 1:0:1:0: [sdd] Mode Sense: 31 00 00 00
[    0.986867] sd 1:0:1:0: [sdd] Cache data unavailable
[    0.986868] sd 1:0:1:0: [sdd] Assuming drive cache: write through
[    0.987074] sd 1:0:0:0: [sdc] Sector size 0 reported, assuming 512.
[    0.987668] Dev sdc: unable to read RDB block 1
[    0.987719]  sdc: unable to read partition table
[    0.987720] sdc: partition table beyond EOD, enabling native capacity
[    0.988215] sd 1:0:1:0: [sdd] Sector size 0 reported, assuming 512.
[    0.988463] sd 0:0:1:0: [sdb] Attached SCSI disk
[    0.988677] Dev sdd: 

Bug#996115: apt upgrade --no-download --fix-missing --auto-remove: "E: Internal error, InstallPackages was called with broken packages!"

[Jakub Wilk]

This is how to reproduce this in a bullseye chroot:

  apt install --no-install-recommends -y gcc libfido2-1
  echo 'deb http://ftp.debian.org/debian unstable main' >> /etc/apt/sources.list
  apt update
  apt install -yd libfido2-1
  apt upgrade --no-download --fix-missing --auto-remove

--
Jakub Wilk

Bug#995926: Error validating Let's Encrypt cert chains

[Andreas Metzler]

Control: reassign -1 lftp 4.8.4-2

On 2021-10-11 Andreas Metzler  wrote:
> On 2021-10-08 Andre Heider  wrote:
>> Source: gnutls28
>> Version: 3.7.2-2

>> Apps using gnutls fail to connect to servers using a Let's Encrypt
>> certificate which are cross-signed by the now expired DST Root CA X3, see
>> [0].

>> Examples:

>> $ lftp https://shop.bbc.com
>> cd: Fatal error: Certificate verification: Not trusted
>> (93:3C:6D:DE:E9:5C:9C:41:A4:0F:9F:50:49:3D:82:BE:03:AD:87:BF)
> [...]
>> [0] https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/

> given that 
> gnutls-cli --port https shop.bbc.com
> works I suspect that it is not necessarily a GnuTLS problem.

This looks like
https://github.com/lavv17/lftp/issues/641
which has a fix in upstream GIT.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#655097: mrgt: Please make ifref default to name

[Eriberto Mota]

Hi guys,

Thanks a lot for your contribution.

I have good news. I have been working over MRTG with the upstream
(Tobias Oetiker) since last week. We already made several changes in
MRTG. The good news is Tobias liked this idea (make ifref default to
name) and he will approve my PR[1] soon (in few hours, I think).

[1] https://github.com/oetiker/mrtg/pull/51

Have a nice day.

Regards,

Eriberto

Bug#996163: tzdata: [INTL:fr] French templates translation

[Jean-Pierre Giraud]

Package: tzdata
Severity: wishlist
Tags: patch l10n

Hi!

Please find attached the updated french templates translation, 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

Jean-Pierre Giraud

Bug#995678: Bug#995392: ghostscript: ps2pdf trashes some characters

[Norbert Preining]

> >   /usr/bin/ps2pdf chartest3.pdf out.pdf

Honestly, feeding PDF into "ps2pdf" is something new, and I am not
surprised that this does not work.

The description clearly states
ps2pdf - Convert PostScript to PDF using ghostscript
PDF is **not** PostScript.

Can you explain me what are you trying to do?

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research  +  IFMGA Guide  +  TU Wien  +  TeX Live  + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#995926: Error validating Let's Encrypt cert chains

[Andreas Metzler]

X-Debbugs-Cc: Andre Heider , l...@packages.debian.org

On 2021-10-08 Andre Heider  wrote:
> Source: gnutls28
> Version: 3.7.2-2

> Apps using gnutls fail to connect to servers using a Let's Encrypt
> certificate which are cross-signed by the now expired DST Root CA X3, see
> [0].

> Examples:

> $ lftp https://shop.bbc.com
> cd: Fatal error: Certificate verification: Not trusted
> (93:3C:6D:DE:E9:5C:9C:41:A4:0F:9F:50:49:3D:82:BE:03:AD:87:BF)
[...]
> [0] https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/

Hello,

given that 
gnutls-cli --port https shop.bbc.com
works I suspect that it is not necessarily a GnuTLS problem.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#996070: gnome-shell-extension-sound-device-chooser: does not declare compatibility with GNOME Shell 41

[Simon McVittie]

Control: tags -1 + fixed-upstream

On Mon, 11 Oct 2021 at 13:17:30 -0300, Fabio A. De Muzio Tobich wrote:
> The compatibility with GNOME 41 was declared upstream [1].
> I didin't had the oportunity to test it yet, but soon as I do I'll upload
> a fixed version to experimental (and I will also be using the dependency 
> technique
> that you explained).

If the new upstream version continues to be compatible with Shell 40, you
could upload to unstable rather than experimental, like I did for
gnome-shell-extension-caffeine.

smcv

Bug#994457: r-cran-gnm autopkgtest needs to be adapted for lapack 3.10

[Sébastien Villemot]

Dear Heather,

Please find attached the patch that I am going to apply to r-cran-gnm
in Debian.

With this patch applied, the test now works with both lapack 3.9 and
3.10.

Feel free to use it (or not) for the next release of gnm.

Best wishes,

Le lundi 27 septembre 2021 à 12:01 +0100, Heather Turner a écrit :
> Hi Andreas,
> 
> Thanks for forwarding this bug report and thanks to Sébastien for the 
> detailed and accurate analysis. I will need to submit an update to CRAN, 
> which should be feasible in the next week or two. Is there a deadline that I 
> need to work to?
> 
> Best wishes,
> 
> Heather
> 
> On Mon, Sep 27, 2021, at 10:12 AM, Andreas Tille wrote:
> > Control: tags -1 upstream
> > Control: forwarded -1 Heather Turner 
> > 
> > Hi Heather,
> > 
> > the Debian packaged gnm recieved a bug report about a failing test in
> > connection with the upgrade to lapack 3.10.0 on the machine running the
> > test.  Please read the bug report below.
> > 
> > We admit we need your help to solve this issue that might affect
> > other systems as well.
> > 
> > Kind regards
> > 
> > Andreas.
> > 
> > On Thu, Sep 16, 2021 at 10:59:19AM +0200, Sébastien Villemot wrote:
> > > Package: r-cran-gnm
> > > Version: 1.1-1-2
> > > Severity: serious
> > > Tags: sid bookworm
> > > X-Debbugs-CC: debian...@lists.debian.org
> > > User: debian...@lists.debian.org
> > > Usertags: needs-update
> > > 
> > > Dear Maintainer,
> > > 
> > > Since the upload of lapack 3.10.0-1, the autopkgtest of r-cran-gnm
> > > fails in unstable. See for example:
> > > https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-gnm/15155026/log.gz
> > > 
> > > More precisely, test-biplot.R fails, because some results have the
> > > opposite sign compared to the one which is expected.
> > > 
> > > My understanding is that this comes from the SVD of barleyMatrix in
> > > that test file, which is different between lapack 3.9 and 3.10.
> > > Mathematically, the SVD is not unique, and lapack 3.10 returns a
> > > different (still valid) solution. More precisely, I verified that one
> > > of the right-singular vector of that matrix has the opposite sign in
> > > lapack 3.10. I also verified that the decomposition is correct by
> > > checking that:
> > > 
> > >   max(abs(barleySVD$u %*% diag(barleySVD$d) %*% t(barleySVD$v) - 
> > > barleyMatrix))
> > > 
> > > is a small value (about 2e-14).
> > > 
> > > Also note that the hardcoded expected values already partially differ 
> > > from those of the original research paper mentioned in that test
> > > (Gabriel (1998): Generalised bilinear regression). More precisely, half
> > > of the values were hardcoded with the opposite sign. It seems that now
> > > all values need to be hardcoded with the opposite sign.
> > > 
> > > The testsuite of r-cran-gnm thus needs to be adapted, by being more
> > > tolerant to such sign changes.
> > > 
> > > N.B. : when trying to reproduce the problem, please ensure that your
> > > lapack alternative (as given by “update-alternatives --display
> > > liblapack.so.3-x86_64-linux-gnu) points to /usr/lib/x86_64-linux-
> > > gnu/lapack/liblapack.so.3, and not to the binary provided by either
> > > openblas or atlas (because these two have not yet been recompiled
> > > against lapack 3.10, and thus do not expose the problem).
> > > 
> > > Best regards,
> > > 
> > > -- 
> > > ⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
> > > ⣾⠁⢠⠒⠀⣿⡁  Debian Developer
> > > ⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
> > > ⠈⠳⣄  https://www.debian.org
> > > 
> > 
> > 
> > 
> > > ___
> > > R-pkg-team mailing list
> > > r-pkg-t...@alioth-lists.debian.net
> > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team
> > 
> > 
> > -- 
> > http://fam-tille.de

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

Description: Fix test-biplot.R with lapack 3.10
 With lapack 3.10, test-biplot.R fails, because some results have the
 opposite sign compared to the one which is expected.
 .
 This comes from the SVD of barleyMatrix in that test file, which is different
 between lapack 3.9 and 3.10. Mathematically, the SVD is not unique, and lapack
 3.10 returns a different (still valid) solution.
 .
 This patch accomodates sign differences in the columns of the test matrices,
 so that the test passes with both lapack 3.9 and lapack 3.10.
Author: Sébastien Villemot 
Bug-Debian: https://bugs.debian.org/994457
Forwarded: no
Last-Update: 2021-10-11
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/tests/testthat/test-biplot.R
+++ b/tests/testthat/test-biplot.R
@@ -6,6 +6,15 @@ set.seed(1)
 
 # Gabriel, K R (1998). Generalised bilinear regression. Biometrika 85, 689–700.
 
+expect_equivalent_up_to_column_sign <- function(A, B)
+{
+  ok <- nrow(A) == nrow(B) && ncol(A) == ncol(B)
+  if (ok)
+for (j in 1:ncol(A))
+  ok <- ok && (all(A[,j] == B[,j]) || all(A[,j] == 

Bug#996070: gnome-shell-extension-sound-device-chooser: does not declare compatibility with GNOME Shell 41

[Fabio A. De Muzio Tobich]

Em 10/10/2021 17:38, Simon McVittie escreveu:

Package: gnome-shell-extension-sound-device-chooser
Version: 38-2
Severity: normal
Tags: bookworm sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-41

The metadata.json for this extension doesn't declare compatibility with
GNOME 41. I don't know whether the actual code will need changes or not:
the conservative assumption is that it probably will (so please test).
gnome-shell 41 should be available in experimental soon.

In versions of GNOME Shell up to 3.38, metadata.json didn't matter much,
because validation of extensions' metadata against the installed Shell
version was disabled by default; but since GNOME 40 the default has changed
back to enabling the version check by default, in an effort to avoid
issues caused by outdated extensions remaining enabled. As a result,
GNOME Shell extensions in bookworm should probably have a dependency like:

 Depends: gnome-shell (>= x), gnome-shell (<< y~)

where x and y are set according to metadata.json.
gnome-shell-extension-caffeine is a good example of this technique.

When we do the GNOME Shell 41 transition, hopefully soon, we will have
to either update this extension or remove it from testing. It would be
useful to get a fixed version into experimental.

Thanks,
 smcv



Hi Simon,

Thanks for reporting this.

The compatibility with GNOME 41 was declared upstream [1].
I didin't had the oportunity to test it yet, but soon as I do I'll upload
a fixed version to experimental (and I will also be using the dependency 
technique
that you explained).

Again, thanks.

Cheers.

[1] 
https://github.com/kgshank/gse-sound-output-device-chooser/commit/209b5e554e22ff6931405231781da84a79880703

--
⢀⣴⠾⠻⢶⣦
⣾⠁⢠⠒⠀⣿⡁   Fabio Augusto De Muzio Tobich
⢿⡄⠘⠷⠚⠋⠀   9730 4066 E5AE FAC2 2683  D03D 4FB3 B4D3 7EF6 3B2E
⠈⠳⣄



OpenPGP_signature
Description: OpenPGP digital signature

Bug#996019: debootstrap: bootstrap of ubuntu impish is failing

[Sylvestre Ledru]

Hello


Le 10/10/2021 à 12:41, Sylvestre Ledru a écrit :
> Package: debootstrap
> Version: 1.0.124
> Severity: normal
>
> Dear Maintainer,
>
> $ sudo debootstrap impish impish 
> https://www-ftp.lip6.fr/pub/linux/distributions//Ubuntu/archive/ 
> I: impish uses zstd compression, setting --extractor=ar option
> I: Retrieving InRelease 
> I: Retrieving Packages 
> I: Validating Packages
> [...]
> I: Validating zlib1g 1:1.2.11.dfsg-2ubuntu7
> I: Chosen extractor for .deb packages: ar
> I: Extracting base-files...
> I: Extracting base-passwd...
> E: Extracting .//var/cache/apt/archives/base-passwd_3.5.51_amd64.deb requires 
> the zstdcat command, which is not available


> One needs to install zstd on the host, including zstd in the
debootstrap,set will not help.,,Does $ sudo apt install zstd => fix the
issue for you?

Yeah, it fixed my test case but my actual problem was:

$ export d=impish
$ export a=amd64
$ sudo DIST=$d ARCH=$a cowbuilder --create --basepath
/var/cache/pbuilder/base-$d-$a.cow --distribution $d --debootstrap
debootstrap --architecture $a --debootstrapopts --arch --debootstrapopts
amd64 --debootstrapopts --variant=buildd --configfile=/tmp/configfile
--hookdir /usr/share/jenkins-debian-glue/pbuilder-hookdir/
I: Invoking pbuilder
I: forking: pbuilder create --debootstrap debootstrap --debootstrapopts
--arch --debootstrapopts amd64 --debootstrapopts --variant=buildd
--configfile /tmp/configfile --hookdir
/usr/share/jenkins-debian-glue/pbuilder-hookdir/ --buildplace
/var/cache/pbuilder/base-impish-amd64.cow --mirror
http://www-ftp.lip6.fr/pub/linux/distributions//Ubuntu/archive/
--architecture amd64 --distribution impish --no-targz --extrapackages '
ccache zstd cowdancer'
I: Running in no-targz mode
I: Distribution is impish.
I: Current time: Mon Oct 11 16:01:34 UTC 2021
I: pbuilder-time-stamp: 1633968094
I: Building the build environment
I: running debootstrap
/usr/sbin/debootstrap
I: impish uses zstd compression, setting --extractor=ar option
I: Retrieving InRelease
I: Retrieving Packages
I: Validating Packages
I: Resolving dependencies of required packages...
I: Resolving dependencies of base packages...
I: Checking component main on
http://www-ftp.lip6.fr/pub/linux/distributions//Ubuntu/archive...
I: Validating adduser 3.118ubuntu5
[...]
I: Validating util-linux 2.36.1-8ubuntu1
I: Validating xz-utils 5.2.5-2
I: Validating zlib1g 1:1.2.11.dfsg-2ubuntu7
I: Chosen extractor for .deb packages: ar
I: Extracting base-files...
E: Unknown compression type for data.tar.zst in
.//var/cache/apt/archives/base-files_11.1ubuntu5_amd64.deb
E: debootstrap failed
E: Tail of debootstrap.log:
2021-10-11 16:01:35
URL:http://www-ftp.lip6.fr/pub/linux/distributions//Ubuntu/archive/dists/impish/InRelease
[270090/270090] ->
"/var/cache/pbuilder/base-impish-amd64.cow/var/lib/apt/lists/partial/www-ftp.lip6.fr_pub_linux_distributions__Ubuntu_archive_dists_impish_InRelease"
[1]
2021-10-11 16:01:36
URL:http://www-ftp.lip6.fr/pub/linux/distributions//Ubuntu/archive/dists/impish/main/binary-amd64/by-hash/SHA256/5f55112843e1755f687849f2f61645c3428d00cc103b646b696cd5ed4ae7d3cc
[1417328/1417328] ->
"/var/cache/pbuilder/base-impish-amd64.cow/var/lib/apt/lists/partial/www-ftp.lip6.fr_pub_linux_distributions__Ubuntu_archive_dists_impish_main_binary-amd64_Packages.xz"
[1]
E: End of debootstrap.log
W: Aborting with an error
E: pbuilder create failed
I: forking: rm -rf /var/cache/pbuilder/base-impish-amd64.cow

And the system has zstd:

$ dpkg -l|grep zstd
ii  libzstd1:amd64    1.4.8+dfsg-2.1
amd64    fast lossless compression algorithm
ii  zstd  1.4.8+dfsg-2.1
amd64    fast lossless compression algorithm -- CLI tool

Bug#996162: O: linux-ftpd -- File Transfer Protocol (FTP) server

[Bastian Germann]

Package: wnpp

ftpd is unmaintained/non-existing upstream and the package seems to be unmaintained as 
well (see related #986997). It should be removed in favour of another ftpd that is in the 
archive. None of them is fully command-line compatible. inetutils-ftpd seems to be the 
most compatible one with only a few options missing.


If noone wants to adopt the package, I am going to file a RM bug soon. In that case, 
inetutils-ftpd should provide a transitional package with more information on how to 
switch to inetutils-ftpd.


Whoever wants to use the linux-ftpd source can still install ftpd-ssl.

Bug#947233: ifupdown: Please include restart-ms option in can config

[Joerg Dorchain]

On Mon, Oct 11, 2021 at 05:14:15PM +0200, Santiago Ruano Rincón wrote:
> 
> Hi,
> 
> On Mon, 23 Dec 2019 11:03:33 +0100 Joerg Dorchain  wrote:
> > Package: ifupdown
> > Version: 0.8.35
> > Tags: Patch
> > Severity: wishlist
> > 
> > Hi,
> > 
> > please include the restart-ms option in the can static method, e.g as per
> > attached patch.
> > 
> > Thanks for considering.
> > 
> > Bye,
> > 
> > Joerg
> > 
> > 
> > --- ifupdown-0.8.35.orig/can.defn   2018-10-29 22:29:33.0 +0100
> > +++ ifupdown-0.8.35/can.defn2019-12-23 11:00:03.421389325 +0100
> > @@ -14,6 +14,7 @@
> >  triple triple  -- activate triple sampling (on|off)
> >  oneshot oneshot-- one shot mode (on|off)
> >  berr berr  -- activate berr reporting (on|off) 
> > +restart-ms restart-ms  -- restart-ms (0..)
> >  
> >up
> >  ip link set %iface% type can bitrate %bitrate%
> > @@ -22,6 +23,7 @@
> >  [[ ip link set %iface% type can triple-sampling %triple% ]]
> >  [[ ip link set %iface% type can one-shot %oneshot% ]]
> >  [[ ip link set %iface% type can berr-reporting %berr% ]]
> > +[[ ip link set %iface% type can restart-ms %restart-ms% ]]
> >  ip link set %iface% up
> >  
> >down
> > 
> 
> Thanks for your patch. I cannot test it by myself but I suppose it is OK
> to include it. However, could you please document this option in your
> patch? You may include it in interfaces(5)

Here you are:
--- interfaces.5.orig   2021-10-11 17:39:09.417498419 +0200
+++ interfaces.52021-10-11 17:42:08.263610653 +0200
@@ -889,6 +889,9 @@
 .TP
 .BI berr " berr"
 activate berr reporting (on|off)
+.TP
+.BI restart-ms " restart-ms"
+set restart-ms value (0..)
 .RE
 .SH KNOWN BUGS/LIMITATIONS
 The

Bye,

Joerg


signature.asc
Description: PGP signature

Bug#996115: apt upgrade --no-download --fix-missing --auto-remove: "E: Internal error, InstallPackages was called with broken packages!"

[Julian Andres Klode]

Control: tag -1 moreinfo

On Mon, Oct 11, 2021 at 02:35:39PM +0200, Jakub Wilk wrote:
> Package: apt
> Version: 2.3.9
> 
> I was in the middle of "apt upgrade" downloading packages, stopped it, and
> decided to upgrade stuff that is already downloaded. It didn't go well:
> 
>   # apt upgrade --no-download --fix-missing --auto-remove
>   Reading package lists... Done
>   Building dependency tree... Done
>   Reading state information... Done
>   Calculating upgrade... Done
>   The following packages will be REMOVED:
>  gobjc-10* (10.3.0-11)
>  libcbor0* (0.5.0+dfsg-2)
>   The following packages have been kept back:
>  bzr (2.7.0+bzr6622-15 => 2.7.0+bzr6622+brz)
>  cpp (4:10.2.1-1 => 4:11.2.0-2)
>  d-shlibs (0.101 => 0.102)
>  docutils-common (0.16+dfsg-2 => 0.16+dfsg-4)
>  g++ (4:10.2.1-1 => 4:11.2.0-2)
>  gcc (4:10.2.1-1 => 4:11.2.0-2)
>  gobjc (4:10.2.1-1 => 4:11.2.0-2)
>  libaio1 (0.3.112-10 => 0.3.112-11)
>  libaio1:amd64 (0.3.112-10 => 0.3.112-11)
>  libdeflate-dev (1.7-2 => 1.8-1)
>  libdeflate0 (1.7-2 => 1.8-1)
>  libdeflate0:amd64 (1.7-2 => 1.8-1)
>  libfido2-1 (1.8.0-1 => 1.8.0-1+b1)
>  libglibmm-2.4-1v5 (2.66.1-1 => 2.66.2-1)
>  libjs-sphinxdoc (4.2.0-3 => 4.2.0-4)
>  libuser (1:0.63~dfsg-2 => 1:0.63~dfsg-3)
>  libuser1 (1:0.63~dfsg-2 => 1:0.63~dfsg-3)
>  libwireshark-data (3.4.8-1 => 3.4.9-1)
>  libwireshark14 (3.4.8-1 => 3.4.9-1)
>  libwiretap11 (3.4.8-1 => 3.4.9-1)
>  libwsutil12 (3.4.8-1 => 3.4.9-1)
>  libwww-perl (6.53-1 => 6.57-1)
>  libzint2.10 (2.10.0-1 => 2.10.0-1+b1)
>  mksh (59c-11 => 59c-12)
>  mkvtoolnix (61.0.0-1 => 62.0.0-1)
>  neomutt (20180716+dfsg.1-1+deb10u2 => 20201127+dfsg.1-1.2+b1)
>  python3-astroid (2.8.1-1 => 2.8.2-1)
>  python3-bcrypt (3.1.7-4 => 3.2.0-1)
>  python3-click (7.1.2-1 => 8.0.2-1)
>  python3-docutils (0.16+dfsg-2 => 0.16+dfsg-4)
>  python3-kiwisolver (1.3.1-2 => 1.3.2-1)
>  python3-logilab-common (1.4.3-1 => 1.8.1-1)
>  python3-regex (0.1.20201113-2 => 0.1.20211008-1)
>  python3-sphinx (4.2.0-3 => 4.2.0-4)
>  python3-urwid (2.1.2-1 => 2.1.2-2)
>  sphinx-common (4.2.0-3 => 4.2.0-4)
>  sphinx-doc (4.2.0-3 => 4.2.0-4)
>  tshark (3.4.8-1 => 3.4.9-1)
>  wireshark-common (3.4.8-1 => 3.4.9-1)
>  zint (2.10.0-1 => 2.10.0-1+b1)
>   0 upgraded, 0 newly installed, 2 to remove and 40 not upgraded.
>   The following packages have unmet dependencies:
>gobjc : Depends: gobjc-10 (>= 10.2.1-3~) but it is not going to be 
> installed
>libfido2-1 : Depends: libcbor0 (>= 0.5.0) but it is not going to be 
> installed
>   E: Internal error, InstallPackages was called with broken packages!

I don't know where this ends up, but we definitely need more logs, see
README.md for debugging instructions.

If this fails in the resolver, doing --solver dump with
APT_EDSP_DUMP_FILENAME set to a nice filename and attaching that file
would be super helpful.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#984206: libquazip: ftbfs with GCC-11

[Sebastiaan Couwenberg]

Control: tags -1 patch

The attached patch fixes the issue by updating the symbols file and
overriding dh_makeshlibs to use the upstream version and not failing on
changes to fix this permanently.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
diff -Nru libquazip-0.9.1/debian/changelog libquazip-0.9.1/debian/changelog
--- libquazip-0.9.1/debian/changelog2020-07-23 15:48:10.0 +0200
+++ libquazip-0.9.1/debian/changelog2021-10-11 17:11:23.0 +0200
@@ -1,3 +1,12 @@
+libquazip (0.9.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update symbols for gcc-11.
+(closes: #984206)
+  * Override dh_makeshlibs to use upstream version and not fail on changes.
+
+ -- Bas Couwenberg   Mon, 11 Oct 2021 17:11:23 +0200
+
 libquazip (0.9.1-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru libquazip-0.9.1/debian/libquazip5-1.symbols.amd64 
libquazip-0.9.1/debian/libquazip5-1.symbols.amd64
--- libquazip-0.9.1/debian/libquazip5-1.symbols.amd64   2020-07-23 
15:48:10.0 +0200
+++ libquazip-0.9.1/debian/libquazip5-1.symbols.amd64   2021-10-11 
17:11:23.0 +0200
@@ -164,8 +164,6 @@
  _ZN5QHashI7QString16unz64_file_pos_sE11deleteNode2EPN9QHashData4NodeE@Base 
0.7.3
  
_ZN5QHashI7QString16unz64_file_pos_sE13duplicateNodeEPN9QHashData4NodeEPv@Base 
0.7.3
  _ZN5QHashI7QString16unz64_file_pos_sE6insertERKS0_RKS1_@Base 0.9.1
- _ZN5QHashI7QString16unz64_file_pos_sED1Ev@Base 0.9.1
- _ZN5QHashI7QString16unz64_file_pos_sED2Ev@Base 0.9.1
  _ZN5QHashIt5QListI10QByteArrayEE11deleteNode2EPN9QHashData4NodeE@Base 0.9
  _ZN5QHashIt5QListI10QByteArrayEE13duplicateNodeEPN9QHashData4NodeEPv@Base 0.9
  _ZN5QHashIt5QListI10QByteArrayEED1Ev@Base 0.9
@@ -334,9 +332,8 @@
  
_ZSt13__heap_selectIN5QListI16QuaZipFileInfo64E8iteratorEN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_S9_S9_T0_@Base
 0.9
  
_ZSt16__insertion_sortIN5QListI16QuaZipFileInfo64E8iteratorEN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_S9_T0_@Base
 0.9
  
_ZSt16__introsort_loopIN5QListI16QuaZipFileInfo64E8iteratorEiN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_S9_T0_T1_@Base
 0.9
- 
_ZSt21__unguarded_partitionIN5QListI16QuaZipFileInfo64E8iteratorEN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEET_S9_S9_S9_T0_@Base
 0.9.1
- 
_ZSt22__move_median_to_firstIN5QListI16QuaZipFileInfo64E8iteratorEN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_S9_S9_S9_T0_@Base
 0.9.1
  
_ZSt25__unguarded_linear_insertIN5QListI16QuaZipFileInfo64E8iteratorEN9__gnu_cxx5__ops14_Val_comp_iterI19QuaZipDirComparatorEEEvT_T0_@Base
 0.9
+ 
_ZSt4swapI16QuaZipFileInfo64ENSt9enable_ifIXsrSt6__and_IJSt6__not_ISt15__is_tuple_likeIT_EESt21is_move_constructibleIS5_ESt18is_move_assignableIS5_EEE5valueEvE4typeERS5_SF_@Base
 0.9.1
  _ZTI10QuaAdler32@Base 0.7.3
  _ZTI10QuaZipFile@Base 0.7.3
  _ZTI11QuaGzipFile@Base 0.7.3
diff -Nru libquazip-0.9.1/debian/rules libquazip-0.9.1/debian/rules
--- libquazip-0.9.1/debian/rules2020-07-23 15:48:10.0 +0200
+++ libquazip-0.9.1/debian/rules2021-10-11 17:11:23.0 +0200
@@ -11,6 +11,10 @@
 
 QT_SELECT=qt5
 
+include /usr/share/dpkg/pkg-info.mk
+
+UPSTREAM_VERSION = $(shell echo $(DEB_VERSION_UPSTREAM) | sed -e 's/\+.*//')
+
 # Enable multiarch builds & prepare qmake vars
 include /usr/share/dpkg/architecture.mk
 
@@ -55,3 +59,6 @@
 
 override_dh_missing:
dh_missing --fail-missing
+
+override_dh_makeshlibs:
+   dh_makeshlibs -- -c0 -v$(UPSTREAM_VERSION)

Bug#364913: still valid?

[Helge Kreutzmann]

Hello Thomas,
On Sun, Oct 10, 2021 at 11:28:16PM +0200, Thomas Lange wrote:
> Is this bug still valid or can we close this bug?

I'm still having a faint hope that the vote pages get i18n, but I do
understand that this is low priority. I still monitor the devotee
repository for changes …

Admittingly I haven't done translation work on the web pages for quite
some years now.

Best greetings from a few kilometres south.

  Helge

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#947233: ifupdown: Please include restart-ms option in can config

[Santiago Ruano Rincón]

Hi,

On Mon, 23 Dec 2019 11:03:33 +0100 Joerg Dorchain  wrote:
> Package: ifupdown
> Version: 0.8.35
> Tags: Patch
> Severity: wishlist
> 
> Hi,
> 
> please include the restart-ms option in the can static method, e.g as per
> attached patch.
> 
> Thanks for considering.
> 
> Bye,
> 
> Joerg
> 
> 
> --- ifupdown-0.8.35.orig/can.defn 2018-10-29 22:29:33.0 +0100
> +++ ifupdown-0.8.35/can.defn  2019-12-23 11:00:03.421389325 +0100
> @@ -14,6 +14,7 @@
>  triple triple-- activate triple sampling (on|off)
>  oneshot oneshot  -- one shot mode (on|off)
>  berr berr-- activate berr reporting (on|off) 
> +restart-ms restart-ms-- restart-ms (0..)
>  
>up
>  ip link set %iface% type can bitrate %bitrate%
> @@ -22,6 +23,7 @@
>  [[ ip link set %iface% type can triple-sampling %triple% ]]
>  [[ ip link set %iface% type can one-shot %oneshot% ]]
>  [[ ip link set %iface% type can berr-reporting %berr% ]]
> +[[ ip link set %iface% type can restart-ms %restart-ms% ]]
>  ip link set %iface% up
>  
>down
> 

Thanks for your patch. I cannot test it by myself but I suppose it is OK
to include it. However, could you please document this option in your
patch? You may include it in interfaces(5)

Thanks,

 -- Santiago

Bug#994723: libimath-dev conflicts with libilmbase-dev

[Matteo F. Vescovi]

Hi!

On Mon, Oct 11, 2021 at 3:46 PM Andrius Merkys  wrote:
> Sure, but does opencolorio 2.1.0 build with libilmbase-dev 2.5.7-2 for
> you? I run into the following:
>
> CMake Error at
> /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:230
> (message):
>   Could NOT find Imath (missing: Imath_INCLUDE_DIR) (Required is at least
>   version "3.1.2")
> Call Stack (most recent call first):
>   /usr/share/cmake-3.21/Modules/FindPackageHandleStandardArgs.cmake:594
> (_FPHSA_FAILURE_MESSAGE)
>   share/cmake/modules/FindImath.cmake:116
> (find_package_handle_standard_args)
>   share/cmake/modules/FindExtPackages.cmake:45 (find_package)
>   CMakeLists.txt:243 (include)
>
> By the way, I had to monkey-patch #995907 to get here.

Oh, I guess I never came to that point since I was blocked by pystring
and sphinx theme in the first place.
How did you get over the sphinx theme blocker? I'm not going to
package that too... I'm full for now ;-)

Cheers.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A

Bug#995678: Bug#995392: ghostscript: ps2pdf trashes some characters

[Vincent Lefevre]

On 2021-10-11 16:46:08 +0200, Vincent Lefevre wrote:
> I've attached an archive with
>   * chartest3.tex (already mentioned)
>   * chartest3.aux, chartest3.log, chartest3.pdf: the files generated
> with "pdflatex chartest3.tex"
>   * out.pdf: the file generated with
>   /usr/bin/ps2pdf chartest3.pdf out.pdf
> (ghostscript 9.54.0~dfsg-5 being installed) after unsetting
> GS_OPTIONS.

BTW, since ps2pdf is just a script, I could see with strace that
the following command was executed:

  /usr/bin/gs -P- -dSAFER -dCompatibilityLevel=1.4 -q -P- -dNOPAUSE -dBATCH 
-sDEVICE=pdfwrite -sstdout=%stderr -sOutputFile=out.pdf -P- -dSAFER 
-dCompatibilityLevel=1.4 chartest3.pdf

and indeed, I can reproduce the issue with this command (on
chartest3.pdf generated by pdflatex with TL 2021 installed).

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