Bug#1041900: cloud.debian.org: please publish arm64 vagrant boxes

[Ross Vandegrift]

Hi Lucas,

On Wed, Aug 02, 2023 at 10:38:24PM -0700, Ross Vandegrift wrote:
> The system tests need some easy fixes.  The end to end test tries to boot the
> image on the native arch.  It probably needs a feature to check if qemu is
> needed.  Time permitting, I plan to look at these in the next few days.

I have the tests fixed and added support for non-native arch E2E test runs with
qemu.  I've opened:
- system test fixes: 
https://salsa.debian.org/cloud-team/debian-vagrant-images/-/merge_requests/16
- arm64 pipeline support wip: 
https://salsa.debian.org/cloud-team/debian-vagrant-images/-/merge_requests/17

The first could be merged, the second needs some more work.

I'm not really clear on how to work on this pipeline - is the `debvagrant`
script available anywhere?

Ross

Bug#1037736: [Pkg-sass-devel] Bug#1037736: Bug#1037736: libsass: ftbfs with GCC-13

[Bo YU]

Hi!

On Sun, Aug 6, 2023 at 10:10 PM Jonas Smedegaard  wrote:
>
> Quoting Jonas Smedegaard (2023-08-06 14:07:09)
> > Quoting Bo YU (2023-08-06 13:48:43)
> > > On Mon, Jul 31, 2023 at 1:09 AM Jonas Smedegaard  wrote:
> > > > If you are generally interested in SASS tools and want to help maintain
> > > > them in Debian, then you are very welcome to join the team (which is
> > > > effectively only me at the moment).
> > > Thanks for the invitation. I am happy to maintain SASS tools packages.
> >
> > Great!  Please request membership of the salsa group at
> > https://salsa.debian.org/groups/sass-team/-/group_members
>
Request has been sent.

> Please also subscribe to our mailinglist - it is listed at our team page
> at https://wiki.debian.org/Teams/Sass (which I created just now,
> reminded by my earlier mention of lousy documentation).
>
Done. Thanks again for your work here, I will look at them.

BR,
Bo
>
>  - Jonas
>
> --
>  * Jonas Smedegaard - idealist & Internet-arkitekt
>  * Tlf.: +45 40843136  Website: http://dr.jones.dk/
>  * Sponsorship: https://ko-fi.com/drjones
>
>  [x] quote me freely  [ ] ask before reusing  [ ] keep private

Bug#1041786: Codeblocks crash Debian Bookworm

[jmgibson81]

Confirming bug. I've tried running Codeblocks from the terminal. There
is no output on the terminal, just a window that flashes real fast
about an XML error of some sort. I can't find a way to get an actual
error out of it. This happens in my case with regular C rather than
C++.

Bug#1043178: RM: flex-old -- RoQA; low popcon; dead upstream; announced by maintainer

[Bastian Germann]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 + src:flex-old
Control: block -1 by 932521

Please remove flex-old. The package maintainer filed bugs to get rid of all 
reverse dependencies.
One last reverse dependency is still in unstable (see blocks). The package has 
a low popcon.

Bug#957230: freebsd-buildutils: ftbfs with GCC-10

[Bastian Germann]

Am 07.08.23 um 02:40 schrieb Bastian Germann:

I am uploading a NMU to fix this. The debdiff is attached.


Now with the correct debdiff. I mixed up the BTS addresses.diff -Nru freebsd-buildutils-10.3~svn296373/debian/changelog 
freebsd-buildutils-10.3~svn296373/debian/changelog
--- freebsd-buildutils-10.3~svn296373/debian/changelog  2017-02-13 
22:45:25.0 +0100
+++ freebsd-buildutils-10.3~svn296373/debian/changelog  2023-08-07 
00:36:34.0 +0200
@@ -1,3 +1,14 @@
+freebsd-buildutils (10.3~svn296373-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't build against flex-old. (Closes: #932512)
+  * Build with gcc-9. (Closes: #957230)
+  * Depend on bsd{extra}utils instead of bsdmainutils. (Closes: #964527)
+  * Require newer freebsd-glue.
+  * Do not require lorder.
+
+ -- Bastian Germann   Mon, 07 Aug 2023 00:36:34 +0200
+
 freebsd-buildutils (10.3~svn296373-7) unstable; urgency=medium
 
   * Build fmtree with support for MD5, SHA1, RMD160, SHA256 checksums
diff -Nru freebsd-buildutils-10.3~svn296373/debian/control 
freebsd-buildutils-10.3~svn296373/debian/control
--- freebsd-buildutils-10.3~svn296373/debian/control2017-02-13 
22:25:13.0 +0100
+++ freebsd-buildutils-10.3~svn296373/debian/control2023-08-07 
00:36:34.0 +0200
@@ -7,13 +7,14 @@
  Robert Millan ,
  Steven Chamberlain ,
 Build-Depends: debhelper (>= 9),
- flex | flex-old,
- libfl-dev | flex-old,
+ gcc-9,
+ flex,
+ libfl-dev,
  bison,
  dpkg-dev (>= 1.16.1.1),
  libbsd-dev (>= 0.3.0),
  libmd-dev,
- freebsd-glue (>= 0.2.20),
+ freebsd-glue (>> 0.2.22),
  bmake,
  byacc (>= 20120115~),
 # for freebsd-config
@@ -24,8 +25,8 @@
 
 Package: freebsd-buildutils
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, bsdmainutils, unzip, patchutils,
- freebsd-glue (>= 0.2.8~),
+Depends: ${shlibs:Depends}, ${misc:Depends}, bsdutils, bsdextrautils, unzip,
+ patchutils, freebsd-glue (>= 0.2.8~),
 # Required by lex
  m4,
 # Not strictly required anymore. But let's drag it in for now, to avoid 
breaking
diff -Nru freebsd-buildutils-10.3~svn296373/debian/patches/01_make_fixes.diff 
freebsd-buildutils-10.3~svn296373/debian/patches/01_make_fixes.diff
--- freebsd-buildutils-10.3~svn296373/debian/patches/01_make_fixes.diff 
2016-03-05 16:28:15.0 +0100
+++ freebsd-buildutils-10.3~svn296373/debian/patches/01_make_fixes.diff 
2023-08-07 00:36:34.0 +0200
@@ -76,7 +76,7 @@
@${ECHO} building static ${LIB} library
@rm -f ${.TARGET}
 -  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${OBJS} ${STATICOBJS} | 
tsort -q` ${ARADD}
-+  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${OBJS} ${STATICOBJS} | 
tsort` ${ARADD}
++  ${AR} ${ARFLAGS} ${.TARGET} ${OBJS} ${STATICOBJS} ${ARADD}
${RANLIB} ${RANLIBFLAGS} ${.TARGET}
  .endif
  
@@ -85,7 +85,7 @@
@${ECHO} building profiled ${LIB} library
@rm -f ${.TARGET}
 -  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${POBJS} | tsort -q` 
${ARADD}
-+  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${POBJS} | tsort` 
${ARADD}
++  ${AR} ${ARFLAGS} ${.TARGET} ${POBJS} ${ARADD}
${RANLIB} ${RANLIBFLAGS} ${.TARGET}
  .endif
  
@@ -94,7 +94,7 @@
${_LD} ${LDFLAGS} ${SSP_CFLAGS} ${SOLINKOPTS} \
-o ${.TARGET} -Wl,-soname,${SONAME} \
 -  `NM='${NM}' lorder ${SOBJS} | tsort -q` ${LDADD}
-+  `NM='${NM}' lorder ${SOBJS} | tsort` ${LDADD}
++  ${SOBJS} ${LDADD}
  .if ${MK_CTF} != "no"
${CTFMERGE} ${CTFFLAGS} -o ${.TARGET} ${SOBJS}
  .endif
diff -Nru 
freebsd-buildutils-10.3~svn296373/debian/patches/ar_command_lines.diff 
freebsd-buildutils-10.3~svn296373/debian/patches/ar_command_lines.diff
--- freebsd-buildutils-10.3~svn296373/debian/patches/ar_command_lines.diff  
2016-07-19 10:30:55.0 +0200
+++ freebsd-buildutils-10.3~svn296373/debian/patches/ar_command_lines.diff  
2023-08-07 00:36:34.0 +0200
@@ -1,27 +1,9 @@
 Date: Tue, 19 Jul 2016 09:06:50 +0100
 From: Steven Chamberlain 
-Subject: make ar command lines visible in build log
+Subject: make ar command line visible in build log
 
 --- a/src/share/mk/bsd.lib.mk
 +++ b/src/share/mk/bsd.lib.mk
-@@ -175,7 +175,7 @@
- lib${LIB}.a: ${OBJS} ${STATICOBJS}
-   @${ECHO} building static ${LIB} library
-   @rm -f ${.TARGET}
--  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${OBJS} ${STATICOBJS} | 
tsort` ${ARADD}
-+  ${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${OBJS} ${STATICOBJS} | 
tsort` ${ARADD}
-   ${RANLIB} ${RANLIBFLAGS} ${.TARGET}
- .endif
- 
-@@ -188,7 +188,7 @@
- lib${LIB}_p.a: ${POBJS}
-   @${ECHO} building profiled ${LIB} library
-   @rm -f ${.TARGET}
--  @${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${POBJS} | tsort` 
${ARADD}
-+  ${AR} ${ARFLAGS} ${.TARGET} `NM='${NM}' lorder ${POBJS} | tsort` 
${ARADD}
-   ${RANLIB} ${RANLIBFLAGS} ${.TARGET}
- .endif
- 
 @@ -239,7 +239,7 @@
  lib${LIB}_pic.a: ${SOBJS}
@${ECHO} 

Bug#964661: freebsd-buildutils: ftbfs with GCC-10

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru freebsd-glue-0.2.22/debian/changelog 
freebsd-glue-0.2.22+nmu1/debian/changelog
--- freebsd-glue-0.2.22/debian/changelog2016-03-05 16:44:54.0 
+0100
+++ freebsd-glue-0.2.22+nmu1/debian/changelog   2023-08-07 01:20:16.0 
+0200
@@ -1,3 +1,12 @@
+freebsd-glue (0.2.22+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with gcc-9. (Closes: #964661)
+  * Include #pragma once in md5.h for freebsd-buildutils.
+  * Temporarily include lorder/tsort workaround. (Closes: #964661)
+
+ -- Bastian Germann   Mon, 07 Aug 2023 01:20:16 +0200
+
 freebsd-glue (0.2.22) unstable; urgency=medium
 
   * Actually use the proper build architecture compiler
diff -Nru freebsd-glue-0.2.22/debian/control 
freebsd-glue-0.2.22+nmu1/debian/control
--- freebsd-glue-0.2.22/debian/control  2016-03-05 02:08:01.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/control 2023-08-07 01:18:20.0 
+0200
@@ -7,6 +7,7 @@
  Steven Chamberlain ,
 Build-Depends:
  debhelper (>= 8.0),
+ gcc-9,
  kfreebsd-kernel-headers (>= 10.0~3) [kfreebsd-any],
  freebsd-mk,
  bmake,
diff -Nru freebsd-glue-0.2.22/debian/lorder 
freebsd-glue-0.2.22+nmu1/debian/lorder
--- freebsd-glue-0.2.22/debian/lorder   1970-01-01 01:00:00.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/lorder  2023-08-07 01:20:16.0 
+0200
@@ -0,0 +1,2 @@
+#!/bin/sh
+echo $@
diff -Nru freebsd-glue-0.2.22/debian/rules freebsd-glue-0.2.22+nmu1/debian/rules
--- freebsd-glue-0.2.22/debian/rules2016-03-05 01:54:10.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/rules   2023-08-07 01:20:16.0 
+0200
@@ -6,7 +6,7 @@
 # Determine host architecture compiler
 DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 ifeq ($(origin CC),default)
-CC := $(DEB_HOST_GNU_TYPE)-gcc
+CC := $(DEB_HOST_GNU_TYPE)-gcc-9
 endif
 
 # Determine build architecture compiler
@@ -23,7 +23,7 @@
 endif
 
 DESTDIR = $(CURDIR)/debian/tmp
-PATH := /usr/lib/freebsd:$(PATH)
+PATH := $(CURDIR)/debian:/usr/lib/freebsd:$(PATH)
 PMAKE := \
MAKEFLAGS=$(BSD_MAKEFLAGS) \
MAKEOBJDIRPREFIX=$(CURDIR)/obj-deb \
diff -Nru freebsd-glue-0.2.22/debian/tsort freebsd-glue-0.2.22+nmu1/debian/tsort
--- freebsd-glue-0.2.22/debian/tsort1970-01-01 01:00:00.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/tsort   2023-08-07 01:20:16.0 
+0200
@@ -0,0 +1,2 @@
+#!/bin/sh
+sort $@
diff -Nru freebsd-glue-0.2.22/include/md5.h 
freebsd-glue-0.2.22+nmu1/include/md5.h
--- freebsd-glue-0.2.22/include/md5.h   2014-08-25 21:40:17.0 +0200
+++ freebsd-glue-0.2.22+nmu1/include/md5.h  2023-08-07 01:20:16.0 
+0200
@@ -1 +1,2 @@
+#pragma once
 #include 

Bug#1043177: dbus-broker: kernel: memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=756 'dbus-broker-lau'

[Paul Wise]

Package: dbus-broker
Version: 33-1
Severity: normal
Usertags: warnings

I noticed that during boot the Linux kernel version 6.4.4 complains
about how dbus-broker-launch uses memfd_create, it should use one of
the MFD_EXEC nor MFD_NOEXEC_SEAL options. No reason is given though.

   Aug 07 08:27:15 systemd[1]: Starting dbus-broker.service - D-Bus System 
Message Bus...
   Aug 07 08:27:15 dbus-broker-launch[756]: Kernel is missing AppArmor DBus 
support. Ignoring.
   Aug 07 08:27:15 systemd[1]: Started dbus-broker.service - D-Bus System 
Message Bus.
   Aug 07 08:27:15 systemd[1]: Reached target basic.target - Basic System.
   Aug 07 08:27:15 dbus-broker-launch[756]: Ready
   Aug 07 08:27:15 kernel: memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, 
pid=756 'dbus-broker-lau'
   Aug 07 08:27:15 systemd[1]: Starting NetworkManager.service - Network 
Manager...

-- System Information:
Debian Release: trixie/sid
  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')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.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

Versions of packages dbus-broker depends on:
ii  dbus-system-bus-common  1.14.8-2
ii  init-system-helpers 1.65.2
ii  libapparmor13.0.8-3
ii  libaudit1   1:3.1.1-1
ii  libc6   2.37-6
ii  libcap-ng0  0.8.3-1+b3
ii  libexpat1   2.5.0-2
ii  libselinux1 3.5-1
ii  libsystemd0 254-1
ii  systemd-sysv254-1

Versions of packages dbus-broker recommends:
ii  dbus-bin  1.14.8-2

dbus-broker suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1042381: rust-ctr: Please upgrade to v0.7

[Jonas Smedegaard]

Quoting Peter Green (2023-08-07 01:51:19)
> > Please upgrade to newer upstream branch v0.7.
> 
> Would 0.9.x work for you?

Yes.

Thanks!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#957230: freebsd-buildutils: ftbfs with GCC-10

[Bastian Germann]

I am uploading a NMU to fix this. The debdiff is attached.diff -Nru freebsd-glue-0.2.22/debian/changelog 
freebsd-glue-0.2.22+nmu1/debian/changelog
--- freebsd-glue-0.2.22/debian/changelog2016-03-05 16:44:54.0 
+0100
+++ freebsd-glue-0.2.22+nmu1/debian/changelog   2023-08-07 01:20:16.0 
+0200
@@ -1,3 +1,12 @@
+freebsd-glue (0.2.22+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build with gcc-9. (Closes: #964661)
+  * Include #pragma once in md5.h for freebsd-buildutils.
+  * Temporarily include lorder/tsort workaround. (Closes: #964661)
+
+ -- Bastian Germann   Mon, 07 Aug 2023 01:20:16 +0200
+
 freebsd-glue (0.2.22) unstable; urgency=medium
 
   * Actually use the proper build architecture compiler
diff -Nru freebsd-glue-0.2.22/debian/control 
freebsd-glue-0.2.22+nmu1/debian/control
--- freebsd-glue-0.2.22/debian/control  2016-03-05 02:08:01.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/control 2023-08-07 01:18:20.0 
+0200
@@ -7,6 +7,7 @@
  Steven Chamberlain ,
 Build-Depends:
  debhelper (>= 8.0),
+ gcc-9,
  kfreebsd-kernel-headers (>= 10.0~3) [kfreebsd-any],
  freebsd-mk,
  bmake,
diff -Nru freebsd-glue-0.2.22/debian/lorder 
freebsd-glue-0.2.22+nmu1/debian/lorder
--- freebsd-glue-0.2.22/debian/lorder   1970-01-01 01:00:00.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/lorder  2023-08-07 01:20:16.0 
+0200
@@ -0,0 +1,2 @@
+#!/bin/sh
+echo $@
diff -Nru freebsd-glue-0.2.22/debian/rules freebsd-glue-0.2.22+nmu1/debian/rules
--- freebsd-glue-0.2.22/debian/rules2016-03-05 01:54:10.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/rules   2023-08-07 01:20:16.0 
+0200
@@ -6,7 +6,7 @@
 # Determine host architecture compiler
 DEB_HOST_GNU_TYPE  ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE)
 ifeq ($(origin CC),default)
-CC := $(DEB_HOST_GNU_TYPE)-gcc
+CC := $(DEB_HOST_GNU_TYPE)-gcc-9
 endif
 
 # Determine build architecture compiler
@@ -23,7 +23,7 @@
 endif
 
 DESTDIR = $(CURDIR)/debian/tmp
-PATH := /usr/lib/freebsd:$(PATH)
+PATH := $(CURDIR)/debian:/usr/lib/freebsd:$(PATH)
 PMAKE := \
MAKEFLAGS=$(BSD_MAKEFLAGS) \
MAKEOBJDIRPREFIX=$(CURDIR)/obj-deb \
diff -Nru freebsd-glue-0.2.22/debian/tsort freebsd-glue-0.2.22+nmu1/debian/tsort
--- freebsd-glue-0.2.22/debian/tsort1970-01-01 01:00:00.0 +0100
+++ freebsd-glue-0.2.22+nmu1/debian/tsort   2023-08-07 01:20:16.0 
+0200
@@ -0,0 +1,2 @@
+#!/bin/sh
+sort $@
diff -Nru freebsd-glue-0.2.22/include/md5.h 
freebsd-glue-0.2.22+nmu1/include/md5.h
--- freebsd-glue-0.2.22/include/md5.h   2014-08-25 21:40:17.0 +0200
+++ freebsd-glue-0.2.22+nmu1/include/md5.h  2023-08-07 01:20:16.0 
+0200
@@ -1 +1,2 @@
+#pragma once
 #include 

Bug#932516: ipfm: Don't build against flex-old

[Bastian Germann]

I am uploading a LowNMU to fix this. The debdiff is attached.diff -Nru ipfm-0.11.5/debian/changelog ipfm-0.11.5/debian/changelog
--- ipfm-0.11.5/debian/changelog2022-11-03 15:53:05.0 +0100
+++ ipfm-0.11.5/debian/changelog2023-08-07 02:13:35.0 +0200
@@ -1,3 +1,10 @@
+ipfm (0.11.5-4.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Don't build against flex-old. (Closes: #932516)
+
+ -- Bastian Germann   Mon, 07 Aug 2023 02:13:35 +0200
+
 ipfm (0.11.5-4.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ipfm-0.11.5/debian/control ipfm-0.11.5/debian/control
--- ipfm-0.11.5/debian/control  2016-06-27 13:54:17.0 +0200
+++ ipfm-0.11.5/debian/control  2023-08-07 02:13:31.0 +0200
@@ -2,7 +2,7 @@
 Section: net
 Priority: optional
 Maintainer: Sam Hocevar (Debian packages) 
-Build-Depends: libpcap-dev, bison, flex-old, debhelper (>= 9.0)
+Build-Depends: libpcap-dev, bison, flex, debhelper (>= 9.0)
 Standards-Version: 3.6.1.1
 
 Package: ipfm

Bug#1043078: linux-image-6.3.0-2-amd64: kernel NULL pointer dereference with MD write-back journal

[Corey Hickey]

On 2023-08-06 05:33, Salvatore Bonaccorso wrote:

If possible can you verify the issue is still present in either the
newest 6.4.y upstream or mainline (or nearest to that, the
6.5~rc4-1~exp1 in experimental)?

If so can you report the issue upstream and link back here the
upstream report?


Yes, I reproduced the bug with 6.4.8 today and reported it to linux-raid.

https://marc.info/?l=linux-raid=169136256805891=2

Thanks,
Corey

Bug#1043043: UDD patches: marks Forwarded as invalid if not 'no', 'not-needed', 'yes' or URL

[Guillem Jover]

Hi!

On Fri, 2023-08-04 at 23:35:27 -0300, David da Silva Polverari wrote:
> Package: qa.debian.org
> Severity: normal
> User: qa.debian@packages.debian.org
> Usertags: udd

> When using https://udd.debian.org/patches.cgi, I notice that whenever
> the Forwarded field contains anything other than "no", "not-needed",
> "yes" or an URL, it gets marked as invalid.

> As such, I think it would be interesting to either propose changes to
> DEP-3 or to adhere more closely to it.

Yes, this has been discussed recently, and I've got some notes on
multiple issues with the Patch Guidelines. I'll try to start a
discussion about updating it during this week or so.

Thanks,
Guillem

Bug#1032567:

[Yangfl]

I'm aware that autopkgtests do not test the final package, but clearly
they do not provide test cases other than unit tests. If this is not a
feasible way, better to remove autopkgtests completely.

Bug#1043176: sccache - update for new serial-test

[Peter Green]

Package: sccache
Severity: serious
Tags: trixie, sid

I just updated the serial-test crate to version 2.0. sccache
needs a small update to the Debian dependency to match. (the Cargo
dependency already allows both versions).

Debdiff attatched.
diff -Nru sccache-0.5.4/debian/changelog sccache-0.5.4/debian/changelog
--- sccache-0.5.4/debian/changelog  2023-07-30 16:13:02.0 +
+++ sccache-0.5.4/debian/changelog  2023-08-06 13:14:32.0 +
@@ -1,3 +1,11 @@
+sccache (0.5.4-7.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Debian dependency on serial-test to version 2
+(Cargo dependencies already allow it).
+
+ -- root   Sun, 06 Aug 2023 13:14:32 +
+
 sccache (0.5.4-7) unstable; urgency=medium
 
   * fix yet again: reduce lto further on mipsel
diff -Nru sccache-0.5.4/debian/control sccache-0.5.4/debian/control
--- sccache-0.5.4/debian/control2023-07-27 16:54:09.0 +
+++ sccache-0.5.4/debian/control2023-08-06 13:13:12.0 +
@@ -58,7 +58,7 @@
  librust-serde-1+default-dev,
  librust-serde-1+derive-dev,
  librust-serde-json-1+default-dev,
- librust-serial-test-0.9+default-dev ,
+ librust-serial-test-2+default-dev ,
  librust-sha2-0.10+default-dev,
  librust-strip-ansi-escapes-0.1+default-dev,
  librust-tar-0.4+default-dev,

Bug#1043175: rust-rustls-native-certs - update for new serial-test

[Peter Green]

Package: rust-rustls-native-certs
Severity: serious
Tags: trixie, sid

I just updated the serial-test crate to version 2.0. rust-rustls-native-certs
needs a small update to the Debian dependency to match. (the Cargo
dependency already allows both versions).

Debdiff attatched.
diff -Nru rust-rustls-native-certs-0.6.3/debian/changelog 
rust-rustls-native-certs-0.6.3/debian/changelog
--- rust-rustls-native-certs-0.6.3/debian/changelog 2023-07-29 
21:03:41.0 +
+++ rust-rustls-native-certs-0.6.3/debian/changelog 2023-08-06 
13:08:55.0 +
@@ -1,3 +1,11 @@
+rust-rustls-native-certs (0.6.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update debian dependencies for rust-serial-test 2
+(Cargo dependencies already allow that version).
+
+ -- Peter Michael Green   Sun, 06 Aug 2023 13:08:55 +
+
 rust-rustls-native-certs (0.6.3-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru rust-rustls-native-certs-0.6.3/debian/control 
rust-rustls-native-certs-0.6.3/debian/control
--- rust-rustls-native-certs-0.6.3/debian/control   2023-07-29 
21:03:41.0 +
+++ rust-rustls-native-certs-0.6.3/debian/control   2023-08-06 
13:07:44.0 +
@@ -9,7 +9,7 @@
  librust-rustls-0.21+default-dev ,
  librust-rustls-pemfile-1+default-dev ,
  librust-rustls-webpki-0.101+default-dev ,
- librust-serial-test-0.9+default-dev ,
+ librust-serial-test-2+default-dev ,
  librust-untrusted-0.7+default-dev ,
  libstring-shellquote-perl,
 Maintainer: Jonas Smedegaard 
diff -Nru rust-rustls-native-certs-0.6.3/debian/tests/control 
rust-rustls-native-certs-0.6.3/debian/tests/control
--- rust-rustls-native-certs-0.6.3/debian/tests/control 2023-07-29 
21:03:41.0 +
+++ rust-rustls-native-certs-0.6.3/debian/tests/control 2023-08-06 
13:08:50.0 +
@@ -8,7 +8,7 @@
  librust-rustls-0.21+default-dev,
  librust-rustls-native-certs-0.6-dev,
  librust-rustls-webpki-0.101+default-dev,
- librust-serial-test-0.9+default-dev,
+ librust-serial-test-2+default-dev,
  librust-untrusted-0.7+default-dev,
 Restrictions: allow-stderr, flaky
 
@@ -22,7 +22,7 @@
  librust-rustls-0.21+default-dev,
  librust-rustls-native-certs-0.6+default-dev,
  librust-rustls-webpki-0.101+default-dev,
- librust-serial-test-0.9+default-dev,
+ librust-serial-test-2+default-dev,
  librust-untrusted-0.7+default-dev,
 Restrictions: allow-stderr, flaky
 
@@ -36,6 +36,6 @@
  librust-rustls-0.21+default-dev,
  librust-rustls-native-certs-0.6-dev,
  librust-rustls-webpki-0.101+default-dev,
- librust-serial-test-0.9+default-dev,
+ librust-serial-test-2+default-dev,
  librust-untrusted-0.7+default-dev,
 Restrictions: allow-stderr, flaky

Bug#1043174: precious - update for new serial-test

[Peter Green]

Package: precious
Severity: serious
Tags: trixie, sid

I just updated the serial-test crate to version 2.0. Precious
needs a small update to the Debian dependency to match. (the Cargo
dependency already allows both versions).

Debdiff attatched.diff -Nru precious-0.5.1+20230704/debian/changelog 
precious-0.5.1+20230704/debian/changelog
--- precious-0.5.1+20230704/debian/changelog2023-07-11 21:20:29.0 
+
+++ precious-0.5.1+20230704/debian/changelog2023-08-06 12:48:08.0 
+
@@ -1,3 +1,11 @@
+precious (0.5.1+20230704-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Debian dependency on serial-test to 2.0.
+(cargo dependency already allows the new version)
+
+ -- Peter Michael Green   Sun, 06 Aug 2023 12:48:08 +
+
 precious (0.5.1+20230704-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru precious-0.5.1+20230704/debian/control 
precious-0.5.1+20230704/debian/control
--- precious-0.5.1+20230704/debian/control  2023-07-11 21:20:29.0 
+
+++ precious-0.5.1+20230704/debian/control  2023-08-06 12:47:55.0 
+
@@ -33,7 +33,7 @@
  librust-regex-1+default-dev (>= 1.7),
  librust-serde-1+default-dev (>= 1.0.147),
  librust-serde-1+derive-dev (>= 1.0.147),
- librust-serial-test-0.9+default-dev ,
+ librust-serial-test-2.0+default-dev ,
  librust-tempfile-3+default-dev (>= 3.3) ,
  librust-test-case-2+default-dev ,
  librust-thiserror-1+default-dev (>= 1.0.37),

Bug#1043173: wlgreet: Fails to start sway due to incorrect configuration

[Diederik de Haas]

On 07 Aug 2023 00:18:15 +0200 Diederik de Haas  wrote:
> Package: wlgreet
> Version: 0.4.1-1
> Severity: grave
> Tags: patch
> Justification: renders package unusable
> 
> I'm preparing a MR on Salsa and once I have a bug number for this bug,
> I'll submit it.

https://salsa.debian.org/debian/wlgreet/-/merge_requests/2

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

Bug#1043173: wlgreet: Fails to start sway due to incorrect configuration

[Diederik de Haas]

Package: wlgreet
Version: 0.4.1-1
Severity: grave
Tags: patch
Justification: renders package unusable

If you switch greetd's config to start wlgreet, you get presented a
screen to input your username and the next screen is for the password.
When you then press enter sway is supposed to start and it appears that
'something' is happening, but then you get thrown back to wlgreet's
login screen. It appears that the configuration is incorrect. After I
fixed that, I did login and a sway session (?) was started.

I'm preparing a MR on Salsa and once I have a bug number for this bug,
I'll submit it.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: arm64 (aarch64)

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

Versions of packages wlgreet depends on:
ii  libc6  2.37-6
ii  libgcc-s1  13.2.0-1
ii  sway   1.8.1-2

wlgreet recommends no packages.

wlgreet suggests no packages.

-- Configuration Files:
/etc/greetd/sway-config changed:
exec "/usr/sbin/wlgreet --command sway; swaymsg exit"
bindsym Mod4+shift+e exec swaynag \
-t warning \
-m 'What do you want to do?' \
-b 'Poweroff' 'systemctl poweroff -i' \
-b 'Reboot' 'systemctl reboot -i'
output * bg 
/usr/share/desktop-base/active-theme/lockscreen/contents/images/3840x2160.svg 
fill
include /etc/sway/config.d/*
include /etc/greetd/sway-config.d/*

/etc/greetd/wlgreet.tom [Errno 2] No such file or directory: 
'/etc/greetd/wlgreet.tom'

-- no debconf information

Bug#1043172: wlgreet's sway-config points to non-existing background image

[Diederik de Haas]

Package: wlgreet
Version: 0.4.1-1
Severity: normal

The `/etc/greetd/sway-config` file points to `/etc/greetd/background`
for sway's background image, but that file doesn't exist.
As a consequence of that, the configuration is invalid and sway shows a
rather prominent warning about it.
Because of that I set the severity to 'normal' instead of 'minor', but
I've also considered setting it to 'important'.

To fix it locally, I've installed the desktop-base package and pointed
to an image from the 'active' theme (emerald).
I'm not (so) sure whether that's a good solution as it would add a
dependency with 'Uncompressed Size: 20,1 M' and wlgreet's login window
is right on top of the Debian logo.
An alternative and 'lighter' solution is to just remove that setting.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (101, 'experimental')
Architecture: arm64 (aarch64)

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

Versions of packages wlgreet depends on:
ii  libc6  2.37-6
ii  libgcc-s1  13.2.0-1
ii  sway   1.8.1-2

wlgreet recommends no packages.

wlgreet suggests no packages.

-- Configuration Files:
/etc/greetd/sway-config changed:
exec "/usr/sbin/wlgreet --command sway; swaymsg exit"
bindsym Mod4+shift+e exec swaynag \
-t warning \
-m 'What do you want to do?' \
-b 'Poweroff' 'systemctl poweroff -i' \
-b 'Reboot' 'systemctl reboot -i'
output * bg 
/usr/share/desktop-base/active-theme/lockscreen/contents/images/3840x2160.svg 
fill
include /etc/sway/config.d/*
include /etc/greetd/sway-config.d/*

/etc/greetd/wlgreet.tom [Errno 2] No such file or directory: 
'/etc/greetd/wlgreet.tom'

-- no debconf information

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

[Vincent Lefevre]

On 2023-08-05 13:04:56 +0200, Sven Joachim wrote:
> Ah yes, Guillem implemented the "verbose" option three years ago in
> reaction to #967911.  And it could not be used back then because the
> dpkg version offering it was only uploaded several months later, but now
> it certainly can be used. :-)
> 
> Would you like to submit a merge request on salsa for the master branch?

OK, done here:
  https://salsa.debian.org/apt-team/aptitude/-/merge_requests/21

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

Bug#1041704: $MANWIDTH does not overwrite explicit line length in "~/.manpath"

[Bjarni Ingi Gislason]

  I had forgotten to repeat the testing

  After repeting testing:

  The reason for the failure is my man script.
When running the tests directly with /usr/bin/man the tests work.

  I had defined "MANROFFOPT" in the script, and MANWIDTH was already
defined as an environmental variable.

  I had created my alias to catch the standard error to a temporary
file, and to notice me, if it was not empty.

 with man as my script

I define nroff as "... -rLL=90m"

I tested again

MANWIDTH=80m man test

and it did not work.

But with

MANWIDTH=70m man test

it did!


MANROFFOPT='-rLL=70m' man test

does not work.

Bug#1043133: Patch which fixes the bug for me -> real fix already exists in git

[Chris Ward]

The patches I have on to live-build are here
https://github.com/tjcw/screensavers/tree/bookworm/patches . The
isolinux patch is a choice; for my purposes I want the live build to
display the splash screen before booting. And it may be that just one
of the chroot and installer patches is sufficient, or that something
here should be done a different way; I just hunted for
"firmware-linux" and dummied out all the references that I found.

Chris Ward.

On Sun, 6 Aug 2023 at 17:54, Roland Clobus  wrote:
>
> Hello Chris,
>
> On 06/08/2023 17:19, Chris Ward wrote:
> > The following fixes the bug for me. It may need adjusting so that it
> > can work both for debian 12.0 and previous, and for debian 12.11 where
> > 'firmware-linux' is no longer a separate item.
> >
> > The patch to binary_rootfs fixes a bug that I reported previously.
>
> My previous reply was blocked by Google, but this one should pass.
>
> See my reply [1] for a patch which was already applied in git.
>
> Actually 'firmware-linux' still is available [2], but it moved to
> 'non-free-firmware', which you might want to include in your own images.
>
> I'll take a look at the 'ext4' issue (#1032408) soon, let's keep the
> topic for each bug report separate.
>
> In general, building a bookworm image, typically requires either a
> bookworm+1 basic image, or a fresh git repo.
>
> With kind regards,
> Roland Clobus
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043133#15
> [2] https://packages.debian.org/search?keywords=firmware-linux

Bug#1043171: nmap: segfault when using service-names with -p

[Christopher Bock]

Package: nmap
Version: 7.94+dfsg1-3
Severity: normal

Hi,

when i try to use a service-name instead of the port-number nmap
breaks with a segfault.

cb@asterix ~ % nmap -p ssh localhost
Starting Nmap 7.94 ( https://nmap.org ) at 2023-08-06 22:51 CEST
[1]806174 segmentation fault (core dumped)  nmap -p ssh localhost
139 cb@asterix ~ %

I also tried other service-names and the really odd thing is that it
works occasionally but most of the time it doesn't.

As i don't really can make heads or tails from an strace i will leave
at that.

With many regards,
Christopher Bock


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

Kernel: Linux 6.4.0-1-amd64 (SMP w/8 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 nmap depends on:
ii  libc6 2.37-6
ii  libgcc-s1 13.2.0-1
ii  liblinear42.3.0+dfsg-5
ii  liblua5.4-0   5.4.4-3
ii  libpcap0.81.10.4-3
ii  libpcre2-8-0  10.42-2
ii  libssh2-1 1.11.0-2
ii  libssl3   3.0.9-1
ii  libstdc++613.2.0-1
ii  lua-lpeg  1.0.2-2
ii  nmap-common   7.94+dfsg1-3
ii  zlib1g1:1.2.13.dfsg-1

nmap recommends no packages.

Versions of packages nmap suggests:
pn  ncat
pn  ndiff   
pn  zenmap  

-- no debconf information



-- 
lg,
~cb

Bug#1043170: libdynarmic-dev: Please support boost 1.81

[Karl Pirton]

Package: libdynarmic-dev
Severity: wishlist
X-Debbugs-Cc: jsupert...@dnmx.org

Dear Maintainer,

I am trying to package the Citra emulator, while patching it to use 
system libraries. This requires libdynarmic-dev in build-depends. Unfortunately,
Citra does not build with boost 1.74. In order to get it to build I must use 
boost 1.81. The issue is libdynarmic-dev depends on libboost-dev, which
depends on libboost1.74-dev, which 1.81 confilcts with.

If libdynarmic depended on libboost1.81-dev, it would not only solve this
problem, but would also future-proof libdynarmic-dev, since the boost
library is going through a transition period between 1.74 and 1.81.

The only package that depends on libdynarmic, as far as I can tell, is yuzu.
I can confirm that yuzu builds and runs when linked against 
libboost-context1.81.0.

Thank you for your time.

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

Kernel: Linux 6.4.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libdynarmic-dev depends on:
pn  libboost-dev  
ii  libdynarmic6  6.4.5+ds-1
pn  llvm-dev  

libdynarmic-dev recommends no packages.

libdynarmic-dev suggests no packages.

Bug#1043169: gnome-software: Application version number ( flatpak and deb source ) stopped showing in description.

[zezamoral]

Package: gnome-software
Version: 43.5-1~deb12u1
Severity: normal
X-Debbugs-Cc: sazamor...@gmail.com

Dear Maintainer,


   * What led up to the situation?
Searching for new software.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Looking for app details do not shows application version number.
Neither flatpak or deb source version.

   * What was the outcome of this action?
Not showing application version number.

   * What outcome did you expect instead?
Being able to check the applications version number in the app
description as usual.
This was working last week.


Best Regards.


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

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

Versions of packages gnome-software depends on:
ii  appstream0.16.1-2
ii  apt-config-icons 0.16.1-2
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gnome-software-common43.5-1~deb12u1
ii  gsettings-desktop-schemas43.0-1
ii  libadwaita-1-0   1.2.2-1
ii  libappstream40.16.1-2
ii  libc62.36-9+deb12u1
ii  libcairo21.16.0-7
ii  libfwupd21.8.12-2
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-4-1   4.8.3+ds-2
ii  libgtk3-perl 0.038-3
ii  libgudev-1.0-0   237-2
ii  libjson-glib-1.0-0   1.6.6-1
ii  libmalcontent-0-00.11.0-4
ii  libpackagekit-glib2-18   1.2.6-5
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpolkit-gobject-1-0122-3
ii  libsoup-3.0-03.2.2-2
ii  libxmlb2 0.3.10-2
ii  packagekit   1.2.6-5
ii  software-properties-gtk  0.99.30-4

Versions of packages gnome-software recommends:
ii  fwupd  1.8.12-2

Versions of packages gnome-software suggests:
pn  apt-config-icons-hidpi 
ii  gnome-software-plugin-flatpak  43.5-1~deb12u1
pn  gnome-software-plugin-snap 

-- no debconf information

Bug#1043168: please include missing stub_flasher_32.json file

[Piotr Ożarowski]

Package: esptool
Version: 4.6.2+dfsg-0.1
Severity: minor

Hi,

I had to add stub_flasher_32.json file manually from upstream repo in
order to make my esphome (not yet in Debian, working on it) work with
ESP32 WROOM 32 board.

Please include this file in the package. TIA


signature.asc
Description: PGP signature

Bug#967470: gtans: depends on deprecated GTK 2

[Bastian Germann]

I do not expect gtans to be ported to a newer gtk version.
Please consider removing it from the archive.

Bug#1043167: RM: graphmonkey -- RoQA; low popcon; depends on gtk2

[Bastian Germann]

Source: graphmonkey
Version: 1.7-4.2
Severity: serious

Please consider removing graphmonkey. It build depends on 
libgtk2.0-cil-dev which should be removed in oder to get rid of gtk2 
eventually.


I am filing this as serious so that people recognize this bug.
If nobody complains about the possible removal when the package is 
autoremoved, I am going to file the RM bug.

Bug#1043145: Upgraded ntpsec to 1.2.2+dfsg1-1+deb12u1: fewer servers remain

[Thure Dührsen]

Dear Maintainer,

after upgrading ntpsec to 1.2.2+dfsg1-1+deb12u1, the behaviour is slightly 
different:

only ten servers remain after disconnecting from the internet,

[tdu:debiantutor] ~
 date; ntpq -pn | grep -Fv pool
Sun  6 Aug 21:02:52 CEST 2023
 remote   refid  st t when poll reach   delay   offset   jitter
===
+78.47.168.188   17.253.14.1252 u 1103  1280  46.9383  -4.3886 124.1287
+144.76.0.164193.190.230.65   2 u 1101  1280  33.9219  -7.6402 217.2358
-84.46.245.73237.17.204.952 u 1107  1280  45.2009 -13.4787 120.2817
-54.38.156.2210.1.1.2 2 u 1109  1280  29.9127  -7.8516  43.2926
+162.159.200.123 10.124.8.190 3 u 1102  1280  32.4660  36.9115 120.6871
+86.90.148.127   125.199.53.762 u 1105  1280  42.9345  37.2525  33.6707
-158.101.216.150 94.198.159.102 u 1101  1280  32.8930  35.2584 187.7465
-193.219.28.60   194.29.130.252   2 u 1090  1280  45.6136   5.0617 134.6725
-93.105.88.82194.146.251.101  2 u 1095  1280  60.3874  34.2942 141.3178
*91.227.212.78   194.146.251.100  2 u 1101  1280  60.9678  39.8529  37.1395

and no more than eight remain after reconnecting.

[tdu:debiantutor] ~
 date; ntpq -pn | grep -Fv pool
Sun  6 Aug 21:35:39 CEST 2023
 remote   refid  st t when poll reach   delay   offset   jitter
===
*78.47.168.188   17.253.14.1252 u4  128  377  42.4310  -4.7689  11.4233
+144.76.0.164193.190.230.65   2 u3  128  377  35.6690   0.3855  71.0345
+162.159.200.123 10.216.8.4   3 u   21  128  377  36.2527  -5.7169  19.8860
+86.90.148.127   125.199.53.762 u   14  128  375  48.7406  -0.6191  19.9919
+158.101.216.150 94.198.159.102 u  153  128  376  36.3177  -2.0115  23.1690
+193.219.28.60   210.100.177.101  2 u   15  128  377  47.5177   1.2094 134.4656
+93.105.88.82194.146.251.101  2 u   21  128  377  62.4123  -8.6088  18.5243
+91.227.212.78   194.146.251.100  2 u   15  128  377  59.2438   0.2789 182.5268


Something is undocumented here, if not wrong.

Feel free to tell me how I can assist in tracking the issue down.

To be clear, I am happy the number of servers is no longer 18, but confusion
does remain as to how exactly the "pool" directive works.

Best regards


-- 
Thure Dührsen
Kiel, Germany


Thure Dührsen
Elisabethstraße 116
4. OG rechts
24143 Kiel

Tel. +49 431 591 9707
Handy +49 160 9641 8332
tduehr...@schreib-doch-mal-wieder.de
ICQ 192-268-058
öffentlicher GnuPG-Schlüssel siehe http://www.informatik.uni-kiel.de/~tdu/

Bug#1043166: O: gpsim-doc -- Documentation for gpsim

[Bastian Germann]

Package: wnpp

gpsim-doc is obviously not maintained anymore.
If you consider adopting it please make sure to update it to reflect the 
latest gpsim package version in Debian with your first upload.

Bug#1043165: gnome-icon-theme-yasis: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: gnome-icon-theme-yasis
Version: 0.4.2-1.2
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1043164: gatos: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: gatos
Version: 0.0.5-19.2
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1043163: golang-golang-x-net: CVE-2023-3978

[Salvatore Bonaccorso]

Source: golang-golang-x-net
Version: 1:0.10.0-1
Severity: important
Tags: security upstream
Forwarded: https://go.dev/issue/61615
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for golang-golang-x-net.

CVE-2023-3978[0]:
| Text nodes not in the HTML namespace are incorrectly literally
| rendered, causing text which should be escaped to not be. This could
| lead to an XSS attack.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-3978
https://www.cve.org/CVERecord?id=CVE-2023-3978
[1] https://go.dev/issue/61615
[2] 
https://github.com/golang/net/commit/8ffa475fbdb33da97e8bf79cc5791ee8751fca5e 

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1043162: matrix-sydent: CVE-2023-38686

[Salvatore Bonaccorso]

Source: matrix-sydent
Version: 2.5.1-1.1
Severity: important
Tags: security upstream
Forwarded: https://github.com/matrix-org/sydent/pull/574
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for matrix-sydent.

CVE-2023-38686[0]:
| Sydent is an identity server for the Matrix communications protocol.
| Prior to version 2.5.6, if configured to send emails using TLS,
| Sydent does not verify SMTP servers' certificates. This makes
| Sydent's emails vulnerable to interception via a man-in-the-middle
| (MITM) attack. Attackers with privileged access to the network can
| intercept room invitations and address confirmation emails. This is
| patched in Sydent 2.5.6. When patching, make sure that Sydent trusts
| the certificate of the server it is connecting to. This should
| happen automatically when using properly issued certificates. Those
| who use self-signed certificates should make sure to copy their
| Certification Authority certificate, or their self signed
| certificate if using only one, to the trust store of your operating
| system. As a workaround, one can ensure Sydent's emails fail to send
| by setting the configured SMTP server to a loopback or non-routable
| address under one's control which does not have a listening SMTP
| server.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-38686
https://www.cve.org/CVERecord?id=CVE-2023-38686
[1] https://github.com/matrix-org/sydent/pull/574
[2] 
https://github.com/matrix-org/sydent/commit/1cd748307c6b168b66154e6c4db715d4b9551261
[3] https://github.com/matrix-org/sydent/security/advisories/GHSA-p6hw-wm59-3g5g

Regards,
Salvatore

Bug#1043161: i2p: CVE-2023-36325

[Salvatore Bonaccorso]

Source: i2p
Version: 0.9.48-1.1
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for i2p.

CVE-2023-36325[0]:
| Attackers can de-anonymize i2p hidden services with a message replay
| attack

Should i2p be removed from unstable?

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-36325
https://www.cve.org/CVERecord?id=CVE-2023-36325
[1] https://xeiaso.net/blog/CVE-2023-36325

Regards,
Salvatore

Bug#1043114: Please remove mipsel port from testing and sid

[Sebastian Ramacher]

Control: clone -1 -2
Control: reassign -2 release.debian.org
Control: retitle -2 britney2: remove mipsel from testing
Control: block -1 by -2

Hi YunQiang,

for the record: discussion on the future of mips starts at
https://lists.debian.org/debian-devel/2023/07/msg00217.html

On 2023-08-06 16:50:28 +0800, YunQiang Su wrote:
> Package: ftp.debian.org
> X-Debbugs-CC: debian-m...@lists.debian.org, d...@debian.org,
> debian-rele...@lists.debian.org
> 
> Since the Y2038 problem, 2G user space memory limit,
> and some lack of manpower,  It's time for us to drop mipsel support
> from the list of official release architectures.
> 
> Note: please keep mips64el for now.

>From https://lists.debian.org/debian-devel/2023/07/msg00288.html:

Mark Hymers wrote:
> 1. Release team: reconfigure britney2 to remove mipsel from testing
> 2. ftp-team remove architecture from testing and associated queues and
> perform any needed cleanup
> 3. ftp-team remove architecture from unstable and experimental and
> associated queues + cleanup

To handle the first step, I'm cloning and reassigning this bug to
release.debian.org.

Cheers
-- 
Sebastian Ramacher

Bug#1043159: golang-golang-x-image: CVE-2023-29407 CVE-2023-29408

[Salvatore Bonaccorso]

Source: golang-golang-x-image
Version: 0.7.0-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for golang-golang-x-image.

CVE-2023-29407[0]:
| A maliciously-crafted image can cause excessive CPU consumption in
| decoding. A tiled image with a height of 0 and a very large width
| can cause excessive CPU consumption, despite the image size (width *
| height) appearing to be zero.


CVE-2023-29408[1]:
| The TIFF decoder does not place a limit on the size of compressed
| tile data. A maliciously-crafted image can exploit this to cause a
| small image (both in terms of pixel width/height, and encoded size)
| to make the decoder decode large amounts of compressed data,
| consuming excessive memory and CPU.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-29407
https://www.cve.org/CVERecord?id=CVE-2023-29407
https://go.dev/issue/61581
[1] https://security-tracker.debian.org/tracker/CVE-2023-29408
https://www.cve.org/CVERecord?id=CVE-2023-29408
https://go.dev/issue/61582
[2] 
https://github.com/golang/image/commit/cb227cd2c919b27c6206fe0c1041a8bcc677949d

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1037567: abseil: ftbfs with GCC-13

[Benjamin Barenblat]

Thank you for the patch, Aurelien! I’ve applied it to the 20220623.1
release and uploaded it to unstable as 20220623.1-2.

Bug#1043158: waka waka waka

[Barak A. Pearlmutter]

Package: elpa-use-package
Version: 2.4.4-1

I am a fun-loving bloke so /usr/games is on my path and pacman (the
package) is installed. When emacs is started and elpa-use-package
loads and searches for an appropriate value for
system-packages-package-manager it finds the executable
/usr/games/pacman so the variable gets set to "pacman" instead of
"apt".

Waka waka waka.

Bug#1043156: floatbg: please consider upgrading to 3.0 source format

[Howard Jones]

On 06/08/2023 19:40, Bastian Germann wrote:

Source: floatbg
Version: 1.0-28.1
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

I think it's been about 20 years since I reported an issue with this 
package - is there a reason why I still get updates on every other issue 
filed for it? :-)

Bug#1040801: mcomix: pillow 10.0.0 not recognized as higher than 6.0.0

[Olivier Allard-Jacquin]

Hi,

On Mon, 10 Jul 2023 22:08:46 +0200 Sebastien KALT  wrote:

Package: mcomix
Version: 2.1.0-2
Severity: grave
Justification: renders package unusable


Same issue here (Debian testing up to date).

The issue is here :
/usr/lib/python3/dist-packages/mcomix/run.py:

 if PIL.__version__ < '6.0.0':


	I guess that issue root cause is due to "<", who is probably not the 
good way to compare strings under python. Python look like understand 
that "6.0" is after "10.0", due to comparison-only between 6 and 1...


I'm not a python developer, so here a quick and dirty patch:

# diff /usr/lib/python3/dist-packages/mcomix/run.py.bak 
/usr/lib/python3/dist-packages/mcomix/run.py

143c143
< if PIL.__version__ < '6.0.0':
---
> if PIL.__version__ < '10.0.0':

With this modification, mcomix work fine.

	Real python developers, or packagers should provide a better and more 
python-style than me ! :)


Best regards,
Olivier

Bug#1043157: ITS: g3data

[Bastian Germann]

Source: g3data
Severity: important

g3data needs a little love and seems to be ignored by its maintainer 
currently. I intend to salvage it. If you disagree, please tell me 
within three weeks.

Bug#1043156: floatbg: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: floatbg
Version: 1.0-28.1
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#932521: marked as pending in kbd-chooser

[Bastian Germann]

Hi Cyril,

On Sat, 20 Jul 2019 11:52:55 + Cyril Brulebois wrote:

Bug #932521 in kbd-chooser reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/installer-team/kbd-chooser/commit/966ad52d5810a49376a31d9a532377f03b5e1bd0


Drop flex-old as an alternative build-dep to flex (Closes: #932521).

As requested by the maintainer. Thanks, Tommi Vainikainen!


Can you please release a kbd-chooser version that includes this commit?

Thanks,
Bastian

Bug#1042871: transition: simdjson

[M. Zhou]

Yesterday I made a mistake to reply to the old simdjson transition
bug #1024380 which dates back to 1 year ago.

Anyway, it has been uploaded to unstable, and successfully built for
all release architectures.

On Sat, 2023-08-05 at 15:50 +0200, Sebastian Ramacher wrote:
> Control: tags -1 confirmed
> 
> On 2023-08-01 22:07:33 -0700, M. Zhou wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > X-Debbugs-Cc: simdj...@packages.debian.org
> > Control: affects -1 + src:simdjson
> > 
> > Hi release team,
> > 
> > The simdjson upstream has bumped the ABI version along with their
> > new release. Thus the transition request.
> > 
> > It has only two reverse dependencies in testing. src:vast is not
> > in testing. All reverse dependencies compiles against the new
> > version.
> 
> Please go ahead
> 
> Cheers

Bug#1043155: farpd: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: farpd
Version: 0.2-11.1
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1043154: falselogin: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: falselogin
Version: 0.3-4.1
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1041499: meson: glib2.0 FTBFS on mips64el: "native build" but then "Can not run test applications in this cross environment"

[Eli Schwartz]

On Wed, 19 Jul 2023 20:12:08 +0100 Simon McVittie  wrote:

> glib2.0's meson.build has several calls to 'cc.run(...)' guarded by
> a check for 'cc_can_run = meson.can_run_host_binaries()'.
> 
> On mips64el, Meson seems confused about whether this is a native or
> cross build. At first, it correctly reports that this is a native build:
> 
> 
> > The Meson build system
> > Version: 1.2.0
> > Source dir: /<>
> > Build dir: /<>/debian/build/deb
> > Build type: native build
> > Project name: glib
> > Project version: 2.76.4
> 
> but then later, cc.run() fails:
> 
> > ../../../meson.build:1127:14: ERROR: Can not run test applications in this 
> > cross environment.


Update: Simon wrote a fix for this and it is merged upstream and tagged
for the .1 maintenance release.

https://github.com/mesonbuild/meson/pull/12080


-- 
Eli Schwartz

Bug#1043153: empire-lafe: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: empire-lafe
Version: 1.1-1.1
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

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

[Drew Parsons]

On 2023-08-03 20:46, Adrian Bunk wrote:

On Wed, Aug 02, 2023 at 10:58:17AM +0200, Drew Parsons wrote:

On 2023-07-31 21:30, Sebastian Ramacher wrote:
> >
> > combblas:  1.16.0 → 2.0.0
> > superlu:5 → 6
> > hypre: 2.26.0 → 2.28.0
> > mumps:5.5 → 5.6
>
> Please go ahead.

combblas and superlu are loaded.

Probably best to run the rebuild of superlu-dist against combblas
...


That didn't build:

...

At first sight this looks like a bug in the combblas headers to me.



CombBLAS is now fixed, upstream notified 
https://github.com/PASSIONLab/CombBLAS/issues/20


All main packages are uploaded. mumps has lost powerpc and x32 but we 
won't stop the transition for that.


hypre test timeouts are an ongoing problem, now chronic on ppc64el. 
Historically a retry would pass, but ppc64el remains uncooperative.  I 
raised the issue upstream at 
https://github.com/hypre-space/hypre/issues/955
They suggest making life easier for ourselves and just run `make check`, 
touching only a subset of all their tests.  Since these timeouts have 
always been a problem (I even get them locally on my own system from 
time to time), we should probably accept their advice.  Possibly that 
will let us reactivate tests for armhf.



BTW: dolfin/fenics-basix/fenics-dolfinx need source-only uploads
 for testing migration.


Yes, I figured it's simplest to consider them honorary members of this 
transition.  That is I'll upload them after petsc gets rebuilt for this 
transition.

Bug#1043152: dsh: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: dsh
Version: 0.25.10-1.5
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1043151: bookworm-pu: package network-manager-applet/1.32.0-2+deb12u1

[Michael Biebl]

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

Hi,

I'd like to make a stable upload for network-manager-applet, which fixes
a crash in nm-connection-editor when importing a VPN configuration.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042712

It's a targetted fix, the patch has been cherry-picked from upstream Git
and applied to the package in unstable with not reported regressions.

Full debdiff is attached.

Regards,
Michael
diff --git a/debian/changelog b/debian/changelog
index 2e03baf9..e3e2fa50 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+network-manager-applet (1.32.0-2+deb12u1) bookworm; urgency=medium
+
+  * c-e: fix crash in import_vpn_from_file_cb() when importing VPN profiles
+(Closes: #1042712)
+
+ -- Michael Biebl   Sun, 06 Aug 2023 20:02:05 +0200
+
 network-manager-applet (1.32.0-2) unstable; urgency=medium
 
   * Upload to unstable
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 05e704d0..7a75dbc3 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,5 +1,5 @@
 [DEFAULT]
 pristine-tar = True
 patch-numbers = False
-debian-branch = debian/master
+debian-branch = debian/bookworm
 upstream-branch = upstream/latest
diff --git 
a/debian/patches/c-e-fix-crash-in-import_vpn_from_file_cb-when-importing-V.patch
 
b/debian/patches/c-e-fix-crash-in-import_vpn_from_file_cb-when-importing-V.patch
new file mode 100644
index ..ebe3b089
--- /dev/null
+++ 
b/debian/patches/c-e-fix-crash-in-import_vpn_from_file_cb-when-importing-V.patch
@@ -0,0 +1,53 @@
+From: Thomas Haller 
+Date: Tue, 2 May 2023 10:39:29 +0200
+Subject: c-e: fix crash in import_vpn_from_file_cb() when importing VPN
+ profiles
+
+Import code can create incomplete profiles, that don't have
+"connection.type" set. Avoid the crash.
+
+  #0  __strcmp_evex () at ../sysdeps/x86_64/multiarch/strcmp-evex.S:314
+  #1  0x0043d177 in import_vpn_from_file_cb (dialog=0x7f4650, 
response=, user_data=0x7d66e0) at 
src/connection-editor/connection-helpers.c:275
+  #2  0x76f564ea in g_closure_invoke (closure=0x8d5120, 
return_value=0x0, n_param_values=2, param_values=0x7fffd0f0, 
invocation_hint=0x7fffd070) at ../gobject/gclosure.c:832
+  #3  0x76f84d36 in signal_emit_unlocked_R.isra.0
+  (node=node@entry=0x847c70, detail=detail@entry=0, 
instance=instance@entry=0x7f4650, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0x7fffd0f0) at 
../gobject/gsignal.c:3812
+  #4  0x76f75bdd in g_signal_emit_valist (instance=, 
signal_id=, detail=, 
var_args=var_args@entry=0x7fffd2b0) at ../gobject/gsignal.c:3565
+  #5  0x76f75e53 in g_signal_emit (instance=, 
signal_id=, detail=) at ../gobject/gsignal.c:3622
+  #6  0x76f75cda in _g_closure_invoke_va (param_types=0x0, 
n_params=, args=0x7fffd520, instance=0x8ee230, 
return_value=0x0, closure=0x8efbf0) at ../gobject/gclosure.c:895
+  #7  g_signal_emit_valist (instance=0x8ee230, signal_id=216, detail=0, 
var_args=var_args@entry=0x7fffd520) at ../gobject/gsignal.c:3472
+  #8  0x76f75e53 in g_signal_emit (instance=instance@entry=0x8ee230, 
signal_id=, detail=detail@entry=0) at ../gobject/gsignal.c:3622
+  #9  0x776dd7dd in gtk_button_clicked (button=button@entry=0x8ee230) 
at ../gtk/gtkbutton.c:1541
+  #10 0x776dfad6 in gtk_button_finish_activate (do_it=1, 
button=0x8ee230) at ../gtk/gtkbutton.c:2042
+  #11 button_activate_timeout (data=0x8ee230) at ../gtk/gtkbutton.c:1984
+  #12 0x77eddcad in gdk_threads_dispatch (data=data@entry=0xa5f470) at 
../gdk/gdk.c:769
+  #13 0x76e55c69 in g_timeout_dispatch (source=0x711550, 
callback=0x77eddc80 , user_data=0xa5f470) at 
../glib/gmain.c:5054
+  #14 0x76e5539c in g_main_dispatch (context=0x4e7c70) at 
../glib/gmain.c:3460
+  #15 g_main_context_dispatch (context=0x4e7c70) at ../glib/gmain.c:4200
+  #16 0x76eb3438 in g_main_context_iterate.isra.0 (context=0x4e7c70, 
block=1, dispatch=1, self=) at ../glib/gmain.c:4276
+  #17 0x76e52a23 in g_main_context_iteration 
(context=context@entry=0x4e7c70, may_block=may_block@entry=1) at 
../glib/gmain.c:4343
+  #18 0x7708a01d in g_application_run 
(application=application@entry=0x4e5010, argc=, 
argv=0x7fffd9e8) at ../gio/gapplication.c:2573
+  #19 0x004133ad in main (argc=, argv=) 
at src/connection-editor/main.c:259
+
+https://gitlab.gnome.org/GNOME/network-manager-applet/-/issues/178
+
+Fixes: 3ff5b6cc9841 ('c-e: support importing WireGuard profiles from wg-quick 
files')
+(cherry picked from commit 01281fae6b601598cd2006bc8f2d5be98810228d)
+---
+ src/connection-editor/connection-helpers.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/connection-editor/connection-helpers.c 

Bug#1043150: RM: dnshistory -- RoQA; RC-buggy; orphaned; low popcon; depends on pcre3

[Bastian Germann]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 + src:dnshistory

Please remove dnshistory. It is orphaned with an open RC bug, which will 
probably not be fixed. It has a low popcon.

Bug#1043059: abseil/experimental FTBFS on mipsel

[Adrian Bunk]

On Sat, Aug 05, 2023 at 03:34:07PM +0300, Adrian Bunk wrote:
>...
> The patch below works around the address space issue, but later there is a 
> test failure:
> 
> ...
> 86: ./absl/log/scoped_mock_log.cc:39: Failure
> 86: Mock function called more times than expected - returning directly.
> 86: Function call: Log(INFO, @0x7f9b9b2c "./absl/log/log_format_test.cc", 
> @0x7f9b9b14 "nan")
> 86:  Expected: to be never called
> 86:Actual: called once - over-saturated and active
> 86: ./absl/log/log_format_test.cc:611: Failure
> 86: Actual function call count doesn't match EXPECT_CALL(test_sink, 
> Send(AllOf( TextMessage(MatchesOstream(comparison_stream)), 
> TextMessage(AnyOf(Eq("-nan"), Eq("nan"), Eq("NaN"), Eq("-nan(ind)"))), 
> ::testing::_)))...
> 86:  Expected: to be called once
> 86:Actual: never called - unsatisfied and active
> 86: [  FAILED  ] FloatingPointLogFormatTest/0.NegativeNaN, where TypeParam = 
> float (0 ms)
>...

FTR, this failure might be related to 
https://en.wikipedia.org/wiki/NaN#Encoding

cu
Adrian

Bug#1042872: (no subject)

[Patrick ZAJDA]

Hello,

I can reproduce it on Debian Bookworm.
Is the content you gave the exact one?

Because I had some source files which gave me this error and I noticed 
it was because I had a comment followed by a blank line.

If I remove the blank line after all comments, the warning is gone.

HTH,

Patrick

Bug#1043149: dist: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: dist
Version: 1:3.5-236-1
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1043148: dircproxy: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: dircproxy
Version: 1.0.5-6.1
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1043147: ding-libs: please consider upgrading to 3.0 source format

[Bastian Germann]

Source: ding-libs
Version: 0.6.2-1
Severity: wishlist

This package is among the few that still use source format 1.0.
Please upgrade it to source format 3.0:
https://wiki.debian.org/Projects/DebSrc3.0

Bug#1043146: reportbug: Text suggests a bug is being reported against wrong package

[Thure Dührsen]

Package: reportbug
Version: 12.0.0
Severity: normal
X-Debbugs-Cc: t.duehr...@gmx.net

Dear Maintainer,

After interrupting and later continuing work on reporting a bug
against the ntpsec package, the "reportbug" text UI suggests I was
reporting a bug against the reportbug package, which is incorrect.

Cf. lines 5, 19, 37 the following transcript:

 1  [...]
 2  Please select tags: (one at a time) [none] 
 3  Spawning mousepad...
 4  Report will be sent to Debian Bug Tracking System 

 5  Submit this report on ntpsec (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|?]? ?
 6  Y - (default) Submit the bug report via email.
 7  n - Don't submit the bug report; instead, save it in a temporary file 
(exits reportbug).
 8  a - Attach a file.
 9  c - Change editor and re-edit.
10  e - Re-edit the bug report.
11  i - Include a text file.
12  l - Pipe the message through the pager.
13  m - Choose a mailer to edit the report.
14  p - Print message to stdout.
15  q - Save it in a temporary file and quit.
16  d - Detach an attachment file.
17  t - Add tags.
18  ? - Display this help.
19  Submit this report on ntpsec (e to edit) [Y|n|a|c|e|i|l|m|p|q|d|t|?]? q
20  Bug report written to a temporary file.
21  You can resume the unsent report using:
22reportbug -r /tmp/reportbug-ntpsec-20230806191615-5hx3vtse
23  Thank you for using reportbug
24  
25  [tdu:debiantutor] ~
26   reportbug -r /tmp/reportbug-ntpsec-20230806191615-5hx3vtse
27  *** Welcome to reportbug.  Use ? for help at prompts. ***
28  Note: bug reports are publicly archived (including the email address of 
the submitter).
29  Detected character set: UTF-8
30  Please change your locale if this is incorrect.
31  
32  Using 'Thure Dührsen ' as your from address.
33  Will send report to Debian (per lsb_release).
34  
35  Spawning mousepad...
36  Report will be sent to Debian Bug Tracking System 

37  Submit this report on reportbug (e to edit) 
[Y|n|a|c|e|i|l|m|p|q|d|t|?]? ?
38  Y - (default) Submit the bug report via email.
39  n - Don't submit the bug report; instead, save it in a temporary file 
(exits reportbug).
40  [...]


-- Package-specific info:
** Environment settings:
EDITOR="nano"
VISUAL="mousepad"
INTERFACE="text"

** /home/tdu/.reportbugrc:
reportbug_version "12.0.0"
mode standard
ui text
realname "Thure Dührsen"
email "t.duehr...@gmx.net"
no-cc
list-cc-me
smtphost reportbug.debian.org

-- 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/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 reportbug depends on:
ii  apt2.6.1
ii  python33.11.2-1+b1
ii  python3-reportbug  12.0.0
ii  sensible-utils 0.0.17+nmu1

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
ii  debconf1.5.82
pn  debsums
pn  dlocate
ii  emacs-bin-common   1:28.2+1-15
ii  exim4-daemon-light [mail-transport-agent]  4.96-15
ii  file   1:5.44-3
ii  gnupg  2.2.40-1.1
pn  python3-urwid  
pn  reportbug-gtk  
ii  xdg-utils  1.1.3-4.1

Versions of packages python3-reportbug depends on:
ii  apt2.6.1
ii  file   1:5.44-3
ii  python33.11.2-1+b1
ii  python3-apt2.6.0
ii  python3-debian 0.1.49
ii  python3-debianbts  4.0.1
ii  python3-requests   2.28.1+dfsg-1
ii  sensible-utils 0.0.17+nmu1

python3-reportbug suggests no packages.

-- no debconf information

Bug#1043145: ntpsec: Number of servers acquired from pool almost doubles after internet connection failed

[Thure Dührsen]

Package: ntpsec
Version: 1.2.2+dfsg1-1
Severity: normal
X-Debbugs-Cc: t.duehr...@gmx.net

Dear Maintainer,

I am using the following setup:

[tdu:debiantutor] ~
 grep -E '^(server|pool)' /etc/ntpsec/ntp.conf
pool 0.de.pool.ntp.org iburst minpoll 7 maxpoll 14
pool 0.nl.pool.ntp.org iburst minpoll 7 maxpoll 14
pool 0.pl.pool.ntp.org iburst minpoll 7 maxpoll 14

It appears each of the "pool" directives causes four servers to be
picked, for a total of 12 servers.

If the internet connection goes down and is reestablished after all
the "reach" registers have gone to 0, another eight servers are shown
in the ntpq billboard. They remain even after several hours.
This unduly increases the traffic imposed on the network.

See attached file "ntp-transcript.txt" for the session transcript.


-- 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/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.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 ntpsec depends on:
ii  adduser3.134
ii  init-system-helpers1.65.2
ii  libbsd00.11.7-2
ii  libc6  2.36-9
ii  libcap21:2.66-4
ii  libssl33.0.9-1
ii  lsb-base   11.6
ii  netbase6.4
ii  python33.11.2-1+b1
ii  python3-ntp1.2.2+dfsg1-1
ii  sysvinit-utils [lsb-base]  3.06-4
ii  tzdata 2023c-5

Versions of packages ntpsec recommends:
ii  cron [cron-daemon]  3.0pl1-162
ii  systemd 252.6-1

Versions of packages ntpsec suggests:
ii  apparmor   3.0.8-3
pn  certbot
pn  ntpsec-doc 
pn  ntpsec-ntpviz  

-- Configuration Files:
/etc/ntpsec/ntp.conf changed:
driftfile /var/lib/ntpsec/ntp.drift
leapfile /usr/share/zoneinfo/leap-seconds.list
tos maxclock 11
tos minclock 4 minsane 3
pool 0.de.pool.ntp.org iburst minpoll 7 maxpoll 14
pool 0.nl.pool.ntp.org iburst minpoll 7 maxpoll 14
pool 0.pl.pool.ntp.org iburst minpoll 7 maxpoll 14
restrict default kod nomodify nopeer noquery limited
restrict 127.0.0.1
restrict ::1


-- no debconf information
Here is the session transcript:



[tdu:debiantutor] ~
 date; ntpq -pn | grep -Fv pool
Sun  6 Aug 16:47:56 CEST 2023
 remote   refid  st t when poll reach   delay   offset   jitter
===
+168.119.4.163   185.248.188.98   2 u   67  128  377  38.4933   7.3574   4.8569
+89.163.140.67   152.103.15.662 u   27  128  377  33.9683   6.0964   7.8183
+144.76.159.151  131.188.3.2212 u   75  128  377  38.8683  15.1471  12.5484
+81.169.204.195  124.216.164.14   2 u  104  128  377  35.1358  14.4352   5.9411
#108.61.189.74   145.238.203.10   3 u5  128  357  36.6998  10.2047  77.7851
-158.101.221.122 193.79.237.142 u  103  128  377  45.3339   6.0982  10.6504
+149.210.142.45  193.79.237.142 u  114  128  377  34.5920   9.3621   5.0750
+213.239.154.12  193.79.237.142 u   98  128  377  35.5525  15.5329   5.2494
+162.159.200.1   10.125.8.154 3 u   11  128  377  30.9859  12.4891  54.3597
*185.23.20.212   .GPS.1 u3  128  373  43.5971   8.4316   7.2712
-150.254.65.62   150.254.190.51   2 u  130  128  177  41.3541  14.9918  23.4035
-46.175.224.7162.159.200.14 u  115  128  377  48.9135   7.9233   9.0074



[tdu:debiantutor] ~
 date; ntpq -pn | grep -Fv pool
Sun  6 Aug 17:05:28 CEST 2023
 remote   refid  st t when poll reach   delay   offset   jitter
===
+168.119.4.163   185.248.188.98   2 u 1118  1280  38.4933   7.3574   2.9255
+89.163.140.67   152.103.15.662 u 1078  1280  33.9683   6.0964   7.4101
+144.76.159.151  131.188.3.2212 u 1126  1280  38.8683  15.1471  13.3329
+81.169.204.195  124.216.164.14   2 u 1155  1280  35.1358  14.4352   5.4885
#108.61.189.74   145.238.203.10   3 u 1056  1280  36.6998  10.2047  83.7430
-158.101.221.122 193.79.237.142 u 1154  1280  45.3339   6.0982  11.1629
+149.210.142.45  193.79.237.142 u 1165  1280  34.5920   9.3621   4.0312
+213.239.154.12  193.79.237.142 u 1149  1280  35.5525  15.5329   5.3730
+162.159.200.1   10.125.8.154 3 u 1062  1280  30.9859  12.4891  58.6654
*185.23.20.212   .GPS.1 u 1054  128  200  43.5971   8.4316   7.2712
-150.254.65.62   150.254.190.51   2 u 1047  256  200  41.3541  14.9918  23.2715
-46.175.224.7162.159.200.14 u 1166  1280  50.5658  13.2983   5.6284

[tdu:debiantutor] ~
 date; ntpq -pn | grep -Fv pool
Sun  6 Aug 17:12:06 CEST 2023
 remote   refid  st t when poll reach   delay   offset   jitter

Bug#1043144: transition: mutter/gnome-shell 44

[Simon McVittie]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: debian-gtk-gn...@lists.debian.org
Control: affects -1 + src:mutter src:gnome-shell
Control: block -1 by 1042980

It's about time we migrate GNOME Shell 44 to unstable. We delayed this for
a few months for the bookworm release, and then to get more testing for
the packages we wanted included in 12.1, but we should try to get 44 into
testing before upstream gets too close to releasing 45. Ubuntu already
did this transition for their 23.04 'lunar' short-term-support release.

This will require sourceful re-uploads of the following packages from
experimental into unstable, in approximately this order:

* mutter
* gnome-shell
* gnome-shell-extensions
* gnome-remote-desktop
* budgie-desktop
* gnome-shell-extension-bluetooth-quick-connect
* gnome-shell-extension-gsconnect

And then any remaining extensions in
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-gnome-maintainers%40lists.alioth.debian.org=gnome-shell-44
will need to be either fixed, re-uploaded from experimental to unstable
if already fixed in experimental, or temporarily kicked out of testing
to let the transition through.

There is one current blocker, #1042980, which is that gnome-shell is
failing build-time tests on mips64el and mipsel. So far I've fixed one
genuine bug in gnome-shell, and worked around another bug (seemingly in
LLVM or Mesa) by running the tests with softpipe rather than llvmpipe;
but there are still test failures. I don't think anyone in the GNOME
team has mips hardware or knowledge, and there's a limit to how usefully
we can debug this on eller. The failing test is new in v44, so we don't
know whether it would have failed in v43 if it existed there, or whether
it's a real regression: I've asked a mips porter to confirm whether Shell
v43 works with unstable's LLVM and Mesa or whether it is already broken,
but I haven't seen an answer so far.

Unlike s390x, I'm told mips(64)el does have desktop-class hardware that
could at least in principle run GNOME. I don't know how common that
hardware is, whether it's common to run GNOME on it, or whether mips
porters do so in practice (the extent of my information is "There are
some MIPS desktop cases").

Possible resolutions for #1042980:

* If mips porters can diagnose/fix the failing tests before we are
  otherwise ready to do this transition, then of course we should do that
  (but I think we need a contingency plan for if this doesn't happen)
* Or we could do architecture-specific removals on mips(64)el, making
  these uninstallable:
  - gdm3
  - gnome-core and other meta-gnome3 metapackages
  - gnome-session
  - ibus-tests
  - various Architecture: all packages such as Shell extensions
  - indirectly, task-gnome-desktop
* Or we could ignore the failing tests on mips(64)el, and let a
  potentially broken gnome-shell:mips(64)el into testing; and if the GNOME
  desktop has users on mips(64)el hardware who report that it doesn't work,
  ask mips porters to investigate and fix that

I feel as though holding back GNOME Shell 44 for the benefit of mips(64)el
users would be a worse result for Debian than getting GNOME 44 into
testing for the benefit of users of all the other architectures. Do
the release team have thoughts on which would be the best strategy to
avoid that?

Here is an attempt at a ben file that combines the mutter and gnome-shell
transitions, since they're really one transition:

title = "gnome-shell-44";
is_affected = .depends ~ 
/\b(gir1\.2\-mutter\-12|libmutter\-12\-0|libmutter\-12\-dev|libmutter\-test\-12|mutter\-12\-tests|gir1\.2\-mutter\-11|libmutter\-11\-0|libmutter\-11\-dev|libmutter\-test\-11|mutter\-11\-tests|gnome\-shell)\b/
is_good = .depends ~ 
/\b(gir1\.2\-mutter\-12|libmutter\-12\-0|libmutter\-12\-dev|libmutter\-test\-12|mutter\-12\-tests)\b/
 | .depends ~ /gnome\-shell (<< 4[5-9]/ | !.depends ~ /gnome\-shell (<

Bug#1041496: Same problem here

[Giuseppe Barichello]

Just upgraded from bullseye to bookworm and getting the same errors.

I fixed the "primary key type" warning by inserting this option:

DEFAULT_AUTO_FIELD='django.db.models.AutoField'

at the bottom of /usr/share/mailman3-web/settings.py

Now I'm stuck with the "timeout larger than retry": being a
python/django noob I can't figure where to find the settings file where
to edit those values...

Bug#1041236: ruby-nokogiri: useless use of a variable in void context in version.rb

[Richard Lewis]

On Sun, 16 Jul 2023 10:37:15 +0100 Richard Lewis
 wrote:

> When loading nokogiri, with 'ruby -w' i get a warning

> /usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0/gems/nokogiri-1.13.10/lib/nokogiri/version/info.rb:85:
>  warning: possibly useless use of a variable in void context
>
> The relevent lines are
>
>  72 def warnings
>  73   warnings = []
>  # ... other code adding to warnings is versions mismatch
>  85   warnings
>  86   #Debian: ignore warnings from mismatching build/load versions
>  87   []
>  88 end
>
> So it looks like Debian has made the function return an empty list instead of 
> the 'warnings'
> variable, but has left 85 as a useless use of a variable.
>
> Assuming there is a reason for hiding those warnings, I think it would be 
> better to change
> line 85 to say 'warnings=[]' and then the function would returning a now 
> empty warnings message:
> but ruby wouldnt complain.

Please see the following MR which does this - untested, but the
autopkgtests pass

https://salsa.debian.org/ruby-team/ruby-nokogiri/-/merge_requests/1

Bug#1043133: Patch which fixes the bug for me -> real fix already exists in git

[Roland Clobus]

Hello Chris,

On 06/08/2023 17:19, Chris Ward wrote:

The following fixes the bug for me. It may need adjusting so that it
can work both for debian 12.0 and previous, and for debian 12.11 where
'firmware-linux' is no longer a separate item.

The patch to binary_rootfs fixes a bug that I reported previously.


My previous reply was blocked by Google, but this one should pass.

See my reply [1] for a patch which was already applied in git.

Actually 'firmware-linux' still is available [2], but it moved to 
'non-free-firmware', which you might want to include in your own images.


I'll take a look at the 'ext4' issue (#1032408) soon, let's keep the 
topic for each bug report separate.


In general, building a bookworm image, typically requires either a 
bookworm+1 basic image, or a fresh git repo.


With kind regards,
Roland Clobus

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043133#15
[2] https://packages.debian.org/search?keywords=firmware-linux


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1042810: [Debian-pan-maintainers] Bug#1042810: bornagain: FTBFS/BD-Uninstallable on !amd64

[Roland Mas]

Le 01/08/2023 à 10:14, Sebastian Ramacher a écrit :

Source: bornagain
Version: 20.2+ds3-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)


A partial patch fixing several testsuite failures has already been 
committed upstream and cherry-picked in the package, but other failures 
remain. Discussion is ongoing with upstream.


Roland.

Bug#1043143: davmail: autopkgtest depends on netcat virtual package

[Graham Inggs]

Source: davmail
Version: 6.1.0.3423-3
Severity: important

Hi Maintainer

The autopkgtest of davmail has a dependency on the netcat virtual package.
It was discovered in Ubuntu (LP: #2029465) [1] that davmail's
autopkgtest will pass or fail depending on which of the two packages
providing netcat; netcat-openbsd or netcat-traditional, is installed.

Please consider switching the autopkgtest dependency to one of the
real packages.

I think it should be policy for autopkgtests not to depend on virtual
packages, but I will try to find if there is consensus within Debian
before raising the severity of this bug.

Regards
Graham


[1] https://bugs.launchpad.net/ubuntu/+source/davmail/+bug/2029465

Bug#1043133: Patches fixed

[Chris Ward]

Now 2 patches

diff --git a/chroot_firmware b/chroot_firmware.1
index e22068f..d061c42 100755
--- a/chroot_firmware
+++ b/chroot_firmware.1
@@ -54,10 +54,11 @@ Check_package host /usr/bin/wget wget
 FIRMWARE_PACKAGES=""

 # Manually add firmware-linux meta package if available
-if [ $(apt-cache show "^firmware-linux$" 2> /dev/null | grep
"^Package:" | wc -l) -eq 1 ]
-then
-   FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"
-fi
+# tjcw 20230806 firmware now in base install with debian 12.1
+#if [ $(apt-cache show "^firmware-linux$" 2> /dev/null | grep
"^Package:" | wc -l) -eq 1 ]
+#then
+#  FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"
+#fi

 Firmware_List_From_Contents "${LB_PARENT_MIRROR_CHROOT}"
"${LB_PARENT_DISTRIBUTION_CHROOT}" "${LB_PARENT_ARCHIVE_AREAS}"

and

diff --git a/installer_debian-installer b/installer_debian-installer.1
index c28b516..5b3819a 100755
--- a/installer_debian-installer
+++ b/installer_debian-installer.1
@@ -402,10 +402,11 @@ then
FIRMWARE_PACKAGES=""

# Manually add firmware-linux meta package if available
-   if [ $(apt-cache show "^firmware-linux$" 2> /dev/null
| grep "^Package:" | wc -l) -eq 1 ]
-   then
-   FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"
-   fi
+# 20230806 tjcw Already in base linux with debian 12.1
+   #if [ $(apt-cache show "^firmware-linux$" 2> /dev/null
| grep "^Package:" | wc -l) -eq 1 ]
+   #then
+   #   FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"
+   #fi

Firmware_List_From_Contents
"${LB_PARENT_MIRROR_CHROOT}" "${LB_PARENT_DISTRIBUTION_CHROOT}"
"${LB_PARENT_ARCHIVE_AREAS}"

Chris Ward

Bug#1037346: My Calendars and Addressbooks are also affected

[Joachim Zobel]

Unfortunately my #calendars and #adresses mailboxes have also been hit.
They now have Inboxes and all entries are gone. Any experience on how
to recover these?

Thanks,
jOACHIM

-- 
   Papier ist gebundenes CO2. Bitte drucken Sie diese EMail aus und
archivieren Sie sie.

Bug#1043142: git-buildpackage: import-dscs importing upstream branches out-of-order

[Joao Eriberto Mota Filho]

Package: git-buildpackage
Version: 0.9.22
Severity: important
Tags: sid trixie bookworm bullseye
X-Debbugs-Cc: eribe...@debian.org

Dear Maintainer,

When using:

gbp import-dscs --debsnap acr

or

debsnap acr; gbp import-dscs source-acr/*.dsc

the result is the upstream branches out-of-order. See the following command
after an import (important lines only):

$ git log
commit 17d263cee50d3f4b8ba881ca7216194672e7fdfb (HEAD -> debian/master, tag: 
debian/1.9.4-2)
Author: Thiago Marques Siqueira 
Date:   Sun Jul 9 17:11:06 2023 +0100
[...]
commit 8b622b80fb70e9cbdbd071f1d7f714f3f9629e57 (tag: debian/1.9.4-1)
Merge: 4adf342 ce6c977
Author: Ruben Pollan 
Date:   Wed Nov 11 13:04:48 2020 +0100
[...]
commit 4adf342f0ecaf0853e2a67ce4ecd3e1acc4b (tag: debian/1.9.2-1)
Merge: 5c67e33 e093e17
Author: Ruben Pollan 
Date:   Mon May 11 17:50:30 2020 +0200
[...]
commit ce6c977714bed2df56c2b5196c63be93163b9c76 (tag: upstream/1.9.4, upstream)
Author: Joao Eriberto Mota Filho 
Date:   Sun Aug 6 12:49:57 2023 -0300
[...]
commit 5c67e33227e93c952beb794f187f0ea939bf6da3 (tag: debian/1.7.2-1)
Merge: bf4799a 8fb8e10
Author: Ruben Pollan 
Date:   Thu Feb 21 13:36:37 2019 +0100
[...]
commit e093e17ad41e54455a91294fe7f91ea02a9d3b32 (tag: upstream/1.9.2)
Author: Joao Eriberto Mota Filho 
Date:   Sun Aug 6 12:49:57 2023 -0300
[...]
commit bf4799a838a39ebfc55ab0a5927d8199918ed5ee (tag: debian/1.7.0-1)
Merge: f75f0d0 4ed59ec
Author: Ruben Pollan 
Date:   Tue Oct 2 12:40:27 2018 -0500
[...]
commit 8fb8e104db07fac42c81a796c50cf47febdb130b (tag: upstream/1.7.2)
Author: Joao Eriberto Mota Filho 
Date:   Sun Aug 6 12:49:56 2023 -0300
[...]
commit f75f0d08a3b8e81914fbe69450e1215be93231e1 (tag: debian/1.6.2-1)
Merge: 8765fb7 b83b9fb
Author: Ruben Pollan 
Date:   Fri May 18 20:20:29 2018 +0200
[...]
commit 4ed59ece03f46f22e525615aa3283ce8e4344043 (tag: upstream/1.7.0)
Author: Joao Eriberto Mota Filho 
Date:   Sun Aug 6 12:49:56 2023 -0300
[...]
commit 8765fb751b746fb7e2aa320821972735869ca8d7 (tag: debian/1.6.1-1)
Merge: 281c76f 3916c6a
Author: Ruben Pollan 
Date:   Mon Apr 16 09:54:12 2018 +0200
[...]


I consider this issue 'important' because several people use gbp import-dscs to
create a repository for a package, keeping all previous history. Importing each
package by hand using import-dsc (not dscs) will work fine.

Regards,

Eriberto

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

Kernel: Linux 6.1.0-10-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE=C.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages git-buildpackage depends on:
ii  devscripts 2.23.5
ii  git1:2.40.1-1
ii  man-db 2.11.2-3
ii  python33.11.4-5+b1
ii  python3-dateutil   2.8.2-2
ii  python3-pkg-resources  68.0.0-1
ii  python3-yaml   6.0.1-1
ii  sensible-utils 0.0.20

Versions of packages git-buildpackage recommends:
ii  cowbuilder0.89
ii  pbuilder  0.231
ii  pristine-tar  1.50
ii  python3-requests  2.31.0+dfsg-1

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
ii  sudo 1.9.14p2-1
ii  unzip6.0-28

-- Configuration Files:
/etc/git-buildpackage/gbp.conf changed:
[DEFAULT]
debian-branch = debian/master
pristine-tar = True
[buildpackage]
[import-orig]
[import-dsc]
[dch]
[pq]
[clone]
[pull]
[create-remote-repo]
[remote-config pkg-libvirt]
remote-url-pattern = ssh://git.debian.org/git/pkg-libvirt/%(pkg)s
template-dir = 
/srv/alioth.debian.org/chroot/home/groups/pkg-libvirt/git-template

Bug#994722: apt-show-versions: Syntax error on or around line 378.

[Richard Lewis]

On Sun, 19 Sep 2021 22:41:24 +0100 Richard Lewis
 wrote:

> giving two arguments including one that is not a package shows there is a 
> syntax error somewhere around line 378:
>
> $ apt-show-versions apt whatever
> apt:amd64/bullseye 2.2.4 uptodate
> Use of uninitialized value $arch in concatenation (.) or string at 
> /usr/bin/apt-show-versions line 378.
> Use of uninitialized value $arch in hash element at 
> /usr/bin/apt-show-versions line 381.
> Use of uninitialized value $arch in hash element at 
> /usr/bin/apt-show-versions line 393.
> whatever: not installed
>

I think this is because at the start of print_package,  the 'if' at
359 always succeeds if we had more than one package on the command
line, (mode will !=MODE_SINGLE) but
if the package was invalid, $archname is not defined.

It doesnt make sense to call print_package_internal unless $archname
has been set, so i wonder if line 359 should be
- deleted
- replaced with if($archname)
-replaced with "if(mode!=$MODE_SINGLE&& $archname"
-something else
?

356if ($archname and ! defined $apackages->{$pkgname}{$archname})
{
357printf("%s not available for architecture %s\n", $pkgname,
$archname);
358} elsif (! defined $pkgs->{$pkgname}) {
359if ($mode != $MODE_SINGLE || $archname) {
360print_package_internal($pkgname, $archname)
361} elsif (keys(%{$apackages->{$pkgname}})) {
362my $archlist = "";
363foreach my $a (sort keys(%{$apackages->{$pkgname}})) {
364print_package_internal($pkgname, $a);
365$archlist .= ($archlist ? ", $a" : "$a");
366}
367} else {
368printf("%s not installed (not available)\n", $pkgname);
369}
370} else {
371foreach my $arch ($archname or sort
keys(%{{map{$_=>1}(keys(%{$apackages->{$pkgname}}),

Bug#1043141: synaptic: Switch mirror, Synaptic changes the URL address of the bookworm-security (sources.list)

[Mester Imre]

Package: synaptic
Version: 0.91.3
Severity: important
X-Debbugs-Cc: mesterimr...@gmail.com

Dear Maintainer,

I switched mirrors in Synaptic package manager (Software & Sources) from the
main mirror to one of the faster ones, like Switzerland or Slovakia.

After the change I updated the lists using the Synaptic Update button.

Error message:

LANG=C sudo apt-get update

Err:16 http://ftp.sk.debian.org/debian bookworm-security Release
  404  Not Found [IP: 195.80.174.186 80]
...
Reading package lists... Done
E: The repository 'http://ftp.sk.debian.org/debian bookworm-security Release'
does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration
details.

It clearly happened after the changeover to the Slovak mirror!

I checked, the contents of the sources.list in /etc/apt/ changed to

deb http://ftp.sk.debian.org/debian bookworm-security main contrib non-free
non-free-firmware
deb-src http://ftp.sk.debian.org/debian bookworm-security main contrib non-free
non-free-firmware

Whereas, it is the right contents, that it used to same as like earlyer

deb http://security.debian.org/debian-security bookworm-security main contrib
non-free non-free-firmware
deb-src http://security.debian.org/debian-security bookworm-security main
contrib non-free non-free-firmware

As an aside, but interestingly, the bookworm-backports mirror has not been
changed to Slovak, it has remained original

# bookworm-backports
# https://wiki.debian.org/Backports
deb http://deb.debian.org/debian bookworm-backports main contrib non-free non-
free-firmware
deb-src http://deb.debian.org/debian bookworm-backports main contrib non-free
non-free-firmware

From saved file (sources.list.ORIG), I restored the mirror to the original and
working URL,

# bookworm-security
deb http://security.debian.org/debian-security bookworm-security main contrib
non-free non-free-firmware
deb-src http://security.debian.org/debian-security bookworm-security main
contrib non-free non-free-firmware

majd frissítettem. And everything is fine

This is the result I was expecting, the improvement, of course. After all, I
found the error and corrected it using the official method.

However, I first suspected an fresh update (here the mirror is good),

sudo apt-get upgrade
Csomaglisták olvasása... Kész
Függőségi fa építése... Kész
Állapotinformációk olvasása... Kész
Frissítés kiszámítása... Kész
Az alábbi csomagok frissítve lesznek:
  gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 libjavascriptcoregtk-4.0-18
  libjavascriptcoregtk-4.1-0 libwebkit2gtk-4.0-37 libwebkit2gtk-4.1-0
6 frissített, 0 újonnan telepített, 0 eltávolítandó és 0 nem frissített.
Letöltendő adatmennyiség: 53,7 MB.
A művelet után 12,3 kB lemezterület kerül felhasználásra.
Folytatni akarja? [I/n]
Letöltés:1 http://security.debian.org/debian-security bookworm-security/main
amd64 gir1.2-webkit2-4.0 amd64 2.40.5-1~deb12u1 [95,5 kB]

And more tried to fix it this way.

sudo mv var/lib/apt/lists /var/lib/apt/lists.ORIG

sudo apt-get update

and with this commands.

sudo apt-get --allow-releaseinfo-change update

sudo apt-get --allow-releaseinfo-change-suite update

And then I discovered the exact cause of the error...

Unfortunately, the bug exists! Today I tried the mirror switch again, and just
as before, the contents of the sources.list file, the bookworm-security line,
will corrupted.


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

Kernel: Linux 6.4.8-1-liquorix-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages synaptic depends on:
ii  hicolor-icon-theme   0.17-2
ii  libapt-pkg6.02.6.1
ii  libc62.36-9+deb12u1
ii  libept1.6.0  1.2.1
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-3-0   3.24.37-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libstdc++6   12.2.0-14
ii  libvte-2.91-02022-0.60.1-0~202004100917~ubuntu20.04.1
ii  libxapian30  1.4.22-1
ii  pkexec   122-3
ii  policykit-1  122-3
ii  polkitd  122-3

Versions of packages synaptic recommends:
ii  libgtk3-perl  0.038-3
ii  xdg-utils 1.1.3-4.1

Versions of packages synaptic suggests:
ii  apt-xapian-index 0.53
pn  deborphan
pn  dwww 
ii  software-properties-gtk  0.99.30-4
ii  tasksel  3.73

-- no debconf information

Bug#1043140: libweston-12-0: Weston fails to start with "Assertion `csi->width == width' failed"

[Thomas Preud'homme]

Package: libweston-12-0
Version: 12.0.1-1
Severity: important
Tags: upstream

After upgrading my system sddm fails to start a wayland session with the
following error in .local/share/sddm/wayland-session.log:

weston: ../libweston/output-capture.c:398 weston_output_pull_capture_task: 
Assertion `csi->width == width' failed.
Failed to process Wayland connection: Broken pipe
failed to create display: Broken pipe
Failed to process Wayland connection: Broken pipe
failed to create display: Broken pipe

This seems to match upstream bug
https://gitlab.freedesktop.org/wayland/weston/-/issues/757 which is also
against weston 12.0 and has a fix. Hopefully this can be applied to the
Debian package.

Best regards,
Thomas

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

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

Versions of packages libweston-12-0 depends on:
ii  libaml0 0.3.0-1
ii  libc6   2.37-7
ii  libcairo2   1.16.0-7
ii  libdrm2 2.4.115-1
ii  libegl1 1.6.0-1
ii  libfontconfig1  2.14.1-4
ii  libfreerdp-server2-22.10.0+dfsg1-1
ii  libfreerdp2-2   2.10.0+dfsg1-1
ii  libgbm1 23.1.4-1
ii  libgles21.6.0-1
ii  libglib2.0-02.77.1-2
ii  libgstreamer-plugins-base1.0-0  1.22.4-1
ii  libgstreamer1.0-0   1.22.4-1
ii  libinput10  1.23.0-2
ii  libjpeg62-turbo 1:2.1.5-2
ii  liblcms2-2  2.14-2
ii  libneatvnc0 0.6.0+dfsg-4+b1
ii  libpam0g1.5.2-6
ii  libpango-1.0-0  1.50.14+ds-1
ii  libpangocairo-1.0-0 1.50.14+ds-1
ii  libpipewire-0.3-0   0.3.77-1
ii  libpixman-1-0   0.42.2-1
ii  libpng16-16 1.6.40-1
ii  libseat10.8.0-1
ii  libudev1254-1
ii  libva-drm2  2.19.0-1
ii  libva2  2.19.0-1
ii  libwayland-client0  1.22.0-2
ii  libwayland-cursor0  1.22.0-2
ii  libwayland-egl1 1.22.0-2
ii  libwayland-server0  1.22.0-2
ii  libwebp71.2.4-0.2
ii  libwinpr2-2 2.10.0+dfsg1-1
ii  libx11-62:1.8.6-1
ii  libx11-xcb1 2:1.8.6-1
ii  libxcb-composite0   1.15-1
ii  libxcb-render0  1.15-1
ii  libxcb-shm0 1.15-1
ii  libxcb-xfixes0  1.15-1
ii  libxcb-xkb1 1.15-1
ii  libxcb1 1.15-1
ii  libxcursor1 1:1.2.1-1
ii  libxkbcommon0   1.5.0-1

libweston-12-0 recommends no packages.

libweston-12-0 suggests no packages.

-- no debconf information

Bug#1030290: Should have been RC

[Scott Kitterman]

Bumped severity to serious as the package is not working at all.  Although 
fixed in Unstable, it still affects Stable and should be fixed there as well.

Scott K

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

Bug#1043103: Package data not updated since August 4th

[Adam D. Barratt]

On Sun, 2023-08-06 at 08:22 +0200, Sebastiaan Couwenberg wrote:
> The package data on available via NFS on ullmann.d.o hasn't been
> updated 
> since August 4th as reported in #1043103:
> 

Unfortunately one of the sync nodes in the mirror network is
unexpectedly offline, starting late on Friday (UTC). UBC, which hosts
ullmann and coccia, is one of the downstreams affected by that.

While we work out the longer-term solution, I've reconfigured things so
that UBC syncs the main archive from a different sync node. The syncs
for the debian-buildd, debian-ports and debian-security archives are
still not working currently, but the sync for the main archive was
higher priority. (The debian-debug mirror syncs directly from ftp-
master, so was not affected.)

Regards,

Adam

Bug#1042398: debhelper: should disable Python byte-compilation when building .deb with Meson

[Simon McVittie]

Control: tags -1 + patch

On Thu, 27 Jul 2023 at 15:43:26 +0100, Simon McVittie wrote:
> [A Meson behaviour change that breaks the build of src:libgit2-glib]
> can be turned off by passing -Dpython.bytecompile=-1 to `meson setup`.

Please consider
.

I included a version check, to avoid needing debhelper to have a versioned
Breaks on meson (>= 1.2.0).

Also attached as a patch since some maintainers require that. If I receive
review feedback on Salsa, I will assume that's the preferred contribution
route and only update that version, unless reminded to send an updated
patch to the bug.

A convenient test-case for both this and #1043136, without any
particularly large packages, is to rebuild libgit2-glib version 1.1.0-1
(in bookworm, and currently also testing and unstable) using the proposed
debhelper: it will FTBFS until both #1042398 and #1043136 are fixed.

smcv
>From fc2bb90f01d2a09171339178d1cd0a39b1e014bf Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sun, 6 Aug 2023 13:50:13 +0100
Subject: [PATCH] meson: Disable Python byte-compilation if the Meson version
 is new enough

Meson 1.2.0 added support for byte-compilation at build time, and the
default is to do so. In Debian we want byte-compilation to be done at
package install time, so explicitly turn this off. We cannot pass this
option to older Meson versions, because it would make them fail.

Closes: #1042398
Signed-off-by: Simon McVittie 
---
 lib/Debian/Debhelper/Buildsystem/meson.pm | 12 
 1 file changed, 12 insertions(+)

diff --git a/lib/Debian/Debhelper/Buildsystem/meson.pm b/lib/Debian/Debhelper/Buildsystem/meson.pm
index 3cd447de..9e52f74c 100644
--- a/lib/Debian/Debhelper/Buildsystem/meson.pm
+++ b/lib/Debian/Debhelper/Buildsystem/meson.pm
@@ -51,6 +51,13 @@ sub new {
 sub configure {
 	my $this=shift;
 
+	eval { require Dpkg::Version; };
+	error($@) if $@;
+
+	my $output = qx{meson --version};
+	chomp $output;
+	my $version = Dpkg::Version->new($output);
+
 	# Standard set of options for meson.
 	my @opts = (
 		'--wrap-mode=nodownload',
@@ -62,6 +69,11 @@ sub configure {
 	my $multiarch=dpkg_architecture_value("DEB_HOST_MULTIARCH");
 	push @opts, "--libdir=lib/$multiarch";
 	push(@opts, "--libexecdir=lib/$multiarch") if compat(11);
+	# There was a behaviour change in Meson 1.2.0: previously
+	# byte-compilation wasn't supported, but since 1.2.0 it is on by
+	# default. We can only use this option to turn it off in versions
+	# where the option exists.
+	push(@opts, "-Dpython.bytecompile=-1") if $version >= '1.2.0';
 
 	if (is_cross_compiling()) {
 		# http://mesonbuild.com/Cross-compilation.html
-- 
2.40.1

Bug#1042398: debhelper: should disable Python byte-compilation when building .deb with Meson

[Eli Schwartz]

On 8/6/23 9:27 AM, Simon McVittie wrote:
> On Tue, 01 Aug 2023 at 15:14:13 -0400, Eli Schwartz wrote:
>> My conclusion was that all distros want bytecode, except for Debian,
>> which doesn't want bytecode.
> 
> Debian does want bytecode, but the Debian Python team's policy is to
> generate it at package-installation time, rather than generating it at
> package build time and including it in the content of the .deb.


There was an implied "... in the downloadable package archive" there. :D

Indeed, the other distro that simply runs a cleaning pass on the staging
files , runs a package-installation-time script to create them too.


> (This allows the same .deb to be used for more than one major version
> of Python, without always having to rebuild it, as long as it doesn't
> contain compiled extensions; requiring rebuilds for this would be a
> problem because the Debian infrastructure cannot currently do fully
> automated rebuilds of fully-architecture-independent packages, so doing
> those rebuilds would require a package maintainer to sign and upload a
> new package with only trivial changes, which would scale poorly across
> the very large number of packages that depend on Python.)


Aside, but: I find this very troublesome and bad for users. I have
actually attempted to use "more than one major version of python", on
Ubuntu which is admittedly not Debian but does reuse Debian's
infrastructure for this.

It was an unmitigated disaster, and I'm specifically talking about
python packages that contain zero compiled extensions, purely python
code. The issue is that lots of projects need source code changes to run
on newer versions of python, obtained by updating to new upstream releases.

It's very possible this was a Ubuntu-specific issue, but when Ubuntu
Bionic packaged python 3.8 as an optional alternative to the system
python 3.6, I hit lots of issues trying to switch Meson's CI over while
upgrading from 3.6 to "at least 3.7", because various modules were not
actually 3.8-ready and apparently no one bothered to check that the
python3.8 package was compatible with all the software packaged in
Ubuntu that was visible to it.

I had to install them with pip instead, after forcing pip to ignore the
apt versions.



> CMake and Autotools packages have it easier here, because they don't
> fail the build when given an option that is not recognised, so if they
> gained a new option whose action we didn't want, we could give them a
> -DDISABLE_NEW_THING=ON or --disable-new-thing argument unconditionally.


autotools *does* fail the build when given an option that is not
recognized, but it makes a special exception for user options prefixed
with --enable / --disable / --with / --without, and documents this
behavior under the rationale:

"""
An unknown option ordinarily indicates a mistake by the user and
configure halts with an error. However, by default unknown
--with-package and --enable-feature options elicit only a warning, to
support configuring entire source trees.

Source trees often contain multiple packages with a top-level configure
script that uses the AC_CONFIG_SUBDIRS macro (see Subdirectories).
Because the packages generally support different --with-package and
--enable-feature options, the GNU Coding Standards say they must accept
unrecognized options without halting.
"""

You can upgrade that warning to a fatal error using
--enable-option-checking=fatal. Meson doesn't have the underlying
problem, though, because it supports option namespacing, so it would be
like autotools supporting:

--subdir:with-package

Hence meson uses errors instead of warnings.

As for cmake... the less said, the better. :D cmake doesn't support
options at all -- when you use -DDISABLE_NEW_THING=ON, you're setting a
cmake scripting variable, not passing options into an option parser.
cmake isn't capable of warning you on unknown options, which autotools
does. And really, it can't, because the cmake files may not actually
attempt to read DISABLE_NEW_THING except in certain codepaths. There's
no centralized option parser like both autotools and meson have.

So I would say that meson's behavior is pretty standard *for option
parsing*, cmake is just a terrible build system. :D


> I'm aware that Meson is intentionally being strict with -D
> to detect typos and avoid unintended behaviour, but would it
> be possible to add a variant of -D in a future version that
> specifically ignores unrecognised options? Perhaps something like
> --set-option-if-supported=python.bytecompile=-1?


Hmm, I daresay I would not object to such a feature, actually. :)
Although I wonder if it should be limited to machine files.


-- 
Eli Schwartz

Bug#1043136: debhelper: should set DEB_PYTHON_INSTALL_LAYOUT=deb when building .deb with CMake or Meson

[Simon McVittie]

Control: tags -1 + patch

On Sun, 06 Aug 2023 at 14:47:40 +0100, Simon McVittie wrote:
> As a result of upstream changes in meson and changes to the Debian
> packaging/patches of Python, rebuilding gi-docgen with meson >= 1.2.0
> results in the installed tree in debian/tmp putting Python code in
> /usr/local, not /usr.
...
> pybuild avoids this by setting DEB_PYTHON_INSTALL_LAYOUT=deb
...
> I think either debhelper's cmake and meson build systems should be doing
> this for us, or debhelper should be doing this globally, to avoid every
> affected package having to be changed for this.

Please consider
.

Also attached as a patch since some maintainers require that. If I receive
review feedback on Salsa, I will assume that's the preferred contribution
route and only update that version, unless reminded to send an updated
patch to the bug.

smcv
>From 2254e54fec6d6f537d63d90692e69f0f2bbe9f16 Mon Sep 17 00:00:00 2001
From: Simon McVittie 
Date: Sun, 6 Aug 2023 14:02:57 +0100
Subject: [PATCH] cmake, meson: Set DEB_PYTHON_INSTALL_LAYOUT=deb if not
 already set

With recent versions of cmake, meson and python3, the default
installation layout discovered by cmake or meson is below /usr/local,
unless we explicitly override DEB_PYTHON_INSTALL_LAYOUT to tell Python
that we are building a distro package.

Closes: #1043136
Signed-off-by: Simon McVittie 
---
 lib/Debian/Debhelper/Buildsystem/cmake.pm | 12 +++-
 lib/Debian/Debhelper/Buildsystem/meson.pm | 18 +++---
 2 files changed, 22 insertions(+), 8 deletions(-)

diff --git a/lib/Debian/Debhelper/Buildsystem/cmake.pm b/lib/Debian/Debhelper/Buildsystem/cmake.pm
index 2b793939..c64c418e 100644
--- a/lib/Debian/Debhelper/Buildsystem/cmake.pm
+++ b/lib/Debian/Debhelper/Buildsystem/cmake.pm
@@ -79,6 +79,12 @@ sub new {
 	return $this;
 }
 
+sub _get_cmake_env {
+	my $update_env = {};
+	$update_env->{DEB_PYTHON_INSTALL_LAYOUT} = 'deb' unless $ENV{DEB_PYTHON_INSTALL_LAYOUT};
+	return $update_env;
+}
+
 sub configure {
 	my $this=shift;
 	# Standard set of cmake flags
@@ -141,7 +147,10 @@ sub configure {
 
 	$this->mkdir_builddir();
 	eval { 
-		$this->doit_in_builddir("cmake", @flags, @_, $this->get_source_rel2builddir());
+		my %options = (
+			update_env => _get_cmake_env(),
+		);
+		$this->doit_in_builddir(\%options, "cmake", @flags, @_, $this->get_source_rel2builddir());
 	};
 	if (my $err = $@) {
 		if (-e $this->get_buildpath("CMakeCache.txt")) {
@@ -196,6 +205,7 @@ sub install {
 			update_env => {
 'LC_ALL'  => 'C.UTF-8',
 'DESTDIR' => $destdir,
+%{ _get_cmake_env() },
 			}
 		);
 		print_and_doit(\%options, 'cmake', '--install', $this->get_buildpath, @_);
diff --git a/lib/Debian/Debhelper/Buildsystem/meson.pm b/lib/Debian/Debhelper/Buildsystem/meson.pm
index 3cd447de..066216a7 100644
--- a/lib/Debian/Debhelper/Buildsystem/meson.pm
+++ b/lib/Debian/Debhelper/Buildsystem/meson.pm
@@ -48,6 +48,14 @@ sub new {
 	return $this;
 }
 
+sub _get_meson_env {
+	my $update_env = {
+		LC_ALL => 'C.UTF-8',
+	};
+	$update_env->{DEB_PYTHON_INSTALL_LAYOUT} = 'deb' unless $ENV{DEB_PYTHON_INSTALL_LAYOUT};
+	return $update_env;
+}
+
 sub configure {
 	my $this=shift;
 
@@ -92,7 +100,7 @@ sub configure {
 	$this->mkdir_builddir();
 	eval {
 		my %options = (
-			update_env => { LC_ALL => 'C.UTF-8'},
+			update_env => _get_meson_env(),
 		);
 		$this->doit_in_builddir(\%options, "meson", "setup", $this->get_source_rel2builddir(), @opts, @_);
 	};
@@ -115,9 +123,7 @@ sub test {
 			# In compat 13 with meson+ninja, we prefer using "meson test"
 			# over "ninja test"
 			my %options = (
-update_env => {
-	'LC_ALL' => 'C.UTF-8',
-}
+update_env => _get_meson_env(),
 			);
 			if ($this->get_parallel() > 0) {
 $options{update_env}{MESON_TESTTHREADS} = $this->get_parallel();
@@ -144,9 +150,7 @@ sub install {
 		# In compat 14 with meson+ninja, we prefer using "meson install"
 		# over "ninja install"
 		my %options = (
-			update_env => {
-'LC_ALL' => 'C.UTF-8',
-			}
+			update_env => _get_meson_env(),
 		);
 		$this->doit_in_builddir(\%options, 'meson', 'install', '--destdir', $destdir, @args);
 	}
-- 
2.40.1

Bug#939973: tiger: lin001w does not recognize usrmerge

[Richard Lewis]

On Tue, 10 Sep 2019 17:15:45 +0200 Benoit Friry  wrote:

> I did migrate "all in /usr" with usrmerge package.
> After the migration, all my files are in /usr, and there are links from
> /lib to /usr/lib, /bin to /usr/bin and /sbin to /usr/sbin.
>
> lin001w reports files found through links in root as files that do not
> belong to any packages.

This now affects every user of package,

As a workaround you can add

^WARN lin001w File `/(s?bin|lib)/.+' does not belong to any package\.$

to /etc/tiger/tiger.ignore to hide the report - if debian doesn't want
to patch the upstream code, it perhaps makes sense to ship this in
tiger.ignore by default

Bug#1043133: Patch which fixes the bug for me

[Chris Ward]

The following fixes the bug for me. It may need adjusting so that it
can work both for debian 12.0 and previous, and for debian 12.11 where
'firmware-linux' is no longer a separate item.

The patch to binary_rootfs fixes a bug that I reported previously.

diff --git a/./binary_rootfs b/home/tjcw/live-build/binary_rootfs
index af8448d..080ee15 100755
--- a/./binary_rootfs
+++ b/home/tjcw/live-build/binary_rootfs
@@ -106,7 +106,7 @@ case "${LB_CHROOT_FILESYSTEM}" in
dd if=/dev/zero
of=chroot/filesystem.${LB_CHROOT_FILESYSTEM} bs=1024k count=0
seek=${REAL_DIM}

FAKE_MTAB=false
-   if ! Chroot chroot "test -s /etc/mtab"
+   if ! Chroot chroot "test -e /etc/mtab"
then
Chroot chroot "ln -s
/proc/mounts/mtab /etc/mtab"
FAKE_MTAB=true
diff --git a/./chroot_firmware b/home/tjcw/live-build/chroot_firmware
index e22068f..6272c9e 100755
--- a/./chroot_firmware
+++ b/home/tjcw/live-build/chroot_firmware
@@ -54,10 +54,11 @@ Check_package host /usr/bin/wget wget
 FIRMWARE_PACKAGES=""

 # Manually add firmware-linux meta package if available
-if [ $(apt-cache show "^firmware-linux$" 2> /dev/null | grep
"^Package:" | wc -l) -eq 1 ]
-then
-   FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"
-fi
+# 20230806 tjcw firmware-linux no longer shipped as separate package
+#if [ $(apt-cache show "^firmware-linux$" 2> /dev/null | grep
"^Package:" | wc -l) -eq 1 ]
+#then
+#  FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"
+#fi

 Firmware_List_From_Contents "${LB_PARENT_MIRROR_CHROOT}"
"${LB_PARENT_DISTRIBUTION_CHROOT}" "${LB_PARENT_ARCHIVE_AREAS}"

diff --git a/./installer_debian-installer
b/home/tjcw/live-build/installer_debian-installer
index c28b516..edc5edb 100755
--- a/./installer_debian-installer
+++ b/home/tjcw/live-build/installer_debian-installer
@@ -402,10 +402,11 @@ then
FIRMWARE_PACKAGES=""

# Manually add firmware-linux meta package if available
-   if [ $(apt-cache show "^firmware-linux$" 2> /dev/null
| grep "^Package:" | wc -l) -eq 1 ]
-   then
-   FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"
-   fi
+# 20230806 tjcw no firmware-linux any more
+   #if [ $(apt-cache show "^firmware-linux$" 2> /dev/null
| grep "^Package:" | wc -l) -eq 1 ]
+   #then
+   #   FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"
+   #fi

Firmware_List_From_Contents
"${LB_PARENT_MIRROR_CHROOT}" "${LB_PARENT_DISTRIBUTION_CHROOT}"
"${LB_PARENT_ARCHIVE_AREAS}"

Bug#1037966: Also affects normal chroot operation

[Athanasius]

  This bug doesn't only affect `systemctl restart named.service`.  After
upgrading a server to bookworm yesterday I just found that named was
being restarted periodically.

2023-08-06T15:48:31.080060+01:00 river systemd[1]: named.service: Failed with 
result 'timeout'.
2023-08-06T15:48:31.080557+01:00 river systemd[1]: Failed to start 
named.service - BIND Domain Name Server.
2023-08-06T15:48:31.315062+01:00 river systemd[1]: named.service: Scheduled 
restart job, restart counter is at 853.
2023-08-06T15:48:31.315934+01:00 river systemd[1]: Stopped named.service - BIND 
Domain Name Server.
2023-08-06T15:48:31.369499+01:00 river systemd[1]: Starting named.service - 
BIND Domain Name Server...
2023-08-06T15:48:31.370021+01:00 river systemd[1]: Started named.service - BIND 
Domain Name Server.
...
2023-08-06T15:48:31.435786+01:00 river named[792739]: all zones loaded

I tracked this down to `Type=notify` with our chroot not having the
socket present.

  Whilst it took me a while to notice because it was *mostly* working,
this issue *was* causing some downtime during the restarts.  It would
also have been spamming secondary's with notifications upon each
restart.

  I'll go see about implementing the socket in the chroot

-- 
- Athanasius (he/him) = Athanasius(at)miggy.org / https://miggy.org/
  GPG/PGP Key: https://miggy.org/gpg-key
   "And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME


signature.asc
Description: PGP signature

Bug#1043139: linux-image-6.3.0-2-amd64: tg3 backtraces in net/core/skbuff.c:376 __build_skb_around with "Use slab_build_skb() instead"

[наб]

Package: src:linux
Version: 6.3.11-1
Severity: normal

Dear Maintainer,

On boot I get:
-- >8 --
Aug 06 14:49:47 szarotka kernel: [ cut here ]
Aug 06 14:49:47 szarotka kernel: Use slab_build_skb() instead
Aug 06 14:49:47 szarotka kernel: WARNING: CPU: 1 PID: 0 at 
net/core/skbuff.c:376 __build_skb_around+0x103/0x110
Aug 06 14:49:47 szarotka kernel: Modules linked in: nfnetlink pppoe pppox 
ppp_generic slhc sunrpc binfmt_misc zfs(POE) nls_ascii nls_cp437 vfat fat 
zunicode(POE) zzstd(OE) zlua(OE) zavl(POE) icp(POE) zcommon(POE) znvpair(POE) 
i915 spl(OE) bonding snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio 
tls snd_hda_intel snd_intel_dspcfg drm_buddy drm_display_helper 
snd_intel_sdw_acpi snd_hda_codec kvm_intel snd_hda_core cec rc_core snd_hwdep 
ttm snd_pcm iTCO_wdt cfg80211 snd_timer intel_pmc_bxt tg3 kvm drm_kms_helper 
libphy iTCO_vendor_support snd watchdog ppdev i2c_algo_bit evdev soundcore 
pcspkr irqbypass parport_pc lpc_ich parport button sg psmouse acpi_cpufreq 
rfkill wmi_bmof drm loop fuse dm_mod efi_pstore configfs ip_tables x_tables 
ext4 crc16 mbcache jbd2 crc32c_generic sd_mod t10_pi crc64_rocksoft_generic 
crc64_rocksoft crc_t10dif crct10dif_generic sr_mod cdrom crc64 crct10dif_common 
ata_generic ata_piix ehci_pci libata uhci_hcd ehci_hcd scsi_mod sha512_ssse3 
usbcore sha512_generic scsi_common serio_raw usb_common video wmi
Aug 06 14:49:47 szarotka kernel:  smsc47b397 coretemp autofs4
Aug 06 14:49:47 szarotka kernel: CPU: 1 PID: 0 Comm: swapper/1 Tainted: P   
OE  6.3.0-2-amd64 #1  Debian 6.3.11-1
Aug 06 14:49:47 szarotka kernel: Hardware name: Hewlett-Packard HP rp5700 
Business System/0A80h, BIOS 786E4 v01.24 08/23/2016
Aug 06 14:49:47 szarotka kernel: RIP: 0010:__build_skb_around+0x103/0x110
Aug 06 14:49:47 szarotka kernel: Code: 83 4b 9f ff 48 39 c3 0f 84 33 ff ff ff 
0f 0b 48 89 c3 e9 29 ff ff ff 48 c7 c7 84 dc c5 b1 c6 05 43 4e 0e 01 01 e8 7d 
80 79 ff <0f> 0b eb bd 66 0f 1f 84 00 00 00 00 00 90 90 90 90 90 90 90 90 90
Aug 06 14:49:47 szarotka kernel: RSP: 0018:9c504000eda0 EFLAGS: 00010286
Aug 06 14:49:47 szarotka kernel: RAX:  RBX: 8d36471a8000 
RCX: 
Aug 06 14:49:47 szarotka kernel: RDX: 0103 RSI: b1c37476 
RDI: 
Aug 06 14:49:47 szarotka kernel: RBP:  R08:  
R09: 9c504000ec30
Aug 06 14:49:47 szarotka kernel: R10: 0003 R11: b22d1fe8 
R12: 8d36505acf00
Aug 06 14:49:47 szarotka kernel: R13: 002e R14: 8d3646f1f080 
R15: 8d3646f1e9c0
Aug 06 14:49:47 szarotka kernel: FS:  () 
GS:8d365bd0() knlGS:
Aug 06 14:49:47 szarotka kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Aug 06 14:49:47 szarotka kernel: CR2: 566369e0 CR3: 00010cf54000 
CR4: 06e0
Aug 06 14:49:47 szarotka kernel: Call Trace:
Aug 06 14:49:47 szarotka kernel:  
Aug 06 14:49:47 szarotka kernel:  ? __build_skb_around+0x103/0x110
Aug 06 14:49:47 szarotka kernel:  ? __warn+0x81/0x130
Aug 06 14:49:47 szarotka kernel:  ? __build_skb_around+0x103/0x110
Aug 06 14:49:47 szarotka kernel:  ? report_bug+0x191/0x1c0
Aug 06 14:49:47 szarotka kernel:  ? prb_read_valid+0x1b/0x30
Aug 06 14:49:47 szarotka kernel:  ? handle_bug+0x41/0x70
Aug 06 14:49:47 szarotka kernel:  ? exc_invalid_op+0x17/0x70
Aug 06 14:49:47 szarotka kernel:  ? asm_exc_invalid_op+0x1a/0x20
Aug 06 14:49:47 szarotka kernel:  ? __build_skb_around+0x103/0x110
Aug 06 14:49:47 szarotka kernel:  __build_skb+0x4b/0x60
Aug 06 14:49:47 szarotka kernel:  build_skb+0x15/0xb0
Aug 06 14:49:47 szarotka kernel:  tg3_poll_work+0x574/0xe70 [tg3]
Aug 06 14:49:47 szarotka kernel:  ? raw_notifier_call_chain+0x48/0x60
Aug 06 14:49:47 szarotka kernel:  tg3_poll_msix+0x3d/0x170 [tg3]
Aug 06 14:49:47 szarotka kernel:  __napi_poll+0x2b/0x1b0
Aug 06 14:49:47 szarotka kernel:  net_rx_action+0x2a6/0x360
Aug 06 14:49:47 szarotka kernel:  ? __raise_softirq_irqoff+0x1a/0x80
Aug 06 14:49:47 szarotka kernel:  __do_softirq+0xf4/0x301
Aug 06 14:49:47 szarotka kernel:  ? handle_edge_irq+0xa3/0x240
Aug 06 14:49:47 szarotka kernel:  __irq_exit_rcu+0xb5/0x130
Aug 06 14:49:47 szarotka kernel:  common_interrupt+0xbd/0xe0
Aug 06 14:49:47 szarotka kernel:  
Aug 06 14:49:47 szarotka kernel:  
Aug 06 14:49:47 szarotka kernel:  asm_common_interrupt+0x26/0x40
Aug 06 14:49:47 szarotka kernel: RIP: 0010:pv_native_safe_halt+0xf/0x20
Aug 06 14:49:47 szarotka kernel: Code: 0b 66 2e 0f 1f 84 00 00 00 00 00 90 90 
90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa eb 07 0f 00 2d b5 78 28 
00 fb f4  cc cc cc cc 66 2e 0f 1f 84 00 00 00 00 00 66 90 90 90 90 90 90
Aug 06 14:49:47 szarotka kernel: RSP: 0018:9c50400afe58 EFLAGS: 0246
Aug 06 14:49:47 szarotka kernel: RAX: 4000 RBX: 0001 
RCX: 
Aug 06 14:49:47 szarotka kernel: RDX: 8d365bd0 RSI: 8d36409c6800 
RDI: 8d36409c6864
Aug 

Bug#1039591: logcheck: prompting due to modified conffiles which were not modified by the user: /etc/logcheck/header.txt

[Richard Lewis]

On Wed, 12 Jul 2023 at 12:20, Mathias Gibbens  wrote:
>
>   Andreas, thanks for the report, and Richard, thanks for your work as
> well. I think the changes look good, and if there's no other concerns
> I'll merge the salsa MR, and upload a new version to unstable. Once
> that's done, I'll also file a bug for uploading the updated version to
> stable-proposed-updates;

A gentle reminder on the last bit of this - getting it into bookworm
point release. (i think i read somewhere
 that 12.2 would be at the end of august)

 -- let me know if there's anything i can do to help with this (i
couldn't find anything listing what it involves!)

im about to set up a merge request to add a systemd timer, and have
some other changes in mind,
but think we should get this bit done first

Bug#1043138: thunderbird: cannot send OpenPGP signed message: rnp_op_sign_add_signature failed since upgrade to 115.1.0 (sid)

[Jamie McClelland]

Package: thunderbird
Version: 1:115.1.0-1
Severity: normal

Dear Maintainer,

After upgrading to 115.1.0, when sending a message with "Digitally sign"
selected I consistently receive an error that "Sending of the message 
failed." (When

just encrypting it works fine.)

The error console reports:

CryptoAPI.sync() failed result:  Error: rnp_op_encrypt_add_signature failed
encryptAndOrSign chrome://openpgp/content/modules/RNP.jsm:3526
sync chrome://openpgp/content/modules/cryptoAPI/interface.js:56
encryptMessageStart chrome://openpgp/content/modules/encryption.jsm:446
finishCryptoEncapsulation 
chrome://openpgp/content/modules/mimeEncrypt.jsm:516

createMessageFile resource:///modules/MimeMessage.jsm:90
interface.js:46:17
Error: failure in finishCryptoEncapsulation, exitCode: -1
finishCryptoEncapsulation 
chrome://openpgp/content/modules/mimeEncrypt.jsm:537

createMessageFile resource:///modules/MimeMessage.jsm:90
mimeEncrypt.jsm:554:15
mimeEncrypt.js: caught exception: Error
Message: 'failure in finishCryptoEncapsulation, exitCode: -1'
File:chrome://openpgp/content/modules/mimeEncrypt.jsm
Line:537
Stack: 
finishCryptoEncapsulation@chrome://openpgp/content/modules/mimeEncrypt.jsm:537:15

createMessageFile@resource:///modules/MimeMessage.jsm:90:27


Error: failure in finishCryptoEncapsulation, exitCode: -1 
mimeEncrypt.jsm:537:15
finishCryptoEncapsulation 
chrome://openpgp/content/modules/mimeEncrypt.jsm:537

createMessageFile resource:///modules/MimeMessage.jsm:90
InterpretGeneratorResume self-hosted:1455
AsyncFunctionNext self-hosted:852
mailnews.send: NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS: [JavaScript 
Error: "failure in finishCryptoEncapsulation, exitCode: -1" {file: 
"chrome://openpgp/content/modules/mimeEncrypt.jsm" line: 
537}]'[JavaScript Error: "failure in finishCryptoEncapsulation, 
exitCode: -1" {file: "chrome://openpgp/content/modules/mimeEncrypt.jsm" 
line: 537}]' when calling method: 
[nsIMsgComposeSecure::finishCryptoEncapsulation]

createMessageFile resource:///modules/MimeMessage.jsm:90
MessageSend.jsm:137:32
createAndSendMessage resource:///modules/MessageSend.jsm:137
mailnews.send: Sending failed; , exitCode=2153185313, originalMsgURI= 
MessageSend.jsm:362:32

fail resource:///modules/MessageSend.jsm:362
createAndSendMessage resource:///modules/MessageSend.jsm:145
Error: rnp_op_encrypt_add_signature failed RNP.jsm:3526:21




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

Kernel: Linux 6.4.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

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

Versions of packages thunderbird depends on:
ii  debianutils  5.8-1
ii  fontconfig   2.14.1-4
ii  libasound2   1.2.9-1
ii  libatk1.0-0  2.48.3-1
ii  libc62.37-6
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.8-2
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-8
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.14.1-4
ii  libfreetype6 2.13.0+dfsg-1
ii  libgcc-s113.1.0-9
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.76.4-4
ii  libgtk-3-0   3.24.38-2
ii  libnspr4 2:4.35-1.1
ii  libnss3  2:3.91-1
ii  libotr5  4.1.1-5
ii  libpango-1.0-0   1.50.14+ds-1
ii  libstdc++6   13.1.0-9
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.6-1
ii  libx11-xcb1  2:1.8.6-1
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxext6 2:1.3.4-1+b1
ii  libxrandr2   2:1.5.2-2+b1
ii  psmisc   23.6-1
ii  x11-utils7.7+5
ii  zenity   3.44.0-3
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages thunderbird recommends:
ii  hunspell-en-us [hunspell-dictionary]  1:2020.12.07-2
ii  hunspell-hu [hunspell-dictionary] 1:7.5.0-1
ii  hunspell-se [hunspell-dictionary] 1.0~beta6.20081222-1.3
ii  myspell-hy [myspell-dictionary]   0.20.0-2.2

Versions of packages thunderbird suggests:
ii  apparmor  3.0.8-3
ii  fonts-lyx 2.3.7-1
ii  libgssapi-krb5-2  1.20.1-2

-- no debconf information

Bug#1043137: RM: openmw [ppc64el] -- RoQA; BDs on libluajit-5.1-dev

[Sebastian Ramacher]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: ope...@packages.debian.org, sramac...@debian.org
Control: affects -1 + src:openmw

openwm build depends on libluajit-5.1-dev. luajit was removed on ppc64el
a while ago, but apperently openwm was not. So please also remove
openwm on ppc64el.

Cheers
-- 
Sebastian Ramacher

Bug#1037736: [Pkg-sass-devel] Bug#1037736: Bug#1037736: libsass: ftbfs with GCC-13

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2023-08-06 14:07:09)
> Quoting Bo YU (2023-08-06 13:48:43)
> > On Mon, Jul 31, 2023 at 1:09 AM Jonas Smedegaard  wrote:
> > > If you are generally interested in SASS tools and want to help maintain
> > > them in Debian, then you are very welcome to join the team (which is
> > > effectively only me at the moment).
> > Thanks for the invitation. I am happy to maintain SASS tools packages.
> 
> Great!  Please request membership of the salsa group at
> https://salsa.debian.org/groups/sass-team/-/group_members

Please also subscribe to our mailinglist - it is listed at our team page
at https://wiki.debian.org/Teams/Sass (which I created just now,
reminded by my earlier mention of lousy documentation).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1041096: raspi-firmware: kernel removal can render raspi unbootable

[Daniel Moran]

Hi, it looks like this bug was introduced in the suggested patch for 
#1032186 [1].


I've attached a simple patch which rearranges the conditionals to make 
sure the variables containing the Kernel and Initrd names are populated 
even if the command is "remove".


Daniel

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032186#5

On Fri, 14 Jul 2023 15:52:24 -0500 Andreas Kloeckner  
wrote:

Package: raspi-firmware
Version: 1.20230405+ds-1
Severity: important

Dear Maintainer,

When removing a no-longer-in-use kernel recently, the raspi-firmware
postrm script, presumably the fact that this line [1] is not executed
on kernel removals, left me with a /boot/firmware/config.txt containing
the line

kernel=auto

which in turn left the Raspi (Model 4B in case it matters) firmware
very confused, and the machine unbootable.

Andreas

[1] 
https://salsa.debian.org/debian/raspi-firmware/-/blob/9cafcd85f8aed1ec0c0f609b98af591fae367ba2/debian/kernel/postinst.d/z50-raspi-firmware#L128


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

Kernel: Linux 6.3.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages raspi-firmware depends on:
ii  dosfstools  4.2-1
ii  dpkg1.21.22

raspi-firmware recommends no packages.

Versions of packages raspi-firmware suggests:
pn  bluez-firmware 
pn  firmware-brcm80211 
ii  firmware-misc-nonfree  20230515-3

From bdf757722770155e9e885b2fff7f229100ca898c Mon Sep 17 00:00:00 2001
From: Daniel Moran 
Date: Sun, 6 Aug 2023 14:49:31 +0100
Subject: [PATCH 1/1] Ensure kernel and initrd names are set, even on remove

---
 debian/kernel/postinst.d/z50-raspi-firmware | 14 +++---
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/debian/kernel/postinst.d/z50-raspi-firmware b/debian/kernel/postinst.d/z50-raspi-firmware
index 9b3bfa502744..86d5d95fa683 100755
--- a/debian/kernel/postinst.d/z50-raspi-firmware
+++ b/debian/kernel/postinst.d/z50-raspi-firmware
@@ -115,18 +115,18 @@ else
   dtb_path="/usr/lib/linux-image-${latest_kernel#/boot/vmlinuz-}"
 fi
 
-# Do not copy DTBs or kernel/initramfs when removing packages (#1032186)
-if [ "$1" != "remove" ]; then
-  if [ "$KERNEL" = "auto" ] ; then
+if [ "$KERNEL" = "auto" ] ; then
+  latest_kernel_basename=$(basename "$latest_kernel")
+  latest_initrd_basename=$(basename "$latest_initrd")
+  KERNEL=${latest_kernel_basename}
+
+  # Do not copy DTBs or kernel/initramfs when removing packages (#1032186)
+  if [ "$1" != "remove" ]; then
 for dtb in "${dtb_path}"/bcm*.dtb; do
   [ -e "${dtb}" ] || continue
   cp "${dtb}" /boot/firmware/
 done
 
-latest_kernel_basename=$(basename "$latest_kernel")
-latest_initrd_basename=$(basename "$latest_initrd")
-KERNEL=${latest_kernel_basename}
-
 cp "$latest_kernel" /boot/firmware/
 cp "$latest_initrd" /boot/firmware/
   fi
-- 
2.40.1

Bug#1043136: debhelper: should set DEB_PYTHON_INSTALL_LAYOUT=deb when building .deb with CMake or Meson

[Simon McVittie]

Package: debhelper
Version: 13.11.4
Tags: trixie sid
Severity: normal
X-Debbugs-Cc: Timo Röhling 

As a result of upstream changes in meson and changes to the Debian
packaging/patches of Python, rebuilding gi-docgen with meson >= 1.2.0
results in the installed tree in debian/tmp putting Python code in
/usr/local, not /usr.

CMake has a similar issue, which was discussed on -devel recently:


pybuild avoids this by setting DEB_PYTHON_INSTALL_LAYOUT=deb, which tells
Debian's patched Python that we're building a .deb, but this is not done
for packages that use CMake or Meson directly. As well as this being a
regression for existing non-pybuild packages, pybuild is not always
desirable for packages that contain some Python as an implementation
detail, but are not primarily a Python library:
.

I think either debhelper's cmake and meson build systems should be doing
this for us, or debhelper should be doing this globally, to avoid every
affected package having to be changed for this.

There was some confusion over whether deb or deb_system is the preferred
value. The python3.11 changelog suggests that deb_system is preferred for
package builds, but pybuild uses deb, and
 clarifies
that actually, deb is preferred.

I'm trying to prepare a patch for this, which will follow when I have a
bug number to refer to.

smcv

Bug#1043133: Candidate fix -> real fix already exists

[Roland Clobus]

Hello Chris,

On 06/08/2023 15:17, Chris Ward wrote:

I revised 2 files along the lines of

...

and now I can run the live builds that I want to run


I've seen the issue as well and have prepared a fix in git at [1].
This fix has not been released yet.

As you wrote in the first mail, you are using Debian 12.1 to build an 
image. Unfortunately such fixes cannot flow back into Debian stable, so 
for building Debian 12.1 images you'll have to use the git version of 
live-build for now. See the instructions at [2].


With kind regards,
Roland Clobus

[1] 
https://salsa.debian.org/live-team/live-build/-/commit/ba34bfbfd0efdd6c036496f960bf4df1f42ba332

[2] https://wiki.debian.org/ReproducibleInstalls/LiveImages
Section "Use case: while preparing new hooks, using the local git 
checkout of `live-build`" -> The environment variable LIVE_BUILD must be 
correctly set




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1043135: phosh 0.29.0-1 crashes with phoc 0.30 in trixie

[Chris Talbot]

Package: phosh
Version: 0.29.0-1

When I upgraded Trixie this morning, Phoc upgraded to 0.30.0+ds-1 but
Phosh is still at 0.29.0-1. This combination of packages cause a crash
with Phosh.

I suggest that if Phosh is installed, do not let users upgrade Phoc to
0.30 until the newer Phosh lands in Trixie.

-- 
Respectfully,
Chris Talbot

Bug#1042398: debhelper: should disable Python byte-compilation when building .deb with Meson

[Simon McVittie]

On Tue, 01 Aug 2023 at 15:14:13 -0400, Eli Schwartz wrote:
> My conclusion was that all distros want bytecode, except for Debian,
> which doesn't want bytecode.

Debian does want bytecode, but the Debian Python team's policy is to
generate it at package-installation time, rather than generating it at
package build time and including it in the content of the .deb.

(This allows the same .deb to be used for more than one major version
of Python, without always having to rebuild it, as long as it doesn't
contain compiled extensions; requiring rebuilds for this would be a
problem because the Debian infrastructure cannot currently do fully
automated rebuilds of fully-architecture-independent packages, so doing
those rebuilds would require a package maintainer to sign and upload a
new package with only trivial changes, which would scale poorly across
the very large number of packages that depend on Python.)

> a lintian style "error if you have it" approach

To be clear, Lintian is not the thing that makes this a serious problem:
Lintian is a lint tool, which can give recommendations but does not make
packages' builds fail.

The thing that makes this a serious problem is that many packages' builds
have a list of files that are meant to be installed into each .deb. If a
file not in any of those lists appears, the conservative thing to do is to
fail the build, so that a maintainer can check which .deb the newly created
files should have been in and update the packaging accordingly. Because
Meson has not historically built bytecode automatically, packages that
are built using Meson don't include it in their lists of expected files,
causing their build to regress.

> It's theoretically possible to hardcode Debian yet again and skip this
> install script, but only if running inside a package build. Is there
> even a way to detect this? No idea. Not an enthusiastic topic anyway.

I don't think it should be Meson's job to detect this, which is why I
filed this as a debhelper bug, not a Meson bug. debhelper is the component
that's responsible for telling Meson to use --prefix=/usr when building
a .deb, and this seems analogous.

The way in which this could be considered to be a Meson regression is
that Meson < 1.2.0 never compiled bytecode, and Meson >= 1.2.0 compiles
bytecode by default, which was a behaviour change. This causes Meson-built
Python packages to need to change their behaviour, either by disabling the
new default (which as far as I can see can't be done in a
backwards-compatible way and needs a version check) or by making sure they
can cope with the new default.

CMake and Autotools packages have it easier here, because they don't
fail the build when given an option that is not recognised, so if they
gained a new option whose action we didn't want, we could give them a
-DDISABLE_NEW_THING=ON or --disable-new-thing argument unconditionally.

I'm aware that Meson is intentionally being strict with -D
to detect typos and avoid unintended behaviour, but would it
be possible to add a variant of -D in a future version that
specifically ignores unrecognised options? Perhaps something like
--set-option-if-supported=python.bytecompile=-1?

smcv

Bug#1043133: Candidate fix

[Chris Ward]

I revised 2 files along the lines of

tjcw@debian:~/lb$ fgrep -A 2 -r firmware-linux /usr/lib/live/build
/usr/lib/live/build/chroot_firmware:# Manually add firmware-linux meta 
package if available
/usr/lib/live/build/chroot_firmware:# 20230806 tjcw firmware-linux no 
longer shipped as separate package
/usr/lib/live/build/chroot_firmware:#if [ $(apt-cache show 
"^firmware-linux$" 2> /dev/null | grep "^Package:" | wc -l) -eq 1 ]

/usr/lib/live/build/chroot_firmware-#then
/usr/lib/live/build/chroot_firmware:# 
FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"

/usr/lib/live/build/chroot_firmware-#fi
/usr/lib/live/build/chroot_firmware-
--
/usr/lib/live/build/installer_debian-installer:        # Manually add 
firmware-linux meta package if available
/usr/lib/live/build/installer_debian-installer:    # 
20230806 tjcw no firmware-linux any more
/usr/lib/live/build/installer_debian-installer:        #if [ $(apt-cache 
show "^firmware-linux$" 2> /dev/null | grep "^Package:" | wc -l) -eq 1 ]

/usr/lib/live/build/installer_debian-installer-        #then
/usr/lib/live/build/installer_debian-installer:        # 
FIRMWARE_PACKAGES="${FIRMWARE_PACKAGES} firmware-linux"

/usr/lib/live/build/installer_debian-installer-        #fi
/usr/lib/live/build/installer_debian-installer-
tjcw@debian:~/lb$


and now I can run the live builds that I want to run


Chris Ward.

Bug#1008088:

[Yangfl]

Can you kindly post it to upstream? Since it's hard to illustrate your
idea without a screenshot.

Bug#1043116: openvpn-dco-dkms: module fails to build for Linux 6.5: error: implicit declaration of function 'skb_gso_segment'

[Andreas Beckmann]

Followup-For: Bug #1043116
Control: tag -1 sid trixie

The fix may be as simple as adding

#if LINUX_VERSION_CODE >= KERNEL_VERSION(6,5,0)
#include 
#endif

somewhere.
That's all I had to do for fixing r8168-dkms which had the same error.


Andreas

Bug#1040748: pycairo: diff for NMU version 1.24.0-1.1

[Chris Hofstaedtler]

Source: pycairo
Followup-For: Bug #1040748

Control: tags 1040748 + patch
Control: tags 1040748 + pending

Dear maintainer,

I've prepared an NMU for pycairo (versioned as 1.24.0-1.1) and
uploaded it directly. 

Chris


diff -Nru pycairo-1.24.0/debian/changelog pycairo-1.24.0/debian/changelog
--- pycairo-1.24.0/debian/changelog 2023-07-03 19:31:14.0 +0200
+++ pycairo-1.24.0/debian/changelog 2023-08-06 14:42:07.0 +0200
@@ -1,3 +1,13 @@
+pycairo (1.24.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Workaround automatic Python bytecode compilation leading to
+FTBFS. (Closes: #1040748)
+Fixing this in debhelper for all packages would obviously be preferred,
+but for now this has to do.
+
+ -- Chris Hofstaedtler   Sun, 06 Aug 2023 14:42:07 +0200
+
 pycairo (1.24.0-1) unstable; urgency=medium
 
   * Team upload
diff -Nru pycairo-1.24.0/debian/rules pycairo-1.24.0/debian/rules
--- pycairo-1.24.0/debian/rules 2023-07-03 19:31:14.0 +0200
+++ pycairo-1.24.0/debian/rules 2023-08-06 14:41:01.0 +0200
@@ -5,6 +5,9 @@
 %:
dh $@ --with python3,sphinxdoc --buildsystem=meson
 
+override_dh_auto_configure:
+   dh_auto_configure -- -Dpython.bytecompile=-1
+
 execute_after_dh_auto_build:
python3 -m sphinx -bhtml docs debian/tmp-doc/html
# to fix lintian: privacy-breach-generic

Bug#1041704: $MANWIDTH does not overwrite explicit line length in "~/.manpath"

[Colin Watson]

Control: tag -1 fixed-upstream

On Sun, Jul 23, 2023 at 12:23:58AM +0100, Colin Watson wrote:
> On Sat, Jul 22, 2023 at 01:10:23PM +, Bjarni Ingi Gislason wrote:
> > In my ".manpath" for "nroff" was:
> > 
> > DEFINE nroff test-nroff -b -ww -mandoc -rF=0  -P-i -rHY=0 -dAD=l 
> > -rCHECKSTYLE=0 -rLL=90m
> > 
> > Changing the line length with, say "export MANWIDTH=80", had no effect.
> 
> I believe this can be fixed as follows:
> 
> diff --git a/src/man.c b/src/man.c
> index 70d0dc7a..68515eed 100644
> --- a/src/man.c
> +++ b/src/man.c
> @@ -685,8 +685,7 @@ static int get_roff_line_length (void)
>  {
>   int line_length = cat_width ? cat_width : get_line_length ();
>  
> - /* groff >= 1.18 defaults to 78. */
> - if ((!troff || ditroff) && line_length != 80) {
> + if (!troff || ditroff) {
>   int length = line_length * 39 / 40;
>   if (length > line_length - 2)
>   return line_length - 2;
> 
> This may be the right thing to do.  However, it will mean that the -rLL
> in your ~/.manpath is always overridden, so I don't understand why
> you're going to the effort of specifying it explicitly in the first
> place if you want it to be overridden.  Can you explain why you're doing
> this?

In the absence of feedback, I've gone ahead and committed this upstream,
since it doesn't seem to make sense for the -rLL to be overridden if and
only if the requested width is 80 columns.

  https://gitlab.com/man-db/man-db/-/commit/39cdee4ada

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

Bug#1043078: linux-image-6.3.0-2-amd64: kernel NULL pointer dereference with MD write-back journal

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

On Sat, Aug 05, 2023 at 12:45:18PM -0700, Corey Hickey wrote:
> Package: src:linux
> Version: 6.3.11-1
> Severity: normal
> 
> Dear Maintainer,
> 
> I was testing RAID-5 write-back journal (AKA cache) for the first time.
> 
> https://docs.kernel.org/driver-api/md/raid5-cache.html
> 
> I experienced a NULL pointer dereference early in the process.
> 
>  steps leading up to the crash ---
> 
> Make a RAID-1 from a pair of SSDs.
> 
> $ sudo mdadm --create /dev/md101 -l 1 -n 2 
> /dev/disk/by-id/ata-Samsung_SSD_850_PRO_256GB_S251NX0H60631*
> 
> Make a RAID-5 containing the journal and three block device (one of
> which is, in turn a RAID). Size is restricted to 10 GB for testing
> purposes.
> 
> $ sudo mdadm --create /dev/md5 -n 3 -l 5 -z 10G --write-journal /dev/md101 -c 
> 128K /dev/disk/by-id/ata-TOSHIBA_HDWG21C_* /dev/md3
> 
> I waited for the RAID to re-sync (this is necessary in order to enable
> write-back jornal mode, though not documented).
> 
> Enable write-back mode:
> 
> $ echo write-back | sudo tee /sys/block/md5/md/journal_mode
> 
> Test writes to the RAID-5 via dd:
> 
> $ sudo dd if=/dev/zero of=/dev/md5 iflag=fullblock oflag=direct bs=1M 
> count=10240
> 
>  observed behavior --
> Writes proceded at 100 +/- 4 MB/sec to the journal disks.
> Writes proceded at 29 +/- 1 MB/sec to the RAID-5 member devices.
> This lasted for 50 +/1 1 second, at which point writes stopped and the
> kernel printed an error:
> BUG: kernel NULL pointer dereference, address: 0157

If possible can you verify the issue is still present in either the
newest 6.4.y upstream or mainline (or nearest to that, the
6.5~rc4-1~exp1 in experimental)?

If so can you report the issue upstream and link back here the
upstream report?

Regards,
Salvatore

Bug#1043134: guile-gnutls: FTBFS against gnutls28 3.8.1

[Andreas Metzler]

Package: guile-gnutls
Version: 3.7.12
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)

I have already forwarded this upstream
https://gitlab.com/gnutls/guile/-/issues/15

Bug#1043128: kodi: FTBFS on s390x

[Vasyl Gello]

Hi Sebastian,

Thanks for the report! I did a preliminary investigation yesterday and filed the
bug against gcc-13 [1]. In the meantime I will include the workaround for it
and upload the -4 (as there is another ffmpeg6-related crash fix to upload).

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043076

-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Bug#1037736: [Pkg-sass-devel] Bug#1037736: libsass: ftbfs with GCC-13

[Jonas Smedegaard]

Quoting Bo YU (2023-08-06 13:48:43)
> Sorry for the later reply, I was travelling some days and now I can
> own my time.

No problem - there is no rush, so just take your time :-)


> On Mon, Jul 31, 2023 at 1:09 AM Jonas Smedegaard  wrote:
> > If you are generally interested in SASS tools and want to help maintain
> > them in Debian, then you are very welcome to join the team (which is
> > effectively only me at the moment).
> Thanks for the invitation. I am happy to maintain SASS tools packages.

Great!  Please request membership of the salsa group at
https://salsa.debian.org/groups/sass-team/-/group_members

> At the moment I need to take some time to understand their technical
> details but maintaining them should be okay given the packages were in
> a good sharp.

Don't hesitate to ask!  This is a very small team, and I am bad at
writing documentation so some things are only in my head and maybe not
easy to guess, to please just ask!

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1043133: live-build fails with debian 12.1 becuase it expects linux-firmware

[Chris Ward]

Package: live-build
Version: 1:20230502
Severity: important
X-Debbugs-Cc: t...@cantab.net

Dear Maintainer,

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

   * What led up to the situation?
I installed debian 12.1 in a VM and installed the live-build package
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I attempted to use live-build to build an ISO
   * What was the outcome of this action?
I got an error message about linux-firmware not being available
   * What outcome did you expect instead?
A successful build of a live ISO

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


-- Package-specific info:

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

Kernel: Linux 6.1.0-10-amd64 (SMP w/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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages live-build depends on:
ii  debootstrap  1.0.128+nmu2

Versions of packages live-build recommends:
ii  apt-utils   2.6.1
ii  bzip2   1.0.8-5+b1
ii  cpio2.13+dfsg-7.1
ii  cryptsetup  2:2.6.1-4~deb12u1
ii  file1:5.44-3
ii  live-boot-doc   1:20230131
ii  live-config-doc 11.0.3+nmu1
ii  live-manual-html [live-manual]  2:20151217.2
ii  rsync   3.2.7-1
ii  systemd-container   252.12-1~deb12u1
ii  wget1.21.3-1+b2
ii  xz-utils5.4.1-0.2

Versions of packages live-build suggests:
ii  e2fsprogs  1.47.0-2
pn  mtd-utils  
ii  parted 3.5-3

-- no debconf information