Bug#1031923: marked as done (d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck)

[Debian Bug Tracking System]

Your message dated Wed, 1 Mar 2023 08:32:13 +0100
with message-id <20230301073213.m47xk7d3ixzfn...@mraw.org>
and subject line Re: Bug#1031923: d-i.debian.org: testing (bookworm): Unable to 
boot due to unsupported FEATURE_C12 in e2fsck
has caused the Debian Bug report #1031923,
regarding d-i.debian.org: testing (bookworm): Unable to boot due to unsupported 
FEATURE_C12 in e2fsck
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: d-i.debian.org
Severity: grave
Tags: d-i
Justification: renders package unusable
X-Debbugs-Cc: cqu...@arcor.de

I have installed Debian testing (bookworm) from one of the latest ISO images
(https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-
amd64-netinst.iso from 2023-02-21) and after an apparently succesfull
installation the system cannot be booted.

The screen shows this message when trying to boot:



/dev/mapper/hostname--vg-root has unsupported feature(s): FEATURE_C12
e2fsck: Get a newer version of e2fsck

/dev/mapper/hostname--vg-root: * WARNING: Filesystem still has errors
**

fsck exited with status code 12
The root filesystem on /dev/mapper/hostname--vg-root requires a manual fsck



And after that a BusyBox prompt is offered. I have tried several times the
installation all of them with the same result. Installing Debian bullseye
proceeded without errors in the same system.
--- End Message ---
--- Begin Message ---
Cyril Brulebois  (2023-02-27):
> Unfortunately, I wasn't aware of those instructions, and that looks utterly
> buggy. How can we claim to publish “official images” that are snapshots, built
> using debian-installer daily builds, that can be broken by random packages in
> unstable, and left unfixed for weeks?!
> 
> We already have specific instructions on the d-i page[1] regarding
> *actual* official releases (as soon as testing gets an Alpha 1), plus
> snapshots. My first instinct would be to entirely scrap testing-related
> things from the page you started from[2], and just redirect to [1]
> instead.
> 
>  1. https://www.debian.org/devel/debian-installer/
>  2. https://www.debian.org/CD/http-ftp/

Just pushed:
  
https://salsa.debian.org/webmaster-team/webwml/-/commit/3b306bd46ff504f215e2758f81199d663bc27d0a
  
https://salsa.debian.org/webmaster-team/webwml/-/commit/eadc4392f9f84dc7a3ce1881472a18a42a52d748
  
https://salsa.debian.org/webmaster-team/webwml/-/commit/554e4e9521a3d022ea052a28fdc6a215cc1f3c5b

Note the website is built every few hours, and those updates will need
to be picked up by translators.

> That link should be updated too… http://debian-cd.debian.net/

No idea whether that's still useful/maintained, but switched to
https:// along with other external links getting adjusted:

  
https://salsa.debian.org/webmaster-team/webwml/-/commit/3d70cb0d8821c3f8ec922ac96298ad77e041fc7e

At least right now, it's reporting 11.5.0 as been the latest, which is
obviously wrong…


Closing this bug report I've been using to track buggy claims on the
website.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature
--- End Message ---

Bug#1032177: faketime doesn't fake time (on i386)

[Jakub Wilk]

Package: faketime
Version: 0.9.10-2.1
Severity: grave

faketime no longer works on i386:

   $ faketime -f '2008-12-24 08:15:42' date -R
   Wed, 01 Mar 2023 08:25:58 +0100


-- System Information:
Architecture: i386

Versions of packages faketime depends on:
ii  libfaketime  0.9.10-2.1
ii  libc62.36-8

--
Jakub Wilk

Bug#1030638: cp -a fails to preserve ownership information on 32-bit arches

[Shengjing Zhu]

On Wed, Mar 1, 2023 at 3:00 PM Johannes Schauer Marin Rodrigues
 wrote:
>
> Hi Shengjing,
>
> Quoting Shengjing Zhu (2023-03-01 06:40:38)
> > I've debugged it as well and here is my write up. Though I don't have
> > solution yet.
>
> you don't have a *good* solution yet but I think you are extremely close! 
> Thank
> you so much for spending all the time debugging this *and* for this very
> helpful writeup which is helpful for guys like me who could've never come this
> far by themselves. Thank you! :)
>
> Would it maybe possible to choose the correct stat struct by trying to see 
> with
> which struct the values make sense? For example it should be easy to check
> which inode numbers actually exist. The other entries of the stat struct also
> can be checked if they look legitimate, like the file mode (which should not 
> be
> larger than 0o4777).

I realized there probably was no need for runtime detection after some
discussion with others.

After all, it has already dispatched the right _time64 function. But
on i386, the only case to use _time64 function is when compiled with
D_TIME_BITS=64.
So there shouldn't be two variants of stat64 struct. It's just
fakeroot is using the wrong one.
fakeroot should compile its all time64 funcs with D_TIME_BITS=64, then
it should get the right struct. (only these _time64 parts, so be in
separate files.)

I'm still exploring this idea, but anyone more familiar with autoconf
would be helpful!

-- 
Shengjing Zhu

Bug#1030638: cp -a fails to preserve ownership information on 32-bit arches

[Johannes Schauer Marin Rodrigues]

Hi Shengjing,

Quoting Shengjing Zhu (2023-03-01 06:40:38)
> I've debugged it as well and here is my write up. Though I don't have
> solution yet.

you don't have a *good* solution yet but I think you are extremely close! Thank
you so much for spending all the time debugging this *and* for this very
helpful writeup which is helpful for guys like me who could've never come this
far by themselves. Thank you! :)

Would it maybe possible to choose the correct stat struct by trying to see with
which struct the values make sense? For example it should be easy to check
which inode numbers actually exist. The other entries of the stat struct also
can be checked if they look legitimate, like the file mode (which should not be
larger than 0o4777).

What do you think?

Thanks!

cheers, josch

Bug#1019841: marked as done (amule: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2023 06:50:09 +
with message-id 
and subject line Bug#1019841: fixed in amule 1:2.3.3-3
has caused the Debian Bug report #1019841,
regarding amule: Please transition to wxwidgets3.2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1019841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: amule
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition amule from wxwidgets3.0 to wxwidgets3.2.

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: amule
Source-Version: 1:2.3.3-3
Done: Sandro Tosi 

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

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

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated amule package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Mar 2023 01:32:05 -0500
Source: amule
Architecture: source
Version: 1:2.3.3-3
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 1019841
Changes:
 amule (1:2.3.3-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Apply multi-arch hints.
 + amule-common: Add Multi-Arch: foreign.
   * Use secure URI in Homepage field.
   * Drop transition for old debug package migration.
   * Update standards version to 4.6.0, no changes needed.
   * Remove constraints unnecessary since buster (oldstable):
 + Build-Depends: Drop versioned constraint on libupnp-dev (>= 1:1.6.24-4~).
 + amule: Drop conflict with removed package amule-common (<<
   2.2.0~svn20080525-1) in Replaces.
 + amule-common: Drop conflict with removed package amule-daemon (<< 
2.1.2-3)
   in Replaces.
 + amule-common: Drop conflict with removed package amule-utils (<< 2.0.3-4)
   in Replaces.
 + amule-utils: Drop conflict with removed package amule (<< 2.1.2-1) in
   Replaces.
 + amule-utils: Drop conflict with removed package amule-common (<< 2.1.2-3)
   in Replaces.
 .
   [ Pino Toscano ]
   * Drop menu files and their Debian-specific pixmaps, since amule &
 amule-utils-gui already provide .desktop files.
 .
   [ Olly Betts ]
   * Update to use wxwidgets3.2 - new patch wx3.2.patch; Closes: #1019841
Checksums-Sha1:
 788a66b3b7497466893469fd98ffd9d5608bd783 2293 amule_2.3.3-3.dsc
 cc2253cd6a28c8cfcc0c9d839d45b6236af6ff04 29992 amule_2.3.3-3.debian.tar.xz
 6c2a1a2c1b17ecc4328fa7dbe02b4c079084c99a 13970 amule_2.3.3-3_source.buildinfo
Checksums-Sha256:
 3f4f3dfcc71bf95a14d5ee0859fc27cc762df62e3f34dad33c51f949ab0b6c8d 2293 
amule_2.3.3-3.dsc
 1e6127eead0cd61c08cac8c027a015f636178c4b4d0124f55884c0396086ac81 29992 
amule_2.3.3-3.debian.tar.xz
 d6456864a69b8d7a00b668bc016f1c3d318d3f0b1ec3d889089f2d338a777480 13970 
amule_2.3.3-3_source.buildinfo
Files:
 8b750946a8a335130f4afd9bf5d95765 2293 net optional amule_2.3.3-3.dsc
 cf603e59872a90492065bb8ff9aed1f8 29992 net optional amule_2.3.3-3.debian.tar.xz
 2bbb97cbfd1a251916f6423a927489ac 13970 net optional 
amule_2.3.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAmP+8aEACgkQh588mTgB
qU+3+A//aZj9yNIfr5wUgKQRfkaUphnDnw5XaiDRJXCrairlw8+MPo35e403/DGw
xSn8vx/iEvpY/D5Jje7Nt2tBgyJ15WMIOUjWcnpipy/OqnadfBgkX8ms62hR58Cy
GsCF6Q69hFsilGfgtOub3CtYPWTO5biPsSXlLIzMB4PlgmpQlz0qd5iXu08CsVXz
Y9WUhJZrfJbD6ZIj1dx6SpNL/s88GJkmssZuk10ZB8qSAjMPBPbNFt6uag9G43Yo

Bug#1030638: cp -a fails to preserve ownership information on 32-bit arches

[Shengjing Zhu]

X-Debbugs-Cc: z...@debian.org, cl...@debian.org, jo...@debian.org

Hi,

I've debugged it as well and here is my write up. Though I don't have solution
yet.

I use an i386 VM for testing and following code to simplify my test.

```c
int main() {
 struct stat buf;
 int r;
 r = fstatat(AT_FDCWD, "./test.c", , 0);
 printf("%d %d %d\n", r, buf.st_ino, buf.st_gid);
}
```

Compile it with:

$ gcc -g -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 ./test.c

This same as coreutils that enables time64 support.

with the instruction in DEBUG file:

$ gdb ./a.out
(gdb) set env FAKEROOTKEY=430935964
(gdb) set env LD_PRELOAD=./prefix/lib/libfakeroot-0.so
(gdb) b main
Breakpoint 1 at 0x11b6: file ./test.c, line 10.
(gdb) r
Starting program: /home/debian/a.out 
Breakpoint 1, main () at ./test.c:10
10   r = fstatat(AT_FDCWD, "./test.c", , 0);
(gdb) s
__fstatat64_time64 (dir_fd=-100, path=0x402008 "./test.c", st=0xb4d0, 
flags=0) at libfakeroot.c:2700
2700  r=NEXT_FSTATAT64_TIME64(ver, dir_fd, path, st, flags);
(gdb) p st
$1 = (struct stat64 *) 0xb4d0
(gdb) p *st
$2 = {st_dev = 11676941228, __pad1 = 3086760800, __st_ino = 1, st_mode = 0, 
st_nlink = 1, st_uid = 3087006272, st_gid = 0, st_rdev = 13257672154138279935, 
__pad2 = 3087005192, 
  st_size = -5188164414456463360, st_blksize = 44, st_blocks = 
-4611686117211635712, st_atim = {tv_sec = -1208183472, tv_nsec = 0}, st_mtim = 
{tv_sec = -1210426833, 
tv_nsec = -1208328120}, st_ctim = {tv_sec = -1208207344, tv_nsec = 
-1208108853}, st_ino = 13257533047527070255}
(gdb) n
2701  if(r)
(gdb) p *st
$3 = {st_dev = 2049, __pad1 = 262484, __st_ino = 0, st_mode = 33188, st_nlink = 
1, st_uid = 1000, st_gid = 1000, st_rdev = 0, __pad2 = 221, st_size = 
17592186044416, st_blksize = 8, 
  st_blocks = 7205240262505791488, st_atim = {tv_sec = 0, tv_nsec = 29600}, 
st_mtim = {tv_sec = 0, tv_nsec = 1677600726}, st_ctim = {tv_sec = 0, tv_nsec = 
9200}, 
  st_ino = 7205240253915856896}
(gdb) p (struct __stat64_t64)(*st)
$4 = {st_dev = 2049, st_ino = 262484, st_mode = 33188, st_nlink = 1, st_uid = 
1000, st_gid = 1000, st_rdev = 0, st_size = 221, st_blksize = 4096, st_blocks = 
8, st_atim = {
tv_sec = 1677600728, tv_nsec = 29600}, st_mtim = {tv_sec = 1677600726, 
tv_nsec = 9200}, st_ctim = {tv_sec = 1677600726, tv_nsec = 10800}}

We can see that st struct is decoded into a wrong layout.
It causes the message passed to faked has wrong inode.

To verify the guess, I use following dirty patch,

>From ea3eab6ea82604f9a16d658f7fc7ec5ce4bc337d Mon Sep 17 00:00:00 2001
From: Shengjing Zhu 
Date: Wed, 1 Mar 2023 13:21:25 +0800
Subject: [PATCH] hack

---
 communicate.c | 35 +++
 communicate.h |  1 +
 libfakeroot.c |  9 +++--
 stat64.h  | 15 +++
 4 files changed, 58 insertions(+), 2 deletions(-)
 create mode 100644 stat64.h

diff --git a/communicate.c b/communicate.c
index dec9cc6..f7bbaf4 100644
--- a/communicate.c
+++ b/communicate.c
@@ -63,6 +63,8 @@
 #include "stats.h"
 #endif
 
+#include "stat64.h"
+
 #ifndef _UTSNAME_LENGTH
 /* for LINUX libc5 */
 #  define _UTSNAME_LENGTH _SYS_NMLN
@@ -864,6 +866,39 @@ void send_get_stat64(struct stat64 *st
   }
 }
 
+void send_get_stat64_2(struct stat64 *st)
+{
+  struct fake_msg buf;
+
+#ifndef FAKEROOT_FAKENET
+  if(init_get_msg()!=-1)
+#endif /* ! FAKEROOT_FAKENET */
+  {
+  buf.st.mode =((struct x__stat64 *)st)->st_mode;
+  buf.st.ino  =((struct x__stat64 *)st)->st_ino ;
+  buf.st.uid  =((struct x__stat64 *)st)->st_uid ;
+  buf.st.gid  =((struct x__stat64 *)st)->st_gid ;
+  buf.st.dev  =((struct x__stat64 *)st)->st_dev ;
+  buf.st.rdev =((struct x__stat64 *)st)->st_rdev;
+  buf.st.nlink=((struct x__stat64 *)st)->st_nlink;
+
+  fprintf(stderr, "libfakeroot: before ino %ld uid %ld gid %ld \n", 
buf.st.ino, buf.st.uid, buf.st.gid);
+
+buf.id=stat_func;
+send_get_fakem();
+
+
+  ((struct x__stat64 *)st)->st_mode =buf.st.mode;
+  ((struct x__stat64 *)st)->st_ino  =buf.st.ino ;
+  ((struct x__stat64 *)st)->st_uid  =buf.st.uid ;
+  ((struct x__stat64 *)st)->st_gid  =buf.st.gid ;
+  ((struct x__stat64 *)st)->st_dev  =buf.st.dev ;
+  ((struct x__stat64 *)st)->st_rdev =buf.st.rdev;
+
+  fprintf(stderr, "libfakeroot: after ino %ld uid %ld gid %ld \n", buf.st.ino, 
buf.st.uid, buf.st.gid);
+  }
+}
+
 void send_get_xattr64(struct stat64 *st
, xattr_args *xattr
 #ifdef STUPID_ALPHA_HACK
diff --git a/communicate.h b/communicate.h
index a586108..5562402 100644
--- a/communicate.h
+++ b/communicate.h
@@ -211,6 +211,7 @@ extern void unlock_comm_sd(void);
 #ifndef STUPID_ALPHA_HACK
 extern void send_stat64(const struct stat64 *st, func_id_t f);
 extern void send_get_stat64(struct stat64 *buf);
+extern void send_get_stat64_2(struct stat64 *buf);
 extern void send_get_xattr64(struct stat64 *st, xattr_args *xattr);
 #else
 extern void send_stat64(const struct stat64 *st, func_id_t f, int ver);
diff --git a/libfakeroot.c b/libfakeroot.c
index 26a3e90..5eb35b3 

Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"

[tony mancill]

On Tue, Feb 28, 2023 at 11:13:35PM +0100, Markus Koschany wrote:
> Control: reassign -1 shrinksafe
> Control: severity -1 serious
> 
> I uploaded a new version of rhino a while ago and it seems this bug is still
> relevant. I have rebuilt dojo with rhino 1.7.14 and all shrinksafe tests pass.
> However the same tests fail with autopkgtest and block the migration of rhino
> to testing. Could you take a look at that please?

I'm not able to reproduce the autopkgtest failure locally running in
clean sid chroots.  First, I build the dojo source package and ran the
autopkgtest against those binaries.  When that didn't fail, I pulled the
binary packages from the archive and ran the autopkgtest against those.
Again, no failures.

I see the autopkgtest failure when I run against a bookworm chroot.

So it seems like the migration of rhino will resolve the test failure.
(Or I'm missing something fundamental.)


signature.asc
Description: PGP signature

Bug#1031357: marked as done (firefox 109 is obsolete/insecure, firefox 110 needs rustc >= 1.65, not in unstable)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2023 04:05:07 +
with message-id 
and subject line Bug#1031357: fixed in firefox 110.0.1-1
has caused the Debian Bug report #1031357,
regarding firefox 109 is obsolete/insecure, firefox 110 needs rustc >= 1.65, 
not in unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox
Version: 109.0-1
Severity: serious

Several vulnerabilities have been fixed in Firefox 110:
  https://www.mozilla.org/en-US/security/advisories/mfsa2023-05/

So Firefox should be updated to this version. However, it now
build-depends on rustc >= 1.65, which will not be in unstable
during the freeze, thus not before several months.

There should either be an alternate way to get Firefox 110 in
unstable (e.g. include rust for the Firefox build or ask for a
rustc-unstable package[*]?), or it should (permanently?) move
to experimental.

[*] which will never go to testing, just like the firefox package.

-- Package-specific info:


-- Addons package information

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

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

Versions of packages firefox depends on:
ii  debianutils  5.7-0.4
ii  fontconfig   2.14.1-4
ii  libasound2   1.2.8-1+b1
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-8
ii  libcairo-gobject21.16.0-7
ii  libcairo21.16.0-7
ii  libdbus-1-3  1.14.6-1
ii  libdbus-glib-1-2 0.112-3
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.4-1
ii  libfontconfig1   2.14.1-4
ii  libfreetype6 2.12.1+dfsg-4
ii  libgcc-s112.2.0-14
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.5-1
ii  libgtk-3-0   3.24.36-3
ii  libnspr4 2:4.35-1
ii  libnss3  2:3.87.1-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libstdc++6   12.2.0-14
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.3-3
ii  libx11-xcb1  2:1.8.3-3
ii  libxcb-shm0  1.15-1
ii  libxcb1  1.15-1
ii  libxcomposite1   1:0.4.5-1
ii  libxdamage1  1:1.1.6-1
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxrandr2   2:1.5.2-2+b1
ii  libxtst6 2:1.2.3-1.1
ii  procps   2:4.0.2-3
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages firefox recommends:
ii  libavcodec59  7:5.1.2-2

Versions of packages firefox suggests:
ii  fonts-lmodern  2.005-1
ii  fonts-stix [otf-stix]  1.1.1-4.1
ii  libcanberra0   0.30-10
ii  libgssapi-krb5-2   1.20.1-1
ii  pulseaudio 16.1+dfsg1-2+b1

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: firefox
Source-Version: 110.0.1-1
Done: Mike Hommey 

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

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

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated firefox package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Mar 2023 08:35:30 +0900
Source: firefox
Architecture: source
Version: 110.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 

Bug#1030284: [Pkg-javascript-devel] Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

[Jérémy Lal]

Le mer. 1 mars 2023 à 02:30, Thorsten Glaser  a écrit :

> Jérémy Lal dixit:
>
> >I can build nodejs on amhdal.debian.org if you're not comfortable with
> that.
>
> The problem with the DSA porterboxen is that you cannot install your own
> built packages in the chroot to use them there… unless there’s a
> solution not yet known to me?
>

Indeed, but the binary can be run from build dir, so I just need to try and
reproduce the bug from there.

Processed: reopening 987008

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 987008
Bug #987008 {Done: Antoine Beaupré } [grub2] Grub fails to 
find LVM volume after previous LV rename
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions grub2/2.06-8.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
987008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#987008: marked as done (Grub fails to find LVM volume after previous LV rename)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2023 01:31:34 +
with message-id 
and subject line Bug#987008: fixed in grub2 2.06-8.1
has caused the Debian Bug report #987008,
regarding Grub fails to find LVM volume after previous LV rename
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
987008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub2
Version: 2.02+dfsg1-20+deb10u4

-- System Information:
Debian Release: 10.8
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-14-clp-eseries-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

lvm2 version: 2.03.02-3
libc6 version: 2.28-10

Dear Maintainer,

We are seeing a problem with the latest buster version of grub2 with finding 
our LVM volume to boot from.
Our host has a single VG (named 'system'), with around 10 LVs.   One of the LVs 
is system-root.active which 
is what we boot from.   It contains both the /boot volume as well as the rest 
of the OS.   Also we are
using legacy boot on this host.

We are finding that if you rename an LV (not the LV we boot from), that on a 
reboot, we sometimes cannot
find the boot LV and end up at grub rescue prompt:

error: disk `lvm/system-root.active' not found. 

Entering rescue mode... 

grub rescue>

For a test, we have a LV which is not in use and we rename it to something else 
and then reboot.   After about 220
iterations of this, we run into this problem.   We are able to boot these hosts 
through a PXE server so that we
can get access to the drive which contains this VG.  When we do this sort of 
boot, we are not actually using the VG.
When we do this and then simply rename that unused LV again and then reboot, 
suddenly it will boot up again.

We reverted back to grub version 2.02+dfsg1-20+deb10u3 and the problem went 
away.

As part of our investigation of this matter, I have been running 
grub-bios-setup command after PXE booting.  I chroot
into the LV system-root.active and run the grub-bios-setup command with 
appropriate parameters and verbose enabled
as we have seen this to also fail due to the same problem.   Below is the 
output from that command when we fail:


grub-bios-setup: info: adding `hd0' -> `/dev/sda' from device.map.
grub-bios-setup: info: /dev/sda is present.
grub-bios-setup: info: Looking for /dev/sda.
grub-bios-setup: info: /dev/sda is a parent of /dev/sda.
grub-bios-setup: info: /dev/sda is present.
grub-bios-setup: info: Looking for /dev/sda.
grub-bios-setup: info: /dev/sda is a parent of /dev/sda.
grub-bios-setup: info: transformed OS device `/dev/sda' into GRUB device `hd0'.
grub-bios-setup: info: reading /boot/grub/i386-pc/boot.img.
grub-bios-setup: info: reading /boot/grub/i386-pc/core.img.
grub-bios-setup: info: root is `(null)', dest is `hd0'.
grub-bios-setup: info: Opening dest.
grub-bios-setup: info: drive = 0.
grub-bios-setup: info: the size of hd0 is 62533296.
grub-bios-setup: info: changing current directory to /dev/mapper.
grub-bios-setup: info: /dev/mapper/system-root.active is not present.
grub-bios-setup: info: changing current directory to /dev.
grub-bios-setup: info: changing current directory to system.
grub-bios-setup: info: changing current directory to mapper.
grub-bios-setup: info: changing current directory to disk.
grub-bios-setup: info: changing current directory to by-label.
grub-bios-setup: info: changing current directory to by-uuid.
grub-bios-setup: info: changing current directory to by-partuuid.
grub-bios-setup: info: changing current directory to by-id.
grub-bios-setup: info: changing current directory to by-path.
grub-bios-setup: info: changing current directory to block.
grub-bios-setup: info: /dev/sda1 is present.
grub-bios-setup: info: Looking for /dev/sda1.
grub-bios-setup: info: /dev/sda is a parent of /dev/sda1.
grub-bios-setup: info: /dev/sda1 starts from 2048.
grub-bios-setup: info: opening the device hd0.
grub-bios-setup: info: drive = 0.
grub-bios-setup: info: the size of hd0 is 62533296.
grub-bios-setup: info: drive = 0.
grub-bios-setup: info: the size of hd0 is 62533296.
grub-bios-setup: info: Scanning for DISKFILTER devices on disk hd0.
grub-bios-setup: info: Scanning for mdraid1x devices on disk hd0.
grub-bios-setup: info: Scanning for mdraid09 devices on disk hd0.
grub-bios-setup: info: 

Bug#1030284: [Pkg-javascript-devel] Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

[Thorsten Glaser]

Jérémy Lal dixit:

>I can build nodejs on amhdal.debian.org if you're not comfortable with that.

The problem with the DSA porterboxen is that you cannot install your own
built packages in the chroot to use them there… unless there’s a
solution not yet known to me?

bye,
//mirabilos
-- 
“ah that reminds me, thanks for the stellar entertainment that you and certain
other people provide on the Debian mailing lists │ sole reason I subscribed to
them (I'm not using Debian anywhere) is the entertainment factor │ Debian does
not strike me as a place for good humour, much less German admin-style humour”

Bug#1030284: [Pkg-javascript-devel] Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

[James Addison]

That'd be great, thank you - my local (emulated) aarch64 build of
nodejs is proving to be much more time consuming than I expected.

On Tue, 28 Feb 2023 at 23:21, Jérémy Lal  wrote:
>
>
>
> Le mar. 28 févr. 2023 à 19:06, James Addison  a écrit :
>>
>> On Tue, Feb 28, 2023, 17:55 Thorsten Glaser  wrote:
>>>
>>> Can you test it? I don’t have the bandwidth for that right now…
>>
>>
>> Should be able to, yep - I seem to remember seeing some repro instructions 
>> from you on the GitHub thread and will give those a try in an emulator/vm.
>
>
> I can build nodejs on amhdal.debian.org if you're not comfortable with that.
>
>> --
>> Pkg-javascript-devel mailing list
>> pkg-javascript-de...@alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Bug#1031414: clinfo breaks libgpuarray autopkgtest on i386: numerical deltas

[Andreas Beckmann]

On 24/02/2023 23.52, Adrian Bunk wrote:> $ clang-15 -march=i686 -O2 
test_fmod.c -lm -frounding-math  && ./a.out

> (-ffp-model=strict is a superset of -frounding-math)

Very nice finding, unfortunately pocl fails most of its tests (with a 
seemingly unrelated error) if I enable one of these options for kernel 
compilation.

https://github.com/pocl/pocl/issues/1183


Andreas

Bug#1031762: marked as done (Dies with "Object is not writable.")

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 18:22:10 -0500
with message-id 

and subject line Re: Dies with "Object is not writable."
has caused the Debian Bug report #1031762,
regarding Dies with "Object is not writable."
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-cryptography
Version: 2.6.1-3+deb10u3
Severity: grave

After updating python3-cryptography from 2.6.1-3+deb10u2 to
2.6.1-3+deb10u3, I get the following error from ansible:
Unexpected failure during module execution.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/ansible/executor/task_executor.py", 
line 106, in run
item_results = self._run_loop(items)
  File "/usr/lib/python3/dist-packages/ansible/executor/task_executor.py", 
line 343, in _run_loop
res = self._execute(variables=task_vars)
  File "/usr/lib/python3/dist-packages/ansible/executor/task_executor.py", 
line 612, in _execute
result = self._handler.run(task_vars=variables)
  File "/etc/ansible/plugins/mitogen/ansible_mitogen/mixins.py", line 121, 
in run
return super(ActionModuleMixin, self).run(tmp, task_vars)
  File 
"/usr/lib/python3/dist-packages/ansible/plugins/action/include_vars.py", line 
131, in run
self._load_files(self.source_file)
  File 
"/usr/lib/python3/dist-packages/ansible/plugins/action/include_vars.py", line 
236, in _load_files
b_data, show_content = self._loader._get_file_contents(filename)
  File "/usr/lib/python3/dist-packages/ansible/parsing/dataloader.py", line 
170, in _get_file_contents
return self._decrypt_if_vault_data(data, b_file_name)
  File "/usr/lib/python3/dist-packages/ansible/parsing/dataloader.py", line 
140, in _decrypt_if_vault_data
b_data = self._vault.decrypt(b_vault_data, filename=b_file_name)
  File "/usr/lib/python3/dist-packages/ansible/parsing/vault/__init__.py", 
line 661, in decrypt
plaintext, vault_id, vault_secret = 
self.decrypt_and_get_vault_id(vaulttext, filename=filename)
  File "/usr/lib/python3/dist-packages/ansible/parsing/vault/__init__.py", 
line 739, in decrypt_and_get_vault_id
b_plaintext = this_cipher.decrypt(b_vaulttext, vault_secret)
  File "/usr/lib/python3/dist-packages/ansible/parsing/vault/__init__.py", 
line 1361, in decrypt
b_plaintext = cls._decrypt_cryptography(b_ciphertext, b_crypted_hmac, 
b_key1, b_key2, b_iv)
  File "/usr/lib/python3/dist-packages/ansible/parsing/vault/__init__.py", 
line 1295, in _decrypt_cryptography
decryptor.update(b_ciphertext) + decryptor.finalize()
  File 
"/usr/lib/python3/dist-packages/cryptography/hazmat/primitives/ciphers/base.py",
 line 149, in update
return self._ctx.update(data)
  File 
"/usr/lib/python3/dist-packages/cryptography/hazmat/backends/openssl/ciphers.py",
 line 124, in update
n = self.update_into(data, buf)
  File 
"/usr/lib/python3/dist-packages/cryptography/hazmat/backends/openssl/ciphers.py",
 line 140, in update_into
self._backend._ffi.from_buffer(data, require_writable=True), len(data)
BufferError: Object is not writable.

This renders the package unusable.
-- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Wed, 22 Feb 2023 09:03:19 +0100 Klaus Ethgen  wrote:
> Package: python3-cryptography
> Version: 2.6.1-3+deb10u3
> Severity: grave
>
> After updating python3-cryptography from 2.6.1-3+deb10u2 to
> 2.6.1-3+deb10u3, I get the following error from ansible:

please read the rules of backports:
https://backports.debian.org/Instructions/#index6h2

this bug does not belong to the BTS

> Unexpected failure during module execution.
> Traceback (most recent call last):
>   File 
> "/usr/lib/python3/dist-packages/ansible/executor/task_executor.py", line 106, 
> in run
> item_results = self._run_loop(items)
>   File 
> "/usr/lib/python3/dist-packages/ansible/executor/task_executor.py", line 343, 
> in _run_loop
> res = self._execute(variables=task_vars)
>   File 
> "/usr/lib/python3/dist-packages/ansible/executor/task_executor.py", line 612, 
> in _execute
> result = self._handler.run(task_vars=variables)
>   File 

Bug#1030284: [Pkg-javascript-devel] Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

[Jérémy Lal]

Le mar. 28 févr. 2023 à 19:06, James Addison  a écrit :

> On Tue, Feb 28, 2023, 17:55 Thorsten Glaser  wrote:
>
>> Can you test it? I don’t have the bandwidth for that right now…
>
>
> Should be able to, yep - I seem to remember seeing some repro instructions
> from you on the GitHub thread and will give those a try in an emulator/vm.
>

I can build nodejs on amhdal.debian.org if you're not comfortable with that.

-- 
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
>

Bug#1032168: meson: autopkgtest fills disk completely

[Jussi Pakkanen]

On Tue, 28 Feb 2023 at 23:30, Paul Gevers  wrote:

> With your last upload of meson, we're seeing issues on
> ci.debian.net. It turns out that the autopkgtest of meson is using so
> much disk space that the most of our hosts runs out of it when meson
> is tested.

This is weird. As far as we know we have not made any changes that
should affect disk usage in 1.0.1.

Is /tmp on the same file system as the rest of the image or is it a
separate partition?

Is it possible to know how close to filling up the disk the old
succeeding builds got? And how much disk space is given to the build
in total?

Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic

[Dirk Eddelbuettel]

Hi Graham,

On 28 February 2023 at 19:36, Graham Inggs wrote:
| Hi Dirk
| 
| Thanks for the quick upload!
| Already got a successful build of tiledb-py on riscv64[1].
| 
| On Tue, 28 Feb 2023 at 17:14, Dirk Eddelbuettel  wrote:
| > TileDB upstream does everything in CMake (which I do not fully speak) so
| > "eventually" it would be nice to port this.
| 
| After testing the patch which I eventually submitted, I found a bug[2]
| that in message #5, discusses a way to automatically link libatomic
| when required by calling the linker with -pthread, instead of linking
| with -lpthread.
| 
| Then, in message #25, the way to do this in CMake is shown:
| 
| set(THREADS_PREFER_PTHREAD_FLAG ON)
| find_package(Threads REQUIRED)
|
| I tried applying this patch to TileDB, but it did not work for me.
| Perhaps upstream can make more sense of what is suggested in that bug
| report and in the linked cmake issue[3].

That's quite helpful. I will pass that on. 

Cheers, Dirk
 
| Regards
| Graham
| 
| 
| [1] https://buildd.debian.org/status/logs.php?pkg=tiledb-py=riscv64
| [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895969
| [3] https://cmake.org/Bug/view.php?id=14767

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1028743: marked as done (python-bottle: FTBFS: AssertionError: b'OK' != "URLError(ConnectionRefusedError(111, 'Connection refused'))")

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 22:19:30 +
with message-id 
and subject line Bug#1028743: fixed in python-bottle 0.12.23-1.1
has caused the Debian Bug report #1028743,
regarding python-bottle: FTBFS: AssertionError: b'OK' != 
"URLError(ConnectionRefusedError(111, 'Connection refused'))"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1028743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-bottle
Version: 0.12.23-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
>   pybuild --build -i python{version} -p "3.10 3.11"
> I: pybuild base:240: /usr/bin/python3.10 setup.py build 
> running build
> running build_py
> copying bottle.py -> /<>/.pybuild/cpython3_3.10_bottle/build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> copying bottle.py -> /<>/.pybuild/cpython3_3.11_bottle/build
> PYTHONPATH=. http_proxy='http://127.0.0.1:9/' sphinx-build -N -E -bhtml docs 
> build/html
> Running Sphinx v5.3.0
> making output directory... done
> loading intersphinx inventory from http://docs.python.org/objects.inv...
> loading intersphinx inventory from 
> http://werkzeug.pocoo.org/docs/objects.inv...
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://docs.python.org/objects.inv' not fetchable due 
> to : 
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url: 
> http://docs.python.org/objects.inv (Caused by ProxyError('Cannot connect to 
> proxy.', NewConnectionError(' 0x7f7ae8af2690>: Failed to establish a new connection: [Errno 111] Connection 
> refused')))
> WARNING: failed to reach any of the inventories with the following issues:
> intersphinx inventory 'http://werkzeug.pocoo.org/docs/objects.inv' not 
> fetchable due to : 
> HTTPConnectionPool(host='127.0.0.1', port=9): Max retries exceeded with url: 
> http://werkzeug.pocoo.org/docs/objects.inv (Caused by ProxyError('Cannot 
> connect to proxy.', NewConnectionError(' object at 0x7f7ae8b04710>: Failed to establish a new connection: [Errno 111] 
> Connection refused')))
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 19 source files that are out of date
> updating environment: [new config] 19 added, 0 changed, 0 removed
> reading sources... [  5%] api
> reading sources... [ 10%] async
> reading sources... [ 15%] changelog
> reading sources... [ 21%] cli
> reading sources... [ 26%] configuration
> reading sources... [ 31%] contact
> reading sources... [ 36%] deployment
> reading sources... [ 42%] development
> reading sources... [ 47%] faq
> reading sources... [ 52%] index
> reading sources... [ 57%] plugindev
> reading sources... [ 63%] plugins/index
> reading sources... [ 68%] plugins/sqlite
> reading sources... [ 73%] plugins/werkzeug
> reading sources... [ 78%] recipes
> reading sources... [ 84%] routing
> reading sources... [ 89%] stpl
> reading sources... [ 94%] tutorial
> reading sources... [100%] tutorial_app
> 
> /<>/bottle.py:docstring of bottle.request:1: WARNING: duplicate 
> object description of bottle.request, other instance in api, use :noindex: 
> for one of them
> /<>/bottle.py:docstring of bottle.ConfigDict:1: WARNING: Inline 
> emphasis start-string without end-string.
> /<>/docs/contact.rst:: WARNING: image file not readable: 
> _static/myface_small.png
> /<>/docs/faq.rst:1: WARNING: duplicate object description of 
> bottle, other instance in api, use :noindex: for one of them
> /<>/docs/plugindev.rst:1: WARNING: duplicate object description 
> of bottle, other instance in faq, use :noindex: for one of them
> /<>/docs/plugins/index.rst:1: WARNING: duplicate object 
> description of bottle, other instance in plugindev, use :noindex: for one of 
> them
> /<>/docs/recipes.rst:1: WARNING: duplicate object description of 
> bottle, other instance in plugins/index, use :noindex: for one of them
> /<>/docs/tutorial.rst:1: WARNING: duplicate object description 
> of bottle, other instance in recipes, use :noindex: for one of them
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... /<>/docs/cli.rst: WARNING: document 
> isn't included in any toctree
> /<>/docs/contact.rst: WARNING: document 

Processed: Re: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 shrinksafe
Bug #977027 [rhino] rhino breaks dojo autopkgtest: Cannot set property "dojo" 
of null to "[object Object]"
Bug reassigned from package 'rhino' to 'shrinksafe'.
No longer marked as found in versions rhino/1.7.7.2-1.
Ignoring request to alter fixed versions of bug #977027 to the same values 
previously set
> severity -1 serious
Bug #977027 [shrinksafe] rhino breaks dojo autopkgtest: Cannot set property 
"dojo" of null to "[object Object]"
Severity set to 'serious' from 'important'

-- 
977027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032168: meson: autopkgtest fills disk completely

[Paul Gevers]

Source: meson
Version: 1.0.1-1
Severity: serious

Dear Jussi,

With your last upload of meson, we're seeing issues on
ci.debian.net. It turns out that the autopkgtest of meson is using so
much disk space that the most of our hosts runs out of it when meson
is tested.

See e.g. the history (look for the tmpfails for 1.0.1-1) of armhf,
ppc64el and s390x:
https://ci.debian.net/packages/m/meson/testing/armhf/
https://ci.debian.net/packages/m/meson/testing/arm64/
https://ci.debian.net/packages/m/meson/testing/ppc64el/
https://ci.debian.net/packages/m/meson/testing/s390x/

Particularly s390x was bad, as we only have one host, so it took down
all capacity.

Paul

Processed: Re: Bug#1032165: gcc-12-cross-ports: not binNMU safe

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #1032165 [src:gcc-12-cross-ports] gcc-12-cross-ports: not binNMU safe
Bug 1032165 cloned as bug 1032167
> reassign -2 gcc-11-cross-mipsen 5+c3
Bug #1032167 [src:gcc-12-cross-ports] gcc-12-cross-ports: not binNMU safe
Bug reassigned from package 'src:gcc-12-cross-ports' to 'gcc-11-cross-mipsen'.
No longer marked as found in versions gcc-12-cross-ports/12.
Ignoring request to alter fixed versions of bug #1032167 to the same values 
previously set
Bug #1032167 [gcc-11-cross-mipsen] gcc-12-cross-ports: not binNMU safe
There is no source info for the package 'gcc-11-cross-mipsen' at version '5+c3' 
with architecture ''
Unable to make a source version for version '5+c3'
Marked as found in versions 5+c3.
> retitle -2 gcc-11-cross-mipsen: not binNMU-safe
Bug #1032167 [gcc-11-cross-mipsen] gcc-12-cross-ports: not binNMU safe
Changed Bug title to 'gcc-11-cross-mipsen: not binNMU-safe' from 
'gcc-12-cross-ports: not binNMU safe'.

-- 
1032165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032165
1032167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032165: gcc-12-cross-ports: not binNMU safe

[Sebastian Ramacher]

Control: clone -1 -2
Control: reassign -2 gcc-11-cross-mipsen 5+c3
Control: retitle -2 gcc-11-cross-mipsen: not binNMU-safe

On 2023-02-28 22:13:59 +0100, Sebastian Ramacher wrote:
> Source: gcc-12-cross-ports
> Version: 12
> Severity: serious
> 
> The method to compute the version of the binary packages is not
> binNMU-safe. This can be seen from the latest round of binNMUs to
> rebuild for outdated Built-Using fields. See
> https://buildd.debian.org/status/fetch.php?pkg=gcc-12-cross-ports=amd64=12%2Bb1=1677602107=0
> 
> As it can be seen from the log, the version computed for the binary
> packages is the same as the one of the build of the initial upload of
> version 12. The binNMU version -- b1 in this case -- is missing.

gcc-11-cross-mipsen is affected by the same issue. Cloning and
reassigning.

Cheers
-- 
Sebastian Ramacher

Bug#1032166: do not release in bookworm

[Ana Guerrero Lopez]

Source: debian-timeline
Version: 45
Severity: serious
X-Debbugs-Cc: debian-public...@lists.debian.org

Please, keep debian-timeline out of bookworm, the installed HTML doesn't
show the timeline like it should so the package is useless.

Bug#1032165: gcc-12-cross-ports: not binNMU safe

[Sebastian Ramacher]

Source: gcc-12-cross-ports
Version: 12
Severity: serious

The method to compute the version of the binary packages is not
binNMU-safe. This can be seen from the latest round of binNMUs to
rebuild for outdated Built-Using fields. See
https://buildd.debian.org/status/fetch.php?pkg=gcc-12-cross-ports=amd64=12%2Bb1=1677602107=0

As it can be seen from the log, the version computed for the binary
packages is the same as the one of the build of the initial upload of
version 12. The binNMU version -- b1 in this case -- is missing.

Cheers
-- 
Sebastian Ramacher

Bug#1032163: sudo: CVE-2023-27320

[Salvatore Bonaccorso]

Source: sudo
Version: 1.9.13p1-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for sudo, filling as RC
aiming to have it fixed before bookworm release.

CVE-2023-27320[0]:
| Sudo before 1.9.13p2 has a double free in the per-command chroot
| feature.


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-27320
https://www.cve.org/CVERecord?id=CVE-2023-27320
[1] https://www.openwall.com/lists/oss-security/2023/02/28/1

Regards,
Salvatore

Processed: notfixed 1010807 in 4.4.3-1.1, fixed 1010807 in 4.4.3-P1-1.1, notfound 985536 in 4.1-1 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfixed 1010807 4.4.3-1.1
Bug #1010807 {Done: Santiago Ruano Rincón } 
[src:isc-dhcp] isc-dhcp: ftbfs on riscv64 arch
The source 'isc-dhcp' and version '4.4.3-1.1' do not appear to match any binary 
packages
No longer marked as fixed in versions 4.4.3-1.1.
> fixed 1010807 4.4.3-P1-1.1
Bug #1010807 {Done: Santiago Ruano Rincón } 
[src:isc-dhcp] isc-dhcp: ftbfs on riscv64 arch
Marked as fixed in versions isc-dhcp/4.4.3-P1-1.1.
> notfound 985536 4.1-1
Bug #985536 {Done: Daniel Baumann } [mdadm] 
mdadm crashing when trying to grow an array with big disks
No longer marked as found in versions mdadm/4.1-1.
> notfound 1031671 43.3-3
Bug #1031671 [libmutter-11-0] gnome-shell: Some applications always lose focus
No longer marked as found in versions mutter/43.3-3.
> reassign 1031970 shotcut 22.12.21+ds-2~mx21+1
Bug #1031970 [version: <22.12.21+ds-2~mx21+1 amd64>] Shotcut 
Version(s), and Melt 7 for latest version.
Warning: Unknown package 'version:'
Warning: Unknown package '<22.12.21+ds-2~mx21+1'
Warning: Unknown package 'amd64>'
Bug reassigned from package 'version: <22.12.21+ds-2~mx21+1 amd64>' to 
'shotcut'.
Ignoring request to alter found versions of bug #1031970 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1031970 to the same values 
previously set
Bug #1031970 [shotcut] Shotcut Version(s), and Melt 7 for latest version.
There is no source info for the package 'shotcut' at version 
'22.12.21+ds-2~mx21+1' with architecture ''
Unable to make a source version for version '22.12.21+ds-2~mx21+1'
Marked as found in versions 22.12.21+ds-2~mx21+1.
> reassign 1030942 src:linux 6.1.8-1
Bug #1030942 [linux-image-6.1.0-3-amd64] PC Hangs on Boot
Warning: Unknown package 'linux-image-6.1.0-3-amd64'
Bug reassigned from package 'linux-image-6.1.0-3-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/6.1.8+1 and 
linux/6.1.8-1.
Ignoring request to alter fixed versions of bug #1030942 to the same values 
previously set
Bug #1030942 [src:linux] PC Hangs on Boot
Marked as found in versions linux/6.1.8-1.
> reassign 1030874 src:linux 6.1.8-1
Bug #1030874 {Done: Salvatore Bonaccorso } 
[linux-headers-6.1.0-3-amd64] linux-headers-6.1.0-3-amd64: Dependency problems 
prevent configuration of linux-headers-amd64
Warning: Unknown package 'linux-headers-6.1.0-3-amd64'
Bug reassigned from package 'linux-headers-6.1.0-3-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #1030874 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1030874 to the same values 
previously set
Bug #1030874 {Done: Salvatore Bonaccorso } [src:linux] 
linux-headers-6.1.0-3-amd64: Dependency problems prevent configuration of 
linux-headers-amd64
Marked as found in versions linux/6.1.8-1.
> tags 1032114 + sid bookworm
Bug #1032114 [src:golang-github-jesseduffield-termbox-go] Don't release with 
bookworm
Added tag(s) sid and bookworm.
> tags 1032109 + sid bookworm
Bug #1032109 [src:golang-github-jesseduffield-gocui] Don't release with bookworm
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1010807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010807
1030874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030874
1030942: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030942
1031671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031671
1031970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031970
1032109: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032109
1032114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032114
985536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 1031296 is forwarded to https://github.com/mozilla/sccache/issues/1631

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1031296 https://github.com/mozilla/sccache/issues/1631
Bug #1031296 [src:sccache] sccache FTBFS (on non-i386 32bit?)
Set Bug forwarded-to-address to 
'https://github.com/mozilla/sccache/issues/1631'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1031296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032125: marked as done (zeitgeist - import fails: AttributeError: module 'inspect' has no attribute 'getargspec')

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 18:52:00 +
with message-id 
and subject line Bug#1032125: fixed in zeitgeist 1.0.4-5
has caused the Debian Bug report #1032125,
regarding zeitgeist - import fails: AttributeError: module 'inspect' has no 
attribute 'getargspec'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1032125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zeitgeist
Version: 1.0.4-4
Severity: serious
Control: forwarded -1 
https://gitlab.freedesktop.org/zeitgeist/zeitgeist/-/issues/26

Dear Maintainer,

This import fails:

Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from zeitgeist import client
Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python3/dist-packages/zeitgeist/client.py", line 1100, in 

   _FIND_EVENTS_FOR_TEMPLATES_ARGS = inspect.getargspec(
 ^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
'getargs'?
>>>

After applying upstream commit:

Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from zeitgeist import client
>>>


Kind Regards
--- End Message ---
--- Begin Message ---
Source: zeitgeist
Source-Version: 1.0.4-5
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated zeitgeist package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Feb 2023 19:20:44 +0100
Source: zeitgeist
Architecture: source
Version: 1.0.4-5
Distribution: unstable
Urgency: medium
Maintainer: Debian semweb Team 
Changed-By: Jonas Smedegaard 
Closes: 1032125
Changes:
 zeitgeist (1.0.4-5) unstable; urgency=medium
 .
   * fix source helper tool copyright-check
 + work with Path::Tiny 0.144
 + avoid insecure shell expansion
   * add patch cherry-picked upstream to support Python 3.11;
 closes: bug#1032125, thanks to s3v
   * declare compliance with Debian Policy 4.6.2
   * update copyright info: update coverage
Checksums-Sha1:
 836197d1475fb1826b852527bd707869844a5047 2728 zeitgeist_1.0.4-5.dsc
 9714ef8326715e70f05ad5fcfe612f18ae3e18d0 20176 zeitgeist_1.0.4-5.debian.tar.xz
 db77940dd56659ab2e31eadfde2ccc937b9d 18973 
zeitgeist_1.0.4-5_amd64.buildinfo
Checksums-Sha256:
 6c3c7d4217a6a6a1eaf901705d53cd67f4d5634ba1b3f86025403c799cd4e8c7 2728 
zeitgeist_1.0.4-5.dsc
 9f966b5c0b2f90d6bfa0314679969dd84f2a9a0342a4d05bb57d050d929cc6bf 20176 
zeitgeist_1.0.4-5.debian.tar.xz
 88aefc2698ce1d520f6384edf20008c673191f41602d00555cb9eca6edc838b9 18973 
zeitgeist_1.0.4-5_amd64.buildinfo
Files:
 8f3a00b681435cb91ed451444f1efbe4 2728 utils optional zeitgeist_1.0.4-5.dsc
 130c3c76f590401c4088cc119d3a2032 20176 utils optional 
zeitgeist_1.0.4-5.debian.tar.xz
 d38f6eedc2fcfa62020f19c767dc80cf 18973 utils optional 
zeitgeist_1.0.4-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmP+R1sACgkQLHwxRsGg
ASFTUxAAj0fDMl2/1qahcyMjH4kXjnplvsI8Ip67N15KGtn22KeBUr9iAJig03/K
bzDhihB6NhKNpYh2PBIN2PDxrf/7OkyTcyo3EWfa7JqMP7XsIo04CbVstTxt52h5
6/8nuEIKf6Whyu1CuYxLED7F5XJcZR2SSBBEHdZ/JEYPlDCmlxfbiZPvOQ5B3vfC
3PXXcXI5fKM2wT3kBwnTO86kkATC/KYZw2yOa+5H3AdlrXjVJrjmRuZED0SVQD71
amqFtNyeaQwzK6LWz01ybqKKnBn/TivB3yF4gszqtxsfxsobu3ad/DJsBAeRqy8k
xQowNbJ2vCfYy294Hh3MwZry0YyIvG/ZZPjcafI/sbqRxJ7Y0c5UZfyioqyalR5O
x1ZlgbgKG+PnfdMOTfsmLFwVBgJgSg53s0+9KzKv+C9G9/w4VXfzwtSnHWI8oZUD
tFlGVJ2WN27ftFSGw2fJx//Jzw2PGpFzMC7/aSlr5S+ovyk86sHB0mwxx/fzH80k
coRGpNELW5vrML9XxxBa2FZB5XlrZb9hqiAUHQjh2t6HwNSsid/jbtjet6XxpHO1
h6xf8na4U95whKxz/K1wedAGC5njkSuAdZ/pzck9k+zh9QChUg5bspD/DMHsqmZU
oHqc3B5pcO+lYojm6flMgSgoiNSUDmJN2LAJA/w6UAolnwbj4y0=
=zjG1
-END PGP SIGNATURE End Message ---

Bug#1030697: marked as done (libjs-bootstrap5: not co-installable with libjs-bootstrap4)

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 18:49:01 +
with message-id 
and subject line Bug#1030697: fixed in bootstrap-html 5.2.3+dfsg-8
has caused the Debian Bug report #1030697,
regarding libjs-bootstrap5: not co-installable with libjs-bootstrap4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1030697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjs-bootstrap5
Version: 5.2.3+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

I'm not sure whether B+R are the right solution here or whether
the package should be co-installable.

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libjs-bootstrap5_5.2.3+dfsg-3_all.deb ...
  Unpacking libjs-bootstrap5 (5.2.3+dfsg-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libjs-bootstrap5_5.2.3+dfsg-3_all.deb (--unpack):
   trying to overwrite '/usr/share/nodejs/bootstrap/package.json', which is 
also in package libjs-bootstrap4 4.6.1+dfsg1-4
  Errors were encountered while processing:
   /var/cache/apt/archives/libjs-bootstrap5_5.2.3+dfsg-3_all.deb

These files are shipped by both packages:

usr/share/nodejs/bootstrap/package.json
usr/share/sass/bootstrap/_alert.scss
usr/share/sass/bootstrap/_badge.scss
usr/share/sass/bootstrap/_breadcrumb.scss
usr/share/sass/bootstrap/_button-group.scss
usr/share/sass/bootstrap/_buttons.scss
usr/share/sass/bootstrap/_card.scss
usr/share/sass/bootstrap/_carousel.scss
usr/share/sass/bootstrap/_close.scss
usr/share/sass/bootstrap/_dropdown.scss
usr/share/sass/bootstrap/_forms.scss
usr/share/sass/bootstrap/_functions.scss
usr/share/sass/bootstrap/_grid.scss
usr/share/sass/bootstrap/_images.scss
usr/share/sass/bootstrap/_list-group.scss
usr/share/sass/bootstrap/_mixins.scss
usr/share/sass/bootstrap/_modal.scss
usr/share/sass/bootstrap/_nav.scss
usr/share/sass/bootstrap/_navbar.scss
usr/share/sass/bootstrap/_pagination.scss
usr/share/sass/bootstrap/_popover.scss
usr/share/sass/bootstrap/_progress.scss
usr/share/sass/bootstrap/_reboot.scss
usr/share/sass/bootstrap/_root.scss
usr/share/sass/bootstrap/_spinners.scss
usr/share/sass/bootstrap/_tables.scss
usr/share/sass/bootstrap/_toasts.scss
usr/share/sass/bootstrap/_tooltip.scss
usr/share/sass/bootstrap/_transitions.scss
usr/share/sass/bootstrap/_type.scss
usr/share/sass/bootstrap/_utilities.scss
usr/share/sass/bootstrap/_variables.scss
usr/share/sass/bootstrap/bootstrap-grid.scss
usr/share/sass/bootstrap/bootstrap-reboot.scss
usr/share/sass/bootstrap/bootstrap.scss
usr/share/sass/bootstrap/mixins/_alert.scss
usr/share/sass/bootstrap/mixins/_border-radius.scss
usr/share/sass/bootstrap/mixins/_box-shadow.scss
usr/share/sass/bootstrap/mixins/_breakpoints.scss
usr/share/sass/bootstrap/mixins/_buttons.scss
usr/share/sass/bootstrap/mixins/_caret.scss
usr/share/sass/bootstrap/mixins/_clearfix.scss
usr/share/sass/bootstrap/mixins/_deprecate.scss
usr/share/sass/bootstrap/mixins/_forms.scss
usr/share/sass/bootstrap/mixins/_gradients.scss
usr/share/sass/bootstrap/mixins/_grid.scss
usr/share/sass/bootstrap/mixins/_image.scss
usr/share/sass/bootstrap/mixins/_list-group.scss
usr/share/sass/bootstrap/mixins/_lists.scss
usr/share/sass/bootstrap/mixins/_pagination.scss
usr/share/sass/bootstrap/mixins/_reset-text.scss
usr/share/sass/bootstrap/mixins/_resize.scss
usr/share/sass/bootstrap/mixins/_text-truncate.scss
usr/share/sass/bootstrap/mixins/_transition.scss
usr/share/sass/bootstrap/vendor/_rfs.scss


cheers,

Andreas


libjs-bootstrap4=4.6.1+dfsg1-4_libjs-bootstrap5=5.2.3+dfsg-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: bootstrap-html
Source-Version: 5.2.3+dfsg-8
Done: Daniel Baumann 

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

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

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

Debian distribution maintenance software
pp.
Daniel Baumann  (supplier of updated 
bootstrap-html 

Bug#1031297: marked as done (diffoscope: autopkgtest regression due to unavailable Recommends on several architectures)

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 18:19:13 +
with message-id 
and subject line Bug#1031297: fixed in diffoscope 237
has caused the Debian Bug report #1031297,
regarding diffoscope: autopkgtest regression due to unavailable Recommends on 
several architectures
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1031297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diffoscope
Version: 235
Severity: serious

Issues preventing migration:
∙ ∙ autopkgtest for diffoscope/235: amd64: Pass, arm64: Pass, armel: Regression 
♻ (reference ♻), armhf: Pass, i386: Pass, ppc64el: Regression ♻ (reference ♻), 
s390x: Regression ♻ (reference ♻)


pytest-with-recommends FAIL badpkg
blame: diffoscope
badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.




aapt   | 1:10.0.0+r36-10 | unstable| amd64, arm64, armel, 
armhf, i386, mips64el, mipsel
dexdump| 11.0.0+r48-5  | unstable | amd64, arm64, armhf, i386
--- End Message ---
--- Begin Message ---
Source: diffoscope
Source-Version: 237
Done: Mattia Rizzolo 

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated diffoscope package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 28 Feb 2023 18:16:09 +0100
Source: diffoscope
Architecture: source
Version: 237
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks 

Changed-By: Mattia Rizzolo 
Closes: 1031297
Changes:
 diffoscope (237) unstable; urgency=medium
 .
   * autopkgtest: only install appt and dexdump on architectures where they are
 available. (Closes: #1031297)
   * compartors/pdf:
 + Drop backward compatibility assignment.
 + Fix flake warnings, potentially reinstating PyPDF 1.x support (untested).
Checksums-Sha1:
 f6fefd651a5bac3518f98a41e2f4bed2ed0945d9 5151 diffoscope_237.dsc
 d99e2186a7b2cfc96793628d0a3ffcc8211a3adb 2462840 diffoscope_237.tar.xz
 d56de18076be4a6d612939d11951f85491a31a4b 31468 diffoscope_237_amd64.buildinfo
Checksums-Sha256:
 d9620b1e2d783594bbdf18c904b0e0968ee4d1de1634fa22779ab22d68ffd4c8 5151 
diffoscope_237.dsc
 0fcf91b77f36b8cbfb9347c627f74673d060bc99c5b568158a5cf975b09bbfb3 2462840 
diffoscope_237.tar.xz
 8e263e95efc316984e8783b2684bc5fa4ca9485516ce5547678a9ff7e1a4 31468 
diffoscope_237_amd64.buildinfo
Files:
 cab433c0266a1bcbb477385e0e574fb6 5151 devel optional diffoscope_237.dsc
 77e2de67857f2236100c2a8c63a46467 2462840 devel optional diffoscope_237.tar.xz
 9b931bd8267d7df685618fa5e4fc98e4 31468 devel optional 
diffoscope_237_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmP+O7AACgkQCBa54Yx2
K6207Q/8CdQ75MtSDDi9byEedZe1Cpi02Ks99fixhETJw+olDbYDlZJJLFChXsc7
EC0q/5t4cH8fJlTFvcx5lMaIlZupDq9O2znwir2rm+PwEuq+jYkacNot0Soa+FeE
4o1WpoLaauKA4cc9GkJleckGV+9m+ZdLCPdTPqY36AOz8G8evf/zAImkY4wevOas
0zuUd9/3VfQMFRDlLAxXAaMQ64i1aBbKNWY4YvMiOytGfHpq3CXrbRR45yPM0Ctc
eDlJgTKIiHwr/VoUy5H/Ozng8nveghhkPCKNQhV9TneDj5oBj966sZqOkiarFE85
hEK6b8CIh60taCfzT3lOK9LrVWQ7P4L1MZzB5yNI3BOm1gXl9Bhc4Dn3Ubd6I0VT
ar3TMcoN0x9SJPB58A6E/mhu8Fd5I4tctRj0WBKsws0yvyxx2oUVeRIgV5R/u9NW
+3PmjV9uikfmd2Zmp/gtG1zvXS89awCLoZJ9EeLDVhnqy4kF34c0XO2M95CceY/k
BxjI2ttds6B+VQIojdrEa/l4aK+eNj9rZyDGVQ2zph88AoLqwFcU4z4Vwb+eNdXs
SU3fLkvCmAtKYB3sT0vLh/qsQH3uExKsOX5qQM/QEfj3QRJQysMVvYO2yhlOpSvo
HvqrcmW7rSlZkMZdoQvmqYPSWkMLxFtArQyRw9A82zGKIcW9z/U=
=gfbh
-END PGP SIGNATURE End Message ---

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

[James Addison]

On Tue, Feb 28, 2023, 17:55 Thorsten Glaser  wrote:

> Can you test it? I don’t have the bandwidth for that right now…


Should be able to, yep - I seem to remember seeing some repro instructions
from you on the GitHub thread and will give those a try in an emulator/vm.

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

[Thorsten Glaser]

James Addison dixit:

>Hi - what do you both think of the attached patch, which brings the ARM stack
>size into line with almost all other architectures (= 984 KB)?

It might do the job unless arm64 for some reason uses more stack
elsewhere as well.

Can you test it? I don’t have the bandwidth for that right now…

Thanks,
//mirabilos
-- 
> Hi, does anyone sell openbsd stickers by themselves and not packaged
> with other products?
No, the only way I've seen them sold is for $40 with a free OpenBSD CD.
-- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc

Bug#1031297: marked as pending in diffoscope

[Mattia Rizzolo]

Control: tag -1 pending

Hello,

Bug #1031297 in diffoscope 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/reproducible-builds/diffoscope/-/commit/61f7c2b394c9134ee0f280a65a8e2efa97ee58c4


autopkgtest: only install appt and dexdump on architectures where they are 
available

Closes: #1031297
Signed-off-by: Mattia Rizzolo 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1031297

Processed: Bug#1031297 marked as pending in diffoscope

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1031297 [src:diffoscope] diffoscope: autopkgtest regression due to 
unavailable Recommends on several architectures
Added tag(s) pending.

-- 
1031297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic

[Graham Inggs]

Hi Dirk

Thanks for the quick upload!
Already got a successful build of tiledb-py on riscv64[1].

On Tue, 28 Feb 2023 at 17:14, Dirk Eddelbuettel  wrote:
> TileDB upstream does everything in CMake (which I do not fully speak) so
> "eventually" it would be nice to port this.

After testing the patch which I eventually submitted, I found a bug[2]
that in message #5, discusses a way to automatically link libatomic
when required by calling the linker with -pthread, instead of linking
with -lpthread.

Then, in message #25, the way to do this in CMake is shown:

set(THREADS_PREFER_PTHREAD_FLAG ON)
find_package(Threads REQUIRED)

I tried applying this patch to TileDB, but it did not work for me.
Perhaps upstream can make more sense of what is suggested in that bug
report and in the linked cmake issue[3].

Regards
Graham


[1] https://buildd.debian.org/status/logs.php?pkg=tiledb-py=riscv64
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895969
[3] https://cmake.org/Bug/view.php?id=14767

Bug#1030048: pgpool2: CVE-2023-22332

[Adrian Bunk]

On Mon, Jan 30, 2023 at 06:47:23PM +0100, Moritz Mühlenhoff wrote:
> Source: pgpool2
> X-Debbugs-CC: t...@security.debian.org
> Severity: grave
> Tags: security
> 
> Hi,
> 
> The following vulnerability was published for pgpool2.
> 
> CVE-2023-22332[0]:
> | Information disclosure vulnerability exists in Pgpool-II 4.4.0 to
> | 4.4.1 (4.4 series), 4.3.0 to 4.3.4 (4.3 series), 4.2.0 to 4.2.11 (4.2
> | series), 4.1.0 to 4.1.14 (4.1 series), 4.0.0 to 4.0.21 (4.0 series),
> | All versions of 3.7 series, All versions of 3.6 series, All versions
> | of 3.5 series, All versions of 3.4 series, and All versions of 3.3
> | series. A specific database user's authentication information may be
> | obtained by another database user. As a result, the information stored
> | in the database may be altered and/or database may be suspended by a
> | remote attacker who successfully logged in the product with the
> | obtained credentials.
> 
> Quoting from https://www.pgpool.net/mediawiki/index.php/Main_Page#News :
> 
> (I have no idea how common that is, feel free to downgrade as necessary)
> 
> --
> This release contains a security fix.
> 
> If following conditions are all met, the password of "wd_lifecheck_user" is 
> exposed by "SHOW POOL STATUS" command. The command can be executed by any 
> user who can
> connect to Pgpool-II. (CVE-2023-22332)
> 
> • Version 3.3 or later
> • use_watchdog = on
> • wd_lifecheck_method = 'query'
> • A plain text password is set to wd_lifecheck_password
> --
>...

Christoph, is there a reason why this cannot be fixed with a backport
or an upgrade to 4.3.5?

cu
Adrian

Bug#1028725: marked as done (flycheck: FTBFS: 4 tests failed)

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 16:34:13 +
with message-id 
and subject line Bug#1028725: fixed in flycheck 32~git.20200527.9c435db3-3
has caused the Debian Bug report #1028725,
regarding flycheck: FTBFS: 4 tests failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1028725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flycheck
Version: 32~git.20200527.9c435db3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230113 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b html -d _build/doctrees -j4 . -Dflycheck_offline_html=1 
> _build/html
> Running Sphinx v5.3.0
> making output directory... done
> WARNING: extlinks: Sphinx-6.0 will require a caption string to contain 
> exactly one '%s' and all other '%' need to be escaped as '%%'.
> WARNING: extlinks: Sphinx-6.0 will require a caption string to contain 
> exactly one '%s' and all other '%' need to be escaped as '%%'.
> Building offline documentation without external resources!
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 22 source files that are out of date
> updating environment: [new config] 22 added, 0 changed, 0 removed
> reading sources... [ 20%] changes .. community/people
> reading sources... [ 40%] contributor/contributing .. glossary
> reading sources... [ 60%] index .. user/error-list
> reading sources... [ 80%] user/error-reports .. user/syntax-checkers
> reading sources... [100%] user/syntax-checks .. user/troubleshooting
> 
> /<>/doc/contributor/style-guide.rst:69: ERROR: Unknown 
> interpreted text role "infonode".
> /<>/doc/contributor/style-guide.rst:85: ERROR: Unknown 
> interpreted text role "infonode".
> /<>/doc/contributor/style-guide.rst:128: ERROR: Unknown 
> interpreted text role "infonode".
> /<>/doc/developer/developing.rst:53: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/developer/developing.rst:55: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/glossary.rst:22: ERROR: Unknown interpreted text role 
> "infonode".
> /<>/doc/glossary.rst:24: ERROR: Unknown interpreted text role 
> "infonode".
> /<>/doc/user/error-reports.rst:273: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/user/syntax-checkers.rst:123: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/user/syntax-checkers.rst:125: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/user/syntax-checkers.rst:183: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/user/syntax-checkers.rst:185: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/user/syntax-checkers.rst:212: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/user/syntax-checkers.rst:5: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/user/syntax-checkers.rst:9: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/user/syntax-checks.rst:20: ERROR: Unknown interpreted 
> text role "infonode".
> /<>/doc/languages.rst:394: ERROR: Unknown interpreted text role 
> "infonode".
> /<>/doc/languages.rst:400: ERROR: Unknown interpreted text role 
> "infonode".
> /<>/doc/user/error-interaction.rst:17: ERROR: Unknown 
> interpreted text role "infonode".
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> /<>/doc/developer/developing.rst:120: WARNING: 'any' reference 
> target not found: flycheck-define-checker
> /<>/doc/developer/developing.rst:145: WARNING: 'any' reference 
> target not found: flycheck-substitute-argument
> /<>/doc/developer/developing.rst:180: WARNING: 'any' reference 
> target not found: flycheck-rx-to-string
> /<>/doc/developer/developing.rst:207: WARNING: 'any' reference 
> target not found: flycheck-define-generic-checker
> /<>/doc/developer/developing.rst:245: WARNING: 'any' reference 
> target not found: flycheck-substitute-argument
> /<>/doc/developer/developing.rst:272: WARNING: 'any' reference 
> target not found: flycheck-define-checker
> /<>/doc/developer/developing.rst:272: WARNING: 'any' reference 
> target not found: flycheck-define-command-checker
> /<>/doc/developer/developing.rst:290: WARNING: 'any' reference 
> target not found: flycheck-define-checker
> /<>/doc/developer/developing.rst:293: WARNING: 'any' reference 
> target not found: 

Bug#1000955: libkf5globalaccel-bin: /usr/bin/kglobalaccel5 eats up huge amount of CPU after suspend

[James Addison]

Package: libkf5globalaccel-bin
Followup-For: Bug #1000955
X-Debbugs-Cc: lopi...@debian.org

Hi Filippo,

On Wed, 1 Dec 2021 12:12:44 +0100, Filippo wrote:
> Should I install other packages to fix the problem? What can I do to help?

Two ideas related to this part of your report:

> Note that I also see a huge CPU consumption for the following processes:
>
> /usr/lib/xorg/Xorg (63%)
> /usr/sbin/rsyslogd (14%)
> /lib/systemd/systemd-journald (10%)
>
> Yeah, I know these percentages sum up to > 100 :-( 

The sum-of-percentages being above one-hundred is likely due to a multi-CPU (or
perhaps multiple-core) system - I think that each percentage reported is for a
single processor.  If the total goes above 100 * x, where x is the number of
processors, then we're allowed to become more confused.  Let's not do that yet.

> /lib/systemd/systemd-journald (10%)

Focusing more on this line in particular -- and the fact that kglobalaccel was
(and still is, in 5.103.0-1) configured to auto-restart on unhandled error[1],
then I think it's possible that the process is failing and being recreated
rapidly.  Each occurrence of that should be logged in the system journal,
and that could cause high CPU usage for that service.

All a theory so far, but if you are able to replicate the behaviour (I realize
it has been a while since your report) then I would suggest taking a look at
the service logs in journalctl to see if there are any clues there, and let us
know.

Thank you,
James

[1] - 
https://sources.debian.org/src/kglobalaccel/5.78.0-3/src/runtime/main.cpp/?hl=92#L79

Bug#1023666: gcc-10 should not be shipped in bookworm

[James Addison]

Package: gcc-10
Version: 10.4.0-7
Followup-For: Bug #1023666

Bug #1004184 implies that gcc-11 cannot build correct mips64 code for a key
Debian package (source: matplotlib) without buildflag adjustments.  However,
gcc-10 does emit correct code for the same package and architecture.

Should that be considered a blocker for this bug?

Bug#988021: marked as done (mongo-tools: CVE-2020-7924)

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 15:12:17 +
with message-id 
and subject line Bug#1032005: Removed package(s) from unstable
has caused the Debian Bug report #988021,
regarding mongo-tools: CVE-2020-7924
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
988021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mongo-tools
Version: 3.4.14-4
Severity: important
Tags: security upstream
Forwarded: https://jira.mongodb.org/browse/TOOLS-2587
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for mongo-tools.

CVE-2020-7924[0]:
| Usage of specific command line parameter in MongoDB Tools which was
| originally intended to just skip hostname checks, may result in
| MongoDB skipping all certificate validation. This may result in
| accepting invalid certificates.This issue affects: MongoDB Inc.
| MongoDB Database Tools 3.6 versions later than 3.6.5; 3.6 versions
| prior to 3.6.21; 4.0 versions prior to 4.0.21; 4.2 versions prior to
| 4.2.11; 100 versions prior to 100.2.0. MongoDB Inc. Mongomirror 0
| versions later than 0.6.0.


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-2020-7924
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7924
[1] https://jira.mongodb.org/browse/TOOLS-2587

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Version: 3.4.14-4+rm

Dear submitter,

as the package mongo-tools has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1032005

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#935286: marked as done (mongo-tools: FTBFS on amd64)

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 15:12:17 +
with message-id 
and subject line Bug#1032005: Removed package(s) from unstable
has caused the Debian Bug report #935286,
regarding mongo-tools: FTBFS on amd64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
935286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:mongo-tools
version: 3.4.14-4
severity: serious
tags: ftbfs

Hi,

A binnmu of mongo-tools in unstable fails on amd64:

https://buildd.debian.org/status/package.php?p=mongo-tools

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Version: 3.4.14-4+rm

Dear submitter,

as the package mongo-tools has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1032005

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic

[Dirk Eddelbuettel]

(Whoops typed this hours ago but apparently did not send from Emacs. --D.)

Hi Graham,

On 28 February 2023 at 10:49, Graham Inggs wrote:
| Source: tiledb
| Version: 2.14.1-1
| Severity: serious
| Tags: ftbfs patch
| Control: affects -1 src:tiledb-py
| 
| Hi Dirk
| 
| TileDB uses atomic operations but it is not linked to libatomic on the
| architectures that need it.  This can be seen in recent build logs for
| armel[1], mipsel[2], powerpc[3], riscv64[4] and sh4[5], where warnings
| like the following are emitted:
| 
| dpkg-shlibdeps: warning: symbol __atomic_fetch_add_8 used by
| debian/libtiledb2.13/usr/lib/arm-linux-gnueabi/libtiledb.so.2.14 found
| in none of the libraries
| 
| and
| 
| dpkg-shlibdeps: warning: symbol __atomic_compare_exchange_1 used by
| debian/libtiledb2.13/usr/lib/riscv64-linux-gnu/libtiledb.so.2.14 found
| in none of the libraries

Very attentive, thanks for spotting that!

| This causes at least tiledb-py to FTBFS on riscv64[6].  I have tested
| the patch below on riscv64 and was able to build tiledb-py
| successfully.  It should do the right thing on the other architectures
| as well.

I agree. Small and to the point patch.

TileDB upstream does everything in CMake (which I do not fully speak) so
"eventually" it would be nice to port this. 

Cheers, Dirk


| Regards
| Graham
| 
| 
| [1] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=armel=2.14.1-1=1676252451=0
| [2] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=mipsel=2.14.1-1=1676341362=0
| [3] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=powerpc=2.14.1-1=1676251162=0
| [4] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=riscv64=2.14.1-1=1676255427=0
| [5] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=sh4=2.14.1-1=1676262874=0
| [6] https://buildd.debian.org/status/logs.php?pkg=tiledb-py=riscv64
| 
| 
| --- a/debian/rules
| +++ b/debian/rules
| @@ -9,6 +9,11 @@
|  # Workaround until
| https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953855 is fixed
|  #export DEB_CXXFLAGS_MAINT_APPEND = -DSPDLOG_FMT_EXTERNAL -DFMT_HEADER_ONLY
| 
| +# Link with -latomic on architectures that need it
| +ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel powerpc riscv64 sh4))
| +  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic
| -Wl,--as-needed
| +endif
| +
|  #PKG_SHORT_DESC := $(shell grep 'Description:' debian/control | tail
| -n 1 | cut -d':' -f2 | sed 's/^\s//')
| 
|  #ifeq ($(filter nocheck,$(DEB_BUILD_PROFILES)),)

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#984287: marked as done (pepper: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 15:11:31 +
with message-id 
and subject line Bug#1031940: Removed package(s) from unstable
has caused the Debian Bug report #984287,
regarding pepper: ftbfs with GCC-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
984287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pepper
Version: 0.3.3-4
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/pepper_0.3.3-4_unstable_gcc11.log
The last lines of the build log are at the end of this report.

To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
  |   ^
make[3]: *** [Makefile:654: gnuplot.o] Error 1
make[3]: *** Waiting for unfinished jobs
plot.cpp: In member function ‘int Plot::set_output(lua_State*)’:
plot.cpp:117:54: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  117 | case 4: terminal = LuaHelpers::pops(L);
  |  ^
plot.cpp:118:17: note: here
  118 | case 3: height = LuaHelpers::popi(L);
  | ^~~~
plot.cpp:118:50: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  118 | case 3: height = LuaHelpers::popi(L);
  |  ^~~
plot.cpp:119:17: note: here
  119 | case 2: width = LuaHelpers::popi(L);
  | ^~~~
plot.cpp:119:49: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  119 | case 2: width = LuaHelpers::popi(L);
  | ^~~
plot.cpp:120:17: note: here
  120 | default: file = LuaHelpers::pops(L);
  | ^~~
plot.cpp: In member function ‘int Plot::plot_series(lua_State*)’:
plot.cpp:204:25: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  204 | if (lua_type(L, -1) == LUA_TTABLE) {
  | ^~
plot.cpp:210:17: note: here
  210 | case 3: luaL_checktype(L, index--, LUA_TTABLE);
  | ^~~~
plot.cpp:210:39: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  210 | case 3: luaL_checktype(L, index--, LUA_TTABLE);
  | ~~^~~~
plot.cpp:211:17: note: here
  211 | default:
  | ^~~
plot.cpp: In member function ‘int Plot::plot_multi_series(lua_State*)’:
plot.cpp:325:25: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  325 | if (lua_type(L, -1) == LUA_TTABLE) {
  | ^~
plot.cpp:331:17: note: here
  331 | case 3: luaL_checktype(L, index--, LUA_TTABLE);
  | ^~~~
plot.cpp:331:39: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  331 | case 3: luaL_checktype(L, index--, LUA_TTABLE);
  | ~~^~~~
plot.cpp:332:17: note: here
  332 | default:
  | 

Bug#1030447: marked as done (libgeo-distance-xs-perl: FTBFS: Failed test 'PP version loads XS')

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 15:11:03 +
with message-id 
and subject line Bug#1031934: Removed package(s) from unstable
has caused the Debian Bug report #1030447,
regarding libgeo-distance-xs-perl: FTBFS: Failed test 'PP version loads XS'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1030447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgeo-distance-xs-perl
Version: 0.13-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> true
> true
> true
> rm -rf blib/arch/auto/Geo/Distance/XS/XS.bs
> "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- XS.bs 
> blib/arch/auto/Geo/Distance/XS/XS.bs 644
> true
> true
> true
> true
> true
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/00_load.t  
> 1..1
> ok 1 - use Geo::Distance::XS;
> ok
> t/01_new.t . 
> ok 1 - 'new' isa 'Geo::Distance'
> ok 2 - Geo::Distance->can(...)
> ok 3 - @FORMULAS exists
> 1..3
> ok
> 
> #   Failed test 'PP version loads XS'
> #   at t/02_new_pp.t line 11.
> #  got: ''
> # expected: '1'
> # Looks like you failed 1 test of 1.
> t/02_new_pp.t .. 
> not ok 1 - PP version loads XS
> 1..1
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/1 subtests 
> t/03_methods.t . 
> ok 1 - alt: distance from LA to NY
> ok 2 - alt with antipodal coordinates is not NaN
> ok 3 - cos: distance from LA to NY
> ok 4 - cos with antipodal coordinates is not NaN
> ok 5 - gcd: distance from LA to NY
> ok 6 - gcd with antipodal coordinates is not NaN
> ok 7 - hsin: distance from LA to NY
> ok 8 - hsin with antipodal coordinates is not NaN
> ok 9 - mt: distance from LA to NY
> ok 10 - mt with antipodal coordinates is not NaN
> ok 11 - polar: distance from LA to NY
> ok 12 - polar with antipodal coordinates is not NaN
> ok 13 - tv: distance from LA to NY
> ok 14 - tv with antipodal coordinates is not NaN
> 1..14
> ok
> t/04_disable_xs.t .. 
> ok 1 - GEO_DISTANCE_PP
> 1..1
> ok
> 
> Test Summary Report
> ---
> t/02_new_pp.t(Wstat: 256 (exited 1) Tests: 1 Failed: 1)
>   Failed test:  1
>   Non-zero exit status: 1
> Files=5, Tests=20,  0 wallclock secs ( 0.04 usr  0.01 sys +  0.42 cusr  0.06 
> csys =  0.53 CPU)
> Result: FAIL
> Failed 1/5 test programs. 1/20 subtests failed.
> make[1]: *** [Makefile:1020: test_dynamic] Error 255


The full build log is available from:
http://qa-logs.debian.net/2023/02/03/libgeo-distance-xs-perl_0.13-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230203;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230203=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 0.13-3+rm

Dear submitter,

as the package libgeo-distance-xs-perl has just been removed from the Debian 
archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1031934

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed (with 1 error): Re: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 1031622 -1
Bug #1031622 [src:e2fsprogs] mke2fs: should not enable orphan_file by default 
until trixie
Unable to merge bugs because:
package of #1031923 is 'd-i.debian.org' not 'src:e2fsprogs'
Failed to forcibly merge 1031622: Did not alter merged bugs.


-- 
1031622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031622
1031923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031923
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1031923: d-i.debian.org: testing (bookworm): Unable to boot due to unsupported FEATURE_C12 in e2fsck

[James Addison]

Package: d-i.debian.org
Followup-For: Bug #1031923
Control: forcemerge 1031622 -1

Bug#1030495: marked as done (navarp: FTBFS: AttributeError: module 'numpy' has no attribute 'complex')

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 20:13:56 +0530
with message-id <20230228144356.xmfddlyisbngs...@nileshpatra.info>
and subject line Re: Bug#1030495: navarp: FTBFS: AttributeError: module 'numpy' 
has no attribute 'complex'
has caused the Debian Bug report #1030495,
regarding navarp: FTBFS: AttributeError: module 'numpy' has no attribute 
'complex'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1030495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: navarp
Version: 1.3.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230203 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> running build
> running build_py
> file navarp.py (for module navarp) not found
> creating /<>/.pybuild/cpython3_3.11_navarp/build/navarp
> copying navarp/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp
> copying navarp/navarp_gui.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp
> creating /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/kinterp.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/navplt.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/navfile.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/isomclass.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/fermilevel.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/isocut.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> copying navarp/utils/ktransf.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/utils
> creating /<>/.pybuild/cpython3_3.11_navarp/build/navarp/extras
> copying navarp/extras/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/extras
> copying navarp/extras/simulation.py -> 
> /<>/.pybuild/cpython3_3.11_navarp/build/navarp/extras
> running egg_info
> creating navarp.egg-info
> writing navarp.egg-info/PKG-INFO
> writing dependency_links to navarp.egg-info/dependency_links.txt
> writing entry points to navarp.egg-info/entry_points.txt
> writing requirements to navarp.egg-info/requires.txt
> writing top-level names to navarp.egg-info/top_level.txt
> writing manifest file 'navarp.egg-info/SOURCES.txt'
> file navarp.py (for module navarp) not found
> reading manifest file 'navarp.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> adding license file 'LICENSE'
> adding license file 'AUTHORS.rst'
> writing manifest file 'navarp.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: 
> SetuptoolsDeprecationWarning: Installing 'navarp.gui' as data is 
> deprecated, please list it in `packages`.
> !!
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'navarp.gui' as an importable package,
> but it is not listed in the `packages` configuration of setuptools.
> 
> 'navarp.gui' has been automatically added to the distribution only
> because it may contain data files, but this behavior is likely to change
> in future versions of setuptools (and therefore is considered deprecated).
> 
> Please make sure that 'navarp.gui' is included as a package by using
> the `packages` configuration field or the proper discovery methods
> (for example by using `find_namespace_packages(...)`/`find_namespace:`
> instead of `find_packages(...)`/`find:`).
> 
> You can read more about "package discovery" and "data files" on setuptools
> documentation page.
> 
> 
> !!
> 
>   check.warn(importable)
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:202: 
> SetuptoolsDeprecationWarning: Installing 'navarp.gui.icons' as data is 
> deprecated, please list it in `packages`.
> !!
> 
> 
> 
> # Package would be ignored #
> 
> Python recognizes 'navarp.gui.icons' as an importable package,
> but it is not listed in the `packages` configuration of setuptools.
> 
> 'navarp.gui.icons' has been automatically added to the distribution only
> 

Bug#1029626: marked as done (pagure fails to purge when adduser is not installed)

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 13:19:55 +
with message-id 
and subject line Bug#1029626: fixed in pagure 5.11.3+dfsg-2.1
has caused the Debian Bug report #1029626,
regarding pagure fails to purge when adduser is not installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1029626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pagure
Version: 5.11.3+dfsg-1
Severity: serious

https://piuparts.debian.org/sid/fail/pagure_5.11.3+dfsg-2.log

...
  Purging configuration files for pagure (5.11.3+dfsg-2) ...
  /var/lib/dpkg/info/pagure.postrm: 22: deluser: not found
  dpkg: error processing package pagure (--purge):
   installed pagure package post-removal script subprocess returned error exit 
status 127
  Errors were encountered while processing:
   pagure
0m58.6s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpemwrio1i', 'dpkg', '--purge', 'pagure']
  (Reading database ... 8052 files and directories currently installed.)
  Purging configuration files for pagure (5.11.3+dfsg-2) ...
  /var/lib/dpkg/info/pagure.postrm: 22: deluser: not found
  dpkg: error processing package pagure (--purge):
   installed pagure package post-removal script subprocess returned error exit 
status 127
  Errors were encountered while processing:
   pagure



https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#summary-of-ways-maintainer-scripts-are-called

The postrm script is called after the package’s files have been removed or 
replaced. The package whose postrm is being called may have previously been 
deconfigured and only be “Unpacked”, at which point subsequent package changes 
do not consider its dependencies. Therefore, all postrm actions must only rely 
on essential packages and must gracefully skip any actions that require the 
package’s dependencies if those dependencies are unavailable.
--- End Message ---
--- Begin Message ---
Source: pagure
Source-Version: 5.11.3+dfsg-2.1
Done: Adrian Bunk 

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated pagure package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Feb 2023 14:26:40 +0200
Source: pagure
Architecture: source
Version: 5.11.3+dfsg-2.1
Distribution: unstable
Urgency: medium
Maintainer: Sergio Durigan Junior 
Changed-By: Adrian Bunk 
Closes: 1029626
Changes:
 pagure (5.11.3+dfsg-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/pagure.postrm: Don't fail if adduser is not installed.
 (Closes: #1029626)
Checksums-Sha1:
 523f695983ff08af5dc99e05dc75cc0b61d1769a 3576 pagure_5.11.3+dfsg-2.1.dsc
 b3dea9471955116515387fed15cb5d670d838928 24144 
pagure_5.11.3+dfsg-2.1.debian.tar.xz
Checksums-Sha256:
 37254841f593628d79346256617998500e029effea6f6d608af07dac5a7ab1d3 3576 
pagure_5.11.3+dfsg-2.1.dsc
 be2d3ae346a9cd614096c48f7e8e52fccc44f17b0d92fe43a55d0825922c24cd 24144 
pagure_5.11.3+dfsg-2.1.debian.tar.xz
Files:
 0aa6ffc63c90c8026966f00bc88d9905 3576 net optional pagure_5.11.3+dfsg-2.1.dsc
 9b197da1c593a40faa659d41867dd915 24144 net optional 
pagure_5.11.3+dfsg-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmP0vPwACgkQiNJCh6LY
mLHpiw//SpxrYcsScnjbdYZqeS+D260vFyVgbtdLNlJtfK8BtZGq8TptE+i8KY7c
FGrPAEY+E/+PFsqljp1nejmkaTsGNkwjJFubF5Dnc0Er4pRud96g4DIb6ULCBAAe
O/rH3hQwrRiTlfFi6nPGbUieeXWV1PD6Tb7Khs3oCVruHYx4pcVLZ4c5at9wXog/
SsWMULe5pFcZdLbXr/o0I1g5VEy8rmZXReloamjk3YKjFTsmx7wU/4b+GA0g/Hlw
bqobe0z3vprJ6D4jL0TSubw47Q2UYZ26WaHAzYYbuH6X3Vaq2xwTUMZpCP5THUy9
TYdb9ZpKTLlIziDMchYJmnPZL0/n1s5fb+QJSz7CzDszuLzf/b7PCLUmc/1aX1Ve
4kXYxDOoAtRFUMgcfnDhLmZ80Unj/LGHFjzIjhePA+8XuEnZmrJj9rp4E4k44abI
F+nxnSk/yyGeanzDSppS2u6tioZ/vfzg3gWN06CMfNSmIqZmQiuHZq2iNKWqSh51
shHAbSzvyL7vBReeZPx890rwFEoqh5KLjNGpoumGzHYGNUghMgqHzw0RbyAMus1D
oJ/HvUskaQ3zuL9zTI4rBVC+JKWWNQjkEYiGu66Yd0jzU+ez6km2O6BSpzbr9DWR

Bug#1016958: epics-base: FTBFS without network access

[Santiago Vila]

El 28/2/23 a las 12:53, Andrius Merkys escribió:

On a related note, is trying network access to localhost RC?


It's ok if you try to connect to a service started by the build process
itself (please downgrade again if my severity change was wrong).

This is the exact wording in policy:


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


It is not ok if you try to use a service which was already running
in the host machine. Here is a funny example of that:

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

I guess that according to the spirit of the norm, it's also not
ok to do DNS queries, as that's "communication with the outside world".

Thanks.

Bug#1032120: marked as done (tiledb: uses atomic operations, but is not linked to libatomic)

[Debian Bug Tracking System]

Your message dated Tue, 28 Feb 2023 12:37:34 +
with message-id 
and subject line Bug#1032120: fixed in tiledb 2.14.1-2
has caused the Debian Bug report #1032120,
regarding tiledb: uses atomic operations, but is not linked to libatomic
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1032120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiledb
Version: 2.14.1-1
Severity: serious
Tags: ftbfs patch
Control: affects -1 src:tiledb-py

Hi Dirk

TileDB uses atomic operations but it is not linked to libatomic on the
architectures that need it.  This can be seen in recent build logs for
armel[1], mipsel[2], powerpc[3], riscv64[4] and sh4[5], where warnings
like the following are emitted:

dpkg-shlibdeps: warning: symbol __atomic_fetch_add_8 used by
debian/libtiledb2.13/usr/lib/arm-linux-gnueabi/libtiledb.so.2.14 found
in none of the libraries

and

dpkg-shlibdeps: warning: symbol __atomic_compare_exchange_1 used by
debian/libtiledb2.13/usr/lib/riscv64-linux-gnu/libtiledb.so.2.14 found
in none of the libraries

This causes at least tiledb-py to FTBFS on riscv64[6].  I have tested
the patch below on riscv64 and was able to build tiledb-py
successfully.  It should do the right thing on the other architectures
as well.

Regards
Graham


[1] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=armel=2.14.1-1=1676252451=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=mipsel=2.14.1-1=1676341362=0
[3] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=powerpc=2.14.1-1=1676251162=0
[4] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=riscv64=2.14.1-1=1676255427=0
[5] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=sh4=2.14.1-1=1676262874=0
[6] https://buildd.debian.org/status/logs.php?pkg=tiledb-py=riscv64


--- a/debian/rules
+++ b/debian/rules
@@ -9,6 +9,11 @@
 # Workaround until
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953855 is fixed
 #export DEB_CXXFLAGS_MAINT_APPEND = -DSPDLOG_FMT_EXTERNAL -DFMT_HEADER_ONLY

+# Link with -latomic on architectures that need it
+ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel powerpc riscv64 sh4))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic
-Wl,--as-needed
+endif
+
 #PKG_SHORT_DESC := $(shell grep 'Description:' debian/control | tail
-n 1 | cut -d':' -f2 | sed 's/^\s//')

 #ifeq ($(filter nocheck,$(DEB_BUILD_PROFILES)),)
--- End Message ---
--- Begin Message ---
Source: tiledb
Source-Version: 2.14.1-2
Done: Dirk Eddelbuettel 

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

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

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated tiledb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 28 Feb 2023 06:13:55 -0600
Source: tiledb
Architecture: source
Version: 2.14.1-2
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Closes: 1032120
Changes:
 tiledb (2.14.1-2) unstable; urgency=medium
 .
   * debian/rules: Apply patch kindly provided by Graham Inggs to link with
 -latomic where needed (Closes: #1032120)
Checksums-Sha1:
 27ddc56ec66537c9f81bbe44c02685d4c924cacb 2027 tiledb_2.14.1-2.dsc
 0e7756025a891b102a7da8928be92d35eb1c8ce0 8764 tiledb_2.14.1-2.debian.tar.xz
 15c7c0ec07a0493ef661e258c02fc585acaea3cb 7765 tiledb_2.14.1-2_amd64.buildinfo
Checksums-Sha256:
 026100fda875b35a7169e9bdba296e26c798b677c28fb8aae58e1e87a085969b 2027 
tiledb_2.14.1-2.dsc
 1f21e045d3641895236128fca5b202857869ede7a967ed1d694563161b47c4a6 8764 
tiledb_2.14.1-2.debian.tar.xz
 b5b1978261bb78d3cf9bf6006b5157de9befc597cf3420139557702fb74921b6 7765 
tiledb_2.14.1-2_amd64.buildinfo
Files:
 a49dfe168c3a82cc6b2b05538954cc1b 2027 libs optional tiledb_2.14.1-2.dsc
 91d9c3b2e92a963ac74fd6083c7e6be5 8764 libs optional 
tiledb_2.14.1-2.debian.tar.xz
 d1211da8deb8dd6bcdf8f44881b1e794 7765 libs optional 
tiledb_2.14.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1016958: epics-base: FTBFS without network access

[Andrius Merkys]

Hello,

On 2023-02-28 12:57, Santiago Vila wrote:

Hello. Merely trying network access is already considered RC,
so this should really be serious.

(I would be willing to test a fix if somebody proposes one).


This particular test seems to attempt to communicate to a locally 
running server daemon. It assumes a certain executable is installed in 
$PATH, thus will always fail in build time tests. I think it is OK to 
skip the test entirely and maybe make it an autopkgtest.


On a related note, is trying network access to localhost RC?

Best,
Andrius

Bug#1032125: zeitgeist - import fails: AttributeError: module 'inspect' has no attribute 'getargspec'

[s3v]

Dear Maintainer,

As side note, this error is catched by tests:

#:> apt install python3-dbus
#:> ln -s python zeitgeist
#:> make test-dbus
...
./test/dbus/run-all-tests.py
Traceback (most recent call last):
  File "/build/zeitgeist-1.0.4/./test/dbus/run-all-tests.py", line 42, in 

    from testutils import RemoteTestCase
  File "/build/zeitgeist-1.0.4/test/dbus/testutils.py", line 42, in 
    from zeitgeist.client import ZeitgeistDBusInterface, ZeitgeistClient, \
  File "/build/zeitgeist-1.0.4/./test/dbus/../../zeitgeist/client.py", line 
1100, in 
    _FIND_EVENTS_FOR_TEMPLATES_ARGS = inspect.getargspec(
  ^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
'getargs'?
make: *** [Makefile:984: test-dbus] Error 1

Soft link is "documented" in ./test/dbus/run-all-tests.py

 if not os.path.isdir("zeitgeist"):
 print("*** If you get unexpected failures, " \
 "you may want to run: `ln -s python zeitgeist`", 
file=sys.stderr)

Kind Regards

Bug#1028725: flycheck: FTBFS: make: *** [debian/rules:4: binary] Error 25

[David Bremner]

Sergio Durigan Junior  writes:

> On Monday, February 27 2023, David Bremner wrote:
>
>> Sergio Durigan Junior  writes:
>>>
>>> I was testing with an upstream build.  For Debian's Emacs, we should
>>> use:
>>>
>>>   buttercup --eval "(setq comp-enable-subr-trampolines nil)" -L .
>>>
>>
>> Did you get that working with the upstream version currently in master
>> or with a new upstream snapshot? I tried cherry picking 8379be91 but it
>> seemed not to be enough (there was a bunch of conflicts, so maybe I
>> missed something).
>
> I backported 8379be91, and it needed manual adjustments to apply
> cleanly.  After that, it was enough to solve the other two failures.
>
> Here's the full diff.  If you're OK with it I can upload the package.
>

Go ahead.

d

Processed: reassign to src package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # FTBFS bugs are really bugs in the source package
> tags 1016958 + ftbfs
Bug #1016958 [epics-base] epics-base: FTBFS without network access
Added tag(s) ftbfs.
> reassign 1016958 src:epics-base
Bug #1016958 [epics-base] epics-base: FTBFS without network access
Bug reassigned from package 'epics-base' to 'src:epics-base'.
No longer marked as found in versions 7.0.3.1-3.
Ignoring request to alter fixed versions of bug #1016958 to the same values 
previously set
> found 1016958 7.0.3.1-3
Bug #1016958 [src:epics-base] epics-base: FTBFS without network access
Marked as found in versions epics-base/7.0.3.1-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1016958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: epics-base: FTBFS without network access

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1016958 serious
Bug #1016958 [epics-base] epics-base: FTBFS without network access
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1016958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032125: zeitgeist - import fails: AttributeError: module 'inspect' has no attribute 'getargspec'

[s3v]

Package: zeitgeist
Version: 1.0.4-4
Severity: serious
Control: forwarded -1 
https://gitlab.freedesktop.org/zeitgeist/zeitgeist/-/issues/26

Dear Maintainer,

This import fails:

Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from zeitgeist import client
Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python3/dist-packages/zeitgeist/client.py", line 1100, in 

   _FIND_EVENTS_FOR_TEMPLATES_ARGS = inspect.getargspec(
 ^^
AttributeError: module 'inspect' has no attribute 'getargspec'. Did you mean: 
'getargs'?
>>>

After applying upstream commit:

Python 3.11.2 (main, Feb 12 2023, 00:48:52) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from zeitgeist import client
>>>


Kind Regards

Processed: zeitgeist - import fails: AttributeError: module 'inspect' has no attribute 'getargspec'

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.freedesktop.org/zeitgeist/zeitgeist/-/issues/26
Bug #1032125 [zeitgeist] zeitgeist - import fails: AttributeError: module 
'inspect' has no attribute 'getargspec'
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/zeitgeist/zeitgeist/-/issues/26'.

-- 
1032125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: vect: Don't allow vect_emulated_vector_p type in vectorizable_call [PR106322]

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1016903 [g++-12] tree-vectorize: Wrong code at O2 level 
(-fno-tree-vectorize is working)
Severity set to 'grave' from 'normal'

-- 
1016903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032124: pd-ableton-link: FTBFS on armel: fatal error: gnu/stubs-hard.h: No such file or directory

[Sebastian Ramacher]

Source: pd-ableton-link
Version: 0.6~ds0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=pd-ableton-link=armel=0.6%7Eds0-5%2Bb3=1677541943=0

make[1]: Entering directory '/<>/external'
 info: using Makefile.pdlibbuilder version 0.6.0
 info: using Pd API /usr/include/pd/m_pd.h
 info: making target all in lib abl_link~
 info: making abl_link~.o in lib abl_link~
g++ -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fcheck-new -std=c++11 -I./link/include 
-I./link/modules/asio-standalone/asio/include -Wno-multichar 
-DLINK_PLATFORM_LINUX=1 -Wall -Wextra -Wshadow -Winline -Wstrict-aliasing 
-Wno-unused-function -Wno-unused-parameter -Wno-unused-value 
-Wno-unused-variable -O3 -ffast-math -funroll-loops -fomit-frame-pointer 
-march=armv7-a -mfpu=vfpv3 -mfloat-abi=hard -o abl_link~.o -c abl_link~.cpp
 info: making abl_link_instance.o in lib abl_link~
g++ -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fcheck-new -std=c++11 -I./link/include 
-I./link/modules/asio-standalone/asio/include -Wno-multichar 
-DLINK_PLATFORM_LINUX=1 -Wall -Wextra -Wshadow -Winline -Wstrict-aliasing 
-Wno-unused-function -Wno-unused-parameter -Wno-unused-value 
-Wno-unused-variable -O3 -ffast-math -funroll-loops -fomit-frame-pointer 
-march=armv7-a -mfpu=vfpv3 -mfloat-abi=hard -o abl_link_instance.o -c 
abl_link_instance.cpp
In file included from /usr/include/features.h:513,
 from 
/usr/include/arm-linux-gnueabi/c++/12/bits/os_defines.h:39,
 from 
/usr/include/arm-linux-gnueabi/c++/12/bits/c++config.h:655,
 from /usr/include/c++/12/cmath:41,
 from /usr/include/c++/12/math.h:36,
 from abl_link~.cpp:9:
/usr/include/arm-linux-gnueabi/gnu/stubs.h:10:11: fatal error: 
gnu/stubs-hard.h: No such file or directory
   10 | # include 
  |   ^~
compilation terminated.
In file included from /usr/include/features.h:513,
 from 
/usr/include/arm-linux-gnueabi/c++/12/bits/os_defines.h:39,
 from 
/usr/include/arm-linux-gnueabi/c++/12/bits/c++config.h:655,
 from /usr/include/c++/12/bits/stl_algobase.h:59,
 from /usr/include/c++/12/memory:63,
 from abl_link_instance.hpp:10,
 from abl_link_instance.cpp:7:
/usr/include/arm-linux-gnueabi/gnu/stubs.h:10:11: fatal error: 
gnu/stubs-hard.h: No such file or directory
   10 | # include 
  |   ^~
compilation terminated.
make[1]: *** [Makefile.pdlibbuilder:959: abl_link~.o] Error 1

Cheers
-- 
Sebastian Ramacher

Processed: tiledb: uses atomic operations, but is not linked to libatomic

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:tiledb-py
Bug #1032120 [src:tiledb] tiledb: uses atomic operations, but is not linked to 
libatomic
Added indication that 1032120 affects src:tiledb-py

-- 
1032120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic

[Graham Inggs]

Source: tiledb
Version: 2.14.1-1
Severity: serious
Tags: ftbfs patch
Control: affects -1 src:tiledb-py

Hi Dirk

TileDB uses atomic operations but it is not linked to libatomic on the
architectures that need it.  This can be seen in recent build logs for
armel[1], mipsel[2], powerpc[3], riscv64[4] and sh4[5], where warnings
like the following are emitted:

dpkg-shlibdeps: warning: symbol __atomic_fetch_add_8 used by
debian/libtiledb2.13/usr/lib/arm-linux-gnueabi/libtiledb.so.2.14 found
in none of the libraries

and

dpkg-shlibdeps: warning: symbol __atomic_compare_exchange_1 used by
debian/libtiledb2.13/usr/lib/riscv64-linux-gnu/libtiledb.so.2.14 found
in none of the libraries

This causes at least tiledb-py to FTBFS on riscv64[6].  I have tested
the patch below on riscv64 and was able to build tiledb-py
successfully.  It should do the right thing on the other architectures
as well.

Regards
Graham


[1] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=armel=2.14.1-1=1676252451=0
[2] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=mipsel=2.14.1-1=1676341362=0
[3] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=powerpc=2.14.1-1=1676251162=0
[4] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=riscv64=2.14.1-1=1676255427=0
[5] 
https://buildd.debian.org/status/fetch.php?pkg=tiledb=sh4=2.14.1-1=1676262874=0
[6] https://buildd.debian.org/status/logs.php?pkg=tiledb-py=riscv64


--- a/debian/rules
+++ b/debian/rules
@@ -9,6 +9,11 @@
 # Workaround until
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953855 is fixed
 #export DEB_CXXFLAGS_MAINT_APPEND = -DSPDLOG_FMT_EXTERNAL -DFMT_HEADER_ONLY

+# Link with -latomic on architectures that need it
+ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel powerpc riscv64 sh4))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic
-Wl,--as-needed
+endif
+
 #PKG_SHORT_DESC := $(shell grep 'Description:' debian/control | tail
-n 1 | cut -d':' -f2 | sed 's/^\s//')

 #ifeq ($(filter nocheck,$(DEB_BUILD_PROFILES)),)

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 1021165
Bug #1021165 {Done: Matthias Klose } [src:glibc] armhf: 
floatn-common.h:214:9: error: multiple types in one declaration
Bug reopened
Ignoring request to alter fixed versions of bug #1021165 to the same values 
previously set
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1021165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 1021165 src:highway
Bug #1021165 {Done: Matthias Klose } [src:glibc] armhf: 
floatn-common.h:214:9: error: multiple types in one declaration
Added indication that 1021165 affects src:highway
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1021165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems