Bug#1010550: src:node-regenerator is in unstable

[Yadd]

Hi Ftpmasters,

new src:node-regenerator is now in unstable, old 
src:node-regenerator-runtime and node-regenerator-transform can be 
safely removed now.


Cheers,
Yadd

Bug#949608: usbguard: bring back some GUI frontend to Debian

[Christoph Anton Mitterer]

Hey.

If you don't mind,... then from my side we can close the bug.

usbguard-notifier is probably not getting packaged anytime soon, and
with usbguard thus being left barely usable for desktops (which are
however it's main target) ... I'm switching now to usbauth.

Cheers,
Chris.

Bug#1006625: pulseaudio-module-bluetooth: A2DP and HSP profiles unavailable after update

[brian m. carlson]

On 2022-02-28 at 20:35:06, Claire wrote:
> Package: pulseaudio-module-bluetooth
> Version: 15.0+dfsg1-4
> Severity: important
> X-Debbugs-Cc: claire.dbts-0...@sitedethib.com
> 
> Dear Maintainer,
> 
> Since updating to 15.0+dfsg1-4 from 15.0+dfsg1-3, I am stuck with the
> low-quality HFP profile.
> 
> Reinstalling pulseaudio, libpulseaudio0 and pulseaudio-module-bluetooth to
> 15.0+dfsg1-3 fixes the issue.
> 
> Rebuilding the pulseaudio packages by changing `-Dbluez5-gstreamer=enabled` to
> `-Dbluez5-gstreamer=disabled` also works.

I'm able to confirm this.  My Pixel Buds A-Series no longer function in
A2DP mode with the new version of pulseaudio, but continue to work just
fine in HFP mode.  Downgrading restores the functionality.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1010915: mutt: GSSAPI SMTP authentication no longer works

[brian m. carlson]

Package: mutt
Version: 2.2.4-1
Severity: important

I use Kerberos on my personal network at home, and therefore I use
GSSAPI authentication for IMAP and SMTP.  While GSSAPI with IMAP works
fine, recently, GSSAPI with SMTP stopped working.  I suspect this is
related to the move to gsasl.

When it fails, mutt merely says "SASL authentication failed".  What
Postfix (Debian bullseye) reports is this:

  May 13 01:52:52 ring postfix/submission/smtpd[2307029]: Anonymous TLS 
connection established from : TLSv1.2 with cipher 
ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)
  May 13 01:52:53 ring postfix/submission/smtpd[2307029]: warning: : 
SASL GSSAPI authentication aborted
  May 13 01:52:54 ring postfix/submission/smtpd[2307029]: lost connection after 
AUTH from 
  May 13 01:52:54 ring postfix/submission/smtpd[2307029]: disconnect from 
 ehlo=2 starttls=1 auth=0/1 commands=3/4

I've filed this as important because it prevents me from sending emails,
which is an important functionality of any mail client.  Downgrading to
2.0.5-4.1 works.

-- Package-specific info:
Mutt 2.2.4 (2022-04-30)
Copyright (C) 1996-2022 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 5.16.0-6-amd64 (x86_64)
ncurses: ncurses 6.3.20220423 (compiled with 6.3)
libidn2: 2.3.2 (compiled with 2.3.2)
hcache backend: tokyocabinet 1.4.48

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 11.3.0-1' 
--with-bugurl=file:///usr/share/doc/gcc-11/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-11 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-11-m8KK5z/gcc-11-11.3.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-11-m8KK5z/gcc-11-11.3.0/debian/tmp-gcn/usr
 --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu 
--with-build-config=bootstrap-lto-lean --enable-link-serialization=2
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 11.3.0 (Debian 11.3.0-1) 

Configure options: --build=x86_64-linux-gnu --prefix=/usr 
'--includedir=${prefix}/include' '--mandir=${prefix}/share/man' 
'--infodir=${prefix}/share/info' --sysconfdir=/etc --localstatedir=/var 
--disable-option-checking --disable-silent-rules 
'--libdir=${prefix}/lib/x86_64-linux-gnu' --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--with-mailpath=/var/mail --enable-compressed --enable-debug --enable-fcntl 
--enable-hcache --enable-gpgme --enable-imap --enable-smtp --enable-pop 
--enable-sidebar --enable-dotlock --disable-fmemopen --with-curses 
--with-gnutls --with-gss --with-idn2 --with-mixmaster --with-gsasl 
--without-gdbm --without-bdb --without-qdbm --with-tokyocabinet 
build_alias=x86_64-linux-gnu 'CFLAGS=-g -O2 
-ffile-prefix-map=/build/mutt-ziEvPb/mutt-2.2.4=. -fstack-protector-strong 
-Wformat -Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now' 
'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 
-ffile-prefix-map=/build/mutt-ziEvPb/mutt-2.2.4=. -fstack-protector-strong 
-Wformat -Werror=format-security

Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  +USE_FCNTL  -USE_FLOCK   
+USE_POP  +USE_IMAP  +USE_SMTP  
-USE_SSL_OPENSSL  +USE_SSL_GNUTLS  -USE_SASL  +USE_GSASL  +USE_GSS  
+HAVE_GETADDRINFO  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  +HAVE_FUTIMENS  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  +CRYPT_BACKEND_GPGME  
-EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  -LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET  
+HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  -HAVE_LIBIDN  +HAVE_LIBIDN2  +HAVE_GETSID  
+USE_HCACHE  
+USE_SIDEBAR  +USE_COMPRESSED  +USE_INOTIFY  
-ISPELL
SENDMAIL="/usr/sbin/sendmail"

Bug#1010913: nala: Please provide a means to run "nala upgrade" without updating the package list

[Axel Beckert]

Package: nala
Version: 0.8.2
Severity: wishlist

Hi,

nala seems to mimic that annoying misfeature of yum/dnf to always update
the package list even if you just did that and just want to upgrade
packages.

So please provide a means (e.g. a configuration option in
/etc/nala/nala.conf) to not run a package list update on "nala upgrade".

Thanks in advance!

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

Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages nala depends on:
ii  apt  2.4.5
ii  python3  3.10.4-1+b1
ii  python3-anyio3.5.0-4
ii  python3-apt  2.3.0+b1
ii  python3-httpx0.22.0-2
ii  python3-pexpect  4.8.0-2
ii  python3-rich 12.1.0-1
ii  python3-typer0.4.1-1

Versions of packages nala recommends:
ii  python3-socksio  1.0.0-2

nala suggests no packages.

-- no debconf information

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Diederik de Haas]

Hi Petra and Axel,

On Thursday, 28 April 2022 09:56:29 CEST Salvatore Bonaccorso wrote:
> Now this gives us probably a good hint!
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=215909
> 
> d6b88ce2eb9d ("ACPI: processor idle: Allow playing dead in C3 state")
> and a followup commit bfe55a1f7fd6 ("ACPI: processor: idle: fix lockup
> regression on 32-bit ThinkPad T40") were both applied to 5.15.35. I
> suspect the former is the one so which causes the regression as well
> for you.

It was a good hint, but apparently not (yet) the solution.
Francesco reported that the issue was fixed for him in 5.17.0-2-686 which 
corresponds to 5.17.6 upstream kernel.
Petra & Axel: can you verify whether it is also fixed for you?

Looking through the changes between 5.17.5 and 5.17.6, I found the following:

- 14defb873c1dc4cef1e7e7951f47f019821734fc titled:
Revert "ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40"
Secondary commit message:
"  commit 20e582e16af24b074e583f9551fad557882a3c9d upstream.

This reverts commit bfe55a1f7fd6bfede16078bf04c6250fbca11588.

This was presumably misdiagnosed as an inability to use C3 at
all when I suspect the real problem is just misconfiguration of
C3 vs. ARB_DIS.
"
- b3b0ca1c324982fcc005063af045439670e16aa3 titled:
ACPI: processor: idle: Avoid falling back to C3 type C-states
Secondary commit message:
"  commit fc45e55ebc58dbf622cb89ddbf797589c7a5510b upstream.

The "safe state" index is used by acpi_idle_enter_bm() to avoid
entering a C-state that may require bus mastering to be disabled
on entry in the cases when this is not going to happen.  For this
reason, it should not be set to point to C3 type of C-states, because
they may require bus mastering to be disabled on entry in principle.

This was broken by commit d6b88ce2eb9d ("ACPI: processor idle: Allow
playing dead in C3 state") which inadvertently allowed the "safe
state" index to point to C3 type of C-states.

This results in a machine that won't boot past the point when it first
enters C3. Restore the correct behaviour (either demote to C1/C2, or
use C3 but also set ARB_DIS=1).

I hit this on a Fujitsu Siemens Lifebook S6010 (P3) machine.
"

The rest of the commits between .5 and .6 don't appear relevant for this bug 
to *me*, but I can ofc be wrong.

Cheers,
  Diederik

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

Bug#1010912: libdcmtk16 version 3.6.7-1: ldd blender shows missing .so files

[Satyam]

Package: libdcmtk16
Version: 3.6.7-1
Severity: grave
Tags: d-i
Justification: renders package unusable
X-Debbugs-Cc: sat...@newdev.siduction.org

Dear Maintainer,

I have two debian sid computers. Blender stopped working after an update to
libdcmtk16 version 3.6.7-1 on one of them. It had a missing library error. "ldd
/usr/bin/blender" showed 5 missing libraries that were all in libdcmtk16.
"apt-file show libdcmtk16" displayed both so.16 and so.17 versions of the
packages. "dpkg -L libdcmtk16" only showed so.17 versions. The blender not
found error concerned so.16 files.

I went to the other sid install that had the earlier package version "3.6.6-5"
and copied its so.16 files onto the broken system and blender now works.


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

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

Versions of packages libdcmtk16 depends on:
ii  libc62.33-7
ii  libgcc-s112.1.0-1
ii  libpng16-16  1.6.37-5
ii  libssl1.11.1.1o-1
ii  libstdc++6   12.1.0-1
ii  libtiff5 4.3.0-7
ii  libwrap0 7.6.q-31
ii  libxml2  2.9.14+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4

libdcmtk16 recommends no packages.

libdcmtk16 suggests no packages.

-- no debconf information

Bug#1010792: RFS: psi-notify/1.2.1-2 [ITP] -- Alert when your machine is becoming oversaturated

[Michel Alexandre Salim]

On Tue, May 10, 2022 at 02:03:15PM +0800, Paul Wise wrote:
> On Mon, 2022-05-09 at 20:18 -0700, Michel Alexandre Salim wrote:
> 
> > I am looking for a sponsor for my package "psi-notify":
> 
> I prefer that three issues are fixed before uploading psi-notify:
> 
Thanks! Done most of them. Will do PRs for upstream for the remaining
ones:
- adding `make install`
- pointing to repology
- changing the notification spec URL

Will ask upstream about making the demo dynamically generated too. Chris
mentioned he's cutting a new release at some point.

-- 
Michel Alexandre Salim
identities: https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


signature.asc
Description: PGP signature

Bug#1010911: RM: gajim-plugininstaller/experimental -- ROM; obsoleted by gajim 1.4.0

[Martin]

Package: ftp.debian.org

Please remove gajim-plugininstaller from experimental.
Gajim 1.4.0 (now in unstable) includes its functionality.
The plugin is therefore obsolete.
Thank you!

Bug#1010910: python3-sipbuild: sip-build crashes while trying to parse

[Sebastian Kuzminsky]

Package: python3-sipbuild
Version: 6.6.1+dfsg-1
Severity: important
Tags: patch upstream
X-Debbugs-Cc: s...@highlab.com

I'm having trouble building libSavitar 5.0-beta (part of Cura, a slicer
for 3d printers): 

When building with sip 6.6.1+dfsg-1 it fails with this traceback:

'/usr/bin/cmake' '-E' 'env' 
'PYTHONPATH=::/home/seb/cura-debs/libsavitar-docker-sandbox/.pybuild/cpython3_3.9/build'
 '/usr/bin/sip-build' '--pep484-pyi' '--no-protected-is-public' '--verbose'
Using the CMake builder
These bindings will be built: pySavitar.
Generating the source files
Generating the pySavitar bindings...
sip-build: An internal error occurred...
Traceback (most recent call last):
  File "/usr/bin/sip-build", line 33, in 
sys.exit(load_entry_point('sip==6.6.1', 'console_scripts', 
'sip-build')())
  File "/usr/lib/python3/dist-packages/sipbuild/tools/build.py", line 37, 
in main
handle_exception(e)
  File "/usr/lib/python3/dist-packages/sipbuild/exceptions.py", line 81, in 
handle_exception
raise e
  File "/usr/lib/python3/dist-packages/sipbuild/tools/build.py", line 34, 
in main
project.build()
  File "/usr/lib/python3/dist-packages/sipbuild/project.py", line 249, in 
build
self.builder.build()
  File 
"/home/seb/cura-debs/libsavitar-docker-sandbox/.pybuild/cpython3_3.9/build/CMakeBuilder.py",
 line 12, in build
self._generate_bindings()
  File "/usr/lib/python3/dist-packages/sipbuild/builder.py", line 277, in 
_generate_bindings
buildable = bindings.generate()
  File "/usr/lib/python3/dist-packages/sipbuild/bindings.py", line 166, in 
generate
spec, sip_files = parse(self.sip_file, SIP_VERSION, encoding,
  File 
"/usr/lib/python3/dist-packages/sipbuild/generator/parser/parser.py", line 35, 
in parse
protected_is_public, include_dirs, strict).parse(sip_file)
  File 
"/usr/lib/python3/dist-packages/sipbuild/generator/parser/parser_manager.py", 
line 1454, in parse
self._parser.parse(self._read(sip_file), lexer=self._lexer,
  File "/usr/lib/python3/dist-packages/ply/yacc.py", line 331, in parse
return self.parseopt(input, lexer, debug, tracking, tokenfunc)
  File "/usr/lib/python3/dist-packages/ply/yacc.py", line 823, in parseopt
p.callable(pslice)
  File "/usr/lib/python3/dist-packages/sipbuild/generator/parser/rules.py", 
line 3097, in p_variable
fq_cpp_name = normalised_scoped_name(cpp_name, pm.scope)
  File "/usr/lib/python3/dist-packages/sipbuild/generator/utils.py", line 
156, in normalised_scoped_name
fq_scoped_name.prepend(scope.iface_file.fq_cpp_name)
  File 
"/usr/lib/python3/dist-packages/sipbuild/generator/specification.py", line 748, 
in prepend
new_name = list(scoped_name._name)
AttributeError: 'NoneType' object has no attribute '_name'

Building the same version of libSavitar on testing, which has sip
6.5.1+dfsg-1, works fine.

The problem is present in upstream, and is due to upstream's ongoing
effort to switch from parsing with bison & flex, to parsing with PLY
instead.  The new pure-python parser is not quite fully functional yet.
(The sip 6.5 in testing still uses the old bison/flex-based parser.)

After applying patches from upstream's mercurial repo, r2748 through
r2761, the parser now successfully handles libSavitar 5.0-beta.

Here is a gbp branch with these changes from upstream applied:

https://salsa.debian.org/seb_kuzminsky-guest/sip6/-/commits/debian/master/

That probably isn't in the correct format, if you give me feedback i'll
try to fix it, or feel free to do with it what you will.

We may also want to consider staying on sip 6.5 for a while, until the
new parser is more mature, but I defer to your judgement on this.


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

Kernel: Linux 5.10.0-14-rt-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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

Bug#1006149: linux-image-5.16.0-1-686: Fails to boot on T41 Thinkpads

[Francesco C]

Hi

After updating linux-image-686 with the latest update (5.17.0-2-686) ,
finally my machine successfully boots.  The problem should be solved
also for other people affected by this bug.

P.S. : For other people interested , starting from linux-5.18-rc5-rt4
and beyond ( latest I've built is linux-5.18-rc6-rt7) my system is
shutting down correctly in both power off and restart modes. And I
suppose it should be the same for other 686 class users that are
running a RT kernel :)

Bug#1006920: please split out a libtbbmalloc2 package, both in tbb and onetbb

[M. Zhou]

Yes. If you have time to handle it please go ahead.
I'm suffering from a recent paper submission deadline,
so I'm only able to build and upload some small packages
that can be built on my weak laptop.
The paper deadline is May 19. After that I should be
able to handle this with a proper build machile.

On Thu, 2022-05-12 at 09:33 +0300, Andrius Merkys wrote:
> Hello,
> 
> Can we proceed with splitting out libtbbmalloc2 if there are no
> blockers? tbb/onetbb transition is blocking quite some packages, it
> would be nice to deal with all of them until the freeze.
> 
> Best,
> Andrius
> 

Bug#1010908: [INTL:sv] Swedish strings for openstack-pkg-tools debconf

[Martin Bagge / brother]

package: openstack-pkg-tools
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf.
--
brother# Translation of openstack-pkg-tools debconf template to Swedish
# Copyright (C) 2012-2022 Martin Bagge 
# This file is distributed under the same license as the openstack-pkg-tools package.
#
# Martin Bagge , 2012, 2014, 2022
msgid ""
msgstr ""
"Project-Id-Version: openstack-pkg-tools\n"
"Report-Msgid-Bugs-To: openstack-pkg-to...@packages.debian.org\n"
"POT-Creation-Date: 2019-10-10 18:44+0200\n"
"PO-Revision-Date: 2022-05-13 00:28+0200\n"
"Last-Translator: Martin Bagge / brother \n"
"Language-Team: Swedish \n"
"Language: Swedish\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: emacs\n"

#. Type: boolean
#. Description
#: ../openstack-pkg-tools.configure-db.templates:1001
msgid "Set up a database for this package?"
msgstr "Ska en databas installeras för detta paket?"

#. Type: boolean
#. Description
#: ../openstack-pkg-tools.configure-db.templates:1001
msgid ""
"No database has been set up for this package. Before continuing, you should "
"make sure you have the following information:"
msgstr ""
"Ingen databas har installerats för detta paket. Innan du fortsätter behöver "
"följande finnas tillgängligt:"

#. Type: boolean
#. Description
#: ../openstack-pkg-tools.configure-db.templates:1001
msgid ""
" * the type of database that you want to use - generally the MySQL backend\n"
"   (which is compatible with MariaDB) is a good choice, and other\n"
"   implementations like PostgreSQL or SQLite are often problematic with\n"
"   OpenStack (this depends on the service);\n"
" * the database server hostname (that server must allow TCP connections "
"from\n"
"   this machine);\n"
" * a username and password to access the database."
msgstr ""
" * vilken databastyp du vill använda. Generellt sett är MySQL-\n"
"   kompatabilitet att föredra (exempelvis MariaDB). Andra alternativ\n"
"   likt PostgreSQL och SQLite är ofta svåra att använda med\n"
"   OpenStack (beroende på vilken\n"
"   service som körs).\n"
" * serverns värdnamn (som måste kunna ta emot TCP-anslutningar\n"
"   från den här maskinen)\n"
" * användarnamn och lösenord för att komma åt databasen."

#. Type: boolean
#. Description
#: ../openstack-pkg-tools.configure-db.templates:1001
msgid ""
"Note that if you plan on using a remote database server, you must first "
"configure dbconfig-common to do so (using dpkg-reconfigure dbconfig-common), "
"and the remote database server needs to be configured with adequate "
"credentials."
msgstr ""
"Observera att om du planerar att använda en databasserver på annan maskin så "
"måste du justera detta i dbconfig-common först (använd dpkg-reconfigure "
"dbconfig-common) och databasservern som du ämnar använda måste ställas in "
"med korrekta uppgifter."

#. Type: boolean
#. Description
#: ../openstack-pkg-tools.configure-db.templates:1001
msgid ""
"If some of these requirements are missing, do not choose this option. Run "
"with regular SQLite support instead."
msgstr ""
"Om något av dessa krav saknas ska du avböja detta alternativ. Använda "
"istället SQLite-stödet."

#. Type: boolean
#. Description
#: ../openstack-pkg-tools.configure-db.templates:1001
msgid ""
"You can change this setting later on by running \"dpkg-reconfigure -plow\"."
msgstr ""
"Denna inställning kan ändras senare genom att köra \"dpkg-reconfigure -"
"plow\"."

#. Type: boolean
#. Description
#: ../openstack-pkg-tools.configure-ksat.templates:1001
msgid "Manage keystone_authtoken with debconf?"
msgstr "Ska keystone_authtoken hanteras av debconf?"

#. Type: boolean
#. Description
#: ../openstack-pkg-tools.configure-ksat.templates:1001
msgid ""
"Every OpenStack service must contact Keystone, and this is configured "
"through the [keystone_authtoken] section of the configuration. Specify if "
"you wish to handle this configuration through debconf."
msgstr ""
"Alla OpenStack-tjänster måste kontakta Keystone och detta ställs in via "
"sektionen [keystone_authtoken] i inställningsfilen. Ange om du vill hantera "
"detta genom debconf."

#. Type: string
#. Description
#: ../openstack-pkg-tools.configure-ksat.templates:2001
msgid "Auth server public endpoint URL:"
msgstr "URL för publik ändpunkt på identifieringsservern:"

#. Type: string
#. Description
#: ../openstack-pkg-tools.configure-ksat.templates:2001
msgid ""
"Specify the URL of your Keystone authentication server public endpoint. This "
"value will be set in the www_authenticate_uri directive."
msgstr ""
"Ange URL för din publika ändpunkt på Keystone autentiseringsservern. Detta "
"värde kommer att sparas för www_authenticate_uri."

#. Type: string
#. Description
#: ../openstack-pkg-tools.configure-ksat.templates:3001
msgid "Keystone region:"
msgstr "Keystone-region:"

#. Type: string
#. Description
#: ../openstack-pkg-tools.configure-ksat.templates:3001
msgid "Specify the Keystone region to 

Bug#1010909: [INTL:sv] Swedish strings for gnunet debconf

[Martin Bagge / brother]

package: gnunet
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf.
--
brother# Translation of gnunet debconf template to Swedish
# Copyright (C) 2022 Martin Bagge 
# This file is distributed under the same license as the XX package.
#
# Martin Bagge , 2022
# Daniel Nylander , 2007
msgid ""
msgstr ""
"Project-Id-Version: gnunet\n"
"Report-Msgid-Bugs-To: gnu...@packages.debian.org\n"
"POT-Creation-Date: 2021-02-27 11:07+0100\n"
"PO-Revision-Date: 2022-05-13 00:11+0200\n"
"Last-Translator: Martin Bagge / brother \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: title
#. Description
#: ../gnunet.templates:1001
msgid "GNUnet: Setup"
msgstr "GNUnet: Inställningar"

#. Type: string
#. Description
#: ../gnunet.templates:2001
msgid "GNUnet user:"
msgstr "GNUnet-användare:"

#. Type: string
#. Description
#: ../gnunet.templates:2001
msgid "Please choose the user that the GNUnet server process will run as."
msgstr "Välj den användare som GNUnet-demonens process ska köra som."

#. Type: string
#. Description
#: ../gnunet.templates:2001
msgid ""
"This should be a dedicated account. If the specified account does not "
"already exist, it will automatically be created, with no login shell."
msgstr ""
"Det här bör vara ett särskilt konto. Om det angivna kontot inte finns kommer "
"det automatiskt att skapas, utan något inloggningsskal."

#. Type: string
#. Description
#: ../gnunet.templates:3001
msgid "GNUnet group:"
msgstr "GNUnet-grupp:"

#. Type: string
#. Description
#: ../gnunet.templates:3001
msgid "Please choose the group that the GNUnet server process will run as."
msgstr "Välj den grupp som GNUnet-demonens process ska köra som."

#. Type: string
#. Description
#: ../gnunet.templates:3001
msgid ""
"This should be a dedicated group, not one that already owns data. Only the "
"members of this group will have access to GNUnet data, and be allowed to "
"start and stop the GNUnet server."
msgstr ""
"Det här bör vara en särskilt utsedd grupp, inte en grupp som redan äger "
"data. Endast medlemmar av den här gruppen kommer att få åtkomst till GNUnets "
"data och kommer att tillåtas att starta och stoppa GNUnet-servern."

#. Type: boolean
#. Description
#: ../gnunet.templates:4001
msgid "Should the GNUnet server be launched on boot?"
msgstr "Ska GNUnet-demonen startas vid systemets uppstart?"

#. Type: boolean
#. Description
#: ../gnunet.templates:4001
msgid ""
"If you choose this option, a GNUnet server will be launched each time the "
"system is started. Otherwise, you will need to launch GNUnet each time you "
"want to use it."
msgstr ""
"Om du väljer det här alternativet kommer en GNUnet-server att startas varje "
"gång som systemet startar upp. Om inte behöver du starta GNUnet varje gång "
"du vill använda det."

Bug#1009253: www.debian.org: remove debian-www list from the footer; direct people to the contact page instead

[Paul Wise]

On Thu, 2022-04-21 at 09:35 +0100, Justin B Rye wrote:

>       See our [contact page] to get in touch.

Thanks! We ended up going with this one. I have credited you in the
commit message. The change is committed to git and we are getting
translations updated before we rebuild the website with the new footer.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1009253: translations needed: bug #1009253 remove debian-www list from the footer; direct people to the contact page instead

[Laura Arjona Reina]

Dear translators
Thanks Paul Wise and Justin B. Rye, we have updated the website footer to 
change the contact address in the from debian-www to the contact page, in order 
to help people ask in the right place (bug #1009253, commit 
https://salsa.debian.org/webmaster-team/webwml/-/commit/39793d99332303af2dc56ed4b1a556019997bb86).

We would need translations of the new string. How to do it:

* Update your local repo (git pull)
* Go to your language/po folder and do "update-po"
* Complete the translation in templates.po file
* Commit changes (thanks!)

Since the footer is used in almost all the pages, the website build has been 
stopped until we get some translations, so we avoid several consecutive long 
builds (one for each translation if they don't arrive together).

I hope we get at least 3-4 languages during this time, and then activate the 
cron job to do the builds maybe around noon UTC.

Note: if your language has no active translator group or coordinator but you want to 
help, just reply this mail to debian-www with your the name of the language and 
translation. The sentence is quite short: "See our [contact page] to get in touch. 
Web site source code is [available]."

Thanks!
--
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#1010907: lintian: bad-jar-name check doesn't handle suffixes

[Emmanuel Bourg]

Package: lintian
Version: 2.114.0
Severity: normal

The bad-jar-name check flags many packages that do conform to the Java policy,
which allows a suffix after the base package name (packagename-extraname.jar).

See for example the batik package, /usr/share/java/batik-all.jar and its
siblings are wrongly reported.

Emmanuel Bourg

Bug#1010795: libnet-ssleay-perl: Autopkgtest failures on OpenSSL 3.0.* patch releases

[gregor herrmann]

On Tue, 10 May 2022 10:55:05 -0700, Simon Chopin wrote:

> > Thanks for the patch!
> > I have
> > - applied it in git
> > - made a cosmetical change to make it more perl-ish (or
> >   Test::More-ish) [0]
> > - tested it lightly
> Thanks! This patch being the most Perl I have ever written, I'll take
> any rewrite :D

You'll get the hang :)
 
> > I'd rather wait for the upload of OpenSSL 3.x.x to unstable, because
> > before that a full test is rather cumbersome (the skipped tests are
> > in a 3.x.x-only branch, and setting this up in an experimental chroot
> > would require a rebuild of perl-openssl-defaults first etc.).
> Fair enough, I'll apply it to Ubuntu directly then.

Makes sense, thanks.

I've updated the patch in our git repo from your Ubuntu debdiff, i.e.
added the Ubuntu-Bug field, so after an upload to Debian and a sync
to Ubuntu you should be able to drop any delta.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#944386: autopkgtest: can autopkgtest-build-qemu create a QEMU/KVM image without requiring superuser privileges?

[Johannes Schauer Marin Rodrigues]

Hi Francesco,

On Fri, 08 Nov 2019 23:59:48 +0100 "Francesco Poli (wintermute)" 
 wrote:
> Hello and thanks for maintaining autopkgtest!
> 
> I wanted to give the QEMU/KVM testbed a try. Hence I tried to create
> a VM image by using autopkgtest-build-qemu. Its man page states:
> 
> [...]
> |  Note that you need to call this as root.
> [...]
> 
> And indeed the command
> 
>   $ autopkgtest-build-qemu unstable ~/var/cache/autopkgtest/sid.img
> 
> fails, when issued by a regular user, as it cannot even find parted
> in the search PATH.
> 
> I guess this is because of vmdb2, which requires superuser privileges.
> But why?
> Is there any hope to improve vmdb2 or to use another tool, in order
> to create a KVM testbed without requiring superuser privileges?

since you reported #944485 against mmdebstrap you already know that the answer
is "Yes" but I just stumbled across this bug and wanted to share one possible
solution with the readers here as well.

How to do it is described in the mmdebstrap man page under "Use as replacement
for autopkgtest-build-qemu and vmdb2" and the TLDR is:

$ mmdebstrap --variant=important --include=linux-image-amd64 \
--customize-hook='chroot "$1" passwd --delete root' \
--customize-hook='chroot "$1" useradd --home-dir /home/user 
--create-home user' \
--customize-hook='chroot "$1" passwd --delete user' \
--customize-hook='echo host > "$1/etc/hostname"' \
--customize-hook='echo "127.0.0.1 localhost host" > "$1/etc/hosts"' \
--customize-hook=/usr/share/autopkgtest/setup-commands/setup-testbed \
unstable debian-unstable.tar
$ cat << END > extlinux.conf
> default linux
> timeout 0
>
> label linux
> kernel /vmlinuz
> append initrd=/initrd.img root=/dev/vda1 console=ttyS0
END
$ guestfish -N debian-unstable.img=disk:8G -- \
part-disk /dev/sda mbr : \
part-set-bootable /dev/sda 1 true : \
mkfs ext2 /dev/sda1 : mount /dev/sda1 / : \
tar-in debian-unstable.tar / xattrs:true : \
extlinux / : copy-in extlinux.conf / : \
sync : umount / : shutdown
$ qemu-img convert -O qcow2 debian-unstable.img debian-unstable.qcow2

Unfortunately, extlinux is only available on amd64 and i386. To support more
architectures we have to boot using grub. Because this becomes a bit more
complicated I put the whole thing into a script:

https://salsa.debian.org/debian/mmdebstrap/-/blob/master/mmdebstrap-autopkgtest-build-qemu

This now works on amd64, arm64, armhf, i386 and ppc64el. But it only works for
building *native* qemu images because guestfish cannot handle foreign
architecture emulation. I see five options that allow avoiding guestfish for
building foreign architecture bootable images without being root.

Option 1 is to run guestfish inside another qemu instance. This is extremely
slow though. Since it's also easiest to set-up I won't go further into this
option here.

Option 2 is to do the partition setup and bootloader installation as an
initramfs hook script:

main script: http://paste.debian.net/1235312/
initramfs-hook: http://paste.debian.net/1235313/
initramfs-script: http://paste.debian.net/1235314/

Option 3 is to use debian-installer and use pre-seeding to make the whole
process unattended. I managed to get this working for amd64, i386, arm64 and
ppc64el. Here is how to do it for ppc64el:

$ qemu-img create -f qcow2 disk.qcow 4G
$ curl 
https://deb.debian.org/debian/dists/bullseye/main/installer-ppc64el/current/images/netboot/debian-installer/ppc64el/initrd.gz
 > initrd.gz
$ curl 
https://deb.debian.org/debian/dists/bullseye/main/installer-ppc64el/current/images/netboot/debian-installer/ppc64el/vmlinux
 > linux
$ qemu-system-ppc64le -no-reboot -machine pseries,graphics=off -serial 
stdio -display none -monitor none -m 1G -initrd initrd.gz -kernel linux -append 
'console=hvc0 auto-install/enable=true debconf/priority=critical 
preseed/url=http://www.debian.org/releases/stable/example-preseed.txt 
netcfg/get_hostname=hostname netcfg/get_domain=domain 
passwd/root-password=r00tme passwd/root-password-again=r00tme 
passwd/user-fullname=user passwd/username=user passwd/user-password=insecure 
passwd/user-password-again=insecure pkgsel/run_tasksel=false 
popularity-contest:popularity-contest/participate=false 
grub-installer/bootdev=/dev/sda1' -hda disk.qcow

Option 4 is to use u-boot-qemu like this (in case of riscv64):

$ mmdebstrap --arch=riscv64 --variant=apt \
--include=linux-image-riscv64,u-boot-menu,systemd-sysv
--customize-hook='printf "U_BOOT_PARAMETERS=\"rw noquiet 
root=/dev/vda1\"\nU_BOOT_FDT_DIR=\"noexist\"\n" > "$1"/etc/default/u-boot' \
--customize-hook='chroot "$1" u-boot-update' \
unstable chroot.tar \
"deb http://deb.debian.org/debian-ports/ sid main" \
"deb http://deb.debian.org/debian-ports/ unreleased main"
$ genext2fs --block-size 1024 --size-in-blocks 2097152 

Bug#1010905: RFS: lirc/0.10.1-7 [RC] -- Infra-red remote control support - daemons and utils

[Alec Leamas]

Package: sponsorship-requests
Severity: important

Dear mentors,

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

 * Package name: lirc
   Version : 0.10.1-7
   Upstream Author : Alec Leamas 
 * URL : https://sf.net/p/lirc
 * License : MIT, GPL-2.0+
 * Vcs : https://gitlab.com/leamas/lirc
   Section : utils

The source builds the following binary packages:

  lirc - Infra-red remote control support - daemons and utils
  lirc-doc - Infra-red remote control support - website and manual docs
  liblirc0 - Infra-red remote control support - Run-time libraries
  liblircclient0 - Transitional placeholder for obsoleted liblircclient0
  liblircclient-dev - Transitional placeholder for obsoleted 
liblircclient-dev

  liblirc-dev - Infra-red remote control support - development files
  liblirc-client0 - infra-red remote control support - client library
  lirc-x - infra-red remote control support - X utilities

More info on https://mentors.debian.net/package/lirc/ or  using:

  dget -x 
https://mentors.debian.net/debian/pool/main/l/lirc/lirc_0.10.1-7.dsc


Changes since the last upload:

 lirc (0.10.1-7) unstable; urgency=medium
 .
   * Add patch from Fedora for failing tests. Closes: #1009389
   * Add patch avoiding build path in docs. Closes: #961954

Regards,
--
  Alec Leamas

Bug#597899: Good day

[Anna Cooper]

I'm  Miss.Anna Cooper, suffering from Leukemia. I am reaching out to you
for the purpose of charity work, I wish to donate the tune of
$4,600,000.00USD to the less privileged through you for humanitarian goals.
 kind of inheritance, my instinct asked me to contact you, hence if you can
email me for more details.

I will give you more information upon your response. (  )
Sincerely yours

Mr.Anna Cooper (Widow)
anna_cooper2...@yahoo.com

Bug#964579: lsblk not included in busybox version used with installer

[Metztli Information Technology]

Niltze- 

On Sun, May 8, 2022 at 2:06 PM Michael Tokarev  wrote:
>
> Control: tag -1 + moreinfo
>
> On Wed, 8 Jul 2020 23:23:51 + Holger Levsen  wrote:
> > Package: busybox
> > Version: 1:1.30.1-4
> > Severity: wishlist
> > x-debbugs-cc: Russell Weber 
> > submitter: Russell Weber 
> >
> > On Wed, Jul 08, 2020 at 02:43:43PM -0600, Russell Weber wrote:
> > > Package: busybox
> > > Version: 1:1.30.1-4
> > > Severity: wishlist
> > > lsblk is a very useful tool for understanding your current disks and block
> > > devices. It can be used to
> > > query lots of information including disk manufacturer, serial number, 
> > > modelb
> > > number, the structure of your disks if the disk is already in use for
> > > another block device. Given that the installer has mission critical goals
> > > associated with the disks, it's a bit of a mystery that lsblk isn't
> > > included into the busy box implementation used in the installer. This is
> > > especially important when seeding automatic/unattended installs for debian
> > > since many of the seed files used will query information from disks in
> > > scripts using the "d-i partman/early_command string" of debconf.  I can 
> > > see
> > > that this issue has been raised in multiple places online: stack overflow,
> > > IRC.  However, scanning older tickets, I was not able to find a ticket
> > > which raises the issue.  Is there any reason that lsblk as a command is 
> > > not
> > > included?  As far as I can tell, the bloat size would only be around 
> > > 20-40
> > > KiB in size.  May I suggest that we start including the lsblk binaries in
> > > the next versions of Debian?
>
> Hi Russel!
>
> Thank you for the detailed bug description.
>
> The only question remain is who will write lsblk for busybox, who
> writes the actual code to do all this?  Can you help with that,
> to collect all the mentioned information in a useful for the user
> form?
>
> This applet is not written.
>
> Thanks,
>
> /mjt
>

Busybox utilities have their limitations. For instance, I had to create 
mount/umount UDEBs
because the d-i busybox equivalents would fail on Reiser4 SFRN4/SFRN5 file 
systems when
installing Debian.

< 
https://metztli.blog/media/blogs/calli/Bullseye-SFRN5/xonecuiltzin-5.13.19-reizer4-sfrn-5.1.3.mp4?mtime=1636642043
 >

Accordingly, probably including an lsblk UDEB in d-i would likely be more 
adequate, i.e.,
the last two(2) UDEBs -- which already exist -- are required for lsblk in d-i:

lsblk-udeb_2.38-4.1_amd64.udeb
libudev1-udeb_250.4-1~bpo11+1_amd64.udeb
libsmartcols1-udeb_2.38-4.1_amd64.udeb

< https://metztli.it/bullseye/netboot-exp/d-i-lsblk.png >


netboot with lsblk UDEB included in d-i:
< https://metztli.it/bullseye/netboot-exp/metztli-reiser4.iso >
< https://metztli.it/bullseye/netboot-exp/metztli-reiser4.iso.SHA256SUM >


Best Professional Regards.

-- 
Jose R R
http://metztli.it
-
Download Metztli Reiser4: Debian Bullseye w/ Linux 5.16.20 AMD64
-
feats ZSTD compression https://sf.net/projects/metztli-reiser4/
-
or SFRN 5.1.3, Metztli Reiser5 https://sf.net/projects/debian-reiser4/
---
Official current Reiser4 resources: https://reiser4.wiki.kernel.org/

Bug#1009927: krb5: deprecated encryption type for master_key_type

[Sam Hartman]

> "Benjamin" == Benjamin Kaduk  writes:

Benjamin> I'm pretty sure that changing the master key encryption
Benjamin> type used for new databases has basically no upgrade
Benjamin> considerations and could be "just done".  Updating the
Benjamin> encryption type for that key on existing databases will
Benjamin> have nontrivial upgrade considerations (and in fact will
Benjamin> not be possible to do automatically in a maintainer script
Benjamin> in all cases).

Agreed.

Benjamin> It is even possible that we might drop that configuration
Benjamin> stanza entirely rather than just changing the encryption
Benjamin> type, though we would want to more thoroughly research the
Benjamin> consequences of doing so before actually making that
Benjamin> change.

For new installations, I think that's fine.  I think going back and
changing kdc.conf on existing installations would be fine so long as
they aren't old enough to use the pre-keytab stash file format.
As I recall that format didn't include enctype.
But I think that was a really long time ago.

I'll remove the master_key_type from kdc.conf in an upload soon.
I'll also add a news item recommending that people upgrade their master
key.
We can talk about how much automated upgrade is possible, but in the
case of kpropd, that's going to be hard.

Bug#1010877: nfoview: cannot run with some custom fonts

[Osmo Salomaa]

Should be fixed upstream now. Gtk CSS formatting was missing quotes. Apparently 
CSS doesn't require quoting for spaces, so this hasn't come up before. It's the 
parentheses here that's the problem.

https://github.com/otsaloma/nfoview/commit/9cc4592d0573b723af4453b44f45c1cf3fe59415

--
Osmo Salomaa

Bug#1010901: missing license information

[Jérémy Lal]

Forwarded: https://github.com/Keruspe/GPaste/issues/398

(but probably the bts will ignore this, I happen to never find the right
doc about it)

Le jeu. 12 mai 2022 à 19:33, Thorsten Alteholz  a
écrit :

> Package: gpaste
> Severity: serious
> User: alteh...@debian.org
> Usertags: ftp
> thanks
>
> Dear Maintainer,
>
> also mention all files under the CC-BY-SA-3.0 license in your
> debian/copyright.
>

Hi,
good catch.
It's not clear to me what is the intent of that CC-BY-SA-3.0 line in
data/appstream/org.gnome.GPaste.Ui.appdata.xml.in
Forwarded upstream...

Jérémy

Bug#1010902: RFP: mlb-statsapi -- python module wrapping the MLB Statistics API

[Joseph Nahmias]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: j...@nahmias.net, t...@toddrob.com, debian-pyt...@lists.debian.org

* Package name: mlb-statsapi
  Version : 1.4.2
  Upstream Author : Todd Roberts 
* URL : https://github.com/toddrob99/MLB-StatsAPI
* License : GPL-3
  Programming Lang: Python
  Description : python module wrapping the MLB Statistics API

Good candidate for the Debian Python Team [DPT]

Bug#1010901: missing license information

[Thorsten Alteholz]

Package: gpaste
Severity: serious
User: alteh...@debian.org
Usertags: ftp
thanks

Dear Maintainer,

also mention all files under the CC-BY-SA-3.0 license in your 
debian/copyright.


Thanks!
  Thorsten

Bug#1010658: set smtp_authenticators=login works!

[Kevin J. McCarthy]

On Thu, May 12, 2022 at 04:57:55PM +0200, Václav Ovsík wrote:

I have added

set smtp_authenticators=login

and things works now!


Great!  Thank you for checking that LOGIN works properly.  I wanted to 
make sure there weren't other problems I needed to address inside Mutt.



So the problem is with the SMTP server side?


Technically it is, but I have made a commit in Mutt to work around the 
bug.  It will be in 2.2.5, or earlier if Antonio decides to add the 
patch to the Debian package.


Thank you,

-Kevin


signature.asc
Description: PGP signature

Bug#1010900: anki: can't open preferences with python3.10

[Kacper Gutowski]

Package: anki
Version: 2.1.15+dfsg-3
Severity: normal

When I try to open Preferences, either with Ctrl+P or from menu, 
I get the following error:


Anki 2.1.15 (442df9d6) Python 3.10.4 Qt 5.15.2 PyQt 5.15.6
Platform: Linux
Flags: frz=False ao=False sv=2

Caught exception:
  File "/usr/share/anki/aqt/main.py", line 882, in onPrefs
aqt.dialogs.open("Preferences", self)
  File "/usr/share/anki/aqt/__init__.py", line 82, in open
instance = creator(*args)
  File "/usr/share/anki/aqt/preferences.py", line 25, in __init__
self.setupCollection()
  File "/usr/share/anki/aqt/preferences.py", line 80, in setupCollection
f.lrnCutoff.setValue(qc['collapseTime']/60.0)
: setValue(self, int): argument 1 has unexpected type 'float'


Anki uses #!/usr/bin/python3 which is python3.10 on testing. Running 
it with python3.9 instead fixes the problem. I suppose closing #958853 
(i.e. packaging a new upstream version) would make this irrelevant, 
but maybe it could be somehow mitigated in the meantime.


-k


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

Kernel: Linux 5.15.0-3-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages anki depends on:
ii  libjs-jquery3.6.0+dfsg+~3.5.13-1
ii  libjs-jquery-flot   4.2.1+dfsg-5
ii  libjs-jquery-ui 1.13.1+dfsg-1
ii  libjs-mathjax   2.7.9+dfsg-1
ii  libqt5core5a5.15.2+dfsg-16+b1
ii  python3 3.10.4-1+b1
ii  python3-bs4 4.11.1-1
ii  python3-decorator   4.4.2-2
ii  python3-distro  1.7.0-1
ii  python3-distutils   3.9.12-1
ii  python3-jsonschema  3.2.0-5
ii  python3-markdown3.3.7-1
ii  python3-pyaudio 0.2.11-1.4
ii  python3-pyqt5   5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtwebchannel  5.15.6+dfsg-1+b2
ii  python3-pyqt5.qtwebengine   5.15.5-1+b1
ii  python3-requests2.27.1+dfsg-1
ii  python3-send2trash  1.8.1~b0-1

Versions of packages anki recommends:
pn  python3-matplotlib  

Versions of packages anki suggests:
ii  dvipng  1.15-1.1+b1
ii  lame3.100-3
ii  mpv 0.34.1-1+b2

-- no debconf information

Bug#1004171: bash: Replace add-shell/remove-shell with declarative shells.d trigger

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Johannes Schauer Marin Rodrigues (2022-04-13 12:10:16)
> Quoting Johannes Schauer Marin Rodrigues (2022-01-22 09:25:43)
> > the attached patch replaces add-shell/remove-shell with the declarative
> > shells.d trigger from debianutils.
> > 
> > For details about this new mechanism see https://bugs.debian.org/990440.
> > 
> > This further reduces the number of maintainer scripts in the
> > Essential:yes set and is the last missing piece for DPKG_ROOT support in
> > bash.
> > 
> > I also submitted the same improvement to dash:
> > 
> > https://salsa.debian.org/debian/dash/-/merge_requests/8
> 
> the shells.d patch has been applied in dash in unstable for over a month now
> and the dash maintainer states that there have been no problems since then.
> 
> I'd thus like to send a friendly ping to this bug and ask about applying
> shells.d support from debianutils to bash as well.
> 
> If you have no objections, I can also prepare an NMU as I've done for #958083.

I've uploaded a NMU with attached debdiff to DELAYED/15.

Thanks!

cheers, joschdiff -Nru bash-5.1/debian/bash.postinst bash-5.1/debian/bash.postinst
--- bash-5.1/debian/bash.postinst	2013-10-23 14:41:22.0 +0200
+++ bash-5.1/debian/bash.postinst	2022-05-12 17:01:36.0 +0200
@@ -14,13 +14,6 @@
 10 \
   || true
 
-if [ "$1" = configure ] && dpkg --compare-versions "$2" le 3.2-3 \
-&& which add-shell >/dev/null
-then
-add-shell /bin/bash
-add-shell /bin/rbash
-fi
-
 #DEBHELPER#
 
 exit 0
diff -Nru bash-5.1/debian/bash.postrm bash-5.1/debian/bash.postrm
--- bash-5.1/debian/bash.postrm	2013-10-23 14:41:22.0 +0200
+++ bash-5.1/debian/bash.postrm	1970-01-01 01:00:00.0 +0100
@@ -1,22 +0,0 @@
-#! /bin/sh
-
-set -e
-
-case "$1" in
-upgrade|failed-upgrade|abort-install|abort-upgrade)
-	;;
-remove|purge|disappear)
-	if which remove-shell >/dev/null && [ -f /etc/shells ]; then
-	remove-shell /bin/bash
-	remove-shell /bin/rbash
-	fi
-	;;
-*)
-echo "postrm called with unknown argument \`$1'" >&2
-exit 1
-	;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff -Nru bash-5.1/debian/bash-static.postinst bash-5.1/debian/bash-static.postinst
--- bash-5.1/debian/bash-static.postinst	2013-10-23 14:41:22.0 +0200
+++ bash-5.1/debian/bash-static.postinst	1970-01-01 01:00:00.0 +0100
@@ -1,13 +0,0 @@
-#! /bin/sh
-
-set -e
-
-if [ "$1" = configure ] && dpkg --compare-versions "$2" le 3.2-4 \
-&& which add-shell >/dev/null
-then
-add-shell /bin/bash-static
-fi
-
-#DEBHELPER#
-
-exit 0
diff -Nru bash-5.1/debian/bash-static.postrm bash-5.1/debian/bash-static.postrm
--- bash-5.1/debian/bash-static.postrm	2013-10-23 14:41:22.0 +0200
+++ bash-5.1/debian/bash-static.postrm	1970-01-01 01:00:00.0 +0100
@@ -1,21 +0,0 @@
-#! /bin/sh
-
-set -e
-
-case "$1" in
-upgrade|failed-upgrade|abort-install|abort-upgrade)
-	;;
-remove|purge|disappear)
-	if which remove-shell >/dev/null && [ -f /etc/shells ]; then
-	remove-shell /bin/bash-static
-	fi
-	;;
-*)
-echo "postrm called with unknown argument \`$1'" >&2
-exit 1
-	;;
-esac
-
-#DEBHELPER#
-
-exit 0
diff -Nru bash-5.1/debian/changelog bash-5.1/debian/changelog
--- bash-5.1/debian/changelog	2022-01-06 17:16:52.0 +0100
+++ bash-5.1/debian/changelog	2022-05-12 17:05:40.0 +0200
@@ -1,3 +1,12 @@
+bash (5.1-6.1) unstable; urgency=medium
+
+  [ Helmut Grohne ]
+  * Non-maintainer upload.
+  * Replace add-shell/remove-shell with declarative shells.d trigger.
+Closes: #1004171
+
+ -- Johannes Schauer Marin Rodrigues   Thu, 12 May 2022 17:05:40 +0200
+
 bash (5.1-6) unstable; urgency=medium
 
   * Apply upstream patches 013 - 016.
diff -Nru bash-5.1/debian/control bash-5.1/debian/control
--- bash-5.1/debian/control	2021-11-27 09:37:56.0 +0100
+++ bash-5.1/debian/control	2022-05-12 17:01:36.0 +0200
@@ -17,7 +17,7 @@
 Architecture: any
 Multi-Arch: foreign
 Pre-Depends: ${shlibs:Pre-Depends}, ${misc:Depends}
-Depends: base-files (>= 2.1.12), debianutils (>= 2.15)
+Depends: base-files (>= 2.1.12), debianutils (>= 5.6-0.1)
 Recommends: bash-completion (>= 20060301-0)
 Conflicts: bash-completion (<< 20060301-0)
 Replaces: bash-doc (<= 2.05-1), bash-completion (<< 20060301-0)
@@ -39,7 +39,7 @@
 Package: bash-static
 Architecture: any
 Multi-Arch: foreign
-Depends: passwd (>= 1:4.0.3-10), ${misc:Depends}
+Depends: passwd (>= 1:4.0.3-10), debianutils (>= 5.6-0.1), ${misc:Depends}
 Suggests: bash-doc
 Section: shells
 Priority: optional
diff -Nru bash-5.1/debian/rules bash-5.1/debian/rules
--- bash-5.1/debian/rules	2021-11-27 09:50:18.0 +0100
+++ bash-5.1/debian/rules	2022-05-12 17:01:36.0 +0200
@@ -227,6 +227,9 @@
 	$(ID) debian/clear_console.1 $(d)/usr/share/man/man1/
 endif
 
+	: # /etc/shells integration
+	$(ID) -D debian/shells.d/bash $(d)/usr/share/debianutils/shells.d/bash
+
 	: # files for the bash-doc package
 
 	dh_installexamples -p$(p_doc) examples/*
@@ 

Bug#1010894: python-cheroot version number does not conform to PEP440

[julien . puydt]

Le jeudi 12 mai 2022 à 17:04 +0200, Heinrich Schuchardt a écrit :
> On 5/12/22 15:36, julien.pu...@gmail.com wrote:
> > Le jeudi 12 mai 2022 à 15:20 +0200, Heinrich Schuchardt a écrit :
> > > On 5/12/22 14:55, julien.pu...@gmail.com wrote:
> > > 
> > > > Let me ask bluntly: how is it a problem?
> > > 
> > > $ python3
> > >   >>> import cheroot
> > >   >>> print cheroot.__version__
> > > 8.6.0+ds1
> > >   >>> from distutils.version import StrictVersion
> > >   >>> StrictVersion(cheroot.__version__)
> > > Traceback (most recent call last):
> > >     File "", line 1, in 
> > >     File "/usr/lib/python3.10/distutils/version.py", line 40, in
> > > __init__
> > >   self.parse(vstring)
> > >     File "/usr/lib/python3.10/distutils/version.py", line 137, in
> > > parse
> > >   raise ValueError("invalid version number '%s'" % vstring)
> > > ValueError: invalid version number '8.6.0+ds1'
> > >   >>>
> > > 
> > > > 
> > > > If there were any issue with general Python packages versioning
> > > > in
> > > > Debian, perhaps you should contact the Debian Python
> > > > Maintainers
> > > > team?
> > > 
> > > You could patch this line to solve the problem:
> > > 
> > > cheroot/__init__.py:13:
> > > __version__ = pkg_resources.get_distribution('cheroot').version
> > 
> > Ok, distutils is unhappy, but:
> > 
> > 1. distutils is obsolete: https://peps.python.org/pep-0632/
> > 
> > 2. your example doesn't look like a real-world situation.
> 
> You err. See the linked issue on launchpad.net. Ceph does not work
> due 
> to your deviation from upstream version numbers.
> 

You're right, I had forgotten about this!

I propose to add the following patch to my package:

Description: make the package return a PEP440-compatible version number
Author: Julien Puydt
Forwarded: Debian-specific

--- python-cheroot.orig/cheroot/__init__.py
+++ python-cheroot/cheroot/__init__.py
@@ -11,5 +11,7 @@
 
 try:
 __version__ = pkg_resources.get_distribution('cheroot').version
+if __version__.find('+ds') != -1:
+__version__ = __version__[:__version__.find('+ds')]
 except Exception:
 __version__ = 'unknown'



Would that solve your issue?

Cheers,

J.Puydt

Bug#999792: npm publish and npm pack broken

[Yadd]

Hi,

this should be fixed in testing/unstable. Could you confirm ?

Cheers,
Yadd

Bug#1010894: python-cheroot version number does not conform to PEP440

[Heinrich Schuchardt]

On 5/12/22 15:36, julien.pu...@gmail.com wrote:

Le jeudi 12 mai 2022 à 15:20 +0200, Heinrich Schuchardt a écrit :

On 5/12/22 14:55, julien.pu...@gmail.com wrote:


Let me ask bluntly: how is it a problem?


$ python3
  >>> import cheroot
  >>> print cheroot.__version__
8.6.0+ds1
  >>> from distutils.version import StrictVersion
  >>> StrictVersion(cheroot.__version__)
Traceback (most recent call last):
    File "", line 1, in 
    File "/usr/lib/python3.10/distutils/version.py", line 40, in
__init__
  self.parse(vstring)
    File "/usr/lib/python3.10/distutils/version.py", line 137, in
parse
  raise ValueError("invalid version number '%s'" % vstring)
ValueError: invalid version number '8.6.0+ds1'
  >>>



If there were any issue with general Python packages versioning in
Debian, perhaps you should contact the Debian Python Maintainers
team?


You could patch this line to solve the problem:

cheroot/__init__.py:13:
__version__ = pkg_resources.get_distribution('cheroot').version


Ok, distutils is unhappy, but:

1. distutils is obsolete: https://peps.python.org/pep-0632/

2. your example doesn't look like a real-world situation.


You err. See the linked issue on launchpad.net. Ceph does not work due 
to your deviation from upstream version numbers.


Best regards

Heinrich



I don't want to diverge from upstream -- however trivial the patch,
unless there's some actual problem to fix.

Cheers,

J.Puydt

Bug#1010658: set smtp_authenticators=login works!

[Václav Ovsík]

Sorry, I was not subscribed to the bugreport… :-(

I have added

 set smtp_authenticators=login

and things works now!

 [2022-05-12 16:47:53] 5< 250-PIPELINING
 [2022-05-12 16:47:53] 5< 250-SIZE 52428800
 [2022-05-12 16:47:53] 5< 250-ENHANCEDSTATUSCODES
 [2022-05-12 16:47:53] 5< 250 X-SZNEXTENSIONS
 [2022-05-12 16:47:53] smtp_authenticate: Trying method login
 [2022-05-12 16:47:53] smtp_auth_gsasl: using mech LOGIN
 [2022-05-12 16:47:53] Authenticating (LOGIN)...
 [2022-05-12 16:47:53] 5> AUTH LOGIN
 [2022-05-12 16:47:53] 5< 334 VXNlcm5hbWU6
 [2022-05-12 16:47:53] 5> <<>>
 [2022-05-12 16:47:53] 5< 334 UGFzc3dvcmQ6
 …

So the problem is with the SMTP server side?
Thank you very much!
-- 
Zito

Bug#1010899: ITP: python3-pyst -- Python module for interacting with the Asterisk PBX

[Bernd Schumacher]

Package: wnpp
Severity: wishlist
Owner: Bernd Schumacher 

* Package name: python3-pyst
  Version : 0.8
  Upstream Author : Ralf Schlatterbeck 
* URL : https://github.com/schlatterbeck/pyst.git
* License : LGPL, PSFL
  Programming Lang: Python
  Description : Python module for interacting with the Asterisk PBX

Pyst consists of a set of interfaces and libraries to allow programming of
Asterisk from python. The library currently supports AGI, AMI, and the
parsing of Asterisk configuration files. The library also includes debugging
facilities for AGI.

In debian buster an older python2 version of pyst called python-pyst is already
maintained by Apollon Oikonomopoulos .

Now pyst supports also python3.
Apollon Oikonomopoulos told me he is a bit short on time these days,
and I could feel free to file an ITP and "adopt" the package.
Ralf Schlatterbeck told me, he likes to see the a debian python3-pyst pakage.

Bug#1005818: task-lxde-desktop: libreoffice is used as default pdf reader

[Andriy Grytsenko]

Although it appears there is another way to make that, just for LXDE,
using file /etc/xdg/lxde-mimeapps.list. May be it will be the best way
after all.

Bug#1010898: dbus-broker update from 29-4 to 30-1 kills Gnome session

[Roderich Schupp]

Package: dbus-broker
Version: 29-4
Severity: critical
X-Debbugs-Cc: roderich.sch...@gmail.com

After upgrading to dbus-broker 30-1 every Gnome session is terminated after
a few seconds. coredumpctl shows a coredump of dbus-broker (as system bus)
afterwards. Downgrading to 29-4 fixes the problem.

Unfortunately there's no dbgsym package for dbus-broker, so
I rebuild dbus-broker on my own, and reproduced the coredump with it.
See attached backtrace.



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

Kernel: Linux 5.18.0-rc6 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dbus-broker depends on:
ii  dbus-system-bus-common  1.14.0-1
ii  init-system-helpers 1.62
ii  libaudit1   1:3.0.7-1+b1
ii  libc6   2.34-0experimental4
ii  libcap-ng0  0.7.9-2.2+b2
ii  libexpat1   2.4.8-1
ii  libselinux1 3.3-1+b2
ii  libsystemd0 250.4-1
ii  systemd-sysv250.4-1

Versions of packages dbus-broker recommends:
ii  dbus-bin  1.14.0-1

dbus-broker suggests no packages.

-- no debconf information
$ sudo coredumpctl debug 598
   PID: 598 (dbus-broker)
   UID: 106 (messagebus)
   GID: 110 (messagebus)
Signal: 6 (ABRT)
 Timestamp: Thu 2022-05-12 15:45:35 CEST (3min 6s ago)
  Command Line: dbus-broker --log 4 --controller 9 --machine-id 
caea74b6a4cd4fb0923b70899fcbf683 --max-bytes 536870912 --max-fds 4096 
--max-matches 131072 --audit
Executable: /usr/bin/dbus-broker
 Control Group: /system.slice/dbus-broker.service
  Unit: dbus-broker.service
 Slice: system.slice
   Boot ID: 36c298f742824f50bd63be069bb09f9c
Machine ID: caea74b6a4cd4fb0923b70899fcbf683
  Hostname: nuc8
   Storage: 
/var/lib/systemd/coredump/core.dbus-broker.106.36c298f742824f50bd63be069bb09f9c.598.165236313500.zst
 (present)
 Disk Size: 229.2K
   Message: Process 598 (dbus-broker) of user 106 dumped core.

Module linux-vdso.so.1 with build-id 
a9dceeea750ce5ec931ba1a7c8a410c15fe86d83
Module libpthread.so.0 with build-id 
57f259dd67020116e5dc26b4af09cbe6da07c7f1
Module libdl.so.2 with build-id 
073081140383016718e36f40166bcbce3d8e7b46
Module libpcre2-8.so.0 with build-id 
5aa43e3778622f4b95261331e97a45be5b87481d
Module ld-linux-x86-64.so.2 with build-id 
1c29a692e5c9d29b6e5e1ac4c775a7756b8b375f
Module libc.so.6 with build-id 
25869a8d9ced14f5f57bfbdba67bc48443cdcc09
Module libselinux.so.1 with build-id 
67bbdc6d15e86b50fcaddb3da92029278c864375
Module libcap-ng.so.0 with build-id 
7a34dce748ca1912c47cb2e85fe8d04772a44514
Module libaudit.so.1 with build-id 
ba1f4c9df343f43c8ad6d16550ba67aece053d95
Module libm.so.6 with build-id 
6fd40290d638df4deec34df9e534b57d25a05b2a
Module dbus-broker with build-id 
52c9e6ffc9ae946613578d5c320c07a37c743cc8
Stack trace of thread 598:
#0  0x7f4312a8982c __pthread_kill_implementation (libc.so.6 
+ 0x8982c)
#1  0x7f4312a3da32 __GI_raise (libc.so.6 + 0x3da32)
#2  0x7f4312a28469 __GI_abort (libc.so.6 + 0x28469)
#3  0x7f4312a28395 __assert_fail_base (libc.so.6 + 0x28395)
#4  0x7f4312a36ae2 __GI___assert_fail (libc.so.6 + 0x36ae2)
#5  0x558749e6270b user_free (dbus-broker + 0x2070b)
#6  0x558749e5746f ref_sub (dbus-broker + 0x1546f)
#7  0x558749e576df peer_dispatch (dbus-broker + 0x156df)
#8  0x558749e6077f dispatch_context_dispatch (dbus-broker + 
0x1e77f)
#9  0x558749e477b8 broker_run (dbus-broker + 0x57b8)
#10 0x558749e46ac6 run (dbus-broker + 0x4ac6)
#11 0x7f4312a291ea __libc_start_call_main (libc.so.6 + 
0x291ea)
#12 0x7f4312a2929c __libc_start_main_impl (libc.so.6 + 
0x2929c)
#13 0x558749e46dc1 _start (dbus-broker + 0x4dc1)
ELF object binary architecture: AMD x86-64

GNU gdb (Debian 11.2-1) 11.2
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:

Bug#1005818: task-lxde-desktop: libreoffice is used as default pdf reader

[Andriy Grytsenko]

>> Since evince is automatically installed, it's "just" a matter of setting
>> evince as the default application for PDF - as you already have tried to :-)

>Sure.

Well, if evince is installed then it should exist in the XDG MIME
database and therefore it should be present in the "Open with ..." file
manager menu. Although which application will be launched on simple Open
action is defined by order:
1) use user defined default application for that MIME type
2) use system defined default application for that MIME type
3) use last registered for that MIME type by user
4) use last registered for that MIME type by system

When (1) is used - this is what we do when we associate some file with
some application, as it was said.

Usage of (2) is Debian-wide, you know, and it definitely has no relation
to LXDE package but rather to evince package (which may set system-wide
default to evince at installation and drop it at removal).

I see nothing what could be done in regards of (3) and (4) as we cannot
determine order in which packages (and especially user applications such
as WINE ones) are installed, and there is no preference order in terms of
XDG MIME database.

Please, clarify what we can do in that regard, and probably we should
reassign this issue to evince package instead if we decide it should be
set as system default.

Thanks.

Bug#1010897: ITP: python3-versioningit -- PEP 518 driven setuptools plugin for auto-versioning using git/hg

[Yaroslav Halchenko]

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

* Package name: python3-versioningit
  Version : 1.1.1
  Upstream Author : John T. Wodder II
* URL : https://github.com/jwodder/versioningit
* License : MIT
  Programming Lang: Python
  Description : PEP 518 driven setuptools plugin for auto-versioning using 
git/hg

versioningit is yet another setuptools plugin for automatically
determining your package's version based on your version control repository's
tags. Unlike others, it allows easy customization of the version format and
even lets you easily override the separate functions used for version
extraction and calculation.

Features:

- Installed & configured through PEP 518's pyproject.toml
- Supports Git, modern Git archives, and Mercurial
- Formatting of the final version uses format template strings, with fields for 
basic VCS information and separate template strings for distanced vs. dirty vs. 
distanced-and-dirty repository states
- Can optionally write the final version to a file for loading at runtime
- Provides custom setuptools commands for inserting the final version into a 
source file at build time
- The individual methods for VCS querying, tag-to-version calculation, version 
bumping, version formatting, and writing the version to a file can all be 
customized using either functions defined alongside one's project code or via 
publicly-distributed entry points
- Can alternatively be used as a library for use in setup.py or the like, in 
case you don't want to or can't configure it via pyproject.toml
- The only thing it does is calculate your version and optionally write it to a 
file; there's no overriding of your sdist contents based on what's in your Git 
repository, especially not without a way to turn it off, because that would 
just be rude.

Bug#1010894: python-cheroot version number does not conform to PEP440

[julien . puydt]

Le jeudi 12 mai 2022 à 15:20 +0200, Heinrich Schuchardt a écrit :
> On 5/12/22 14:55, julien.pu...@gmail.com wrote:
> 
> > Let me ask bluntly: how is it a problem?
> 
> $ python3
>  >>> import cheroot
>  >>> print cheroot.__version__
> 8.6.0+ds1
>  >>> from distutils.version import StrictVersion
>  >>> StrictVersion(cheroot.__version__)
> Traceback (most recent call last):
>    File "", line 1, in 
>    File "/usr/lib/python3.10/distutils/version.py", line 40, in
> __init__
>  self.parse(vstring)
>    File "/usr/lib/python3.10/distutils/version.py", line 137, in
> parse
>  raise ValueError("invalid version number '%s'" % vstring)
> ValueError: invalid version number '8.6.0+ds1'
>  >>>
> 
> > 
> > If there were any issue with general Python packages versioning in
> > Debian, perhaps you should contact the Debian Python Maintainers
> > team?
> 
> You could patch this line to solve the problem:
> 
> cheroot/__init__.py:13:
> __version__ = pkg_resources.get_distribution('cheroot').version

Ok, distutils is unhappy, but:

1. distutils is obsolete: https://peps.python.org/pep-0632/

2. your example doesn't look like a real-world situation.

I don't want to diverge from upstream -- however trivial the patch,
unless there's some actual problem to fix.

Cheers,

J.Puydt

Bug#1010896: freeplane: Exporting to PDF renders wrong font types

[Antonio M . López Alonso]

Package: freeplane
Version: 1.7.10-1
Severity: normal
X-Debbugs-Cc: a...@ipna.csic.es

Dear maintainers,

Exporting to PDF renders wrong font types (i.e. sans-serif fonts turn to serif
ones) and also some spaces between words seem to be squashed even overlapping
involved words.

This does not happen when exporting to other formats (XHTML, SVG), nor when
ticking "Convert text to images" (sorry if this is not the right title in 
English but I do
use Spanish packages).

Also PDF files are heavier than previous files when the exporting function was
working properly (MB rather than kB).

Regards,
Antonio


-- Package-specific info:
[debug] /usr/bin/freeplane: Picking up the JVM designated by the alternatives 
system: 
[debug] /usr/bin/freeplane:   JAVA_HOME = '/usr/lib/jvm/java-11-openjdk-amd64'
[debug] /usr/bin/freeplane: Found JAVA_HOME = 
'/usr/lib/jvm/java-11-openjdk-amd64'
[debug] /usr/bin/freeplane: Found JAVA_CMD = 
'/usr/lib/jvm/java-11-openjdk-amd64/bin/java'
DEBUG:   Freeplane parameters are ''.
DEBUG:   Linux nivaria 5.10.0-13-amd64 #1 SMP Debian 5.10.106-1 (2022-03-17) 
x86_64 GNU/Linux
No LSB modules are available.
DEBUG:   Distributor ID:Debian
Description:Debian GNU/Linux 11 (bullseye)
Release:11
Codename:   bullseye
DEBUG:   The following DEB packages are installed:
ii  freeplane 1.7.10-1  
   all  Java program for working with Mind Maps
DEBUG:   Link '/usr/bin/freeplane' resolved to 
'/usr/share/freeplane/freeplane.sh'.
DEBUG:   Freeplane Directory is '/usr/share/freeplane'.
DEBUG:   Calling: /usr/lib/jvm/java-11-openjdk-amd64/bin/java
 -Xmx512m
 -Dorg.freeplane.basedirectory=/usr/share/freeplane
 -Dorg.freeplane.userfpdir=/home/amla/.config/freeplane
 -Dorg.freeplane.old_userfpdir=/home/amla/.freeplane
 -Dorg.freeplane.globalresourcedir=/usr/share/freeplane/resources
 -Dswing.systemlaf=javax.swing.plaf.metal.MetalLookAndFeel
 -Dorg.freeplane.os.lib.ext=/usr/share/java
 -Dawt.useSystemAAFontSettings=on
 -Dswing.aatext=true
 -Dgnu.java.awt.peer.gtk.Graphics=Graphics2D
 -jar
 /usr/share/freeplane/freeplanelauncher.jar

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

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

Versions of packages freeplane depends on:
ii  darcula  2018.2-2
ii  default-jre [java8-runtime]  2:1.11-72
ii  groovy   2.4.21-1
ii  ivy  2.5.0-1
ii  javahelp22.0.05.ds1-9.1
ii  jmapviewer   2.14+dfsg-1
ii  libavalon-framework-java 4.2.0-10
ii  libbatik-java1.12-4
ii  libcommons-codec-java1.15-1
ii  libcommons-io-java   2.8.0-1
ii  libcommons-lang-java 2.6-9
ii  libcommons-logging-java  1.2-2
ii  libdata-url-java 1.0.1-2
ii  libfop-java  1:2.5-3
ii  libiconloader-java   0.0+git20170615+dfsg1-2
ii  libidw-java  1.6.1-1.1
ii  libjaxp1.3-java  1.3.05-6
ii  libjgoodies-forms-java   1.9.0-3.1
ii  libjlatexmath-java   1.0.7-3
ii  libjsyntaxpane-java  0.9.6~r156-7.1
ii  libknopflerfish-osgi-framework-java  6.1.1-3.1
ii  libmnemonicsetter-java   0.5-1.1
ii  librhino-java1.7.7.2-3
ii  libsvgsalamander-java1.1.1+dfsg-3
ii  libxerces2-java  2.12.1-1
ii  libxml-commons-external-java 1.4.01-5
ii  libxmlgraphics-commons-java  2.4-2~deb11u1
ii  openjdk-11-jre [java8-runtime]   11.0.15+10-1~deb11u1
ii  simplyhtml   0.17.3+dfsg1-1

Versions of packages freeplane recommends:
ii  java-wrappers  0.3
ii  xdg-utils  1.1.3-4.1

Versions of packages freeplane suggests:
pn  freeplane-scripting-api  

-- no debconf information

-- 
BEGIN:VCARD
VERSION:3.0
EMAIL;TYPE=OTHER:a...@ipna.csic.es
FN:Antonio M. López Alonso
LOGO;ENCODING=b;TYPE=png:iVBORw0KGgoNSUhEUgAAALQAAAC0CAY9zQYyCX
 BIWXMAAAxOAAAMTgF/d4wjGXRFWHRTb2Z0d2FyZQB3d3cuaW5rc2NhcGUub3Jnm+48GgAAE
 LNJREFUeJzt3X10VPWZwPHvc2eSgIiCp9SCgSQYIYkU2cWXKou1q9XFtb6tWIUEEV0ovq/rntY9
 nqV6enTd3e76LmJboQmskqN1rYov3V27RbZW8QUwCRUkAaqrqFXkLcnMffaPm8BMMi93Zu5MJvB
 8zsk5mcnv5Qk8+c29v/u7vwvGGGOMMcYYY4wxxhhjjDHGGGOMMcYYY4wxxhhjjDHGGGOMMcYYY4
 wxwVrw/Cl1Ax2DMblyer8JESq/5vlpswcyGGNytT+hd+w65j8VvWPBc9NOHMiAjMnF/oRuvrQ5i
 

Bug#1010894: python-cheroot version number does not conform to PEP440

[Heinrich Schuchardt]

On 5/12/22 14:55, julien.pu...@gmail.com wrote:

Hi,

Le jeudi 12 mai 2022 à 14:45 +0200, Heinrich Schuchardt a écrit :

Package: python-cheroot
Version: 8.6.0+ds1-2
Severity: normal

Python package versions like 8.6.0+ds1 do not conform to PEP440. This
leads to errors in Ceph as reported in
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1967139



It's not a Python package version ; it's a Debian package version, so
PEP440 doesn't apply.


Unfortunately this number is propagated into cheroot.__version__.




Is this something to be corrected in this package?
Or is this a general problem with how we do Python packaging?


Let me ask bluntly: how is it a problem?


$ python3
>>> import cheroot
>>> print cheroot.__version__
8.6.0+ds1
>>> from distutils.version import StrictVersion
>>> StrictVersion(cheroot.__version__)
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3.10/distutils/version.py", line 40, in __init__
self.parse(vstring)
  File "/usr/lib/python3.10/distutils/version.py", line 137, in parse
raise ValueError("invalid version number '%s'" % vstring)
ValueError: invalid version number '8.6.0+ds1'
>>>



If there were any issue with general Python packages versioning in
Debian, perhaps you should contact the Debian Python Maintainers team?


You could patch this line to solve the problem:

cheroot/__init__.py:13:
__version__ = pkg_resources.get_distribution('cheroot').version

Best regards

Heinrich



Cheers,

J.Puydt

Bug#416695: Advertisement in rarp.8 manual

[наб]

retitle 416695 Advertisement in rarp.8 manual
tags 416695 + patch
thanks

Hi!

This still persists, unchanged since 2007, except now dementia.org is a
content-free ad farm.

I'm attaching two patches:
  rarp.8-ad which simply replaces that text with
"install the rarpd package"
(there is no upstream, according to rarpd d/watch:
 # The location used to be at http://rawhide.redhat.com/,
 # but seems to be extinct now.
)
  rarp-deletion which removes rarp and rarp.8 from the distribution;
rarp.8 itself says it's useless since Linux "2.3",
so the latest supported release is 2.2.26
(or, well, you could say 2.2.27-rc1),
which EOLed over a decade ago; it's before snapshot.d.o
reaches so I can't say for certain w/o inspecting
install ISOs, but I'd hazard a guess the last compatible
Debian for it was the 2.x-series, either Slink or Potato.
All it says is
  $ rarp -a
  This kernel does not support RARP.
Let it die.

The latter yields the following debdiff:
-- >8 --
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/share/man/de/man8/rarp.8.gz
-rw-r--r--  root/root   /usr/share/man/fr/man8/rarp.8.gz
-rw-r--r--  root/root   /usr/share/man/man8/rarp.8.gz
-rw-r--r--  root/root   /usr/share/man/pt_BR/man8/rarp.8.gz
-rwxr-xr-x  root/root   /sbin/rarp

Control files: lines which differ (wdiff format)

 [-rarp,-]
Installed-Size: [-991-] {+945+}
-- >8 --

Best,
наб
--- net-tools-1.60+git20181103.0eebece.orig/man/en_US/rarp.8
+++ net-tools-1.60+git20181103.0eebece/man/en_US/rarp.8
@@ -13,8 +13,9 @@ rarp \- manipulate the system RARP table
 .P
 This program is obsolete.  From version 2.3, the Linux kernel 
 no longer contains RARP support.  For a replacement RARP daemon, see
-.I
-ftp://ftp.dementia.org/pub/net\-tools
+the
+.B rarpd
+package.
 .SH DESCRIPTION
 .B Rarp
 manipulates the kernel's RARP table in various ways.  The primary options
diff --git a/net-tools-1.60+git20181103.0eebece.orig/debian/control 
b/net-tools-1.60+git20181103.0eebece/debian/control
index 3966fe7..0789a63 100644
--- a/net-tools-1.60+git20181103.0eebece.orig/debian/control
+++ b/net-tools-1.60+git20181103.0eebece/debian/control
@@ -21,7 +21,7 @@ Depends: ${misc:Depends},
 Description: NET-3 networking toolkit
  This package includes the important tools for controlling the network
  subsystem of the Linux kernel.  This includes arp, ifconfig, netstat,
- rarp, nameif and route.  Additionally, this package contains utilities
+ nameif and route.  Additionally, this package contains utilities
  relating to particular network hardware types (plipconfig, slattach,
  mii-tool) and advanced aspects of IP configuration (iptunnel, ipmaddr).
  .
diff --git a/net-tools-1.60+git20181103.0eebece.orig/debian/install 
b/net-tools-1.60+git20181103.0eebece/debian/install
index 950abb2..eb9d2ee 100644
--- a/net-tools-1.60+git20181103.0eebece.orig/debian/install
+++ b/net-tools-1.60+git20181103.0eebece/debian/install
@@ -6,6 +6,5 @@ mii-tool/sbin
 nameif /sbin
 netstat/bin
 plipconfig /sbin
-rarp   /sbin
 route  /sbin
 slattach   /sbin
diff --git a/net-tools-1.60+git20181103.0eebece.orig/debian/rules 
b/net-tools-1.60+git20181103.0eebece/debian/rules
index 4cd8fbb..a96cd56 100755
--- a/net-tools-1.60+git20181103.0eebece.orig/debian/rules
+++ b/net-tools-1.60+git20181103.0eebece/debian/rules
@@ -20,10 +20,10 @@ COPTS := -D_GNU_SOURCE -Wall $(shell dpkg-buildflags --get 
CFLAGS) \
 $(shell dpkg-buildflags --get CPPFLAGS)
 LOPTS := $(shell dpkg-buildflags --get LDFLAGS)
 
-PROGS= ifconfig arp netstat route rarp slattach plipconfig \
+PROGS= ifconfig arp netstat route slattach plipconfig \
 nameif iptunnel ipmaddr mii-tool
 MANPAGES = arp.8 ethers.5 ifconfig.8 mii-tool.8 nameif.8 netstat.8 \
-  plipconfig.8 rarp.8 route.8 slattach.8
+  plipconfig.8 route.8 slattach.8
 DEB_MANPAGES = iptunnel.8
 
 %:


signature.asc
Description: PGP signature

Bug#762521: gpaste: distribute gpaste-applet snippet

[Jérémy Lal]

Source: gpaste
Version: 3.42.6-1
Followup-For: Bug #762521

https://github.com/Keruspe/gpaste-applet
is just a simple executable that relies on gir to launch gpaste UI.

It could be distributed easily.


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

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

Bug#1006513: fixed in openpace 1.1.2+ds-1

[Gianfranco Costamagna]

control: reopen -1
control: notfixed -1 1.1.2+ds-1
control: tags -1 patch

https://launchpad.net/ubuntu/+source/openpace/1.1.2+ds-1ubuntu1

Hello, looks like you need 3 additional upstream commits released after 1.1.2 
to properly make it build with openssl 3.0

2d94a152dd36543d2a713f1abe20717fdaafae0a, 
4c22789d264bd249cfff1c3e69466991e58a76cf and 
2c8a76873da4862dbf4240c901f3e6d4bc040a.

G.

On Wed, 11 May 2022 07:49:00 + Debian FTP Masters 
 wrote:

Source: openpace
Source-Version: 1.1.2+ds-1
Done: Andrej Shadura 

We believe that the bug you reported is fixed in the latest version of
openpace, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1006...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrej Shadura  (supplier of updated openpace package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 11 May 2022 09:42:31 +0200
Source: openpace
Architecture: source
Version: 1.1.2+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura 
Changed-By: Andrej Shadura 
Closes: 1006513
Changes:
 openpace (1.1.2+ds-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1006513).
   * Fix the Git URLs.
   * Add debian/watch.
Checksums-Sha1:
 14f53774bfbc28628b1c05897476cb8f0d6989d3 1542 openpace_1.1.2+ds-1.dsc
 6b6fbe55250008e0d87be561d4069c3b32eda0f0 878336 openpace_1.1.2+ds.orig.tar.xz
 5c826b5a28f22c55cc954f38511389f4a5def407 3712 openpace_1.1.2+ds-1.debian.tar.xz
Checksums-Sha256:
 6949673f752405bf4464fb033e67cdb78298fc86f530cdf784292f16ccdb1030 1542 
openpace_1.1.2+ds-1.dsc
 732e1653ca64efcd62e4ff71269b387ae038c66cdd3092fba1db8663f7c97dd8 878336 
openpace_1.1.2+ds.orig.tar.xz
 a94a1aa02f88635746b6d541f80659df537459f7f13bd0a7cfd3220409a900cf 3712 
openpace_1.1.2+ds-1.debian.tar.xz
Files:
 9a5ad1fca6ed47fbb8ffb26e6c442af9 1542 misc optional openpace_1.1.2+ds-1.dsc
 16b9efca3d1f51dc7537cf27cfa576b3 878336 misc optional 
openpace_1.1.2+ds.orig.tar.xz
 024453aaf53a97b7ff13abd5dbbf2e03 3712 misc optional 
openpace_1.1.2+ds-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCYntpWgAKCRDoRGtKyMdy
YREkAQD+TD3hU5vd6Fr0FZF6NqJT5ai0fOnq49B2JpVIuaY+8AEA7g1no/d2fAOm
ayOa0xz51CzrCazCVplDXt0k9w+TzgY=

Bug#1010152: emacs-gtk: tries to read a config file from another user's home dir

[Vincent Lefevre]

Control: tags -1 patch

I've attached the patch.

(Unfortunately, I get an unrelated failure in the tests; bug 1010170.)

On 2022-04-25 14:26:29 +0200, Vincent Lefevre wrote:
> After wondering why Emacs was hanging on startup after a reinstallation
> of machines with Debian 11 at my lab, I looked at the strace output
> (strace -o str.out -f /usr/bin/emacs-gtk -Q) and could see:
[...]
> -- System Information:
> Debian Release: bookworm/sid
[...]

To clarify, I reported the bug from a Debian/unstable machine,
but the bug *also* occurs in Debian 11 (bullseye).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Description: Fix search for init file (GNU Emacs 27.1).
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010152

Patch from https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42827#16

diff --git a/src/xrdb.c b/src/xrdb.c
index e3a1fcb15a..3d7f715c88 100644
--- a/src/xrdb.c
+++ b/src/xrdb.c
@@ -289,9 +289,9 @@ get_user_app (const char *class)
   /* Check in the home directory.  This is a bit of a hack; let's
 	 hope one's home directory doesn't contain ':' or '%'.  */
   char const *home = get_homedir ();
-  db = search_magic_path (home, class, "%L/%N");
+  db = search_magic_path (home, class, "/%L/%N");
   if (! db)
-	db = search_magic_path (home, class, "%N");
+	db = search_magic_path (home, class, "/%N");
 }
 
   return db;

Bug#1010894: python-cheroot version number does not conform to PEP440

[Heinrich Schuchardt]

Package: python-cheroot
Version: 8.6.0+ds1-2
Severity: normal

Hello Julien,

Python package versions like 8.6.0+ds1 do not conform to PEP440. This 
leads to errors in Ceph as reported in

https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1967139

Allowable package versions are defined in PEP440 
(https://peps.python.org/pep-0440/) as

[N!]N(.N)*[{a|b|rc}N][.postN][.devN]

So 8.6.0a1 would be legal. 8.6.0+ds1 is illegal.

Is this something to be corrected in this package?
Or is this a general problem with how we do Python packaging?

Best regards

Heinrich

Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies

[Andreas Beckmann]

On 12/05/2022 09.57, Paul Gevers wrote:

I: No Linux header packages are installed. Installing all available ones:
I:   linux-headers-5.17.0-1-arm64
I:   linux-headers-5.17.0-1-cloud-arm64
I:   linux-headers-5.17.0-1-rt-arm64
I:   linux-headers-arm64
I:   linux-headers-cloud-arm64
I:   linux-headers-rt-arm64
I:   linux-headers-5.17.0-2-arm64
I:   linux-headers-5.17.0-2-cloud-arm64
I:   linux-headers-5.17.0-2-rt-arm64
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  linux-headers-5.17.0-2-arm64 : Depends: linux-kbuild-5.17 (>= 
5.17.6-1) but 5.17.3-1 is to be installed
  linux-headers-5.17.0-2-cloud-arm64 : Depends: linux-kbuild-5.17 (>= 
5.17.6-1) but 5.17.3-1 is to be installed
  linux-headers-5.17.0-2-rt-arm64 : Depends: linux-kbuild-5.17 (>= 
5.17.6-1) but 5.17.3-1 is to be installed

E: Unable to correct problems, you have held broken packages.
E: Linux headers failed to install
autopkgtest [12:19:58]: test dkms-autopkgtest


That dependency problem should resolve automatically once src:linux gets 
decrufted.
But we should probably have a better way to enumerate "all 
linux-header-* packages" in dkms-autopkgtest ... and skip cruft ...


Will think about it post-holidays ...

Andreas

Bug#1010893: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142.

[Paul Menzel]

Package: docker.io
Version: 20.10.14+dfsg1-1
Severity: normal

Dear Debian folks,


On Debian sid/unstable installing *docker.io* the error below is shown:

Setting up docker.io (20.10.14+dfsg1-1+b1) ...
Installing new version of config file /etc/default/docker ...
Installing new version of config file /etc/init.d/docker ...
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

The package seems to be installed correctly though.


Kind regards,

Paul

Bug#1004347: wireless-regdb: Remove the suggestion

[Alexandre Ghiti]

Package: wireless-regdb
Version: 2021.08.28
Followup-For: Bug #1004347
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to remove the obsolete
suggestion.

Thanks for considering the patch.


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

Kernel: Linux 5.15.0-27-generic (SMP w/16 CPU threads)
Kernel taint flags: TAINT_WARN
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
diff -Nru wireless-regdb-2021.08.28/debian/control 
wireless-regdb-2021.08.28/debian/control
--- wireless-regdb-2021.08.28/debian/control2021-08-28 18:56:48.0 
+0200
+++ wireless-regdb-2021.08.28/debian/control2022-05-12 13:10:31.0 
+0200
@@ -15,7 +15,6 @@
 Architecture: all
 Multi-Arch: foreign
 Depends: ${misc:Depends}
-Suggests: crda
 Description: wireless regulatory database
  This package contains the wireless regulatory database used by the Central
  Regulatory Database Agent (CRDA) to configure wireless devices to operate

Bug#1009598: reassigned this bug to node-postcss-loader

[Akshay S Dinesh]

On Wed, 11 May 2022 11:23:52 +0200 Georges Khaznadar 
 wrote:

Hello,

the errors raised during the build of node-ktex are due to an error
which comes from node-postcss-loader



I can confirm the bug is in node-postcss-loader

It is because webpack 5 is required for this version of postcss-loader.

https://github.com/webpack-contrib/postcss-loader/issues/514

Bug#1005301: ITP: python-dt-schema -- Devicetree schema tools

[Bastian Germann]

Am 12.05.22 um 12:54 schrieb Bastian Germann:

On Thu, 10 Feb 2022 21:51:17 +0100 Romain Porte  wrote:

* Package name    : python-dt-schema
  Version : 2022.01


This version should be the last version that does not need jsonschema 4.*.
So just package this older version and you will not need #1005757 fixed or pylibfdt packaged (which would be another 
unpackaged dep for later versions).


It is actually 2021.10 that has these properties. README is out of sync with 
setup.py in-between.




  Upstream Author : Devicetree Specification 
* URL : http://www.devicetree.org
* License : BSD-2-Clause
  Programming Lang: Python
  Description : Devicetree schema tools

The tools contained in this package are used by the Linux kernel for
doing device-tree specification validation.

Bug#1010878: installation-reports: preseeding passwords doesn't work on mips64el under qemu

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Philip Hands (2022-05-12 10:14:46)
> > So for some reason passwd/root-password-again is ignored. Above recipe
> > works fine for other architectures and for some reason stops with above
> > prompt on mips64el. Why?
> 
> It seems that you are hitting a limit on the length of the command line.
> 
> If you flip to one of the shells (Ctrl-A Ctrl-A 2) and do:
> 
>   cat /proc/cmdline

Ah thank you! I probably missed that in the docs (this is probably screen
running?). This is very helpful. :)

> you'll see that most of your kernel commandline is missing.  I'd guess
> that's a limitation of mips64el.  Probably best to specify a preseed
> file in order to get round this limitation, either by url, or you could
> try this:
> 
>   
> https://wiki.debian.org/DebianInstaller/Preseed/EditIso#Adding_a_Preseed_File_to_the_Initrd

Ouch... that's a very unexpected architecture specific limitation. Thanks a lot
for your very quick help!

I wasn't sure where to direct my d-i "bug" reports to. Context is, that I'm
running d-i inside qemu to create bootable disk images that can then be used
with autopkgtest-virt-qemu. So far amd64, i386, ppc64el and arm64 work well.
I'm running into problems with the network interface on s390x but I'm maybe
just driving QEMU wrongly.

I assume that somebody is already running d-i in QEMU for multiple
architectures somewhere as part of some d-i CI infrastructure? If that already
exists, I'd welcome a pointer because I'm probably re-inventing the wheel here.
:)

Otherwise, feel free to close this bug report.

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1010892: audacity: Length and position of selection is not shown correctly

[Dennis Real]

Package: audacity
Version: 2.4.2~dfsg0-5
Severity: normal
X-Debbugs-Cc: reportbug_deb...@tildepipe.org

Dear Maintainer,

Steps to reproduce:

1. Open .wav/.ogg file in audacity 2.4.2
2. Select length and end position as selection option below
3. Make a short selection (e.g. 4 samples long)
4. Change length and position unit to "samples"

Expected Result:
"000 000 004 Samples" as length is shown

Result:
"004 000 000 Samples" as length is shown


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

Kernel: Linux 5.15.0-27-generic (SMP w/4 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages audacity depends on:
ii  audacity-data 2.4.2~dfsg0-5
ii  libavcodec58  7:4.4.1-3ubuntu5
ii  libavformat58 7:4.4.1-3ubuntu5
ii  libavutil56   7:4.4.1-3ubuntu5
ii  libc6 2.35-0ubuntu3
ii  libexpat1 2.4.7-1
ii  libflac++6v5  1.3.3-2build2
ii  libflac8  1.3.3-2build2
ii  libgcc-s1 12-20220319-1ubuntu1
ii  libgdk-pixbuf-2.0-0   2.42.8+dfsg-1
ii  libglib2.0-0  2.72.1-1
ii  libgtk-3-03.24.33-1ubuntu1
ii  libid3tag00.15.1b-14
ii  liblilv-0-0   0.24.12-2
ii  libmad0   0.15.1b-10ubuntu1
ii  libogg0   1.3.5-0ubuntu3
ii  libportaudio2 19.6.0-1.1
ii  libportsmf0v5 0.1~svn20101010-5ubuntu2
ii  libsndfile1   1.0.31-2build1
ii  libsoundtouch12.3.1+ds1-1
ii  libsoxr0  0.1.3-4build2
ii  libstdc++612-20220319-1ubuntu1
ii  libsuil-0-0   0.10.10-1
ii  libtwolame0   0.4.0-2build2
ii  libvamp-hostsdk3v52.10.0-1
ii  libvorbis0a   1.3.7-1build2
ii  libvorbisenc2 1.3.7-1build2
ii  libvorbisfile31.3.7-1build2
ii  libwxbase3.0-0v5  3.0.5.1+dfsg-4
ii  libwxgtk3.0-gtk3-0v5  3.0.5.1+dfsg-4

audacity recommends no packages.

Versions of packages audacity suggests:
pn  ladspa-plugin  

-- no debconf information

Bug#1010891: libcloud: autopkgtest failure on big-endian architectures

[Olivier Gayot]

Package: libcloud
Version: 3.4.1-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Dear Maintainer,

Since the move to upstream 3.4.1, a new test breaks autopkgtest on
big-endian architectures:

  chan.recv.side_effect = ['臘'.encode('utf-32'), 'a', 'b']
  
  stdout = client._consume_stdout(chan).getvalue()
  > self.assertEqual('\x00\x00&\x01\x00ab', stdout)
  E AssertionError: '\x00\x00&\x01\x00ab' != '\x00\x00\x00\x01'
  
  test/compute/test_ssh_client.py:563: AssertionError

In Ubuntu, the attached patch was applied to achieve the following:

  * Fix autopkgtest failure on s390x (big-endian) (LP: #1973158)
  * The bug also affects Debian as shown in this log:
  
https://ci.debian.net/data/autopkgtest/testing/s390x/libc/libcloud/21309362/log.gz


Thanks for considering the patch.


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

Kernel: Linux 5.15.0-27-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libcloud-3.4.1/debian/control libcloud-3.4.1/debian/control
--- libcloud-3.4.1/debian/control   2022-05-11 15:51:43.0 +0200
+++ libcloud-3.4.1/debian/control   2022-05-11 15:51:43.0 +0200
@@ -1,8 +1,7 @@
 Source: libcloud
 Section: python
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian Python Team 
+Maintainer: Debian Python Team 
 Uploaders:
  Soren Hansen ,
  Hans-Christoph Steiner ,
diff -Nru 
libcloud-3.4.1/debian/patches/df060de6ea325cba2b6411780728705252543bc3.patch 
libcloud-3.4.1/debian/patches/df060de6ea325cba2b6411780728705252543bc3.patch
--- 
libcloud-3.4.1/debian/patches/df060de6ea325cba2b6411780728705252543bc3.patch
1970-01-01 01:00:00.0 +0100
+++ 
libcloud-3.4.1/debian/patches/df060de6ea325cba2b6411780728705252543bc3.patch
2022-05-11 15:51:43.0 +0200
@@ -0,0 +1,45 @@
+Description: test: fix test_ssh_client on big-endian architectures
+ The tests test_consume_*_chunk_contains_no_utf8_character are meant to
+ ensure support for non-UTF-8 characters. To do so, we use UTF-8
+ characters and compare their binary representation after being fed to
+ paramiko.
+ 
+ Unfortunately, UTF-32 is affected by endianness, resulting in failed
+ tests on big-endian architectures.
+ 
+ Fixed by checking the endianness and comparing the UTF-32 characters to
+ their respective binary representation.
+Author: Olivier Gayot 
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libcloud/+bug/1973158
+Forwarded: https://github.com/apache/libcloud/pull/1693
+Last-Update: 2022-05-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: libcloud-3.4.1/libcloud/test/compute/test_ssh_client.py
+===
+--- libcloud-3.4.1.orig/libcloud/test/compute/test_ssh_client.py   
2022-05-12 12:36:47.037706112 +0200
 libcloud-3.4.1/libcloud/test/compute/test_ssh_client.py2022-05-12 
12:37:34.529747766 +0200
+@@ -560,7 +560,10 @@
+ chan.recv.side_effect = ['臘'.encode('utf-32'), 'a', 'b']
+ 
+ stdout = client._consume_stdout(chan).getvalue()
+-self.assertEqual('\x00\x00&\x01\x00ab', stdout)
++if sys.byteorder == "little":
++self.assertEqual("\x00\x00&\x01\x00ab", stdout)
++else:
++self.assertEqual("\x00\x00\x00\x01", stdout)
+ self.assertEqual(len(stdout), 7)
+ 
+ def test_consume_stderr_chunk_contains_non_utf8_character(self):
+@@ -574,7 +577,10 @@
+ chan.recv_stderr.side_effect = ['臘'.encode('utf-32'), 'a', 'b']
+ 
+ stderr = client._consume_stderr(chan).getvalue()
+-self.assertEqual('\x00\x00&\x01\x00ab', stderr)
++if sys.byteorder == "little":
++self.assertEqual("\x00\x00&\x01\x00ab", stderr)
++else:
++self.assertEqual("\x00\x00\x00\x01", stderr)
+ self.assertEqual(len(stderr), 7)
+ 
+ def test_keep_alive_and_compression(self):
diff -Nru libcloud-3.4.1/debian/patches/series 
libcloud-3.4.1/debian/patches/series
--- libcloud-3.4.1/debian/patches/series2022-05-11 15:51:43.0 
+0200
+++ libcloud-3.4.1/debian/patches/series2022-05-11 15:51:43.0 
+0200
@@ -3,3 +3,4 @@
 43b71091ebd159570302b695f0a244f4d0a7e497.patch
 83bd562337abdda4b1ba6706999b13aa358bdd28.patch
 disable-online-test.patch
+df060de6ea325cba2b6411780728705252543bc3.patch

Bug#1005301: ITP: python-dt-schema -- Devicetree schema tools

[Bastian Germann]

On Thu, 10 Feb 2022 21:51:17 +0100 Romain Porte  wrote:

* Package name: python-dt-schema
  Version : 2022.01


This version should be the last version that does not need jsonschema 4.*.
So just package this older version and you will not need #1005757 fixed or pylibfdt packaged (which would be another 
unpackaged dep for later versions).



  Upstream Author : Devicetree Specification 
* URL : http://www.devicetree.org
* License : BSD-2-Clause
  Programming Lang: Python
  Description : Devicetree schema tools

The tools contained in this package are used by the Linux kernel for
doing device-tree specification validation.

Bug#668462: network-manager: Wrong default for IPv6 Privacy Extensions

[Sam Morris]

Control: tags -1 + moreinfo

On Thu, Apr 12, 2012 at 01:47:18AM +0200, Juerd Waalboer wrote:
> It appears that when ip6-privacy is not defined, it defaults to 0. I believe
> that it should default to nothing at all and leave the sysctl value at 
> whatever
> value was set without the help of NetworkManager. Users who had enabled IPv6
> Privacy Extensions will probably have done so by adding a manual sysctl for
> net.ipv6.conf.*.use_tempaddr; the current NetworkManager overrides this value,
> possibly disabling previously perfectly functioning IPv6 Privacy Extensions.

Is this still the case? NetworkManager.conf(5) says:

ipv6.ip6-privacy
   If ipv6.ip6-privacy is unset, use the content of 
"/proc/sys/net/ipv6/conf/default/use_tempaddr" as last fallback.

-- 
Sam Morris 
PGP: rsa4096/CAAA AA1A CA69 A83A 892B  1855 D20B 4202 5CDA 27B9

Bug#1010889: network-manager: Please ship additional NM config examples found in examples/nm-conf.d/

[Sam Morris]

Package: network-manager
Version: 1.37.92-1
Severity: wishlist

examples/nm-conf.d has a couple of drop-in example config files that it
would be nie to find in /usr/share/doc/network-manager/examples.

In particular, 30-anon.conf shows how to configure NM so that it won't
leak information to the network provider via DHCP identifiers.


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

Kernel: Linux 5.10.0-13-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_DIE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 network-manager depends on:
ii  adduser  3.121
ii  dbus 1.14.0-1
ii  libaudit11:3.0.7-1+b1
ii  libbluetooth35.64-2
ii  libc62.33-7
ii  libcurl3-gnutls  7.83.0-1
ii  libglib2.0-0 2.72.1-1
ii  libgnutls30  3.7.4-2
ii  libjansson4  2.14-2
ii  libmm-glib0  1.18.6-2
ii  libndp0  1.8-1
ii  libnewt0.52  0.52.21-5+b1
ii  libnm0   1.37.92-1
ii  libpsl5  0.21.0-1.2
ii  libreadline8 8.1.2-1.2
ii  libselinux1  3.3-1+b2
ii  libsystemd0  250.4-1
ii  libteamdctl0 1.31-1
ii  libudev1 250.4-1
ii  policykit-1  0.105-33
ii  udev 250.4-1

Versions of packages network-manager recommends:
ii  dnsmasq-base [dnsmasq-base]  2.86-1.1
ii  libpam-systemd   250.4-1
pn  modemmanager 
pn  ppp  
ii  wireless-regdb   2021.08.28-1
ii  wpasupplicant2:2.10-9

Versions of packages network-manager suggests:
ii  iptables   1.8.7-1
pn  libteam-utils  

Versions of packages network-manager is related to:
pn  isc-dhcp-client  

-- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed [not included]

-- no debconf information

Bug#1010882: aseba: FTBFS because of non-constant SIGSTKSZ

[Georges Khaznadar]

Than you for the bug report and the patch, Alexandre.

I am uploading the new release shortly.

Best regards,   Georges.

Alexandre Ghiti a écrit :
> Package: aseba
> Version: 1.6.99+dfsg
> Severity: normal
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu kinetic ubuntu-patch
> 
> Dear Maintainer,
> 
> SIGSTKSZ is not constant anymore so altStackMem must be allocated
> dynamically: this patch implements what is done upstream.
> 
> In Ubuntu, the attached patch was applied to fix the FTBFS as can be
> seen in [1].
> 
> Not related but I updated the homepage link to directly point to aseba,
> it took me a few minutes to find it from the original link.
> 
> Thanks for considering the patch.
> 
> [1] 
> https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13492679/+listing-archive-extra
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers jammy-updates
>   APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.15.0-27-generic (SMP w/16 CPU threads)
> Kernel taint flags: TAINT_WARN
> 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

> diff -Nru aseba-1.6.99+dfsg/debian/control aseba-1.6.99+dfsg/debian/control
> --- aseba-1.6.99+dfsg/debian/control  2020-09-17 18:17:11.0 +0200
> +++ aseba-1.6.99+dfsg/debian/control  2022-05-03 16:24:08.0 +0200
> @@ -15,7 +15,7 @@
>  Standards-Version: 4.5.0
>  Vcs-Browser: https://salsa.debian.org/science-team/aseba.git
>  Vcs-Git: https://salsa.debian.org/science-team/aseba.git
> -Homepage: https://www.thymio.org/
> +Homepage: https://github.com/aseba-community/aseba
>  
>  Package: aseba
>  Architecture: any
> diff -Nru 
> aseba-1.6.99+dfsg/debian/patches/0001-third_party-catch2-Fix-non-constant-SIGSTKSZ.patch
>  
> aseba-1.6.99+dfsg/debian/patches/0001-third_party-catch2-Fix-non-constant-SIGSTKSZ.patch
> --- 
> aseba-1.6.99+dfsg/debian/patches/0001-third_party-catch2-Fix-non-constant-SIGSTKSZ.patch
>   1970-01-01 01:00:00.0 +0100
> +++ 
> aseba-1.6.99+dfsg/debian/patches/0001-third_party-catch2-Fix-non-constant-SIGSTKSZ.patch
>   2022-05-03 16:21:52.0 +0200
> @@ -0,0 +1,81 @@
> +From 830dbd151a5743629f3c6fb2827bb65bb6bca70d Mon Sep 17 00:00:00 2001
> +From: Alexandre Ghiti 
> +Date: Tue, 3 May 2022 15:15:12 +0200
> +Subject: [PATCH] third_party: catch2: Fix non-constant SIGSTKSZ
> +
> +SIGSTKSZ is not constant anymore so altStackMem must be allocated
> +dynamically: this patch implements what is done upstream.
> +
> +Signed-off-by: Alexandre Ghiti 
> +---
> + third_party/catch2/include/catch2/catch.hpp | 23 ++---
> + 1 file changed, 20 insertions(+), 3 deletions(-)
> +
> +diff --git a/third_party/catch2/include/catch2/catch.hpp 
> b/third_party/catch2/include/catch2/catch.hpp
> +index 081cb41..2de9330 100644
> +--- a/third_party/catch2/include/catch2/catch.hpp
>  b/third_party/catch2/include/catch2/catch.hpp
> +@@ -4731,7 +4731,8 @@ namespace Catch {
> + static bool isSet;
> + static struct sigaction oldSigActions[];
> + static stack_t oldSigStack;
> +-static char altStackMem[];
> ++static char* altStackMem;
> ++static std::size_t altStackSize;
> + 
> + static void handleSignal( int sig );
> + 
> +@@ -7226,6 +7227,11 @@ namespace {
> + void reportFatal( char const * const message ) {
> + 
> Catch::getCurrentContext().getResultCapture()->handleFatalErrorCondition( 
> message );
> + }
> ++
> ++//! Minimal size Catch2 needs for its own fatal error handling.
> ++//! Picked empirically, so it might not be sufficient on all
> ++//! platforms, and for all configurations.
> ++constexpr std::size_t minStackSizeForErrors = 32 * 1024;
> + }
> + 
> + #endif // signals/SEH handling
> +@@ -7318,10 +7324,16 @@ namespace Catch {
> + }
> + 
> + FatalConditionHandler::FatalConditionHandler() {
> ++assert(!altStackMem && "Cannot initialize POSIX signal handler when 
> one already exists");
> ++if (altStackSize == 0) {
> ++altStackSize = std::max(static_cast(SIGSTKSZ), 
> minStackSizeForErrors);
> ++}
> ++altStackMem = new char[altStackSize]();
> ++
> + isSet = true;
> + stack_t sigStack;
> + sigStack.ss_sp = altStackMem;
> +-sigStack.ss_size = SIGSTKSZ;
> ++sigStack.ss_size = altStackSize;
> + sigStack.ss_flags = 0;
> + sigaltstack(, );
> + struct sigaction sa = { };
> +@@ -7334,6 +7346,10 @@ namespace Catch {
> + }
> + 
> + FatalConditionHandler::~FatalConditionHandler() {
> ++delete[] altStackMem;
> ++// We signal that another instance can be constructed by 

Bug#1010128: Acknowledgement (linux-image-5.17.0-1-amd64: DKMS Module Rebuild for Broadcom Wireless Chip BCM4352 Fails to Build)

[Kurt Meyer]

Consider closing this bug report. The broadcom-sta-dkms 6.30.223.271-19 upgrade 
resolved the issue.

On Sun, Apr 24, 2022, at 19:03, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1010128: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010128.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  Debian Kernel Team 
>
> If you wish to submit further information on this problem, please
> send it to 1010...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> -- 
> 1010128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010128
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Bug#997293: pinfo: diff for NMU version 0.6.13-1.2

[Bas Zoetekouw]

That's excellent, thanks a lot!

Greeting,
Bas.

On 08-05-2022 14:40, gregor herrmann wrote:

Control: tags 997293 + patch
Control: tags 997293 + pending


Dear maintainer,

I've prepared an NMU for pinfo (versioned as 0.6.13-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

Bug#1010886: linux-image-5.17.0-1-amd64: Xorg crash

[Brilliantov Kirill Vladimirovich]

Package: src:linux
Version: 5.17.3-1
Severity: normal
X-Debbugs-Cc: kirill.brillian...@rt.ru

Dear Maintainer,

At noutbook Lenovo ThinkPad X1 Carbon Gen6 some times at boot I see linux crash

-- Package-specific info:
** Version:
Linux version 5.17.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.2.0-20) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT Debian 
5.17.3-1 (2022-04-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.17.0-1-amd64 
root=UUID=e82d3032-542f-47b4-ac08-ae6333505c0b ro quiet

** Tainted: DW (640)
 * kernel died recently, i.e. there was an OOPS or BUG
 * kernel issued warning

** Kernel log:
[   12.523063]  
[   12.523090] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE 
nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 
xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c bnep nfnetlink 
br_netfilter snd_ctl_led bridge btusb snd_soc_skl btrtl btbcm 
snd_hda_codec_realtek(+) btintel snd_soc_hdac_hda stp x86_pkg_temp_thermal 
intel_powerclamp coretemp llc kvm_intel snd_hda_codec_generic kvm btmtk 
irqbypass bluetooth ghash_clmulni_intel joydev iwlmvm sd_mod snd_hda_ext_core 
snd_soc_sst_ipc aesni_intel snd_soc_sst_dsp crypto_simd jitterentropy_rng 
mei_hdcp i915 overlay sg snd_soc_acpi_intel_match cryptd snd_soc_acpi mac80211 
intel_rapl_msr snd_soc_core snd_compress libarc4 uvcvideo sha512_ssse3 
snd_hda_intel rapl sha512_generic snd_intel_dspcfg videobuf2_vmalloc 
videobuf2_memops snd_intel_sdw_acpi intel_cstate videobuf2_v4l2 snd_hda_codec 
iwlwifi ttm intel_uncore ctr nls_ascii snd_hda_core iTCO_wdt videobuf2_common 
evdev nls_cp437 pcspkr intel_pmc_bxt
[   12.523230]  drm_kms_helper serio_raw efi_pstore drbg 
processor_thermal_device_pci_legacy snd_hwdep processor_thermal_device wmi_bmof 
intel_wmi_thunderbolt iTCO_vendor_support rmi_smbus cec ansi_cprng videodev 
snd_pcm mei_me vfat processor_thermal_rfim thinkpad_acpi ucsi_acpi cfg80211 fat 
rmi_core watchdog typec_ucsi rc_core processor_thermal_mbox nvram snd_timer 
processor_thermal_rapl ecdh_generic mc intel_rapl_common 
intel_xhci_usb_role_switch mei ecc i2c_algo_bit roles intel_soc_dts_iosf 
intel_pch_thermal platform_profile typec ledtrig_audio snd soundcore rfkill 
int3403_thermal int340x_thermal_zone ac intel_pmc_core int3400_thermal 
acpi_thermal_rel button acpi_pad drm fuse configfs efivarfs ip_tables x_tables 
autofs4 ext4 crc16 mbcache jbd2 crc32c_generic uas usb_storage scsi_mod 
scsi_common xhci_pci e1000e nvme xhci_hcd nvme_core t10_pi intel_lpss_pci 
crc_t10dif i2c_i801 ptp intel_lpss crct10dif_generic i2c_smbus thunderbolt 
psmouse usbcore crc32_pclmul crc32c_intel pps_core
[   12.524085]  crct10dif_pclmul crct10dif_common idma64 usb_common wmi battery 
video
[   12.524952] ---[ end trace  ]---
[   12.691698] RIP: 0010:__mutex_lock.constprop.0+0x151/0x470
[   12.691730] Code: 31 c9 31 d2 4c 89 f7 e8 9d 20 7a ff 84 c0 0f 84 e2 02 00 
00 f3 90 49 8b 06 48 89 c6 48 83 e6 f8 75 b0 48 89 d9 48 89 c2 eb ba <8b> 50 34 
85 d2 0f 85 ce 02 00 00 65 48 8b 04 25 c0 fb 01 00 48 8b
[   12.691780] RSP: 0018:a55101b67c90 EFLAGS: 00010202
[   12.691794] RAX: 000301010b40 RBX: 000e001f RCX: 9671b85a8000
[   12.691810] RDX:  RSI: 000301010b40 RDI: b8d50a50
[   12.691825] RBP: a55101b67cf8 R08: 967190f9a168 R09: 9671817aad00
[   12.691841] R10: a55101b67d20 R11: 967190f34910 R12: 967190d92010
[   12.691856] R13: 9671d932e3e0 R14: 967190d92010 R15: 9671b85a8ca0
[   12.691871] FS:  () GS:96751270() 
knlGS:
[   12.691889] CS:  0010 DS:  ES:  CR0: 80050033
[   12.691902] CR2: 557af81b11c0 CR3: 000128a5a003 CR4: 003706e0
[   12.691918] note: Xorg:sh4[707] exited with preempt_count 1
[   12.693011] Fixing recursive fault but reboot is needed!
[   12.694137] BUG: using smp_processor_id() in preemptible [] code: 
Xorg:sh4/707
[   12.695246] caller is __schedule+0x32/0x9e0
[   12.696333] CPU: 4 PID: 707 Comm: Xorg:sh4 Tainted: G  D   
5.17.0-1-amd64 #1  Debian 5.17.3-1
[   12.697663] Hardware name: LENOVO 20KH006JRT/20KH006JRT, BIOS N23ET50W (1.25 
) 06/25/2018
[   12.698735] Call Trace:
[   12.699787]  
[   12.701363]  dump_stack_lvl+0x48/0x5e
[   12.703062]  check_preemption_disabled+0xde/0xe0
[   12.704218]  __schedule+0x32/0x9e0
[   12.705370]  ? _printk+0x58/0x6f
[   12.706516]  do_task_dead+0x3f/0x50
[   12.707679]  make_task_dead.cold+0x51/0xab
[   12.708946]  rewind_stack_and_make_dead+0x17/0x17
[   12.710149] RIP: 0033:0x7f10e6c900fa
[   12.711343] Code: Unable to access opcode bytes at RIP 0x7f10e6c900d0.
[   12.712493] RSP: 002b:7f10d27fb8b0 EFLAGS: 0246 ORIG_RAX: 
00ca
[   12.713644] RAX: fe00 RBX:  RCX: 7f10e6c900fa
[   12.714798] RDX:  RSI: 0189 RDI: 558be6bad4a8
[   12.715952] 

Bug#826044: Hangs in apt hook with a zombie - problem still exists in debian10

[zm5s-trnc]

On Wed, 11 May 2022 22:59:41 +0200 Thomas Liske  
wrote:

> Hi,
>
> you are using some ansible deployment? Could you share your ansible
> role?
>
> This is a long-standing bug and it feels like that affected users are
> using aptitude. I wonder if this is related - could you give it a try
> (force_apt_get task parameter)?

Yes, using Ansible.

There's nothing special in it.

- name: Debian | Ensure Debian upgraded
  apt:
    update_cache: yes
    upgrade: "yes"
  tags:
    - os_force_upgrade

Bug#1006981: fixed in rails 2:6.1.4.6+dfsg-2

[Paul Gevers]

Control: reopen -1
Control: found -1 2:6.1.4.6+dfsg-2

On Sat, 30 Apr 2022 13:20:23 + Debian FTP Masters 
 wrote:

 rails (2:6.1.4.6+dfsg-2) unstable; urgency=medium
 .
   * Skip flaky tests (Closes: #1006981)


Looks like there are more flaky tests:

https://ci.debian.net/data/autopkgtest/testing/armhf/r/rails/21412101/log.gz

/usr/bin/ruby3.0 -w -I"lib" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/cache/stores/redis_cache_store_test.rb" --seed=0

Run options: --seed=0

# Running:

S.F

Failure:
ActiveSupport::Cache::RedisCacheStoreTests::RedisCacheStoreCommonBehaviorTest#test_delete 
[/tmp/autopkgtest-lxc.ccf2mxu8/downtmp/build.j4S/src/activesupport/test/cache/behaviors/cache_store_behavior.rb:371]:

Expected false to be truthy.

rails test 
tmp/autopkgtest-lxc.ccf2mxu8/downtmp/build.j4S/src/activesupport/test/cache/behaviors/cache_store_behavior.rb:369


...

Finished in 3.461934s, 46.7947 runs/s, 95.0336 assertions/s.
162 runs, 329 assertions, 1 failures, 0 errors, 1 skips

You have skipped tests. Run with --verbose for details.
rake aborted!
Command failed with status (1): [ruby -w -I"lib" 
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/rake_test_loader.rb 
"test/cache/stores/redis_cache_store_test.rb" --seed=0]
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/testtask.rb:130:in 
`block (3 levels) in define'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/file_utils.rb:57:in 
`sh'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/file_utils.rb:104:in 
`ruby'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/testtask.rb:117:in 
`block (2 levels) in define'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/file_utils_ext.rb:58:in 
`verbose'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/testtask.rb:111:in 
`block in define'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`block in execute'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`each'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`execute'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:219:in 
`block in invoke_with_call_chain'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:199:in 
`synchronize'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:199:in 
`invoke_with_call_chain'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:188:in 
`invoke'
/tmp/autopkgtest-lxc.ccf2mxu8/downtmp/build.j4S/src/activesupport/Rakefile:17:in 
`block in '
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`block in execute'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`each'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:281:in 
`execute'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:219:in 
`block in invoke_with_call_chain'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:199:in 
`synchronize'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:199:in 
`invoke_with_call_chain'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/task.rb:188:in 
`invoke'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:160:in 
`invoke_task'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:116:in 
`block (2 levels) in top_level'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:116:in 
`each'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:116:in 
`block in top_level'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:125:in 
`run_with_threads'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:110:in 
`top_level'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:83:in 
`block in run'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:186:in 
`standard_exception_handling'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/lib/rake/application.rb:80:in 
`run'
/usr/share/rubygems-integration/all/gems/rake-13.0.6/exe/rake:27:in 
`'

/usr/bin/rake:25:in `load'
/usr/bin/rake:25:in `'
Tasks: TOP => test:cache_stores:redis:ruby
cd -
Failed tests: activesupport:test
mv ./.gem2deb.Gemfile.lock Gemfile.lock



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1010884: dkms breaks nvidia-graphics-drivers-tesla-470 autopkgtest on arm64 and ppc64el: unmet dependencies

[Paul Gevers]

Source: dkms, nvidia-graphics-drivers-tesla-470
Control: found -1 dkms/3.0.3-1
Control: found -1 nvidia-graphics-drivers-tesla-470/470.103.01-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of dkms the autopkgtest of 
nvidia-graphics-drivers-tesla-470 fails in testing when that autopkgtest 
is run with the binary packages of dkms from unstable. It passes when 
run with only packages from testing. In tabular form:


   passfail
dkms   from testing3.0.3-1
nvidia-graphics-drivers-tesla-470  from testing470.103.01-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of dkms to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


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

Paul

[1] https://qa.debian.org/excuses.php?package=dkms

https://ci.debian.net/data/autopkgtest/testing/arm64/n/nvidia-graphics-drivers-tesla-470/21589790/log.gz

I: Removing binary package nvidia-tesla-470-kernel-dkms, to get clean state
I: Installing binary package nvidia-tesla-470-kernel-dkms
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  glx-alternative-mesa glx-alternative-nvidia glx-diversions
  nvidia-installer-cleanup nvidia-kernel-common nvidia-modprobe
  nvidia-tesla-470-alternative nvidia-tesla-470-kernel-support update-glx
Suggested packages:
  libgl1-mesa-glx | libgl1 nvidia-driver | nvidia-driver-any
Recommended packages:
  nvidia-tesla-470-driver | libnvidia-tesla-470-cuda1
The following NEW packages will be installed:
  glx-alternative-mesa glx-alternative-nvidia glx-diversions
  nvidia-installer-cleanup nvidia-kernel-common nvidia-modprobe
  nvidia-tesla-470-alternative nvidia-tesla-470-kernel-dkms
  nvidia-tesla-470-kernel-support update-glx
0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
Need to get 25.9 MB of archives.
After this operation, 50.2 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian testing/contrib arm64 update-glx 
arm64 1.2.1 [10.6 kB]
Get:2 http://deb.debian.org/debian testing/contrib arm64 
glx-alternative-mesa arm64 1.2.1 [9912 B]
Get:3 http://deb.debian.org/debian testing/contrib arm64 
nvidia-installer-cleanup arm64 20220217+1 [19.4 kB]
Get:4 http://deb.debian.org/debian testing/contrib arm64 glx-diversions 
arm64 1.2.1 [12.6 kB]
Get:5 http://deb.debian.org/debian testing/contrib arm64 
glx-alternative-nvidia arm64 1.2.1 [10.9 kB]
Get:6 http://deb.debian.org/debian testing/non-free arm64 
nvidia-tesla-470-alternative arm64 470.103.01-2 [242 kB]
Get:7 http://deb.debian.org/debian testing/contrib arm64 
nvidia-kernel-common arm64 20220217+1 [10.9 kB]
Get:8 http://deb.debian.org/debian testing/contrib arm64 nvidia-modprobe 
arm64 510.68.02-1 [20.5 kB]
Get:9 http://deb.debian.org/debian testing/non-free arm64 
nvidia-tesla-470-kernel-support arm64 470.103.01-2 [241 kB]
Get:10 http://deb.debian.org/debian testing/non-free arm64 
nvidia-tesla-470-kernel-dkms arm64 470.103.01-2 [25.3 MB]

debconf: delaying package configuration, since apt-utils is not installed
Fetched 25.9 MB in 5s (5151 kB/s)
Selecting previously unselected package update-glx.
(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 ... 29721 files and directories currently installed.)
Preparing to unpack .../update-glx_1.2.1_arm64.deb ...
Unpacking update-glx (1.2.1) ...
Selecting previously unselected package glx-alternative-mesa.
Preparing to unpack .../glx-alternative-mesa_1.2.1_arm64.deb ...
Unpacking glx-alternative-mesa (1.2.1) ...
Selecting previously unselected package nvidia-installer-cleanup.
Preparing to unpack .../nvidia-installer-cleanup_20220217+1_arm64.deb ...
Unpacking nvidia-installer-cleanup (20220217+1) ...
Setting up nvidia-installer-cleanup (20220217+1) ...
Selecting previously unselected package glx-diversions.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%

Bug#1010885: dkms breaks nvidia-graphics-drivers-tesla-510 autopkgtest on arm64 and ppc64el: unmet dependencies

[Paul Gevers]

Source: dkms, nvidia-graphics-drivers-tesla-510
Control: found -1 dkms/3.0.3-1
Control: found -1 nvidia-graphics-drivers-tesla-510/510.47.03-2
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of dkms the autopkgtest of 
nvidia-graphics-drivers-tesla-510 fails in testing when that autopkgtest 
is run with the binary packages of dkms from unstable. It passes when 
run with only packages from testing. In tabular form:


  passfail
dkms  from testing3.0.3-1
nvidia-graphics-drivers-tesla-510 from testing510.47.03-2
all othersfrom testingfrom testing

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

Currently this regression is blocking the migration of dkms to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


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

Paul

[1] https://qa.debian.org/excuses.php?package=dkms

https://ci.debian.net/data/autopkgtest/testing/arm64/n/nvidia-graphics-drivers-tesla-510/21592376/log.gz

I: Removing binary package nvidia-tesla-510-kernel-dkms, to get clean state
I: Installing binary package nvidia-tesla-510-kernel-dkms
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  glx-alternative-mesa glx-alternative-nvidia glx-diversions
  nvidia-installer-cleanup nvidia-kernel-common nvidia-modprobe
  nvidia-tesla-510-alternative nvidia-tesla-510-kernel-support update-glx
Suggested packages:
  libgl1-mesa-glx | libgl1 nvidia-driver | nvidia-driver-any
Recommended packages:
  nvidia-tesla-510-driver | libnvidia-tesla-510-cuda1
The following NEW packages will be installed:
  glx-alternative-mesa glx-alternative-nvidia glx-diversions
  nvidia-installer-cleanup nvidia-kernel-common nvidia-modprobe
  nvidia-tesla-510-alternative nvidia-tesla-510-kernel-dkms
  nvidia-tesla-510-kernel-support update-glx
0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
Need to get 50.4 MB of archives.
After this operation, 95.1 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian testing/contrib arm64 update-glx 
arm64 1.2.1 [10.6 kB]
Get:2 http://deb.debian.org/debian testing/contrib arm64 
glx-alternative-mesa arm64 1.2.1 [9912 B]
Get:3 http://deb.debian.org/debian testing/contrib arm64 
nvidia-installer-cleanup arm64 20220217+1 [19.4 kB]
Get:4 http://deb.debian.org/debian testing/contrib arm64 glx-diversions 
arm64 1.2.1 [12.6 kB]
Get:5 http://deb.debian.org/debian testing/contrib arm64 
glx-alternative-nvidia arm64 1.2.1 [10.9 kB]
Get:6 http://deb.debian.org/debian testing/non-free arm64 
nvidia-tesla-510-alternative arm64 510.47.03-2 [246 kB]
Get:7 http://deb.debian.org/debian testing/contrib arm64 
nvidia-kernel-common arm64 20220217+1 [10.9 kB]
Get:8 http://deb.debian.org/debian testing/contrib arm64 nvidia-modprobe 
arm64 510.68.02-1 [20.5 kB]
Get:9 http://deb.debian.org/debian testing/non-free arm64 
nvidia-tesla-510-kernel-support arm64 510.47.03-2 [20.7 MB]
Get:10 http://deb.debian.org/debian testing/non-free arm64 
nvidia-tesla-510-kernel-dkms arm64 510.47.03-2 [29.4 MB]

debconf: delaying package configuration, since apt-utils is not installed
Fetched 50.4 MB in 5s (10.2 MB/s)
Selecting previously unselected package update-glx.
(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 ... 29721 files and directories currently installed.)
Preparing to unpack .../update-glx_1.2.1_arm64.deb ...
Unpacking update-glx (1.2.1) ...
Selecting previously unselected package glx-alternative-mesa.
Preparing to unpack .../glx-alternative-mesa_1.2.1_arm64.deb ...
Unpacking glx-alternative-mesa (1.2.1) ...
Selecting previously unselected package nvidia-installer-cleanup.
Preparing to unpack .../nvidia-installer-cleanup_20220217+1_arm64.deb ...
Unpacking nvidia-installer-cleanup (20220217+1) ...
Setting up nvidia-installer-cleanup (20220217+1) ...
Selecting previously unselected package glx-diversions.
(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading 

Bug#1010791: (no subject)

[Breno Leitao]

Thanks for packaging this tool Michel. I gave it a try and this tool is
quite useful.

I've looked at the packaging and script, and they are sane. I will be
sponsoring this package.

Bug#1010883: dkms breaks nvidia-graphics-drivers autopkgtest on arm64: unmet dependencies

[Paul Gevers]

Source: dkms, nvidia-graphics-drivers
Control: found -1 dkms/3.0.3-1
Control: found -1 nvidia-graphics-drivers/470.103.01-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of dkms the autopkgtest of nvidia-graphics-drivers 
fails in testing when that autopkgtest is run with the binary packages 
of dkms from unstable. It passes when run with only packages from 
testing. In tabular form:


passfail
dkmsfrom testing3.0.3-1
nvidia-graphics-drivers from testing470.103.01-3
all others  from testingfrom testing

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

Currently this regression is blocking the migration of dkms to testing 
[1]. Due to the nature of this issue, I filed this bug report against 
both packages. Can you please investigate the situation and reassign the 
bug to the right package?


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

Paul

[1] https://qa.debian.org/excuses.php?package=dkms

https://ci.debian.net/data/autopkgtest/testing/arm64/n/nvidia-graphics-drivers/21589789/log.gz

I: Removing binary package nvidia-kernel-dkms, to get clean state
I: Installing binary package nvidia-kernel-dkms
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  glx-alternative-mesa glx-alternative-nvidia glx-diversions
  nvidia-alternative nvidia-installer-cleanup nvidia-kernel-common
  nvidia-kernel-support nvidia-modprobe update-glx
Suggested packages:
  libgl1-mesa-glx | libgl1 nvidia-driver | nvidia-driver-any
Recommended packages:
  nvidia-driver | libcuda1
The following NEW packages will be installed:
  glx-alternative-mesa glx-alternative-nvidia glx-diversions
  nvidia-alternative nvidia-installer-cleanup nvidia-kernel-common
  nvidia-kernel-dkms nvidia-kernel-support nvidia-modprobe update-glx
0 upgraded, 10 newly installed, 0 to remove and 0 not upgraded.
Need to get 25.9 MB of archives.
After this operation, 50.2 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian testing/contrib arm64 update-glx 
arm64 1.2.1 [10.6 kB]
Get:2 http://deb.debian.org/debian testing/contrib arm64 
glx-alternative-mesa arm64 1.2.1 [9912 B]
Get:3 http://deb.debian.org/debian testing/contrib arm64 
nvidia-installer-cleanup arm64 20220217+1 [19.4 kB]
Get:4 http://deb.debian.org/debian testing/contrib arm64 glx-diversions 
arm64 1.2.1 [12.6 kB]
Get:5 http://deb.debian.org/debian testing/contrib arm64 
glx-alternative-nvidia arm64 1.2.1 [10.9 kB]
Get:6 http://deb.debian.org/debian testing/non-free arm64 
nvidia-alternative arm64 470.103.01-3 [240 kB]
Get:7 http://deb.debian.org/debian testing/contrib arm64 
nvidia-kernel-common arm64 20220217+1 [10.9 kB]
Get:8 http://deb.debian.org/debian testing/contrib arm64 nvidia-modprobe 
arm64 510.68.02-1 [20.5 kB]
Get:9 http://deb.debian.org/debian testing/non-free arm64 
nvidia-kernel-support arm64 470.103.01-3 [239 kB]
Get:10 http://deb.debian.org/debian testing/non-free arm64 
nvidia-kernel-dkms arm64 470.103.01-3 [25.3 MB]

debconf: delaying package configuration, since apt-utils is not installed
Fetched 25.9 MB in 2s (16.5 MB/s)
Selecting previously unselected package update-glx.
(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 ... 29721 files and directories currently installed.)
Preparing to unpack .../update-glx_1.2.1_arm64.deb ...
Unpacking update-glx (1.2.1) ...
Selecting previously unselected package glx-alternative-mesa.
Preparing to unpack .../glx-alternative-mesa_1.2.1_arm64.deb ...
Unpacking glx-alternative-mesa (1.2.1) ...
Selecting previously unselected package nvidia-installer-cleanup.
Preparing to unpack .../nvidia-installer-cleanup_20220217+1_arm64.deb ...
Unpacking nvidia-installer-cleanup (20220217+1) ...
Setting up nvidia-installer-cleanup (20220217+1) ...
Selecting previously unselected package glx-diversions.
(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 

Bug#933396: Why this bug report can be closed (again?)

[Georges Khaznadar]

@garbage_collec...@nym.hush.com:
Thanks to Christian Kastner, here is a clue for the buggy behavior you
noticed:

The manual page of crontab (5) states that
--8<
   The entire command portion of the line, up to a newline or a "%"
   character, will be executed by /bin/sh or by the shell specified in
   the SHELL variable of the cronfile.  A "%" character in the command,
   unless escaped with a backslash (\), will be changed into newline
   characters, and  all data after the first % will be sent to the
   command as standard input.
--8<

So the line
@reboot root echo Logged time = %time% %date% >> /home/marc/log.txt
is most probably not interpreted as you thought.

Best regards,   Georges.

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



signature.asc
Description: PGP signature

Bug#1010882: aseba: FTBFS because of non-constant SIGSTKSZ

[Alexandre Ghiti]

Package: aseba
Version: 1.6.99+dfsg
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Dear Maintainer,

SIGSTKSZ is not constant anymore so altStackMem must be allocated
dynamically: this patch implements what is done upstream.

In Ubuntu, the attached patch was applied to fix the FTBFS as can be
seen in [1].

Not related but I updated the homepage link to directly point to aseba,
it took me a few minutes to find it from the original link.

Thanks for considering the patch.

[1] 
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13492679/+listing-archive-extra

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

Kernel: Linux 5.15.0-27-generic (SMP w/16 CPU threads)
Kernel taint flags: TAINT_WARN
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
diff -Nru aseba-1.6.99+dfsg/debian/control aseba-1.6.99+dfsg/debian/control
--- aseba-1.6.99+dfsg/debian/control2020-09-17 18:17:11.0 +0200
+++ aseba-1.6.99+dfsg/debian/control2022-05-03 16:24:08.0 +0200
@@ -15,7 +15,7 @@
 Standards-Version: 4.5.0
 Vcs-Browser: https://salsa.debian.org/science-team/aseba.git
 Vcs-Git: https://salsa.debian.org/science-team/aseba.git
-Homepage: https://www.thymio.org/
+Homepage: https://github.com/aseba-community/aseba
 
 Package: aseba
 Architecture: any
diff -Nru 
aseba-1.6.99+dfsg/debian/patches/0001-third_party-catch2-Fix-non-constant-SIGSTKSZ.patch
 
aseba-1.6.99+dfsg/debian/patches/0001-third_party-catch2-Fix-non-constant-SIGSTKSZ.patch
--- 
aseba-1.6.99+dfsg/debian/patches/0001-third_party-catch2-Fix-non-constant-SIGSTKSZ.patch
1970-01-01 01:00:00.0 +0100
+++ 
aseba-1.6.99+dfsg/debian/patches/0001-third_party-catch2-Fix-non-constant-SIGSTKSZ.patch
2022-05-03 16:21:52.0 +0200
@@ -0,0 +1,81 @@
+From 830dbd151a5743629f3c6fb2827bb65bb6bca70d Mon Sep 17 00:00:00 2001
+From: Alexandre Ghiti 
+Date: Tue, 3 May 2022 15:15:12 +0200
+Subject: [PATCH] third_party: catch2: Fix non-constant SIGSTKSZ
+
+SIGSTKSZ is not constant anymore so altStackMem must be allocated
+dynamically: this patch implements what is done upstream.
+
+Signed-off-by: Alexandre Ghiti 
+---
+ third_party/catch2/include/catch2/catch.hpp | 23 ++---
+ 1 file changed, 20 insertions(+), 3 deletions(-)
+
+diff --git a/third_party/catch2/include/catch2/catch.hpp 
b/third_party/catch2/include/catch2/catch.hpp
+index 081cb41..2de9330 100644
+--- a/third_party/catch2/include/catch2/catch.hpp
 b/third_party/catch2/include/catch2/catch.hpp
+@@ -4731,7 +4731,8 @@ namespace Catch {
+ static bool isSet;
+ static struct sigaction oldSigActions[];
+ static stack_t oldSigStack;
+-static char altStackMem[];
++static char* altStackMem;
++static std::size_t altStackSize;
+ 
+ static void handleSignal( int sig );
+ 
+@@ -7226,6 +7227,11 @@ namespace {
+ void reportFatal( char const * const message ) {
+ 
Catch::getCurrentContext().getResultCapture()->handleFatalErrorCondition( 
message );
+ }
++
++//! Minimal size Catch2 needs for its own fatal error handling.
++//! Picked empirically, so it might not be sufficient on all
++//! platforms, and for all configurations.
++constexpr std::size_t minStackSizeForErrors = 32 * 1024;
+ }
+ 
+ #endif // signals/SEH handling
+@@ -7318,10 +7324,16 @@ namespace Catch {
+ }
+ 
+ FatalConditionHandler::FatalConditionHandler() {
++assert(!altStackMem && "Cannot initialize POSIX signal handler when 
one already exists");
++if (altStackSize == 0) {
++altStackSize = std::max(static_cast(SIGSTKSZ), 
minStackSizeForErrors);
++}
++altStackMem = new char[altStackSize]();
++
+ isSet = true;
+ stack_t sigStack;
+ sigStack.ss_sp = altStackMem;
+-sigStack.ss_size = SIGSTKSZ;
++sigStack.ss_size = altStackSize;
+ sigStack.ss_flags = 0;
+ sigaltstack(, );
+ struct sigaction sa = { };
+@@ -7334,6 +7346,10 @@ namespace Catch {
+ }
+ 
+ FatalConditionHandler::~FatalConditionHandler() {
++delete[] altStackMem;
++// We signal that another instance can be constructed by zeroing
++// out the pointer.
++altStackMem = nullptr;
+ reset();
+ }
+ 
+@@ -7352,7 +7368,8 @@ namespace Catch {
+ bool FatalConditionHandler::isSet = false;
+ struct sigaction 
FatalConditionHandler::oldSigActions[sizeof(signalDefs)/sizeof(SignalDefs)] = 
{};
+ stack_t FatalConditionHandler::oldSigStack = {};
+-char FatalConditionHandler::altStackMem[SIGSTKSZ] = {};

Bug#1010881: libcloud: Autopkgtest failure when no network or https_proxy/http_proxy set

[Olivier Gayot]

Package: libcloud
Version: 3.4.1-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch

Dear Maintainer,

Since the move to 3.4.1, libcloud fails autopkgtest when either:
 * Internet access is not available
 * http_proxy or https_proxy is set

In Ubuntu, the attached patch was applied to achieve the following:

  * Disable test that requires access to the Internet.
  * Applied patches forwarded upstream to fix failures when HTTP proxy
variables are set (LP: #1972888)


Thanks for considering the patch.


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

Kernel: Linux 5.15.0-27-generic (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru 
libcloud-3.4.1/debian/patches/43b71091ebd159570302b695f0a244f4d0a7e497.patch 
libcloud-3.4.1/debian/patches/43b71091ebd159570302b695f0a244f4d0a7e497.patch
--- 
libcloud-3.4.1/debian/patches/43b71091ebd159570302b695f0a244f4d0a7e497.patch
1970-01-01 01:00:00.0 +0100
+++ 
libcloud-3.4.1/debian/patches/43b71091ebd159570302b695f0a244f4d0a7e497.patch
2022-05-11 15:51:43.0 +0200
@@ -0,0 +1,49 @@
+Description: stop HTTP server (thread) properly
+ test/test_http.py: stop HTTP server (thread) properly
+
+ The HttpLayerTestCase test class creates a HTTPServer instance and runs
+ it in a separate thread.
+
+ After running all the test-cases, we attempt to close the server and the
+ thread by killing the thread. Unfortunately, the code that does that is
+ unreachable because the tear-down member function is called tearDownCls
+ intead of tearDownClass.
+
+ Moreover, there is no threading.Thread.kill function. This was undetected
+ because the code was unreachable.
+
+ The proper way to clean things up is to:
+
+ 1. Stop the HTTP server using HTTPServer.shutdown()
+ 2. Release the resources using HTTPServer.server_close()
+ 3. Join the thread using threading.Thread.join()
+
+ The original patch from upstream was missing the call to
+ HTTPServer.server_close(), which was added later.
+
+ This patch is not strictly necessary to fix the tests but subsequent patches
+ depend on tearDownClass being spelled properly.
+Author: Olivier Gayot 
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libcloud/+bug/1972888
+Forwarded: https://github.com/apache/libcloud/pull/1690
+Applied-Upstream: 
https://github.com/apache/libcloud/pull/1690/commits/43b71091ebd159570302b695f0a244f4d0a7e497
+Last-Update: 2022-05-11
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: b/libcloud/test/test_http.py
+===
+--- a/libcloud/test/test_http.py   2022-05-11 17:11:36.733859740 +0200
 b/libcloud/test/test_http.py   2022-05-11 17:11:36.729859732 +0200
+@@ -116,8 +116,10 @@
+ cls.mock_server_thread.start()
+ 
+ @classmethod
+-def tearDownCls(cls):
+-cls.mock_server_thread.kill()
++def tearDownClass(cls):
++cls.mock_server.shutdown()
++cls.mock_server.server_close()
++cls.mock_server_thread.join()
+ 
+ def test_prepared_request_empty_body_chunked_encoding_not_used(self):
+ connection = LibcloudConnection(host=self.listen_host, 
port=self.listen_port)
diff -Nru 
libcloud-3.4.1/debian/patches/83bd562337abdda4b1ba6706999b13aa358bdd28.patch 
libcloud-3.4.1/debian/patches/83bd562337abdda4b1ba6706999b13aa358bdd28.patch
--- 
libcloud-3.4.1/debian/patches/83bd562337abdda4b1ba6706999b13aa358bdd28.patch
1970-01-01 01:00:00.0 +0100
+++ 
libcloud-3.4.1/debian/patches/83bd562337abdda4b1ba6706999b13aa358bdd28.patch
2022-05-11 15:51:43.0 +0200
@@ -0,0 +1,46 @@
+Description: test/test_http.py: also backup/restore HTTP proxy settings
+
+ The HttpLayerTestCase class relies on the LibcloudConnection class -
+ which honors https_proxy and http_proxy variables.
+
+ Since the tests expect connections to the loopback interface (e.g.,
+ 127.0.0.1), we need to clear the http_proxy and https_proxy
+ variables before running the tests. Later on, we need to restore the
+ variables just like we did in test/test_connection.py
+Author: Olivier Gayot 
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libcloud/+bug/1972888
+Forwarded: https://github.com/apache/libcloud/pull/1692
+Applied-Upstream: 
https://github.com/apache/libcloud/commit/83bd562337abdda4b1ba6706999b13aa358bdd28
+Last-Update: 2022-05-11
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: b/libcloud/test/test_http.py

Bug#997512: zzuf: Fix FTBFS by disabling win32 test

[Alexandre Ghiti]

Package: zzuf
Version: 0.15-1
Followup-For: Bug #997512
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to fix the FTBFS discussed
here: it simply consists in disabling the win32 test.

Thanks for considering the patch.


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

Kernel: Linux 5.15.0-27-generic (SMP w/16 CPU threads)
Kernel taint flags: TAINT_WARN
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
diff -Nru 
zzuf-0.15/debian/patches/0001-test-Do-not-check-win32-as-it-fails.patch 
zzuf-0.15/debian/patches/0001-test-Do-not-check-win32-as-it-fails.patch
--- zzuf-0.15/debian/patches/0001-test-Do-not-check-win32-as-it-fails.patch 
1970-01-01 01:00:00.0 +0100
+++ zzuf-0.15/debian/patches/0001-test-Do-not-check-win32-as-it-fails.patch 
2022-05-03 14:12:06.0 +0200
@@ -0,0 +1,24 @@
+From 173742831d1ba9a0dfe815757d05c19b5c92da58 Mon Sep 17 00:00:00 2001
+From: Alexandre Ghiti 
+Date: Tue, 3 May 2022 14:11:57 +0200
+Subject: [PATCH] test: Do not check win32 as it fails
+
+---
+ test/Makefile.am | 1 -
+ 1 file changed, 1 deletion(-)
+
+diff --git a/test/Makefile.am b/test/Makefile.am
+index 7a3719c..db24f39 100644
+--- a/test/Makefile.am
 b/test/Makefile.am
+@@ -18,7 +18,6 @@ TESTS = check-zzuf-A-autoinc \
+ check-zzuf-M-max-memory \
+ check-zzuf-r-ratio \
+ check-source \
+-check-win32 \
+ check-overflow \
+ check-div0 \
+ check-utils \
+-- 
+2.34.1
+
diff -Nru zzuf-0.15/debian/patches/series zzuf-0.15/debian/patches/series
--- zzuf-0.15/debian/patches/series 2015-06-28 13:45:01.0 +0200
+++ zzuf-0.15/debian/patches/series 2022-05-03 14:12:24.0 +0200
@@ -0,0 +1 @@
+0001-test-Do-not-check-win32-as-it-fails.patch

Bug#1010879: reportbug: mmh is not co-installable with nmh

[William Hay]

Package: mmh
Version: mmh-0.4.4
Severity: wishlist

Dear Maintainer,
I want to use a more modern version of MH but retain the refile command
from nmh because I use the rmmproc functionality.
Attempting to install mmh with apt install mmh says it will remove nmh.
I was hoping the two would be co-installable.  I assume this conflict
occurs because both install executables with the same name in
/usr/bin/mh.  mailutils-mh avoids this conflict by installing
executables in /usr/bin/mu-mh.  Ideally both nmh and mmh would move
to different directories and manage /usr/bin/mh via /etc/alternatives or
similar but if not nmh was there first.

Thanks,
William

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

Kernel: Linux 5.16.0-0.bpo.4-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 mmh depends on:
ii  file   1:5.39-3
ii  libc6  2.31-13+deb11u3
ii  libtinfo6  6.2+20201114-2

mmh recommends no packages.

mmh suggests no packages.

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

[Paul Gevers]

Hi Athos, Rafael,

On 12-05-2022 06:16, Launchpad Bug Tracker wrote:

This bug was fixed in the package cacti - 1.2.20+ds1-2ubuntu1

---
cacti (1.2.20+ds1-2ubuntu1) kinetic; urgency=medium

   * Merge with Debian unstable (LP: #1972833). Remaining changes:
 - General installing instructions update for NO_AUTO_CREATE_USER.
 - Use new dbconfig "dbc_authplugin" variable to mitigate MySQL 8 issues.

  -- Athos Ribeiro   Tue, 10 May 2022
10:03:33 -0300

** Changed in: cacti (Ubuntu)
Status: In Progress => Fix Released


As Debian has MySQL 8+ for some time now, wouldn't it make sense to 
merge this back into Debian now. Are these changes compatible with 
MariaDB, and if not, what would it take to make them compatible?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006920: please split out a libtbbmalloc2 package, both in tbb and onetbb

[Andrius Merkys]

Hello,

Can we proceed with splitting out libtbbmalloc2 if there are no
blockers? tbb/onetbb transition is blocking quite some packages, it
would be nice to deal with all of them until the freeze.

Best,
Andrius

Bug#1010878: installation-reports: preseeding passwords doesn't work on mips64el under qemu

[Johannes Schauer Marin Rodrigues]

Package: installation-reports
Severity: normal
X-Debbugs-Cc: jo...@debian.org

Hi,

steps to reproduce:

qemu-img create -f qcow2 disk.qcow 4G
curl 
https://deb.debian.org/debian/dists/bullseye/main/installer-mips64el/current/images/malta/netboot/initrd.gz
 > initrd.gz
curl 
https://deb.debian.org/debian/dists/bullseye/main/installer-mips64el/current/images/malta/netboot/vmlinuz-5.10.0-13-5kc-malta
 > linux
/usr/bin/time -v qemu-system-mips64el -M malta -cpu 5KEc -nographic -no-reboot 
-m 1G -initrd initrd.gz -kernel linux -append 'auto-install/enable=true 
debconf/priority=critical 
preseed/url=http://www.debian.org/releases/stable/example-preseed.txt 
netcfg/get_hostname=hostname netcfg/get_domain=domain 
passwd/root-password=r00tme passwd/root-password-again=r00tme 
passwd/user-fullname=user passwd/username=user passwd/user-password=insecure 
passwd/user-password-again=insecure pkgsel/run_tasksel=false 
popularity-contest:popularity-contest/participate=false 
grub-installer/bootdev=/dev/sda --- console=ttyS0' -hda disk.qcow

This stops at the following screen:

[(1*installer)  2 shell  3 shell  4- log   ][ May 12  6:27 ]



 ┌┤ [!!] Set up users and passwords ├─┐ 
 ││ 
 │ Please enter the same root password again to verify that you have  │ 
 │ typed it correctly.│ 
 ││ 
 │ Re-enter password to verify:   │ 
 ││ 
 │ __ │ 
 ││ 
 │ [ ] Show Password in Clear │ 
 ││ 
 │ │ 
 ││ 
 └┘ 





 moves;  selects;  activates buttons 


So for some reason passwd/root-password-again is ignored. Above recipe
works fine for other architectures and for some reason stops with above
prompt on mips64el. Why?

Thanks!

cheers, josch

Bug#1010862: src:pysph: fails to migrate to testing for too long: new build dependency not available on ppc64el and s390x

[Antonio Valentino]

Dear Paul,

On Wed, 11 May 2022 21:26:52 +0200 Paul Gevers  wrote:

Source: pysph
Version: 1.0~b0~20191115.gite3d5e10-6
Severity: serious
Control: close -1 1.0~b1-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:pysph has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. I think the situation is as 
follows. Your package needed a new build dependency. That B-D isn't 
available on all architectures, including some where your package 
successfully built in the past. You'll have to request the FTP-master to 
remove the binaries from those architectures. I recommend using 
reportbug to file the right bug report against the ftp.debian.org pseudo 
package.


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


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


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


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


Paul

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


I see that this issue has been closed already.
Not sure anyway to understand what happened.
Should I still file a bug report against ftp.debian.org asking for the 
removal of the binary packages from unsupported architectures?


kind regards
--
Antonio Valentino

Bug#1010877: nfoview: cannot run with some custom fonts

[Nicolas JEANNE]

Package: nfoview
Version: 1.28.1-1
Severity: important

Dear Maintainer,

nfoview failed to launch after I configured it to use a custom font (i.e.
Terminus (TTF) Bold 12).

I found a simple workaround, though: putting the font's name between double-
quotes in my '~/.config/nfoview/nfoview.conf' file.

Best regards,

- Nicolas Jeanne.


Failed to open None: gtk-css-provider-error-quark: :4:30Junk at end of
value for font-family (1)
Traceback (most recent call last):
  File "/usr/share/nfoview/nfoview/application.py", line 51, in open_window
window = nfoview.Window(path)
  File "/usr/share/nfoview/nfoview/window.py", line 37, in __init__
self.view = nfoview.TextView()
  File "/usr/share/nfoview/nfoview/view.py", line 36, in __init__
self.update_style()
  File "/usr/share/nfoview/nfoview/view.py", line 136, in update_style
nfoview.util.apply_style(self)
  File "/usr/share/nfoview/nfoview/util.py", line 63, in apply_style
provider.load_from_data(bytes(css.encode()))
gi.repository.GLib.GError: gtk-css-provider-error-quark: :4:30Junk at end
of value for
font-family (1)



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

Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: 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 nfoview depends on:
ii  gir1.2-gtk-3.0  3.24.33-2
ii  python3 3.10.4-1+b1
ii  python3-gi  3.42.1-1

Versions of packages nfoview recommends:
ii  fonts-cascadia-code  2102.03-1

nfoview suggests no packages.

-- no debconf information