Bug#1042880: systemd: service with PrivateNetwork=yes fails to start inside a lxc container

[Simon McVittie]

On Wed, 02 Aug 2023 at 13:13:05 +0200, Michael Biebl wrote:
> Are you by any chance using unprivileged containers?

I don't know, but not intentionally! My test VM had no special
configuration and no lxc before starting the steps-to-reproduce, so I
was using whatever is the default in bookworm.

smcv

Bug#1042901: ITP: python-dm-tree -- library for working with nested data structures

[Michael Fladischer]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: python-dm-tree
  Version : 0.1.8
  Upstream Contact: DeepMind 
* URL : https://github.com/deepmind/tree
* License : Apache2
  Programming Lang: C++, Python
  Description : library for working with nested data structures

 A library for working with nested data structures. In a way, tree generalizes
 the builtin map function which only supports flat sequences, and allows one to
 apply a function to each "leaf" preserving the overall structure.
 .
 It is backed by an optimized C++ implementation suitable for use in demanding
 applications, such as machine learning models.

I intend to maintain this as part of the DPT.

-BEGIN PGP SIGNATURE-

iQFFBAEBCgAvFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmTKY1QRHGZsYWRpQGRl
Ymlhbi5vcmcACgkQ/9PIi5l90WrENQf/eyNqUFP/+iyLw5PZJQePG1ZeG6Uvi9cW
vRCh+3zFoX3hvz+T21aREY8KYpJQZayMnVLHag/DSuBbg7AX1ZTvPlO0xwPssigv
rXYodzpGGPvJBAF93tCZJhNhhooWW2OECyZowGJZSE2AmIXbt9ACtU5dAA8ErFQ/
UKm5ArGDvVu9mRKRso7hGG619cM6j8UPeb4hbSKmcu8o3iXEqzveflwe6iOSg0UU
kS4wfNL2plbRU6DOG61wQ0jZBaMmVCbWSCN6utYUsYcWXr65n/McmzdVcPvAy2bb
gJeZiyC1NfrDq8v4cxCM3Fd0RfN+OlvhG8efdViMDoPmpT4oeZ+O+A==
=KMDs
-END PGP SIGNATURE-

Bug#1042900: Breaks Emacs 29.1 upgrade: pointback.el:34:2: Error: Cannot open load file: No such file or directory, assoc

[Axel Beckert]

Package: elpa-pointback
Version: 0.2-4
Severity: serious
X-Debbugs-Cc: a...@debian.org
Control: affects -1 emacs emacs-gtk emacs-lucid emacs-nox emacs-pgtk

Since the upgrade to Emacs 29.1-1, byte (re-)compilation fails as
follows:

[…]
Install elpa-pointback for emacs
install/pointback-0.2: Handling install of emacsen flavor emacs
install/pointback-0.2: byte-compiling for emacs

In toplevel form:
pointback.el:34:2: Error: Cannot open load file: No such file or directory, 
assoc
ERROR: install script from elpa-pointback package failed
dpkg: error processing package emacs-gtk (--configure):
 installed emacs-gtk package post-installation script subprocess returned error 
exit status 1
dpkg: dependency problems prevent configuration of emacs:
[…]

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

Kernel: Linux 6.4.0-1-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 elpa-pointback depends on:
ii  dh-elpa-helper  2.0.17
ii  emacsen-common  3.0.5

Versions of packages elpa-pointback recommends:
iu  emacs  1:29.1+1-2
ih  emacs-gtk [emacs]  1:29.1+1-2

elpa-pointback suggests no packages.

-- no debconf information

Bug#1042899: bind9: Superfluous listen-on-v6 option given in named.conf.options

[Dominic Preston]

Package: bind9
Version: 1:9.18.16-1~deb12u1
Severity: minor
X-Debbugs-Cc: lzq...@gmail.com

On a default installation of bind9 on Debian, this option is included:
listen-on-v6 { any; };

According to the bind9 documentation, this is the default anyway, and does
not need to be specified:
https://bind9.readthedocs.io/en/stable/reference.html#namedconf-statement-listen-on-v6

Furthermore, this (unnecessary) listen-on option for IPv4 is not specified
in Debian's default configuration, making listen-on-v6's inclusion 
inconsistent with the default IPv4 options:
listen-on { any; };

Therefore I propose this option is removed from the default bind9 Debian
configuration for consistency with IPv4:
listen-on-v6 { any; };

Bug#1042898: RM: python3-gsd [s390x hppa m68k powerpc ppc64 sparc64] -- NBS; not built for big-endian architectures)

[Drew Parsons]

retitle 1042898 RM: python3-gsd [s390x hppa m68k powerpc ppc64 sparc64] 
-- NBS; not built for big-endian architectures

thanks

My apologise, I had my endianness mixed the wrong way.  python3-gsd 
works normally on little-endian systems

and fails on big-endian systems.

The list of arches is correct.

Bug#1042898: RM: python3-gsd [s390x hppa m68k powerpc ppc64 sparc64] -- NBS; not built for little-endian architectures

[Drew Parsons]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: python-...@packages.debian.org
Control: affects -1 + src:python-gsd

Technically python3-gsd builds on little-endian machines, but it does
not work.  Assumptions are made in the code about data structures
which means gsd files cannot be read on little-endian machines, and
tests fail on s390x. The python3-gsd is useless on these systems.

The issue is raised in Bug#1042500 and discussed upstream at
https://github.com/glotzerlab/gsd/issues/12

Since gsd in principle can't work on little-endian systems (without
large scale rewriting upstream), the binary packages are no longer
being built for little-endian.  For consistency, the old binary
packages on little-endian arches should now be removed.

Bug#1042889: vm: autopkgtest fails against Emacs 29.1

[Ian Jackson]

Sean Whitton writes ("Bug#1042889: vm: autopkgtest fails against Emacs 29.1"):
> vm's autopkgtest fails with Emacs 29.1, which latter is now in sid.

Hi, Sean, as you see we're looking into this.
I have some questions for you as an Emacs expert:

Is byte-compilation known to be sometimes broken?  Is there a
recommended approach to problems caused by byte-compilation ?

We recently did an update to vm in Debian stable, to work around a
critical problem with Emacs 28 (#1039105).  The autopkgtest which is
now failing is new - I introduced it to detect future bugs, which it
seems to have done.

The previous bug was related to byte-compilation and we "fixed" it by
turning off byte-compilation for at least some of vm's files (in what
I feel was rather an ad-hoc way, albeit an effective one).

Or to put it another way, is it possible that this is a bug in emacs
29.1 and if so what is the best workaround ?

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.  

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

Bug#1042897: aptitude: viewing a package's changelog from the TUI outputs a warning that is immediately erased

[Vincent Lefevre]

Package: aptitude
Version: 0.8.13-5
Severity: normal

When I use "C" (View a package's changelog) on clang-15 from the
aptitude TUI, I get a warning that is immediately erased, so that
it is impossible to read it.

I suppose that aptitude should redirect stderr from
aptitude-changelog-parser so that it can display its contents
(when non empty) in a clear way.

Enabling the terminal's logs allows me to get the text of this
warning:

aptitude-changelog-parser: warning: 
/tmp/aptitude-root.7707:EXkCUB/aptitude-download-4-bORTciGPJi,..uo2EeQnZD7WBcD+L6_aptitude-download-cbF3RCIRNjR7d%D7+V.DiRimX__YaCHL(l105):
 found start of entry where expected more change data or trailer

This text seems to come from /usr/share/perl5/Dpkg/Changelog/Debian.pm:

unless ($expect eq FIRST_HEADING || $expect eq NEXT_OR_EOF) {
$self->parse_error($file, $.,
sprintf(g_('found start of entry where expected %s'),
$expect), "$_");
}

About this unexpected warning, there may be some other bug.
But note that "apt changelog clang-15" is fine.

-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.13
Compiler: g++ 12.1.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.3
  libsigc++ version: 2.10.8
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20230625
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7fff953a4000)
libgtk3-nocsd.so.0 => /usr/lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f4eb8d16000)
libapt-pkg.so.6.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f4eb840)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f4eb8cdd000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f4eb8ca8000)
libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f4eb8c9f000)
libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f4eb870e000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f4eb8299000)
libboost_iostreams.so.1.74.0 => 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 (0x7f4eb8c85000)
libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f4eb800)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f4eb8c8)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f4eb7c0)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f4eb862f000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f4eb8c5a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4eb7a1e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f4eb8c55000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f4eb8c36000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f4eb8c23000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f4eb826a000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7f4eb8244000)
libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 
(0x7f4eb7f4)
libudev.so.1 => /usr/lib/x86_64-linux-gnu/libudev.so.1 
(0x7f4eb7f0e000)
libsystemd.so.0 => /usr/lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f4eb793f000)
libgcrypt.so.20 => /usr/lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7f4eb77f9000)
libxxhash.so.0 => /usr/lib/x86_64-linux-gnu/libxxhash.so.0 
(0x7f4eb861a000)
/lib64/ld-linux-x86-64.so.2 (0x7f4eb8d43000)
libuuid.so.1 => /usr/lib/x86_64-linux-gnu/libuuid.so.1 
(0x7f4eb861)
libcap.so.2 => /lib/x86_64-linux-gnu/libcap.so.2 (0x7f4eb8238000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7f4eb7ee6000)

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.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 aptitude depends on:
ii  aptitude-common   0.8.13-5
ii  libapt-pkg6.0 2.7.2
ii  libboost-iostreams1.74.0  1.74.0+ds1-22
ii  libc6 2.37-6
ii  libcwidget4   0.5.18-6
ii  libgcc-s1 13.2.0-1
ii  libncursesw6  6.4+20230625-2
ii  libsigc++-2.0-0v5 2.12.0-1
ii  

Bug#1042896: transition: armadillo

[Kumar Appaiah]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: armadi...@packages.debian.org
Control: affects -1 + src:armadillo

Dear Release Team,

I have uploaded the new Armadillo to experimental. I would like your
permission to upload it to unstable. binNMUs should be sufficient for
the reverse dependencies.

Please let me know if you have any questions.

Thank you.

Kumar

Ben file:

title = "armadillo";
is_affected = .depends ~ "libarmadillo11" | .depends ~ "libarmadillo12";
is_good = .depends ~ "libarmadillo12";
is_bad = .depends ~ "libarmadillo11";

Bug#1042889: vm breakage with Emacs 29

[Ian Jackson]

Dirk Eddelbuettel writes ("Re: vm breakage with Emacs 29"):
> On 2 August 2023 at 13:17, Ian Jackson wrote:
> | Hi.  Since you were helpful with #1039105 "Fails to start with Emacs
> | 28" I thought I would draw your attention to #1042889
> | "vm: autopkgtest fails against Emacs 29.1" [0]
> | 
> | I won't have time to look at this until next week, probably.  Any help
> | or background research would be greatly appreciated.  We need to fix
> | this to avoid vm getting autoremoved.
> | 
> | I did have a quick look at the test log [1] and the failure looks
> | genuine.  I suggest we do any further diagnosis in the bug.
> 
> The band-aid I found and submitted for #1039105 (ie per Fedora's tracker,
> "just do not byte compile") seems apt here, no?  I still do not really read
> (or, for that matter, write) elisp but it seems to complain about byte code.
> 
> So I would try two things:
>  - turn off elisp byte compilation as in #1039105

The patch from #1039105 is still in the package.

Do we need to add to a list of files in it, or something, do you
think ?  Maybe it would be best to disable byte compilation
completely.

One thing that would be useful would be for someone to try out emacs
and vm in a sid chroot; that would confirm that this isn't a spurious
test failure (or confirm that it is).

Thanks,
Ian.

-- 
Ian JacksonThese opinions are my own.  

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

Bug#1042023: opm-common: FTBFS on armel and mipsel

[Markus Blatt]

Thanks a lot for reporting this. We are aware of this but did not find 
the time to look into it, yet.


Is there a good howto/instructions how to debug such problems using e.g. 
qemu for emulating arm? Or is it possible to gain access to an arm 
machine as a Debian Maintainer?


That would help a lot.

Kind regards,

Markus

Bug#1042895: RM: ares [armel armhf i386 mips64el mipsel s390x] -- ROM; allow migration to testing

[Alexandre Detiste]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: a...@packages.debian.org, debian-devel-ga...@lists.debian.org
Control: affects -1 + src:ares

Hi,

We were busy packaging v133 as a way to workaround
the FTBFS of v132, but during this process
we found a whole BIOS added as a .h file.

This will take a while to resolve/strip-out and
may later need the packaging of a new ares-nonfree.

A new release would also depends on ITP's libchdr
that depends on my new-DD process mentoring.


All of this will take a while,
can you please in the meantime remove
the blacklisted architecure to
allow v132-1 to migrate to testing ?

Thank you for your time.


Greetings,

Bug#1042894: cron: PATH values should be modernized

[Daniel Lewart]

Package: cron
Version: 3.0pl1-163
Severity: normal

Georges, et al,

pathnames.h has the following line:
# define _PATH_DEFPATH "/usr/bin:/bin"
Could it be changed to this?
# define _PATH_DEFPATH "/usr/sbin:/usr/bin"
crontab.5 would need to be changed too.

debian/crontab.main has the following line:
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
Could it be changed to this?
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin

Thank you!
Daniel Lewart
Urbana, Illinois

Bug#1042824: Logging into SLBackup frontend returns error

[Guido Berhoerster]

There are actually two critical problems causing logins to fail:

1. usage of crypt() without a salt (not actually used for passwords
   but as a hash function for some homemade encryption, see
   
https://salsa.debian.org/debian-edu-pkg-team/slbackup-php/-/blob/8eb0d468422cb3e06eed0092643d1bb4082f9b1c/src/index.php#L698)
2. a typo where the key is switched with the value while looping over
   an associative array which causes an exception with PHP 8 since 
   the key is a string accessed as an associative array (see
   
https://salsa.debian.org/debian-edu-pkg-team/slbackup-php/-/blob/8eb0d468422cb3e06eed0092643d1bb4082f9b1c/src/index.php#L48)

-- 
Guido Berhoerster

Bug#1042892: nvidia-legacy-390xx-kernel-dkms: dkms module does not build against kernel 6.4

[Vincent Lefevre]

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042081
for the same bug corresponding to nvidia-kernel-dkms.

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

Bug#1041242: libheif1: 1.16.2-1+b1 breaks displaying any pictures

[Christoph Anton Mitterer]

Control: forwarded -1 https://github.com/strukturag/libheif/issues/933

Hey.

AFAICS, this had also been reported (and fixed meanwhile) upstream.

Cheers,
Chris.

Bug#1042893: pcs: resource move fails

[Rik Theys]

Source: pcs
Version: 0.11.5-1
Severity: important
Tags: upstream patch

Hi,

I've set up a pacemaker cluster using pcs on Debian 12. When trying to
move a resource from one node to the next, this fails with a python
error:

Traceback (most recent call last):  
  File "/usr/sbin/pcs", line 33, in 
 
sys.exit(load_entry_point('pcs==0.11.5', 'console_scripts', 'pcs')())
 ^^^
  File "/usr/lib/python3/dist-packages/pcs/app.py", line 273, in main
routing.create_router(cmd_map, [])(
  File "/usr/lib/python3/dist-packages/pcs/cli/common/routing.py", line 33, in 
_router
return cmd_map[sub_cmd](lib, argv_next, modifiers)
   ^^^
  File "/usr/lib/python3/dist-packages/pcs/cli/common/routing.py", line 33, in 
_router
return cmd_map[sub_cmd](lib, argv_next, modifiers)
   ^^^
  File "/usr/lib/python3/dist-packages/pcs/resource.py", line 854, in 
resource_move
lib.resource.move_autoclean(
  File "/usr/lib/python3/dist-packages/pcs/cli/common/lib_wrapper.py", line 95, 
in decorated_run
return run_with_middleware(run, cli_env, *args, **kwargs)
   ^^
  File "/usr/lib/python3/dist-packages/pcs/cli/common/middleware.py", line 14, 
in run
return next_in_line(env, *args, **kwargs)
   ^^
  File "/usr/lib/python3/dist-packages/pcs/cli/common/middleware.py", line 42, 
in apply
result_of_next = next_in_line(env, *args, **kwargs)
 ^^
  File "/usr/lib/python3/dist-packages/pcs/cli/common/middleware.py", line 80, 
in apply
result_of_next = next_in_line(env, *args, **kwargs)
 ^^
  File "/usr/lib/python3/dist-packages/pcs/cli/common/lib_wrapper.py", line 86, 
in run
lib_call_result = run_library_command(lib_env, *args, **kwargs)
  ^
  File "/usr/lib/python3/dist-packages/pcs/lib/commands/resource.py", line 
1823, in move_autoclean
_, move_transitions, after_move_simulated_cib = simulate_cib(
^
  File "/usr/lib/python3/dist-packages/pcs/lib/pacemaker/live.py", line 426, in 
simulate_cib
plaintext_result, transitions_xml, new_cib_xml = simulate_cib_xml(
 ^
  File "/usr/lib/python3/dist-packages/pcs/lib/pacemaker/live.py", line 387, in 
simulate_cib_xml
with tools.get_tmp_file() as new_cib_file, tools.get_tmp_file() as 
transitions_file:
 
  File "/usr/lib/python3.11/contextlib.py", line 289, in helper
return _GeneratorContextManager(func, args, kwds)
   ^^
  File "/usr/lib/python3.11/contextlib.py", line 105, in __init__
self.gen = func(*args, **kwds)
   ^^^
TypeError: get_tmp_file() missing 1 required positional argument: 'data'


This seems to be a known regression: 
https://github.com/ClusterLabs/pcs/issues/696

A patch is available upstream: 
https://github.com/ClusterLabs/pcs/commit/2ab9e9c4fd1f26e5320c7585a83ba5d1857d4042


The patch looks very small and clean. Please apply the patch to the Debian 12 
version.

Regards,
Rik



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

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

Bug#1019404: wireplumber doesn't start without systemd-logind

[urs]

In addition to the startup issues above, recent versions of the 
wireplumber package fail to start in the absence of systemd logind on 
the system:

---
M 15:38:55.288462 mod.rt 
../src/modules/module-rt.c:278:pw_rtkit_check_xdg_portal: Can't find 
xdg-portal: (null)
M 15:38:55.288536 mod.rt 
../src/modules/module-rt.c:991:pipewire__module_init: found session bus 
but no portal
M 15:38:55.289375 mod.rt 
../src/modules/module-rt.c:297:translate_error: RTKit error: 
org.freedesktop.DBus.Error.ServiceUnknown
M 15:38:55.289505 mod.rt 
../src/modules/module-rt.c:622:set_nice: could not set nice-level to 
-11: No such file or directory
M 15:38:55.289691 mod.rt 
../src/modules/module-rt.c:297:translate_error: RTKit error: 
org.freedesktop.DBus.Error.ServiceUnknown
M 15:38:55.291435 mod.rt 
../src/modules/module-rt.c:297:translate_error: RTKit error: 
org.freedesktop.DBus.Error.ServiceUnknown
M 15:38:55.291641 mod.rt 
../src/modules/module-rt.c:297:translate_error: RTKit error: 
org.freedesktop.DBus.Error.ServiceUnknown
M 15:38:55.291654 mod.rt 
../src/modules/module-rt.c:843:impl_acquire_rt: could not make thread 
27742 realtime using RTKit: No such file or directory

failed to start systemd logind monitor: -2 (No such file or directory)
M 15:38:55.303907wireplumber ../src/main.c:364:on_disconnected: 
disconnected from pipewire

---

This can be fixed by editing 
/usr/share/wireplumber/bluetooth.lua.d/50-bluez-config.lua and setting

---
 ["with-logind"] = false,
---

Bug#1042891: rust-ron: Please upgrade to v0.8

[Jonas Smedegaard]

Source: rust-ron
Version: 0.7.1-2
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to (or separately provide) newer upstream branch v0.8.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTKTD8ACgkQLHwxRsGg
ASFVZA//c5Sth/JWn2r4DFPbSeAUJhqMZ59rpR//GY8k8Di9+SB5QafP9Ys2jnC4
xckaHoaoZw/rJVcfb3WAKS3dlhqZLGVkGO8Cm227Ztg5ldDX1JQJZbX7d65nsiJl
j/j0thAJkKhVszJP6mRHPWX7wRppYEE57XnLREus+nQuuid8vs87QG0H5zFE6G4u
z7VmfhroDFK9luUvrR1bwq/j3wVubJOMXRbEEbuuf0CjUcgxrIgKfKpjK/10PoSs
cPWT3Cg5cS00Qx2YsXPbDDmAWNmxmgpECI+SrMsmghkQ+h4u1mlv517p8HRLLahm
LV4nM9JVTRzicxfepzlAtwy4cPB6ekeBQ7YwutYX78iaxEMa1P3uzci/peSjb/14
DcfqUbO57Zpt9RpCOYJuSPnApzEVEU5Fh6kicyXgq7c4wHGqd6Uj5YA5uBncNWOQ
ac6KcTvzScauFWCgGYri1Stzy1k8L9Hs6Z8BhGPhiJYtrNGMEBv3BBGT0zHYpoVm
wcM/Sz4pKwPmrwp8A2R0UWTRTY1F8seB526FcTvqoll/Hks8Svx1S4HEAGC931EZ
kSfo5yqiVLftCi/dabb76s81aa4Nnt1zfvBKTuBKd+V/LAFxAcTpvkhKjx9FbNnf
iSoFVb1MS1HQG7huyARNARRgBkCo+rnWUsdoVuUr5H+Nbwq2OO0=
=0+H6
-END PGP SIGNATURE-

Bug#1042890: haskell-mode: bytecompilation fails against Emacs 29.1

[Sean Whitton]

Source: haskell-mode
Version: 17.2-5
Severity: serious

Dear maintainer,

haskell-mode fails to bytecompile against Emacs 29.1, which latter is
now in sid.

In toplevel form:
haskell.el:30:2: Error: Eager macro-expansion failure: (error "Misplaced t 
or ‘otherwise’ clause")

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1042889: vm: autopkgtest fails against Emacs 29.1

[Sean Whitton]

Source: vm
Version: 8.2.0b-10
Severity: serious

Dear maintainer,

vm's autopkgtest fails with Emacs 29.1, which latter is now in sid.

https://ci.debian.net/packages/v/vm/testing/amd64/

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1042888: gdm3: 61-gdm.rules: bad pattern will skip some future nvidia driver versions

[Andreas Beckmann]

Package: gdm3
Severity: normal

# For nvidia drivers versions Above 510, keep Wayland by default
ATTR{version}=="[5-9][1-9][0-9].*", GOTO="gdm_end"
# For nvidia drivers versions 470-495, prefer Xorg by default
GOTO="gdm_prefer_xorg"

This pattern does not match e.g. 600.*, so some future nvidia releases
might run with a default of Xorg instead of wayland.

Also note the bad capitalization of "Above" in the comment above.


Andreas

Bug#1025545: dependencies on transitional policykit-1 package are now RC

[Simon McVittie]

Control: severity -1 serious

On Sun, 11 Jun 2023 at 13:12:25 +0100, Simon McVittie wrote:
> On Tue, 06 Dec 2022 at 13:09:22 +, Simon McVittie wrote:
> > This package has a Depends on the transitional package policykit-1, which
> > has been separated into polkitd, pkexec and (deprecated) polkitd-pkla
> > packages.
> 
> Now that bookworm has been released, I'm intending to remove the
> policykit-1 transitional package during the trixie cycle, so I'm raising
> the severity of depends/recommends on the transitional package to
> important. The severity will increase to serious later on.

The polkitd and pkexec packages have existed since Debian 12 and Ubuntu
22.04, and policykit-1 was a transitional package in those stable
releases, so it has served its purpose and should be removed before the
next stable release.

Please replace all Depends, Recommends or Build-Depends on policykit-1:

* If this package runs /usr/bin/pkexec, please represent that as a Depends,
  Recommends or Suggests on pkexec, whichever is appropriate.

* If this package communicates with polkitd via D-Bus, please represent that
  as a Depends, Recommends or Suggests on polkitd, whichever is appropriate.

* If this package requires the gettext extensions polkit.its and polkit.loc,
  please build-depend on libpolkit-gobject-1-dev. If the package will be
  backported to bookworm, also build-depend on polkitd.

* If this package requires polkitd and/or pkexec at build-time, please
  build-depend on polkitd and/or pkexec as appropriate.

> (I'm doing this for packages with only a Recommends too, even though those
> don't technically prevent removal of policykit-1, because a Recommends
> on a package that no longer exists is not allowed under Policy §2.2.1.)

Thanks,
smcv

Bug#1042887: procps: CVE-2023-4016 ps buffer overflow

[Craig Small]

Package: procps
Version: 2:4.0.3-1
Severity: important
Tags: security
X-Debbugs-Cc: Debian Security Team 

We have a very scant report of a ps buffer overflow security bug.

Under some circumstances, this weakness allows a user who has access to run the 
“ps” utility on a machine, the ability to write almost unlimited amounts of 
unfiltered data into the process heap.

We don't know the versions impacted, we don't know how to cause it. We
have that single sentence. Once (any) details are given we will update
this bug and the gitlab issue.

I made the severity important because I'm not even sure its a real bug
yet.

References:
 https://nvd.nist.gov/vuln/detail/CVE-2023-4016
 https://gitlab.com/procps-ng/procps/-/issues/297



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

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

Versions of packages procps depends on:
ii  init-system-helpers  1.65.2
ii  libc62.36-9+deb12u1
ii  libncursesw6 6.4-4
ii  libproc2-0   2:4.0.3-1
ii  libtinfo66.4-4

Versions of packages procps recommends:
ii  psmisc  23.6-1

procps suggests no packages.

-- no debconf information

Bug#1042886: zstd libzstd1 breaks boot mkinitramfs update-initramfs-u initramfs-tools

[Christian Kiss]

Package: zstd
Version: 1.4.8+dfsg-2.1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: christianpeterk...@yahoo.com

Dear Maintainer,

/var/tmp/lib/modules/ does not include files into vmlinuz and this error of
bookworm 6.1 zstd libzstd1 mkinitramfs may cluster the -rt-kernels of 5.10 too


your recent rt-kernel updates 179-3 on to BULLSEYE-to-BOOKWORM upgrade breaks
the boot right after bios.

#KEYPOINT initramfs-tools-core, initramfs-tools, mkinitramfs, zstd, libzstd1
are the core of the issue. VMLINUZ and INITRD.IMG are not created functional
any longer.

The systems are functional and longterm stable before these modifications.

Bookworm 0.142 and 1.54 are problem packages,
Bullseye -rt-22- and -rt-23- kernels are dysfunct now, while non-rt kernel -20-
work yet.

Thank you for your hard work, i hope this helps fix the issue.
All the best
Christian KISS

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

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

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


-- System Information:
Debian Release: 11.7
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500,
'oldstable')
Architecture: i386 (i686)

Kernel: Linux 5.10.0-20-686-pae (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages zstd depends on:
ii  libc6   2.31-13+deb11u6
ii  libgcc-s1   10.2.1-6
ii  liblz4-11.9.3-2
ii  liblzma55.2.5-2.1~deb11u1
ii  libstdc++6  10.2.1-6
ii  zlib1g  1:1.2.11.dfsg-2+deb11u2

zstd recommends no packages.

zstd suggests no packages.

Bug#1042885: initramfs-tools: breaks system boot after bios: initramfs-tools-core, initramfs-tools, zstd, libzstd1

[Christian Kiss]

Package: initramfs-tools
Version: 0.140
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: christianpeterk...@yahoo.com

Dear Maintainer,

your recent rt-kernel updates 179-3 on to BULLSEYE-to-BOOKWORM upgrade breaks
the boot right after bios.

#KEYPOINT initramfs-tools-core, initramfs-tools, mkinitramfs, zstd, libzstd1
are the core of the issue. VMLINUZ and INITRD.IMG are not created functional
any longer.

The systems are functional and longterm stable before these modifications.

Bookworm 0.142 and 1.54 are problem packages,
Bullseye -rt-22- and -rt-23- kernels are dysfunct now, while non-rt kernel -20-
work yet.

Thank you for your hard work, i hope this helps fix the issue.
All the best
Christian KISS




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

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

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


-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 62M Aug  2 13:21 /boot/initrd.img-5.10.0-20-686-pae
-rw-r--r-- 1 root root 62M Aug  1 23:49 /boot/initrd.img-5.10.0-23-rt-686-pae
-rw-r--r-- 1 root root 20M Aug  2 13:16 /boot/initrd.img-DEB_BUILD_HARDENING=1
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.10.0-20-686-pae root=/dev/mapper/via_dcfiheddca8 ro 
dmraid=true splash maxcstate=0 max.cstate=0 quiet kaslr pti=on slab_nomerge 
page_poison=1 slub_debug=FPZ nosmt

-- resume
RESUME=UUID=4b9b288b-6e37-48b5-8390-ffaad362e47e
-- /proc/filesystems
ext3
ext2
ext4
fuseblk

-- lsmod
Module  Size  Used by
ath5k 139264  0
tuner_simple   20480  1
tuner_types16384  1 tuner_simple
nf_log_ipv616384  6
ath28672  1 ath5k
mac80211  663552  1 ath5k
tuner  28672  1
cfg80211  614400  3 mac80211,ath,ath5k
msp340032768  1
snd_emu10k1_synth  20480  0
snd_emux_synth 36864  1 snd_emu10k1_synth
snd_seq_midi   20480  0
snd_seq_midi_emul  20480  1 snd_emux_synth
snd_seq_virmidi16384  1 snd_emux_synth
snd_seq_midi_event 16384  2 snd_seq_virmidi,snd_seq_midi
snd_seq57344  5 
snd_seq_virmidi,snd_seq_midi_event,snd_seq_midi_emul,snd_seq_midi,snd_emux_synth
rfkill 20480  4 cfg80211
libarc416384  1 mac80211
bttv  122880  0
serio_raw  20480  0
tea575x16384  1 bttv
pcspkr 16384  0
snd_emu10k1   135168  1 snd_emu10k1_synth
tveeprom   24576  1 bttv
snd_util_mem   16384  2 snd_emu10k1,snd_emux_synth
videobuf_dma_sg16384  1 bttv
snd_via82xx_modem  24576  0
snd_hwdep  16384  2 snd_emu10k1,snd_emux_synth
videobuf_core  24576  2 bttv,videobuf_dma_sg
snd_ac97_codec122880  2 snd_via82xx_modem,snd_emu10k1
snd_rawmidi32768  3 snd_emu10k1,snd_seq_virmidi,snd_seq_midi
rc_core45056  1 bttv
snd_seq_device 16384  5 
snd_emu10k1,snd_seq,snd_emu10k1_synth,snd_rawmidi,snd_seq_midi
snd_bt87x  20480  0
ac97_bus   16384  1 snd_ac97_codec
snd_pcm90112  4 
snd_via82xx_modem,snd_emu10k1,snd_bt87x,snd_ac97_codec
videodev  180224  4 tuner,tea575x,msp3400,bttv
snd_timer  32768  3 snd_emu10k1,snd_seq,snd_pcm
snd65536  12 
snd_via82xx_modem,snd_emu10k1,snd_seq_virmidi,snd_hwdep,snd_seq,snd_bt87x,snd_ac97_codec,snd_timer,snd_rawmidi,snd_seq_device,snd_pcm,snd_emux_synth
mc 40960  3 tuner,msp3400,videodev
soundcore  16384  1 snd
sg 28672  0
xt_hl  16384  22
evdev  20480  7
ip6_tables 24576  52
ip6t_rt20480  3
ip6t_REJECT16384  523
nf_reject_ipv6 20480  1 ip6t_REJECT
nf_log_ipv416384  6
nf_log_common  16384  2 nf_log_ipv6,nf_log_ipv4
xt_LOG 20480  12
xt_recent  24576  4
xt_multiport   20480  24
nft_limit  16384  15
xt_limit   16384  0
xt_addrtype16384  4
xt_tcpudp  20480  1047
xt_conntrack   16384  16
nf_conntrack  114688  1 xt_conntrack
nf_defrag_ipv6 24576  1 nf_conntrack
nf_defrag_ipv4 16384  1 nf_conntrack
ipt_REJECT 16384  527
nf_reject_ipv4 16384  1 ipt_REJECT
nft_compat 20480  2242
nft_counter16384  1227
msr16384  0
nf_tables 167936  2500 nft_limit,nft_compat,nft_counter
parport_pc 32768  0
libcrc32c  16384  2 nf_conntrack,nf_tables
ppdev  24576  0
nfnetlink  20480  2 nft_compat,nf_tables
lp  

Bug#1025536: crontab_5_manpage.patch undoes No-multiple-timezones.patch and more

[Daniel Lewart]

Version: 3.0pl1-163

Georges, et al,

crontab_5_manpage.patch:

https://salsa.debian.org/debian/cron/-/blob/master/debian/patches/fixes/crontab_5_manpage.patch
undoes No-multiple-timezones.patch:

https://salsa.debian.org/debian/cron/-/blob/master/debian/patches/features/No-multiple-timezones.patch
and more.

If this was accidental and No-multiple-timezones.patch is restored,
please remove "SHELL=/bin/sh", which is a no op.

Thank you!
Daniel Lewart
Urbana, Illinois

Bug#1040782: working with GIMP 2.10.30

[graeme vetterlein]

In case it helps in narrowing it down.


I have the wacom tablet connected via a USB switch. If I switch the 
hardware to a Kubuntu system running GIMP 2.10.30, it works fine.



The failing system is a "dev box", so if you want me to try a number of 
versions (and give brief instructions) I can do that.



As I said previously, the failing system just moved from bookwork to 
trixie, I'm afraid I didn't note the (working) gimp version prior to 
upgrade.



--


Graeme

Bug#1041792: httpie: phones home for version check

[ss0buh+5z7qu6hu1fgzw]

Package: httpie
Followup-For: Bug #1041792
Control: tags -1 patch

quick patch attached
>From 3ce3cacb8d3f7beff8d684a088ac4ecc016cc9c1 Mon Sep 17 00:00:00 2001
From: Your Name 
Date: Wed, 2 Aug 2023 11:23:38 +
Subject: [PATCH] disable updates

---
 httpie/core.py|   2 -
 httpie/internal/daemon_runner.py  |   2 -
 httpie/internal/update_warnings.py| 171 ---
 httpie/manager/tasks/__init__.py  |   2 -
 httpie/manager/tasks/check_updates.py |  10 --
 tests/test_update_warnings.py | 237 --
 6 files changed, 424 deletions(-)
 delete mode 100644 httpie/internal/update_warnings.py
 delete mode 100644 httpie/manager/tasks/check_updates.py
 delete mode 100644 tests/test_update_warnings.py

diff --git a/httpie/core.py b/httpie/core.py
index d0c26dc..0755e6d 100644
--- a/httpie/core.py
+++ b/httpie/core.py
@@ -24,7 +24,6 @@ from .output.writer import write_message, write_stream, 
write_raw_data, MESSAGE_
 from .plugins.registry import plugin_manager
 from .status import ExitStatus, http_status_to_exit_status
 from .utils import unwrap_context
-from .internal.update_warnings import check_updates
 from .internal.daemon_runner import is_daemon_mode, run_daemon_task
 
 
@@ -95,7 +94,6 @@ def raw_main(
 raise
 exit_status = ExitStatus.ERROR
 else:
-check_updates(env)
 try:
 exit_status = main_program(
 args=parsed_args,
diff --git a/httpie/internal/daemon_runner.py b/httpie/internal/daemon_runner.py
index ec20b50..b2d3fb1 100644
--- a/httpie/internal/daemon_runner.py
+++ b/httpie/internal/daemon_runner.py
@@ -3,7 +3,6 @@ from contextlib import redirect_stderr, redirect_stdout
 from typing import List
 
 from httpie.context import Environment
-from httpie.internal.update_warnings import _fetch_updates, 
_get_suppress_context
 from httpie.status import ExitStatus
 
 STATUS_FILE = '.httpie-test-daemon-status'
@@ -23,7 +22,6 @@ def _check_status(env):
 
 DAEMONIZED_TASKS = {
 'check_status': _check_status,
-'fetch_updates': _fetch_updates,
 }
 
 
diff --git a/httpie/internal/update_warnings.py 
b/httpie/internal/update_warnings.py
deleted file mode 100644
index a4b80d4..000
--- a/httpie/internal/update_warnings.py
+++ /dev/null
@@ -1,171 +0,0 @@
-import json
-from contextlib import nullcontext, suppress
-from datetime import datetime, timedelta
-from pathlib import Path
-from typing import Any, Optional, Callable
-
-import requests
-
-import httpie
-from httpie.context import Environment, LogLevel
-from httpie.internal.__build_channel__ import BUILD_CHANNEL
-from httpie.internal.daemons import spawn_daemon
-from httpie.utils import is_version_greater, open_with_lockfile
-
-# Automatically updated package version index.
-PACKAGE_INDEX_LINK = 'https://packages.httpie.io/latest.json'
-
-FETCH_INTERVAL = timedelta(weeks=2)
-WARN_INTERVAL = timedelta(weeks=1)
-
-UPDATE_MESSAGE_FORMAT = """\
-A new HTTPie release ({last_released_version}) is available.
-To see how you can update, please visit 
https://httpie.io/docs/cli/{installation_method}
-"""
-
-ALREADY_UP_TO_DATE_MESSAGE = """\
-You are already up-to-date.
-"""
-
-
-def _read_data_error_free(file: Path) -> Any:
-# If the file is broken / non-existent, ignore it.
-try:
-with open(file) as stream:
-return json.load(stream)
-except (ValueError, OSError):
-return {}
-
-
-def _fetch_updates(env: Environment) -> str:
-file = env.config.version_info_file
-data = _read_data_error_free(file)
-
-response = requests.get(PACKAGE_INDEX_LINK, verify=False)
-response.raise_for_status()
-
-data.setdefault('last_warned_date', None)
-data['last_fetched_date'] = datetime.now().isoformat()
-data['last_released_versions'] = response.json()
-
-with open_with_lockfile(file, 'w') as stream:
-json.dump(data, stream)
-
-
-def fetch_updates(env: Environment, lazy: bool = True):
-if lazy:
-spawn_daemon('fetch_updates')
-else:
-_fetch_updates(env)
-
-
-def maybe_fetch_updates(env: Environment) -> None:
-if env.config.get('disable_update_warnings'):
-return None
-
-data = _read_data_error_free(env.config.version_info_file)
-
-if data:
-current_date = datetime.now()
-last_fetched_date = datetime.fromisoformat(data['last_fetched_date'])
-earliest_fetch_date = last_fetched_date + FETCH_INTERVAL
-if current_date < earliest_fetch_date:
-return None
-
-fetch_updates(env)
-
-
-def _get_suppress_context(env: Environment) -> Any:
-"""Return a context manager that suppress
-all possible errors.
-
-Note: if you have set the developer_mode=True in
-your config, then it will show all errors for easier
-debugging."""
-if env.config.developer_mode:
-return nullcontext()
-else:
-return suppress(BaseException)
-
-
-def _update_checker(
-  

Bug#1042880: systemd: service with PrivateNetwork=yes fails to start inside a lxc container

[Michael Biebl]

Hi Simon

Am 02.08.23 um 12:32 schrieb Simon McVittie:

However, in a lxc container, this isn't working for me, causing
autopkgtest failure for policykit-1 (>= 123) (which I'm going to work
around by removing the PrivateNetwork=yes option for now). This is
important because ci.debian.net can currently only test packages in an
lxc container.

Steps to reproduce
==


I'm not able to reproduce the issue (running LXC on Debian sid).
I use privileged LXC containers with the following config:

# cat /etc/lxc/default.conf
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up

lxc.apparmor.profile = generated
lxc.apparmor.allow_nesting = 1
lxc.apparmor.profile = unconfined


Are you by any chance using unprivileged containers?


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1042884: rust-lru: Please upgrade to v0.8

[Jonas Smedegaard]

Source: rust-lru
Version: 0.7.8-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please upgrade to (or separately provide) newer upstream branch v0.8.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTKOQEACgkQLHwxRsGg
ASHjEg//aNrI77FurvvtKaHwWGYcOW7kz49MF1U5BB0rnEi11O8Ut9fZM9CAfzQf
fx/c1uIt655YKsWC6h+eNI3zK3zWHWtoSr7LVRQbm8/PCs51bzadA76+XbQsSxJ1
gnpzpwZXscseb1bfMiztwAmxmd0GiDVW/dWvb+O2YROsdZ3eli2H2NsPt3oZFoWx
Y4YZ2o+DVss+lmIHiRPCXDmYvtD2sp0o6315Wu9y/AjRtU5zjMBtM8PhDxxep22d
HnuCl5I8gvfnCDW48uZqaLs2dhX3jSGELhFP+3/VUNVth9gr60UwsFt/e0GHNSOc
BVR0CT0fsEP/BbBuwnb/eOggP6lXjhDqEtlTxDiZKE0qdNzhIzVKK01hDFKmBvtP
4QV3UhJO0+gxuxMyhYpgAobwRS0H/QnRxfs1Cb8QF3jIdne9QECNt7eLh4mRTRzm
lO8B1FBoj01tBYyMJmYCslwnas2lPN1/9RHErZRKKHAZfPieaFt4LaoUzVAESJIQ
26qUEMhOwO618S+ruIQo518hW7uINpd9oase5MwADpBkT7RmlvZDoBSQ8sgMdbsl
kLwhDPbndCcKmblPTEvCNu3HxfW+V5Bkk8Laxtq6lUwwQbWsY7pno7aFHHFqCdGM
+5TcURcHUDgSRJGWFIvS5V/x4PwH2rCvIEOuhsITCQuMWo3F6x8=
=w5Uj
-END PGP SIGNATURE-

Bug#1042883: rust-home: Please update to v0.5.4

[Jonas Smedegaard]

Source: rust-home
Version: 0.5.1-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to (at least) newer upstream release v0.5.4.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTKOFoACgkQLHwxRsGg
ASFpPg/9HpyjC+b+8+poGB0is1NyxaZAShKikfZAUKNGn1qAxGZSNu0mTLywbXm3
j7YBOC38uGkRJqPbm0AwJAv9T98gU1nyEslgOjRuj36XucbyvF5/HS+MI4PHHkfU
HpRx53bmp0LLk+qJ47bT+MFxLWbsoUag+DxjBBfoyPKX7er/M+Rs8ZuZzhmFlTsh
DwvmQj3p7hwVHpSNtqI5PLSUysxEJkcWJdcwHrcHmeETcxS2BFOczL8uiLdlOYQp
czv1XipqhGoY2ugmJhOCQbh9/LvvKP29djaUEAzy+Y8duMUM9keTEyDtR+wMRsgC
vB9/xMuInqAlpqG5OfLRBS8E69JXkBF7e14LezCIQ7ts3UxBbTNY33qJs0QZ1mDI
5M+fu+9RwiwiuxSWFQACFxQ2p3rwKj1FbqkTh0JyVinINydDVGAr4SwQy/HkhrB+
aDthbJfr/nf14KZvWlEHVil1MZuf1sNXLY2cZBlgqbUsGueXpoMuO8EijYJmxy1E
jZohXtuTnXAZj+oqNwIKhTiSnFidCvb3en0OcYQmrk4hvgSYQ+iGP/mb+pcZ0Owq
5VRQhD5eI+TEfskpqrmwirfHWxF7PR2Z2M9w/UcUr3oTJZSzpF1774c7XhSsnUvn
1NeMEYOb25QNQYkNl7eG6EITtJudHkdMJ8th0cg4Mihn5xLowcA=
=8OZg
-END PGP SIGNATURE-

Bug#1042882: librust-bytemuck-dev: Please provide feature derive

[Jonas Smedegaard]

Package: librust-bytemuck-dev
Version: 1.12.1-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please provide feature "derive".
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTKN5AACgkQLHwxRsGg
ASGPnA//SVzKDsZEcU+cRx4Rw8l+xTvxBaVcfSAYnXzdHO+WEMDNuc0US75PkxZm
ZOisP/iuVS9udILV981HZ63ut7a2hK3iInQ89It8axRtshb4yrDwlShwt8JumymC
TRND4UCGCpdfzo25Xgoeb7FnUsWSFHbeKpR4cpu1ZQTDM1S7rnAdq8Vw/Ics4BkC
Fobgfo0V3L2bYj59qGi2FXatjxBkjR7EsUn0AouhIvrRvl5flFZUG++s1pyM+ja0
Mb6SGNdlE25klbPHA6HIOTcFDGrpNlqEXu1QqoAY7qjbSZVNLDIsdy3wRd6i6EYc
AsUGT8oWR3JXEqPA1aKVObZgslUnZHcuFBkaPqQuxiYIGJLMTMNNJ/pQyCC5TIFQ
D9RbxdSAunktNDiqgK6NKzEanH2MO5uYz0wmJawiyPJvXgiEhCy0yxyVEbmGT6C6
YpHLc+qkRba0k195gpNZBQIb0kPbObMFj5oIJYSdGSxRyD2FUB8R6h+GTTzO7C+g
veM4S9j1Ph6OPRTKI9DkbSbpooAKUsUaZiFEBOKV7DhjWUN3V/t53+2ZdoRy5zgW
0nNN3kZ6VZN0zxAwRgooRG9BR1iR3qBfpO+kUpX943S039FiGNoIMt8QQMSUK9qK
s1R8+wh4nzH/qpH67BAEacRDLZ6ePqfwdrlJ0aQd522UYIpfFfk=
=XEDI
-END PGP SIGNATURE-

Bug#1042881: ppp: debian-installer fails when using 'modules=ppp-udeb' kernel-parameter to connect via PPPoE

[Markus Schramma]

Package: ppp
Version: 2.4.9-1
Severity: normal
Tags: d-i newcomer patch

The debian-installer manual tells that you can use the boot-kernel-parameter
'modules=ppp-udev' to use a PPPoE connection during installation, which I had
used successfully on older (Jessie) versions. Now I want to use that feature in
Bullseye which fails. I have investigated the problem and found two reasons:

1) The ppp-udeb's postinst-script runs pppoe-discovery with the '-A' parameter,
which was deprecated and is removed in the version shipped with bullseye.
Thus ppp-discovery don't run successfully and the installer gives an
error message. I have fixed this successfully:


--- ppp-2.4.9/debian/ppp-udeb.postinst  2021-01-07 01:10:29.0 +0100
+++ ppp-udeb.postinst   2023-08-02 12:10:30.233592399 +0200
@@ -31,7 +31,7 @@
db_progress START 0 $TOTWAIT ppp/detect_progress
for P in "" "-U" ; do
rm -f /tmp/probe-finished /tmp/ppp-errors
-   ( R=$(pppoe-discovery -A $P -I $1 2>/tmp/ppp-errors | \
+   ( R=$(pppoe-discovery $P -I $1 2>/tmp/ppp-errors | \
grep AC | wc -l)
  echo $R > /tmp/probe-finished ) &
WAIT=0



I found that the '-A' parameter is used in the current git master
branch, so this should affect more recent versions also.

2) In the bullseye installer, running ppp-udeb breaks with error messages for
missing libraries: libsystemd0, liblzma5 and libz4-1. I have
copied the entries for that libraries out of
'/dists/bullseye/main/debian-installer/binary-amd64/Packages.gz'
into
'/dists/bullseye/main/binary-amd64/Packages.gz',
which works fine for me, but I think there is a more elegant way
to do that. (But I'm not familiar to that. I also think that these libraries
are not needed to establish a PPPoE-connection.)

With this two fixes I got it working on my Bullseye USB Installer stick and I
have tested on BIOS and UEFI Virtual and Physical machines, but I don't know a
better way to commit that to the Debian project.



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

Kernel: Linux 5.10.0-23-amd64 (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

Bug#1042842: [Pkg-xen-devel] Bug#1042842: Acknowledgement (network interface names wrong in domU (>10 interfaces))

[zithro]

On 02 Aug 2023 10:22, Valentin Kleibel wrote:

Hi,


the bug has been mentionned on #xen-devel, will keep you posted.


Thanks. I wasn't able to find such a report, could you link the archive 
or post the threads subject so i can find it?


#xen-devel is the IRC Xen channel. I just pinged them, I'll wait.
Depending on their answers, I'll post on the xen-devel mailing list.


Meanwhile, you may try to force the domU vif names with a letter


The sorting with letters doesn't work out as renaming the interface is a 
secondary step.

...
[53408.899507] vif vif-5-0 sort-a: renamed from vif5.0


Yeah I just tried with vifnames, no more luck, sorry.
Running "xenstore-ls /local/domain/DOMU_ID/device/vif" shows that vif10+ 
are sorted before vif10- (ie. vif1, vif10, vif11, vif2, ...).


Our current workaround is to edit the interface names in the domUs 
config to match the wrong sorting. And be extra careful that the domUs 
MACs match the ones we expect on that network.


Via udev (MAC matching) or /etc/network/interfaces ?
I ask because it may help others, while this gets resolved.


--
zithro / Cyril

Bug#1042081: nvidia-kernel-dkms: Nvidia driver fails to compile on kernel 6.4

[Tobias Frost]

Control: forwarded -1 
https://forums.developer.nvidia.com/t/error-compiling-with-recent-mainline-kernel-linux-6-4-rc1/252732
Control: tags -1 patch

Upstream discussion, links a potential patch (not tested, but confirmed in the 
thread linked in the forwarded thread):

https://gist.github.com/joanbm/77f0650d45747b9a4dc8e330ade2bf5c

Bug#1042880: systemd: service with PrivateNetwork=yes fails to start inside a lxc container

[Simon McVittie]

Package: systemd
Version: 254-1
Severity: normal
X-Debbugs-Cc: l...@packages.debian.org

The PrivateNetwork=yes option hardens services by putting them in a private
network namespace.

systemd.exec(5) says:
> Note that the implementation of this setting might be impossible (for
> example if network namespaces are not available), and the unit should be
> written in a way that does not solely rely on this setting for security.

which makes me think that the intended behaviour of this option is: if
possible, put the service in a private network namespace, but if that's
not possible, then launch it anyway.

However, in a lxc container, this isn't working for me, causing
autopkgtest failure for policykit-1 (>= 123) (which I'm going to work
around by removing the PrivateNetwork=yes option for now). This is
important because ci.debian.net can currently only test packages in an
lxc container.

Steps to reproduce
==

On a Debian 12 'bookworm' system (I used a throwaway VM created by
autopkgtest-build-qemu to get a somewhat reproducible environment):

# apt install ca-certificates debootstrap libpam-cgfs lxcfs lxc-templates \
  rsync uidmap autopkgtest
# autopkgtest-build-lxc debian trixie amd64
# lxc-start autopkgtest-trixie-amd64
# lxc-attach autopkgtest-trixie-amd64
root@autopkgtest-trixie-amd64:~# cat > /lib/systemd/system/test.service <

Versions of packages systemd suggests:
ii  libfido2-11.13.0-1
pn  libqrencode4  
pn  libtss2-esys-3.0.2-0  
pn  libtss2-mu0   
pn  libtss2-rc0   
pn  polkitd   
ii  python3   3.11.4-5
pn  python3-pefile
pn  systemd-boot  
pn  systemd-container 
pn  systemd-homed 
pn  systemd-resolved  
pn  systemd-userdbd   

Versions of packages systemd is related to:
ii  dbus-user-session  1.14.8-2
pn  dracut 
pn  initramfs-tools
pn  libnss-systemd 
ii  libpam-systemd 254-1
pn  udev   

-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "C.UTF-8",
LANG = "en_GB.utf8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

Bug#1042725: qgis-providers: upgrade of qgis will create /.cache/crssync at the root of system

[Alexandre Detiste]

Thanks

> >- clean-up existing systems.
> >  "find /.cache -type -d -empty -delete" should be harmless.
>
> That we won't.

That's ok, users with some kind of serious OCD about 3 wasted
inodes will find the answer in this bug report.
(which is linked from cruft output)

Greetings

Bug#1037579: still ftbfs on arm64, armhf at least

[Matthias Klose]

Control: reopen -1
Control: found -1 20.08-13

still ftbfs on arm64 and armhf at least

Bug#1042867: debmirror: add option to URL-encode paths when fetching packages using http to support repos in AWS S3

[Colin Watson]

On Tue, Aug 01, 2023 at 05:32:59PM -0700, Richard Landster wrote:
> When using debmirror to mirror from a package repository hosted in an AWS
> S3 bucket debmirror fails to fetch files containing characters that have a
> plus sign ("+") as AWS S3 expects such fetches to use a URL-encoded path,
> but debmirror does not do any URL-encoding.
> 
> Please add a command-line option that turns on URL-encoding when fetching
> packages using http or https.

Is there any particular reason this needs to be an option, rather than
simply correcting the HTTP client implementation?

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#970749: Please update nautilus-dropbox to 2022.12.05

[Amr Ibrahim]

Hello,

Please update nautilus-dropbox to 2022.12.05. It supports nautilus 43+ & gtk4.

https://github.com/dropbox/nautilus-dropbox/blob/master/ChangeLog

Version 2022.12.05
--
* Update to use libnautilus-extension-4 and gtk4, supporting Nautilus 43+.
* Fix various uses of deprecated APIs, such as the "DeprecationWarning: isSet()
is deprecated" warning.
* Fix colors of ignored files in `dropbox filestatus`.
* Remove the long-broken `dropbox puburl` command.
* Don't print a ticker to stderr if it's not a tty.

Version 2020.03.04
--
* Coerce XDG_CURRENT_DESKTOP to "Unity". This works around the dropbox binary
that will only activate the indicator icon and menu on Ubuntu Unity < 16.10.
This patch coerces XDG_CURRENT_DESKTOP to report as "Unity" for the budgie-
desktop
https://bugs.launchpad.net/ubuntu/+source/nautilus-dropbox/+bug/1683051


Best,
Amr

Bug#1041537: python3 platlib points again to /usr/local

[Enrico Zini]

On Tue, Aug 01, 2023 at 11:23:43PM +0300, Jussi Pakkanen wrote:
> On Fri, 21 Jul 2023 at 14:09, Jeremy Bícha  wrote:
> 
> > We have been working around this in several Debian packages by setting
> > this in debian/rules:
> > export DEB_PYTHON_INSTALL_LAYOUT = deb
> 
> I'm confused. Why is this not set by default when building packages?
> FWICT this is a custom patch in Debian to make Python use deb paths.In
> this case Meson is doing exactly what you ask it to do, which is to
> use local paths because that environment variable is not set to `deb`.

It will, though it's not there yet.

See the thread starting from
https://lists.debian.org/debian-devel/2023/07/msg00307.html
and see 
https://salsa.debian.org/python-team/tools/dh-python/-/commit/fe7912b8ff386cf21478f2cd7f055b2a8665fdd4

Enrico

-- 
GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini 

Bug#1042842: Acknowledgement (network interface names wrong in domU (>10 interfaces))

[Valentin Kleibel]

Hi,


the bug has been mentionned on #xen-devel, will keep you posted.


Thanks. I wasn't able to find such a report, could you link the archive 
or post the threads subject so i can find it?



Meanwhile, you may try to force the domU vif names with a letter


The sorting with letters doesn't work out as renaming the interface is a 
secondary step.


...
[53408.899507] vif vif-5-0 sort-a: renamed from vif5.0
...

Our current workaround is to edit the interface names in the domUs 
config to match the wrong sorting. And be extra careful that the domUs 
MACs match the ones we expect on that network.


Valentin

Bug#1042005: transition: mumps hypre2.28.0 superlu combblas

[Drew Parsons]

On 2023-07-31 21:30, Sebastian Ramacher wrote:


combblas:  1.16.0 → 2.0.0
superlu:5 → 6
hypre: 2.26.0 → 2.28.0
mumps:5.5 → 5.6


Please go ahead.


combblas and superlu are loaded.

Probably best to run the rebuild of superlu-dist against combblas
before uploading the new hypre.

Drew

Bug#1042026: dlt-daemon: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2

[Gianfranco Costamagna]

control: tags -1 unreproducible
control: severity -1 normal

Hello, this might be a flaky test, I can't reproduce...

G.

On Tue, 25 Jul 2023 22:53:28 +0200 Lucas Nussbaum  wrote:

Source: dlt-daemon
Version: 2.18.9-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230724 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process --verbose -j8
> UpdateCTestConfiguration  from 
:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> UpdateCTestConfiguration  from 
:/<>/obj-x86_64-linux-gnu/DartConfiguration.tcl
> Test project /<>/obj-x86_64-linux-gnu
> Constructing a list of tests
> Done constructing a list of tests
> Updating test list for fixtures
> Added 0 tests to meet fixture requirements
> Checking test dependency graph...
> Checking test dependency graph end
> test 1
> Start 1: gtest_dlt_common
> 
> 1: Test command: /<>/obj-x86_64-linux-gnu/tests/gtest_dlt_common

> 1: Working Directory: /<>/obj-x86_64-linux-gnu/tests
> 1: Test timeout computed to be: 1000
> test 2
> Start 2: gtest_dlt_user
> 
> 2: Test command: /<>/obj-x86_64-linux-gnu/tests/gtest_dlt_user

> 2: Working Directory: /<>/obj-x86_64-linux-gnu/tests
> 2: Test timeout computed to be: 1000
> test 3
> Start 3: gtest_dlt_daemon_common
> 
> 3: Test command: /<>/obj-x86_64-linux-gnu/tests/gtest_dlt_daemon_common

> 3: Working Directory: /<>/obj-x86_64-linux-gnu/tests
> 3: Test timeout computed to be: 1000
> test 4
> Start 4: dlt_env_ll_unit_test
> 
> 4: Test command: /<>/obj-x86_64-linux-gnu/tests/dlt_env_ll_unit_test

> 4: Working Directory: /<>/obj-x86_64-linux-gnu/tests
> 4: Test timeout computed to be: 1000
> test 5
> Start 5: gtest_dlt_daemon_gateway
> 
> 5: Test command: /bin/sh "gtest_dlt_daemon_gateway.sh" "gtest_dlt_daemon_gateway"

> 5: Working Directory: /<>/obj-x86_64-linux-gnu/tests
> 5: Test timeout computed to be: 1000
> test 6
> Start 6: gtest_dlt_daemon_offline_log
> 

Bug#1042879: emacs-gtk: warnings when starting Emacs

[Vincent Lefevre]

Package: emacs-gtk
Version: 1:29.1+1-2
Severity: normal

When starting Emacs, I got the following annoying warnings:

 ■  Warning (comp): debian-ispell.el:420:16: Warning: reference to free 
variable ‘ispell-program-name’
 ■  Warning (comp): debian-ispell.el:427:16: Warning: reference to free 
variable ‘ispell-dictionary’
 ■  Warning (comp): debian-ispell.el:429:11: Warning: assignment to free 
variable ‘ispell-base-dicts-override-alist’
 ■  Warning (comp): debian-ispell.el:437:24: Warning: reference to free 
variable ‘ispell-base-dicts-override-alist’
 ■  Warning (comp): debian-ispell.el:475:9: Warning: reference to free variable 
‘ispell-dictionary’
 ■  Warning (comp): debian-ispell.el:489:18: Warning: reference to free 
variable ‘ispell-program-name’
 ■  Warning (comp): mmm-vars.el:869:2: Warning: defvar `mmm-classes-alist' 
docstring has wrong usage of unescaped single quotes (use \= or different 
quoting)
 ■  Warning (comp): mmm-auto.el:168:2: Warning: docstring has wrong usage of 
unescaped single quotes (use \= or different quoting)

This can be reproduced after removing the .emacs.d directory
(one needs to wait a bit).

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.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 emacs-gtk depends on:
ii  emacs-bin-common 1:29.1+1-2
ii  emacs-common 1:29.1+1-2
ii  libacl1  2.3.1-3
ii  libasound2   1.2.9-1
ii  libc62.37-6
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.8-2
ii  libfontconfig1   2.14.1-4
ii  libfreetype6 2.13.0+dfsg-1
ii  libgccjit0   13.2.0-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgif7  5.2.1-2.5
ii  libglib2.0-0 2.76.4-4
ii  libgmp10 2:6.3.0+dfsg-2
ii  libgnutls30  3.7.9-2
ii  libgpm2  1.20.7-10+b1
ii  libgtk-3-0   3.24.38-2
ii  libharfbuzz0b8.0.1-1
ii  libice6  2:1.0.10-1
ii  libjansson4  2.14-2
ii  libjpeg62-turbo  1:2.1.5-2
ii  liblcms2-2   2.14-2
ii  libm17n-01.8.2-1
ii  libotf1  0.9.16-4
ii  libpango-1.0-0   1.50.14+ds-1
ii  libpng16-16  1.6.40-1
ii  librsvg2-2   2.54.7+dfsg-1
ii  libselinux1  3.5-1
ii  libsm6   2:1.2.3-1
ii  libsqlite3-0 3.42.0-1
ii  libsystemd0  254~rc2-3
ii  libtiff6 4.5.1+git230720-1
ii  libtinfo66.4+20230625-2
ii  libtree-sitter0  0.20.8-2
ii  libwebp7 1.2.4-0.2
ii  libwebpdemux21.2.4-0.2
ii  libx11-6 2:1.8.6-1
ii  libxcomposite1   1:0.4.5-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxi6   2:1.8-1+b1
ii  libxinerama1 2:1.1.4-3
ii  libxml2  2.9.14+dfsg-1.3
ii  libxrandr2   2:1.5.2-2+b1
ii  libxrender1  1:0.9.10-1.1
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages emacs-gtk recommends:
ii  fonts-noto-color-emoji  2.038-1

Versions of packages emacs-gtk suggests:
ii  emacs-common-non-dfsg  1:29.1+1-1

-- no debconf information

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

Bug#1042878: FTBFS: on all architectures

[Picca Frédéric-Emmanuel]

Source: epics-base
Severity: important

Dear Maintainer,

please fix these FTBFS

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

Kernel: Linux 6.4.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, 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

Bug#1042775: r-cran-stringi: fails being loaded in R

[Martin Weiser]

Dne 02. 08. 23 v 8:50 Andreas Tille napsal(a):

Control: tags -1 unreproducible

Am Mon, Jul 31, 2023 at 08:16:25PM +0200 schrieb Martin Weiser:

Error: package or namespace load failed for ‘stringi’ in dyn.load(file, DLLpath 
= DLLpath, ...):
  unable to load shared object 
'/usr/local/lib/R/site-library/stringi/libs/stringi.so':

   ^

are you sure you are loading the Debian packaged stringi?

Kind regards
 Andreas.


Dear Andreas,

I am really sorry for wasting your time.

With sincere apologies,

Martin
--
Please expect long response time (3d+) - this is because of family reasons

Bug#1041204: dhcpcd-base: dhcpcd -T wlp3s0 produces Segmentation fault

[Ingo Wichmann]

forwarded 1041204 https://github.com/NetworkConfiguration/dhcpcd/issues/235

Bug#1042877: rust-image: Please update to v0.24.4

[Jonas Smedegaard]

Source: rust-image
Version: 0.24.3-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to (at least) newer upstream release v0.24.4.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTKCP8ACgkQLHwxRsGg
ASGOLQ//a0qTNDIzIj5MrYBUzawaYmV9Hapxf+WAVqQO6aD8XyOhgw6wzH4jGzmA
C+oIYvoZey13JIRl2ScFPPCyHljXkXJAKKmRAeO8pxkWZOSreWScF2/QMLCbwmuN
sZONephnXouOolWxxLZ8trCv2eghWDD04V5omfc4B5GCqcQhobtWOjioBGqoVlSz
GBdubkTG3DQBW9O+KQcxj7p5ygbmcdt/jo69J+hNzFPwW4F9a0dZ8ubE4JqQVdgi
HfpVf1GN4EviZJZCziEGG3FDFYbOt/U4ERFDmXOoUloE0pSj6mDAW7Jhjjg2jrhZ
2SFg7ONvfnWmh5VEuED52SHLpT+pTZu+VrhuOQT4yIalmIe69Hu8es9SE6rq1pbK
vJJPatz5CVVG2XdHFvNJ8pbmHSZNjrY2q1o92rR7fzOc7HnCOdycn49E7klUxrl8
XFYhLrNZvhAVi6nwhdkLM+yBFPLWSj4b8fIuQOshh1lp+vp0iy+pjDOXa9gqJMPb
1e/L81umsMaDBirg6KeTRBT6oAS7BUN+56flYW9OR6X8zE1KH8HMkh64X2Bqm4rd
+VpRGr5TFN8BeFTrTvWs4328xYRRC8yJ39hfuQTzGIl6p/IsA7qImVN/La99HWSk
5sdyKE4dqj/HRitji1WGjmK6kO4L7wnWgkmQffg8KByX9pp4rNE=
=OYiI
-END PGP SIGNATURE-

Bug#1041202: flang-16: flang fails to compile: missing libraries

[Gianfranco Costamagna]

I uploaded a partial fix, now you can do it with
flang-new-16 hello.f90 -o hello -L /usr/lib/llvm-16/lib/

We need probably newer llvm-defaults to symlink them into a more common 
directory to avoid -L switch.
G.

On Sat, 15 Jul 2023 16:50:15 +0100 Alastair McKinstry  
wrote:

Package: flang-16
Version: 16.0.6-4
Severity: normal

flang-new fails to compile a hello world program:

alastair@debian:/tmp$ flang-new-16 -o foo hello.f90
/usr/bin/ld: cannot find -lFortran_main: No such file or directory
/usr/bin/ld: cannot find -lFortranRuntime: No such file or directory
/usr/bin/ld: cannot find -lFortranDecimal: No such file or directory
flang-new: error: linker command failed with exit code 1 (use -v to see 
invocation)

regards
Alastair



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

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




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1042466: AttributeError: module 'eventlet.green.select' has no attribute 'epoll'

[Gregor Riepl]

Here's a temporary workaround until the issue is fixed.

Either set the environment variable EVENTLET_NO_GREENDNS to "yes" before 
launching applications that import eventlet, or put the following Python 
code before loading the module:


import os
os.environ['EVENTLET_NO_GREENDNS'] = 'yes'
import eventlet
...

Bug#1042876: RFS: git-credential-azure/0.1.0-1 [ITP] -- Git credential helper for Azure Repos (program)

[M Hickford]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "git-credential-azure":

 * Package name : git-credential-azure
   Version  : 0.1.0-1
   Upstream contact : M Hickford 
 * URL  : https://github.com/hickford/git-credential-azure
 * License  : Apache-2.0
 * Vcs  :
https://salsa.debian.org/go-team/packages/git-credential-azure  (if
you have permissions, please change the default branch in settings to
debian/sid)
   Section  : golang

The source builds the following binary packages:

  git-credential-azure - Git credential helper for Azure Repos (program)

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

  https://mentors.debian.net/package/git-credential-azure/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/g/git-credential-azure/git-credential-azure_0.1.0-1.dsc

Changes for the initial release:

 git-credential-azure (0.1.0-1) unstable; urgency=medium
 .
   * Initial release (Closes: #1042861)

Regards,

Bug#1042775: r-cran-stringi: fails being loaded in R

[Andreas Tille]

Control: tags -1 unreproducible

Am Mon, Jul 31, 2023 at 08:16:25PM +0200 schrieb Martin Weiser:
> Error: package or namespace load failed for ‘stringi’ in dyn.load(file, 
> DLLpath = DLLpath, ...):
>  unable to load shared object 
> '/usr/local/lib/R/site-library/stringi/libs/stringi.so':
  ^

are you sure you are loading the Debian packaged stringi?

Kind regards
Andreas.

-- 
http://fam-tille.de

Bug#1042875: cron-apt: man cron-apt mentions a configuration example file without any configuration

[Carles Pina i Estany]

Package: cron-apt
Version: 0.13.0+nmu1
Severity: minor

Dear Maintainer,

I've tested this in cron-apt versions 0.13.0.1 (Bookworm) and
0.13.0+nmu1 (Bullseye).

I was trying to change some configuration and did: man cron-apt

It says (under "CONFIGURATION"):
"""
The  variables  that you can set in /etc/cron-apt/config is documented
in the configuration example in /usr/share/doc/cron-apt/examples/config
"""

The file /usr/share/doc/cron-apt/examples/config does not contain any
example but two lines:
"""
# Configuration for cron-apt. For further information about the possible
# configuration settings see /usr/share/doc/cron-apt/README.gz.
"""

I would suggest that the "man" should mention
/usr/share/doc/cron-apt/README.gz straight away.

Also, I think that reads better ".../etc/cron-apt/config are documented in
the..." (change is to are).

Thanks for cron-apt! I use it in quite a few systems for a long time and
I'm really happy with it.

Thank very much!


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


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

Kernel: Linux 5.10.0-23-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.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 cron-apt depends on:
ii  apt  2.2.4

Versions of packages cron-apt recommends:
ii  cron [cron-daemon]  3.0pl1-137
ii  liblockfile11.17-1+b1
ii  postfix [mail-transport-agent]  3.5.18-0+deb11u1

cron-apt suggests no packages.

-- Configuration Files:
/etc/cron-apt/action.d/3-download changed [not included]
/etc/cron-apt/config changed [not included]
/etc/cron.d/cron-apt changed [not included]

-- no debconf information

Bug#1042874: Acknowledgement (auctex: )

[Janusz S . Bień]

On Wed, Aug 02 2023 at  6:09 GMT, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1042874: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042874.

There was an encoding problem with quoting the error message, so I
enclosed it in the attachment.

Regards - Janusz

LaTeX-label: Wrong type argument: symbolp, #[128 "ÀÁ\"‡" [apply reftex-label 
reftex-label nil] 4 nil nil]


-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien