Bug#992269: texlive-bibtex-extra: Missing beebe bst stiles like abstract.bst

[Preuße]

On 14.06.2023 21:33, Simone Piccardi wrote:

Hi,


I could find the file in CTAN, is here:

http://tug.ctan.org/tex-archive/biblio/bibtex/contrib/misc/abstract.bst

>
Interesting: the Firefox Browser always redirects to HTTPS and the 
reports an 404.


hille@sid-amd64:~$ wget 
http://tug.ctan.org/tex-archive/biblio/bibtex/contrib/misc/abstract.bst


HTTP request sent, awaiting response... 200 OK
Length: 24061 (23K) [text/plain]
Saving to: ‘abstract.bst’

abstract.bst100%[===>]  23.50K  --.-KB/sin 0s

2023-06-15 07:45:44 (54.2 MB/s) - ‘abstract.bst’ saved [24061/24061]

hille@sid-amd64:~$ wget 
https://tug.ctan.org/tex-archive/biblio/bibtex/contrib/misc/abstract.bst


HTTP request sent, awaiting response... 404 Not Found
2023-06-15 07:45:49 ERROR 404: Not Found.

Hilmar

--
sigfault



OpenPGP_0x0C871C4C653C1F59.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037978: openjdk-19: Please update patch for m68k support

[John Paul Adrian Glaubitz]

Source: openjdk-19
Version: 19.0.2+7-1
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: m68k
X-Debbugs-Cc: debian-...@lists.debian.org

Hello!

The patch for adding m68k support in the OpenJDK package needs to be updated
since the path for the file sizes-32-linux.txt was changed with OpenJDK 19
which is why we need to move the m68k version sizes-32-linux-m68k.txt as well.

I have done that for the patch m68k-support.diff, so the patch just needs to
be updated in debian/patches to fix the FTBFS of openjdk-19 and newer on m68k.

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
Subject: Fix alignment issues on m68k
Author: John Paul Adrian Glaubitz 
Last Update: 2023-06-14

Index: 
openjdk-19-19.0.2+7/make/modules/java.desktop/gensrc/GensrcX11Wrappers.gmk
===
--- 
openjdk-19-19.0.2+7.orig/make/modules/java.desktop/gensrc/GensrcX11Wrappers.gmk
+++ openjdk-19-19.0.2+7/make/modules/java.desktop/gensrc/GensrcX11Wrappers.gmk
@@ -29,9 +29,14 @@
 # Put the generated Java classes used to interface X11 from awt here.
 GENSRC_X11WRAPPERS_OUTPUTDIR := 
$(SUPPORT_OUTPUTDIR)/gensrc/java.desktop/sun/awt/X11
 
+GENSRC_X11_VERSION_VARIANT :=
+ifeq ($(OPENJDK_TARGET_OS)-$(OPENJDK_TARGET_CPU), linux-m68k)
+  GENSRC_X11_VERSION_VARIANT := -linux-m68k
+endif
+
 # The pre-calculated offset file are stored here:
 GENSRC_X11WRAPPERS_DATADIR := $(MODULE_SRC)/unix/data/x11wrappergen
-GENSRC_X11WRAPPERS_DATA := 
$(GENSRC_X11WRAPPERS_DATADIR)/sizes-$(OPENJDK_TARGET_CPU_BITS).txt
+GENSRC_X11WRAPPERS_DATA := 
$(GENSRC_X11WRAPPERS_DATADIR)/sizes-$(OPENJDK_TARGET_CPU_BITS)$(GENSRC_X11_VERSION_VARIANT).txt
 
 # Run the tool on the offset files to generate several Java classes used in 
awt.
 $(eval $(call SetupExecute, gen_x11wrappers, \
Index: openjdk-19-19.0.2+7/src/hotspot/share/memory/allocation.hpp
===
--- openjdk-19-19.0.2+7.orig/src/hotspot/share/memory/allocation.hpp
+++ openjdk-19-19.0.2+7/src/hotspot/share/memory/allocation.hpp
@@ -232,7 +232,7 @@ template  class CHeapObj ALL
 
   void  operator delete(void* p) { FreeHeap(p); }
   void  operator delete [] (void* p) { FreeHeap(p); }
-};
+} __attribute__ ((aligned (4)));
 
 // Base class for objects allocated on the stack only.
 // Calling new or delete will result in fatal error.
@@ -243,7 +243,7 @@ class StackObj ALLOCATION_SUPER_CLASS_SP
   void* operator new [](size_t size) throw();
   void  operator delete(void* p);
   void  operator delete [](void* p);
-};
+} __attribute__ ((aligned (4)));
 
 // Base class for objects stored in Metaspace.
 // Calling delete will result in fatal error.
@@ -365,7 +365,7 @@ class MetaspaceObj {
   // that should be read-only by default. See symbol.hpp for an example. This 
function
   // is used by the templates in metaspaceClosure.hpp
   static bool is_read_only_by_default() { return false; }
-};
+} __attribute__ ((aligned (4)));
 
 // Base class for classes that constitute name spaces.
 
@@ -438,7 +438,7 @@ protected:
   void* operator new [](size_t size, const std::nothrow_t& nothrow_constant) 
throw() = delete;
   void  operator delete(void* p);
   void  operator delete [](void* p) = delete;
-};
+} __attribute__ ((aligned (4)));
 
 // One of the following macros must be used when allocating an array
 // or object to determine whether it should reside in the C heap on in
Index: openjdk-19-19.0.2+7/src/hotspot/share/oops/constMethod.hpp
===
--- openjdk-19-19.0.2+7.orig/src/hotspot/share/oops/constMethod.hpp
+++ openjdk-19-19.0.2+7/src/hotspot/share/oops/constMethod.hpp
@@ -530,6 +530,6 @@ private:
 
   // Verify
   void verify_on(outputStream* st);
-};
+} __attribute__ ((aligned (4)));
 
 #endif // SHARE_OOPS_CONSTMETHOD_HPP
Index: openjdk-19-19.0.2+7/src/hotspot/share/oops/oop.hpp
===
--- openjdk-19-19.0.2+7.orig/src/hotspot/share/oops/oop.hpp
+++ openjdk-19-19.0.2+7/src/hotspot/share/oops/oop.hpp
@@ -315,7 +315,7 @@ class oopDesc {
   static void* load_oop_raw(oop obj, int offset);
 
   DEBUG_ONLY(bool size_might_change();)
-};
+} __attribute__ ((aligned (4)));
 
 // An oopDesc is not initialized via a constructor.  Space is allocated in
 // the Java heap, and static functions provided here on HeapWord* are used
Index: 
openjdk-19-19.0.2+7/src/java.desktop/unix/data/x11wrappergen/sizes-32-linux-m68k.txt
===
--- /dev/null
+++ 
openjdk-19-19.0.2+7/src/java.desktop/unix/data/x11wrappergen/sizes-32-linux-m68k.txt
@@ -0,0 +1,1017 @@
+long   4
+int4
+short  2
+ptr4
+Bool   4
+Atom   4
+Window 4
+XExtData.number0
+XExtData.next  4
+XExtData.free_private  8
+XExtData.private_data  12

Bug#1037542: bookworm-pu: package xerial-sqlite-jdbc/3.40.1.0+dfsg-1+deb12u1

[Salvatore Bonaccorso]

Hi Pierre,

On Wed, Jun 14, 2023 at 12:01:18AM +0200, Pierre Gruet wrote:
> Package: release.debian.org
> Severity: normal
> Tags: bookworm
> User: release.debian@packages.debian.org
> Usertags: pu
> X-Debbugs-Cc: xerial-sqlite-j...@packages.debian.org
> Control: affects -1 + src:xerial-sqlite-jdbc
> 
> Dear Release team,
> 
> I would like to upload xerial-sqlite-jdbc to stable-proposed-updates.
> 
> [ Reason ]
> Grave bug #1036706 has been filled a few days before the release of Bookworm.
> This is a security bug associated to CVE-2023-32697. Although it has been
> marked no-dsa by the security team, we exchanged a few emails and our
> conclusion was the fix of this bug, which amounts to cherry-pick one commit of
> upstream, should land in Bookworm during a point release.
> 
> [ Impact ]
> CVE-2023-32697 would remain. The Debian-packaged reverse dependencies of the
> package are mainly used in a single-user environment, but possibly it is also
> used in a network environment by some users for their own programs, and this 
> is
> where there might be some hazard.
> 
> [ Tests ]
> The package was built in a Bookworm chroot and its autopkgtest is passing.
> 
> [ Risks ]
> Code is very simple, only 2 lines are changed. Upstream has published it
> three weeks ago and it has issued new upstream versions since then.
> 
> [ Checklist ]
>   [X] *all* changes are documented in the d/changelog
>   [X] I reviewed all changes and I approve them
>   [X] attach debdiff against the package in (old)stable
>   [X] the issue is verified as fixed in unstable
> 
> [ Changes ]
> Cherry-picking commit edb4b8adc2447bc04e05b9b908195a4bc7926242 from upstream,
> which uses a random UUID instead of the hash of some fixed address in order to
> define the DB file name.
> 
> 
> 
> Thanks for your help,
> 
> Best,
> 
> -- 
> Pierre

> diff -Nru xerial-sqlite-jdbc-3.40.1.0+dfsg/debian/changelog 
> xerial-sqlite-jdbc-3.40.1.0+dfsg/debian/changelog
> --- xerial-sqlite-jdbc-3.40.1.0+dfsg/debian/changelog 2023-02-04 
> 14:24:45.0 +0100
> +++ xerial-sqlite-jdbc-3.40.1.0+dfsg/debian/changelog 2023-06-13 
> 23:19:59.0 +0200
> @@ -1,3 +1,9 @@
> +xerial-sqlite-jdbc (3.40.1.0+dfsg-1+deb12u1) bookworm; urgency=medium
> +
> +  * Using a random UUID for the connection (Fixes CVE-2023-32697 in Bookworm)
> +
> + -- Pierre Gruet   Tue, 13 Jun 2023 23:19:59 +0200

Can you as well add the Debian bug closer for #1036706 here?

Regards,
Salvatore

Bug#1037444: bookworm-pu: package kanboard/1.2.26+ds-4

[Salvatore Bonaccorso]

Hi Joseph,

[disclaimer, not a release team member but I believe can give input on
the debdiff below]

On Mon, Jun 12, 2023 at 08:19:55PM -0400, Joseph Nahmias wrote:
> Package: release.debian.org
> Severity: normal
> Tags: bookworm
> User: release.debian@packages.debian.org
> Usertags: pu
> X-Debbugs-Cc: kanbo...@packages.debian.org, j...@nahmias.net
> Control: affects -1 + src:kanboard
> 
> [ Reason ]
> Security updates for kanboard since v1.2.26.
> 
> [ Tests ]
> upstream's unit test suite are run at build time and via autopkgtest.
> there are also some other (superficial) autopkgtests.
> 
> [ Risks ]
> All listed CVEs have targeted fixes picked from upstream github.
> 
> [ Checklist ]
>   [X] *all* changes are documented in the d/changelog
>   [X] I reviewed all changes and I approve them
>   [X] attach debdiff against the package in (old)stable
>   [X] the issue is verified as fixed in unstable
> 
> [ Other info ]
> 
> My first stable update, so please advise if I missed anything.
> --Joe

> diff -Nru kanboard-1.2.26+ds/debian/changelog 
> kanboard-1.2.26+ds/debian/changelog
> --- kanboard-1.2.26+ds/debian/changelog   2023-05-16 22:49:38.0 
> -0400
> +++ kanboard-1.2.26+ds/debian/changelog   2023-06-07 20:45:40.0 
> -0400
> @@ -1,3 +1,24 @@
> +kanboard (1.2.26+ds-4) unstable; urgency=medium
> +
> +  * backport security fixes from kanboard v1.2.30
> + > CVE-2023-33956: Parameter based Indirect Object Referencing leading
> +   to private file exposure
> + > CVE-2023-33968: Missing access control allows user to move and
> +   duplicate tasks to any project in the software
> + > CVE-2023-33969: Stored XSS in the Task External Link Functionality
> + > CVE-2023-33970: Missing access control in internal task links feature
> +(Closes: #1037167)
> +
> + -- Joseph Nahmias   Wed, 07 Jun 2023 20:45:40 -0400
> +
> +kanboard (1.2.26+ds-3) unstable; urgency=medium
> +
> +  * backport fix for CVE-2023-32685 from kanboard v1.2.29
> +
> https://github.com/kanboard/kanboard/security/advisories/GHSA-hjmw-gm82-r4gv
> +Based on upstream commits 26b6eeb & c9c1872. (Closes: #1036874)
> +
> + -- Joseph Nahmias   Sun, 28 May 2023 21:42:46 -0400

This seems to be the current debdiff between bookworm and the unstable
version. But now that bookworm is releases, a package does nto migrate
anymore from there to stable. What is needed above is to apply the
needed patches on top of the 1.2.26+ds-2 versiion in testing and
version it such that it is 1.2.26+ds-2+deb12u1.

The developers-reference has some additional hints:
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions

Hope this helps,
Regards,
Salvatore

Bug#1037966: bind9: Unable to restart bind9 via systemctl when using chroot on Debian 12

[Marc Haber]

On Thu, Jun 15, 2023 at 06:36:10AM +0200, Ondřej Surý wrote:
> Your chroot is missing the sd_notify socket. The package can’t really expect 
> all non-default configurations. I can probably add a NEWS.Debian entry for 
> this, but it’s certainly not important severity.

Maybe it would also be a good idea to document how to get that socket
into the chroot. Not everybody will know how to do this. #867187 seems
to have a solution for unbound, maybe this one can at least be an
example in the bind9 packages?

Greetings
Marc

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

Bug#1037977: rust-ureq - update for base64 0.21

[Peter Green]

Package: rust-ureq
Version: 2.6.2-3
Severity: serious
Tags: trixie, sid, patch, ftbfs

rust-base64 was recently updated to 0.21 making rust-ureq unbuildable and 
uninstallable.

Upstream already has a fix, I grabbed it and added it to the Debian package and 
it
built and passed autopkgtests fine.

Debdiff attached, I may or may not NMU this later.diff -Nru rust-ureq-2.6.2/debian/changelog rust-ureq-2.6.2/debian/changelog
--- rust-ureq-2.6.2/debian/changelog2023-02-12 16:16:54.0 +
+++ rust-ureq-2.6.2/debian/changelog2023-06-15 02:17:59.0 +
@@ -1,3 +1,10 @@
+rust-ureq (2.6.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply upstream patch for base64 0.21.
+
+ -- Peter Michael Green   Thu, 15 Jun 2023 02:17:59 +
+
 rust-ureq (2.6.2-3) unstable; urgency=medium
 
   * avoid initial dash in autopkgtest test name;
diff -Nru rust-ureq-2.6.2/debian/control rust-ureq-2.6.2/debian/control
--- rust-ureq-2.6.2/debian/control  2023-01-26 16:13:56.0 +
+++ rust-ureq-2.6.2/debian/control  2023-06-15 02:17:57.0 +
@@ -4,7 +4,7 @@
 Build-Depends:
  debhelper-compat (= 13),
  dh-cargo (>= 25),
- librust-base64-0.13+default-dev ,
+ librust-base64-0.21+default-dev ,
  librust-brotli-decompressor-2+default-dev ,
  librust-chunked-transfer-1+default-dev ,
  librust-cookie-0.16-dev ,
@@ -37,7 +37,7 @@
 Architecture: all
 Multi-Arch: foreign
 Depends:
- librust-base64-0.13+default-dev,
+ librust-base64-0.21+default-dev,
  librust-brotli-decompressor-2+default-dev,
  librust-chunked-transfer-1+default-dev,
  librust-cookie-0.16-dev,
diff -Nru rust-ureq-2.6.2/debian/patches/0001_base64.patch 
rust-ureq-2.6.2/debian/patches/0001_base64.patch
--- rust-ureq-2.6.2/debian/patches/0001_base64.patch1970-01-01 
00:00:00.0 +
+++ rust-ureq-2.6.2/debian/patches/0001_base64.patch2023-06-15 
02:16:54.0 +
@@ -0,0 +1,59 @@
+commit abda74c4d8d1235c6eddccafd3c4bd690dc10ea7
+Author: Martin Algesten 
+Date:   Mon Jan 30 23:39:55 2023 +0100
+
+Upgrade deps
+
+diff --git a/Cargo.toml b/Cargo.toml
+index 00dc9f0ea..418ae582b 100644
+--- a/Cargo.toml
 b/Cargo.toml
+@@ -26,7 +26,7 @@ gzip = ["flate2"]
+ brotli = ["brotli-decompressor"]
+ 
+ [dependencies]
+-base64 = "0.13"
++base64 = "0.21"
+ cookie = { version = "0.16", default-features = false, optional = true}
+ once_cell = "1"
+ url = "2"
+diff --git a/src/proxy.rs b/src/proxy.rs
+index ff9413917..0148904a1 100644
+--- a/src/proxy.rs
 b/src/proxy.rs
+@@ -1,3 +1,5 @@
++use base64::{prelude::BASE64_STANDARD, Engine};
++
+ use crate::error::{Error, ErrorKind};
+ 
+ /// Proxy protocol
+@@ -131,7 +133,7 @@ impl Proxy {
+ 
+ pub(crate) fn connect>(, host: S, port: u16) -> String 
{
+ let authorization = if self.use_authorization() {
+-let creds = base64::encode(format!(
++let creds = BASE64_STANDARD.encode(format!(
+ "{}:{}",
+ self.user.clone().unwrap_or_default(),
+ self.password.clone().unwrap_or_default()
+diff --git a/src/unit.rs b/src/unit.rs
+index 895067ff0..2011bb673 100644
+--- a/src/unit.rs
 b/src/unit.rs
+@@ -3,6 +3,7 @@ use std::io::{self, Write};
+ use std::ops::Range;
+ use std::time;
+ 
++use base64::{prelude::BASE64_STANDARD, Engine};
+ use log::debug;
+ use url::Url;
+ 
+@@ -87,7 +88,7 @@ impl Unit {
+ if (!username.is_empty() || !password.is_empty())
+ && get_header(, "authorization").is_none()
+ {
+-let encoded = base64::encode(format!("{}:{}", username, 
password));
++let encoded = BASE64_STANDARD.encode(format!("{}:{}", 
username, password));
+ extra.push(Header::new("Authorization", !("Basic {}", 
encoded)));
+ }
+ 
diff -Nru rust-ureq-2.6.2/debian/patches/series 
rust-ureq-2.6.2/debian/patches/series
--- rust-ureq-2.6.2/debian/patches/series   2023-01-26 16:08:45.0 
+
+++ rust-ureq-2.6.2/debian/patches/series   2023-06-15 02:17:14.0 
+
@@ -1,3 +1,4 @@
+0001_base64.patch
 2001_native_certs.patch
 2002_env_logger.patch
 2003_cookie-store.patch

Bug#1037966: bind9: Unable to restart bind9 via systemctl when using chroot on Debian 12

[Ondřej Surý]

Control: severity -1 minor

Your chroot is missing the sd_notify socket. The package can’t really expect 
all non-default configurations. I can probably add a NEWS.Debian entry for 
this, but it’s certainly not important severity.

Ondrej
--
Ondřej Surý  (He/Him)

> On 14. 6. 2023, at 23:15, Bret Giddings  wrote:
> 
> Package: bind9
> Version: 1:9.18.12-1
> Severity: important
> 
> Dear Maintainer,
> 
> Whilst attempting to upgrade from debian 11 to 12, for my chroot named setup, 
> I
> found that running
> 
>systemctl restart named
> 
> would hang and eventually timeout. It should be noted that named is running 
> fine.
> 
> Having compared the differences from 11 to 12, I believe that this is caused
> by the latter unit file using a service type of notify rather than the default
> simple.
> 
> Creating an override with
> 
>[Service]
>Type=simple
> 
> restores the former behaviour. So, I believe that the notify option is unable
> to communicate with the chroot'ed environment. Whilst I can use the above
> as a workaround, I couldn't find anything in the changelog or elsewhere
> reporting this issue. I also tested and confirmed this behaviour on a new
> install of bind9 with minimal customisation. It only fails when you switch
> to using '-t /var/cache/bind' in /etc/defaults/named (having previously
> created the appropriate directories etc.
> 
> 
> -- 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/48 CPU threads; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages bind9 depends on:
> ii  adduser3.134
> ii  bind9-libs 1:9.18.12-1
> ii  bind9-utils1:9.18.12-1
> ii  debconf [debconf-2.0]  1.5.82
> ii  dns-root-data  2023010101
> ii  init-system-helpers1.65.2
> ii  iproute2   6.1.0-3
> ii  libc6  2.36-9
> ii  libcap21:2.66-4
> ii  libfstrm0  0.6.1-1
> ii  libjson-c5 0.16-2
> ii  liblmdb0   0.9.24-1
> ii  libmaxminddb0  1.7.1-1
> ii  libnghttp2-14  1.52.0-1
> ii  libprotobuf-c1 1.4.1-1+b1
> ii  libssl33.0.9-1
> ii  libsystemd0252.6-1
> ii  libuv1 1.44.2-1
> ii  libxml22.9.14+dfsg-1.2
> ii  netbase6.4
> ii  sysvinit-utils [lsb-base]  3.06-4
> ii  zlib1g 1:1.2.13.dfsg-1
> 
> bind9 recommends no packages.
> 
> Versions of packages bind9 suggests:
> pn  bind-doc   
> ii  bind9-dnsutils [dnsutils]  1:9.18.12-1
> pn  resolvconf 
> pn  ufw
> 
> -- Configuration Files:
> /etc/bind/db.0 [Errno 2] No such file or directory: '/etc/bind/db.0'
> /etc/bind/db.127 [Errno 2] No such file or directory: '/etc/bind/db.127'
> /etc/bind/db.255 [Errno 2] No such file or directory: '/etc/bind/db.255'
> /etc/bind/db.empty [Errno 2] No such file or directory: '/etc/bind/db.empty'
> /etc/bind/db.local [Errno 2] No such file or directory: '/etc/bind/db.local'
> /etc/bind/named.conf changed [not included]
> /etc/bind/named.conf.default-zones [Errno 2] No such file or directory: 
> '/etc/bind/named.conf.default-zones'
> /etc/bind/named.conf.local [Errno 2] No such file or directory: 
> '/etc/bind/named.conf.local'
> /etc/bind/named.conf.options [Errno 2] No such file or directory: 
> '/etc/bind/named.conf.options'
> /etc/bind/zones.rfc1918 [Errno 2] No such file or directory: 
> '/etc/bind/zones.rfc1918'
> /etc/default/named changed [not included]
> 
> -- no debconf information
> 

Bug#1037976: osmcoastline: FTFBS with GDAL 3.7.0

[Bas Couwenberg]

Source: osmcoastline
Version: 2.4.0-1
Severity: important
Tags: ftbfs upstream
User: debian-...@lists.debian.org
Usertags: gdal-3.7
Control: forwarded -1 https://github.com/osmcode/osmcoastline/issues/44

Dear Maintainer,

Your package FTFBS with GDAL 3.7.0 from experimental:

 [ 80%] Building CXX object 
src/CMakeFiles/osmcoastline.dir/coastline_polygons.cpp.o
 cd /build/osmcoastline-2.4.0/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
-DOSMIUM_WITH_LZ4 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-I/build/osmcoastline-2.4.0/include -isystem /usr/include/gdal -g -O2 
-ffile-prefix-map=/build/osmcoastline-2.4.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -g -DNDEBUG   
-std=c++14 -Wall -Wextra -pedantic -Wredundant-decls -Wdisabled-optimization 
-Wctor-dtor-privacy -Wnon-virtual-dtor -Woverloaded-virtual -Wsign-promo 
-Wold-style-cast -pthread -MD -MT 
src/CMakeFiles/osmcoastline.dir/coastline_polygons.cpp.o -MF 
CMakeFiles/osmcoastline.dir/coastline_polygons.cpp.o.d -o 
CMakeFiles/osmcoastline.dir/coastline_polygons.cpp.o -c 
/build/osmcoastline-2.4.0/src/coastline_polygons.cpp
 /build/osmcoastline-2.4.0/src/coastline_polygons.cpp: In member function 'void 
CoastlinePolygons::output_polygon_ring_as_lines(int, const OGRLinearRing*) 
const':
 /build/osmcoastline-2.4.0/src/coastline_polygons.cpp:285:82: error: invalid 
conversion from 'const OGRSpatialReference*' to 'OGRSpatialReference*' 
[-fpermissive]
   285 | add_line_to_output(std::move(new_line), 
ring->getSpatialReference());
   | 
~^~
   |
  |
   |
  const OGRSpatialReference*
 /build/osmcoastline-2.4.0/src/coastline_polygons.cpp:257:102: note:   
initializing argument 2 of 'void 
CoastlinePolygons::add_line_to_output(std::unique_ptr, 
OGRSpatialReference*) const'
   257 | void 
CoastlinePolygons::add_line_to_output(std::unique_ptr line, 
OGRSpatialReference* srs) const {
   |
 ~^~~
 /build/osmcoastline-2.4.0/src/coastline_polygons.cpp:294:70: error: invalid 
conversion from 'const OGRSpatialReference*' to 'OGRSpatialReference*' 
[-fpermissive]
   294 | add_line_to_output(std::move(line), 
ring->getSpatialReference());
   | ~^~
   |  |
   |  
const OGRSpatialReference*
 /build/osmcoastline-2.4.0/src/coastline_polygons.cpp:257:102: note:   
initializing argument 2 of 'void 
CoastlinePolygons::add_line_to_output(std::unique_ptr, 
OGRSpatialReference*) const'
   257 | void 
CoastlinePolygons::add_line_to_output(std::unique_ptr line, 
OGRSpatialReference* srs) const {
   |
 ~^~~
 make[3]: *** [src/CMakeFiles/osmcoastline.dir/build.make:121: 
src/CMakeFiles/osmcoastline.dir/coastline_polygons.cpp.o] Error 1

The full buildlog is attached.

Kind Regards,

Bas
dpkg-checkbuilddeps: error: Unmet build dependencies: libgdal-dev libgeos++-dev 
libosmium2-dev (>= 2.16.0) libgdalcpp-dev pandoc spatialite-bin
W: Unmet build-dependency in source
dh clean --buildsystem cmake
   dh_auto_clean -O--buildsystem=cmake
   dh_autoreconf_clean -O--buildsystem=cmake
   dh_clean -O--buildsystem=cmake
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building osmcoastline using existing 
./osmcoastline_2.4.0.orig.tar.gz
dpkg-source: info: building osmcoastline in osmcoastline_2.4.0-2.debian.tar.xz
dpkg-source: info: building osmcoastline in osmcoastline_2.4.0-2.dsc
I: Generating source changes file for original dsc
dpkg-genchanges: info: not including original source code in upload
I: Copying COW directory
I: forking: rm -rf /var/cache/pbuilder/build/cow.3606036
I: forking: cp -al /var/cache/pbuilder/base-sid+rebuild.cow 
/var/cache/pbuilder/build/cow.3606036
I: removed stale ilistfile /var/cache/pbuilder/build/cow.3606036/.ilist
I: forking: chroot /var/cache/pbuilder/build/cow.3606036 cowdancer-ilistcreate 
/.ilist 'find . -xdev -path ./home -prune -o \( \( -type l -o -type f \) -a 
-links +1 -print0 \) | xargs -0 stat --format '%d %i ''
I: Invoking pbuilder
I: forking: pbuilder build --debbuildopts  --debbuildopts  --buildplace 
/var/cache/pbuilder/build/cow.3606036 --buildresult /var/cache/pbuilder/result/ 
--mirror http://ftp.nl.debian.org/debian/ --distribution sid --no-targz 
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.3606036 cow-shell' 

Bug#1037975: manpages-ro-dev: incorrect short description: mentions Russian instead of Romanian

[Paul Wise]

Package: manpages-ro-dev
Version: 4.19.0-2
Severity: normal

The manpages-ro-dev package has an incorrect short description, it
mentions Russian instead of Romanian, while the long description
mentions Romanian, which seems correct based on the ro language code.

   Description: Russian development manpages
This package contains the Linux development manual pages
translated into Romanian.
   
-- System Information:
Debian Release: 12.0
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-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_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

manpages-ro-dev depends on no packages.

manpages-ro-dev recommends no packages.

Versions of packages manpages-ro-dev suggests:
pn  glibc-doc 
ii  man-db [man-browser]  2.11.2-2
ii  manpages-dev  6.03-2

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1037974: ddcci-dkms: code fails to build and package fails to install with Linux 6.3 headers

[Paul Wise]

Package: ddcci-dkms
Version: 0.4.2-4
Severity: serious

When I try to install ddcci-dkms with the Linux 6.3 headers installed,
the build of the code fails and then the install of the package fails.

I think there are two problems here:

 * The code needs to be adapted to the latest Linux kernel version.
 * The package should not fail to install when the module build fails.
   This might be a problem in dkms itself, or in ddcci's integration.

I note that the combination of these issues also will break
installation of Linux 6.3 when ddcci-dkms is installed.

   $ sudo apt install ddcci-dkms 
   Reading package lists... Done
   Building dependency tree... Done
   Reading state information... Done
   The following NEW packages will be installed:
 ddcci-dkms
   0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
   Need to get 21.7 kB of archives.
   After this operation, 95.2 kB of additional disk space will be used.
   Get:1 https://deb.debian.org/debian testing/main amd64 ddcci-dkms all 
0.4.2-4 [21.7 kB]
   Fetched 21.7 kB in 1s (17.0 kB/s) 
   Retrieving bug reports... Done
   Parsing Found/Fixed information... Done
   Selecting previously unselected package ddcci-dkms.
   (Reading database ... 730615 files and directories currently installed.)
   Preparing to unpack .../ddcci-dkms_0.4.2-4_all.deb ...
   Unpacking ddcci-dkms (0.4.2-4) ...
   Setting up ddcci-dkms (0.4.2-4) ...
   Loading new ddcci-0.4.2 DKMS files...
   Building for 6.3.0-1-amd64
   Building initial module for 6.3.0-1-amd64
   Error! Bad return status for module build on kernel: 6.3.0-1-amd64 (x86_64)
   Consult /var/lib/dkms/ddcci/0.4.2/build/make.log for more information.
   dpkg: error processing package ddcci-dkms (--configure):
    installed ddcci-dkms package post-installation script subprocess returned 
error exit status 10
   Errors were encountered while processing:
    ddcci-dkms
   E: Sub-process /usr/bin/dpkg returned an error code (1)
   
   $ cat /var/lib/dkms/ddcci/0.4.2/build/make.log
   DKMS make.log for ddcci-0.4.2 for kernel 6.3.0-1-amd64 (x86_64)
   Thu 15 Jun 2023 10:23:01 AWST
   make: Entering directory '/var/lib/dkms/ddcci/0.4.2/build'
   make -C "ddcci"
   make[1]: Entering directory '/var/lib/dkms/ddcci/0.4.2/build/ddcci'
   make -C "/lib/modules/6.3.0-1-amd64/build" 
M="/var/lib/dkms/ddcci/0.4.2/build/ddcci" modules
   make[2]: Entering directory '/usr/src/linux-headers-6.3.0-1-amd64'
 CC [M]  /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.o
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1053:27: error: initialization 
of ‘int (*)(const struct device *, struct kobj_uevent_env *)’ from incompatible 
pointer type ‘int (*)(struct device *, struct kobj_uevent_env *)’ 
[-Werror=incompatible-pointer-types]
    1053 | .uevent = ddcci_device_uevent,
 |   ^~~
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1053:27: note: (near 
initialization for ‘ddcci_device_type.uevent’)
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1056:27: error: initialization 
of ‘char * (*)(const struct device *, umode_t *, kuid_t *, kgid_t *)’ {aka 
‘char * (*)(const struct device *, short unsigned int *, kuid_t *, kgid_t *)’} 
from incompatible pointer type ‘char * (*)(struct device *, umode_t *, kuid_t 
*, kgid_t *)’ {aka ‘char * (*)(struct device *, short unsigned int *, kuid_t *, 
kgid_t *)’} [-Werror=incompatible-pointer-types]
    1056 | .devnode    = ddcci_devnode
 |   ^
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1056:27: note: (near 
initialization for ‘ddcci_device_type.devnode’)
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1062:27: error: initialization 
of ‘int (*)(const struct device *, struct kobj_uevent_env *)’ from incompatible 
pointer type ‘int (*)(struct device *, struct kobj_uevent_env *)’ 
[-Werror=incompatible-pointer-types]
    1062 | .uevent = ddcci_device_uevent,
 |   ^~~
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1062:27: note: (near 
initialization for ‘ddcci_dependent_type.uevent’)
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1065:27: error: initialization 
of ‘char * (*)(const struct device *, umode_t *, kuid_t *, kgid_t *)’ {aka 
‘char * (*)(const struct device *, short unsigned int *, kuid_t *, kgid_t *)’} 
from incompatible pointer type ‘char * (*)(struct device *, umode_t *, kuid_t 
*, kgid_t *)’ {aka ‘char * (*)(struct device *, short unsigned int *, kuid_t *, 
kgid_t *)’} [-Werror=incompatible-pointer-types]
    1065 | .devnode    = ddcci_dependent_devnode
 |   ^~~
   /var/lib/dkms/ddcci/0.4.2/build/ddcci/ddcci.c:1065:27: note: (near 
initialization for ‘ddcci_dependent_type.devnode’)
   In file included from 
/usr/src/linux-headers-6.3.0-1-common/include/linux/build_bug.h:5,
    from 

Bug#1037973: cryptsetup: option 'tcrypt-system' in crypttab is unknown

[Ben Westover]

Package: cryptsetup
Version: 2:2.6.1-4
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

I am dual-booted with a Windows install encrypted by VeraCrypt. I have
the following entry in /etc/crypttab to decrypt the filesystem:

cryptwin PARTUUID=dfefa23b-02 none tcrypt,tcrypt-system,veracrypt

The tcrypt-system option is needed because this is a system partition.
It's not documented in the crypttab(5) man page, but I read about it on
the Arch Wiki and it worked for me on Debian bookworm.

When I updated my system after bookworm's stable release, upgrading it
to trixie, I got the warning "ignoring unknown option 'tcrypt-system'"
and it failed to decrypt the partition. Checking crypttab(5) again, it
still doesn't mention anything about the tcrypt-system option, but the
cryptsetup(8) man page stil has the --tcrypt-system flag listed, so the
feature wasn't removed. I can't find any information on how to decrypt
a VeraCrypt system partition other than with this option. I can still
manually use --tcrypt-system to open it with cryptsetup, but the option
is now unknown in crypttab. What happened between bookworm and trixie?

- --
Ben Westover

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

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

Versions of packages cryptsetup depends on:
ii  cryptsetup-bin 2:2.6.1-4
ii  debconf [debconf-2.0]  1.5.82
ii  dmsetup2:1.02.185-2
ii  libc6  2.36-9

cryptsetup recommends no packages.

Versions of packages cryptsetup suggests:
ii  cryptsetup-initramfs2:2.6.1-4
ii  dosfstools  4.2-1
ii  keyutils1.6.3-2
ii  liblocale-gettext-perl  1.07-5

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOGnacqRhdU6eNmtFwxHF9U6JtpgFAmSKcDIACgkQwxHF9U6J
tphJTA//UBx1n+3MleEXiizCZm26nkWovfBu17jiuedmXbx9MHBTjnkuD5SOvAr7
OwMJX4xRLtXR6ez6j02A2yqGaM6ZROmKT9lbXtYnzkPNyfOjrnKq0eWT2uPGx/hV
qrHQdsAB1noiO/Y8uj8ovdYNxZ1yJuVuWHZE0Ugqip2wXpiOPQvVBGWeAaUwL2NP
bnDpTclXimDEp3A4wfCXgJOwsUBLUpkVx7q1S0HPgzoyB4LQIfR1MSMbua9q+iwq
wjxnNe1ySISFOCxoO4Dv+648tQfLC2GbnXNBang1Gl1VKfCMX7unirVuGBwivX1N
0KdNsEIzsMco4YCQ27nseKNb7ffE8uQ0EbcV35muCguACz2iHPHw0vRhlv/rPKa6
3/kquSG3Fc5+mje36e+y1dWNAiRw6xbR9jTzllhHE6HffCgOZf5C8apQkyYGrTuC
zLSyav84SOragi8nFGEe8wb6D2l4sHtz4maaGTj8TnBDdsrj59xxD/E7sjbvmYXM
mPhHFoZXl7XDJXKKC9gezhLyPWeyDtrsmXMfHRrzZipbtMkKEpBRXOyCyQivQvPy
B504ktFdwCQnDe8RmM+qvIxySEDY3IC4SofId4vUjcgr3KxodIJ8RPNrzONipOw6
0CTIfpiQxd1qJfW4B0huzJ0nWSIp91jgqqAjjgvY3RsdlCplgEs=
=2fkH
-END PGP SIGNATURE-

Bug#1036775: transmission-gtk: Stuck / segfault on startup

[Witold Baryluk]

Package: transmission-gtk
Version: 3.00-2.1+b1
Followup-For: Bug #1036775
X-Debbugs-Cc: witold.bary...@gmail.com
Control: severity 1036775 important

Bumping severity. This happens on a clean install of bookworm too, by
just invoking transmission-gtk from a terminal emulator

Bug#1036038: debian-installer: Debian installer, graphical installer, live image, hang on Dell Inspiron 27

[Ernesto Alfonso]

Thanks for following up. I tried the bookworm netinstall and the PXE boot,
but the install failed in the same way:

https://deb.debian.org/debian/dists/bookworm/main/installer-amd64/current/images/SHA256SUMS

I used the netbot.tar.gz as well as the USB

b41d766e5389b4e35bac3a664da84822e0990439c9c4df933ddbaff6847a0009
./netboot/netboot.tar.gz


I managed to get the PXE netboot to work using DHCPD and AFTPD. I modified
the splash.png to be a black 640x480 PNG file and also updated grub.cfg to
replace --- quiet with --debug.

I was able to boot into grub and then I issued the commands based on the
"Expert install" menu entry:

linux /debian-installer/amd64/linux --- debug
initrd /debian-installer/amd64/initrd.gz
boot

After issuing boot, the installer hanged indefinitely with no output.
Here's a 1m video of this after pressing Enter on boot:

https://downloads.erjoalgo.com/WhatsApp%20Video%202023-06-14%20at%208.42.41%20PM.mp4

Is there a way to get more verbose output to figure out what is hanging
boot?

I also want to add that I tried an Ubuntu image and this booted properly:
https://pasteboard.co/9Awz7Io3kEVG.jpg

Thanks again,

Ernesto

On Sat, May 13, 2023 at 6:58 PM Cyril Brulebois  wrote:

> Hi Ernesto,
>
> Ernesto Alfonso  (2023-05-13):
> > I'm attempting to setup Debian on a Dell Inspiron All-in-One system,
> > either as dual boot or replacing the existing windows 10 OS.
> >
> > The installer hangs after entering either the "graphical install",
> > "install" or "live" options from the initial menu. I used the latest
> > 64-bit installer: debian-11.7.0-amd64-netinst.iso, burned onto a USB
> > drive using the dd command:
> >
> > sudo dd if=/debian-11.7.0-amd64-netinst.iso of=/dev/sda
>
> OK, all of that looks good to me. You could try and replace “quiet” with
> “debug” on any entry to see if you're getting some error messages.
>
> > I've tried to disable most or all of the UEFI secure boot options on
> > the BIOS and also the RAID/storage related settings: […]
>
> That really shouldn't be needed, we've been supporting Secure Boot for a
> while. And yes, it's starting to be rather common for systems to come
> without any support for BIOS/Legacy booting (and I kind of like the way
> some hardware manufacturers are up-front about it, with a clear message
> in their UEFI firmware interface).
>
> > Is it possible to install Debian on this type of system?
>
> At this stage, I'd suggest giving Bookworm a shot, e.g. using the D-I
> Bookworm RC 2 installer. Or wait a few hours (maybe days), at which
> point an RC 3 should become available.
>
>   https://www.debian.org/devel/debian-installer/
>
>
> Cheers,
> --
> Cyril Brulebois (k...@debian.org)
> D-I release manager -- Release team member -- Freelance Consultant
>

Bug#1036038: PXE boot on bookworm, "boot" hangs with --- debug. Ubuntu works

[Ernesto Alfonso]

Thanks for following up. I tried the bookworm netinstall and the PXE boot,
but the install failed in the same way:

https://deb.debian.org/debian/dists/bookworm/main/installer-amd64/current/images/SHA256SUMS

I used the netbot.tar.gz as well as the USB

b41d766e5389b4e35bac3a664da84822e0990439c9c4df933ddbaff6847a0009
./netboot/netboot.tar.gz


I managed to get the PXE netboot to work using DHCPD and AFTPD. I modified
the splash.png to be a black 640x480 PNG file and also updated grub.cfg to
replace --- quiet with --debug.

I was able to boot into grub and then I issued the commands based on the
"Expert install" menu entry:

linux /debian-installer/amd64/linux --- debug
initrd /debian-installer/amd64/initrd.gz
boot

After issuing boot, the installer hanged indefinitely with no output.
Here's a 1m video of this after pressing Enter on boot:

https://downloads.erjoalgo.com/WhatsApp%20Video%202023-06-14%20at%208.42.41%20PM.mp4

Is there a way to get more verbose output to figure out what is hanging
boot?

I also want to add that I tried an Ubuntu image and this booted properly:
https://pasteboard.co/9Awz7Io3kEVG.jpg

Thanks again,

Ernesto

Bug#1032616: [Pkg-electronics-devel] Bug#1032616: ghdl: New release (3.0.0) available

[Daniel Gröber]

Hi Andreas,

Just a reminder on this.

On Fri, Mar 10, 2023 at 08:25:15AM +, Stanislav Maslovski wrote:
> Please consider packaging the new release of GHDL ver. 3.0.0. [1]
> 
> The ver. 2.0.0 is more than 1 year old. The new release has a better
> support of VHDL 2008, especially, in the synthesis-targeted area.

My yosys-ghdl-plugin package has also received a number of fixes in ghdl
3.0.0 and in fact the latest upstream version doesn't build with 2.0
anymore.

I'd be happy to do the ghdl packaging (and fixing) work if you want to
sponsor my uploads.

Thanks,
--Daniel

Bug#1037972: Bug on Debian 12 Bookworm - Installation reports - /etc/apt/source.list

[pham...@bluewin.ch]

Package: debian-12.0.0-amd64-DVD-1.iso
File: /etc/apt/source.list
Severity: high (security)

Bug Description :

After installation of Debian 12 with the 'debian-12.0.0-amd64-DVD-1.iso' image, 
the '/etc/apt/source.list' file contains only one entry for installing or 
upgrading the system:
deb cdrom:[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD Binary-1 
with firmware 20230610-10:23]/ bookworm main non-free-firmware
After editing the 'source.list' file with the 'software and updates' software 
and activating all remote repositories of the first tab of this program, only 
one line is added to the 'source.list' file ':
deb https://deb.debian.org/debian/ bookworm main contrib non-free 
non-free-firmware
It therefore lacks parameters to perform updates / security repertories on this 
DVD version of 'source.list' file, while in the Live ISO version of Debian 12 
Cinnamon does not have this type of problem.
Someone who doesn't know Debian and has installed the DVD edition of Debian on 
a machine can find themselves really embarrassed some time later since the 
security updates for their machine are not done without manually updating 
update the 'source.list' file.
Thank you to correct this as soon as possible.
Best regards.
Philippe 

Bug#1005512: irqtop: Errors in man pages

[Axel Beckert]

Hi Helge,

thanks for the bug report!

Helge Kreutzmann wrote:
> Finally the issues I'm reporting have accumulated over time and are
> not always discovered by me, so sometimes my description of the
> problem my be a bit limited - do not hesitate to ask so we can clarify
> them.

Yeah, I think that's the place where things went a bit wrong.

> Man page: irqtop.1
> Issue:ethtool → B(8)

I'm sorry, but this is a groff-written man page, but your suggested
change seems POD syntax.

> "show extra eth stats (from ethtool)"

That line now renders in man like this:

"show extra eth stats (from B(8))"

I don't think that's wanted.

Besides we render htop(1) and friends under "SEE ALSO" also without
any special formatting.

So I'll make it simply "ethtool(8)".
  
> Man page: irqtop.1
> Issue:enouth → enough

"enouth" neither is nor ever was in this Debian package.

> "Show per-cpu statistics by specified mode. Available modes are: B, "
> "B, B. The default option B detects the width of "
> "window, then shows the per-cpu statistics if the width of window is large "
> "enouth to show a full line of statistics."

Neither is this text.

A quick search on codesearch.debian.net reveals that this is part of
the man page from the _other_ tool named irqtop, the one from
util-linux:
https://sources.debian.org/src/util-linux/2.38.1-5/sys-utils/irqtop.1.adoc/?hl=29#L29

Which is not yet shipped in a binary package in Debian as I didn't
manage to start the migration between the two irqtops timely before
the Bookworm freeze.

Please report that error against src:util-linux.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#1037783:

[José Luis Blanco-Claraco]

Thanks, Matthias for reporting.

The issue is now fixed upstream [1].
We'll make a new Debian release of the package soon to close this bug.

Cheers,
JL

[1] Branch "develop" of http://github.com/MRPT/mrpt/ as of today's
version, commit hash
3b01ad11af786acd129f05152fdbfb505086509c

Bug#1037353: lynx.1: a few formatting fixes for the manual

[Thomas Dickey]

On Mon, Jun 12, 2023 at 01:56:56AM +, Bjarni Ingi Gislason wrote:
> Package: lynx
> Version: 2.9.0dev.12-1
> Severity: minor
> Tags: patch
> 
> Dear Maintainer,
> 
> here are some fixes.
> 
> Input file is lynx.1
> 
> Output from "mandoc -T lint lynx.1"
> mandoc: lynx.1:27:2: WARNING: missing date, using "": TH
> mandoc: lynx.1:109:2: WARNING: unknown font, skipping request: ft C   
> 
> mandoc: lynx.1:317:2: WARNING: unknown font, skipping request: ft C   
> 
> mandoc: lynx.1:366:2: WARNING: unknown font, skipping request: ft C   
> 
> mandoc: lynx.1:831:2: WARNING: unknown font, skipping request: ft C   
> 
> mandoc: lynx.1:838:2: WARNING: unknown font, skipping request: ft C   
> 
> mandoc: lynx.1:1131:2: WARNING: unknown font, skipping request: ft C  
> 

That seems to be harmless for nroff, but mainly is for troff (and groff)
to select a fixed-pitch font for PDFs and PostScript.  I'll see if this
is at least no worse than the plain "C".

Solaris 10 appears to have "CO" for "Courier" (troff), while
an AIX that I can access uses "CR".  But on those systems,
I'm not actually using troff :-)

I've been using "C" quite a while, and hadn't noticed a problem with
the indicated usage (i.e., generating PDFs, etc).

> ###
> 
> Increase size of ~ (tilde) to make it more visible
> with "troff" by using character \(ti.

That appears to be groff-specific.
 
> 264:If none is specified, the default value is ~/.lynx_cookies
> 265:for most systems, but ~/cookies for MS-DOS.
> 
> #
> 
>   The following issue is not in the patch:
> 
> an.tmac:lynx.1:27: style: .TH missing third argument; suggest document 
> modification date in ISO 8601 format (-MM-DD)
> an.tmac:lynx.1:27: style: .TH missing fourth argument; suggest 
> package/project name and version (e.g., "lynx ...")

maybe - there are pros/cons (the version number is in the manpage,
and that indirectly gives an accurate date).  If I did put a date,
it would be the modification date for _that_ file.
 
> #
> 
> --- lynx.12023-06-05 16:20:24.0 +
> +++ lynx.1.new2023-06-12 01:32:27.0 +
> @@ -15,7 +15,7 @@
>  .ie n  .in +4
>  .el.in +2
>  .nf
> -.ft C\" Courier
> +.ft CR   \" Courier
>  ..
>  .de NE
>  .fi
> @@ -261,8 +261,8 @@ Sets the connection timeout, where N is
>  .TP
>  .B \-cookie_file\fR=\fIFILENAME
>  specifies a file to use to read cookies.
> -If none is specified, the default value is ~/.lynx_cookies
> -for most systems, but ~/cookies for MS-DOS.
> +If none is specified, the default value is \(ti/.lynx_cookies
> +for most systems, but \(ti/cookies for MS-DOS.
>  .TP
>  .B \-cookie_save_file\fR=\fIFILENAME
>  specifies a file to use to store cookies.
> 
> 
> -- System Information:
> Debian Release: 12.0
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.1.27-1 (SMP w/2 CPU threads; PREEMPT)
> Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
> LANGUAGE not set
> Shell: /bin/sh linked to /usr/bin/dash
> Init: sysvinit (via /sbin/init)
> 
> Versions of packages lynx depends on:
> ii  libbsd0   0.11.7-2
> ii  libbz2-1.01.0.8-5+b1
> ii  libc6 2.36-9
> ii  libgnutls30   3.7.9-2
> ii  libidn2-0 2.3.3-1+b1
> ii  libncursesw6  6.4-4
> ii  libtinfo6 6.4-4
> ii  lynx-common   2.9.0dev.12-1
> ii  zlib1g1:1.2.13.dfsg-1
> 
> Versions of packages lynx recommends:
> ii  mailcap  3.70+nmu1
> 
> lynx suggests no packages.
> 
> -- no debconf information
> 

-- 
Thomas E. Dickey 
https://invisible-island.net


signature.asc
Description: PGP signature

Bug#1037710: kodi: ftbfs with GCC-13

[Nicholas D Steeves]

Control: tag upstream fixed-upstream

https://kodi.tv/article/kodi-omega-alpha-1/

Bug#1037612: control

[Dave Steele]

Control: tags -1 upstream
Control: forwarded -1 https://github.com/cryfs/cryfs/issues/458

Bug#1037548:

[allan]

You're right, the problem was a broken MIME database.  Thank you for the helps!

Bug#1034546: RFS: luametatex/2.10.07-1 [ITP] -- Next generation ConTeXt processing engine

[Preuße]

On 01.06.2023 09:53, Preuße...@buxtehude.debian.org, Hilmar wrote:

Dear mentors,

Ping! Would anybody so kind to upload to experimental? That package is 
prereq for the next version of ConTeXt.


Now that bookworm is released I changed the target distribution to 
unstable and re-uploaded.


Hilmar
--
sigfault



OpenPGP_0x0C871C4C653C1F59.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037971: ksh93u+m: read statement in subshell fails for 0 or 1 character followed by tab

[Bill Brelsford]

Package: ksh93u+m
Version: 1.0.4-3
Severity: normal

Dear Maintainer,

The following:

( read a; print "$a" )

beeps and ignores a tab if entered before two other characters have
been typed.  With () removed, it works in an interactive shell but
fails in an invoked script.

Bill

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

Kernel: Linux 6.1.0-9-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: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages ksh93u+m depends on:
ii  libc6  2.36-9

ksh93u+m recommends no packages.

Versions of packages ksh93u+m suggests:
pn  binfmt-support  

-- no debconf information

Bug#1034464: apper: Administrator password input dialog does not display and installation fails

[Frédéric Mesplède]

Package: apper
Version: 1.0.0-4
Followup-For: Bug #1034464
X-Debbugs-Cc: fredericmespl...@gmail.com

Dear Maintainer,

Apper doesn't ask for sudo privileges to install packages and therefore it
fails.

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

   * What led up to the situation?
I tried to install a package thanks to Apper.
   * 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: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages apper depends on:
ii  apper-data  1.0.0-4
ii  kio 5.103.0-1
ii  libappstreamqt2 0.16.1-2
ii  libc6   2.36-9
ii  libkf5completion5   5.103.0-1
ii  libkf5configcore5   5.103.0-2
ii  libkf5coreaddons5   5.103.0-1
ii  libkf5dbusaddons5   5.103.0-1
ii  libkf5i18n5 5.103.0-1
ii  libkf5iconthemes5   5.103.0-1
ii  libkf5itemviews55.103.0-1
ii  libkf5jobwidgets5   5.103.0-1
ii  libkf5kiocore5  5.103.0-1
ii  libkf5kiowidgets5   5.103.0-1
ii  libkf5notifications55.103.0-1
ii  libkf5service-bin   5.103.0-1
ii  libkf5service5  5.103.0-1
ii  libkf5solid55.103.0-1
ii  libkf5widgetsaddons55.103.0-1
ii  libkf5xmlgui5   5.103.0-1
ii  libkworkspace5-54:5.27.5-2
ii  libpackagekitqt5-1  1.1.1-1
ii  libqt5core5a5.15.8+dfsg-11
ii  libqt5dbus5 5.15.8+dfsg-11
ii  libqt5gui5  5.15.8+dfsg-11
ii  libqt5widgets5  5.15.8+dfsg-11
ii  libqt5xmlpatterns5  5.15.8-2
ii  libstdc++6  12.2.0-14
ii  packagekit  1.2.6-5
ii  polkit-kde-agent-1  4:5.27.5-2
ii  software-properties-qt  0.99.30-4

Versions of packages apper recommends:
ii  appstream   0.16.1-2
ii  apt-config-icons0.16.1-2
ii  debconf-kde-helper  1.1.0-1

apper suggests no packages.

-- no debconf information

Bug#1023491: ovmf-ia32 lacks non-secboot firmware images, but qemu does not (yet) support secboot

[Lionel Debroux]

Hi,

I hit this issue when testing a bugfix for memtest86+ under QEMU. 
Before finding this bug report, I worked around it by taking OVMF 
non-secboot binaries from an Arch package, but I agree with Alain: 
non-secboot binaries are useful, and besides, multiple (most ?) other 
distros provide them :)

For memtest86+, testing 32-bit UEFI binaries in QEMU once in every 
while arguably provides useful test coverage for the goal of 
supporting a broad range of x86 & x86_64 computers: physical 
computers which provide 32-bit UEFI boot support but not legacy BIOS 
boot support are rather uncommon.


Regards,
Lionel Debroux.

Bug#1037969: librsvg2-2: Upgrading librsvg2-2 removing gnome-desktop

[Elite Dragon]

Package: librsvg2-2
Version: 2.54.5+dfsg-1
Severity: important
X-Debbugs-Cc: stigma...@gmail.com

Dear Maintainer,

*** 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?
Upgrading package was stoped. When i try to upgrade package manual by sudo apt 
install librsvg2-2, it removing almost all my system packages like gnome-shell 
and other packages.

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


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages librsvg2-2 depends on:
ii  libc62.36-9
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libgcc-s113.1.0-5
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libxml2  2.9.14+dfsg-1.2

Versions of packages librsvg2-2 recommends:
ii  librsvg2-common  2.54.5+dfsg-1

Versions of packages librsvg2-2 suggests:
pn  librsvg2-bin  

-- no debconf information

Bug#914260: dgit clone fails with "Out of memory, malloc failed"

[Ian Jackson]

Control: tags -1 + moreinfo
Control: retitle -1 "botch" package, server out of memory

I think this should be working now ?  I just tested it.  Sorry for
letting this bug languish.  I do recall at some times asking DSA to
increase the VM's RAM.

Please let me know if it's still broken now.  Otherwise I think we
should close this bug.

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#1037968: unauthorised background updates

[slimshady]

Package: general
Severity: serious
X-Debbugs-Cc: slimshad...@zohomail.eu

without my approval the latest kernel update was applied and the most 
surprising thing is that no downloaded files are present in the cache folder.
all happens in the background without my knowledge. only found out during 
reboot. same for all the other updates like firefox but they not that serious.
again updates set to manual.

Bug#1037967: ITP: libio-compress-brotli-perl -- modules to read/write Brotli buffers/streams

[gregor herrmann]

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

* Package name: libio-compress-brotli-perl
  Version : 0.004001
  Upstream Author : Marius Gavrilescu 
* URL : https://metacpan.org/release/IO-Compress-Brotli
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : modules to read/write Brotli buffers/streams

The IO-Compress-Brotli distribution wraps the Brotli library, offering Perl
modules for compressing Brotli buffers and streams, IO::Compress::Brotli, and
decompressing them, IO::Uncompress::Brotli.

Brotli is a data compression format primarily used in web fonts and
HTTP compression.

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

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


signature.asc
Description: Digital Signature

Bug#1037966: bind9: Unable to restart bind9 via systemctl when using chroot on Debian 12

[Bret Giddings]

Package: bind9
Version: 1:9.18.12-1
Severity: important

Dear Maintainer,

Whilst attempting to upgrade from debian 11 to 12, for my chroot named setup, I
found that running

systemctl restart named

would hang and eventually timeout. It should be noted that named is running 
fine.

Having compared the differences from 11 to 12, I believe that this is caused
by the latter unit file using a service type of notify rather than the default
simple.

Creating an override with

[Service]
Type=simple

restores the former behaviour. So, I believe that the notify option is unable
to communicate with the chroot'ed environment. Whilst I can use the above
as a workaround, I couldn't find anything in the changelog or elsewhere
reporting this issue. I also tested and confirmed this behaviour on a new
install of bind9 with minimal customisation. It only fails when you switch
to using '-t /var/cache/bind' in /etc/defaults/named (having previously
created the appropriate directories etc.


-- 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/48 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bind9 depends on:
ii  adduser3.134
ii  bind9-libs 1:9.18.12-1
ii  bind9-utils1:9.18.12-1
ii  debconf [debconf-2.0]  1.5.82
ii  dns-root-data  2023010101
ii  init-system-helpers1.65.2
ii  iproute2   6.1.0-3
ii  libc6  2.36-9
ii  libcap21:2.66-4
ii  libfstrm0  0.6.1-1
ii  libjson-c5 0.16-2
ii  liblmdb0   0.9.24-1
ii  libmaxminddb0  1.7.1-1
ii  libnghttp2-14  1.52.0-1
ii  libprotobuf-c1 1.4.1-1+b1
ii  libssl33.0.9-1
ii  libsystemd0252.6-1
ii  libuv1 1.44.2-1
ii  libxml22.9.14+dfsg-1.2
ii  netbase6.4
ii  sysvinit-utils [lsb-base]  3.06-4
ii  zlib1g 1:1.2.13.dfsg-1

bind9 recommends no packages.

Versions of packages bind9 suggests:
pn  bind-doc   
ii  bind9-dnsutils [dnsutils]  1:9.18.12-1
pn  resolvconf 
pn  ufw

-- Configuration Files:
/etc/bind/db.0 [Errno 2] No such file or directory: '/etc/bind/db.0'
/etc/bind/db.127 [Errno 2] No such file or directory: '/etc/bind/db.127'
/etc/bind/db.255 [Errno 2] No such file or directory: '/etc/bind/db.255'
/etc/bind/db.empty [Errno 2] No such file or directory: '/etc/bind/db.empty'
/etc/bind/db.local [Errno 2] No such file or directory: '/etc/bind/db.local'
/etc/bind/named.conf changed [not included]
/etc/bind/named.conf.default-zones [Errno 2] No such file or directory: 
'/etc/bind/named.conf.default-zones'
/etc/bind/named.conf.local [Errno 2] No such file or directory: 
'/etc/bind/named.conf.local'
/etc/bind/named.conf.options [Errno 2] No such file or directory: 
'/etc/bind/named.conf.options'
/etc/bind/zones.rfc1918 [Errno 2] No such file or directory: 
'/etc/bind/zones.rfc1918'
/etc/default/named changed [not included]

-- no debconf information

Bug#1037959: BUG: kernel NULL pointer dereference in kthread md2_raid6

[Salvatore Bonaccorso]

Hi Timo,

On Wed, Jun 14, 2023 at 10:44:01AM +0200, Timo Weingärtner wrote:
> Package: src:linux
> Version: 6.1.27-1
> Severity: important
> 
> Dear Maintainer,
> 
> yesterday I upgraded my home server to bookworm. When cutting a
> recording in vdr (reading a big video file while writing out a big video
> file and a smaller index file) it triggered a bug in the raid6 kernel
> thread and the vdr process got stuck in D state.
> 
> I could reproduce this by starting the video cutting again after reboot.
> It doesn't happen with the bullseye kernel 5.10.0-23-amd64 which I'm
> using now.

Would you be able to test the newst upstream version from 6.1.y series
and see if the problem persist? How about 6.3.7-1 or 6.4~rc6-1~exp1?

Would you be in case as well in the position to try to bisect the
issue?

Regards,
Salvatore

Bug#1035733: debian -policy: packages must not use dpkg-divert to override default systemd configuraton files

[Holger Levsen]

On Tue, Jun 13, 2023 at 11:04:07PM +0100, Luca Boccassi wrote:
> ---
>  policy/ap-pkg-alternatives.rst |  3 +++
>  policy/ap-pkg-diversions.rst   |  3 +++
>  policy/ch-binary.rst   | 35 ++
>  3 files changed, 41 insertions(+)
> 
> diff --git a/policy/ap-pkg-alternatives.rst b/policy/ap-pkg-alternatives.rst
> index ffa2163..6f7780f 100644
> --- a/policy/ap-pkg-alternatives.rst
> +++ b/policy/ap-pkg-alternatives.rst
> @@ -24,3 +24,6 @@ See the :manpage:`update-alternatives(8)` man page for 
> details.
>  If ``update-alternatives`` does not seem appropriate you may wish to
>  consider using diversions instead.
>  
> +Do not use alternatives for ``systemd`` configuration files. See
> +:doc:`ch-binary` for more information.
> +
> diff --git a/policy/ap-pkg-diversions.rst b/policy/ap-pkg-diversions.rst
> index fe360d1..d299d04 100644
> --- a/policy/ap-pkg-diversions.rst
> +++ b/policy/ap-pkg-diversions.rst
> @@ -81,3 +81,6 @@ when the file does not exist.
>  Do not attempt to divert a conffile, as ``dpkg`` does not handle it
>  well.
>  
> +Do not use diversions for files that have their own native override 
> mechanisms,
> +such as ``systemd`` unit files. See :doc:`ch-binary` for more information.
> +
> diff --git a/policy/ch-binary.rst b/policy/ch-binary.rst
> index e517f26..19635e7 100644
> --- a/policy/ch-binary.rst
> +++ b/policy/ch-binary.rst
> @@ -371,6 +371,41 @@ against earlier versions of something that previously 
> did not use
>  ``update-alternatives``; this is an exception to the usual rule that
>  versioned conflicts should be avoided.)
>  
> +Diversions are primarily intended as a tool for local administrators or local
> +packages to override the behavior of Debian. While there are some 
> circumstances
> +where one Debian package may need to divert a file of another Debian package,
> +those circumstances are rare and diversions should only be used as a last 
> resort
> +when no other suitable mechanism exists. Diversion of a file in one Debian
> +package by another Debian package should be coordinated between the 
> maintainers
> +of those packages. Maintainers should strongly prefer using other overriding
> +mechanisms, instead of diversions, whenever those other mechanisms are
> +sufficient to accomplish the same goal. In other words, diversions in 
> packages
> +should be considered a last resort.
> +
> +One specific case of that rule is that configuration files used by
> +``systemd`` components, such as `units,
> +`_
> +`udev rules,
> +`_
> +`tmpfiles.d,
> +`_
> +`modules-load.d,
> +`_,
> +`sysusers
> +`_
> +and other such files, including those specific to systemd daemons
> +(e.g.:  `/etc/systemd/system.conf).
> +`_
> +must not be diverted by any Debian package. Instead, use `masking and 
> drop-ins
> +`_.
> +
> +Alternatives must never be used for ``systemd`` configuration files. The
> +alternatives system does not know how to apply changes to services when 
> updating
> +alternatives, so the resulting behavior would be confusing and unpredictable.
> +Instead, `aliases
> +`_
> +can be used to provide alternative implementations of the same named unit.
> +
 
seconded.

and wondering, if there should be a recommendation similar to consulting 
debian-devl@l.d.o
when introducing epochs, or...

..the other way round: should it be explicitly spelled out that, unlike for 
epochs, 
in general there's no need to consult -devel for diversions for packages as 
they are 
generally ment for local admins and only in very very very rare cases...

(maybe be even more verbose about "other overriding mechanisms"?!)

but in any case seconded, things can always be improved, and this is good.


-- 
cheers,
Holger

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

Punk ist nicht tot.
Punk trägt Maske, ist solidarisch und schützt sich und andere.
(@Kreuzpirat)


signature.asc
Description: PGP signature

Bug#1037945: bookworm-pu: package aide/aide_0.18.3-1+deb12u1

[Marc Haber]

On Wed, Jun 14, 2023 at 06:20:44PM +0100, Adam D. Barratt wrote:
> On Wed, 2023-06-14 at 17:27 +0200, Marc Haber wrote:
> > this pre-upload request for the aide package is filed to ask for
> > guidance whether this package is suitable for bookworm-updates.
> 
> Do you actually mean bookworm-updates here (i.e. pushed to users in
> advance of 12.1), or simply (bookworm-)proposed-updates, therefore
> reaching users with the release of 12.1?

I would be fine with either, proposed-updates of course being less
invasive. Probably a misunderstanding because of me being too stupidto
find the docs. I'll read up on what you linked to me.

> I'd be interested in seeing a binary debdiff (for an arbitrary
> architecture) with "--controlfiles=ALL" to see the changes made to the
> maintainer scripts, but overall I think this looks OK.

aide-dynamic:
1 [23/4887]mh@salida:~/packages/aide $ debdiff --controlfiles=ALL
20230614/aide-dynamic_0.18.3-1_all.deb
build-area/aide-dynamic_0.18.3-1+deb12u1_all.deb
File lists identical (after any substitutions)

Control files: lines which differ (wdiff format)

Recommends: aide-common (= [-0.18.3-1)-] {+0.18.3-1+deb12u1)+}
Version: [-0.18.3-1-] {+0.18.3-1+deb12u1+}
1 [24/4888]mh@salida:~/packages/aide $ 

aide:
[19/4883]mh@salida:~/packages/aide $ debdiff --controlfiles=ALL
20230614/aide_0.18.3-1_amd64.deb
build-area/aide_0.18.3-1+deb12u1_amd64.deb 
File lists identical (after any substitutions)

Control files: lines which differ (wdiff format)

Installed-Size: [-289-] {+293+}
Recommends: aide-common (= [-0.18.3-1)-] {+0.18.3-1+deb12u1)+}
Version: [-0.18.3-1-] {+0.18.3-1+deb12u1+}
1 [20/4884]mh@salida:~/packages/aide $

aide-common is attached.

> 
> One small comment:
> 
> +if dpkg --compare-versions "$2" le 0.18.3-1; then
> +# we're updating from 0.18-3 or earlier, chown aideinit logs
> 
> That should presumably be "from 0.18.3".

Yes. fixed in git and master. Thanks for spotting this.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421
[The following lists of changes regard files as different if they have
different names, permissions or owners.]

Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/lib/sysusers.d/aide-common.conf

No differences were encountered between the config files

Control files: lines which differ (wdiff format)

Depends: aide (>= 0.17), liblockfile1, ucf (>= 2.0020), debconf (>= 0.5) | 
[-debconf-2.0-] {+debconf-2.0, systemd | systemd-standalone-sysusers | 
systemd-sysusers+}
Installed-Size: [-449-] {+451+}
Version: [-0.18.3-1-] {+0.18.3-1+deb12u1+}

Postinst files: lines which differ (wdiff format)
-
[-if dpkg --compare-versions "$2" lt 0.17.5-1; then-]
[-# we're updating from a version earlier than 0.17.5, chown logs-]
[-# and databases-]
[-chown --quiet _aide:adm /var/log/aide /var/log/aide/aide.log 
/var/log/aide/aide.log.* || true-]
[-chmod --quiet 2755 /var/log/aide || true-]
[-chown --quiet _aide:root /var/lib/aide/aide.db /var/lib/aide/aide.db.new 
|| true-]
[-fi-]
[-if dpkg --compare-versions "$2" lt 0.18-3; then-]
[-# we're updating from a version earlier than 0.18-3, chown aideinit logs-]
[-chown --quiet _aide:adm /var/log/aide/aideinit.log 
/var/log/aide/aideinit.errors|| true-]
[-fi-]
# Automatically added by {+dh_installsysusers/13.11.4+}
{+if [ "$1" = "configure" ] || [ "$1" = "abort-upgrade" ] || [ "$1" = 
"abort-deconfigure" ] || [ "$1" = "abort-remove" ] ; then+}
{+   systemd-sysusers ${DPKG_ROOT:+--root="$DPKG_ROOT"} aide-common.conf+}
{+fi+}
{+# End automatically added section+}
{+# Automatically added by+} dh_installtmpfiles/13.11.4
{+# this needs to be after debhelper, otherwise the account doesn't+}
{+# yet exist.+}
{+if dpkg --compare-versions "$2" lt 0.17.5-1; then+}
{+# we're updating from a version earlier than 0.17.5, chown logs+}
{+# and databases+}
{+chown --quiet _aide:adm /var/log/aide /var/log/aide/aide.log 
/var/log/aide/aide.log.* || true+}
{+chmod --quiet 2755 /var/log/aide || true+}
{+chown --quiet _aide:root /var/lib/aide/aide.db /var/lib/aide/aide.db.new 
|| true+}
{+fi+}
{+if dpkg --compare-versions "$2" le 0.18.3-1; then+}
{+# we're updating from 0.18-3 or earlier, chown aideinit logs+}
{+chown --quiet _ai

Bug#1037346: Lost all emails during update

[Kai Lindenberg]

Dear Michael,

On Tue, 13 Jun 2023 21:43:34 +1000 Michael Stockenhuber 
 wrote:

> Thank you very much for this report and a possible solution. Exactly the
> same happened to me on upgrade to bookworm. Can you please elaborate how
> you did this in detail? I really would be in trouble if I lose the emails.
> I know this is a big ask but I would really appreciate your help.

Sure, I created a small quick'n'dirty helper script to automate some things 
(see below), I added the comments for this post. The script was created 
iteratively while figuring out how the recovering might work. I worked on the 
live system and relied on my backup. I did not spent any time to make the 
script fail-safe or even readable, sorry. (Be sure to backup the spool 
directory..)

===

#!/bin/bash
# the cyrus spool dir
SPOOLDIR=/var/spool/cyrus/mail/
# first argument is relative spool dir of user e.g.: $ scriptname k/user/kai
# extract user and reformat for cm command of cyadmin
# k/user/kai -> user.kai
USER=$(echo $1|cut -d/ -f 2,3|tr "/" ".")
# find all mailboxes of user and reformat for cm
MBXLIST=$(find $SPOOLDIR$1 -type d|cut -d/ -f 1-8 --complement|tr "/ " "._")
# generate a script for cyradm to create new mailboxes
for MBX in $MBXLIST; do
echo cm $USER.$MBX
done > creatembx.cyradm
echo starting shell to examine the situation
echo creatembx.cyradm created to feed cyradm \(please review\)
echo continue with exit
# start a shell to check cyradmin script and general situation
# you need to feed the cyradmin script to cyadmin with
# $ cat creatembx.cyradm | cyradm --user cyrus localhost
bash
# generate a script to hard-link to the new location
for MBX in $MBXLIST; do
# get path of created mailbox
NEWPATH=$(/usr/lib/cyrus/bin/mbpath $USER.$MBX)
# get original path of mailbox
OLDPATH=$SPOOLDIR$1/${MBX//\./\/}
# link it
echo ln -f ${OLDPATH//_/\\ }/\* $NEWPATH
done | tee linkmbx.bash
echo linkmbx.bash created, please review before executing
echo manual work:
echo 1. might be too many argument, review output
echo 2. main inbox not linked, create inbox_recovered

==

(be sure you understand each step of the script and be sure that it fits to 
your configuration.)

You need to apply this script for all users on your systems (~20 users on my 
system). Then you should see all sub-mailboxes filled with mails.

I treated the INBOX differently because the server was already receiving new 
mail and out them into the INBOX. To avoid any interferences I created a 
mailbox inbox_recovered for each user with cyradm:

$ cyradm --user cyrus localhost
xxx.xxx> cm user.kai.inbox_recovered
ctrl-d

and hard-linked the mails with

$ cd `mbpath user.kai.inbox_recovered`
$ ln -f /var/spool/cyrus/mail/k/user/kai/* .

(these are the commands from by bash history)

some final thoughts:
- I did all the operations as the user cyrus
- I used hard-linking to avoid copying 10s of Gigs of mails
- it fails with unusual characters because of not escaping them
- new mailbox use underscore instead of blank (did not want to escape too)

Total time for my system: 6 hours with analysis, learnings, and recovering

Feel free to ask, if anything was too unclear, of if you want to know why I 
did sth this way (sometime there might be a reason, sometimes I did not know 
better)

Good luck
Kai

Bug#1037931: transition: platformdirs

[Stefano Rivera]

Hi Simon (2023.06.14_13:49:15_+)
> python3-platformdirs 3.x makes python3-virtualenv and python3-poetry
> uninstallable; reporting this as a transition to get it on the release
> team's radar.

Uploaded both of those to unstick it.

They were both staged in experimental, but I'd forgotten that they were
needed :)

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#887526: new upstream version available v4.8.1

[Patrick Hibbs]

Package: nuget
Version: 2.8.7+md510+dhx1-1.1
Followup-For: Bug #887526
X-Debbugs-Cc: hibbsncc1...@gmail.com

Dear Maintainer,

The current (official) nuget version is now 6.6.1.

Mathieu Malaterre suggested that the reason for the lack of an upgrade to
Debian's nuget package is changing the source, but running "sudo nuget update
-self" works just fine and using the updated version to install / update nuget
packages works in Debian Bookworm.

MonoDevelop's nuget functionality also still work with the updated nuget.
(Although, I suspect it uses it's own internal version as I could install nuget
packages (NewtonSoft.Json) that require a newer version of nuget prior to
running "sudo nuget update -self".) Of course, that package is also archived
upstream and no-longer maintained since January 2020 according to:
https://github.com/mono/monodevelop

Is there a reason why this package is still not being updated in Debian? Is
Mathieu Malaterre's suggestion accurate? It would be nice to have some
clarification.


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (100, 
'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

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

Versions of packages nuget depends on:
pn  libmono-corlib4.5-cil 
pn  libmono-microsoft-build-engine4.0-cil 
pn  libmono-microsoft-build-framework4.0-cil  
pn  libmono-microsoft-build4.0-cil
pn  libmono-microsoft-csharp4.0-cil   
pn  libmono-system-componentmodel-composition4.0-cil  
pn  libmono-system-core4.0-cil
pn  libmono-system-xml-linq4.0-cil
pn  libmono-system4.0-cil 
ii  libnuget-core-cil 2.8.7+md510+dhx1-1.1
pn  mono-runtime  

nuget recommends no packages.

nuget suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/lib/nuget/NuGet.exe (from nuget package)

Bug#1037965: ITP:budgie-backgrounds - default set of background images for the budgie desktop

[David Mohammed]

Package: wnpp
Severity: wishlist

Owner: David Mohammed (fossfree...@ubuntu.com)

Package name : budgie-backgrounds
Version : 1.0
Upstream Author : BuddiesOfBudgie
URL : https://github.com/BuddiesOfBudgie/budgie-backgrounds
License : CC0-1.0
Programming Lang: None
Description :
Default set of background images for the Budgie Desktop
 Budgie-Desktop is a GTK+ based desktop environment which focuses on
 simplicity and elegance. It provides a traditional desktop metaphor
 based interface utilising customisable panel based menu driven system.
 Budgie-Desktop is written from scratch utilising many GNOME based
 sub-systems such as GNOME-Session and Mutter.
 .
 This package provides a set of backgrounds that complement and
 showcases the budgie-desktop.

Bug#1037964: live-build: create english only isos

[michel]

Package: live-build
Severity: wishlist
Tags: l10n
X-Debbugs-Cc: okgomdjgbm...@gmail.com

Dear Maintainers,


The official live isos come with 2GBs of language packs. That's basically half 
the iso. 
That's way too much uselles stuff that after install need to be removed.

An easy and simple solution would be to create an additional set of english 
only isos.

Bug#1037963: rabbit ftbfs/autopkgtest failure with ruby-faraday 2.7 in experimental

[Pirate Praveen]

Package: rabbit
Version: 3.0.0-5
Severity: important

Full log attached

Started
E
===
Error: test_upload(TestSlideShare): Faraday::Error: :multipart is not 
registered on Faraday::Request
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday/middleware_registry.rb:57:in 
`lookup_middleware'
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday/rack_builder.rb:242:in 
`use_symbol'
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday/rack_builder.rb:103:in 
`request'

/usr/lib/ruby/3.1.0/forwardable.rb:238:in `request'
/tmp/autopkgtest-lxc.sdllem2t/downtmp/build.zXz/src/lib/rabbit/slideshare.rb:50:in 
`block in initialize'
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday/connection.rb:91:in 
`initialize'
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday.rb:98:in 
`new'
/usr/share/rubygems-integration/all/gems/faraday-2.7.1/lib/faraday.rb:98:in 
`new'
/tmp/autopkgtest-lxc.sdllem2t/downtmp/build.zXz/src/lib/rabbit/slideshare.rb:49:in 
`initialize'
/tmp/autopkgtest-lxc.sdllem2t/downtmp/build.zXz/src/test/test-slideshare.rb:23:in 
`new'
/tmp/autopkgtest-lxc.sdllem2t/downtmp/build.zXz/src/test/test-slideshare.rb:23:in 
`setup'

===
..
Finished in 5.454974752 seconds.
---
123 tests, 173 assertions, 0 failures, 1 errors, 0 pendings, 0 
omissions, 0 notifications

99.187% passed


autopkgtest [00:57:54]: starting date and time: 2023-06-15 00:57:54+0530
autopkgtest [00:57:54]: version 5.28
autopkgtest [00:57:54]: host mahishi; command line: /usr/bin/autopkgtest --user debci --apt-upgrade --log-file=/tmp/ruby-faraday_2.7.1-1_amd64.QYj3zjw6Po/autopkgtest/rabbit.log /home/pravi/forge/ruby-team/ruby-faraday_2.7.1-1_all.deb rabbit -- lxc --sudo autopkgtest-unstable-amd64
autopkgtest [00:58:14]:  test bed setup
Get:1 http://deb.debian.org/debian unstable InRelease [199 kB]
Get:2 http://deb.debian.org/debian-debug unstable-debug InRelease [56.7 kB]
Get:3 http://deb.debian.org/debian unstable/contrib Sources.diff/Index [63.3 kB]
Get:4 http://deb.debian.org/debian unstable/non-free Sources.diff/Index [63.3 kB]
Get:5 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:6 http://deb.debian.org/debian unstable/non-free amd64 Packages.diff/Index [63.3 kB]
Get:7 http://deb.debian.org/debian unstable/contrib amd64 Packages.diff/Index [63.3 kB]
Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB]
Get:9 http://incoming.debian.org/debian-buildd buildd-unstable InRelease [53.7 kB]
Get:10 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-2009.09-F-2023-06-13-1418.37.pdiff [1,691 B]
Get:11 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-2009.09-F-2023-06-13-2009.09.pdiff [715 B]
Get:12 http://deb.debian.org/debian unstable/main Sources T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [149 kB]
Get:13 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-2009.09-F-2023-06-13-2009.09.pdiff [460 B]
Get:14 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-14-0205.16-F-2023-06-13-2009.09.pdiff [563 B]
Get:10 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-2009.09-F-2023-06-13-1418.37.pdiff [1,691 B]
Get:13 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-2009.09-F-2023-06-13-2009.09.pdiff [460 B]
Get:12 http://deb.debian.org/debian unstable/main Sources T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [149 kB]
Get:11 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-2009.09-F-2023-06-13-2009.09.pdiff [715 B]
Get:15 http://deb.debian.org/debian-debug unstable-debug/main Sources.diff/Index [63.6 kB]
Get:16 http://deb.debian.org/debian-debug unstable-debug/contrib Sources.diff/Index [63.3 kB]
Get:17 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages.diff/Index [63.6 kB]
Get:18 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages.diff/Index [63.3 kB]
Get:14 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-14-0205.16-F-2023-06-13-2009.09.pdiff [563 B]
Get:19 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [188 kB]
Get:20 http://deb.debian.org/debian-debug unstable-debug/main Sources T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [66.5 kB]
Get:19 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-14-1403.53-F-2023-06-13-1418.37.pdiff [188 kB]
Get:21 http://deb.debian.org/debian-debug unstable-debug/contrib Sources T-2023-06-14-0205.16-F-2023-06-13-2009.09.pdiff [1,059 B]
Get:22 

Bug#932957: Please migrate Release Notes to reStructuredText

[Holger Wansing]

Hi,

Paul Gevers  wrote (Wed, 14 Jun 2023 21:19:00 +0200):
> Also, on the topic of arch-specific builds, I not convinced it's worth a 
> lot of effort. The amount of arch specific pieces is rather limited, so 
> I wouldn't mind if we drop that altogether. Currently, we don't do a 
> great service to people that need to support multiple architectures, 
> because they need to *search* for the delta's, so I wouldn't be 
> surprised if it is even better if we drop it.

>From the technical side, I managed to get the arch-specific builds done in
the meantime basically; so no problem anymore there - theoretically.

On the other side, I also thought about the arch-specific differences, and
given they are only rather small, my assumption was, that it's maybe not worth
it to differentiate between archs, when it comes to filtering out content
of r-n depending on the architecture.
But even if we leave that point out, there are some arch-dependent links like
http://mirrors.kernel.org/debian/dists/bookworm/main/binary-amd64/...
in chapter 4.3.1
https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#network

So, we still need to build the release-notes differentiated by archs
(based on the current content).



However, that does not mean, we could not change our base rules, so that
filtering out chapters based on architecture is no longer used.
I would vote for this solution, yes.



Holger



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#1037346: new upstream bug

[Kai Lindenberg]

Dear Maintainer,

a new upstream bug was filed on github 
https://github.com/cyrusimap/cyrus-imapd/issues/4532.

Best
-Kai

Bug#1037962: chaos-marmosets: autopkgtest failure on arm64 and ppc64el

[Paul Gevers]

Source: chaos-marmosets
Version: 0.1.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package chaos-marmosets, 
great. However, it fails on arm64 and ppc64el. Currently this failure is 
blocking the migration to testing [1]. Can you please investigate the 
situation and fix it?


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

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=chaos-marmosets

https://ci.debian.net/data/autopkgtest/testing/arm64/c/chaos-marmosets/32979373/log.gz

I: Test that divide-by-zero crashes...
Trace/breakpoint trap
I: divide-by-zero exit code: 133 (expected: 128 + 4 for SIGILL)
autopkgtest [21:14:22]: test crashes



OpenPGP_signature
Description: OpenPGP digital signature

Bug#992269: texlive-bibtex-extra: Missing beebe bst stiles like abstract.bst

[Simone Piccardi]

I could find the file in CTAN, is here:

http://tug.ctan.org/tex-archive/biblio/bibtex/contrib/misc/abstract.bst
--
Simone Piccardi Truelite Srl
picca...@truelite.it (email/jabber) Via Monferrato, 6
Tel. +39-347-103243350142 Firenze
http://www.truelite.it  Tel. +39-055-7879597

Bug#1036633: Acknowledgement (firmware-iwlwifi: Wireless AC 7265 lacks D3cold support)

[Juno Computers UK]

Any updates on this?
*
Giovanni Caligaris*
Juno Computers UK
P: +44 2034887596 
W: 
 
 
 


On Tue, May 23 2023 at 02:42:06 PM +, Debian Bug Tracking System 
 wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 1036633: 
.


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.

As you requested using X-Debbugs-CC, your message was also forwarded 
to

  u...@junocomputers.com 
(after having been given a Bug report number, if it did not have one).

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 1036...@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.

--
1036633: 
Debian Bug Tracking System
Contact ow...@bugs.debian.org  with 
problems

Bug#1037961: picolibc: autopkgtest regression: truncated to fit: R_RISCV_HI20 against `.LC0'

[Paul Gevers]

Source: picolibc
Version: 1.8.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
picolibc   from testing1.8.1-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/p/picolibc/34189996/log.gz

/tmp/ccppXFby.o: in function `main':
touch.c:(.text+0x2e): relocation truncated to fit: R_RISCV_HI20 against 
`.LC0'

collect2: error: ld returned 1 exit status
autopkgtest [17:11:55]: test command1



OpenPGP_signature
Description: OpenPGP digital signature

Bug#882872: First stab at functionality for copying files

[Nicolas Schier]

Hi Mako,

On Fri 09 Jun 2023 12:01:52 GMT, Benj. Mako Hill wrote:
> Greetings!
> 
> This is just a followup to say that I've been using the patch for
> about two years now and have not noticed any trouble. I use the
> copying files functionality in vidir nearly every day!

thanks for your patch and bringing the missing feature back to my mind.  
I _will_ give you feedback on it within the next two weeks.

> If someone wants to take a more active role in maintaince and needs a
> hand, let me know.

I am quite irresolutely how to go on with moreutils in Debian:  
upstream is responsive but it usually takes months until Joey finds 
time to handle moreutils patches (and that reduces the fun to try 
uptreaming patches on my side), and Joey is waiting for someone to 
adopt the upstream maintainence.

In general, I'd like to have Debian's moreutils package strongly 
aligned to the upstream version, but my doubts raise whether this is 
really a sensible policy.  Do you have some thoughts about that?

Kind regards,
Nicolas


signature.asc
Description: PGP signature

Bug#1029203: r-cran-gfonts_0.2.0-1_amd64.changes REJECTED

[Andreas Tille]

Hi Thorsten,

Am Thu, Jun 08, 2023 at 07:00:10PM + schrieb Thorsten Alteholz:
> 
> is there a reason why these fonts are located in /usr/lib/R ?

Well, since the R install procedure does it this way. ;-)

> Wouldn't it make sense to move them to the normal fonts directories and just 
> reference them from the R world?

I've changed the packaging to fit your wish which is IMHO pure academic.

> Several are already packaged for Debian as regular fonts ...

There are some font packages featuring the same names of the directories
the font files are located in.  However, the single font files shipped
have no equivalent names inside any Debian package.  I'd consider it
pretty fragile to guess what Debian packaged font file might possibly
fit the file in r-cran-gfont.  I've checked this in advance before my
first upload.
 
I've just uploaded r-cran-gfonts with the fonts moved to
  /usr/share/fonts/truetype/gfonts
to new.

Kind regards
 Andreas.

-- 
http://fam-tille.de

___
R-pkg-team mailing list
r-pkg-t...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/r-pkg-team

Bug#1037927: ITP: fuse -- bazil.org/fuse - With macOS support and its own import path so replace directives aren't necessary

[Félix Sipma]

Sorry about this, the message was auto-generated by dh-make-golang and I 
forgot to edit the package name in the ITP. I intend to use the usual 
golang naming "golang-github-anacrolix-fuse".


--
Félix


signature.asc
Description: PGP signature

Bug#1037960: The manpages of journalctl should explain bold (or semi-bold), yellow, and blue highlighting/emphasis

[AlMa]

Package: systemd
Version: 252.6-1

The manpage of journalctl doesn't explain the colors yellow and blue and 
the (semi-)bold emphasis of various log entries.  E.g., 
https://www.freedesktop.org/software/systemd/man/journalctl.html 
contains no occurrences of “bold”, “blue”, and “yellow” 
highlighting/emphasis as of now.  Only a generic “lines of level NOTICE 
and higher are highlighted” is stated.  As a result, the I am confused 
when interpreting the output of journalctl -b.


Please explain bold, blue, and yellow in the man pages.

Gratefully,
AlMa

Bug#932957: Please migrate Release Notes to reStructuredText

[Paul Gevers]

Hi,

On 20-05-2023 23:26, Holger Wansing wrote:

And the last point is the integration into the debhelper tools: I don't know
if it is required, to have the release-notes fit for building as a whole
package with sbuild or debuild or similar. Salsa tries to build it via CI
at every push, but currently fails.


It's possible I've misunderstood, but would be the goals here to be to get
the release-notes documentation built by CI, and also for it to be distributed
as a Debian package itself?

(someone who knows more may correct me, but I think it would be great to have
the package available for install using apt in addition to the website)


That was my first thought as well, yes.


At the price this may have been answered already, I think the current 
release notes are not packages because typically a lot of the relevant 
changes get updated in the weeks *around* the release. So one would have 
an outdated release notes. On top of that, most "issues to be aware of 
while upgrading" won't be so useful if you already upgraded. Having said 
that, I don't mind we make it a package, we just need to be clear of 
what the purpose is inside a release.


Also, on the topic of arch-specific builds, I not convinced it's worth a 
lot of effort. The amount of arch specific pieces is rather limited, so 
I wouldn't mind if we drop that altogether. Currently, we don't do a 
great service to people that need to support multiple architectures, 
because they need to *search* for the delta's, so I wouldn't be 
surprised if it is even better if we drop it.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037447: pipewire[…]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?

[AlMa]

On 14.06.23 18:26, Dylan Aïssi wrote:

As explained in the upstream bug, these warnings messages have been demote
to only log messages, nothing to worry about.


Thank you for a fast clarification!  The messages are displayed yellow 
and (semi-)bold in my log.  So I previously thought that the emphasis, 
paired with “Can't …” might need my attention and be a warning of some 
kind.  After all, if a piece of code complains that it can't do 
something, it probably shouldn't have tried it in first place (and, upon 
failure, warn the user).

Bug#1037941: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?

[AlMa]

Thank you for a fast reply.

On 14.06.23 18:06, Dylan Aïssi wrote:

What is the actual error you are facing?


If you wish to know which problems the computer has, then there are 
some, which may or may not be related.  For example, gnome now started 
using X11 instead of Wayland on my machine after the upgrade of Debian 
stable from v11 to v12. Further, I failed to set up any television 
application and to watch TV in Linux using a PCIe DVB tuner card so far. 
Moreover, audacity sometimes failed to record voice at proper speed (and 
sometimes succeeded). Finally, the machine had WiFi problems of various 
kinds (first connection took long after boot and connection got dropped 
long after boot). Though these problems do not look as if they were 
related to a camera or video recording at a first glance or directly, 
there are tons of error/failure/warning/missing/“cannot” messages in the 
log, and I start processing them beginning with the earlier ones so as 
to avoid considering followup errors (because later issues sometimes 
disappear after earlier issues get resolved).



"PipeWire's libcamera SPA missing or broken. libcamera not supported" is only
a log message (not even a warning) saying indeed the plugin provided by
pipewire-libcamera is not installed. SPA is for "Simple Plugin API" is the
pipewire's plugin API. If you don't know what is libcamera then you
probably don't need to install pipewire-libcamera. I can add it in suggested
package of wireplumber though, but again this is not an error only a log
message.


Got it, thank you a lot!  If you do think that pipewire-libcamera is 
indeed related, please feel free to add it as a suggested package. On my 
machine, the messages


SPA handle 'api.libcamera.enum.manager' could not be loaded; is it 
installed?

PipeWire's libcamera SPA missing or broken. libcamera not supported.

are not normally displayed but bold or semi-bold.  Moreover, they follow 
a yellow-colored


Failed to set scheduler settings: Operation not permitted.

(in my case, the part after the colon is “Die Operation ist nicht 
erlaubt” in German).  See the attached screenshot.  I thought, 
hypothetically, these three messages might be related.


Unfortunately, the manpage of journalctl doesn't explicitly say what 
yellow and (semi-)bold emphasis mean; instead we only see a generic term 
“highlighted” (which may or may not refer to yellow, (semi-)bold, and 
blue).  So I didn't really know whether the two (semi-)bold messages 
were really good or bad (and if they were bad, how bad).  Probably, the 
programmers wanted the reader to notice such emphasized messages. 
However, when I noticed them, I didn't really know how bad it was and 
what to do next.


Gratefully,
AlMa

Bug#1037697: [Debian-med-packaging] Bug#1037697: insighttoolkit5: ftbfs with GCC-13

[Étienne Mollier]

Control: tags -1 + patch
Control: forwarded -1 https://github.com/InsightSoftwareConsortium/ITK/pull/4041

Thanks Matthias for the report!

The relevant part of the log (from the download link) is:
> /<>/Modules/Filtering/MathematicalMorphology/include/itkMathematicalMorphologyEnums.h:41:14:
>  error: use of enum ‘Algorithm’ without previous declaration
>41 |   enum class Algorithm : uint8_t
>   |  ^

This very much looks fixed by the patch upstream already inlined
in their codebase some time ago to fix builds with gcc-13.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-on air: K2 - Infinite Voyage


signature.asc
Description: PGP signature

Bug#1037490: www.debian.org: clean up old files

[Cyril Brulebois]

(Cc-ing Adam for DSA following the ping about disk space earlier.)

Cyril Brulebois  (2023-06-13):
> Spotted while working on #1037479: we have a bunch of files around that
> are no longer useful, because relevant suites are EOL and archived, and
> have been dropped from the relevant config files, templates, etc.
> 
> They could probably be cleaned up, but I don't want to rush this kind of
> things, hence this bug report.

Apparently we're going to have to do something soon, since the recent
updates in picconi have led to a noticeable and worrisome bump in
storage used:

/dev/mapper/vg0-srv  246G  234G  822M  100%  /srv

Some cleanup happened in user directories, but I suppose it would make
sense to keep track of our disk space usage:

/dev/mapper/vg0-srv  246G  136G  99G58%  /srv

And beware, there are peaks during runs, with e.g. tmp/ filing up.

Also, the mirror (pkgmirror-csail) should like this as well given:

/dev/vdb 148G  129G  12G92%  /srv

See also graphs (with the usual guest authentication):
  https://munin.debian.org/debian.org/picconi.debian.org/df.html
  https://munin.debian.org/debian.org/pkgmirror-csail.debian.org/df.html


Our directory looked like this when I started:

426M./archive
200K./bin
268K./cache
8.0K./cgi-bin
29M ./conf
64K ./cron.d
8.0K./debian
116G./files
16M ./.git
133M./home
300K./lib
14M ./mail
8.4G./mirror
4.0K./po
196K./static
116K./templates
7.5G./tmp
2.6G./www
---
135Gtotal

I was thinking of getting rid of these:

$ du -sch $(find -name 'jessie*')
65M ./mirror/202306141247/www/jessie-backports
17M ./mirror/202306141247/www/source/jessie-backports
87M ./mirror/202306141247/www/source/jessie
3.5M./mirror/202306141247/www/source/jessie-updates
5.3M./mirror/202306141247/www/source/jessie-backports-sloppy
505M./mirror/202306141247/www/jessie
12M ./mirror/202306141247/www/jessie-updates
6.4M./mirror/202306141247/www/jessie-backports-sloppy
196K./archive/backports/jessie-backports
26M ./www/jessie-backports
5.8M./www/source/jessie-backports
11M ./www/source/jessie
2.3M./www/source/jessie-updates
3.4M./www/source/jessie-backports-sloppy
176M./www/jessie
3.1M./www/jessie-updates
4.0M./www/jessie-backports-sloppy

930Mtotal

and these:

$ du -sch $(find -name 'stretch*')
85M ./mirror/202306141247/www/source/stretch
5.1M./mirror/202306141247/www/source/stretch-backports-sloppy
15M ./mirror/202306141247/www/source/stretch-backports
3.4M./mirror/202306141247/www/source/stretch-updates
416M./mirror/202306141247/www/stretch
6.2M./mirror/202306141247/www/stretch-backports-sloppy
52M ./mirror/202306141247/www/stretch-backports
4.9M./mirror/202306141247/www/stretch-updates
11M ./www/source/stretch
3.4M./www/source/stretch-backports-sloppy
5.8M./www/source/stretch-backports
2.2M./www/source/stretch-updates
179M./www/stretch
3.9M./www/stretch-backports-sloppy
22M ./www/stretch-backports
2.6M./www/stretch-updates
-
813Mtotal

But those easy ones would only account for 1.7G combined, as mentioned
yesterday.

Searching for files containing but not starting with either jessie or
stretch, there are a lot of other things that looked like they could go
away:
 - filelists_*
 - filenames_*
 - new_package_info_*
 - package_names_*
 - packages_all_*
 - reverse_*
 - source_names_*
 - sources_all_*

and I expected no collateral damages.

To be on the safe side, I created two tarballs, one for jessie, one for
stretch, containing all those files, before removing them. I've compressed
them so that they take less space than actual files, moved them in a
directory that shouldn't be mirrored to pkgmirror-csail, and I've
scheduled their deletions in 6 months (via at), which should leave plenty
of time to restore them if needed, while making sure full cleanup happens
eventually.

pkg_user@picconi:/srv/packages.debian.org$ echo 'rm -rv 
/srv/packages.debian.org/obsolete/' | at 'now + 6 months'
warning: commands will be executed using /bin/sh
job 5 at Thu Dec 14 18:56:00 2023
pkg_user@picconi:/srv/packages.debian.org$ atq
5   Thu Dec 14 18:56:00 2023 a pkg_user

Also removed, a long obsolete file:

-rw--- 1 pkg_user pkg_maint 7.5G May  2  2021 tmp/sort01fAge

Not sure why this file stays behind, but at least the name is stable, so
the non-freed space is getting reclaimed when the next run starts:

-rw-r--r-- 1 pkg_user pkg_maint 14794575872 Jun 14 17:37 

Bug#1037958: ITP: golang-github-bep-mclib -- simple Go library to make it possible to run mkcert's main method

[Anthony Fok]

Package: wnpp
Severity: wishlist
Owner: Anthony Fok 

* Package name: golang-github-bep-mclib
  Version : 1.20400.20402-1
  Upstream Author : The mkcert Authors; Bjørn Erik Pedersen
* URL : https://github.com/bep/mclib
* License : Expat
  Programming Lang: Go
  Description : simple Go library to make it possible to run mkcert main 
method

 This is a simple Go library to make it possible to run mkcert's
 (https://github.com/FiloSottile/mkcert) main method.
 .
 The script that updates the internal package does no logic changes to
 the source; it simply
 .
  1. Renames the main package to internal.
  2. Renames the main func to RunMain
  3. Replaces any log.Fatal with panic to allow us to handle the errors.
  4. Exports getCAROOT().
 .
 For more advanced library usage, see this issue
 (https://github.com/FiloSottile/mkcert/issues/45).

Reason for packaging: Needed by hugo 0.113.0 and up

Bug#1033130: gcc-snapshot: FTBFS on hppa - sys/mman.h: No such file or directory

[John David Anglin]

On 2023-06-14 1:00 p.m., Matthias Klose wrote:

wondering if configuring with --disable-libgcc would help?

I don't need to do this when building the hppa64 gcc target by itself.

I think configure must be finding the header in 
/usr/include/hppa-linux-gnu/sys/mman.h.
We don't have any headers for hppa64 installed at this time.

Something seems to have changed in the build mechanism between gcc-12 and 
gcc-13.

I have a debian non-buildd build of gcc-13 going.  Maybe it will help to find 
issue.

--
John David Anglin  dave.ang...@bell.net

Bug#1037946: mmdebstrap: Create /var/lib/dpkg/available for Debian releases <=buster

[Guillem Jover]

Hi!

On Wed, 2023-06-14 at 19:09:35 +0200, Johannes Schauer Marin Rodrigues wrote:
> Quoting Michael Prokop (2023-06-14 17:19:37)
> > since version 1.20.0, dpkg no longer creates /var/lib/dpkg/available (see
> > #647911).
> 
> I see that the bug talks about 1.20.0 but I've had code creating
> /var/lib/dpkg/available in mmdebstrap for a while and determined that it 
> wasn't
> necessary anymore since dpkg 1.17.11. Did you do practical tests or are you
> only basing your analysis on that bug?
> 
> I'm quite certain about the version requirement because I did tests using
> debbisect and using the suggestion below I'm able to create chroots for all of
> unstable since 2006-08-10.

So just to clarify, old and new dpkg in normal conditions works fine
for a long time when the available file is not present (since 1.17.11 as
you point out). The problem here as hinted at below is that apt tries to
set the package selections via «dpkg --set-selections» after having
refreshed the available file via «dpkg --merge-avail» where both these
commands fail if the available file is missing with versions earlier
than 1.20.0.

> > But on Debian releases until and including buster, dpkg fails to operate 
> > with
> > e.g. `dpkg --set-selections`, if /var/lib/dpkg/available doesn't exist:
> > 
> > | The following NEW packages will be installed:
> > | [...]
> > | debconf: delaying package configuration, since apt-utils is not installed
> > | dpkg: error: failed to open package info file '/var/lib/dpkg/available' 
> > for reading: No such file or directory
> > 
> > My workaround to work around this is to run:
> > 
> >   chroot "${TARGET}" /usr/lib/dpkg/methods/apt/update /var/lib/dpkg
> > 
> > As mmdebstrap seems to rely on dpkg of the host system, it would be
> > nice if mmdebstrap could ensure to create an environment where apt/dpkg of
> > the installed system doesn't stumble upon. :)
> 
> this already exists as a hook. :)

> Try running mmdebstrap with
> 
> --hook-dir=/usr/share/mmdebstrap/hooks/jessie-or-older
> 
> which will unconditionally do certain things only necessary for old releases.
> 
> If you instead use
> 
> --hook-dir=/usr/share/mmdebstrap/hooks/maybe-jessie-or-older
> 
> some detection code will only run the hook if necessary (in case you do not
> know upfront which release you are creating a chroot for).

Yeah I mentioned this also to Mika, but also encouraged him to file
this report as I think it might make sense for these hooks to be
adapted to cover up to buster out of the box.

Initially I thought that perhaps only the variants that end up with
apt installed so that it can work correctly, but given that with older
dpkg versions some of these actions will always fail, then perhaps it
makes sense to still add those unconditionally so that users do not
need to create the file manually if they use the other dpkg actions.

(Hope this clarifies things! :)

Thanks,
Guillem

Bug#1037956: mailman3-web: SQL Syntax error installing mailman3-web on mariadb

[Falk Hackenberger]

Package: mailman3-web
Version: 0+20200530-2.1
Severity: important

Dear Maintainer,

if I install mailman3-web with mariadb/mysql choise I get this the 
following output:




Determining localhost credentials from /etc/mysql/debian.cnf: succeeded.
dbconfig-common: writing config to /etc/dbconfig-common/mailman3-web.conf

Creating config file /etc/dbconfig-common/mailman3-web.conf with new version
checking privileges on database mailman3web for mailman3web@localhost: user
creation needed.
granting access to database mailman3web for mailman3web@localhost: success.
verifying access for mailman3web@localhost: success.
creating database mailman3web: success.
verifying database mailman3web exists: success.
dbconfig-common: flushing administrative password

Creating config file /etc/mailman3/mailman-web.py with new version
/usr/lib/python3/dist-packages/django_q/conf.py:139: UserWarning: Retry and
timeout are misconfigured. Set retry larger than timeout,
failure to do so will cause the tasks to be retriggered before
completion.
See https://django-q.readthedocs.io/en/latest/configure.html#retry for
details.
warn(
System check identified some issues:

WARNINGS:
django_mailman3.MailDomain: (models.W042) Auto-created primary key used when
not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
DjangoMailman3Config.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
django_mailman3.Profile: (models.W042) Auto-created primary key used 
when not

defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
DjangoMailman3Config.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Attachment: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Email: (models.W042) Auto-created primary key used when not 
defining

a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Favorite: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.LastView: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.MailingList: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Profile: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Tag: (models.W042) Auto-created primary key used when not 
defining a

primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Tagging: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Thread: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used 
when not

defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 

Bug#1037957: nextcloud-desktop: XFCE sessions cause broken behavior after 11 -> 12 upgrade

[Patrick Hibbs]

Package: nextcloud-desktop
Version: 3.7.3-1
Severity: normal
X-Debbugs-Cc: hibbsncc1...@gmail.com

Dear Maintainer,

After upgrading to Debian Bookworm from Bullseye, nextcloud-desktop erroneously
opens it's main popup window in the dead center of the screen when a user logs
in to an XFCE session.

Closing the window normally, by clicking outside of the window, does not work.

Instead the user must either input the Alt-F4 combination. Or click on the tray
icon once to move the window back under the tray icon, (Where it should appear
normally.) and again to close the window. This has to be done on every login
regardless of reboots.

Also, if the user has configured items to be excluded from sync (such as files
that are too big for the destination, server files on external storage, etc.)
nextcloud-desktop will also start sending notifications about them prompting
the user to configure the app despite having already made their configuration
choice. This too happens on every login, but can be disabled by disabling
notifications from the app.

As an additional note, when I upgraded from Bullseye, the nextcloud-desktop
package was uninstalled due to a package conflict. I reinstalled it after the
upgrade was complete without the conflict occuring again.


-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (100, 
'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

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

Versions of packages nextcloud-desktop depends on:
ii  libc6  2.36-9
ii  libcloudproviders0 0.3.1-2
ii  libgcc-s1  12.2.0-14
ii  libglib2.0-0   2.74.6-2
ii  libkf5archive5 5.103.0-1
ii  libnextcloudsync0  3.7.3-1
ii  libqt5core5a   5.15.8+dfsg-11
ii  libqt5dbus55.15.8+dfsg-11
ii  libqt5gui5 5.15.8+dfsg-11
ii  libqt5keychain10.13.2-5
ii  libqt5network5 5.15.8+dfsg-11
ii  libqt5qml5 5.15.8+dfsg-3
ii  libqt5quick5   5.15.8+dfsg-3
ii  libqt5quickcontrols2-5 5.15.8+dfsg-2
ii  libqt5sql5-sqlite  5.15.8+dfsg-11
ii  libqt5svg5 5.15.8-3
ii  libqt5webenginecore5   5.15.13+dfsg-1~deb12u1
ii  libqt5webenginewidgets55.15.13+dfsg-1~deb12u1
ii  libqt5widgets5 5.15.8+dfsg-11
ii  libstdc++6 12.2.0-14
ii  nextcloud-desktop-common   3.7.3-1
ii  nextcloud-desktop-l10n 3.7.3-1
ii  qml-module-qt-labs-platform5.15.8+dfsg-2
ii  qml-module-qtgraphicaleffects  5.15.8-2
ii  qml-module-qtqml   5.15.8+dfsg-3
ii  qml-module-qtqml-models2   5.15.8+dfsg-3
ii  qml-module-qtquick-controls2   5.15.8+dfsg-2
ii  qml-module-qtquick-dialogs 5.15.8-2
ii  qml-module-qtquick-layouts 5.15.8+dfsg-3
ii  qml-module-qtquick-window2 5.15.8+dfsg-3
ii  qml-module-qtquick25.15.8+dfsg-3

Versions of packages nextcloud-desktop recommends:
ii  nextcloud-desktop-doc  3.7.3-1

nextcloud-desktop suggests no packages.

-- no debconf information

Bug#1037954: please ship upstream themes/

[Birger Schacht]

See https://packages.debian.org/unstable/foot-themes ;)

PS: severity "critical"?

On 6/14/23 20:09, Antoine Beaupre wrote:

Package: foot
Version: 1.13.1-2
Severity: critical
X-Debbugs-Cc: please ship upstream themes

Upstream has a bunch of themes in the source tree. Those can be
included with a simple, say:

[main]
include=/usr/share/foot/themes/gruvbox-light.ini

yet we don't ship those themes! Wouldn't it be great to have those
around?

I'm not sure about /usr/share/foot, but i'm pretty sure it's a good
idea to ship them. :)


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

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

Versions of packages foot depends on:
ii  foot-terminfo   1.13.1-2
ii  libc6   2.36-9
ii  libfcft43.1.5-3
ii  libfontconfig1  2.14.1-4
ii  libpixman-1-0   0.42.2-1
ii  libutf8proc22.8.0-1
ii  libwayland-client0  1.21.0-1
ii  libwayland-cursor0  1.21.0-1
ii  libxkbcommon0   1.5.0-1

foot recommends no packages.

Versions of packages foot suggests:
pn  foot-themes  

-- no debconf information

Bug#1037952: rasdaemon(1) and /etc/default/rasdaemon point to /etc/sysconfig/rasdaemon which doesn't exist on Debian

[наб]

one day i'll attach the patches i say i'm gonna
From 7a86b08751735cfd0afff941e5f7b8bd90ea1944 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=BD=D0=B0=D0=B1?= 
Date: Wed, 14 Jun 2023 19:23:16 +0200
Subject: [PATCH 1/3] Remove /etc/sysconfig reference from
 /etc/default/rasdaemon
X-Mutt-PGP: OS

---
 debian/control   | 2 +-
 debian/rasdaemon.install | 2 --
 debian/rules | 2 ++
 3 files changed, 3 insertions(+), 3 deletions(-)
 mode change 100755 => 100644 debian/rasdaemon.install

diff --git a/debian/control b/debian/control
index 4a79b1b..c827820 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: admin
 Priority: optional
 Maintainer: Taihsiang Ho (tai271828) 
 Build-Depends: debhelper (>= 12), quilt, libsqlite3-dev, libgettextpo-dev,
- autoconf, dh-exec
+ autoconf
 Standards-Version: 4.5.0
 Homepage: https://salsa.debian.org/tai271828/rasdaemon
 Vcs-Git: https://salsa.debian.org/tai271828/rasdaemon.git
diff --git a/debian/rasdaemon.install b/debian/rasdaemon.install
old mode 100755
new mode 100644
index 6acf933..f830f85
--- a/debian/rasdaemon.install
+++ b/debian/rasdaemon.install
@@ -1,4 +1,2 @@
-#!/usr/bin/dh-exec
 misc/rasdaemon.service	/lib/systemd/system
 misc/ras-mc-ctl.service	/lib/systemd/system
-misc/rasdaemon.env => /etc/default/rasdaemon
diff --git a/debian/rules b/debian/rules
index cbde216..9082553 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,3 +19,5 @@ override_dh_install:
 	dh_installsystemd --name=rasdaemon rasdaemon.service
 	dh_installsystemd --name=ras-mc-ctl ras-mc-ctl.service
 	rm -rf $(CURDIR)/debian/rasdaemon/usr/include
+	mkdir -p $(CURDIR)/debian/rasdaemon/etc/default
+	sed '\:/etc/sysconfig:d' < $(CURDIR)/misc/rasdaemon.env > $(CURDIR)/debian/rasdaemon/etc/default/rasdaemon
-- 
2.39.2

From 6f63004a8bff132549482815aeda0df382ec8351 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=BD=D0=B0=D0=B1?= 
Date: Wed, 14 Jun 2023 19:30:56 +0200
Subject: [PATCH 2/3] Fix config file path in rasdaemon(8)
X-Mutt-PGP: OS

---
 debian/patches/rasdaemon.8-config-path.patch | 19 +++
 debian/patches/series|  1 +
 2 files changed, 20 insertions(+)
 create mode 100644 debian/patches/rasdaemon.8-config-path.patch

diff --git a/debian/patches/rasdaemon.8-config-path.patch b/debian/patches/rasdaemon.8-config-path.patch
new file mode 100644
index 000..798d93f
--- /dev/null
+++ b/debian/patches/rasdaemon.8-config-path.patch
@@ -0,0 +1,19 @@
+diff --git a/man/rasdaemon.8.in b/man/rasdaemon.8.in
+index 833c8e1..59affb4 100644
+--- a/man/rasdaemon.8.in
 b/man/rasdaemon.8.in
+@@ -62,12 +62,8 @@ .SH OPTIONS
+ .BI "--version"
+ Print the program version and exit.
+ 
+-.SH CONFIG FILE
+-
+-The \fBrasdaemon\fR program supports a config file to set rasdaemon systemd service
+-environment variables. By default the config file is read from /etc/sysconfig/rasdaemon.
+-
+-The general format is environmentname=value.
++.SH FILES
++.B /etc/default/rasdaemon
+ 
+ .SH SEE ALSO
+ \fBras-mc-ctl\fR(8)
diff --git a/debian/patches/series b/debian/patches/series
index 763d6ea..bbea539 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -3,3 +3,4 @@ systemd-targets.patch
 add-man-options.patch
 systemd-requires.patch
 ras-mc-ctl.patch
+rasdaemon.8-config-path.patch
-- 
2.39.2

From d72612c57c3883588fd7c1cda9d4f2be899a5ece Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=BD=D0=B0=D0=B1?= 
Date: Wed, 14 Jun 2023 19:31:51 +0200
Subject: [PATCH 3/3] Fix empty line before heading in manuals
X-Mutt-PGP: OS

---
 debian/patches/manual-spacing-before-TH.patch | 26 +++
 debian/patches/series |  1 +
 2 files changed, 27 insertions(+)
 create mode 100644 debian/patches/manual-spacing-before-TH.patch

diff --git a/debian/patches/manual-spacing-before-TH.patch b/debian/patches/manual-spacing-before-TH.patch
new file mode 100644
index 000..14e3089
--- /dev/null
+++ b/debian/patches/manual-spacing-before-TH.patch
@@ -0,0 +1,26 @@
+diff --git a/man/ras-mc-ctl.8.in b/man/ras-mc-ctl.8.in
+index 54a8a3a..5a790f4 100644
+--- a/man/ras-mc-ctl.8.in
 b/man/ras-mc-ctl.8.in
+@@ -23,7 +23,7 @@
+ .\" with this program; if not, write to the Free Software Foundation, Inc.,
+ .\" 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA.
+ .\"
+-
++.
+ .TH RAS-MC-CTL 8 "@META_DATE@" "@META_ALIAS@" "RAS memory controller admin utility"
+ 
+ .SH NAME
+diff --git a/man/rasdaemon.8.in b/man/rasdaemon.8.in
+index 59affb4..1beff9c 100644
+--- a/man/rasdaemon.8.in
 b/man/rasdaemon.8.in
+@@ -17,7 +17,7 @@
+ .\" with this program; if not, write to the Free Software Foundation, Inc.,
+ .\" 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA.
+ .\"
+-
++.
+ .TH RASDAEMON 8 "@META_DATE@" "@META_ALIAS@" "RAS memory controller admin utility"
+ 
+ .SH NAME
diff 

Bug#1037955: egctl: New version 0.3 available

[Wolfram Sang]

Package: egctl
Version: 1:0.1-1.1
Severity: wishlist

Dear Maintainer,

upstream has now version 0.3 available. It adds support for the WLAN
variant of the device which is the mainly available one these days.
Also, the README now mentions how to overload PREFIX, so the Debian
patch could be dropped, I assume.

Thanks and happy hacking,

   Wolfram


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

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

Versions of packages egctl depends on:
ii  libc6  2.36-6

egctl recommends no packages.

egctl suggests no packages.

-- no debconf information

Bug#1033503: dgit autopkgtests broken by git 2.40 [and 2 more messages]

[Paul Gevers]

Control: severity -1 serious

Hi,

On Sun, 9 Apr 2023 12:37:16 +0100 Ian Jackson 
 wrote:

After the bookworm release, the severity of this bug should probably
be raised.  That will put this issue back on my radar.


Doing so now, thanks.

Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037954: please ship upstream themes/

[Antoine Beaupre]

Package: foot
Version: 1.13.1-2
Severity: critical
X-Debbugs-Cc: please ship upstream themes

Upstream has a bunch of themes in the source tree. Those can be
included with a simple, say:

[main]
include=/usr/share/foot/themes/gruvbox-light.ini

yet we don't ship those themes! Wouldn't it be great to have those
around?

I'm not sure about /usr/share/foot, but i'm pretty sure it's a good
idea to ship them. :)


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

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

Versions of packages foot depends on:
ii  foot-terminfo   1.13.1-2
ii  libc6   2.36-9
ii  libfcft43.1.5-3
ii  libfontconfig1  2.14.1-4
ii  libpixman-1-0   0.42.2-1
ii  libutf8proc22.8.0-1
ii  libwayland-client0  1.21.0-1
ii  libwayland-cursor0  1.21.0-1
ii  libxkbcommon0   1.5.0-1

foot recommends no packages.

Versions of packages foot suggests:
pn  foot-themes  

-- no debconf information

Bug#1037953: darcs: frequent segmentation fault

[Tirifto]

Package: darcs
Version: 2.16.5-1
Severity: important
X-Debbugs-Cc: tiri...@posteo.cz

Dear Maintainer,

when trying to run different commands with darcs, it often happens that the
program crashes right away, reporting this segmentation fault:

  darcs: mmap 4096 bytes at (nil): Cannot allocate memory
  darcs: Try specifying an address with +RTS -xm -RTS
  Segmentation fault

This leaves a ‘lock’ file in the ‘_darcs’ directory. I must remove the file to
be able to try again. Trying again works sometimes.

Running ‘darcs record’ sometimes fails, but retrying can usually make it work.
At one point, the program only crashed after I had entered a patch description.
At the moment, I am unable to run ‘darcs amend’ no matter how many times I try.
I'm not seeing any pattern to the crashes.

I should note that the problem might not be in Debian’s build of darcs, but
rather in other parts of Debian and how they interact with darcs. I tried
uninstalling Debian's darcs and installing darcs using the Guix package manager
instead, but the issue has persisted. I have no clue what might be causing it.


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

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

Versions of packages darcs depends on:
ii  libc62.36-9
ii  libcurl3-gnutls  7.88.1-10
ii  libffi8  3.4.4-1
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libtinfo66.4-4
ii  zlib1g   1:1.2.13.dfsg-1

darcs recommends no packages.

darcs suggests no packages.

-- no debconf information

Bug#1037952: rasdaemon(1) and /etc/default/rasdaemon point to /etc/sysconfig/rasdaemon which doesn't exist on Debian

[наб]

Package: rasdaemon
Version: 0.6.8-1.1
Severity: minor
Tags: patch

Dear Maintainer,

rasdaemon(8) says
  CONFIG FILE
 The rasdaemon program supports a config file to set rasdaemon systemd 
service environment variables. By default the config file is read from 
/etc/sysconfig/ras‐
 daemon.

 The general format is environmentname=value.
the weirdness of that aside, /etc/sysconfig/rasdaemon doesn't exist.
/etc/default/rasdaemon does, however, and says:
  # Page Isolation
  # Note: Run-time configuration is unsupported, service restart needed.
  # Note: this file should be installed at /etc/sysconfig/rasdaemon
  
  # Specify the threshold of isolating buggy pages.
  #
  # Format:
  #   [0-9]+[unit]
  # Notice: please make sure match this format, rasdaemon will use default 
value for exception input cases.
  #
  # Supported units:
  # PAGE_CE_REFRESH_CYCLE: D|d (day), H|h (hour), M|m (min), default is in hour
  # PAGE_CE_THRESHOLD: K|k (x1000), M|m (x1000k), default is none
  #
  # The two configs will only take no effect when PAGE_CE_ACTION is "off".
  PAGE_CE_REFRESH_CYCLE="24h"
  PAGE_CE_THRESHOLD="50"
  
  # Specify the internal action in rasdaemon to exceeding a page error 
threshold.
  #
  # off  no action
  # account  only account errors
  # soft try to soft-offline page without killing any processes
  #  This requires an uptodate kernel. Might not be successfull.
  # hard try to hard-offline page by killing processes
  #  Requires an uptodate kernel. Might not be successfull.
  # soft-then-hard   First try to soft offline, then try hard offlining.
  # Note: default offline choice is "soft".
  PAGE_CE_ACTION="soft"

Again, it shouldn't on Debian because the service says
  $ systemctl cat rasdaemon.service
  # /lib/systemd/system/rasdaemon.service
  [Unit]
  Description=RAS daemon to log the RAS events
  # only needed when not running in foreground (--foreground | -f)
  #After=syslog.target
  
  [Service]
  EnvironmentFile=/etc/default/rasdaemon
  ExecStart=/usr/sbin/rasdaemon -f -r
  ExecStartPost=/usr/sbin/rasdaemon --enable
  ExecStop=/usr/sbin/rasdaemon --disable
  Restart=on-abort
  
  [Install]
  WantedBy=multi-user.target

To that end, I'm attaching three patches (also at Salsa as
 https://salsa.debian.org/tai271828/rasdaemon-sandbox-01/-/merge_requests/1):
  * fixing /etc/default/rasdaemon
  * fixing rasdaemon(8) by replacing that whole section with
  .SH FILES
  .B /etc/default/rasdaemon
  * fixing rasdaemon(8) and ras-mc-ctl(8) by removing the empty line
from before .TH, which removes the empty line before the heading

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

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

Versions of packages rasdaemon depends on:
ii  init-system-helpers  1.65.2
ii  libc62.36-9
ii  libdbd-sqlite3-perl  1.72-1
ii  libsqlite3-0 3.40.1-2
ii  perl 5.36.0-7
ii  sqlite3  3.40.1-2

rasdaemon recommends no packages.

rasdaemon suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1037174: RFS: damo/1.8.4-1 [ITP] -- Data Access Monitoring Operator

[Michel Alexandre Salim]

Hi Adam,

Thanks for all the feedback! I've addressed them all and updated to
1.8.5 which has been released in the meantime. Added comments inline - and
the additional question at the end.

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

https://salsa.debian.org/python-team/packages/damo/-/tree/44d7ecd2bf2af277e2b93be82c32ffcb242f5d17

On Mon, Jun 12, 2023 at 05:15:24PM +0200, Adam Borowski wrote:
> On Tue, Jun 06, 2023 at 09:45:25PM -0500, Michel Alexandre Salim wrote:
> 
> Hi!
> The commands you run for % targets will fail badly if ran in parallel, and
> that's the default these days.  Please run that only once, eg from
> override_dh_auto_configure (as that's a target that's run early).
> 
Fixed, thanks

> Other nice to have bits:
>  * the description doesn't say what DAMON is, even "Data Access Monitoring
>Operator" doesn't shed much light
Added description, thank you!

>  * a command-line tool really should have a man page
Added a manpage using help2man and checked in the generator script

One question: is it alright to mark the architecture here as "all"? The
code itself is pure Python, but it depends on functionality of the Linux
kernel. `linux-all` is not a valid target, and if I mark it as
`linux-any` it will... cause buildd to unnecessarily build this on each
architecture, right?

Best regards,

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


signature.asc
Description: PGP signature

Bug#1034904: ImportError: cannot import name 'util' from 'distutils' (/usr/lib/python3.11/distutils/__init__.py)

[Christophe Alonso]

Installing python3-distutils solved the problem here. May be diffuse 
should depend on this package as well.




OpenPGP_0xF1596A7FBB6E093A.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037946: mmdebstrap: Create /var/lib/dpkg/available for Debian releases <=buster

[Michael Prokop]

Hi,

* Johannes Schauer Marin Rodrigues [Wed Jun 14, 2023 at 07:09:35PM +0200]:
> Quoting Michael Prokop (2023-06-14 17:19:37)
> > since version 1.20.0, dpkg no longer creates /var/lib/dpkg/available (see
> > #647911).
> 
> I see that the bug talks about 1.20.0 but I've had code creating
> /var/lib/dpkg/available in mmdebstrap for a while and determined that it 
> wasn't
> necessary anymore since dpkg 1.17.11. Did you do practical tests or are you
> only basing your analysis on that bug?

This showed up in an actual environment, where we automatically
deploy systems on a daily base. The deployment of a buster based
system failed as soon as we upgraded the host system (a Grml based
live system) to bookworm, which provides dpkg v1.21.22 and
mmdebstrap v1.3.5-7. (Deploying bullseye where dpkg v1.20.12 exists
works fine, FTR)

> I'm quite certain about the version requirement because I did tests using
> debbisect and using the suggestion below I'm able to create chroots for all of
> unstable since 2006-08-10.

mmdebstrap itself does *not* fail, but the installation of e.g. the
`nullmailer` package inside the target buster environment then fails:

| Error: Execution of '/usr/bin/apt-get -q -y -o 
DPkg::Options::=--force-confold install nullmailer' returned 100: Reading 
package lists...
| Building dependency tree...
| Reading state information...
| The following packages were automatically installed and are no longer 
required:
|   libevent-2.1-6 libgnutls-dane0 libunbound8
| Use 'apt autoremove' to remove them.
| The following packages will be REMOVED:
|   exim4-base exim4-config exim4-daemon-light
| The following NEW packages will be installed:
|   nullmailer
| 0 upgraded, 1 newly installed, 3 to remove and 0 not upgraded.
| Need to get 109 kB of archives.
| After this operation, 3560 kB disk space will be freed.
| [...]
| [master dbda30d] saving uncommitted changes in /etc prior to apt run
|  6 files changed, 115 insertions(+), 575 deletions(-)
|  rewrite locale.gen (99%)
|  create mode 100644 needrestart/conf.d/ignore.conf
| debconf: delaying package configuration, since apt-utils is not installed
| dpkg: error: failed to open package info file '/var/lib/dpkg/available' for 
reading: No such file or directory
| Fetched 109 kB in 0s (542 kB/s)
| E: Sub-process dpkg --set-selections returned an error code (2)
| E: Couldn't record the approved state changes as dpkg selection states[0m

(FTR, this is part of an automated puppet run)

I can manually reproduce the problem with:

| # mmdebstrap buster /tmp/buster
| [...]
| # chroot /tmp/buster apt update
| [...]
| # chroot /tmp/buster apt install nullmailer
| [...]
| # chroot /tmp/buster apt purge nullmailer
| [...]
| perl: warning: Falling back to the standard locale ("C").
| locale: Cannot set LC_CTYPE to default locale: No such file or directory
| locale: Cannot set LC_MESSAGES to default locale: No such file or directory
| locale: Cannot set LC_ALL to default locale: No such file or directory
| dpkg: error: failed to open package info file '/var/lib/dpkg/available' for 
reading: No such file or directory
| E: Sub-process dpkg --set-selections returned an error code (2)
| E: Couldn't record the approved state changes as dpkg selection states

> > But on Debian releases until and including buster, dpkg fails to operate 
> > with
> > e.g. `dpkg --set-selections`, if /var/lib/dpkg/available doesn't exist:
> > 
> > | The following NEW packages will be installed:
> > | [...]
> > | debconf: delaying package configuration, since apt-utils is not installed
> > | dpkg: error: failed to open package info file '/var/lib/dpkg/available' 
> > for reading: No such file or directory
> > 
> > My workaround to work around this is to run:
> > 
> >   chroot "${TARGET}" /usr/lib/dpkg/methods/apt/update /var/lib/dpkg
> > 
> > As mmdebstrap seems to rely on dpkg of the host system, it would be
> > nice if mmdebstrap could ensure to create an environment where apt/dpkg of
> > the installed system doesn't stumble upon. :)
> 
> this already exists as a hook. :)
> 
> Try running mmdebstrap with
> 
> --hook-dir=/usr/share/mmdebstrap/hooks/jessie-or-older
> 
> which will unconditionally do certain things only necessary for old releases.

This indeed solves the problem, /var/lib/dpkg/available exists in
the target system then (as empty file, FTR).

> If you instead use
> 
> --hook-dir=/usr/share/mmdebstrap/hooks/maybe-jessie-or-older
> 
> some detection code will only run the hook if necessary (in case you do not
> know upfront which release you are creating a chroot for).

This does *not* help/work, though, FYI.

(FTR, we already have a local workaround, I just thought that it
would make sense to have a decent and nice out-of-the-box experience
also for other users. :))

Thanks! :)

regards
-mika-


signature.asc
Description: PGP signature

Bug#1037932: transition: python-resolvelib

[Sebastian Ramacher]

Control: reassign -1 src:ansible-core 2.14.3-1 
Control: severity -1 serious
Control: tags -1 sid trixie
Control: retitle -1 ansible-core: requires update for python3-resolvelib 1.x

On 2023-06-14 14:51:03 +0100, Simon McVittie wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: python-resolve...@packages.debian.org, 
> ansible-c...@packages.debian.org
> Control: affects -1 + src:ansible-core src:python-resolvelib
> 
> python3-resolvelib 1.x makes ansible-core uninstallable; reporting this
> as a transition to get it on the release team's radar.

It's only one package. So let's turn this into an RC bug against
ansible-core.

Cheers
-- 
Sebastian Ramacher

Bug#1037951: RM: manpages-pt -- RoQA; Transitional package, superseded by manpages-pt-br

[Helge Kreutzmann]

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

manpages-pt contained very old man pages (from almost 20 years ago,
i.e. 2004). The last maintainer upload happend around 2009. 

With the help of upstream (Mario Blättermann) we integrated the
translations into manpages-l10n, namely manpages-pt-br. While pt-br
and pt are different, they are close enough for this to be feasible.
This was confirmed by Mario.

During the bookworm development cycle we transformed manpages-pt into
a dummy package which (by dependency) pulls in manpages-pt-br.

So now that bookworm has been released, manpage-pt is no longer
necessary. Please remove this transitional package from the archive.

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


signature.asc
Description: PGP signature

Bug#1037945: bookworm-pu: package aide/aide_0.18.3-1+deb12u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2023-06-14 at 17:27 +0200, Marc Haber wrote:
> this pre-upload request for the aide package is filed to ask for
> guidance whether this package is suitable for bookworm-updates.

Do you actually mean bookworm-updates here (i.e. pushed to users in
advance of 12.1), or simply (bookworm-)proposed-updates, therefore
reaching users with the release of 12.1?

>  I have
> never done this before and am open for suggestions to improve and for
> documentation pointers. I haven't found the bookwork point release
> policy yet, for example.
> 

There's been no substantial changes to the policy for a while. The
"workflow" section of 
https://lists.debian.org/debian-devel-announce/2019/08/msg0.html
(as linked from https://release.debian.org/ ) is still basically
appropriate, and the basis of 
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions

(The "must be severity:important" bit isn't strictly enforced, more a
guide as to the expected impact of the issue being resolved.)

Maybe we should re-post it.

I'd be interested in seeing a binary debdiff (for an arbitrary
architecture) with "--controlfiles=ALL" to see the changes made to the
maintainer scripts, but overall I think this looks OK.

One small comment:

+if dpkg --compare-versions "$2" le 0.18.3-1; then
+# we're updating from 0.18-3 or earlier, chown aideinit logs

That should presumably be "from 0.18.3".

Regards,

Adam

Bug#1037950: general: I had VBoxService installed in /sbin, but the program did not start

[Bert Nijhof]

Package: general
Severity: normal
X-Debbugs-Cc: lammert.nij...@gmail.com

Dear Maintainer,

Virtualbox installed Guest Additions and I use VBoxService in Conky. It did not
work. Also when I type it in the terminal the program does not start, while in
all other distros it works. Here I had to start it like /sbin/VBoxService, so
Debian does not look for (new) executables or (new) links to executables in
/sbin.

Bug#1035671: [ftpmas...@ftp-master.debian.org: Accepted hoteldruid 3.0.5-1 (source) into unstable]

[Salvatore Bonaccorso]

Source: hoteldruid
Source-Version: 3.0.5-1

- Forwarded message from Debian FTP Masters 
 -

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 16 Mar 2023 09:34:09 +
Source: hoteldruid
Architecture: source
Version: 3.0.5-1
Distribution: unstable
Urgency: low
Maintainer: Marco Maria Francesco De Santis 
Changed-By: Marco Maria Francesco De Santis 
Changes:
 hoteldruid (3.0.5-1) unstable; urgency=low
 .
   * New upstream release (Fixes CVE-2023-29839)
   * debian/control: updated Standards-Version
   * debian/control: added recommendation on php-mbstring previously
 included in core php packages
   * fixed icon name in desktop file
   * fixed launchable field in appdata file
Checksums-Sha1:
 ff8d76fa6206e2b967c17c9d0130fbb3df7e1f64 1932 hoteldruid_3.0.5-1.dsc
 b57149b42691fae826d9f203e891db092e78e451 2036258 hoteldruid_3.0.5.orig.tar.gz
 a8bc4f885b09073c49065a9fbf96934c9c302f52 833 hoteldruid_3.0.5.orig.tar.gz.asc
 092b7607f20499507f7265727fe151ed0f47c4ea 43580 hoteldruid_3.0.5-1.debian.tar.xz
 80aa8f2fe74cba129fcd53c17d251d59bdb0c316 5333 
hoteldruid_3.0.5-1_source.buildinfo
Checksums-Sha256:
 af799f742b5f0af6c4cc5f6e876b9f6c401a9d06d43d81d38486467917abefbb 1932 
hoteldruid_3.0.5-1.dsc
 07e9c13bd0d1d278b7f4e617d4485dc4bc918483943fa26709c0165307e93ece 2036258 
hoteldruid_3.0.5.orig.tar.gz
 f1e0f9a996c8f7ac6ae66b8b683db6a766ee32fa9e4660870556f2819c8559d8 833 
hoteldruid_3.0.5.orig.tar.gz.asc
 e02759b97a2b03776ad34eeca5ef297fc3bc172331c29663847d2c8728ab7a6b 43580 
hoteldruid_3.0.5-1.debian.tar.xz
 ecaea2a0d87f9fcccfe01faf17b3837d0dd0c7d54b76070624193ec1a3d6c81b 5333 
hoteldruid_3.0.5-1_source.buildinfo
Files:
 1773dfcac94990d05976dffb9839707e 1932 web optional hoteldruid_3.0.5-1.dsc
 2c59d726195e3802366e7e6a9f879770 2036258 web optional 
hoteldruid_3.0.5.orig.tar.gz
 b8d5548eb42f24522f84f9c3b17ce48a 833 web optional 
hoteldruid_3.0.5.orig.tar.gz.asc
 704e4cf4c51f8b9c4a0804102cb54003 43580 web optional 
hoteldruid_3.0.5-1.debian.tar.xz
 f0a342070d28d784467a4043b9268505 5333 web optional 
hoteldruid_3.0.5-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmSJtw0QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFNp2DACH2tFXr5ZUn7v2QKkJYpEKZmXi08yuYtMO
3IWPAkrbfARbWqOrI7JHrjJg2HMmwhCPXot8zaLvy8oBdOvJjUB660SwCKL/IG5w
8bxoQqTd2raToGOFdGW+p77b2liTdh04JsycGlOgEUK9TwdNm22Y69PKCMIlgmO+
hsN1cC8xaCpRqDtib7tJKjNTgcVnnqKGsqnFROg5Ps/SPKHD9Mt3Cq48+Qszel6I
cEbqZibAd5jKhRNVqXuW0Wp+C1yNCSIhEsZ4OdPX1MJYg5ave1RZ5XcqMIGEhadQ
cXQ7k1gjdmSQQHo/p/CH65gcxEoEW8hvm7sCCsEBnLqKhSewVlQj3MKmo6d2OrgD
a+Fq7O2Fj2O9g23UMasS5zNGewzSumHkUlz1nGjZMxzBdWgEbL3SY8gqN7FJkc4/
7/6zhuWJjVV0pRrLQ/02SuFl4kWtdMYNgQtcvxZ/6Wojde0Bvl/xY+qTeKmH0QmY
4Ge4gYnnKQXMDuxi1nT1N2PQ+XbPaaE=
=qAKP
-END PGP SIGNATURE-


- End forwarded message -

Bug#1035023: [ftpmas...@ftp-master.debian.org: Accepted cloud-init 23.2-1 (source) into unstable]

[Salvatore Bonaccorso]

Source: cloud-init
Source-Version: 23.2-1

Fixes as well CVE-2023-1786.

- Forwarded message from Debian FTP Masters 
 -

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 14 Jun 2023 09:42:18 -0700
Source: cloud-init
Architecture: source
Version: 23.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cloud Team 
Changed-By: Noah Meyerhans 
Closes: 999400 1005318 1008039
Changes:
 cloud-init (23.2-1) unstable; urgency=medium
 .
   [ Jochen Sprickerhof ]
   * Drop unused build dependencies
 .
   [ Noah Meyerhans ]
   * New upstream version 23.2 (Closes: #1008039, #1005318, #999400)
   * Refresh patches
   * drop special handling of files that no longer exist upstream
   * drop dependency on obsolete lsb-base package
Checksums-Sha1:
 347e8f3f7f34433ca013c8a686ff481b5bf3697c 2384 cloud-init_23.2-1.dsc
 ae2f9969eba76b62d2ae20a0d3c70b4613f84d94 1566508 cloud-init_23.2.orig.tar.gz
 953b9681a1224bc984b8d34afaefbfd3dd00dbb2 26464 cloud-init_23.2-1.debian.tar.xz
 ca3faf72c41b9ded219424de211015465b7823be 6876 
cloud-init_23.2-1_source.buildinfo
Checksums-Sha256:
 3d9cea3097b238ffa62f157e4997902df8363b530a3a2358c52350bf42864879 2384 
cloud-init_23.2-1.dsc
 8ad3c1a942e709c51b7b12b4e6e7f6c4ed8207e989b552f613ed646b82ecbdcc 1566508 
cloud-init_23.2.orig.tar.gz
 b84c09a18f9a0c336638a209ee2a94d661686dbd8ed83a3239eb6c8b529d1f4a 26464 
cloud-init_23.2-1.debian.tar.xz
 e9e1d06f7344dc0b599605ab1ebe3c047c259538c0225ecf97e0960c1a6b6da9 6876 
cloud-init_23.2-1_source.buildinfo
Files:
 ed80a08f3893b4076fb094ab98cf90c7 2384 admin optional cloud-init_23.2-1.dsc
 157c0c93aed174932dac611fb40a4bc1 1566508 admin optional 
cloud-init_23.2.orig.tar.gz
 95f01d442318efee12990557170ca4cf 26464 admin optional 
cloud-init_23.2-1.debian.tar.xz
 ff8541d1ae08cc8c9cf1a5619d38aaf6 6876 admin optional 
cloud-init_23.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE5G+E0xEKhJuZ7RJ34+c1IpshdTUFAmSJ7zkRHG5vYWhtQGRl
Ymlhbi5vcmcACgkQ4+c1IpshdTXc/hAAgEnFncimmxvHwdub6l/vdhcI3mbEt4oX
Cdb5yHKBmSK5MuYg0lYL7Kv/up1YKCq2RE12KTV+6gGYCuRf/p2VpgM3NnJTFvlG
aywcikmE3f8z/v3P0QRUT5km/KRMviv6c+lizYPvfdlrADX9LWx6ohMddlPySKhg
sGhvE4VSURSelObePwRSYy3MvGHZabNYlycO4qsD5GXpSXEnkzNDgonAyK3Bc2/A
PGR1SiPoWMs3++6JlAg9jv5Ifmvue1fgBm0Y1erKe03bbJvxD+bL2Kl+3JwVg+VL
28fOTODk3FIxRcGJX8KQmego/S3WY0LTKoHxxXrzlZExbGZZEYbj2TUuwXv+kdOY
NaM/M1kF+26V1oSqTTEFwO/UbDYh/RGSNAhqLZ0R3v5max1EtUaugKjUAtxJv0zu
Kw9iVvGRLy4bKYqoiH6Nk0d0Pr+TcY3rWc2urh4zeX5L6HKQ6oZYVrU20IQ4wDhs
1up6uRwsxCkQCClsaYuo9QpV8W0ZMNzXBi/zGniMumi8acvVUyQjYBIWja9MDm+U
glWH2Ha2yeKw2DYgvyxAJELOjFDhatiRAGm/UXdNlSiZ8dIhzYGCMNHr+DI6E932
6KWTSxhNpQ7cPoZXPUWrvuDII4ut+4iHE1Dq0AVQhTzfo/ZSJnxEiCXP+tXSI26z
6V/GAKpTtk4=
=aSna
-END PGP SIGNATURE-


- End forwarded message -

Bug#1037946: mmdebstrap: Create /var/lib/dpkg/available for Debian releases <=buster

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Michael Prokop (2023-06-14 17:19:37)
> since version 1.20.0, dpkg no longer creates /var/lib/dpkg/available (see
> #647911).

I see that the bug talks about 1.20.0 but I've had code creating
/var/lib/dpkg/available in mmdebstrap for a while and determined that it wasn't
necessary anymore since dpkg 1.17.11. Did you do practical tests or are you
only basing your analysis on that bug?

I'm quite certain about the version requirement because I did tests using
debbisect and using the suggestion below I'm able to create chroots for all of
unstable since 2006-08-10.

> But on Debian releases until and including buster, dpkg fails to operate with
> e.g. `dpkg --set-selections`, if /var/lib/dpkg/available doesn't exist:
> 
> | The following NEW packages will be installed:
> | [...]
> | debconf: delaying package configuration, since apt-utils is not installed
> | dpkg: error: failed to open package info file '/var/lib/dpkg/available' for 
> reading: No such file or directory
> 
> My workaround to work around this is to run:
> 
>   chroot "${TARGET}" /usr/lib/dpkg/methods/apt/update /var/lib/dpkg
> 
> As mmdebstrap seems to rely on dpkg of the host system, it would be
> nice if mmdebstrap could ensure to create an environment where apt/dpkg of
> the installed system doesn't stumble upon. :)

this already exists as a hook. :)

Try running mmdebstrap with

--hook-dir=/usr/share/mmdebstrap/hooks/jessie-or-older

which will unconditionally do certain things only necessary for old releases.

If you instead use

--hook-dir=/usr/share/mmdebstrap/hooks/maybe-jessie-or-older

some detection code will only run the hook if necessary (in case you do not
know upfront which release you are creating a chroot for).

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1037949: general: After installing VBox Guest Addition on the reboot the system gets into an enternal loop

[Bert Nijhof]

Package: general
Severity: normal
X-Debbugs-Cc: lammert.nij...@gmail.com

Dear Maintainer,

Debian was a fresh install. I tried to install VBox Guest Addtions like I have
done 100 times for at least 20 different distros. During that install I noticed
a small line, that said that the linux headers were missing. On the next reboot
the systen got into an eternal loop trying to add a VBox Service. The system
also looped selecting Grub Recovery mode.

I reinstalled Debian and before installing VBox Guest Additions, I installed
perl; make; gcc and the linux headers and afterwards the installation of VBox
Guest Additions was OK.

Other distros (e.g Ubuntu) avoid the installation of VBox Guest Additions, if
the dependencies are not satisfied and they clearly tell you what is missing.

Bug#1035820: 9base: leaves entries in /etc/shells after upgrade from bullseye

[Andreas Beckmann]

Control: unmerge -1
Control: reassign -1 debianutils 5.7-0.4
Control: affects -1 + src:9base
Control: tag -1 patch pending

On 13/06/2023 07.26, Helmut Grohne wrote:


The entry is added by /usr/lib/usrmerge/convert-etc-shells (which is the
policy violation this bug has been merged into). The merging strategy
there is based on a knowledge of the symlinks that should exist rather
than looking them up in the filesystem.

So this is two distinct bugs actually. We also need to fix update-shells
to properly deal with update-alternatives using the patch above.


Let's use this bug for the debianutils side.

I've prepared a NMU with three changes:
https://salsa.debian.org/anbe/debianutils/-/commits/fix-update-shells
* avoid creating duplicate entries in /etc/shells
* handle /bin/sh as defined in the template file
* fix canonicalization of shells that are symlinks

Especially with the /bin/sh change in place, update-shells and 
convert-etc-shells should produce similar results. convert-etc-shells 
needs to call update-shells (before manipulating /etc/shells on its own, 
s.t. the statefile gets updated), and maybe it can be replaced entirely 
by update-shells.



Andreas

Bug#1033130: gcc-snapshot: FTBFS on hppa - sys/mman.h: No such file or directory

[Matthias Klose]

wondering if configuring with --disable-libgcc would help?

Bug#1037485: Adsense of ovt in Debian 12 iso image

[Salvatore Bonaccorso]

Hi,

One other thing which might be of interest for you, but not directly
relating to the question if open-vm-tools is the iso image,
/usr/lib/finish-install.d/08hw-detect in the debian-installer's
hw-detect udeb should install open-vm-tools when it detects that the
virtualization type is vmware:

https://sources.debian.org/src/hw-detect/1.159/hw-detect.finish-install.d/08hw-detect/?hl=109#L104-L111

I realize this was not the question, but IMHO was worth mentioning.

Regards,
Salvatore

Bug#1037306: ITP: apycula -- Tools to generate Gowin FPGA bitstreams

[Daniel Gröber]

Hi Simon,

On Sun, Jun 11, 2023 at 11:33:52AM +0200, Daniel Gröber wrote:
> > I'd be interested in sponsoring nextpnr related packages.
> 
> Excellent.
> 
> The package is up on mentors and the git repo is in the electronics-team 
> salsa team:
> 
> https://mentors.debian.net/package/apycula/
> https://salsa.debian.org/electronics-team/apycula
> 
> have a look.

I've tested the apycula integration into nextpnr and made some more tweaks
to the packaging. Also the gbp upstream branch/tag was still missin in the
repo. All fixed now.

In the meantime I've opened another ITP for prjtrellis (Lattice ECP5
support) and I'm wondering if you'd be interested in sponsoring that too?
Package is on mentors and salsa too:

https://mentors.debian.net/package/prjtrellis/
https://salsa.debian.org/electronics-team/prjtrellis

Thanks,
--Daniel

Bug#1037917: gnutls28: leaves processes running after build: gnutls-serv, openssl s_server

[Andreas Metzler]

Control: found -1 3.8.0+git20230413-1

On 2023-06-14 Andreas Beckmann  wrote:
> Source: gnutls28
> Version: 3.8.0+git20230529-1
> Severity: serious

> Hi,

> after building gnutls28/experimental with pbuilder, there are a lot of
> gnutls-serv and a few openssl s_server processes running, preventing
> pbuilder to cleanup the chroot.

Hello,

This was caused by the changes related to fixing #1031553 (supporting
either datefudge or faketime. I think
tests/ocsp-tests/ocsp-tls-connection.sh or
tests/ocsp-tests/ocsp-must-staple-connection.sh triggers this.

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

Bug#1037524: libortp: still missing -lbctoolbox (was: Bug#994437: fixed in ortp 1:5.0.37-1)

[Dennis Filder]

Control: tags -1 confirmed
X-Debbugs-CC: Frank Heckenbach 

On Tue, Jun 13, 2023 at 08:25:28PM +0200, Frank Heckenbach wrote:
> Package: libortp-dev
> Version: 1:5.1.64-2
> Severity: normal
>
> It's actually not fixed!
>
> You added a "Requires.private" in the .pc, but that doesn't help.
> "Requires" is required (sic!) because a program that links to ortp
> apparently must also link to bctoolbox.

Dude, did you not see that the string "bctbx_set_log_level_mask" does
not occur anywhere in your program?  And that as a consequence the
error message does not really make any sense?  Because if you did see
it then you could have said something.

It was not immediately obvious to me that ortp_set_log_level_mask() in
the distant past was provided by libortp.so, but then replaced with
bctbx_set_log_level_mask() from libbctoolbox.so and the name change
papered over with a macro (instead of a wrapper function which would
have preserved the old linkage relationship).

Anyway, I'll fix it when preparing 1:5.2.x which I'll try to get to in
the coming weeks.

Regards.

Bug#1037948: xmltooling: Parsing of KeyInfo elements can cause remote resource access

[Ferenc Wágner]

Source: xmltooling
Severity: important
Tags: patch upstream security

Shibboleth Service Provider Security Advisory [12 June 2023]

An updated version of the XMLTooling library that is part of the
OpenSAML and Shibboleth Service Provider software is now available
which corrects a server-side request forgery (SSRF) vulnerability.

Parsing of KeyInfo elements can cause remote resource access.
=
Including certain legal but "malicious in intent" content in the
KeyInfo element defined by the XML Signature standard will result
in attempts by the SP's shibd process to dereference untrusted
URLs.

While the content of the URL must be supplied within the message
and does not include any SP internal state or dynamic content,
there is at minimum a risk of denial of service, and the attack
could be combined with others to create more serious vulnerabilities
in the future.

This issue is *not* specific to the V3 XMLTooling software and is
believed to impact all versions prior to V3.2.4.

Recommendations
===
Update to V3.2.4 or later of the XMLTooling library, which is
now available. Note that on Linux and similar platforms, upgrading
this component will require restarting the shibd process to correct
the bug.

The updated version of the library has been included in a V3.4.1.3
patch release of the Service Provider software on Windows.

Other Notes
===
The xmltooling git commit containing the fix for this issue is
6080f6343f98fec085bc0fd746913ee418cc9d30 and may be in general terms
applicable to V2 of the library.

Credits
===
Juriën de Jong, an independent security researcher in the Netherlands

URL for this Security Advisory:
https://shibboleth.net/community/advisories/secadv_20230612.txt

Bug#1037447: pipewire[…]: mod.rt: Can't find org.freedesktop.portal.Desktop. Is xdg-desktop-portal running?

[Dylan Aïssi]

Le mar. 13 juin 2023 à 22:51, AlMa  a écrit :
>
> Here, wireplumber 0.4.13-1 and pipewire:amd64 0.3.65-3 are installed.  I
> have no idea whether the pipewire issue 3194 at gitlab.freedesktop.org
> resolves it or not.
>

As explained in the upstream bug, these warnings messages have been demote
to only log messages, nothing to worry about.

Bug#1029586: apt: "apt-cache rdepends --installed" false positives

[Ingo Brückl]

On Wed, 25 Jan 2023 10:45:53 +0100, Julian wrote:

> The --installed flag here behaves exactly as it is documented. It
> filters the output list by packages that are installed; it doesn't
> say anything about restricting matching to installed versions only
> - matching always happens on all versions effectively.

Perhaps this should be documented more clearly. My reading of the option
was just as wrong as Vincent's.


1029586.patch
Description: Binary data

Bug#1037941: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?

[Dylan Aïssi]

Le mer. 14 juin 2023 à 17:03, AlMa  a écrit :
>
> What is SPA? The package pipewire-libcamera is NOT installed; it seems
> to be not recommended or even suggested by any other package. So besides
> a guess based on the name (and pipewire-libcamera may or may not be
> relevant), there's no way of knowing how to get rid of this error.  So
> who is the culprit and what to do?
>

What is the actual error you are facing?
"PipeWire's libcamera SPA missing or broken. libcamera not supported" is only
a log message (not even a warning) saying indeed the plugin provided by
pipewire-libcamera is not installed. SPA is for "Simple Plugin API" is the
pipewire's plugin API. If you don't know what is libcamera then you
probably don't need to install pipewire-libcamera. I can add it in suggested
package of wireplumber though, but again this is not an error only a log
message.

Bug#1037737: libreoffice: ftbfs with GCC-13

[Rene Engelhard]

Hi again,

Am 14.06.23 um 14:47 schrieb Rene Engelhard:

S=/<> && I=$S/instdir && W=$S/workdir && mkdir -p
$W/GenCxxObject/UnpackedTarball/skia/src/gpu/ganesh/vk/
$W/Dep/GenCxxObject/UnpackedTarball/skia/src/gpu/ganesh/vk/ && cd
/<> && clang++ -DBOOST_ERROR_CODE_HEADER_ONLY
-DBOOST_SYSTEM_NO_DEPRECATED -DCPPU_ENV=gcc3 -DLINUX -DNDEBUG
-DOSL_DEBUG_LEVEL=0 -DUNIX -DUNX -DX86_64 -D_FORTIFY_SOURCE=2
-D_PTHREADS -D_REENTRANT -Wdate-time -Wdate-time -D_FORTIFY_SOURCE=2
-DSKIA_IMPLEMENTATION=1 -DSKIA_DLL
-DSK_USER_CONFIG_HEADER="<$S/config_host/config_skia.h>"
-DSYSTEM_ZLIB -DZLIB_CONST -flto=thin -fvisibility=hidden -Wall
-Wno-missing-braces -Wnon-virtual-dtor -Wendif-labels -Wextra
-Wundef -Wunreachable-code -Wshadow -Wunused-macros
-finput-charset=UTF-8 -fmessage-length=0 -fno-common -pipe
-Wdeprecated-copy-dtor -Wduplicated-cond -Wlogical-op
-Wshift-overflow=2 -Wunused-const-variable=1 -Wno-cast-function-type
-fvisibility-inlines-hidden -fPIC -Wshadow -Woverloaded-virtual
-std=c++17 -pthread -g -O2 -f
file-prefix-map=/<>=. -ffat-lto-objects
-fstack-protector-strong -Wformat -Werror=format-security
-DEXCEPTIONS_ON -fexceptions -O2 -w -DLIBO_INTERNAL_ONLY -c
$W/UnpackedTarball/skia/src/gpu/ganesh/vk/GrVkSampler.cpp -o
$W/GenCxxObject/UnpackedTarball/skia/src/gpu/ganesh/vk/GrVkSampler.o
-MMD -MT
$W/GenCxxObject/UnpackedTarball/skia/src/gpu/ganesh/vk/GrVkSampler.o
-MP -MF
$W/Dep/GenCxxObject/UnpackedTarball/skia/src/gpu/ganesh/vk/GrVkSampler.d_ 
-I$S/include -I/usr/lib/jvm/default-java/include 
-I/usr/lib/jvm/default-java/include/linux -I$S/config_host -isystem 
/usr/include/freetype2 -isystem /usr/include/libpng16 -isystem /usr/include/freetype2 
-isystem /usr/include/libpng16 -isystem /usr/include/libpng16 -I$W/UnpackedTarball/skia 
-I$W/UnpackedTarball/skia/include/third_party/skcms/ 
-I$W/UnpackedTarball/skia/third_party/vulkanmemoryallocator/ 
-I$W/UnpackedTarball/skia/include/third_party/vulkan/ -I$S/external/skia/inc/ 
&& mv $W/Dep/GenCxxObject/Unp
ackedTarball/skia/src/gpu/ganesh/vk/GrVkSampler.d_
$W/Dep/GenCxxObject/UnpackedTarball/skia/src/gpu/ganesh/vk/GrVkSampler.d
test -f
/<>/workdir/UnpackedTarball/skia/src/gpu/ganesh/vk/GrVkSamplerYcbcrConversion.cpp || (echo 
"Missing generated source file 
/<>/workdir/UnpackedTarball/skia/src/gpu/ganesh/vk/GrVkSamplerYcbcrConversion.cpp" 
&& false)


On a side-note this is clang++, not g++. But I assume since upgrade of 
gcc and g++ from experimental also upgrades cpp it's cpp which is more 
strict here for the missing #include.


Anyways, as said: already fixed.

Regards,

Rene

Bug#1037947: boinc: starting boinc fails with GUI RPC bind to port 31416 failed: 98 even after fresh install

[Christopher Walker]

Package: boinc
Version: 7.20.5+dfsg-1.1
Severity: important
X-Debbugs-Cc: than...@outlook.com

Dear Maintainer,

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

   * What led up to the situation?
Updated to debian bookworm from bullseye.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Ran boinc
   * What was the outcome of this action?
  GUI RPC bind to port 31416 failed: 98
   * What outcome did you expect instead?
Bind to rpc port, run normally.
*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable'), (100, 
'bookworm-fasttrack'), (100, 'bookworm-backports-staging')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages boinc depends on:
ii  boinc-client   7.20.5+dfsg-1.1
ii  boinc-manager  7.20.5+dfsg-1.1

boinc recommends no packages.

boinc suggests no packages.

-- no debconf information

Bug#1037563: tech-ctte: Call for votes on TC membership of Timo Röhling

[Christoph Berg]

Re: Sean Whitton
> ===BEGIN
> The Technical Committee recommends that Timo Röhling  be
> appointed by the Debian Project Leader to the Technical Committee.
> 
> R: Recommend to appoint Timo Röhling 
> F: Further discussion
> ===END

I vote R > F

Christoph


signature.asc
Description: PGP signature

Bug#1037562: tech-ctte: Call for votes on TC membership of Stefano Rivera

[Christoph Berg]

Re: Sean Whitton
> ===BEGIN
> The Technical Committee recommends that Stefano Rivera  be
> appointed by the Debian Project Leader to the Technical Committee.
> 
> R: Recommend to appoint Stefano Rivera 
> F: Further discussion
> ===END

I vote R > F

Christoph


signature.asc
Description: PGP signature

Bug#1035733: debian -policy: packages must not use dpkg-divert to override default systemd configuraton files

[Luca Boccassi]

On Wed, 14 Jun 2023 at 16:27, Russ Allbery  wrote:
>
> Luca Boccassi  writes:
>
> > I.e.: if the attached version works, then that's good enough for me.
>
> Seconded.  Thank you for your work on multiple revisions of this patch!

Thanks for your patience and feedback!

Kind regards,
Luca Boccassi

Bug#1035901: spa.v4l2: '/dev/video4' VIDIOC_ENUM_FRAMESIZES: Unpassender IOCTL (I/O-Control) für das Gerät

[AlMa]

severity 1035901 important
found 1035901 0.3.65-3
thanks

The bug still exists in Debian stable with pipewire 0.3.65-3, 
wireplumber 0.4.13-1, and the kernel 6.1.0-9-amd64:


Jun 13 21:00:21 AnonymizedMachineName wireplumber[1148]: PipeWire's 
libcamera SPA missing or broken. libcamera not supported.
Jun 13 21:00:21 AnonymizedMachineName rtkit-daemon[1158]: Successfully 
made thread 1190 of process 1149 owned by '119' RT at priority 20.
Jun 13 21:00:21 AnonymizedMachineName rtkit-daemon[1158]: Supervising 6 
threads of 3 processes of 1 users.
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): glamor X acceleration enabled on NV168
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): glamor initialized
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(==) modeset(0): VariableRefresh: disabled
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(==) modeset(0): AsyncFlipSecondaries: disabled
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Output DP-1 has no monitor section
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Output HDMI-1 has no monitor section
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Output DVI-D-1 has no monitor section
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): EDID for output DP-1
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Manufacturer: PHL  Model: 946  Serial#: 40555
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Year: 2020  Week: 50
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): EDID Version: 1.4
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Digital Display Input
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 8 bits per channel
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Digital interface is DisplayPort
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Max Image Size [cm]: horiz.: 60  vert.: 34
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Gamma: 2.20
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): DPMS capabilities: Off
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 
4:2:2
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): First detailed timing is preferred mode
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Preferred mode is native pixel format and refresh rate
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Display is continuous-frequency
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): redX: 0.667 redY: 0.313   greenX: 0.290 greenY: 0.655
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): blueX: 0.152 blueY: 0.047   whiteX: 0.313 whiteY: 0.329
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Supported established timings:
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 720x400@70Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 640x480@60Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 640x480@67Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 640x480@72Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 640x480@75Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 800x600@56Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 800x600@60Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 800x600@72Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 800x600@75Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 832x624@75Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 1024x768@60Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 1024x768@70Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 1024x768@75Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 1280x1024@75Hz
Jun 13 21:00:21 

Bug#1035733: debian -policy: packages must not use dpkg-divert to override default systemd configuraton files

[Russ Allbery]

Luca Boccassi  writes:

> I.e.: if the attached version works, then that's good enough for me.

Seconded.  Thank you for your work on multiple revisions of this patch!

-- 
Russ Allbery (r...@debian.org)  

Bug#1037946: mmdebstrap: Create /var/lib/dpkg/available for Debian releases <=buster

[Michael Prokop]

Package: mmdebstrap
Version: 1.3.5-7
Severity: normal

Hi,

since version 1.20.0, dpkg no longer creates /var/lib/dpkg/available
(see #647911).

But on Debian releases until and including buster, dpkg fails to
operate with e.g. `dpkg --set-selections`, if
/var/lib/dpkg/available doesn't exist:

| The following NEW packages will be installed:
| [...]
| debconf: delaying package configuration, since apt-utils is not installed
| dpkg: error: failed to open package info file '/var/lib/dpkg/available' for 
reading: No such file or directory

My workaround to work around this is to run:

  chroot "${TARGET}" /usr/lib/dpkg/methods/apt/update /var/lib/dpkg

As mmdebstrap seems to rely on dpkg of the host system, it would be
nice if mmdebstrap could ensure to create an environment where
apt/dpkg of the installed system doesn't stumble upon. :)

Thanks for mmdebstrap!

regards
-mika-

Bug#1037945: bookworm-pu: package aide/aide_0.18.3-1+deb12u1

[Marc Haber]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: a...@packages.debian.org
Control: affects -1 + src:aide

Dear stable release team,

this pre-upload request for the aide package is filed to ask for
guidance whether this package is suitable for bookworm-updates. I have
never done this before and am open for suggestions to improve and for
documentation pointers. I haven't found the bookwork point release
policy yet, for example.

A fixed package has been uploaded to unstable minutes ago, and I do not
plan to actually upload the deb12u1 version of the package until the
fixes have reached testing.

[ Reason ]
This update fixes #1037171, a serious bug that prevents new
installations and upgrades of aide due to a misunderstanding in the dh
code regarding dh_installsysusers. Embarrassing.

And it also fixes #1037436, a "just" important bug that will fix correct
processing of extended attributes on symlinks that are monitored by
aide. This is a fix suggested by upstream (who is also a DD) and I will
create a similiar package for bullseye.

[ Impact ]
Regarding #1037171, Aide will not be useable until the _aide account is
manually created and some file permissions fixed. While package
installation will succeed, neither aideinit nor the daily aide cronjob
are invokeable and will error out.

Regarding #1037436, Aide will wrongly process extended attributes for
the file a symlink points to, which is not the intended behavior. The
fixed aide will process the extended attributes of a symlink.

[ Tests ]
Both bugs are sadly not covered by automated tests, but I am kind of
surprised that piuparts didn't catch #1037171. Regarding #1037171, I
tested:

- installation of aide in a bookworm VM with no aide installed before
- updating 0.18.3-1 to 0.18.3-2 in a bookworm VM
- updating 0.17.3-4+deb11u1 (oldstable) to 0.18.3-2 in a bookworm VM

Regarding #1037436, I created a symlink with extended attributes
pointing to a file with different extended attributes and verified that
actually the extended attributes of the symlink show up in the database.

[ Risks ]
Risks are that I goofed up in the fixes.

[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]
commit 456704ab523c6b7ca088a15ffde543fbac3fa391
Author: Marc Haber 
Date:   Wed Jun 14 16:51:03 2023 +0200

remove trailing whitespace in debian/rules

Git-Dch: ignore

commit 2c221fd08e6c4d570c4a2c86c87d0a94201fbe9d
Author: Marc Haber 
Date:   Wed Jun 14 15:28:15 2023 +0200

chown aide logs even when updating from 0.18.3-1

0.18.3-1 doesn't create the account, so we need to see for correct
file ownership when updating to a version that actually creates the
account.

commit 11547993349b3dffad11f2d6998875d58f6b0395
Author: Marc Haber 
Date:   Wed Jun 14 04:15:51 2023 +0200

Fix handling of extended attributes on symlinks

Closes: #1037436

This fixes wrong behavior regarding extended attributes on symlinks.
Prior versions of aide would wrongly process the extended attributes
of the file a symlink points to. This fix makes aide correctly process
the extended attributes of the link itself, which is the intended
behavior.

The fix for extended attributes on symlinks might lead to reported
changed entries during the next AIDE run. You can use the
`report_ignore_changed_attrs` option (see aide.conf(5)) to ignore
changes of the xattrs attribute; but be aware that this will not
only exclude the expected changes (of the symlink files) but also
the unexpected changes (of other files).

commit 0d0251e639334e0ef139c1f6f9d34b6032378d3d
Author: Marc Haber 
Date:   Tue Jun 13 16:53:49 2023 +0200

Move chown calls after #DEBHELPER#

This is part of the fix for #1037171, the account is only created in the
code inserted by debhelper at the #DEBHELPER# token. We thus cannot use
the account after that tag.

commit 218fff3fc157b89e53ece470267cb238fac5daac
Author: Marc Haber 
Date:   Sun Jun 11 22:54:19 2023 +0200

call dh_installsysusers manually in debian/rules

Thanks: Tomasz Ciolek
Closes: #1037171

dh_installsysusers is not called in the normal dh calling sequence in dh
compat level 13. This resulted in the account not being created in new
installs and probably also during upgrades from bullseye. Thix fixes the
issue by calling dh_installsysusers explicitly in
override_dh_auto_install.


[ Other info ]
source debdiff attached.

Please indicate whether this package might be a valid candidate to be in
the next bookworm point relase once 0.18.3-2 has reached testing.

Greetings
Marc
diff -Nru aide-0.18.3/debian/aide-common.postinst 
aide-0.18.3/debian/aide-common.postinst
--- aide-0.18.3/debian/aide-common.postinst 

Bug#1037074: solved, wrong Version of libgudev-1.0-0 was installed

[Michael Müller]

The problem was solved with installation of libgudev-1.0-0 237-2 

The dist upgrade from bullseye to bookworm did not install the latest version 
of libgudev-1.0-0. Version 230-3 stayed installed, not the version 237-2.
The Package Manager saw the installed version as newest, a manual installation 
of the version 237-2 was necessary. This solved the problem.

-- 
Michael Müller
Am Sonnenhang 55
35447 Reiskirchen
Tel. 06408 965903

Bug#1037944: kaffeine: DVB OTA mode TV channel selection after inital start Freezes Kaffeine

[Steve]

Package: kaffeine
Version: 2.0.18+git20230226.439cd0d-1
Severity: important
X-Debbugs-Cc: marathon.duran...@gmail.com

Dear Maintainer,

   * What led up to the situation?

After initial channel selection, next selection doesn't work and
results in completely frozen Kaffeine. Can't seem to force quit
it either.



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

Kernel: Linux 6.3.7-1-liquorix-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kaffeine depends on:
ii  iso-codes4.15.0-1
ii  kinit5.103.0-1
ii  kio  5.103.0-1
ii  libc62.36-9
ii  libdvbv5-0   1.22.1-5+b2
ii  libkf5configcore55.103.0-2
ii  libkf5configwidgets5 5.103.0-1
ii  libkf5coreaddons55.103.0-1
ii  libkf5dbusaddons55.103.0-1
ii  libkf5i18n5  5.103.0-1
ii  libkf5kiocore5   5.103.0-1
ii  libkf5kiofilewidgets55.103.0-1
ii  libkf5solid5 5.103.0-1
ii  libkf5widgetsaddons5 5.103.0-1
ii  libkf5windowsystem5  5.103.0-1
ii  libkf5xmlgui55.103.0-1
ii  libqt5core5a 5.15.8+dfsg-11
ii  libqt5dbus5  5.15.8+dfsg-11
ii  libqt5gui5   5.15.8+dfsg-11
ii  libqt5sql5   5.15.8+dfsg-11
ii  libqt5sql5-sqlite5.15.8+dfsg-11
ii  libqt5widgets5   5.15.8+dfsg-11
ii  libqt5x11extras5 5.15.8-2
ii  libqt5xml5   5.15.8+dfsg-11
ii  libstdc++6   12.2.0-14
ii  libvlc5  3.0.18-2
ii  libxss1  1:1.2.3-1
ii  vlc-plugin-base  3.0.18-2
ii  vlc-plugin-video-output  3.0.18-2

kaffeine recommends no packages.

Versions of packages kaffeine suggests:
pn  libdvdcss2  

-- no debconf information

Bug#1037943: wireplumber[…]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NameHasNoOwner

[AlMa]

Package: wireplumber
Version: 0.4.13-1

Deep in the journal log I discovered the following failure:

Jun 13 21:00:21 AnonymizedMachineName wireplumber[1148]: PipeWire's 
libcamera SPA missing or broken. libcamera not supported.
Jun 13 21:00:21 AnonymizedMachineName rtkit-daemon[1158]: Successfully 
made thread 1190 of process 1149 owned by '119' RT at priority 20.
Jun 13 21:00:21 AnonymizedMachineName rtkit-daemon[1158]: Supervising 6 
threads of 3 processes of 1 users.
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): glamor X acceleration enabled on NV168
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): glamor initialized
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(==) modeset(0): VariableRefresh: disabled
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(==) modeset(0): AsyncFlipSecondaries: disabled
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Output DP-1 has no monitor section
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Output HDMI-1 has no monitor section
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Output DVI-D-1 has no monitor section
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): EDID for output DP-1
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Manufacturer: PHL  Model: 946  Serial#: 40555
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Year: 2020  Week: 50
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): EDID Version: 1.4
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Digital Display Input
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 8 bits per channel
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Digital interface is DisplayPort
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Max Image Size [cm]: horiz.: 60  vert.: 34
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Gamma: 2.20
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): DPMS capabilities: Off
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4 YCrCb 
4:2:2
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): First detailed timing is preferred mode
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Preferred mode is native pixel format and refresh rate
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Display is continuous-frequency
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): redX: 0.667 redY: 0.313   greenX: 0.290 greenY: 0.655
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): blueX: 0.152 blueY: 0.047   whiteX: 0.313 whiteY: 0.329
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): Supported established timings:
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 720x400@70Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 640x480@60Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 640x480@67Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 640x480@72Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 640x480@75Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 800x600@56Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 800x600@60Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 800x600@72Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 800x600@75Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 832x624@75Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 1024x768@60Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 1024x768@70Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 1024x768@75Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0): 1280x1024@75Hz
Jun 13 21:00:21 AnonymizedMachineName /usr/libexec/gdm-x-session[1154]: 
(II) modeset(0):