Bug#1041674: test case to force error

2023-07-21 Thread Rudi Heitbaum
I have been able to reliable reproduce the build race, using make -j > 1.
the following will trigger the build failure.

the proposed patch in message 10 is incomplete.

testbreakcompile.patch
--- a/Makefile.in   2023-07-12 13:55:26.0 +
+++ b/Makefile.in   2023-07-22 05:00:09.718180145 +
@@ -1163,7 +1163,7 @@
 @MACOSX_TRUE@wrapped.h wrapdef.h wrapstruct.h wraptmpf.h:wrapawk_macosx 
wrapfunc.inp
 @MACOSX_TRUE@  awk -f $(srcdir)/wrapawk_macosx < $(srcdir)/wrapfunc.inp
 @MACOSX_FALSE@wrapped.h wrapdef.h wrapstruct.h wraptmpf.h:wrapawk wrapfunc.inp
-@MACOSX_FALSE@ awk -f $(srcdir)/wrapawk < $(srcdir)/wrapfunc.inp
+@MACOSX_FALSE@ sleep 100;awk -f $(srcdir)/wrapawk < $(srcdir)/wrapfunc.inp
 
 libfakeroot.lo:libfakeroot.c wrapdef.h wrapstruct.h wraptmpf.h
 
--- a/Makefile.am   2023-07-22 04:59:30.671246641 +
+++ b/Makefile.am   2023-07-22 05:01:52.345546358 +
@@ -52,7 +52,7 @@
awk -f $(srcdir)/wrapawk_macosx < $(srcdir)/wrapfunc.inp
 else !MACOSX
 wrapped.h wrapdef.h wrapstruct.h wraptmpf.h:wrapawk wrapfunc.inp
-   awk -f $(srcdir)/wrapawk < $(srcdir)/wrapfunc.inp
+   sleep 100; awk -f $(srcdir)/wrapawk < $(srcdir)/wrapfunc.inp
 endif !MACOSX
 
 libfakeroot.lo:libfakeroot.c wrapdef.h wrapstruct.h wraptmpf.h



Bug#1041683: undeclared file conflict between fabio-viewer and python3-fabio

2023-07-21 Thread Helmut Grohne
Package: python3-fabio,fabio-viewer
Severity: serious

Since very recently, there is an undeclared file conflict between
fabio-viewer and python3-fabio about programs such as
/usr/bin/fabio-convert. It is not clear to me how this is to be
resolved. Is this an attempt to restructure the package?

Helmut



Bug#1041123: marked as done (libkiwix FTBFS with googletest 1.13.0)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Sat, 22 Jul 2023 04:04:54 +
with message-id 
and subject line Bug#1041123: fixed in libkiwix 12.0.0-2
has caused the Debian Bug report #1041123,
regarding libkiwix FTBFS with googletest 1.13.0
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.)


-- 
1041123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkiwix
Version: 11.0.0-2
Severity: serious
Tags: ftbfs trixie sid experimental
Forwarded: https://github.com/kiwix/libkiwix/issues/877

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libkiwix.html

...
In file included from /usr/include/gtest/gtest-message.h:57,
 from /usr/include/gtest/gtest-assertion-result.h:46,
 from /usr/include/gtest/gtest.h:64,
 from ../test/kiwixserve.cpp:1:
/usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less 
than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...
--- End Message ---
--- Begin Message ---
Source: libkiwix
Source-Version: 12.0.0-2
Done: Kunal Mehta 

We believe that the bug you reported is fixed in the latest version of
libkiwix, 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 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kunal Mehta  (supplier of updated libkiwix 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: Fri, 21 Jul 2023 23:09:27 -0400
Source: libkiwix
Architecture: source
Version: 12.0.0-2
Distribution: experimental
Urgency: medium
Maintainer: Kunal Mehta 
Changed-By: Kunal Mehta 
Closes: 1031681 1041123
Changes:
 libkiwix (12.0.0-2) experimental; urgency=medium
 .
   * Depend on libzim >= 8.1.1 (Closes: #1031681)
   * Add patch to build with c++14 (Closes: #1041123)
Checksums-Sha1:
 0bc6de609a5fa1aa739841183b02eb5f97d10032 2100 libkiwix_12.0.0-2.dsc
 d1c1f6b0c668eb3514cdb33b9adc663245333685 16776 libkiwix_12.0.0-2.debian.tar.xz
 9d6cc0ab0a1c4ec75495dea55db23b757a400bdf 8534 libkiwix_12.0.0-2_amd64.buildinfo
Checksums-Sha256:
 dbdf3e468697d2599d21a723cf58de40a7db2971579fdc36656d713a76199339 2100 
libkiwix_12.0.0-2.dsc
 309019e101b0edd46e4f3eeaeb82ff5a1034a99039cbc5e4f10b80122f5f192c 16776 
libkiwix_12.0.0-2.debian.tar.xz
 deb42b50195be89bbd9b1c1068ced9518027f6a028298d7dcd4e64c9535906b7 8534 
libkiwix_12.0.0-2_amd64.buildinfo
Files:
 dc043ecb6f0217d384456f089262330e 2100 libs optional libkiwix_12.0.0-2.dsc
 bb3b271504c3bc3b892c06550eabc15f 16776 libs optional 
libkiwix_12.0.0-2.debian.tar.xz
 8c111e6b1cc0919ce46a47625a934203 8534 libs optional 
libkiwix_12.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE2MtZ8F27ngU4xIGd8QX4EBsFJpsFAmS7UAITHGxlZ29rdG1A
cmlzZXVwLm5ldAAKCRDxBfgQGwUmm1FhD/0VGQ1rGJpA9iFyeO9Xe+jYHmhgrGNP
nWN0SDdgkWYrJjMYgYGSwmTRHB+rADzAPPIqXYyE978QrbTwVRFYEWqRVTEZPoJK
apsBfzAz1MfxoDqJyJ0Hi/QZ65D5MbNpk3nf0EAlqDD1jFX2V0TBIR9hon88ttsY
YcWDiYbce536W9GirHd8XA95sv2mQ3kpHXxTzEouGUfs8Gw58HO+a2ucBrHKXs7m
e36BoQ3UkCICaLzBw5QAv99dKhf6lADPAZdBprghdSWjZFSwm/edh2TC83mgGBus
uZ+W0uK6/lsPq7HCsusZT4sOYZMyGztRcUJ6wGTD39yABAIn2GUO6mscwjaftXm4
OC1/E4MJLGmguPdTeI0Nu/IOGOj3O5YS02E1RF+AmY7Ta9cHqbgPg/W7rL+qh4S5
NJ7sJzBTGIwJjKzerwguJbHJ5/4+/jwoRko4Tm+BcF79qZxbc+Yj3ewYEKPByILu
VHiRFB+ZNNkqKISGFzGTZoxZPZMwF3HtPcrbrxDdVpA4uttZsAgDHXuP3qW/d2mw
uAHtYcJ7iuFoMOquInlFN33nJW1zJBkET4FZ8FrDy3jWtq0RBs0YQ0mKb1AbLqq0
QxzBSNKRr0UCO/rb0J8nyUee8pKeu5U1BslPY2cUmJ6s9C9iF4IkH7Omzu5FxefI
v3wS+N/3l0Hwag==
=98CB
-END PGP SIGNATURE End Message ---


Bug#1031681: marked as done (libkiwix: bump B-D to libzim-dev (>= 8.1.0+really8.1.0))

2023-07-21 Thread Debian Bug Tracking System
Your message dated Sat, 22 Jul 2023 04:04:54 +
with message-id 
and subject line Bug#1031681: fixed in libkiwix 12.0.0-2
has caused the Debian Bug report #1031681,
regarding libkiwix: bump B-D to libzim-dev (>= 8.1.0+really8.1.0)
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.)


-- 
1031681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkiwix
Version: 12.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

libkiwix/experimental started to FTBFS after sid reverted to libzim-dev
8.1.0+really8.0.0-1. Please bump the version in the build-dependency to
match the version in experimental instead.


Andreas
--- End Message ---
--- Begin Message ---
Source: libkiwix
Source-Version: 12.0.0-2
Done: Kunal Mehta 

We believe that the bug you reported is fixed in the latest version of
libkiwix, 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.
Kunal Mehta  (supplier of updated libkiwix 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: Fri, 21 Jul 2023 23:09:27 -0400
Source: libkiwix
Architecture: source
Version: 12.0.0-2
Distribution: experimental
Urgency: medium
Maintainer: Kunal Mehta 
Changed-By: Kunal Mehta 
Closes: 1031681 1041123
Changes:
 libkiwix (12.0.0-2) experimental; urgency=medium
 .
   * Depend on libzim >= 8.1.1 (Closes: #1031681)
   * Add patch to build with c++14 (Closes: #1041123)
Checksums-Sha1:
 0bc6de609a5fa1aa739841183b02eb5f97d10032 2100 libkiwix_12.0.0-2.dsc
 d1c1f6b0c668eb3514cdb33b9adc663245333685 16776 libkiwix_12.0.0-2.debian.tar.xz
 9d6cc0ab0a1c4ec75495dea55db23b757a400bdf 8534 libkiwix_12.0.0-2_amd64.buildinfo
Checksums-Sha256:
 dbdf3e468697d2599d21a723cf58de40a7db2971579fdc36656d713a76199339 2100 
libkiwix_12.0.0-2.dsc
 309019e101b0edd46e4f3eeaeb82ff5a1034a99039cbc5e4f10b80122f5f192c 16776 
libkiwix_12.0.0-2.debian.tar.xz
 deb42b50195be89bbd9b1c1068ced9518027f6a028298d7dcd4e64c9535906b7 8534 
libkiwix_12.0.0-2_amd64.buildinfo
Files:
 dc043ecb6f0217d384456f089262330e 2100 libs optional libkiwix_12.0.0-2.dsc
 bb3b271504c3bc3b892c06550eabc15f 16776 libs optional 
libkiwix_12.0.0-2.debian.tar.xz
 8c111e6b1cc0919ce46a47625a934203 8534 libs optional 
libkiwix_12.0.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE2MtZ8F27ngU4xIGd8QX4EBsFJpsFAmS7UAITHGxlZ29rdG1A
cmlzZXVwLm5ldAAKCRDxBfgQGwUmm1FhD/0VGQ1rGJpA9iFyeO9Xe+jYHmhgrGNP
nWN0SDdgkWYrJjMYgYGSwmTRHB+rADzAPPIqXYyE978QrbTwVRFYEWqRVTEZPoJK
apsBfzAz1MfxoDqJyJ0Hi/QZ65D5MbNpk3nf0EAlqDD1jFX2V0TBIR9hon88ttsY
YcWDiYbce536W9GirHd8XA95sv2mQ3kpHXxTzEouGUfs8Gw58HO+a2ucBrHKXs7m
e36BoQ3UkCICaLzBw5QAv99dKhf6lADPAZdBprghdSWjZFSwm/edh2TC83mgGBus
uZ+W0uK6/lsPq7HCsusZT4sOYZMyGztRcUJ6wGTD39yABAIn2GUO6mscwjaftXm4
OC1/E4MJLGmguPdTeI0Nu/IOGOj3O5YS02E1RF+AmY7Ta9cHqbgPg/W7rL+qh4S5
NJ7sJzBTGIwJjKzerwguJbHJ5/4+/jwoRko4Tm+BcF79qZxbc+Yj3ewYEKPByILu
VHiRFB+ZNNkqKISGFzGTZoxZPZMwF3HtPcrbrxDdVpA4uttZsAgDHXuP3qW/d2mw
uAHtYcJ7iuFoMOquInlFN33nJW1zJBkET4FZ8FrDy3jWtq0RBs0YQ0mKb1AbLqq0
QxzBSNKRr0UCO/rb0J8nyUee8pKeu5U1BslPY2cUmJ6s9C9iF4IkH7Omzu5FxefI
v3wS+N/3l0Hwag==
=98CB
-END PGP SIGNATURE End Message ---


Bug#1041084: marked as done (zim-tools FTBFS with googletest 1.13.0)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Sat, 22 Jul 2023 03:05:22 +
with message-id 
and subject line Bug#1041084: fixed in zim-tools 3.2.0-1
has caused the Debian Bug report #1041084,
regarding zim-tools FTBFS with googletest 1.13.0
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.)


-- 
1041084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zim-tools
Version: 3.1.3-1
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zim-tools.html

...
/tools-test.cpp.o.d -o test/tools-test.p/tools-test.cpp.o -c 
../test/tools-test.cpp
In file included from /usr/include/gtest/gtest-message.h:57,
 from /usr/include/gtest/gtest-assertion-result.h:46,
 from /usr/include/gtest/gtest.h:64,
 from ../test/tools-test.cpp:1:
/usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less 
than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...



This can be fixed by changing cpp_std=c++11 to cpp_std=c++14
in meson.build
--- End Message ---
--- Begin Message ---
Source: zim-tools
Source-Version: 3.2.0-1
Done: Kunal Mehta 

We believe that the bug you reported is fixed in the latest version of
zim-tools, 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 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kunal Mehta  (supplier of updated zim-tools 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: Fri, 21 Jul 2023 22:25:41 -0400
Source: zim-tools
Architecture: source
Version: 3.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Kunal Mehta 
Changed-By: Kunal Mehta 
Closes: 1038284 1041084
Changes:
 zim-tools (3.2.0-1) unstable; urgency=medium
 .
   * New upstream version 3.2.0
   * Add patch to build with c++14 (Closes: #1041084)
   * Drop transitional zimwriterfs package (Closes: #1038284)
Checksums-Sha1:
 2fd5be424f37708bb9819e275d7fd206c9bafb90 2044 zim-tools_3.2.0-1.dsc
 1b0e02ecbcf8c1bbb2555981dae595c3ac13ade8 226568 zim-tools_3.2.0.orig.tar.xz
 0036e680dc548653c8c3fcc80aaf71f8f2726827 12476 zim-tools_3.2.0-1.debian.tar.xz
 f361f93733a5b96e1352db39cf5667b40b562761 8066 zim-tools_3.2.0-1_amd64.buildinfo
Checksums-Sha256:
 99bfc89ee5cd4b17204a5da439e9c72fc9c7df6810d838f98b4bada05aa8f718 2044 
zim-tools_3.2.0-1.dsc
 956d610b8e18c83ae9463dda142f25a07577126079febe348b374184d3942f6c 226568 
zim-tools_3.2.0.orig.tar.xz
 d1e0fb3f66e40dcb7eba7216e87618d2d4d799f1a69ec8393090f81ba3a82d72 12476 
zim-tools_3.2.0-1.debian.tar.xz
 8688ff32a427b33d901282adfc0bd4194da721feedac95804ec9c9c87c7b9848 8066 
zim-tools_3.2.0-1_amd64.buildinfo
Files:
 80253edbe1bbddccd91114cd2929a274 2044 utils optional zim-tools_3.2.0-1.dsc
 d6fa5f2bd7b45a7eb922ef06463e4525 226568 utils optional 
zim-tools_3.2.0.orig.tar.xz
 2d3290d117fe79dfc2172371dbd74719 12476 utils optional 
zim-tools_3.2.0-1.debian.tar.xz
 42fd27ba9fe1a44b109ef59968a31d57 8066 utils optional 
zim-tools_3.2.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE2MtZ8F27ngU4xIGd8QX4EBsFJpsFAmS7QVATHGxlZ29rdG1A
cmlzZXVwLm5ldAAKCRDxBfgQGwUmm0WsD/9FKiQqtAPBY1X7mRcQMmo6CjYDoDi4
2oRPdHRwXhrKf28UYLh6fFsRXCK+nwZj7JwZoQGVur/qLdvHUJty9dvaFEvvbubY
ZEvf2h5TLQ23YXN4sQCdMzwZ1J1Yi+70Hd/HLAvwTgQCXa6+KYHfdr566PpMsgJE
n/jeMHTnpoHxN0uWpf/1xQ+eL/t4PYdj7uWB/4hmX2qNdyYUyclczd6DwXGQgFLB
SAet0t895OJvPMHkga7F7+Kw3PkdaX8XM9Qc7gta9/WFikx6xsC/yNHN7/MhgdQf
P7jeF/UFPuFkC4TyjTnB91i4u231ntVnyER4gqWObsNYZFtbyPlvP1ae7WDJYojd
e76K9G4dJpYm+uC+TI3wMhXTfrOI34jsdaTCBkJ9tC8JG9rTovC3xiN67rK/1A83
eE/UimJ7inr4XyOEm4hGeW8KYUV5ZI92OIDV/Kgpd00lzI3WNuc79xO4DzFVGSkv
8oCrjoPatP16xe0i+s3e9jmeXsrzJHAD2e7coCCS/g40qjYFw93NmPqVcabOZwdm
t7pFUnkMvmURaOdQUsvNl6KeWvOLeajqE8SUdxeTkfnfxKiIHzvpH2v0HFNYCRDY
cMOTlUraaWwFw2uXyJUxcYdNJhSyoCeLcYRdjIcyMgoVbw1XPWuQHP4GdQqinxHf
qNrzp8eFqRPaNA==
=n/jB
-END PGP SIGNATURE End Message ---


Bug#1037851: (no subject)

2023-07-21 Thread Matthew Fernandez
Btw, why does this bug not appear when searching for bugs against the 
package? https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=rumur




Bug#1041588: bug#64773: grep 3.11 -r on 100000+ files fails with "Operation not supported"

2023-07-21 Thread Jim Meyering
On Fri, Jul 21, 2023 at 4:38 PM Paul Eggert  wrote:
> To fix just this bug (as opposed to the other Gnulib-related bugs that
> may be lurking) try applying the attached Gnulib patch to a grep 3.11
> tarball.
>
> Closing the debbugs.gnu.org bug report, as the bug has been fixed upstream.

Thanks for reporting that.
I've just pushed the following, adding a NEWS entry for the 3.11 bug and a test.
https://git.savannah.gnu.org/cgit/grep.git/commit/?id=v3.11-12-gd1c3fbe



Bug#1041674: proposed patch for missing wrapped.h

2023-07-21 Thread Rudi Heitbaum
Please find a proposed patch for the missing wrapped.h during build.
--- a/Makefile.am	2023-07-21 22:53:36.152522891 +
+++ b/Makefile.am	2023-07-22 00:12:21.796916350 +
@@ -7,7 +7,7 @@
 
 libmacosx_la_SOURCES = libfakeroot_inode64.c libfakeroot_unix2003.c patchattr.h
 
-libfakeroot_time64_la_SOURCES = libfakeroot_time64.c
+libfakeroot_time64_la_SOURCES = libfakeroot_time64.c wrapped.h
 libfakeroot_time64_la_CPPFLAGS = -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
 
 lib_LTLIBRARIES=libfakeroot.la
--- a/Makefile.in	2023-07-21 22:06:23.543495829 +
+++ b/Makefile.in	2023-07-21 22:51:43.995255208 +
@@ -436,7 +436,7 @@
 noinst_LTLIBRARIES = libcommunicate.la libmacosx.la libfakeroot_time64.la
 libcommunicate_la_SOURCES = communicate.c
 libmacosx_la_SOURCES = libfakeroot_inode64.c libfakeroot_unix2003.c patchattr.h
-libfakeroot_time64_la_SOURCES = libfakeroot_time64.c
+libfakeroot_time64_la_SOURCES = libfakeroot_time64.c wrapped.h
 libfakeroot_time64_la_CPPFLAGS = -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
 lib_LTLIBRARIES = libfakeroot.la
 libfakeroot_la_SOURCES = libfakeroot.c statconv/glibc/linux/alpha/stats.h wrapdef.h  wrapstruct.h communicate.h


Bug#1041317: dgit: table too wide in man page, trashes autopkgtests

2023-07-21 Thread G. Branden Robinson
Hi Ian,

I don't want to reopen this bug--I appreciate your swift
resolution!--but I did want to correct myself on a point.

At 2023-07-17T14:32:40+0100, Ian Jackson wrote:
[I wrote]:
> > Man pages are formatted for a width of 78n if the terminal width is
> > 80 columns.  This origin of this practice is not well documented but
> > experience with groff upstream leads me to believe that it is a
> > workaround for bugs in GNU tbl(1).  (In AT Unix Version 7, they
> > were formatted for a line length of 65n, with a page offset of one
> > tenth of an inch.  On Western Electric Teletype Model 37 printing
> > terminals.)

I managed to confuse myself by reading Version 7 Unix man(7)'s code for
drawing cut marks.

The page offset for the default nroff device (the aforementioned Model
37) was zero.

Demonstration
=

$ pdp11

PDP-11 simulator V3.8-1
sim> set cpu 11/45
Disabling XQ
sim> set tto 7b
sim> att rl unix_v7_rl.dsk
sim> boot rl
@boot
New Boot, known devices are hp ht rk rl rp tm vt
: rl(0,0)rl2unix
mem = 177856
# Restricted rights: Use, duplication, or disclosure
is subject to restrictions stated in your contract with
Western Electric Company, Inc.
Thu Sep 22 21:03:18 EDT 1988

login: dmr
$ cat measure.man
.pl 30v
.TH measure 1 2023-07-21 "ad hoc man page"
.SH Name
measure \- determine some nroff formatting parameters
.SH Description.
.nr w \w'M'
The width of a character cell (1 en) is \nw basic units.
.br
.nr o \n(.o/\nw
The page offset is \n(.o (\non).
.br
.nr l \n(.l/\nw
The line length is \n(.l (\nln).
.br
.nr i \n(.i/\nw
The indentation is \n(.i (\nin).
.PP
Bye!
$ nroff -man measure.man



measure(1)  UNIX Programmer's Manual   measure(1)



Name
 measure - determine some nroff formatting parameters

Description.
 The width of a character cell (1 en) is 24 basic units.
 The page offset is 0 (0n).
 The line length is 1560 (65n).
 The indentation is 120 (5n).

 Bye!









Printed 9/22/882023-07-21   1



$ exit

Regards,
Branden


signature.asc
Description: PGP signature


Bug#1037707: keyman: ftbfs with GCC-13

2023-07-21 Thread Boyuan Yang
Hi Eberhard,

Are you going to work on this issue?

Thanks,
Boyuan Yang


On Wed, 14 Jun 2023 09:26:08 + Matthias Klose  wrote:
> Package: src:keyman
> Version: 16.0.139-4
> Severity: normal
> Tags: sid trixie
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-13
> 
> [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
> severity of this report will be raised before the trixie release.
> 
> The full build log can be found at:
>
http://qa-logs.debian.net/2023/05/22/logs/keyman_16.0.139-4_unstable_gccexp.log
> The last lines of the build log are at the end of this report.
> 
> To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html
> 
> [...]
> ../../../src/kmx/kmx_processevent.h:58:27: error: ‘PKMX_BYTE’ has not been
declared
>    58 |   KMX_BOOL VerifyKeyboard(PKMX_BYTE filebase, size_t sz);
>   |   ^
> ../../../src/kmx/kmx_processevent.h:59:27: error: ‘PKMX_BYTE’ has not been
declared
>    59 |   KMX_BOOL VerifyChecksum(PKMX_BYTE buf,  size_t sz);
>   |   ^
> ../../../src/kmx/kmx_processevent.h:60:27: error: ‘PKMX_BYTE’ has not been
declared
>    60 |   PKMX_WCHAR StringOffset(PKMX_BYTE base, KMX_DWORD offset);
>   |   ^
> ../../../src/kmx/kmx_processevent.h:60:43: error: ‘KMX_DWORD’ has not been
declared
>    60 |   PKMX_WCHAR StringOffset(PKMX_BYTE base, KMX_DWORD offset);
>   |   ^
> ../../../src/kmx/kmx_processevent.h:62:27: error: ‘PKMX_BYTE’ has not been
declared
>    62 |   LPKEYBOARD CopyKeyboard(PKMX_BYTE bufp, PKMX_BYTE base);
>   |   ^
> ../../../src/kmx/kmx_processevent.h:62:43: error: ‘PKMX_BYTE’ has not been
declared
>    62 |   LPKEYBOARD CopyKeyboard(PKMX_BYTE bufp, PKMX_BYTE base);
>   |   ^
> ../../../src/kmx/kmx_processevent.h:85:45: error: ‘KMX_DWORD’ has not been
declared
>    85 |   PKMX_WCHAR  GetSystemStore(LPKEYBOARD kb, KMX_DWORD SystemID);
>   | ^
> ../../../src/kmx/kmx_processevent.h:89:25: error: ‘KMX_DWORD’ has not been
declared
>    89 |   KMX_BOOL IsCapsLockOn(KMX_DWORD modifiers);
>   | ^
> ../../../src/kmx/kmx_processevent.h:90:20: error: ‘KMX_DWORD’ has not been
declared
>    90 |   void SetCapsLock(KMX_DWORD , KMX_BOOL capsLockOn,
KMX_BOOL force = FALSE);



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


Bug#1041588: bug#64773: grep 3.11 -r on 100000+ files fails with "Operation not supported"

2023-07-21 Thread Paul Eggert
To fix just this bug (as opposed to the other Gnulib-related bugs that 
may be lurking) try applying the attached Gnulib patch to a grep 3.11 
tarball.


Closing the debbugs.gnu.org bug report, as the bug has been fixed upstream.From d4d8abb39eb02c555f062b1f83ffcfac999c582f Mon Sep 17 00:00:00 2001
From: Bruno Haible 
Date: Fri, 5 May 2023 12:02:49 +0200
Subject: [PATCH] dirfd: Fix bogus override (regression 2023-04-26).

Reported by Bjarni Ingi Gislason  in
.

* m4/dirfd.m4 (gl_FUNC_DIRFD): Fix mistake in last change.
---
 ChangeLog   | 7 +++
 m4/dirfd.m4 | 6 +-
 2 files changed, 8 insertions(+), 5 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index aaffe12fc1..5f01a52535 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2023-05-05  Bruno Haible  
+
+	dirfd: Fix bogus override (regression 2023-04-26).
+	Reported by Bjarni Ingi Gislason  in
+	.
+	* m4/dirfd.m4 (gl_FUNC_DIRFD): Fix mistake in last change.
+
 2023-05-04  Bruno Haible  
 
 	c32swidth: Add tests.
diff --git a/m4/dirfd.m4 b/m4/dirfd.m4
index d1ee2c7f61..7968b1287c 100644
--- a/m4/dirfd.m4
+++ b/m4/dirfd.m4
@@ -1,4 +1,4 @@
-# serial 27   -*- Autoconf -*-
+# serial 28   -*- Autoconf -*-
 
 dnl Find out how to get the file descriptor associated with an open DIR*.
 
@@ -40,10 +40,6 @@ AC_DEFUN([gl_FUNC_DIRFD],
 HAVE_DIRFD=0
   else
 HAVE_DIRFD=1
-dnl Replace only if the system declares dirfd already.
-if test $ac_cv_have_decl_dirfd = yes; then
-  REPLACE_DIRFD=1
-fi
 dnl Replace dirfd() on native Windows, to support fdopendir().
 AC_REQUIRE([gl_DIRENT_DIR])
 if test $DIR_HAS_FD_MEMBER = 0; then
-- 
2.39.2



Bug#1041588: marked as done (grep -r on 100000+ files fails with "Operation not supported" due to dirfd bug from gnulib)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 23:35:02 +
with message-id 
and subject line Bug#1041588: fixed in grep 3.11-2
has caused the Debian Bug report #1041588,
regarding grep -r on 10+ files fails with "Operation not supported" due to 
dirfd bug from gnulib
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.)


-- 
1041588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grep
Version: 3.11-1
Severity: grave
Justification: renders package unusable

There is a major regression in grep 3.11-1: I now get an error

cventin:~/Mail> grep -r xxxyyyzzz oldarc
grep: oldarc/cur: Operation not supported

This is just a big maildir mailbox (195700 messages).

The strace output has

[...]
81082 openat(5, "1511962287.17728_1395.cventin:2,S", 
O_RDONLY|O_NOCTTY|O_NONBLOCK|O_NOFOLLOW) = 6
81082 newfstatat(6, "", {st_mode=S_IFREG|0600, st_size=1171, ...}, 
AT_EMPTY_PATH) = 0
81082 read(6, "Return-Path:  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: grep
Source-Version: 3.11-2
Done: Santiago Ruano Rincón 

We believe that the bug you reported is fixed in the latest version of
grep, 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 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Ruano Rincón  (supplier of updated grep 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: Fri, 21 Jul 2023 18:33:27 -0300
Source: grep
Architecture: source
Version: 3.11-2
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar 
Changed-By: Santiago Ruano Rincón 
Closes: 1041588
Changes:
 grep (3.11-2) unstable; urgency=low
 .
   * Add d/patches/grep-dirfd.patch to fix gnulib bug that produces an
 'Operation not supported' error when grep -r 10+ files.
 Thanks to Vincent Lefèvre . (Closes: #1041588)
 - Include debian/tests/dirfd to test the fix.
Checksums-Sha1:
 249311d0eba1ec1f4a3f005e1ea7f0adc239ed1f 1618 grep_3.11-2.dsc
 a77b20035e07eab2556ea46c7c1024738ef0955f 20388 grep_3.11-2.debian.tar.xz
 92af8d0e7698163b9660926b8d82f6b88d95e93f 6626 grep_3.11-2_amd64.buildinfo
Checksums-Sha256:
 1242a5ba53e6c508aa472ad8de1a20de029b109b345af64c56f949ec40cd5bdb 1618 
grep_3.11-2.dsc
 39b98a7fea70c900a0ece8c317a1fc9ceed21326bddda715a2bb9fea60746a82 20388 
grep_3.11-2.debian.tar.xz
 004fd671bdd0d432facea3dd9928684212b95b0924eb2cfa58be45acee7bd68b 6626 
grep_3.11-2_amd64.buildinfo
Files:
 4c174b80af16e50cb799d8542ab1eaaf 1618 utils required grep_3.11-2.dsc
 e9a531c5f5a974d056623e9236edd235 20388 utils required grep_3.11-2.debian.tar.xz
 50fb8ae33a1ebd548dcbf11a3c725655 6626 utils required 
grep_3.11-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQRZVjztY8b+Ty43oH1itBCJKh26HQUCZLr/KAAKCRBitBCJKh26
HUHnAQC5Dmn58+3s3ZtJqzjujdhp5Nd5QUFnhyrDogfgjnZoUgD9HGs6lrGzEPhE
8+LgKQDCEifKVv3MXJI2ebPmyheBDgk=
=oIRl
-END PGP SIGNATURE End Message ---


Bug#1041674: fakeroot: compiling fakeroot looks to have a race condition not generating wrapped.h

2023-07-21 Thread Rudi Heitbaum
Package: fakeroot
Version: 1.32.1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: r...@heitbaum.com

Dear Maintainer,

   * What led up to the situation? 

 build of 1.32.1 on local build host was fine. on the CI build host it 
fails.
 
https://github.com/LibreELEC/actions/actions/runs/5623416630/job/1523806

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

 as per the actions run - you can see that it is inconsistent.


the build log is as below:

<<< fakeroot:host seq 43 <<<
UNPACK  fakeroot
APPLY PATCH (common)  
packages/devel/fakeroot/patches/fakeroot-001-disable-docs-tests.patch
patching file configure.ac
Hunk #1 succeeded at 744 (offset 147 lines).
patching file Makefile.am
Hunk #1 succeeded at 1 with fuzz 2.
FIXCONFIG  
/build/build.LibreELEC-H3.arm-12.0-devel/build/fakeroot-1.32.1/
BUILD  fakeroot (host)
TOOLCHAIN  configure
autoreconf: export WARNINGS=
[039/278] [FAIL] build   fakeroot:host
autoreconf: Entering directory '.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I build-aux
autoreconf: configure.ac: tracing
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'build-aux'.
libtoolize: copying file 'build-aux/libtool.m4'
libtoolize: copying file 'build-aux/ltoptions.m4'
libtoolize: copying file 'build-aux/ltsugar.m4'
libtoolize: copying file 'build-aux/ltversion.m4'
libtoolize: copying file 'build-aux/lt~obsolete.m4'
autoreconf: configure.ac: not using Intltool
autoreconf: configure.ac: not using Gtkdoc
autoreconf: running: aclocal --force -I build-aux
autoreconf: running: 
/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/bin/autoconf --force
configure.ac:428: warning: AC_CHECK_FUNCS($WRAPPED): you should use literals
/build/build.LibreELEC-H3.arm-12.0-devel/build/autoconf-2.71/lib/autoconf/functions.m4:117:
 AC_CHECK_FUNCS is expanded from...
configure.ac:428: the top level
configure.ac:497: warning: AC_CHECK_FUNCS($WRAPPED): you should use literals

The following log for this failure is available:
  /build/build.LibreELEC-H3.arm-12.0-devel/.threads/logs/43.log

/build/build.LibreELEC-H3.arm-12.0-devel/build/autoconf-2.71/lib/autoconf/functions.m4:117:
 AC_CHECK_FUNCS is expanded from...
configure.ac:497: the top level
autoreconf: running: 
/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:10: installing './compile'
configure.ac:7: installing './missing'
Makefile.am: installing './depcomp'
autoreconf: Leaving directory '.'
Executing (host): 
/build/build.LibreELEC-H3.arm-12.0-devel/build/fakeroot-1.32.1/configure 
--host=x86_64-linux-gnu --build=x86_64-linux-gnu 
--prefix=/build/build.LibreELEC-H3.arm-12.0-devel/toolchain 
--bindir=/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/bin 
--sbindir=/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/sbin 
--sysconfdir=/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/etc 
--libexecdir=/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/lib 
--localstatedir=/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/var 
--disable-static --enable-shared --with-gnu-ld
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a race-free mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether make supports the include directive... yes (GNU style)
checking for x86_64-linux-gnu-gcc... 
/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/bin/host-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether the compiler supports GNU C... yes
checking whether 
/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/bin/host-gcc accepts -g... 
yes
checking for /build/build.LibreELEC-H3.arm-12.0-devel/toolchain/bin/host-gcc 
option to enable C11 features... none needed
checking whether 
/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/bin/host-gcc understands -c 
and -o together... yes
checking dependency style of 
/build/build.LibreELEC-H3.arm-12.0-devel/toolchain/bin/host-gcc... gcc3
checking how to run the C preprocessor... cpp
checking whether make sets $(MAKE)... (cached) yes
checking how to print strings... printf
checking for a sed that does not 

Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Santiago Ruano Rincón
Control: tags -1 + pending

El 21/07/23 a las 19:46, Vincent Lefevre escribió:
> Control: tags -1 patch
> 
> On 2023-07-21 19:38:08 +0200, Vincent Lefevre wrote:
> > Indeed, it's a bundled gnulib. I was surprised because there is
> > no "gnulib" directory. Actually these are just files under the m4
> > directory. The bug is in "m4/dirfd.m4". I can see
> > 
> >   if test $ac_cv_func_dirfd = no && test $gl_cv_func_dirfd_macro = no; then
> > HAVE_DIRFD=0
> >   else
> > HAVE_DIRFD=1
> > dnl Replace only if the system declares dirfd already.
> > if test $ac_cv_have_decl_dirfd = yes; then
> >   REPLACE_DIRFD=1
> > fi
> > 
> > where the last 4 lines
> > 
> > dnl Replace only if the system declares dirfd already.
> > if test $ac_cv_have_decl_dirfd = yes; then
> >   REPLACE_DIRFD=1
> > fi
> > 
> > need to be removed to match the upstream gnulib fix.
> 
> And I could check that the corresponding attached patch makes
> the error disappear.

Thank you! Patch and autopkgetst inclucded. As long as I can confirm the
autopkgtest works, I upload the fixed version.

Cheers,

 -- S


signature.asc
Description: PGP signature


Processed: Re: Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + pending
Bug #1041588 [grep] grep -r on 10+ files fails with "Operation not 
supported" due to dirfd bug from gnulib
Added tag(s) pending.

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



Bug#1041474: marked as done (intel-gmmlib: FTBFS on i386: error: ambiguating new declaration of ‘GMM_STATUS GmmLib::GmmMultiAdapterContext::LockMAContextSyncMutex()’)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 20:57:29 +
with message-id 
and subject line Bug#1041474: fixed in intel-gmmlib 22.3.9+ds1-1
has caused the Debian Bug report #1041474,
regarding intel-gmmlib: FTBFS on i386: error: ambiguating new declaration of 
‘GMM_STATUS GmmLib::GmmMultiAdapterContext::LockMAContextSyncMutex()’
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.)


-- 
1041474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: intel-gmmlib
Version: 22.3.7+ds1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=intel-gmmlib=i386=22.3.7%2Bds1-1=1688230619=0

[ 53%] Building CXX object 
Source/GmmLib/CMakeFiles/igfx_gmmumd_dll.dir/GlobalInfo/GmmInfo.cpp.o
cd /<>/obj-i686-linux-gnu/Source/GmmLib && /usr/bin/c++ 
-DGMM_LIB_DLL -DGMM_LIB_DLL_EXPORTS -DGMM_UNIFIED_LIB -DGMM_UNIFY_DAF_API 
-DISTDLIB_UMD -DSMALL_POOL_ALLOC -DUNUSED_ISTDLIB_MT -D_ATL_NO_WIN_SUPPORT 
-D__GFX_MACRO_C__ -D__GMM -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS 
-D__UMD -Digfx_gmmumd_dll_EXPORTS -I/<>/Source/GmmLib 
-I/<>/Source/GmmLib/Utility/GmmLog 
-I/<>/Source/GmmLib/inc -I/<>/Source/GmmLib/Utility 
-I/<>/Source/GmmLib/GlobalInfo 
-I/<>/Source/GmmLib/Texture 
-I/<>/Source/GmmLib/Resource 
-I/<>/Source/GmmLib/Platform -I/<>/Source/util 
-I/<>/Source/inc -I/<>/Source/inc/common 
-I/<>/Source/inc/umKmInc -I/<>/Source/install -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-reorder 
-Wsign-promo -Wnon-virtual-dtor -Wno-invalid-offsetof 
-fvisibility-inlines-hidden -fno-use-cxa-atexit -fno-rtti -fexceptions 
-fcheck-new -std=c++11 -pthread -Werror=non-virtual-dtor -O3 -DNDEBUG -fPIC 
-Wall -Winit-self -Winvalid-pch -Wpointer-arith -Wno-unused 
-Wno-unknown-pragmas -Wno-comments -Wno-narrowing -Wno-overflow 
-Wno-parentheses -Wno-missing-braces -Wno-sign-compare -Wno-enum-compare 
-Werror=address -Werror=format-security -Werror=return-type -march=corei7 
-mpopcnt -msse -msse2 -msse3 -mssse3 -msse4 -msse4.1 -msse4.2 -mfpmath=sse 
-finline-functions -fno-short-enums -Wa,--noexecstack -fno-strict-aliasing 
-DUSE_MMX -DUSE_SSE -DUSE_SSE2 -DUSE_SSE3 -DUSE_SSSE3 -fstack-protector 
-fdata-sections -ffunction-sections -fmessage-length=0 -fvisibility=hidden 
-fPIC -g -m32 -funswitch-loops -Wl,--no-undefined -Wl,--no-as-needed 
-Wl,--gc-sections -O2 -fno-omit-frame-pointer -finline-limit=100 -MD -MT 
Source/GmmLib/CMakeFiles/igfx_gmmumd_dll.dir/GlobalInfo/GmmInfo.cpp.o -MF 
CMakeFiles/igfx_gmmumd_dll.dir/GlobalInfo/GmmInfo.cpp.o.d -o 
CMakeFiles/igfx_gmmumd_dll.dir/GlobalInfo/GmmInfo.cpp.o -c 
/<>/Source/GmmLib/GlobalInfo/GmmInfo.cpp
/<>/Source/GmmLib/GlobalInfo/GmmInfo.cpp:628:24: error: 
ambiguating new declaration of ‘GMM_STATUS 
GmmLib::GmmMultiAdapterContext::LockMAContextSyncMutex()’
  628 | GMM_STATUS GMM_STDCALL 
GmmLib::GmmMultiAdapterContext::LockMAContextSyncMutex()
  |^~
In file included from 
/<>/Source/GmmLib/inc/External/Common/GmmInfoExt.h:25,
 from 
/<>/Source/GmmLib/inc/../Texture/GmmTexture.h:27,
 from 
/<>/Source/GmmLib/inc/Internal/Common/GmmLibInc.h:52,
 from /<>/Source/GmmLib/GlobalInfo/GmmInfo.cpp:23:
/<>/Source/GmmLib/inc/External/Common/GmmInfo.h:630:41: note: old 
declaration ‘GMM_STATUS 
GmmLib::GmmMultiAdapterContext::LockMAContextSyncMutex()’
  630 | GMM_STATUS  LockMAContextSyncMutex();
  | ^~
/<>/Source/GmmLib/GlobalInfo/GmmInfo.cpp:639:24: error: 
ambiguating new declaration of ‘GMM_STATUS 
GmmLib::GmmMultiAdapterContext::UnLockMAContextSyncMutex()’
  639 | GMM_STATUS GMM_STDCALL 
GmmLib::GmmMultiAdapterContext::UnLockMAContextSyncMutex()
  |^~
/<>/Source/GmmLib/inc/External/Common/GmmInfo.h:631:41: note: old 
declaration ‘GMM_STATUS 
GmmLib::GmmMultiAdapterContext::UnLockMAContextSyncMutex()’
  631 | GMM_STATUS  UnLockMAContextSyncMutex();
  | ^~~~
make[3]: *** [Source/GmmLib/CMakeFiles/igfx_gmmumd_dll.dir/build.make:527: 
Source/GmmLib/CMakeFiles/igfx_gmmumd_dll.dir/GlobalInfo/GmmInfo.cpp.o] Error 1


Andreas
--- End Message ---
--- Begin Message ---
Source: intel-gmmlib
Source-Version: 22.3.9+ds1-1
Done: Sebastian Ramacher 

We believe that the bug you reported is fixed in the latest version of
intel-gmmlib, which is due to be installed 

Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH

2023-07-21 Thread Brad King
On Fri, Jul 21, 2023 at 2:37 PM Brad King wrote:
> The behavior change came from this CMake merge request:
> * https://gitlab.kitware.com/cmake/cmake/-/merge_requests/8538
> because the distutils variant is deprecated.

This is now under discussion in an upstream CMake issue:

* https://gitlab.kitware.com/cmake/cmake/-/issues/25113

Thanks,
-Brad



Bug#1040731: wslay: autopkgtest failure due to new CMake deprecation warning

2023-07-21 Thread Anton Gladky
Hi Chris,

Thanks a lot for the MR and update.
I will prepare an update and upload it in one week. If it's ok for you.
Otherwise, please NMU.

 Best regards

Chris Hofstaedtler  schrieb am Fr., 21. Juli 2023, 20:58:

> Hi Anton,
>
> * roehl...@debian.org :
> > Source: wslay
> [..]
> >
> > your package wslay will soon experience autopkgtest failures because
> > the new CMake release 3.27 will issue a deprecation warning on stderr
> > if cmake_minimum_required() asks for compatibility with CMake 3.4 or
> > older.
>
> I've opened an MR with a trivial fix for this on salsa.d.o:
>   https://salsa.debian.org/debian/wslay/-/merge_requests/5
>
> Depending on your preferences I could also prepare an NMU with this
> and upload to delayed?
>
> Thanks,
> Chris
>
>
> PS: I assume wslay probably wants to go away. I hope dnsdist can
> switch from h2o to nghttp2 during trixie.
>


Bug#1040731: wslay: autopkgtest failure due to new CMake deprecation warning

2023-07-21 Thread Chris Hofstaedtler
Hi Anton,

* roehl...@debian.org :
> Source: wslay
[..]
> 
> your package wslay will soon experience autopkgtest failures because
> the new CMake release 3.27 will issue a deprecation warning on stderr
> if cmake_minimum_required() asks for compatibility with CMake 3.4 or
> older.

I've opened an MR with a trivial fix for this on salsa.d.o:
  https://salsa.debian.org/debian/wslay/-/merge_requests/5

Depending on your preferences I could also prepare an NMU with this
and upload to delayed?

Thanks,
Chris


PS: I assume wslay probably wants to go away. I hope dnsdist can
switch from h2o to nghttp2 during trixie.



Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH

2023-07-21 Thread Brad King
On Fri, Jul 21, 2023 at 11:21 AM Sebastiaan Couwenberg wrote:
> On bookworm distutils is still used which returns:
...
> On sid sysconfig is used which results:

The behavior change came from this CMake merge request:

* https://gitlab.kitware.com/cmake/cmake/-/merge_requests/8538

because the distutils variant is deprecated.

> To get the right path for the Debian python3 interpreter,
> you need to add 'deb_system':

With distutils a generic `plat_specific=True` option was enough
to get each platform's preferred behavior.  Does every client
of Python's sysconfig need to have a big dispatch block that
looks up the host platform and memorizes platform-specific
arguments?  A similar concern was raised here:

* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998739#22

but never resolved.

As a side note, adding `DEB_PYTHON_INSTALL_LAYOUT=deb`
to the environment resolves this locally.

-Brad



Processed: src:python-gnuplotlib: fails to migrate to testing for too long: uploader built binaries

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> close -1 0.40-1
Bug #1041661 [src:python-gnuplotlib] src:python-gnuplotlib: fails to migrate to 
testing for too long: uploader built binaries
Marked as fixed in versions python-gnuplotlib/0.40-1.
Bug #1041661 [src:python-gnuplotlib] src:python-gnuplotlib: fails to migrate to 
testing for too long: uploader built binaries
Marked Bug as done

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



Bug#1041661: src:python-gnuplotlib: fails to migrate to testing for too long: uploader built binaries

2023-07-21 Thread Paul Gevers

Source: python-gnuplotlib
Version: 0.39-1
Severity: serious
Control: close -1 0.40-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:python-gnuplotlib has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug.


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=python-gnuplotlib



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1041660: src:sccache: fails to migrate to testing for too long: Build Depends no longer exist

2023-07-21 Thread Paul Gevers

Source: sccache
Version: 0.4.0~~pre8-8
Severity: serious
Control: close -1 0.5.4-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:sccache has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable can't 
migrate because one of its build dependencies no longer exists.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=sccache



OpenPGP_signature
Description: OpenPGP digital signature


Processed: src:sccache: fails to migrate to testing for too long: Build Depends no longer exist

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> close -1 0.5.4-2
Bug #1041660 [src:sccache] src:sccache: fails to migrate to testing for too 
long: Build Depends no longer exist
Marked as fixed in versions sccache/0.5.4-2.
Bug #1041660 [src:sccache] src:sccache: fails to migrate to testing for too 
long: Build Depends no longer exist
Marked Bug as done

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



Processed: update bts meta info

2023-07-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1040058 src:sympy 1.12-2
Bug #1040058 {Done: Georges Khaznadar } [src:sympy, 
src:sagemath] sympy breaks sagemath autopkgtest: 371 tests failed, up to 200 
failures are tolerated
Bug reassigned from package 'src:sympy, src:sagemath' to 'src:sympy'.
No longer marked as found in versions sympy/1.12-2 and sagemath/9.5-6.
No longer marked as fixed in versions sympy/1.12-3.
Bug #1040058 {Done: Georges Khaznadar } [src:sympy] sympy 
breaks sagemath autopkgtest: 371 tests failed, up to 200 failures are tolerated
Marked as found in versions sympy/1.12-2.
> affects 1040058 src:sagemath
Bug #1040058 {Done: Georges Khaznadar } [src:sympy] sympy 
breaks sagemath autopkgtest: 371 tests failed, up to 200 failures are tolerated
Added indication that 1040058 affects src:sagemath
> fixed 1040058 1.12-3
Bug #1040058 {Done: Georges Khaznadar } [src:sympy] sympy 
breaks sagemath autopkgtest: 371 tests failed, up to 200 failures are tolerated
Marked as fixed in versions sympy/1.12-3.
> thanks
Stopping processing here.

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



Processed: bug housekeeping

2023-07-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # no reply from the submitter in over two weeks, downgrade the severity
> # and reassign where it probably belongs
> tags 1040254 + moreinfo
Bug #1040254 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: 
Regression: Crashes with "(EE) Caught signal 11 (Segmentation fault). Server 
aborting" upon start after dist-upgrade from Bullseye to Bookworm
Added tag(s) moreinfo.
> severity 1040254 important
Bug #1040254 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: 
Regression: Crashes with "(EE) Caught signal 11 (Segmentation fault). Server 
aborting" upon start after dist-upgrade from Bullseye to Bookworm
Severity set to 'important' from 'grave'
> reassign 1040254 libgl1-mesa-dri 22.3.6-1+deb12u1
Bug #1040254 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: 
Regression: Crashes with "(EE) Caught signal 11 (Segmentation fault). Server 
aborting" upon start after dist-upgrade from Bullseye to Bookworm
Bug reassigned from package 'xserver-xorg-video-nouveau' to 'libgl1-mesa-dri'.
No longer marked as found in versions xserver-xorg-video-nouveau/1:1.0.17-2.
Ignoring request to alter fixed versions of bug #1040254 to the same values 
previously set
Bug #1040254 [libgl1-mesa-dri] xserver-xorg-video-nouveau: Regression: Crashes 
with "(EE) Caught signal 11 (Segmentation fault). Server aborting" upon start 
after dist-upgrade from Bullseye to Bookworm
Marked as found in versions mesa/22.3.6-1+deb12u1.
> thanks
Stopping processing here.

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



Bug#1041432: marked as done (box64: unsatisfiable dependencies)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 13:53:55 -0400
with message-id 

and subject line Re: Bug#1041432: box64: unsatisfiable dependencies
has caused the Debian Bug report #1041432,
regarding box64: unsatisfiable dependencies
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.)


-- 
1041432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: box64
Version: 0.2.2+dfsg-2
Severity: serious

https://tracker.debian.org/pkg/box64 says that box64 is unable to
migrate into Testing because it has unsatisfiable dependencies on
amd64, arm64, ppc64el (and I guess riscv64)

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Version: 0.2.2+dfsg-3--- End Message ---


Bug#1040049: marked as done (gnome-terminal: crash with assertion failure on mouseover: row < m_start + m_len)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 17:53:12 +
with message-id 
and subject line Bug#1040049: fixed in vte2.91 0.72.2-3
has caused the Debian Bug report #1040049,
regarding gnome-terminal: crash with assertion failure on mouseover: row < 
m_start + m_len
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.)


-- 
1040049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-terminal
Version: 3.46.8-1
Severity: important
Tags: patch bookworm
Forwarded: https://gitlab.gnome.org/GNOME/vte/-/issues/2577

Dear Maintainer(s),

gnome-terminal-server asserts on mouseover, losing all open terminals:

gnome-terminal-server[2464750]: VTE:ERROR:../src/ringview.cc:299:const 
vte::base::BidiRow* vte::base::RingView::get_bidirow(vte::grid::row_t) const: 
assertion failed (row < m_start + m_len): (15728 < 15725)
gnome-terminal-server[2464750]: Bail out! 
VTE:ERROR:../src/ringview.cc:299:const vte::base::BidiRow* 
vte::base::RingView::get_bidirow(vte::grid::row_t) const: assertion failed (row 
< m_start + m_len): (15728 < 15725)

This is upstream issue:

https://gitlab.gnome.org/GNOME/vte/-/issues/2577

Which was fixed by:

https://gitlab.gnome.org/GNOME/vte/-/commit/dcfc0ec44df3084987a6faa0fdc03e6de717c682

Please backport the fix to bookworm via proposed-updates, given it's a
hard crash.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: vte2.91
Source-Version: 0.72.2-3
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
vte2.91, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated vte2.91 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: Fri, 21 Jul 2023 13:24:24 -0400
Source: vte2.91
Built-For-Profiles: noudeb
Architecture: source
Version: 0.72.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1037919 1040049
Launchpad-Bugs-Fixed: 2022019
Changes:
 vte2.91 (0.72.2-3) unstable; urgency=medium
 .
   * Release to unstable
 .
 vte2.91 (0.72.2-2) experimental; urgency=medium
 .
   [ Simon McVittie ]
   * d/p/widget-Invalidate-ringview-when-the-invalidating.patch:
 Add patch from upstream git to invalidate ring view more often when
 necessary, fixing various assertion failures during event handling
 (Closes: #1040049)
 .
 vte2.91 (0.72.2-1) experimental; urgency=medium
 .
   * New upstream release
 - Includes fix for an infinite loop processing OSC 104.
   A malicious program accessed via ssh, telnet or similar protocols could
   use this as a denial of service.
   (Closes: #1037919, LP: #2022019; vte#2631 upstream)
 .
 vte2.91 (0.72.1-1) experimental; urgency=medium
 .
   * New upstream release
 .
 vte2.91 (0.72.0-1) experimental; urgency=medium
 .
   * New upstream release
 .
 vte2.91 (0.71.99-1) experimental; urgency=medium
 .
   * New upstream release
 .
 vte2.91 (0.71.92-1) experimental; urgency=medium
 .
   * New upstream release
   * debian/libvte-2.91-0.symbols: Add new symbols
Checksums-Sha1:
 037bd9e7614041ba8dfea6802fbaa56632f51a51 3199 vte2.91_0.72.2-3.dsc
 133592e0d20e77a7e074cb478c5bd589667ccf16 25476 vte2.91_0.72.2-3.debian.tar.xz
 0703efd48e3df94ae3ac02230355e08867d3890b 18808 
vte2.91_0.72.2-3_source.buildinfo
Checksums-Sha256:
 adebd5fe4b95c90e4bd8d4c0080c6268714aa64509801f87023e3307bf2bedce 3199 
vte2.91_0.72.2-3.dsc
 6f8744ff262d0889230f00088c6333764ffb0f1216c88bbb40c1cd5c78cc67aa 25476 
vte2.91_0.72.2-3.debian.tar.xz
 81cd56e7e38966651a254828fd765a2c5bd00a06d648f90e3b9ef520aff71b17 18808 
vte2.91_0.72.2-3_source.buildinfo
Files:
 c22b9ea3d381a681acd7bd23d65ecb97 3199 libs optional vte2.91_0.72.2-3.dsc
 6bea22291dc71d7c610d5ea30454f6b2 25476 libs optional 
vte2.91_0.72.2-3.debian.tar.xz
 3384041435c4dbe5f96e41a6e48e0609 18808 libs optional 
vte2.91_0.72.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-


Processed: src:vnlog: fails to migrate to testing for too long: uploader built arch:all binaries

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> close -1 1.35-1
Bug #1041659 [src:vnlog] src:vnlog: fails to migrate to testing for too long: 
uploader built arch:all binaries
Marked as fixed in versions vnlog/1.35-1.
Bug #1041659 [src:vnlog] src:vnlog: fails to migrate to testing for too long: 
uploader built arch:all binaries
Marked Bug as done

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



Bug#1041659: src:vnlog: fails to migrate to testing for too long: uploader built arch:all binaries

2023-07-21 Thread Paul Gevers

Source: vnlog
Version: 1.34-2
Severity: serious
Control: close -1 1.35-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:vnlog has been trying to migrate for 31 
days [2]. Hence, I am filing this bug.


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=vnlog



OpenPGP_signature
Description: OpenPGP digital signature


Processed: src:asmjit: fails to migrate to testing for too long: FTBFS on armel, armhf and mips64el

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> close -1 0.0~git20230427.3577608-1
Bug #1041657 [src:asmjit] src:asmjit: fails to migrate to testing for too long: 
FTBFS on armel, armhf and mips64el
Marked as fixed in versions asmjit/0.0~git20230427.3577608-1.
Bug #1041657 [src:asmjit] src:asmjit: fails to migrate to testing for too long: 
FTBFS on armel, armhf and mips64el
Marked Bug as done

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



Bug#1041657: src:asmjit: fails to migrate to testing for too long: FTBFS on armel, armhf and mips64el

2023-07-21 Thread Paul Gevers

Source: asmjit
Version: 0.0~git20221210.5b5b0b3-1
Severity: serious
Control: close -1 0.0~git20230427.3577608-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:asmjit has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable failed to 
build from source on armel, armhf and mips64el where it built 
successfully in the past.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=asmjit



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1037805: marked as done (openmw: ftbfs with GCC-13)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 17:51:59 +
with message-id 
and subject line Bug#1037805: fixed in openmw 0.48.0-1
has caused the Debian Bug report #1037805,
regarding openmw: ftbfs with GCC-13
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.)


-- 
1037805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openmw
Version: 0.47.0-3
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/openmw_0.47.0-3_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:426:3: note: declared here
  426 | } AVPacketList;
  |   ^~~~
/<>/extern/osg-ffmpeg-videoplayer/videostate.cpp:176:25: warning: 
‘AVPacketList’ is deprecated [-Wdeprecated-declarations]
  176 | AVPacketList *pkt, *pkt1;
  | ^~~~
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:426:3: note: declared here
  426 | } AVPacketList;
  |   ^~~~
/<>/extern/osg-ffmpeg-videoplayer/videostate.cpp: In member 
function ‘void Video::VideoThread::run()’:
/<>/extern/osg-ffmpeg-videoplayer/videostate.cpp:443:23: warning: 
‘void av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
  443 | av_init_packet();
  | ~~^
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:512:6: note: declared here
  512 | void av_init_packet(AVPacket *pkt);
  |  ^~
/<>/extern/osg-ffmpeg-videoplayer/videostate.cpp: In member 
function ‘void Video::ParseThread::run()’:
/<>/extern/osg-ffmpeg-videoplayer/videostate.cpp:511:23: warning: 
‘void av_init_packet(AVPacket*)’ is deprecated [-Wdeprecated-declarations]
  511 | av_init_packet();
  | ~~^
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:512:6: note: declared here
  512 | void av_init_packet(AVPacket *pkt);
  |  ^~
In file included from 
/<>/extern/osg-ffmpeg-videoplayer/videoplayer.cpp:8:
/<>/extern/osg-ffmpeg-videoplayer/videostate.hpp:88:19: warning: 
‘AVPacketList’ is deprecated [-Wdeprecated-declarations]
   88 | AVPacketList *first_pkt, *last_pkt;
  |   ^
In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
 from 
/<>/extern/osg-ffmpeg-videoplayer/audiodecoder.hpp:17,
 from 
/<>/extern/osg-ffmpeg-videoplayer/audiofactory.hpp:4,
 from 
/<>/extern/osg-ffmpeg-videoplayer/videoplayer.cpp:7:
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:426:3: note: declared here
  426 | } AVPacketList;
  |   ^~~~
/<>/extern/osg-ffmpeg-videoplayer/videostate.hpp:88:31: warning: 
‘AVPacketList’ is deprecated [-Wdeprecated-declarations]
   88 | AVPacketList *first_pkt, *last_pkt;
  |   ^~~~
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:426:3: note: declared here
  426 | } AVPacketList;
  |   ^~~~
[  1%] Linking CXX static library libosg-ffmpeg-videoplayer.a
cd /<>/build/extern/osg-ffmpeg-videoplayer && /usr/bin/cmake -P 
CMakeFiles/osg-ffmpeg-videoplayer.dir/cmake_clean_target.cmake
cd /<>/build/extern/osg-ffmpeg-videoplayer && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/osg-ffmpeg-videoplayer.dir/link.txt --verbose=1
/usr/bin/ar qc libosg-ffmpeg-videoplayer.a 
"CMakeFiles/osg-ffmpeg-videoplayer.dir/videoplayer.cpp.o" 

Processed: src:aflplusplus: fails to migrate to testing for too long: unresolved RC issues

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> close -1 4.07c-1
Bug #1041655 [src:aflplusplus] src:aflplusplus: fails to migrate to testing for 
too long: unresolved RC issues
Marked as fixed in versions aflplusplus/4.07c-1.
Bug #1041655 [src:aflplusplus] src:aflplusplus: fails to migrate to testing for 
too long: unresolved RC issues
Marked Bug as done
> block -1 by 1038760
Bug #1041655 {Done: Paul Gevers } [src:aflplusplus] 
src:aflplusplus: fails to migrate to testing for too long: unresolved RC issues
1041655 was not blocked by any bugs.
1041655 was not blocking any bugs.
Added blocking bug(s) of 1041655: 1038760

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



Bug#1041655: src:aflplusplus: fails to migrate to testing for too long: unresolved RC issues

2023-07-21 Thread Paul Gevers

Source: aflplusplus
Version: 4.04c-4
Severity: serious
Control: close -1 4.07c-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1038760

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:aflplusplus has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build from source as reported in bug #1038760.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=aflplusplus



OpenPGP_signature
Description: OpenPGP digital signature


Processed: Re: grep -r fails with "Operation not supported"

2023-07-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 1041588 grep -r on 10+ files fails with "Operation not supported" 
> due to dirfd bug from gnulib
Bug #1041588 [grep] grep -r on 10+ files fails with "Operation not 
supported"
Changed Bug title to 'grep -r on 10+ files fails with "Operation not 
supported" due to dirfd bug from gnulib' from 'grep -r on 10+ files fails 
with "Operation not supported"'.
> thanks
Stopping processing here.

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



Processed: Re: Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 patch
Bug #1041588 [grep] grep -r on 10+ files fails with "Operation not 
supported"
Added tag(s) patch.

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



Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Vincent Lefevre
Control: tags -1 patch

On 2023-07-21 19:38:08 +0200, Vincent Lefevre wrote:
> Indeed, it's a bundled gnulib. I was surprised because there is
> no "gnulib" directory. Actually these are just files under the m4
> directory. The bug is in "m4/dirfd.m4". I can see
> 
>   if test $ac_cv_func_dirfd = no && test $gl_cv_func_dirfd_macro = no; then
> HAVE_DIRFD=0
>   else
> HAVE_DIRFD=1
> dnl Replace only if the system declares dirfd already.
> if test $ac_cv_have_decl_dirfd = yes; then
>   REPLACE_DIRFD=1
> fi
> 
> where the last 4 lines
> 
> dnl Replace only if the system declares dirfd already.
> if test $ac_cv_have_decl_dirfd = yes; then
>   REPLACE_DIRFD=1
> fi
> 
> need to be removed to match the upstream gnulib fix.

And I could check that the corresponding attached patch makes
the error disappear.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
diff -Naurd grep-3.11-orig/m4/dirfd.m4 grep-3.11/m4/dirfd.m4
--- grep-3.11~/m4/dirfd.m4	2023-04-29 11:03:00.0 +0200
+++ grep-3.11/m4/dirfd.m4	2023-07-21 19:40:41.345044696 +0200
@@ -40,10 +40,6 @@
 HAVE_DIRFD=0
   else
 HAVE_DIRFD=1
-dnl Replace only if the system declares dirfd already.
-if test $ac_cv_have_decl_dirfd = yes; then
-  REPLACE_DIRFD=1
-fi
 dnl Replace dirfd() on native Windows, to support fdopendir().
 AC_REQUIRE([gl_DIRENT_DIR])
 if test $DIR_HAS_FD_MEMBER = 0; then


Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Vincent Lefevre
On 2023-07-21 13:08:11 -0400, Boyuan Yang wrote:
> BTW: Is grep 3.11-1 using Debian-packaged gnulib anywere? I did not
> see a build-dependency in
> https://sources.debian.org/src/grep/3.11-1/debian/control/ .
> 
> * If grep is indeed using it, please include the build-dep explicitly.
> 
> * If not, your current grep issue is unrelated to Debian-packaged gnulib and
> you will need further debugging.

Indeed, it's a bundled gnulib. I was surprised because there is
no "gnulib" directory. Actually these are just files under the m4
directory. The bug is in "m4/dirfd.m4". I can see

  if test $ac_cv_func_dirfd = no && test $gl_cv_func_dirfd_macro = no; then
HAVE_DIRFD=0
  else
HAVE_DIRFD=1
dnl Replace only if the system declares dirfd already.
if test $ac_cv_have_decl_dirfd = yes; then
  REPLACE_DIRFD=1
fi

where the last 4 lines

dnl Replace only if the system declares dirfd already.
if test $ac_cv_have_decl_dirfd = yes; then
  REPLACE_DIRFD=1
fi

need to be removed to match the upstream gnulib fix.

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



Bug#1040845: marked as done (doit autopkg test fails with setuptools)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 17:34:24 +
with message-id 
and subject line Bug#1040845: fixed in doit 0.31.1-3.4
has caused the Debian Bug report #1040845,
regarding doit autopkg test fails with setuptools
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.)


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

Package: src:doit
Version: 0.31.1-3.3
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/d/doit/35654863/log.gz

[...]
autopkgtest [23:39:02]: test version:  - - - - - - - - - - results - - - - - - - 
- - -
 26s version  FAIL stderr: /usr/bin/doit:6: DeprecationWarning: 
pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html
--- End Message ---
--- Begin Message ---
Source: doit
Source-Version: 0.31.1-3.4
Done: Julian Andres Klode 

We believe that the bug you reported is fixed in the latest version of
doit, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated doit 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: Fri, 21 Jul 2023 19:05:19 +0200
Source: doit
Architecture: source
Version: 0.31.1-3.4
Distribution: unstable
Urgency: medium
Maintainer: Agustin Henze 
Changed-By: Julian Andres Klode 
Closes: 1040845
Changes:
 doit (0.31.1-3.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * No-change rebuild to pick up non-pkg_resources entry point
 (Closes: #1040845)
Checksums-Sha1:
 7810e36ba289edc1ca9ce28704c2786c4279be1e 2289 doit_0.31.1-3.4.dsc
 1acb936aac65c3ba09059b5e65fb3c5a611b6c19 6864 doit_0.31.1-3.4.debian.tar.xz
 db8a860617204af7ffd1ab474cc4806b075ae3e7 7560 doit_0.31.1-3.4_source.buildinfo
Checksums-Sha256:
 0ba6cdaaa52c44ffd5526909e98e3bc519b46d23765da8b0f54ca2deca92ebdb 2289 
doit_0.31.1-3.4.dsc
 d1fdb6dacad3d2f85d28a517444db496fe200177b866690fadbc41899b92bc7e 6864 
doit_0.31.1-3.4.debian.tar.xz
 bc46d73d2c7765ad3af4b020224d9475758674c76fc340439d267a335368ad61 7560 
doit_0.31.1-3.4_source.buildinfo
Files:
 361a8d92ded95bf02e46ad9d302589dd 2289 python optional doit_0.31.1-3.4.dsc
 606e6b07ee2e506e9493997890b5964f 6864 python optional 
doit_0.31.1-3.4.debian.tar.xz
 7a06e2c00d4092a3bee3e7ed5eaef0da 7560 python optional 
doit_0.31.1-3.4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEET7WIqEwt3nmnTHeHb6RY3R2wP3EFAmS6u9sPHGpha0BkZWJp
YW4ub3JnAAoJEG+kWN0dsD9xXHIQAJpc+mcLNOSGKZvE+QKvN+Pbq1uzJOb7xh/c
KK9dR0oKLDFgnIH1yh8CIiEkkMZUrabadTVe/ivGKFnrCqXr4sP3xf8J6gWE1duB
EkEW0OnmC8I+Zw8yYotP9QkmdiC7HLNP4pXO/cxQ95r1fDf7Kw+Tp6g96TIkh2Ng
RBkBLqj+cF0pEUn/xa/sNLiNMU+x1RMKhpCjW6zXvv+RJNGEmnfXI6pXzay5xJQl
1jgIqA3h2OL2jzhYHoy5cRhBsjXLGuRiCVNP44wSkb2c5ZGvO7sbnManl6wtsssb
JGA8vWY2+8PQugE/Jp0hbtzI+RHWUix5EXsBxTda/KPAkG4Xfo0OIU/O6AM7Fg0a
36vtzcujFdFkD5JtHVt8mCalQJoak6ph+8UOkKclWj6/mHEOfMfTvQB2dTSSXUfP
jLfuiIf8JIgYZTP+LZe+j82iCTWV1TeLDrmjvgmvuwKUAcwLWfvHkyB3KgNNsOht
bZf97F5qymXgcA3UkTUiQ9AGcv7pqFwEfbBI7YGUn+oQhqhxze7sPOeYDj68bhKd
NhJveO8NL1kX6O92w5TOKti88VTama353MmhOoYGItDZ42W3GkcgkheOn/lL+Q3+
RODdlcaOFvbetLEnX87+JklOINbCynYg1fa5oTc2de5DCLv4fFBSUTFNZ+EWbZwb
PoSWeepa
=MA+c
-END PGP SIGNATURE End Message ---


Processed: Re: Bug#1041588: Info received (grep 3.11 -r on 100000+ files fails with "Operation not supported")

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64773
Bug #1041588 [grep] grep -r on 10+ files fails with "Operation not 
supported"
Set Bug forwarded-to-address to 
'https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64773'.
> tags -1 + upstream
Bug #1041588 [grep] grep -r on 10+ files fails with "Operation not 
supported"
Added tag(s) upstream.

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



Bug#1041588: Info received (grep 3.11 -r on 100000+ files fails with "Operation not supported")

2023-07-21 Thread Santiago Ruano Rincón
Control: forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64773
Control: tags -1 + upstream


signature.asc
Description: PGP signature


Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Santiago Ruano Rincón
Hi!

El 21/07/23 a las 11:02, Boyuan Yang escribió:
> Hi,
> 
> On Fri, 21 Jul 2023 10:39:54 +0200 Vincent Lefevre  wrote:
> > Control: severity -1 grave
> > Control: tags -1 - moreinfo
> > Control: retitle -1 grep -r on 10+ files fails with "Operation not
> supported"
> > 
> > On 2023-07-20 23:43:45 -0300, Santiago Ruano Rincón wrote:
> > > El 21/07/23 a las 04:06, Vincent Lefevre escribió:
> > > > On 2023-07-21 03:30:12 +0200, Vincent Lefevre wrote:
> > > > > There is a major regression in grep 3.11-1: I now get an error
> > > > > 
> > > > > cventin:~/Mail> grep -r xxxyyyzzz oldarc
> > > > > grep: oldarc/cur: Operation not supported
> > > > 
> > > > And no such issue with grep from the upstream git.
> > > 
> > > How are you compiling it?
> > 
> > $ ./bootstrap
> > $ ./configure --prefix=$HOME/opt/grep
> > $ make
> > $ make install
> > 
> > > My intuition is this comes from gnulib.
> > 
> > Yes, as in my next message, I said that the error disappeared
> > with the commit that updated gnulib (and did nothing else).
> > 
> > > But a reproducer is needed to confirm.
> > > 
> > > Tagging with moreinfo, and downgrading the severity since I cannot
> > > reproduce it myself:
> > [...]
> > > Please, feel free to bump the severity back again if you are able to
> > > find out a way to reproduce it.
> > 
> > One needs at least 10 files in the directory (9 is not enough).
> > With 10 empty files:
> > 
> > $ mkdir test-dir && for i in `seq 10` ; do : > test-dir/$i ; done
> > $ grep -r x test-dir
> > grep: test-dir: Operation not supported
> 
> Debian gnulib package maintainer here. I briefly checked grep source code,
> and it seems that grep is using the bundled gnulib and not using the packaged
> gnulib. Not 100% sure.

It indeed currently uses a bundled gnulib.

> 
> Whether to use the bundled gnulib is up to the packager's decision. Anyway,
> let me know if I could help.

I suppose we could give the packaged gnulib a try. Patches welcome ;-)

Cheers,

 -- S


signature.asc
Description: PGP signature


Bug#1041588: grep 3.11 -r on 100000+ files fails with "Operation not supported"

2023-07-21 Thread Santiago Ruano Rincón
Dear grep developers,

I am forwarding this gnulib bug that affects grep 3.11. Full bug report
can be found at https://bugs.debian.org/1041588

El 21/07/23 a las 10:39, Vincent Lefevre escribió:
> Control: severity -1 grave
> Control: tags -1 - moreinfo
> Control: retitle -1 grep -r on 10+ files fails with "Operation not 
> supported"
> 
> On 2023-07-20 23:43:45 -0300, Santiago Ruano Rincón wrote:
> > El 21/07/23 a las 04:06, Vincent Lefevre escribió:
> > > On 2023-07-21 03:30:12 +0200, Vincent Lefevre wrote:
> > > > There is a major regression in grep 3.11-1: I now get an error
> > > > 
> > > > cventin:~/Mail> grep -r xxxyyyzzz oldarc
> > > > grep: oldarc/cur: Operation not supported
> > > 
> > > And no such issue with grep from the upstream git.
> > 
> > How are you compiling it?
> 
> $ ./bootstrap
> $ ./configure --prefix=$HOME/opt/grep
> $ make
> $ make install
> 
> > My intuition is this comes from gnulib.
> 
> Yes, as in my next message, I said that the error disappeared
> with the commit that updated gnulib (and did nothing else).

Indeed. Our mails crossed.

> 
> > But a reproducer is needed to confirm.
> > 
> > Tagging with moreinfo, and downgrading the severity since I cannot
> > reproduce it myself:
> [...]
> > Please, feel free to bump the severity back again if you are able to
> > find out a way to reproduce it.
> 
> One needs at least 10 files in the directory (9 is not enough).
> With 10 empty files:
> 
> $ mkdir test-dir && for i in `seq 10` ; do : > test-dir/$i ; done
> $ grep -r x test-dir
> grep: test-dir: Operation not supported

Thank you, Vincent. I confirm with 9 files grep works as expected.

Cheers,

 -- Santiago


signature.asc
Description: PGP signature


Bug#1039714: marked as done (gobject-introspection: dh_girepository does not fetch all symbols from GIR files)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 17:05:56 +
with message-id 
and subject line Bug#1039714: fixed in gobject-introspection 1.76.1-3
has caused the Debian Bug report #1039714,
regarding gobject-introspection: dh_girepository does not fetch all symbols 
from GIR files
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.)


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

Package: gir1.2-harfbuzz-0.0
Version: 6.0.0+dfsg-3
Severity: serious

Dear maintainers,

HarfBuzz-0.0.typelib needs the shared library libharfbuzz-gobject.so.0 
(from package libharfbuzz-gobject0) to be installed, but this dependency 
is missing in the control file.
So can you please add the missing dependency on libharfbuzz-gobject0 to 
gir1.2-harfbuzz-0.0.


Thank you in advance!

Best regards,

Thomas Uhle


-- System Information:
Debian Release: 12.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Foreign Architectures: armhf

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

Versions of packages gir1.2-harfbuzz-0.0 depends on:
ii  gir1.2-freedesktop  1.74.0-3
ii  gir1.2-glib-2.0 1.74.0-3

gir1.2-harfbuzz-0.0 recommends no packages.

gir1.2-harfbuzz-0.0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gobject-introspection
Source-Version: 1.76.1-3
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
gobject-introspection, 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 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gobject-introspection 
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: Fri, 21 Jul 2023 14:25:12 +0100
Source: gobject-introspection
Architecture: source
Version: 1.76.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1039714
Changes:
 gobject-introspection (1.76.1-3) unstable; urgency=medium
 .
   * Team upload
 .
   [ Simon McVittie ]
   * d/rules, d/meson/no-exe-wrapper.ini: Work around a meson bug which
 caused FTBFS on mips64el. (Mitigates: #1041499)
 .
   [ Thomas Uhle ]
   * dh_girepository: Discover more symbols in GIR files, fixing incomplete
 ${gir:Depends} in packages like gir1.2-harfbuzz-0.0 and
 gir1.2-freedesktop (Closes: #1039714)
Checksums-Sha1:
 17010e729280d8e824fafd6aaf0affd55f442803 3520 
gobject-introspection_1.76.1-3.dsc
 214307f3a28483070d384c50bdac5b1a9c6c33b4 49248 
gobject-introspection_1.76.1-3.debian.tar.xz
 6910290abf8f09e02be6cfb71e6fd267349799b7 9200 
gobject-introspection_1.76.1-3_source.buildinfo
Checksums-Sha256:
 4a77492b7b2f5264162e13d07fd32d1bff20f63e22cd1c283207780e1cf6f7bb 3520 
gobject-introspection_1.76.1-3.dsc
 6f52612abbf0112c9106d7ce4d7ae3063bf364f280599be07971f4f9985a216b 49248 
gobject-introspection_1.76.1-3.debian.tar.xz
 27348971ddf1deba1eda2b16b890cfec842e1dd15c4203e252596ae9c714a57f 9200 
gobject-introspection_1.76.1-3_source.buildinfo
Files:
 6bed4ed7565058cc593e27917c9021bf 3520 devel optional 
gobject-introspection_1.76.1-3.dsc
 74caec51fc379b82f0f52bc23136c480 49248 devel optional 
gobject-introspection_1.76.1-3.debian.tar.xz
 b24c9abd937ffd9427ac36844c82129c 9200 devel optional 
gobject-introspection_1.76.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmS6uP4ACgkQ4FrhR4+B
TE/qOA/+NH5HrXk64SWLLqnxpXXCG6tkOFos/Zk/VcBax3eaLlHJDB1G6DpavNT5
B4WHuGnY4YWhY+vliTJqpqlb/ApVO7rUpi7U1o3OVw7j0W29H4B14cYfWMzxETI4
vxxcoSq08zUy1Um20hFum0BNJiAhGadNTmSR2+wS2P4CylJQ0r2vvhU9Mfwpkacv
1OZbOhttDZ/KxnNs4b2hWuIhm2In7VvHuoowKzy1JsjA/JL/Wadr5GPkCf0V/a2s
PAZID7BKJTk7Yk5sniaWGpPLsIJbv3IqALnTi/wLkt6fyvdxbYKcxoyuOBGaNg7W

Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Boyuan Yang
Hi,

在 2023-07-21星期五的 19:00 +0200,Vincent Lefevre写道:
> On 2023-07-21 17:22:11 +0200, Vincent Lefevre wrote:
> > The best solution would be to fix gnulib on the Debian side, IMHO.
> > I wonder whether other packages are affected too.
> [...]
> > So, if I understand correctly, the fix in gnulib appeared between
> > these two commits. But I don't see which change could affect the
> > result. I could try to investigate.
> 
> This was fixed in the following commit:
> 
> 
> commit d4d8abb39eb02c555f062b1f83ffcfac999c582f
> Author: Bruno Haible 
> Date:   2023-05-05 12:02:49 +0200
> 
>     dirfd: Fix bogus override (regression 2023-04-26).
>     
>     Reported by Bjarni Ingi Gislason  in
>     .
>     
>     * m4/dirfd.m4 (gl_FUNC_DIRFD): Fix mistake in last change.
> 
> diff --git a/ChangeLog b/ChangeLog
> index aaffe12fc1..5f01a52535 100644
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,10 @@
> +2023-05-05  Bruno Haible  
> +
> +   dirfd: Fix bogus override (regression 2023-04-26).
> +   Reported by Bjarni Ingi Gislason  in
> +  
> .
> +   * m4/dirfd.m4 (gl_FUNC_DIRFD): Fix mistake in last change.
> +
>  2023-05-04  Bruno Haible  
>  
>     c32swidth: Add tests.
> diff --git a/m4/dirfd.m4 b/m4/dirfd.m4
> index d1ee2c7f61..7968b1287c 100644
> --- a/m4/dirfd.m4
> +++ b/m4/dirfd.m4
> @@ -1,4 +1,4 @@
> -# serial 27   -*- Autoconf -*-
> +# serial 28   -*- Autoconf -*-
>  
>  dnl Find out how to get the file descriptor associated with an open DIR*.
>  
> @@ -40,10 +40,6 @@ AC_DEFUN([gl_FUNC_DIRFD],
>  HAVE_DIRFD=0
>    else
>  HAVE_DIRFD=1
> -    dnl Replace only if the system declares dirfd already.
> -    if test $ac_cv_have_decl_dirfd = yes; then
> -  REPLACE_DIRFD=1
> -    fi
>  dnl Replace dirfd() on native Windows, to support fdopendir().
>  AC_REQUIRE([gl_DIRENT_DIR])
>  if test $DIR_HAS_FD_MEMBER = 0; then
> 
> 
> In the bug-gnulib discussion:
> 
>   https://lists.gnu.org/archive/html/bug-gnulib/2023-05/msg00046.html
> 
> Bernhard Voelker says:
> > Gnulib commit 3f0950f65abb (2023-04-26) not only lead to build time
> > issues, but also made e.g. coreutils' rm(1) fail:
> > 
> > $ mkdir d && (cd d && seq 40 | xargs touch )
> > 
> > $ rm -rf d
> > rm: traversal failed: d: Operation not supported
> > 
> > I can confirm that this gnulib commit d4d8abb39eb0 fixes the issue again.
> 
> This is the same kind of error.
> 
> But I can see:
> 
> gnulib (20230615+stable-1) unstable; urgency=medium
> 
>   * QA upload.
>   * New upstream snapshot from stable branch stable-202301.
> 
>  -- Boyuan Yang   Tue, 20 Jun 2023 14:58:32 -0400
> 
> I've just rebuilt grep 3.11-1 with "debuild -i -us -uc -b",
> but I still get the same issue with it. I'm wondering what
> "stable branch stable-202301" means.

Looking at https://git.savannah.gnu.org/gitweb/?p=gnulib.git , gnulib
upstream is now providing stable branches that only include important
fixes. In Debian's package, I was tracking the stable-202301 branch.
It is likely that this bugfix was not backported onto it.

Anyway, I will look into it and see whether it affects Stable and Sid.
Since gnulib upstream also opened stable-202307 branch, I will likely
switch gnulib in Sid onto that branch, which should have included the
fix that grep now needs.

BTW: Is grep 3.11-1 using Debian-packaged gnulib anywere? I did not
see a build-dependency in
https://sources.debian.org/src/grep/3.11-1/debian/control/ .

* If grep is indeed using it, please include the build-dep explicitly.

* If not, your current grep issue is unrelated to Debian-packaged gnulib and
you will need further debugging.


Thanks,
Boyuan Yang


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


Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Vincent Lefevre
On 2023-07-21 17:22:11 +0200, Vincent Lefevre wrote:
> The best solution would be to fix gnulib on the Debian side, IMHO.
> I wonder whether other packages are affected too.
[...]
> So, if I understand correctly, the fix in gnulib appeared between
> these two commits. But I don't see which change could affect the
> result. I could try to investigate.

This was fixed in the following commit:


commit d4d8abb39eb02c555f062b1f83ffcfac999c582f
Author: Bruno Haible 
Date:   2023-05-05 12:02:49 +0200

dirfd: Fix bogus override (regression 2023-04-26).

Reported by Bjarni Ingi Gislason  in
.

* m4/dirfd.m4 (gl_FUNC_DIRFD): Fix mistake in last change.

diff --git a/ChangeLog b/ChangeLog
index aaffe12fc1..5f01a52535 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,10 @@
+2023-05-05  Bruno Haible  
+
+   dirfd: Fix bogus override (regression 2023-04-26).
+   Reported by Bjarni Ingi Gislason  in
+   .
+   * m4/dirfd.m4 (gl_FUNC_DIRFD): Fix mistake in last change.
+
 2023-05-04  Bruno Haible  
 
c32swidth: Add tests.
diff --git a/m4/dirfd.m4 b/m4/dirfd.m4
index d1ee2c7f61..7968b1287c 100644
--- a/m4/dirfd.m4
+++ b/m4/dirfd.m4
@@ -1,4 +1,4 @@
-# serial 27   -*- Autoconf -*-
+# serial 28   -*- Autoconf -*-
 
 dnl Find out how to get the file descriptor associated with an open DIR*.
 
@@ -40,10 +40,6 @@ AC_DEFUN([gl_FUNC_DIRFD],
 HAVE_DIRFD=0
   else
 HAVE_DIRFD=1
-dnl Replace only if the system declares dirfd already.
-if test $ac_cv_have_decl_dirfd = yes; then
-  REPLACE_DIRFD=1
-fi
 dnl Replace dirfd() on native Windows, to support fdopendir().
 AC_REQUIRE([gl_DIRENT_DIR])
 if test $DIR_HAS_FD_MEMBER = 0; then


In the bug-gnulib discussion:

  https://lists.gnu.org/archive/html/bug-gnulib/2023-05/msg00046.html

Bernhard Voelker says:
| Gnulib commit 3f0950f65abb (2023-04-26) not only lead to build time
| issues, but also made e.g. coreutils' rm(1) fail:
|
| $ mkdir d && (cd d && seq 40 | xargs touch )
|
| $ rm -rf d
| rm: traversal failed: d: Operation not supported
|
| I can confirm that this gnulib commit d4d8abb39eb0 fixes the issue again.

This is the same kind of error.

But I can see:

gnulib (20230615+stable-1) unstable; urgency=medium

  * QA upload.
  * New upstream snapshot from stable branch stable-202301.

 -- Boyuan Yang   Tue, 20 Jun 2023 14:58:32 -0400

I've just rebuilt grep 3.11-1 with "debuild -i -us -uc -b",
but I still get the same issue with it. I'm wondering what
"stable branch stable-202301" means.

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



Bug#1039714: marked as pending in gobject-introspection

2023-07-21 Thread Simon McVittie
Control: tag -1 pending

Hello,

Bug #1039714 in gobject-introspection 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/gnome-team/gobject-introspection/-/commit/250937bbdf890847a08747d8d8d42fa506ae90c9


dh_girepository: Discover more symbols in GIR files

dh_girepository creates and compiles a dummy C library that aims to
refer to all the same symbols that are mentioned in the GIR XML, so that
running dpkg-shlibdeps against that library will generate the union of
all the dependencies that would be necessary to provide all the symbols
that a GObject-Introspection binding could get from the typelib. It does
that by parsing the GIR XML and looking for XML elements that refer to
a C symbol.

It was already able to recognise *some* XML elements that refer to a C
symbol: ordinary methods, constructors, and ordinary functions. But it
didn't recognise virtual methods, the get_type() functions of various
GObject types, or other functions that are conceptually part of a
type such as copy and free functions. The result was that if a library
*only* contains virtual methods and get_type() functions - for example
libharfbuzz-gobject, which exists solely to provide get_type() functions
for objects in libharfbuzz - then no dependency on that library would
be generated, leading to ${gir:Depends} being incomplete.

[smcv: Add commit message]
Closes: #1039714


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1039714



Processed: Bug#1039714 marked as pending in gobject-introspection

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1039714 [gobject-introspection] gobject-introspection: dh_girepository 
does not fetch all symbols from GIR files
Added tag(s) pending.

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



Bug#1041644: smuxi: FTBFS (source pkg): cli-common-dev missing

2023-07-21 Thread Bastian Germann

I am uploading a NMU to fix this. The debdiff is attached.
As I am also including the latest git change and dropping two dependencies, I 
am delaying by 10 days.diff -Nru smuxi-1.1/debian/changelog smuxi-1.1/debian/changelog
--- smuxi-1.1/debian/changelog  2021-02-12 18:54:21.0 +0100
+++ smuxi-1.1/debian/changelog  2023-07-21 18:06:31.0 +0200
@@ -1,3 +1,14 @@
+smuxi (1.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Drop notify and gtkspell (part of #967750)
+  * Move cli-common-dev to Build-Depends (Closes: #1041644)
+
+  [ Debian Janitor ]
+  * Remove constraints unnecessary since buster
+
+ -- Bastian Germann   Fri, 21 Jul 2023 18:06:31 +0200
+
 smuxi (1.1-1) unstable; urgency=low
 
   * The "From Hong Kong with Love" upload
diff -Nru smuxi-1.1/debian/control smuxi-1.1/debian/control
--- smuxi-1.1/debian/control2021-02-12 18:54:21.0 +0100
+++ smuxi-1.1/debian/control2023-07-21 18:06:31.0 +0200
@@ -7,31 +7,29 @@
 Build-Depends:
  debhelper (>= 7.0.50),
  dh-autoreconf,
+ cli-common-dev,
 Build-Depends-Indep:
  autoconf,
  automake,
  autopoint,
  autotools-dev,
- cli-common-dev (>= 0.5.7),
  gettext,
  gtk-sharp2-gapi,
  intltool,
  libdbus-glib2.0-cil-dev | libdbus-glib1.0-cil-dev | 
libndesk-dbus-glib1.0-cil-dev,
  libdbus2.0-cil-dev | libdbus1.0-cil-dev | libndesk-dbus1.0-cil-dev,
  libgio2.0-cil-dev | libglib2.0-dev,
- libglade2.0-cil-dev (>= 2.8),
- libglib2.0-cil-dev (>= 2.8),
- libgtk2.0-cil-dev (>= 2.8),
- libgtkspell-dev (>= 2.0.9),
+ libglade2.0-cil-dev,
+ libglib2.0-cil-dev,
+ libgtk2.0-cil-dev,
  liblog4net-cil-dev,
  libnunit-cil-dev,
  libmessagingmenu-cil-dev,
- libnini-cil-dev (>= 1.1),
- libnotify-cil-dev,
+ libnini-cil-dev,
  lsb-release,
- mono-devel (>= 2.6),
+ mono-devel,
  mono-runtime-boehm,
- mono-xbuild (>= 2.6),
+ mono-xbuild,
  pkg-config,
  tzdata,
 Standards-Version: 3.9.8
@@ -64,7 +62,6 @@
 Package: smuxi-engine
 Architecture: all
 Replaces:
- smuxi (<< 0.5.25),
  smuxi-engine-irc (<< 0.8.10.2),
  smuxi-engine-twitter (<< 0.8.10.2),
  smuxi-engine-xmpp (<< 0.8.10.2),
@@ -114,7 +111,6 @@
 Package: smuxi-frontend-gnome
 Architecture: all
 Replaces:
- smuxi (<< 0.5.25),
  smuxi-frontend-gnome-irc (<< 0.8.10.2),
 Breaks:
  smuxi-frontend-gnome-irc (<< 0.8.10.2),
diff -Nru smuxi-1.1/debian/rules smuxi-1.1/debian/rules
--- smuxi-1.1/debian/rules  2021-02-12 18:54:21.0 +0100
+++ smuxi-1.1/debian/rules  2023-07-21 18:02:48.0 +0200
@@ -14,8 +14,6 @@
--enable-engine-xmpp \
--enable-frontend-gnome \
--disable-frontend-stfl \
-   --with-notify \
-   --with-gtkspell \
--with-db4o=included \
GMCS=/usr/bin/mono-csc MCS=/usr/bin/mono-csc
 


Processed: severity

2023-07-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1041644 serious
Bug #1041644 [src:smuxi] smuxi: FTBFS (source pkg): cli-common-dev missing
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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



Bug#1037823: marked as done (pythran: ftbfs with GCC-13)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 16:20:20 +
with message-id 
and subject line Bug#1037823: fixed in pythran 0.11.0+ds-8
has caused the Debian Bug report #1037823,
regarding pythran: ftbfs with GCC-13
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.)


-- 
1037823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pythran
Version: 0.11.0+ds-7
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/pythran_0.11.0+ds-7_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
FAILED pythran/tests/test_base.py::TestBase::test_pow - distutils.errors.Comp...
FAILED pythran/tests/test_base.py::TestBase::test_pow_op0 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_pow_op1 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_pow_op2 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_print - distutils.errors.Co...
FAILED pythran/tests/test_base.py::TestBase::test_print_tuple - distutils.err...
FAILED pythran/tests/test_base.py::TestBase::test_raise - distutils.errors.Co...
FAILED pythran/tests/test_base.py::TestBase::test_range1 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range2 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range3 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range4 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range5 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range6 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range7 - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_range_negative_step - distu...
FAILED pythran/tests/test_base.py::TestBase::test_raw_set - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_recursion1 - distutils.erro...
FAILED pythran/tests/test_base.py::TestBase::test_recursion2 - distutils.erro...
FAILED pythran/tests/test_base.py::TestBase::test_recursive_attr - distutils
FAILED pythran/tests/test_base.py::TestBase::test_reduce - distutils.errors.C...
FAILED pythran/tests/test_base.py::TestBase::test_return_empty_list - distuti...
FAILED pythran/tests/test_base.py::TestBase::test_return_set - distutils.erro...
FAILED pythran/tests/test_base.py::TestBase::test_reversed - distutils.errors...
FAILED pythran/tests/test_base.py::TestBase::test_reversed_range_negative_step
FAILED pythran/tests/test_base.py::TestBase::test_reversed_slice - distutils
FAILED pythran/tests/test_base.py::TestBase::test_round - distutils.errors.Co...
FAILED pythran/tests/test_base.py::TestBase::test_rrange1 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange2 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange3 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange4 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange5 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange6 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_rrange7 - distutils.errors
FAILED pythran/tests/test_base.py::TestBase::test_set - distutils.errors.Comp...
FAILED pythran/tests/test_base.py::TestBase::test_set_comprehension - distuti...
FAILED pythran/tests/test_base.py::TestBase::test_shadow_parameters - 

Bug#1033853: marked as done (r-bioc-megadepth: autopkgtest regression: different output)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 16:20:37 +
with message-id 
and subject line Bug#1033853: fixed in r-bioc-megadepth 1.10.0+ds-1
has caused the Debian Bug report #1033853,
regarding r-bioc-megadepth: autopkgtest regression: different output
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.)


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

Source: r-bioc-megadepth
Version: 1.8.0+ds-1
Severity: serious
Control: tags -1 bookworm-ignore
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails in testing 
since March 2023. Can you please investigate the situation and fix it? I 
copied some of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. [Release Team member hat on] Because 
we're currently in the hard freeze for bookworm, I have marked this bug 
as bookworm-ignore. Targeted fixes are still welcome.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-megadepth/32560589/log.gz

══ Failed tests 

── Failure ('test-megadepth_main_tests.R:74'): test bigwig2mean on 
remote bw ───
readLines(file.path(tempdir(), "bw2.remote.mean.annotation.tsv")) 
(`actual`) not equal to 
readLines("https://raw.githubusercontent.com/ChristopherWilks/megadepth/master/tests/testbw2.bed.mean;) 
(`expected`).


 actual | expected
- "chr10\t0\t10\t0.00"   [1]
- "chr10\t8756697\t8756762\t15.85"   [2]
- "chr10\t4359156\t4359188\t3.00"[3]
- "GL000219.1\t168500\t168620\t1.26" [4]

[ FAIL 1 | WARN 1 | SKIP 0 | PASS 129 ]


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: r-bioc-megadepth
Source-Version: 1.10.0+ds-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
r-bioc-megadepth, 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 1033...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-megadepth 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: Fri, 21 Jul 2023 17:57:52 +0200
Source: r-bioc-megadepth
Architecture: source
Version: 1.10.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1033853
Changes:
 r-bioc-megadepth (1.10.0+ds-1) unstable; urgency=medium
 .
   * Team upload.
   * Rebuild against latest r-base
 Closes: #1033853
   * Standards-Version: 4.6.2 (routine-update)
Checksums-Sha1:
 4d35e31903a18aa02225b205964cc306d0759510 2257 r-bioc-megadepth_1.10.0+ds-1.dsc
 40fafc5ea554fd74d34cb3161f8ee87c708f171e 46484 
r-bioc-megadepth_1.10.0+ds.orig.tar.xz
 cf33c8e47093f89f4bf5d6e5f3a922e4b8c3a000 5856 
r-bioc-megadepth_1.10.0+ds-1.debian.tar.xz
 1bd3936ca195935b7117eca797c75673332c8fb6 23056 
r-bioc-megadepth_1.10.0+ds-1_source.buildinfo
Checksums-Sha256:
 0f13d0bb5bdd3c22d16600ec3271cb5f0565d717612ef90d79f110f4242767b8 2257 
r-bioc-megadepth_1.10.0+ds-1.dsc
 496f36bb62567cbba84c3429c53117b22f53b7128517a549c8d9dc6d061badfa 46484 
r-bioc-megadepth_1.10.0+ds.orig.tar.xz
 61cfcd2cb8955655a09ffd0fe7f060c2dded944c6e494d5df154b9590dc48159 5856 
r-bioc-megadepth_1.10.0+ds-1.debian.tar.xz
 276d933031154888dcab9ef98d16f813c483e1ba1b7d7a54b6f6b439880421be 23056 
r-bioc-megadepth_1.10.0+ds-1_source.buildinfo
Files:
 c12c6cd9f195f5676f62fdb76e0ba800 2257 gnu-r optional 
r-bioc-megadepth_1.10.0+ds-1.dsc
 b91c2a9207dd673e613aad6da3a5b107 46484 gnu-r optional 
r-bioc-megadepth_1.10.0+ds.orig.tar.xz
 1250de599eea59fb4eddc030154d02ff 5856 gnu-r optional 
r-bioc-megadepth_1.10.0+ds-1.debian.tar.xz
 e8f52b6e3a55c4dea5be64a7c7dfdad9 

Bug#1037823: marked as pending in pythran

2023-07-21 Thread Drew Parsons
Control: tag -1 pending

Hello,

Bug #1037823 in pythran 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/python-team/packages/pythran/-/commit/3dedbc4004f9321559311ad246d77ddccebbbcb3


add debian patch gcc13_PR2029.patch

applies upstream PR#2029 to fix build with gcc-13.

Closes: #1037823.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037823



Processed: Bug#1037823 marked as pending in pythran

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1037823 [src:pythran] pythran: ftbfs with GCC-13
Added tag(s) pending.

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



Bug#1041640: RM: sdb -- RoQA; unpackaged upstream versions; unmaintained dependency; low popcon

2023-07-21 Thread Bastian Germann

Source: sdb
Severity: serious

Please consider removing sdb. It depends on the unmaintained nrefactory.
If nobody reacts within a month I am going to file the RM bug.



Bug#1041639: RM: mono-debugger-libs -- RoQA; unpackaged upstream changes; unmaintained dependency

2023-07-21 Thread Bastian Germann

Source: mono-debugger-libs
Severity: serious

Please consider removing mono-debugger-libs. It depends on the unmaintained 
nrefactory.
If nobody reacts within a month I am going to file the RM bug.



Bug#1040334: facet-analyser - build-depends on conflicting packages

2023-07-21 Thread Roland Mas

Le 04/07/2023 à 17:53, Steven Robbins a écrit :

On Tuesday, July 4, 2023 10:03:27 A.M. CDT Peter Green wrote:

Package: facet-analyser
Version: 0.0~git20221121142040.6be10b8+ds1-3
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same
release" User: debian...@lists.debian.org
Usertags: edos-uninstallable
x-debbugs-cc: s...@debian.org

facet-analyser build-depends on both python3-paraview and
libinsighttoolkit5-dev

unfortunately, libinsighttoolkit5-dev recently added a dependency on
libvtk9-dev which depends on python3-vtk9 which conflicts with
python3-paraview.

I am not familiar enough with the packages in question to know what the
most appropriate way to untangle this is.

That's curious.  I don't know either.  My questions are: why do python3-vtk9
and python3-paraview conflict, and could the issue be solved another way?


I think it's because python3-paraview uses its own vtk9, see #982601 and 
#654839.


Roland.



Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Vincent Lefevre
On 2023-07-21 11:02:10 -0400, Boyuan Yang wrote:
> Debian gnulib package maintainer here. I briefly checked grep source code,
> and it seems that grep is using the bundled gnulib and not using the packaged
> gnulib. Not 100% sure.
> 
> Whether to use the bundled gnulib is up to the packager's decision. Anyway,
> let me know if I could help.

The best solution would be to fix gnulib on the Debian side, IMHO.
I wonder whether other packages are affected too.

BTW, the grep commit that updated the bundled gnulib:

diff --git a/gnulib b/gnulib
index c2a5953..2e671b8 16
--- a/gnulib
+++ b/gnulib
@@ -1 +1 @@
-Subproject commit c2a5953f179814dd0f4b7e627aae9a009181ed6a
+Subproject commit 2e671b84c8ec5426aee37f4a6656d531929ee430

So, if I understand correctly, the fix in gnulib appeared between
these two commits. But I don't see which change could affect the
result. I could try to investigate.

Knowing the real problem would allow one to make sure that this
is not a bug that is temporarily hidden.

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



Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH

2023-07-21 Thread Sebastiaan Couwenberg

Changes between bookworm and sid:

cmake 3.25.1:

 ``Python_SITELIB``
   Third-party platform independent installation directory.

   Information returned by

``distutils.sysconfig.get_python_lib(plat_specific=False,standard_lib=False)``
   or else ``sysconfig.get_path('purelib')``.
 ``Python_SITEARCH``
   Third-party platform dependent installation directory.

   Information returned by

``distutils.sysconfig.get_python_lib(plat_specific=True,standard_lib=False)``
   or else ``sysconfig.get_path('platlib')``.

cmake 3.27.0:

 ``Python_SITELIB``
   Third-party platform independent installation directory.

   Information returned by ``sysconfig.get_path('purelib')``.
 ``Python_SITEARCH``
   Third-party platform dependent installation directory.

   Information returned by ``sysconfig.get_path('platlib')``.

On bookworm distutils is still used which returns:

 >>> distutils.sysconfig.get_python_lib(
 plat_specific=False,
 standard_lib=False,
 )
 '/usr/lib/python3/dist-packages'

On sid sysconfig is used which results:

 >>> sysconfig.get_path('platlib')
 '/usr/local/lib/python3.11/dist-packages'

To get the right path for the Debian python3 interpreter,
you need to add 'deb_system':

 >>> sysconfig.get_path('platlib', 'deb_system')
 '/usr/lib/python3/dist-packages'

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#1041633: cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH

2023-07-21 Thread Bas Couwenberg
Source: cmake
Version: 3.27.0-1
Severity: serious
Tags: upstream
Justification: makes the package in question unusable or mostly so

Dear Maintainer,

FindPython.cmake in 3.27 returns the wrong Python_SITEARCH path which breaks 
the qgis build:

 -- Python site-packages: /usr/local/lib/python3.11/dist-packages

This was:

 -- Python site-packages: /usr/lib/python3/dist-packages

Kind Regards,

Bas



Bug#1037680: marked as done (gnss-sdr: ftbfs with GCC-13)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 15:04:49 +
with message-id 
and subject line Bug#1037680: fixed in gnss-sdr 0.0.18-2
has caused the Debian Bug report #1037680,
regarding gnss-sdr: ftbfs with GCC-13
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.)


-- 
1037680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnss-sdr
Version: 0.0.17-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/gnss-sdr_0.0.17-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
[ 84%] Linking CXX static library libtracking_gr_blocks.a
cd 
/<>/obj-x86_64-linux-gnu/src/algorithms/tracking/gnuradio_blocks 
&& /usr/bin/cmake -P CMakeFiles/tracking_gr_blocks.dir/cmake_clean_target.cmake
cd 
/<>/obj-x86_64-linux-gnu/src/algorithms/tracking/gnuradio_blocks 
&& /usr/bin/cmake -E cmake_link_script 
CMakeFiles/tracking_gr_blocks.dir/link.txt --verbose=1
/usr/bin/ar qc libtracking_gr_blocks.a 
CMakeFiles/tracking_gr_blocks.dir/dll_pll_veml_tracking.cc.o 
CMakeFiles/tracking_gr_blocks.dir/galileo_e1_tcp_connector_tracking_cc.cc.o 
CMakeFiles/tracking_gr_blocks.dir/glonass_l1_ca_dll_pll_c_aid_tracking_cc.cc.o 
CMakeFiles/tracking_gr_blocks.dir/glonass_l1_ca_dll_pll_c_aid_tracking_sc.cc.o 
CMakeFiles/tracking_gr_blocks.dir/glonass_l1_ca_dll_pll_tracking_cc.cc.o 
CMakeFiles/tracking_gr_blocks.dir/glonass_l2_ca_dll_pll_c_aid_tracking_cc.cc.o 
CMakeFiles/tracking_gr_blocks.dir/glonass_l2_ca_dll_pll_c_aid_tracking_sc.cc.o 
CMakeFiles/tracking_gr_blocks.dir/glonass_l2_ca_dll_pll_tracking_cc.cc.o 
CMakeFiles/tracking_gr_blocks.dir/gps_l1_ca_kf_tracking_cc.cc.o 
CMakeFiles/tracking_gr_blocks.dir/gps_l1_ca_tcp_connector_tracking_cc.cc.o 
CMakeFiles/tracking_gr_blocks.dir/kf_vtl_tracking.cc.o
[ 84%] Building CXX object 
src/algorithms/signal_source/libs/CMakeFiles/signal_source_libs.dir/fpga_dynamic_bit_selection.cc.o
cd /<>/obj-x86_64-linux-gnu/src/algorithms/signal_source/libs && 
/usr/bin/c++ -DARMA_NO_BOUND_CHECKING=1 -DBOOST_ALL_NO_LIB 
-DBOOST_DATE_TIME_DYN_LINK -DBOOST_SERIALIZATION_DYN_LINK 
-DGNSSSDR_INSTALL_DIR=\"/usr\" -DGNURADIO_FFT_USES_TEMPLATES=1 
-DGNURADIO_USES_STD_POINTERS=1 -DHAS_STD_FILESYSTEM=1 
-DLIBAD9361_VERSION_GREATER_THAN_01=1 -DSPDLOG_FMT_EXTERNAL=1 
-DUSE_BOOST_ASIO_IO_CONTEXT=1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-D_LARGE_FILES -I/<>/src/core/receiver 
-I/<>/src/core/interfaces -I/<>/src/algorithms/libs 
-I/<>/src/core/libs -I/<>/src/core/libs/supl 
-I/<>/src/core/libs/supl/asn-supl 
-I/<>/src/core/libs/supl/asn-rrlp 
-I/<>/src/core/system_parameters 
-I/<>/src/algorithms/PVT/libs 
-I/<>/src/algorithms/libs/rtklib 
-I/<>/src/algorithms/libs/gsl/include -isystem /usr/include/glog 
-isystem /<>/obj-x86_64-linux-
 gnu/src/core/libs -isystem 
/<>/obj-x86_64-linux-gnu/src/algorithms/PVT/libs -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fvisibility=hidden 
-fvisibility-inlines-hidden -Wall -Wextra -std=c++17 -MD -MT 
src/algorithms/signal_source/libs/CMakeFiles/signal_source_libs.dir/fpga_dynamic_bit_selection.cc.o
 -MF CMakeFiles/signal_source_libs.dir/fpga_dynamic_bit_selection.cc.o.d -o 
CMakeFiles/signal_source_libs.dir/fpga_dynamic_bit_selection.cc.o -c 
/<>/src/algorithms/signal_source/libs/fpga_dynamic_bit_selection.cc
/usr/bin/ranlib libtracking_gr_blocks.a
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[ 84%] Built target 

Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Boyuan Yang
Hi,

On Fri, 21 Jul 2023 10:39:54 +0200 Vincent Lefevre  wrote:
> Control: severity -1 grave
> Control: tags -1 - moreinfo
> Control: retitle -1 grep -r on 10+ files fails with "Operation not
supported"
> 
> On 2023-07-20 23:43:45 -0300, Santiago Ruano Rincón wrote:
> > El 21/07/23 a las 04:06, Vincent Lefevre escribió:
> > > On 2023-07-21 03:30:12 +0200, Vincent Lefevre wrote:
> > > > There is a major regression in grep 3.11-1: I now get an error
> > > > 
> > > > cventin:~/Mail> grep -r xxxyyyzzz oldarc
> > > > grep: oldarc/cur: Operation not supported
> > > 
> > > And no such issue with grep from the upstream git.
> > 
> > How are you compiling it?
> 
> $ ./bootstrap
> $ ./configure --prefix=$HOME/opt/grep
> $ make
> $ make install
> 
> > My intuition is this comes from gnulib.
> 
> Yes, as in my next message, I said that the error disappeared
> with the commit that updated gnulib (and did nothing else).
> 
> > But a reproducer is needed to confirm.
> > 
> > Tagging with moreinfo, and downgrading the severity since I cannot
> > reproduce it myself:
> [...]
> > Please, feel free to bump the severity back again if you are able to
> > find out a way to reproduce it.
> 
> One needs at least 10 files in the directory (9 is not enough).
> With 10 empty files:
> 
> $ mkdir test-dir && for i in `seq 10` ; do : > test-dir/$i ; done
> $ grep -r x test-dir
> grep: test-dir: Operation not supported

Debian gnulib package maintainer here. I briefly checked grep source code,
and it seems that grep is using the bundled gnulib and not using the packaged
gnulib. Not 100% sure.

Whether to use the bundled gnulib is up to the packager's decision. Anyway,
let me know if I could help.

Thanks,
Boyuan Yang


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


Bug#1041270: dynarmic: broke ABI without SONAME bump

2023-07-21 Thread Andrea Pappacoda
> Hi Sebastian, thanks for your report. I've uploaded a new version with 
> a possible fix on Mentors, you can find it at 
> . I've also attached a 
> debdiff for your convenience.
> 
> Feel free to upload it to unstable if you find this solution 
> reasonable. Since this is only a soname change, without any actual 
> library change, I believe that uploading to experimental first is 
> unnecessary.
> 
> If it doesn't look right to you, I'll be happy to hear your feedback :)

My previous solution was broken since it introduced a new package with
the same contents as the older libdynarmic6 package, causing an unpack
error. Luckly upstream has merged my patch and tagged a new release,
so I simply updated to the new upstream version, getting rid of the file
conflict and bumping the ABI.

I don't have access to my private OpenPGP keys right now, so I can't upload
the new release on Mentors, but I'll attach a debdiff nonetheless containing
the 6.5.0-1 release. You can also find it on Salsa at
.

dynarmic_6.5.0+ds-1.debdiff
Description: Binary data


Bug#1039633: marked as done (r-bioc-bioccheck: autopkgtest failure with r-base (4.3.1-1))

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 14:40:51 +
with message-id 
and subject line Bug#1039633: fixed in r-bioc-bioccheck 1.36.1+dfsg-1
has caused the Debian Bug report #1039633,
regarding r-bioc-bioccheck: autopkgtest failure with r-base (4.3.1-1)
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.)


-- 
1039633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-bioccheck
Version: 1.34.2+dfsg-1
Severity: serious
Justification: autopkgtest failure

Dear Maintainer,

The autopkgtest of your package fails with r-base (4.3.1-1):

 209s RUNIT TEST PROTOCOL -- Tue Jun 27 15:46:32 2023 
 209s *** 
 209s Number of test functions: 48 
 209s Number of deactivated test functions: 3 
 209s Number of errors: 0 
 209s Number of failures: 1 
 209s 
 209s  
 209s 1 Test Suite : 
 209s BiocCheck RUnit Tests - 48 test functions, 0 errors, 1 failure
 209s FAILURE in test_checkBBScompatibility: Error in 
checkTrue(.BiocCheck$getNum("note") == 1, "citation produces note") : 
 209s   Test not TRUE
 209s citation produces note
 209s DEACTIVATED test_checkExportsAreDocumented: Skip this test, it requires a 
package non-available in Debian
 209s DEACTIVATED test_checkUsageOfDont: Skip this test, it requires a package 
non-available in Debian
 209s DEACTIVATED test_remotesUsage: Skip this test, it requires a package 
non-available in Debian
 209s 
 209s Test files with failing tests
 209s 
 209stest_BiocCheck.R 
 209s  test_checkBBScompatibility 
 209s  test_checkExportsAreDocumented 
 209s  test_checkUsageOfDont 
 209s  test_remotesUsage 
 209s 
 209s 
 209s Error in BiocGenerics:::testPackage("BiocCheck") : 
 209s   unit tests failed for package BiocCheck

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-bioccheck/34907238/log.gz

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Source: r-bioc-bioccheck
Source-Version: 1.36.1+dfsg-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
r-bioc-bioccheck, 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 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-bioccheck 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: Fri, 21 Jul 2023 15:55:25 +0200
Source: r-bioc-bioccheck
Architecture: source
Version: 1.36.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1039633
Changes:
 r-bioc-bioccheck (1.36.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
   * Rebuild against latest version of r-base
 Closes: #1039633
   * New upstream version
   * Reduce piuparts noise in transitions
   * Standards-Version: 4.6.2 (routine-update)
   * dh-update-R to update Build-Depends (routine-update)
Checksums-Sha1:
 ad21caf89cb05fd5a8fdb0c66c7a33cb4fc321c0 2260 
r-bioc-bioccheck_1.36.1+dfsg-1.dsc
 ac0ef1bfee3e4e221644e5ce65eca3bd126d21a8 3987972 
r-bioc-bioccheck_1.36.1+dfsg.orig.tar.xz
 acaffdfe329def743fe79b9fe11a00c4a491b001 5844 
r-bioc-bioccheck_1.36.1+dfsg-1.debian.tar.xz
 b8a6376dd3ae3fccd940aef598c2b15ff3006a57 12574 
r-bioc-bioccheck_1.36.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 24fe61e4795fbde7ff318c19bc1dc346d9cded1f876b5a06314f7a8aeff91f3b 2260 
r-bioc-bioccheck_1.36.1+dfsg-1.dsc
 1b9a70c5284a7388c1a8f5722f3b476676e6128563de831fb20479a274fbe4ec 3987972 
r-bioc-bioccheck_1.36.1+dfsg.orig.tar.xz
 5b6b6bcc1244f5053355d95099105349f644a4acb4ce67f28b8dd78aa95029bc 5844 
r-bioc-bioccheck_1.36.1+dfsg-1.debian.tar.xz
 8bbda5e30ba9ebf7e84dc3752c438d6710d6e338640c98cd20275252704f762f 12574 
r-bioc-bioccheck_1.36.1+dfsg-1_amd64.buildinfo
Files:
 36df81c0b18a3e0e061bb9d7d2159b4a 2260 gnu-r optional 
r-bioc-bioccheck_1.36.1+dfsg-1.dsc
 863d7df8a937b56566ba4df1f8ba56ad 3987972 gnu-r optional 
r-bioc-bioccheck_1.36.1+dfsg.orig.tar.xz
 d5715b508c7c3fa66888ba5f691d008c 5844 gnu-r optional 
r-bioc-bioccheck_1.36.1+dfsg-1.debian.tar.xz
 66e9d27337935e058d9fadcd3d4fc3c1 12574 gnu-r 

Bug#1041529: marked as done (gqrx-sdr: unsatisfiable build dependencies)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 14:39:30 +
with message-id 
and subject line Bug#1041529: fixed in gqrx-sdr 2.16-1
has caused the Debian Bug report #1041529,
regarding gqrx-sdr: unsatisfiable build dependencies
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.)


-- 
1041529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gqrx-sdr
Version: 2.15.9-1
Severity: serious
Tags: ftbfs
Justification: ftbfs

Dear Maintainer,

gqrx-sdr currently fails to build from source due to
unsatisfiable build dependencies:

# apt-get build-dep gqrx-sdr
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 builddeps:gqrx-sdr : Depends: libvolk2-dev but it is not installable
E: Unable to correct problems, you have held broken packages.

Upon further investigation, this looks to be caused by the
collision between gnuradio-dev and libvolk2-dev, the former
depending on libvolk-dev (unversioned) which in turn conflicts
with libvolk2-dev:

# apt-get install --dry-run gnuradio-dev libvolk2-dev 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
libvolk2-dev is already the newest version (2.5.2-3).
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libvolk-dev : Breaks: libvolk2-dev but 2.5.2-3 is to be installed
 libvolk2-dev : Breaks: libvolk-dev but 3.0.0-2 is to be installed
E: Unable to correct problems, you have held broken packages.

Removing the build dependency on libvolk2-dev and relying on the
libvolk-dev being pulled by gnuradio-dev looks to do the trick
on my end.

In hope this helps,
Have a nice day,  :)
Étienne.

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

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

-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/7, please excuse my verbosity
   `-on air: Kingcrow - Right Before


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: gqrx-sdr
Source-Version: 2.16-1
Done: A. Maitland Bottoms 

We believe that the bug you reported is fixed in the latest version of
gqrx-sdr, 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 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
A. Maitland Bottoms  (supplier of updated gqrx-sdr 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: Sun, 30 Apr 2023 11:28:26 -0400
Source: gqrx-sdr
Architecture: source
Version: 2.16-1
Distribution: unstable
Urgency: medium
Maintainer: A. Maitland Bottoms 
Changed-By: A. Maitland Bottoms 
Closes: 1041529
Changes:
 gqrx-sdr (2.16-1) unstable; urgency=medium
 .
   * New upstream release.
   * Adjust volk dependencies. (Closes: #1041529)
Checksums-Sha1:
 21485aac7b061fdef68faa08de9dc7b485357b5f 2044 gqrx-sdr_2.16-1.dsc
 

Bug#1037649: marked as done (fenics-dolfinx: ftbfs with GCC-13)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 14:38:48 +
with message-id 
and subject line Bug#1037649: fixed in fenics-dolfinx 1:0.6.0-5
has caused the Debian Bug report #1037649,
regarding fenics-dolfinx: ftbfs with GCC-13
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.)


-- 
1037649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fenics-dolfinx
Version: 1:0.5.2-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/fenics-dolfinx_0.5.2-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
   42 |   Table timings(std::set type);
  | ^~~
/<>/cpp/dolfinx/common/TimeLogger.h:49:45: error: ‘TimingType’ was 
not declared in this scope
   49 |   void list_timings(MPI_Comm comm, std::set type,
  | ^~
/<>/cpp/dolfinx/common/TimeLogger.h:49:55: error: template 
argument 1 is invalid
   49 |   void list_timings(MPI_Comm comm, std::set type,
  |   ^
/<>/cpp/dolfinx/common/TimeLogger.h:49:55: error: template 
argument 2 is invalid
/<>/cpp/dolfinx/common/TimeLogger.h:49:55: error: template 
argument 3 is invalid
/<>/cpp/dolfinx/common/TimeLogger.h:49:36: error: ‘std::type’ has 
not been declared
   49 |   void list_timings(MPI_Comm comm, std::set type,
  |^~~
make[4]: *** [dolfinx/CMakeFiles/dolfinx.dir/build.make:163: 
dolfinx/CMakeFiles/dolfinx.dir/common/Timer.cpp.o] Error 1
make[4]: *** Waiting for unfinished jobs
/<>/cpp/dolfinx/common/TimeLogger.cpp:42:55: error: ‘TimingType’ 
was not declared in this scope
   42 | void TimeLogger::list_timings(MPI_Comm comm, std::set type,
  |   ^~
/<>/cpp/dolfinx/common/TimeLogger.cpp:42:65: error: template 
argument 1 is invalid
   42 | void TimeLogger::list_timings(MPI_Comm comm, std::set type,
  | ^
/<>/cpp/dolfinx/common/TimeLogger.cpp:42:65: error: template 
argument 2 is invalid
/<>/cpp/dolfinx/common/TimeLogger.cpp:42:65: error: template 
argument 3 is invalid
/<>/cpp/dolfinx/common/TimeLogger.cpp:55:36: error: ‘TimingType’ 
was not declared in this scope
   55 | Table TimeLogger::timings(std::set type)
  |^~
/<>/cpp/dolfinx/common/TimeLogger.cpp:55:46: error: template 
argument 1 is invalid
   55 | Table TimeLogger::timings(std::set type)
  |  ^
/<>/cpp/dolfinx/common/TimeLogger.cpp:55:46: error: template 
argument 2 is invalid
/<>/cpp/dolfinx/common/TimeLogger.cpp:55:46: error: template 
argument 3 is invalid
/<>/cpp/dolfinx/common/TimeLogger.cpp: In member function 
‘dolfinx::Table dolfinx::common::TimeLogger::timings(int)’:
/<>/cpp/dolfinx/common/TimeLogger.cpp:60:25: error: request for 
member ‘find’ in ‘type’, which is of non-class type ‘int’
   60 |   bool time_wall = type.find(TimingType::wall) != type.end();
  | ^~~~
/<>/cpp/dolfinx/common/TimeLogger.cpp:60:30: error: ‘TimingType’ 
has not been declared
   60 |   bool time_wall = type.find(TimingType::wall) != type.end();
  |  ^~
/<>/cpp/dolfinx/common/TimeLogger.cpp:60:56: error: request for 
member ‘end’ in ‘type’, which is of non-class type ‘int’
   60 |   bool 

Bug#1037854: scipy: ftbfs with GCC-13

2023-07-21 Thread Drew Parsons
Source: scipy
Followup-For: Bug #1037854

The errors in the build log refer to pythran, not scipy.



Bug#1041388: libclang-rt-17-dev: ships /usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a, already in libclang-rt-17-dev-wasm*

2023-07-21 Thread Sylvestre Ledru

Hello

This is because of:
https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/merge_requests/106/diffs

let me fix it :)

Cheers
S

Le 18/07/2023 à 11:27, Andreas Beckmann a écrit :

Package: libclang-rt-17-dev
Version: 1:17~++20230709044550+c54ff51be9c1-1~exp1
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.

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

   Selecting previously unselected package libclang-rt-17-dev:amd64.
   Preparing to unpack 
.../libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb ...
   Unpacking libclang-rt-17-dev:amd64 
(1:17~++20230709044550+c54ff51be9c1-1~exp1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb
 (--unpack):
trying to overwrite 
'/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm64.a', which 
is also in package libclang-rt-17-dev-wasm64 
1:17~++20230709044550+c54ff51be9c1-1~exp1
   Errors were encountered while processing:

/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb

   Selecting previously unselected package libclang-rt-17-dev:amd64.
   Preparing to unpack 
.../libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb ...
   Unpacking libclang-rt-17-dev:amd64 
(1:17~++20230709044550+c54ff51be9c1-1~exp1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb
 (--unpack):
trying to overwrite 
'/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm32.a', which 
is also in package libclang-rt-17-dev-wasm32 
1:17~++20230709044550+c54ff51be9c1-1~exp1
   Errors were encountered while processing:

/var/cache/apt/archives/libclang-rt-17-dev_1%3a17~++20230709044550+c54ff51be9c1-1~exp1_amd64.deb


cheers,

Andreas




Processed: Bug#1037715 marked as pending in libatomicqueue

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1037715 [src:libatomic-queue] libatomic-queue: ftbfs with GCC-13
Added tag(s) pending.

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



Bug#1037715: marked as pending in libatomicqueue

2023-07-21 Thread Étienne Mollier
Control: tag -1 pending

Hello,

Bug #1037715 in libatomicqueue 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/med-team/libatomic-queue/-/commit/bb61075a753d52a90a10e51ca0aa2b8b1cb4f08e


d/rules: build with -Wno-error=array-bounds.

This works around gcc-13 bug [1], also Debian Bug#1041607.

Closes: #1037715

[1]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110764


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037715



Bug#816470: marked as done (apt-show-versions: wrong output for apt-doc)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 13:18:55 +
with message-id 
and subject line Bug#858337: fixed in apt-show-versions 0.22.14
has caused the Debian Bug report #858337,
regarding apt-show-versions: wrong output for apt-doc
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.)


-- 
858337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.22.7
Severity: normal

I currently have the following:

cventin:~> apt-cache show apt-doc
Package: apt-doc
Source: apt
Version: 1.2.4
Installed-Size: 875
Maintainer: APT Development Team 
Architecture: all
Description-en: documentation for APT
 This package contains the user guide and offline guide for various
 APT tools which are provided in a html and a text-only version.
Description-md5: bc2b838ed28e60af95d78926380a3300
Tag: admin::package-management, hardware::storage, hardware::storage:cd,
 made-of::html, protocol::ftp, protocol::http, protocol::ipv6,
 role::documentation, suite::debian, use::downloading, use::searching,
 works-with-format::html, works-with-format::plaintext,
 works-with::software:package
Section: doc
Priority: optional
Filename: pool/main/a/apt/apt-doc_1.2.4_all.deb
Size: 339568
MD5sum: dc6c14dca231226855be65bfd967de52
SHA1: 5d64e55b8271da51e85c0de148a10e0393142735
SHA256: a914b340168ef1b0e79e28289d05746c6b4c4bd131e0e6d6940e478a4d89ced4

Package: apt-doc
Source: apt
Version: 1.2.3
Installed-Size: 875
Maintainer: APT Development Team 
Architecture: all
Description-en: documentation for APT
 This package contains the user guide and offline guide for various
 APT tools which are provided in a html and a text-only version.
Description-md5: bc2b838ed28e60af95d78926380a3300
Tag: admin::package-management, hardware::storage, hardware::storage:cd,
 made-of::html, protocol::ftp, protocol::http, protocol::ipv6,
 role::documentation, suite::debian, use::downloading, use::searching,
 works-with-format::html, works-with-format::plaintext,
 works-with::software:package
Section: doc
Priority: optional
Filename: pool/main/a/apt/apt-doc_1.2.3_all.deb
Size: 339430
MD5sum: 95441fe0771c28c207a1a6c2d0075bbd
SHA1: 3843a48005afee4ee5c07b85b66fdf577f455997
SHA256: 19ef1abcd7c7b88496e800c23c8eaa8cb6b4d8dd0b3d6fd94dab91957a7b8684

Package: apt-doc
Source: apt
Version: 1.0.9.8.2
Installed-Size: 715
Maintainer: APT Development Team 
Architecture: all
Description-en: documentation for APT
 This package contains the user guide and offline guide for various
 APT tools which are provided in a html and a text-only version.
Description-md5: bc2b838ed28e60af95d78926380a3300
Tag: admin::package-management, hardware::storage, hardware::storage:cd,
 made-of::html, protocol::ftp, protocol::http, protocol::ipv6,
 role::documentation, suite::debian, use::downloading, use::searching,
 works-with-format::html, works-with-format::plaintext,
 works-with::software:package
Section: doc
Priority: optional
Filename: pool/main/a/apt/apt-doc_1.0.9.8.2_all.deb
Size: 300756
MD5sum: 007ba24fb15341a1eb6fc770ad1ab90b
SHA1: e698dcd1cd6f18ec9b7d432ecb99d74be9fd701b
SHA256: eff6c23b0465e8e382ecc87d87bba12660121730e49cb5f4c7660d641c57cd33

which should respectively be the unstable, testing and stable
versions. And

cventin:~> apt-get install apt-doc -s
NOTE: This is only a simulation!
  apt-get needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-image-4.1.0-2-amd64 linux-image-4.2.0-1-amd64
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  apt-doc
1 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Inst apt-doc [1.2.3] (1.2.4 Debian:unstable [all])
Conf apt-doc (1.2.4 Debian:unstable [all])

confirming that 1.2.4 is the unstable package. But apt-show-versions
says that it is 1.2.3:

cventin:~> apt-show-versions -a apt-doc
apt-doc:all 1.2.3 install ok installed
apt-doc:all 1.0.9.8.2 stable   ftp.fr.debian.org
No stable-updates version
apt-doc:all 1.2.3 testing  ftp.fr.debian.org
apt-doc:all 1.2.3 unstable ftp.fr.debian.org
No experimental version
apt-doc:all 1.2.3 installed: No available version in archive

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 

Bug#1024765: marked as done (apt-show-versions is confused when versions from different architectures disagree)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 13:18:55 +
with message-id 
and subject line Bug#858337: fixed in apt-show-versions 0.22.14
has caused the Debian Bug report #858337,
regarding apt-show-versions is confused when versions from different 
architectures disagree
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.)


-- 
858337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.22.13+nmu1
Severity: normal

I get

cventin:~> apt-show-versions -a clang-14-doc
clang-14-doc:all 1:14.0.6-8 install ok installed
No stable version
No stable-updates version
clang-14-doc:all 1:14.0.6-2   testing  ftp.debian.org
clang-14-doc:all 1:14.0.6-6   unstable ftp.debian.org
clang-14-doc:all 1:14.0.6-10~exp1 experimental ftp.debian.org
clang-14-doc:all/experimental *manually* upgradeable from 1:14.0.6-8 to 
1:14.0.6-10~exp1

but the current unstable version is 1:14.0.6-8, not 1:14.0.6-6!

On https://tracker.debian.org/pkg/llvm-toolchain-14 one has

  [2022-11-12] Accepted llvm-toolchain-14 1:14.0.6-8 (source) into unstable
  (Sylvestre Ledru)

and on my machine, /usr/share/doc/clang-14-doc/changelog.Debian.gz
starts with

llvm-toolchain-14 (1:14.0.6-8) unstable; urgency=medium
   ^^  

Moreover,
/var/lib/apt/lists/ftp.debian.org_debian_dists_unstable_main_binary-amd64_Packages
contains

Package: clang-14-doc
Source: llvm-toolchain-14
Version: 1:14.0.6-8
[...]

I suspect that apt-show-versions is confused by
/var/lib/apt/lists/ftp.debian.org_debian_dists_unstable_main_binary-i386_Packages,
which contains

Package: clang-14-doc
Source: llvm-toolchain-14
Version: 1:14.0.6-6
[...]

i.e. the unstable version given by apt-show-versions.

I suppose that apt-show-versions should follow the behavior of apt
and aptitude.

Concerning apt:

cventin:~> apt install -s clang-14-doc/unstable
[...]
Selected version '1:14.0.6-8' (Debian:unstable [all]) for 'clang-14-doc'

so it takes the amd64 version, probably because this is the main
architecture on this machine (i386 being a foreign one).

And in /var/log/aptitude, I can see

[UPGRADE] clang-14-doc:amd64 1:14.0.6-7 -> 1:14.0.6-8

mentioning amd64 explicitly.

-- 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)
Foreign Architectures: i386

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

Versions of packages apt-show-versions depends on:
ii  apt  2.5.4
ii  libapt-pkg-perl  0.1.40+b2
ii  perl [libstorable-perl]  5.36.0-4

apt-show-versions recommends no packages.

apt-show-versions suggests no packages.

-- 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: apt-show-versions
Source-Version: 0.22.14
Done: Christoph Martin 

We believe that the bug you reported is fixed in the latest version of
apt-show-versions, 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 858...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated apt-show-versions 
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: Fri, 21 Jul 2023 14:44:39 +0200
Source: apt-show-versions
Architecture: source
Version: 0.22.14
Distribution: unstable
Urgency: medium
Maintainer: Christoph Martin 
Changed-By: Christoph Martin 
Closes: 816470 858337 1024765
Changes:
 apt-show-versions (0.22.14) unstable; urgency=medium
 .
   * fix 

Bug#858337: marked as done (apt-show-versions may show incorrect package version for "Architecture: all" when a foreign arch is enabled)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 13:18:55 +
with message-id 
and subject line Bug#858337: fixed in apt-show-versions 0.22.14
has caused the Debian Bug report #858337,
regarding apt-show-versions may show incorrect package version for 
"Architecture: all" when a foreign arch is enabled
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.)


-- 
858337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.22.7
Severity: important

[Severity important as this can lead the user to install potentially
broken packages.]

On my laptop:

zira:~> apt-show-versions -u | grep manually
fonts-opensymbol:all/experimental *manually* upgradeable from 
2:102.7+LibO5.2.6-1 to 2:102.10+LibO5.3.1-1
libreoffice-common:all/experimental *manually* upgradeable from 1:5.2.6-1 to 
1:5.3.1-1
libreoffice-java-common:all/experimental *manually* upgradeable from 1:5.2.6-1 
to 1:5.3.1-1
libreoffice-librelogo:all/experimental *manually* upgradeable from 1:5.2.6-1 to 
1:5.3.1-1
libreoffice-nlpsolver:all/experimental *manually* upgradeable from 
0.9+LibO5.2.6-1 to 0.9+LibO5.3.1-1
libreoffice-report-builder:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-script-provider-bsh:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-script-provider-js:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-script-provider-python:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-style-galaxy:all/experimental *manually* upgradeable from 1:5.2.6-1 
to 1:5.3.1-1
libreoffice-style-tango:all/experimental *manually* upgradeable from 1:5.2.6-1 
to 1:5.3.1-1
libreoffice-wiki-publisher:all/experimental *manually* upgradeable from 
1.2.0+LibO5.2.6-1 to 1.2.0+LibO5.3.1-1

I started to blame aptitude for upgrading packages from unstable
to experimental without any warning. However, after some analysis,
it appears that the messages from apt-show-versions are wrong!
These packages do NOT come from experimental.

I started to wonder about this when I compared two machines:

zira:~> apt-show-versions -a libreoffice-common
libreoffice-common:all 1:5.2.6-1 install ok installed
libreoffice-common:all 1:4.3.3-2+deb8u5 stable   ftp.de.debian.org
libreoffice-common:all 1:4.3.3-2+deb8u6 stable   security.debian.org
No stable-updates version
libreoffice-common:all 1:5.2.5-2testing  ftp.de.debian.org
No unstable version
libreoffice-common:all 1:5.3.1-1experimental http.debian.net
libreoffice-common:all 1:5.3.1-1experimental ftp.de.debian.org
libreoffice-common:all/experimental *manually* upgradeable from 1:5.2.6-1 to 
1:5.3.1-1

cventin:~> apt-show-versions -a libreoffice-common
libreoffice-common:all 1:5.2.6-1 install ok installed
libreoffice-common:all 1:4.3.3-2+deb8u5 stable   ftp.de.debian.org
libreoffice-common:all 1:4.3.3-2+deb8u6 stable   security.debian.org
No stable-updates version
libreoffice-common:all 1:5.2.5-2testing  ftp.de.debian.org
libreoffice-common:all 1:5.2.6-2unstable ftp.de.debian.org
libreoffice-common:all 1:5.3.1-1experimental ftp.de.debian.org
libreoffice-common:all 1:5.3.1-1experimental http.debian.net
libreoffice-common:all/unstable 1:5.2.6-1 upgradeable to 1:5.2.6-2

which is inconsistent.

What actually happened is that libreoffice-common and some of
the other packages of libreoffice source are missing from the
unstable Packages file on zira:

/var/lib/apt/lists/ftp.de.debian.org_debian_dists_unstable_main_binary-amd64_Packages

Perhaps the old 1:5.2.6-1 version has been removed from unstable for some
reason, before it got upgraded to 1:5.2.6-2. This Packages file on cventin
is a bit more recent and has 1:5.2.6-2, which explains why the problem
doesn't appear on this machine. I've attached a compressed diff of these
Packages files.

Now, concerning apt-show-versions, if the installed version (here,
1:5.2.6-1) cannot be found, then apt-show-versions must not assume
that it comes from experimental. Otherwise the user is tempted to
upgrade to the experimental version instead of waiting for the
package to be back in unstable.

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 

Bug#858337: marked as done (apt-show-versions may show incorrect package version for "Architecture: all" when a foreign arch is enabled)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 13:18:55 +
with message-id 
and subject line Bug#816470: fixed in apt-show-versions 0.22.14
has caused the Debian Bug report #816470,
regarding apt-show-versions may show incorrect package version for 
"Architecture: all" when a foreign arch is enabled
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.)


-- 
816470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.22.7
Severity: important

[Severity important as this can lead the user to install potentially
broken packages.]

On my laptop:

zira:~> apt-show-versions -u | grep manually
fonts-opensymbol:all/experimental *manually* upgradeable from 
2:102.7+LibO5.2.6-1 to 2:102.10+LibO5.3.1-1
libreoffice-common:all/experimental *manually* upgradeable from 1:5.2.6-1 to 
1:5.3.1-1
libreoffice-java-common:all/experimental *manually* upgradeable from 1:5.2.6-1 
to 1:5.3.1-1
libreoffice-librelogo:all/experimental *manually* upgradeable from 1:5.2.6-1 to 
1:5.3.1-1
libreoffice-nlpsolver:all/experimental *manually* upgradeable from 
0.9+LibO5.2.6-1 to 0.9+LibO5.3.1-1
libreoffice-report-builder:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-script-provider-bsh:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-script-provider-js:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-script-provider-python:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-style-galaxy:all/experimental *manually* upgradeable from 1:5.2.6-1 
to 1:5.3.1-1
libreoffice-style-tango:all/experimental *manually* upgradeable from 1:5.2.6-1 
to 1:5.3.1-1
libreoffice-wiki-publisher:all/experimental *manually* upgradeable from 
1.2.0+LibO5.2.6-1 to 1.2.0+LibO5.3.1-1

I started to blame aptitude for upgrading packages from unstable
to experimental without any warning. However, after some analysis,
it appears that the messages from apt-show-versions are wrong!
These packages do NOT come from experimental.

I started to wonder about this when I compared two machines:

zira:~> apt-show-versions -a libreoffice-common
libreoffice-common:all 1:5.2.6-1 install ok installed
libreoffice-common:all 1:4.3.3-2+deb8u5 stable   ftp.de.debian.org
libreoffice-common:all 1:4.3.3-2+deb8u6 stable   security.debian.org
No stable-updates version
libreoffice-common:all 1:5.2.5-2testing  ftp.de.debian.org
No unstable version
libreoffice-common:all 1:5.3.1-1experimental http.debian.net
libreoffice-common:all 1:5.3.1-1experimental ftp.de.debian.org
libreoffice-common:all/experimental *manually* upgradeable from 1:5.2.6-1 to 
1:5.3.1-1

cventin:~> apt-show-versions -a libreoffice-common
libreoffice-common:all 1:5.2.6-1 install ok installed
libreoffice-common:all 1:4.3.3-2+deb8u5 stable   ftp.de.debian.org
libreoffice-common:all 1:4.3.3-2+deb8u6 stable   security.debian.org
No stable-updates version
libreoffice-common:all 1:5.2.5-2testing  ftp.de.debian.org
libreoffice-common:all 1:5.2.6-2unstable ftp.de.debian.org
libreoffice-common:all 1:5.3.1-1experimental ftp.de.debian.org
libreoffice-common:all 1:5.3.1-1experimental http.debian.net
libreoffice-common:all/unstable 1:5.2.6-1 upgradeable to 1:5.2.6-2

which is inconsistent.

What actually happened is that libreoffice-common and some of
the other packages of libreoffice source are missing from the
unstable Packages file on zira:

/var/lib/apt/lists/ftp.de.debian.org_debian_dists_unstable_main_binary-amd64_Packages

Perhaps the old 1:5.2.6-1 version has been removed from unstable for some
reason, before it got upgraded to 1:5.2.6-2. This Packages file on cventin
is a bit more recent and has 1:5.2.6-2, which explains why the problem
doesn't appear on this machine. I've attached a compressed diff of these
Packages files.

Now, concerning apt-show-versions, if the installed version (here,
1:5.2.6-1) cannot be found, then apt-show-versions must not assume
that it comes from experimental. Otherwise the user is tempted to
upgrade to the experimental version instead of waiting for the
package to be back in unstable.

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 

Bug#816470: marked as done (apt-show-versions: wrong output for apt-doc)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 13:18:55 +
with message-id 
and subject line Bug#816470: fixed in apt-show-versions 0.22.14
has caused the Debian Bug report #816470,
regarding apt-show-versions: wrong output for apt-doc
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.)


-- 
816470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.22.7
Severity: normal

I currently have the following:

cventin:~> apt-cache show apt-doc
Package: apt-doc
Source: apt
Version: 1.2.4
Installed-Size: 875
Maintainer: APT Development Team 
Architecture: all
Description-en: documentation for APT
 This package contains the user guide and offline guide for various
 APT tools which are provided in a html and a text-only version.
Description-md5: bc2b838ed28e60af95d78926380a3300
Tag: admin::package-management, hardware::storage, hardware::storage:cd,
 made-of::html, protocol::ftp, protocol::http, protocol::ipv6,
 role::documentation, suite::debian, use::downloading, use::searching,
 works-with-format::html, works-with-format::plaintext,
 works-with::software:package
Section: doc
Priority: optional
Filename: pool/main/a/apt/apt-doc_1.2.4_all.deb
Size: 339568
MD5sum: dc6c14dca231226855be65bfd967de52
SHA1: 5d64e55b8271da51e85c0de148a10e0393142735
SHA256: a914b340168ef1b0e79e28289d05746c6b4c4bd131e0e6d6940e478a4d89ced4

Package: apt-doc
Source: apt
Version: 1.2.3
Installed-Size: 875
Maintainer: APT Development Team 
Architecture: all
Description-en: documentation for APT
 This package contains the user guide and offline guide for various
 APT tools which are provided in a html and a text-only version.
Description-md5: bc2b838ed28e60af95d78926380a3300
Tag: admin::package-management, hardware::storage, hardware::storage:cd,
 made-of::html, protocol::ftp, protocol::http, protocol::ipv6,
 role::documentation, suite::debian, use::downloading, use::searching,
 works-with-format::html, works-with-format::plaintext,
 works-with::software:package
Section: doc
Priority: optional
Filename: pool/main/a/apt/apt-doc_1.2.3_all.deb
Size: 339430
MD5sum: 95441fe0771c28c207a1a6c2d0075bbd
SHA1: 3843a48005afee4ee5c07b85b66fdf577f455997
SHA256: 19ef1abcd7c7b88496e800c23c8eaa8cb6b4d8dd0b3d6fd94dab91957a7b8684

Package: apt-doc
Source: apt
Version: 1.0.9.8.2
Installed-Size: 715
Maintainer: APT Development Team 
Architecture: all
Description-en: documentation for APT
 This package contains the user guide and offline guide for various
 APT tools which are provided in a html and a text-only version.
Description-md5: bc2b838ed28e60af95d78926380a3300
Tag: admin::package-management, hardware::storage, hardware::storage:cd,
 made-of::html, protocol::ftp, protocol::http, protocol::ipv6,
 role::documentation, suite::debian, use::downloading, use::searching,
 works-with-format::html, works-with-format::plaintext,
 works-with::software:package
Section: doc
Priority: optional
Filename: pool/main/a/apt/apt-doc_1.0.9.8.2_all.deb
Size: 300756
MD5sum: 007ba24fb15341a1eb6fc770ad1ab90b
SHA1: e698dcd1cd6f18ec9b7d432ecb99d74be9fd701b
SHA256: eff6c23b0465e8e382ecc87d87bba12660121730e49cb5f4c7660d641c57cd33

which should respectively be the unstable, testing and stable
versions. And

cventin:~> apt-get install apt-doc -s
NOTE: This is only a simulation!
  apt-get needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-image-4.1.0-2-amd64 linux-image-4.2.0-1-amd64
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  apt-doc
1 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Inst apt-doc [1.2.3] (1.2.4 Debian:unstable [all])
Conf apt-doc (1.2.4 Debian:unstable [all])

confirming that 1.2.4 is the unstable package. But apt-show-versions
says that it is 1.2.3:

cventin:~> apt-show-versions -a apt-doc
apt-doc:all 1.2.3 install ok installed
apt-doc:all 1.0.9.8.2 stable   ftp.fr.debian.org
No stable-updates version
apt-doc:all 1.2.3 testing  ftp.fr.debian.org
apt-doc:all 1.2.3 unstable ftp.fr.debian.org
No experimental version
apt-doc:all 1.2.3 installed: No available version in archive

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 

Bug#1024765: marked as done (apt-show-versions is confused when versions from different architectures disagree)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 13:18:55 +
with message-id 
and subject line Bug#816470: fixed in apt-show-versions 0.22.14
has caused the Debian Bug report #816470,
regarding apt-show-versions is confused when versions from different 
architectures disagree
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.)


-- 
816470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816470
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.22.13+nmu1
Severity: normal

I get

cventin:~> apt-show-versions -a clang-14-doc
clang-14-doc:all 1:14.0.6-8 install ok installed
No stable version
No stable-updates version
clang-14-doc:all 1:14.0.6-2   testing  ftp.debian.org
clang-14-doc:all 1:14.0.6-6   unstable ftp.debian.org
clang-14-doc:all 1:14.0.6-10~exp1 experimental ftp.debian.org
clang-14-doc:all/experimental *manually* upgradeable from 1:14.0.6-8 to 
1:14.0.6-10~exp1

but the current unstable version is 1:14.0.6-8, not 1:14.0.6-6!

On https://tracker.debian.org/pkg/llvm-toolchain-14 one has

  [2022-11-12] Accepted llvm-toolchain-14 1:14.0.6-8 (source) into unstable
  (Sylvestre Ledru)

and on my machine, /usr/share/doc/clang-14-doc/changelog.Debian.gz
starts with

llvm-toolchain-14 (1:14.0.6-8) unstable; urgency=medium
   ^^  

Moreover,
/var/lib/apt/lists/ftp.debian.org_debian_dists_unstable_main_binary-amd64_Packages
contains

Package: clang-14-doc
Source: llvm-toolchain-14
Version: 1:14.0.6-8
[...]

I suspect that apt-show-versions is confused by
/var/lib/apt/lists/ftp.debian.org_debian_dists_unstable_main_binary-i386_Packages,
which contains

Package: clang-14-doc
Source: llvm-toolchain-14
Version: 1:14.0.6-6
[...]

i.e. the unstable version given by apt-show-versions.

I suppose that apt-show-versions should follow the behavior of apt
and aptitude.

Concerning apt:

cventin:~> apt install -s clang-14-doc/unstable
[...]
Selected version '1:14.0.6-8' (Debian:unstable [all]) for 'clang-14-doc'

so it takes the amd64 version, probably because this is the main
architecture on this machine (i386 being a foreign one).

And in /var/log/aptitude, I can see

[UPGRADE] clang-14-doc:amd64 1:14.0.6-7 -> 1:14.0.6-8

mentioning amd64 explicitly.

-- 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)
Foreign Architectures: i386

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

Versions of packages apt-show-versions depends on:
ii  apt  2.5.4
ii  libapt-pkg-perl  0.1.40+b2
ii  perl [libstorable-perl]  5.36.0-4

apt-show-versions recommends no packages.

apt-show-versions suggests no packages.

-- 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: apt-show-versions
Source-Version: 0.22.14
Done: Christoph Martin 

We believe that the bug you reported is fixed in the latest version of
apt-show-versions, 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 816...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated apt-show-versions 
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: Fri, 21 Jul 2023 14:44:39 +0200
Source: apt-show-versions
Architecture: source
Version: 0.22.14
Distribution: unstable
Urgency: medium
Maintainer: Christoph Martin 
Changed-By: Christoph Martin 
Closes: 816470 858337 1024765
Changes:
 apt-show-versions (0.22.14) unstable; urgency=medium
 .
   * fix 

Bug#1024765: marked as done (apt-show-versions is confused when versions from different architectures disagree)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 13:18:55 +
with message-id 
and subject line Bug#1024765: fixed in apt-show-versions 0.22.14
has caused the Debian Bug report #1024765,
regarding apt-show-versions is confused when versions from different 
architectures disagree
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.)


-- 
1024765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.22.13+nmu1
Severity: normal

I get

cventin:~> apt-show-versions -a clang-14-doc
clang-14-doc:all 1:14.0.6-8 install ok installed
No stable version
No stable-updates version
clang-14-doc:all 1:14.0.6-2   testing  ftp.debian.org
clang-14-doc:all 1:14.0.6-6   unstable ftp.debian.org
clang-14-doc:all 1:14.0.6-10~exp1 experimental ftp.debian.org
clang-14-doc:all/experimental *manually* upgradeable from 1:14.0.6-8 to 
1:14.0.6-10~exp1

but the current unstable version is 1:14.0.6-8, not 1:14.0.6-6!

On https://tracker.debian.org/pkg/llvm-toolchain-14 one has

  [2022-11-12] Accepted llvm-toolchain-14 1:14.0.6-8 (source) into unstable
  (Sylvestre Ledru)

and on my machine, /usr/share/doc/clang-14-doc/changelog.Debian.gz
starts with

llvm-toolchain-14 (1:14.0.6-8) unstable; urgency=medium
   ^^  

Moreover,
/var/lib/apt/lists/ftp.debian.org_debian_dists_unstable_main_binary-amd64_Packages
contains

Package: clang-14-doc
Source: llvm-toolchain-14
Version: 1:14.0.6-8
[...]

I suspect that apt-show-versions is confused by
/var/lib/apt/lists/ftp.debian.org_debian_dists_unstable_main_binary-i386_Packages,
which contains

Package: clang-14-doc
Source: llvm-toolchain-14
Version: 1:14.0.6-6
[...]

i.e. the unstable version given by apt-show-versions.

I suppose that apt-show-versions should follow the behavior of apt
and aptitude.

Concerning apt:

cventin:~> apt install -s clang-14-doc/unstable
[...]
Selected version '1:14.0.6-8' (Debian:unstable [all]) for 'clang-14-doc'

so it takes the amd64 version, probably because this is the main
architecture on this machine (i386 being a foreign one).

And in /var/log/aptitude, I can see

[UPGRADE] clang-14-doc:amd64 1:14.0.6-7 -> 1:14.0.6-8

mentioning amd64 explicitly.

-- 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)
Foreign Architectures: i386

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

Versions of packages apt-show-versions depends on:
ii  apt  2.5.4
ii  libapt-pkg-perl  0.1.40+b2
ii  perl [libstorable-perl]  5.36.0-4

apt-show-versions recommends no packages.

apt-show-versions suggests no packages.

-- 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: apt-show-versions
Source-Version: 0.22.14
Done: Christoph Martin 

We believe that the bug you reported is fixed in the latest version of
apt-show-versions, 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 1024...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated apt-show-versions 
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: Fri, 21 Jul 2023 14:44:39 +0200
Source: apt-show-versions
Architecture: source
Version: 0.22.14
Distribution: unstable
Urgency: medium
Maintainer: Christoph Martin 
Changed-By: Christoph Martin 
Closes: 816470 858337 1024765
Changes:
 apt-show-versions (0.22.14) unstable; urgency=medium
 .
   

Bug#858337: marked as done (apt-show-versions may show incorrect package version for "Architecture: all" when a foreign arch is enabled)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 13:18:55 +
with message-id 
and subject line Bug#1024765: fixed in apt-show-versions 0.22.14
has caused the Debian Bug report #1024765,
regarding apt-show-versions may show incorrect package version for 
"Architecture: all" when a foreign arch is enabled
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.)


-- 
1024765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.22.7
Severity: important

[Severity important as this can lead the user to install potentially
broken packages.]

On my laptop:

zira:~> apt-show-versions -u | grep manually
fonts-opensymbol:all/experimental *manually* upgradeable from 
2:102.7+LibO5.2.6-1 to 2:102.10+LibO5.3.1-1
libreoffice-common:all/experimental *manually* upgradeable from 1:5.2.6-1 to 
1:5.3.1-1
libreoffice-java-common:all/experimental *manually* upgradeable from 1:5.2.6-1 
to 1:5.3.1-1
libreoffice-librelogo:all/experimental *manually* upgradeable from 1:5.2.6-1 to 
1:5.3.1-1
libreoffice-nlpsolver:all/experimental *manually* upgradeable from 
0.9+LibO5.2.6-1 to 0.9+LibO5.3.1-1
libreoffice-report-builder:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-script-provider-bsh:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-script-provider-js:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-script-provider-python:all/experimental *manually* upgradeable from 
1:5.2.6-1 to 1:5.3.1-1
libreoffice-style-galaxy:all/experimental *manually* upgradeable from 1:5.2.6-1 
to 1:5.3.1-1
libreoffice-style-tango:all/experimental *manually* upgradeable from 1:5.2.6-1 
to 1:5.3.1-1
libreoffice-wiki-publisher:all/experimental *manually* upgradeable from 
1.2.0+LibO5.2.6-1 to 1.2.0+LibO5.3.1-1

I started to blame aptitude for upgrading packages from unstable
to experimental without any warning. However, after some analysis,
it appears that the messages from apt-show-versions are wrong!
These packages do NOT come from experimental.

I started to wonder about this when I compared two machines:

zira:~> apt-show-versions -a libreoffice-common
libreoffice-common:all 1:5.2.6-1 install ok installed
libreoffice-common:all 1:4.3.3-2+deb8u5 stable   ftp.de.debian.org
libreoffice-common:all 1:4.3.3-2+deb8u6 stable   security.debian.org
No stable-updates version
libreoffice-common:all 1:5.2.5-2testing  ftp.de.debian.org
No unstable version
libreoffice-common:all 1:5.3.1-1experimental http.debian.net
libreoffice-common:all 1:5.3.1-1experimental ftp.de.debian.org
libreoffice-common:all/experimental *manually* upgradeable from 1:5.2.6-1 to 
1:5.3.1-1

cventin:~> apt-show-versions -a libreoffice-common
libreoffice-common:all 1:5.2.6-1 install ok installed
libreoffice-common:all 1:4.3.3-2+deb8u5 stable   ftp.de.debian.org
libreoffice-common:all 1:4.3.3-2+deb8u6 stable   security.debian.org
No stable-updates version
libreoffice-common:all 1:5.2.5-2testing  ftp.de.debian.org
libreoffice-common:all 1:5.2.6-2unstable ftp.de.debian.org
libreoffice-common:all 1:5.3.1-1experimental ftp.de.debian.org
libreoffice-common:all 1:5.3.1-1experimental http.debian.net
libreoffice-common:all/unstable 1:5.2.6-1 upgradeable to 1:5.2.6-2

which is inconsistent.

What actually happened is that libreoffice-common and some of
the other packages of libreoffice source are missing from the
unstable Packages file on zira:

/var/lib/apt/lists/ftp.de.debian.org_debian_dists_unstable_main_binary-amd64_Packages

Perhaps the old 1:5.2.6-1 version has been removed from unstable for some
reason, before it got upgraded to 1:5.2.6-2. This Packages file on cventin
is a bit more recent and has 1:5.2.6-2, which explains why the problem
doesn't appear on this machine. I've attached a compressed diff of these
Packages files.

Now, concerning apt-show-versions, if the installed version (here,
1:5.2.6-1) cannot be found, then apt-show-versions must not assume
that it comes from experimental. Otherwise the user is tempted to
upgrade to the experimental version instead of waiting for the
package to be back in unstable.

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

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, 

Bug#816470: marked as done (apt-show-versions: wrong output for apt-doc)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 13:18:55 +
with message-id 
and subject line Bug#1024765: fixed in apt-show-versions 0.22.14
has caused the Debian Bug report #1024765,
regarding apt-show-versions: wrong output for apt-doc
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.)


-- 
1024765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.22.7
Severity: normal

I currently have the following:

cventin:~> apt-cache show apt-doc
Package: apt-doc
Source: apt
Version: 1.2.4
Installed-Size: 875
Maintainer: APT Development Team 
Architecture: all
Description-en: documentation for APT
 This package contains the user guide and offline guide for various
 APT tools which are provided in a html and a text-only version.
Description-md5: bc2b838ed28e60af95d78926380a3300
Tag: admin::package-management, hardware::storage, hardware::storage:cd,
 made-of::html, protocol::ftp, protocol::http, protocol::ipv6,
 role::documentation, suite::debian, use::downloading, use::searching,
 works-with-format::html, works-with-format::plaintext,
 works-with::software:package
Section: doc
Priority: optional
Filename: pool/main/a/apt/apt-doc_1.2.4_all.deb
Size: 339568
MD5sum: dc6c14dca231226855be65bfd967de52
SHA1: 5d64e55b8271da51e85c0de148a10e0393142735
SHA256: a914b340168ef1b0e79e28289d05746c6b4c4bd131e0e6d6940e478a4d89ced4

Package: apt-doc
Source: apt
Version: 1.2.3
Installed-Size: 875
Maintainer: APT Development Team 
Architecture: all
Description-en: documentation for APT
 This package contains the user guide and offline guide for various
 APT tools which are provided in a html and a text-only version.
Description-md5: bc2b838ed28e60af95d78926380a3300
Tag: admin::package-management, hardware::storage, hardware::storage:cd,
 made-of::html, protocol::ftp, protocol::http, protocol::ipv6,
 role::documentation, suite::debian, use::downloading, use::searching,
 works-with-format::html, works-with-format::plaintext,
 works-with::software:package
Section: doc
Priority: optional
Filename: pool/main/a/apt/apt-doc_1.2.3_all.deb
Size: 339430
MD5sum: 95441fe0771c28c207a1a6c2d0075bbd
SHA1: 3843a48005afee4ee5c07b85b66fdf577f455997
SHA256: 19ef1abcd7c7b88496e800c23c8eaa8cb6b4d8dd0b3d6fd94dab91957a7b8684

Package: apt-doc
Source: apt
Version: 1.0.9.8.2
Installed-Size: 715
Maintainer: APT Development Team 
Architecture: all
Description-en: documentation for APT
 This package contains the user guide and offline guide for various
 APT tools which are provided in a html and a text-only version.
Description-md5: bc2b838ed28e60af95d78926380a3300
Tag: admin::package-management, hardware::storage, hardware::storage:cd,
 made-of::html, protocol::ftp, protocol::http, protocol::ipv6,
 role::documentation, suite::debian, use::downloading, use::searching,
 works-with-format::html, works-with-format::plaintext,
 works-with::software:package
Section: doc
Priority: optional
Filename: pool/main/a/apt/apt-doc_1.0.9.8.2_all.deb
Size: 300756
MD5sum: 007ba24fb15341a1eb6fc770ad1ab90b
SHA1: e698dcd1cd6f18ec9b7d432ecb99d74be9fd701b
SHA256: eff6c23b0465e8e382ecc87d87bba12660121730e49cb5f4c7660d641c57cd33

which should respectively be the unstable, testing and stable
versions. And

cventin:~> apt-get install apt-doc -s
NOTE: This is only a simulation!
  apt-get needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-image-4.1.0-2-amd64 linux-image-4.2.0-1-amd64
Use 'apt autoremove' to remove them.
The following packages will be upgraded:
  apt-doc
1 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Inst apt-doc [1.2.3] (1.2.4 Debian:unstable [all])
Conf apt-doc (1.2.4 Debian:unstable [all])

confirming that 1.2.4 is the unstable package. But apt-show-versions
says that it is 1.2.3:

cventin:~> apt-show-versions -a apt-doc
apt-doc:all 1.2.3 install ok installed
apt-doc:all 1.0.9.8.2 stable   ftp.fr.debian.org
No stable-updates version
apt-doc:all 1.2.3 testing  ftp.fr.debian.org
apt-doc:all 1.2.3 unstable ftp.fr.debian.org
No experimental version
apt-doc:all 1.2.3 installed: No available version in archive

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 

Bug#858337: apt-show-versions: wrong output when version of an installed package is missing from the Packages files

2023-07-21 Thread Christoph Martin

Thanks for the patch. I'll have a try.

Am 11.07.23 um 12:15 schrieb Vincent Lefevre:


I note that there is a version comparison in sub parse_file:

 if (!defined $packages->{$package->{$PACKAGE}} or
 !defined 
$packages->{$package->{$PACKAGE}}{$package->{$ARCH}}{$VERS} or
 
$vs->compare($packages->{$package->{$PACKAGE}}{$package->{$ARCH}}{$VERS},
  $package->{$VERS}) < 0) {
 $package->{$RELEASE} = $release;
 $packages->{$package->{$PACKAGE}}{$package->{$ARCH}} = 
$package;
 }

So, if I understand correctly, if a Packages file contains several
versions of a package, the most recent one will be chosen. But such
a comparison is absent when these versions are in different Packages
files. I've attached a patch to add this comparison. Now, if I do



OpenPGP_signature
Description: OpenPGP digital signature


Bug#932501: BTS housekeeping and severity adjustments

2023-07-21 Thread Stefano Rivera
Hi Adrian (2021.05.30_21:44:58_+0200)
> severity 932501 serious
I'm wondering if this bug should really be serious. Squid's apparmor
config is shipped disabled, so one has to manually enable it to trigger
this bug.

I would have gone for normal/important.

I don't know what the correct solution to this bug is. Presumably one
has to get the squid profile to include the abstraction that
squid-deb-proxy provides. I don't know how this is usually done in a
Debian package. Maybe one of the apparmor team can comment.

Stefano

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



Bug#1039644: marked as done (r-cran-cowplot: autopkgtest failure with r-base (4.3.1-1))

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 12:49:32 +
with message-id 
and subject line Bug#1039644: fixed in r-cran-cowplot 1.1.1+dfsg-2
has caused the Debian Bug report #1039644,
regarding r-cran-cowplot: autopkgtest failure with r-base (4.3.1-1)
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.)


-- 
1039644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-cowplot
Version: 1.1.1+dfsg-1
Severity: serious
Justification: autopkgtest failure

Dear Maintainer,

The autopkgtest of your package fails with r-base (4.3.1-1):

 43s [ FAIL 7 | WARN 2 | SKIP 0 | PASS 55 ]
 43s 
 43s ══ Failed tests 

 43s ── Error ('test_draw_.R:8'): draw_grob() can align grobs 
───
 43s Error in `svglite_(filename, bg, width, height, pointsize, standalone, 
 43s always_valid)`: Graphics API version mismatch
 43s Backtrace:
 43s ▆
 43s  1. └─cowplot:::expect_doppelganger(...) at test_draw_.R:8:2
 43s  2.   └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at 
tests/testthat/helper-vdiffr.R:3:2
 43s  3. └─vdiffr (local) writer(fig, testcase, title)
 43s  4.   └─vdiffr:::svglite(file)
 43s  5. └─vdiffr:::svglite_(...)
 43s ── Error ('test_draw_.R:30'): image placement and scaling 
──
 43s Error in `svglite_(filename, bg, width, height, pointsize, standalone, 
 43s always_valid)`: Graphics API version mismatch
 43s Backtrace:
 43s ▆
 43s  1. └─cowplot:::expect_doppelganger(...) at test_draw_.R:30:2
 43s  2.   └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at 
tests/testthat/helper-vdiffr.R:3:2
 43s  3. └─vdiffr (local) writer(fig, testcase, title)
 43s  4.   └─vdiffr:::svglite(file)
 43s  5. └─vdiffr:::svglite_(...)
 43s ── Error ('test_draw_.R:85'): draw_plot_label() works 
──
 43s Error in `svglite_(filename, bg, width, height, pointsize, standalone, 
 43s always_valid)`: Graphics API version mismatch
 43s Backtrace:
 43s ▆
 43s  1. └─cowplot:::expect_doppelganger(...) at test_draw_.R:85:2
 43s  2.   └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at 
tests/testthat/helper-vdiffr.R:3:2
 43s  3. └─vdiffr (local) writer(fig, testcase, title)
 43s  4.   └─vdiffr:::svglite(file)
 43s  5. └─vdiffr:::svglite_(...)
 43s ── Error ('test_key_glyph.R:19'): key glyphs 
───
 43s Error in `svglite_(filename, bg, width, height, pointsize, standalone, 
 43s always_valid)`: Graphics API version mismatch
 43s Backtrace:
 43s ▆
 43s  1. └─cowplot:::expect_doppelganger(...) at test_key_glyph.R:19:2
 43s  2.   └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at 
tests/testthat/helper-vdiffr.R:3:2
 43s  3. └─vdiffr (local) writer(fig, testcase, title)
 43s  4.   └─vdiffr:::svglite(file)
 43s  5. └─vdiffr:::svglite_(...)
 43s ── Error ('test_plot_grid.R:11'): basic plot arranging works 
───
 43s Error in `svglite_(filename, bg, width, height, pointsize, standalone, 
 43s always_valid)`: Graphics API version mismatch
 43s Backtrace:
 43s ▆
 43s  1. └─cowplot:::expect_doppelganger(...) at test_plot_grid.R:11:2
 43s  2.   └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at 
tests/testthat/helper-vdiffr.R:3:2
 43s  3. └─vdiffr (local) writer(fig, testcase, title)
 43s  4.   └─vdiffr:::svglite(file)
 43s  5. └─vdiffr:::svglite_(...)
 43s ── Error ('test_plot_grid.R:49'): alignment 

 43s Error in `svglite_(filename, bg, width, height, pointsize, standalone, 
 43s always_valid)`: Graphics API version mismatch
 43s Backtrace:
 43s ▆
 43s  1. └─cowplot:::expect_doppelganger(...) at test_plot_grid.R:49:2
 43s  2.   └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at 
tests/testthat/helper-vdiffr.R:3:2
 43s  3. └─vdiffr (local) writer(fig, testcase, title)
 43s  4.   └─vdiffr:::svglite(file)
 43s  5. └─vdiffr:::svglite_(...)
 43s ── Error ('test_themes.R:62'): themes look right 
───
 43s Error in `svglite_(filename, bg, width, height, pointsize, standalone, 
 43s always_valid)`: Graphics API version mismatch
 43s Backtrace:
 43s ▆
 43s  1. └─cowplot:::expect_doppelganger("theme half open", p + 
theme_half_open()) at test_themes.R:62:2
 43s  2.   └─vdiffr::expect_doppelganger(title, fig, path = path, ...) at 

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

2023-07-21 Thread Jeremy Bícha
Control: found 1041537 1.1.1-2

I believe meson in Testing also has this issue.

We have been working around this in several Debian packages by setting
this in debian/rules:
export DEB_PYTHON_INSTALL_LAYOUT = deb

Thank you,
Jeremy Bícha



Processed: Re: python3 platlib points again to /usr/local

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> found 1041537 1.1.1-2
Bug #1041537 [meson] python3 platlib points again to /usr/local
Marked as found in versions meson/1.1.1-2.

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



Bug#1037585: marked as done (augustus: ftbfs with GCC-13)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 12:42:53 +0200
with message-id <3dee454c-4f82-02cc-8e53-a3cf41f61...@debian.org>
and subject line Re: [Debian-med-packaging] Bug#1037585: augustus: ftbfs with 
GCC-13
has caused the Debian Bug report #1037585,
regarding augustus: ftbfs with GCC-13
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.)


-- 
1037585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:augustus
Version: 3.5.0+dfsg-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/augustus_3.5.0+dfsg-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
make[2]: Leaving directory '/<>/auxprogs/bam2wig'
/usr/bin/make -C auxprogs/compileSpliceCands
make[2]: Entering directory '/<>/auxprogs/compileSpliceCands'
cc -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic -ansi -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c compileSpliceCands.c
compileSpliceCands.c: In function ‘getChromosome’:
compileSpliceCands.c:216:9: warning: ‘__builtin_strncat’ specified bound 
depends on the length of the source argument [-Wstringop-overflow=]
  216 | strncat(checkstring,chromosomename,strlen(chromosomename));
  | ^
compileSpliceCands.c:216:9: note: length computed here
  216 | strncat(checkstring,chromosomename,strlen(chromosomename));
  | ^~
compileSpliceCands.c: In function ‘parseLine’:
compileSpliceCands.c:292:9: warning: ‘__builtin_strncpy’ specified bound 256 
equals destination size [-Wstringop-truncation]
  292 | strncpy(d->name,tokens[0],LINEBUFFER);
  | ^
compileSpliceCands.c: In function ‘parseList’:
compileSpliceCands.c:333:69: warning: ‘left’ may be used uninitialized 
[-Wmaybe-uninitialized]
  333 | isCandidate = 
((right->averageCoverage>=left->averageCoverage*threshold) ||
  | 
^
compileSpliceCands.c:314:14: note: ‘left’ was declared here
  314 | Data left;
  |  ^~~~
compileSpliceCands.c: In function ‘main’:
compileSpliceCands.c:563:17: warning: ‘chromosomeLength’ may be used 
uninitialized [-Wmaybe-uninitialized]
  563 | 
parseList(,actualChromosome,chromosomeLength,oldname,maxSpliceSiteDiff,threshold,maxIntronLength);
  | 
^~~
compileSpliceCands.c:416:18: note: ‘chromosomeLength’ was declared here
  416 | long int chromosomeLength;
  |  ^~~~
cc -Wall -pedantic -ansi -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c -o list.o list.c
cc -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pedantic -ansi -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -o compileSpliceCands 
compileSpliceCands.o list.o
cp -f compileSpliceCands ../../bin/compileSpliceCands
make[2]: Leaving directory '/<>/auxprogs/compileSpliceCands'
/usr/bin/make -C auxprogs/filterBam
make[2]: Entering directory '/<>/auxprogs/filterBam'
(cd src;make)
make[3]: Entering directory '/<>/auxprogs/filterBam/src'
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wpedantic -std=c++11 -O3 -g 

Bug#1017982: marked as done (consul: CVE-2022-29153)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 12:20:55 +0200
with message-id 
and subject line 
has caused the Debian Bug report #1017982,
regarding consul: CVE-2022-29153
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.)


-- 
1017982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: consul
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for consul.

CVE-2021-37219[0]:
| HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows
| non-server agents with a valid certificate signed by the same CA to
| access server-only functionality, enabling privilege escalation. Fixed
| in 1.8.15, 1.9.9 and 1.10.2.

https://discuss.hashicorp.com/t/hcsec-2021-22-consul-raft-rpc-privilege-escalation/29024

CVE-2021-38698[1]:
| HashiCorp Consul and Consul Enterprise 1.10.1 Txn.Apply endpoint
| allowed services to register proxies for other services, enabling
| access to service traffic. Fixed in 1.8.15, 1.9.9 and 1.10.2.

https://discuss.hashicorp.com/t/hcsec-2021-24-consul-missing-authorization-check-on-txn-apply-endpoint/29026
https://github.com/hashicorp/consul/commit/747844bad6410091f2c6e961216c0c5fc285a44d
 (v1.8.15)

CVE-2022-29153[2]:
| HashiCorp Consul and Consul Enterprise through 2022-04-12 allow SSRF.

https://discuss.hashicorp.com/t/hcsec-2022-10-consul-s-http-health-check-may-allow-server-side-request-forgery/38393

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-37219
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-37219
[1] https://security-tracker.debian.org/tracker/CVE-2021-38698
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38698
[2] https://security-tracker.debian.org/tracker/CVE-2022-29153
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29153

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---

Version: consul/1.9.17+dfsg1-1

New upstream release, closes #1017982 (CVE-2022-29152).


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---


Bug#1040853: marked as done (python-lockfile autopkg test fail with setuptools 68)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 09:55:42 +
with message-id 
and subject line Bug#1040853: fixed in python-lockfile 1:0.12.2-3
has caused the Debian Bug report #1040853,
regarding python-lockfile autopkg test fail with setuptools 68
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.)


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

Package: src:python-lockfile
Version: 1:0.12.2-2.2
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-lockfile/35654871/log.gz

[...]
 32s autopkgtest [23:39:35]: test smoke-python3:  - - - - - - - - - - results - 
- - - - - - - - -
 32s smoke-python3FAIL stderr: 
/tmp/autopkgtest-lxc.37ggweuu/downtmp/build.QlD/src/debian/tests/smoke_test.py:27: 
DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html
 32s autopkgtest [23:39:35]: test smoke-python3:  - - - - - - - - - - stderr - 
- - - - - - - - -
 32s 
/tmp/autopkgtest-lxc.37ggweuu/downtmp/build.QlD/src/debian/tests/smoke_test.py:27: 
DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html

 32s   import pkg_resources
--- End Message ---
--- Begin Message ---
Source: python-lockfile
Source-Version: 1:0.12.2-3
Done: Ben Finney 

We believe that the bug you reported is fixed in the latest version of
python-lockfile, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Finney  (supplier of updated python-lockfile 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: Fri, 21 Jul 2023 19:03:46 +1000
Source: python-lockfile
Architecture: source
Version: 1:0.12.2-3
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Ben Finney 
Closes: 1040853
Changes:
 python-lockfile (1:0.12.2-3) unstable; urgency=medium
 .
   * Specify current VCS for Debian packaging work.
   * Grant license in Debian packaging files under terms of GNU GPL 3 or later.
   * debian/gbp.conf:
 * Update for current packaging source maintenance workflow.
   * Document the current packaging source maintenance workflow.
   * Override false positive Lintian check for VCS-* field names.
   * Declare conformance to “Standards-Version: 4.6.2”.
   * Declare Debhelper compatibility level 13.
   * debian/compat:
 * Remove obsolete configuration file.
   * debian/watch:
 * Update UScan configuration format to version 4.
   * Remove ‘get-orig-source’ and ‘get-packaged-orig-source’ targets.
 These are no longer mentioned in Debian Policy 4.1.4 and later.
   * debian/tests/:
 * Remove AutoPkgTest for Python 2 package.
   * Stop building the Python 2 package.
   * Explicitly declare build system for PyBuild.
   * Remove specification of ancient minimum Python version.
   * Specify the package build system does not require root privilege.
   * Declare upstream metadata in DEP-12 format.
   * Explicitly mark a superficial AutoPkgTest case.
   * Use only supported Python versions in the AutoPkgTest.
   * Use external package ‘python3-package-smoke-test’ for AutoPkgTest.
 Closes: bug#1040853. Thanks to Matthias Klose for the report.
   * debian/tests/smoke_test.py:
 * Remove unused test helper module, now migrated to external package.
Checksums-Sha1:
 a9bed5472efa038f7162a46ae984d84a9446341f 2186 python-lockfile_0.12.2-3.dsc
 788ebe1fb3b74e082ebf592eeb8b8ff066764c28 9568 
python-lockfile_0.12.2-3.debian.tar.xz
 71ec135d6a02f7f0672a3ded62da0e92c30fb0d9 8307 
python-lockfile_0.12.2-3_amd64.buildinfo
Checksums-Sha256:
 a127b059046f404712145ada8b9b9263fc92c3e91f82abb58496199f522ac03e 2186 
python-lockfile_0.12.2-3.dsc
 49e1968bc9cf919b7102919413e204f9d607e7fce31ab44e43103d5d3788534c 9568 
python-lockfile_0.12.2-3.debian.tar.xz
 102e0886002476ac14d3af03fd8520fe1ea871841b795cf28b3e28061bfccc44 8307 
python-lockfile_0.12.2-3_amd64.buildinfo
Files:
 607be94d835dd0d15d631b157251f59a 2186 python optional 

Bug#1039636: marked as done (r-bioc-complexheatmap: autopkgtest failure with r-base (4.3.1-1))

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 09:55:58 +
with message-id 
and subject line Bug#1039636: fixed in r-bioc-complexheatmap 2.16.0+dfsg-1
has caused the Debian Bug report #1039636,
regarding r-bioc-complexheatmap: autopkgtest failure with r-base (4.3.1-1)
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.)


-- 
1039636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-complexheatmap
Version: 2.14.0+dfsg-1
Severity: serious
Justification: autopkgtest failure

Dear Maintainer,

The autopkgtest of your package fails with r-base (4.3.1-1):

 120s Set `ht_opt$message = FALSE` to turn off this message.
 120s > draw(ht, test = TRUE)
 120s Error in Cairo(width, height, type = "png", file = filename, pointsize = 
pointsize,  : 
 120s   Graphics API version mismatch
 120s Error: The size of the temporary image for rasterization is too huge (362 
x
 120s 362 px) that it is cannot be handled by the device function
 120s `Cairo:CairoPNG()`. Please reduce the maximal size of temporary image
 120s by setting proper values for `ht_opt$raster_temp_image_max_width` and
 120s `ht_opt$raster_temp_image_max_height`.

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-complexheatmap/34900485/log.gz
--- End Message ---
--- Begin Message ---
Source: r-bioc-complexheatmap
Source-Version: 2.16.0+dfsg-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
r-bioc-complexheatmap, 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 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-complexheatmap 
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: Fri, 21 Jul 2023 10:38:49 +0200
Source: r-bioc-complexheatmap
Architecture: source
Version: 2.16.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1039636
Changes:
 r-bioc-complexheatmap (2.16.0+dfsg-1) unstable; urgency=medium
 .
   * Build against latest version of r-base
 Closes: #1039636
   * New upstream version
   * Standards-Version: 4.6.2 (routine-update)
   * Reduce piuparts noise in transitions (routine-update)
Checksums-Sha1:
 01aafd58be6dd0d2fe119b0ecf1f708193d63155 2417 
r-bioc-complexheatmap_2.16.0+dfsg-1.dsc
 1033ad7e27d1237693a6b8d653372d14928909a1 1308052 
r-bioc-complexheatmap_2.16.0+dfsg.orig.tar.xz
 08d551cad52dfa98b56b4d9959c6752d6d4cad1d 3708 
r-bioc-complexheatmap_2.16.0+dfsg-1.debian.tar.xz
 7912d30b768441cf62d215b9bc6f4a99b3041a43 20640 
r-bioc-complexheatmap_2.16.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 b83332a9e290ab589f5fa9f373cb1a3251cc729453cc9f2578cd981fa6186962 2417 
r-bioc-complexheatmap_2.16.0+dfsg-1.dsc
 ee1fc00a2e28325ee89a644d16e1c799897ffe81db21796a70412058967c995a 1308052 
r-bioc-complexheatmap_2.16.0+dfsg.orig.tar.xz
 9dd2193cd0c066eabec621b4ef6f446e7c46269a64a07f5492b0eb1c025199a5 3708 
r-bioc-complexheatmap_2.16.0+dfsg-1.debian.tar.xz
 aa56831c71bd75549a04513c9574517b363cfe5e20a191a8d004177d4a0e31b5 20640 
r-bioc-complexheatmap_2.16.0+dfsg-1_source.buildinfo
Files:
 b26b276fa4f4a7d265ef00f8b24041fc 2417 gnu-r optional 
r-bioc-complexheatmap_2.16.0+dfsg-1.dsc
 d7dadd29ba3f2c3e7f85fd854059a28c 1308052 gnu-r optional 
r-bioc-complexheatmap_2.16.0+dfsg.orig.tar.xz
 9d466065a34b8f435f817c1388378e4a 3708 gnu-r optional 
r-bioc-complexheatmap_2.16.0+dfsg-1.debian.tar.xz
 775e5bd57b2d39fe9e316d240214f24d 20640 gnu-r optional 
r-bioc-complexheatmap_2.16.0+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmS6RKYOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtGkMQ/9HwaGYvYGyEGIBT0X46ozkp5YSZbDj9pggUnC
cvaPwx0ulSldcVHxLemXsaSDffv010MQFuNVXpfAV3Sz46MY5bgXedH0j8Tu+SQc
IPkUZulYmQC2hEI9LZ/i7FkrUrG0DtgRc1OKivB6Y9f6alArBtVVFQpEMPD3tVPY
vKtMlhzIlX2rQcRzlPGOwVI0Th20LhdOoTKBalNbdGjiD09WarcQZYiuXHt4Xccq
mORk/4RQW7bmslgT0DMjF0Rihk5EVgYkSKR+ne+8glTcMhUYhpT1i0f57ZhhWEc9
BLe/LQLDntIMy5R4xD3WO8vUPRjNJRr45IBYgW0sp/Iss6d1k7Z2KeIXj4cL+GJt

Bug#1011775: marked as done (jamm: FTBFS with OpenJDK 17 due to an illegal reflective access during the tests)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 12:40:51 +0300
with message-id <918a6062-afd0-4290-7d3b-4359aa43d...@debian.org>
and subject line 1011775: fixed by new upstream release
has caused the Debian Bug report #1011775,
regarding jamm: FTBFS with OpenJDK 17 due to an illegal reflective access 
during the tests
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.)


-- 
1011775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jamm
Version: 0.3.3-3
Severity: important
Tags: ftbfs sid bookworm
User: debian-j...@lists.debian.org
Usertags: default-java17


jamm fails to build with OpenJDK 17, the tests make an illegal
reflective access into java.base/java.lang:


  [INFO] ---
  [INFO]  T E S T S
  [INFO] ---
  [INFO] Running org.github.jamm.MemoryMeterTest
  [ERROR] Tests run: 20, Failures: 1, Errors: 2, Skipped: 5, Time elapsed: 
0.147 s <<< FAILURE! - in org.github.jamm.MemoryMeterTest
  [ERROR] testPrimitives(org.github.jamm.MemoryMeterTest)  Time elapsed: 0.005 
s  <<< ERROR!
  java.lang.reflect.InaccessibleObjectException: Unable to make field private 
final byte[] java.lang.String.value accessible: module java.base does not 
"opens java.lang" to unnamed module @768debd
  at 
org.github.jamm.MemoryMeterTest.testPrimitives(MemoryMeterTest.java:443)
  
  [ERROR] testUnmeteredAnnotationOnFields(org.github.jamm.MemoryMeterTest)  
Time elapsed: 0.001 s  <<< ERROR!
  java.lang.reflect.InaccessibleObjectException: Unable to make field private 
final byte[] java.lang.String.value accessible: module java.base does not 
"opens java.lang" to unnamed module @768debd
  at 
org.github.jamm.MemoryMeterTest.testUnmeteredAnnotationOnFields(MemoryMeterTest.java:614)
  
  [ERROR] testByteBuffer(org.github.jamm.MemoryMeterTest)  Time elapsed: 0 s  
<<< FAILURE!
  java.lang.AssertionError: Shallow empty ByteBuffer expected:<48> but was:<56>
  at 
org.github.jamm.MemoryMeterTest.testByteBuffer(MemoryMeterTest.java:478)
  
  [INFO] Running org.github.jamm.GuessTest
  Guessed 16, instrumented 24 for {LONG*1}->{FLOAT*1}
  Guessed 16, instrumented 24 for {LONG*1}->{BYTE*4}
  [ERROR] Tests run: 4, Failures: 1, Errors: 0, Skipped: 3, Time elapsed: 0.418 
s <<< FAILURE! - in org.github.jamm.GuessTest
  [ERROR] testProblemClasses(org.github.jamm.GuessTest)  Time elapsed: 0.385 s  
<<< FAILURE!
  java.lang.AssertionError: Not all guesses matched the instrumented values. 
See output for details. expected:<0> but was:<2>
  at org.github.jamm.GuessTest.testProblemClasses(GuessTest.java:85)
  
  [INFO]
  [INFO] Results:
  [INFO]
  [ERROR] Failures:
  [ERROR]   GuessTest.testProblemClasses:85 Not all guesses matched the 
instrumented values. See output for details. expected:<0> but was:<2>
  [ERROR]   MemoryMeterTest.testByteBuffer:478 Shallow empty ByteBuffer 
expected:<48> but was:<56>
  [ERROR] Errors:
  [ERROR]   MemoryMeterTest.testPrimitives:443 » InaccessibleObject Unable to 
make field p...
  [ERROR]   MemoryMeterTest.testUnmeteredAnnotationOnFields:614 » 
InaccessibleObject Unabl...
  [INFO]
  [ERROR] Tests run: 24, Failures: 2, Errors: 2, Skipped: 8
  [INFO]
  [INFO] 

  [INFO] BUILD FAILURE
  [INFO] 

--- End Message ---
--- Begin Message ---

Version: 0.4.0-1

Hello,

New upstream release of jamm no longer has this FTBFS issue.

Andrius--- End Message ---


Bug#1039634: marked as done (r-bioc-biocneighbors: autopkgtest failure with r-base (4.3.1-1))

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 09:27:25 +
with message-id 
and subject line Bug#1039634: fixed in r-bioc-biocneighbors 1.18.0+ds-1
has caused the Debian Bug report #1039634,
regarding r-bioc-biocneighbors: autopkgtest failure with r-base (4.3.1-1)
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.)


-- 
1039634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-biocneighbors
Version: 1.16.0+ds-1
Severity: serious
Justification: autopkgtest failure

Dear Maintainer,

The autopkgtest of your package fail with r-base (4.3.1-1):

 344s [ FAIL 6 | WARN 488 | SKIP 0 | PASS 3372 ]
 344s 
 344s ══ Failed tests 

 344s ── Error ('test-find-exhaustive.R:11'): findExhaustive() behaves 
correctly on simple inputs ──
 344s Error in `FNN::get.knn(X, k = k)`: DLL requires the use of native symbols
 344s Backtrace:
 344s ▆
 344s  1. └─BiocNeighbors:::refFindKNN(X, k = k) at test-find-exhaustive.R:11:12
 344s  2.   └─FNN::get.knn(X, k = k) at tests/testthat/setup.R:58:8
 344s ── Error ('test-find-kmknn.R:11'): findKmknn() behaves correctly on 
simple inputs ──
 344s Error in `FNN::get.knn(X, k = k)`: DLL requires the use of native symbols
 344s Backtrace:
 344s ▆
 344s  1. └─BiocNeighbors:::refFindKNN(X, k = k) at test-find-kmknn.R:11:12
 344s  2.   └─FNN::get.knn(X, k = k) at tests/testthat/setup.R:58:8
 344s ── Error ('test-find-vptree.R:11'): findVptree() behaves correctly on 
simple inputs ──
 344s Error in `FNN::get.knn(X, k = k)`: DLL requires the use of native symbols
 344s Backtrace:
 344s ▆
 344s  1. └─BiocNeighbors:::refFindKNN(X, k = k) at test-find-vptree.R:11:12
 344s  2.   └─FNN::get.knn(X, k = k) at tests/testthat/setup.R:58:8
 344s ── Error ('test-query-exhaustive.R:15'): queryExhaustive() behaves 
correctly with queries ──
 344s Error in `FNN::get.knnx(data = X, query = Y, k = k)`: DLL requires the 
use of native symbols
 344s Backtrace:
 344s ▆
 344s  1. └─BiocNeighbors:::refQueryKNN(X, Y, k = k) at 
test-query-exhaustive.R:15:12
 344s  2.   └─FNN::get.knnx(data = X, query = Y, k = k) at 
tests/testthat/setup.R:78:8
 344s ── Error ('test-query-kmknn.R:15'): queryKmknn() behaves correctly with 
queries ──
 344s Error in `FNN::get.knnx(data = X, query = Y, k = k)`: DLL requires the 
use of native symbols
 344s Backtrace:
 344s ▆
 344s  1. └─BiocNeighbors:::refQueryKNN(X, Y, k = k) at test-query-kmknn.R:15:12
 344s  2.   └─FNN::get.knnx(data = X, query = Y, k = k) at 
tests/testthat/setup.R:78:8
 344s ── Error ('test-query-vptree.R:15'): queryVptree() behaves correctly with 
queries ──
 344s Error in `FNN::get.knnx(data = X, query = Y, k = k)`: DLL requires the 
use of native symbols
 344s Backtrace:
 344s ▆
 344s  1. └─BiocNeighbors:::refQueryKNN(X, Y, k = k) at 
test-query-vptree.R:15:12
 344s  2.   └─FNN::get.knnx(data = X, query = Y, k = k) at 
tests/testthat/setup.R:78:8
 344s 
 344s [ FAIL 6 | WARN 488 | SKIP 0 | PASS 3372 ]

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-biocneighbors/34918493/log.gz
--- End Message ---
--- Begin Message ---
Source: r-bioc-biocneighbors
Source-Version: 1.18.0+ds-1
Done: Andreas Tille 

We believe that the bug you reported is fixed in the latest version of
r-bioc-biocneighbors, 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 1039...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated r-bioc-biocneighbors 
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: Fri, 21 Jul 2023 10:11:46 +0200
Source: r-bioc-biocneighbors
Architecture: source
Version: 1.18.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Andreas Tille 
Closes: 1039634
Changes:
 r-bioc-biocneighbors (1.18.0+ds-1) unstable; urgency=medium
 .
   * Team upload.
   * Rebuild against latest r-base
 Closes: #1039634
   * Standards-Version: 4.6.2 (routine-update)
   * Reduce piuparts noise in transitions (routine-update)
Checksums-Sha1:
 

Processed: bug 1037698 is forwarded to https://github.com/enkore/j4-dmenu-desktop/pull/139

2023-07-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1037698 https://github.com/enkore/j4-dmenu-desktop/pull/139
Bug #1037698 [src:j4-dmenu-desktop] j4-dmenu-desktop: ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/enkore/j4-dmenu-desktop/pull/139'.
> thanks
Stopping processing here.

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



Bug#1037698: j4-dmenu-desktop: ftbfs with GCC-13

2023-07-21 Thread Jochen Sprickerhof

Control: forwared -1 https://github.com/enkore/j4-dmenu-desktop/pull/139

Hi Peter,

j4-dmenu-desktop is a dependency of sxmo-utils and so I would like to 
prevent it's removal from testing. The patch linked above is really 
simple and I would be happy if you could upload a fixed version.

I can also sponsor the upload, if needed.

There where also multiple new upstream versions and I would be happy to 
help maintain this package if you would be ok with that.


In case you don't have time to do the upload, I can do an NMU. If you 
don't answer by end of next week I will assume that you are ok with an 
NMU containing the above patch and will upload.


Cheers Jochen

* Matthias Klose  [2023-06-14 09:25]:

Package: src:j4-dmenu-desktop
Version: 2.16-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/j4-dmenu-desktop_2.16-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html

[...]
 |  ^~~
/<>/src/Application.hh:149:22: error: unable to find string literal operator 
‘operator""_istr’ with ‘const char [11]’, ‘long unsigned int’ arguments
 149 | case "OnlyShowIn"_istr:
 |  ^
/<>/src/Application.hh:161:22: error: unable to find string literal operator 
‘operator""_istr’ with ‘const char [10]’, ‘long unsigned int’ arguments
 161 | case "NotShowIn"_istr:
 |  ^~~~
/<>/src/Application.hh:173:22: error: unable to find string literal operator 
‘operator""_istr’ with ‘const char [7]’, ‘long unsigned int’ arguments
 173 | case "Hidden"_istr:
 |  ^
/<>/src/Application.hh:174:22: error: unable to find string literal operator 
‘operator""_istr’ with ‘const char [10]’, ‘long unsigned int’ arguments
 174 | case "NoDisplay"_istr:
 |  ^~~~
/<>/src/Application.hh:182:22: error: unable to find string literal operator 
‘operator""_istr’ with ‘const char [9]’, ‘long unsigned int’ arguments
 182 | case "Terminal"_istr:
 |  ^~~
/<>/src/Application.hh:183:61: error: unable to find string literal operator 
‘operator""_istr’ with ‘const char [5]’, ‘long unsigned int’ arguments
 183 | this->terminal = make_istring(value) == "true"_istr;
 | ^~~
In file included from /<>/src/TestFormatters.cc:8:
/<>/src/Application.hh: In member function ‘bool 
Application::read(const char*, char**, size_t*)’:
/<>/src/Application.hh:94:19: warning: ignoring return value of 
‘char* getcwd(char*, size_t)’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
  94 | getcwd(pwd, 100);
 | ~~^~
/<>/src/Main.hh: In member function ‘bool Main::read_args(int, 
char**)’:
/<>/src/Main.hh:167:33: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
 167 | exclude_generic = true;
 | ^~
/<>/src/Main.hh:168:13: note: here
 168 | case 'l':
 | ^~~~
/<>/src/Main.hh: In member function ‘void Main::collect_files()’:
/<>/src/Main.hh:187:15: warning: ignoring return value of ‘char* 
getcwd(char*, size_t)’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
 187 | getcwd(original_wd, 384);
 | ~~^~
/<>/src/Main.hh:195:18: warning: ignoring return value of ‘int 
chdir(const char*)’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
 195 | chdir(path.c_str());
 | ~^~
/<>/src/Main.hh:204:14: warning: ignoring return value of ‘int 
chdir(const char*)’ declared with attribute ‘warn_unused_result’ [-Wunused-result]
 204 | chdir(original_wd);
 |   

Processed: Re: Bug#1041588: grep -r fails with "Operation not supported"

2023-07-21 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 grave
Bug #1041588 [grep] grep -r fails with "Operation not supported"
Severity set to 'grave' from 'important'
> tags -1 - moreinfo
Bug #1041588 [grep] grep -r fails with "Operation not supported"
Removed tag(s) moreinfo.
> retitle -1 grep -r on 10+ files fails with "Operation not supported"
Bug #1041588 [grep] grep -r fails with "Operation not supported"
Changed Bug title to 'grep -r on 10+ files fails with "Operation not 
supported"' from 'grep -r fails with "Operation not supported"'.

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



Bug#999952: marked as done (suricata: depends on obsolete pcre3 library)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 10:03:35 +0200
with message-id <8b8969c5-13a9-74d2-8bef-99437a02d...@debian.org>
and subject line Re: Bug#52: suricata: depends on obsolete pcre3 library
has caused the Debian Bug report #52,
regarding suricata: depends on obsolete pcre3 library
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.)


-- 
52: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=52
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: suricata
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---

Hi,


Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

[...]

Suricata upstream have moved to pcre2 and also released Suricata 7.0 
which contains this change. I just packaged and uploaded 7.0. Hence the 
version currently in unstable does no longer depend on pcre3 in Debian.

Closing this issue.

Thanks
Sascha


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---


Bug#1040854: marked as done (tinyrpc autopkg test fail with setuptools 68)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 07:50:18 +
with message-id 
and subject line Bug#1040854: fixed in python-tinyrpc 0.6-5
has caused the Debian Bug report #1040854,
regarding tinyrpc autopkg test fail with setuptools 68
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.)


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

Package: src:python-tinyrpc
Version: 0.6-4
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-tinyrpc/35654872/log.gz

[...]
 32s autopkgtest [23:39:35]: test smoke-python3: ---]
 32s autopkgtest [23:39:35]: test smoke-python3:  - - - - - - - - - - results - 
- - - - - - - - -
 32s smoke-python3FAIL stderr: 
/tmp/autopkgtest-lxc.7sjhefhd/downtmp/build.0BU/src/debian/tests/smoke_test.py:24: 
DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html
 33s autopkgtest [23:39:36]: test smoke-python3:  - - - - - - - - - - stderr - 
- - - - - - - - -
 33s 
/tmp/autopkgtest-lxc.7sjhefhd/downtmp/build.0BU/src/debian/tests/smoke_test.py:24: 
DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html

 33s   import pkg_resources
--- End Message ---
--- Begin Message ---
Source: python-tinyrpc
Source-Version: 0.6-5
Done: Ben Finney 

We believe that the bug you reported is fixed in the latest version of
python-tinyrpc, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Finney  (supplier of updated python-tinyrpc 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: Fri, 21 Jul 2023 17:10:51 +1000
Source: python-tinyrpc
Architecture: source
Version: 0.6-5
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Ben Finney 
Closes: 1040854
Changes:
 python-tinyrpc (0.6-5) unstable; urgency=medium
 .
   * Declare conformance to “Standards-Version: 4.6.2”.
 No additional changes needed.
   * Use packaged ‘python3-package-smoke-test’ for AutoPkgTest.
 Closes: bug#1040854. Thanks to Matthias Klose for the report.
   * debian/tests/smoke_test.py:
 * Remove unused test helper module, now migrated to external package.
   * debian/patches/use-python3-interpreter-for-example-programs.patch:
 * Correct the Python interpreter specified in example programs.
   * Update Lintian overrides to match current Lintian output.
Checksums-Sha1:
 2313f45d497d597894721fa7b408301042e13038 2245 python-tinyrpc_0.6-5.dsc
 beeb64895c235dac59a539a49166c91a44b90f20 7120 
python-tinyrpc_0.6-5.debian.tar.xz
 b021cf5ef46cec80add5223c40d5c57f84f89e74 8826 
python-tinyrpc_0.6-5_amd64.buildinfo
Checksums-Sha256:
 467b40dca5da17dc756d76c48776b8459e6bf1b0386ab340d1a1530abdf558b0 2245 
python-tinyrpc_0.6-5.dsc
 222737f26ad7054313e655431a3ac4b89ff1a5150465e583babb9b2ca940845c 7120 
python-tinyrpc_0.6-5.debian.tar.xz
 07ea1f08d093a0f5ad60ea7a44ff6adf8f758debaaa0934e424e570846e38f9e 8826 
python-tinyrpc_0.6-5_amd64.buildinfo
Files:
 7633c7bf66baa13a272483363c4e5903 2245 python optional python-tinyrpc_0.6-5.dsc
 cda541f8bcefca8b082d343e202853da 7120 python optional 
python-tinyrpc_0.6-5.debian.tar.xz
 ba80249cd6c926900ccd55f5fcd2958c 8826 python optional 
python-tinyrpc_0.6-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYVng8p4vpBLgeVxz+bRqrIRCDIIFAmS6ME0ACgkQ+bRqrIRC
DIIX8A/9HhawCDct563dQUiMcWu2hMKQ93N8Qka60kSesUEF457U7z5BHo6zWEaE
AvESvkuVFONHNwDBDhnuOn/LiesgdpHDtBe8+rMAtqyoRxhezz3zvvSie6m7hYVJ
1ZcJH+YVoueww/Q099u+cpjXaJEcH9Zgv6vgoSfdVoL0IcKM1nMGJjUbrDTbTcos
IgeJyqlc3AgDHPALPiP1X6FqayAuO7NQ8YNf2meDkjqacARtI8QZ9W5Bo5WZ6bs/
4Aoz+Blayln3CzBc0mc9UdgMMNzEPevVjlEkwyWSkQC+Jpc3nO0/5PFhfriro5A9
IHNj6nalXLYkqp6dyajnuOCy/UjvOe0FFKfjMDEFeHOgJcIzPf/OALWaMrW8l+qB
2VufMWvcJeHWGc99HFTrRMYD3HLJxu+WpVOcd5ueVm1cAF1mFLxptIrDpgSUNoKz
Azlr2/4gajTYHN4WLMsmwzaZqC9q5whJCiaV4wUSI1spGEyEAqiJesn0fLo6AqS+
McgGoHVvImXMmjmi2bC9Y3aAjA8RyoVzz97oa5gb9TdQw+BuezX9mIsBz/TCfHnc

Bug#1040852: marked as done (python-jsonext autopkg test fail with setuptools 68)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 07:22:43 +
with message-id 
and subject line Bug#1040852: fixed in python-jsonext 0.4.2-3
has caused the Debian Bug report #1040852,
regarding python-jsonext autopkg test fail with setuptools 68
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.)


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

Package: src:python-jsonext
Version: 0.4.2-2
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-jsonext/35654870/log.gz

[...]
 17s autopkgtest [23:39:14]: test smoke-python3:  - - - - - - - - - - results - 
- - - - - - - - -
 17s smoke-python3FAIL stderr: 
/tmp/autopkgtest-lxc.yon5r0mj/downtmp/build.7KI/src/debian/tests/smoke_test.py:24: 
DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html
 17s autopkgtest [23:39:14]: test smoke-python3:  - - - - - - - - - - stderr - 
- - - - - - - - -
 17s 
/tmp/autopkgtest-lxc.yon5r0mj/downtmp/build.7KI/src/debian/tests/smoke_test.py:24: 
DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html

 17s   import pkg_resources
--- End Message ---
--- Begin Message ---
Source: python-jsonext
Source-Version: 0.4.2-3
Done: Ben Finney 

We believe that the bug you reported is fixed in the latest version of
python-jsonext, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Finney  (supplier of updated python-jsonext 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: Fri, 21 Jul 2023 16:48:54 +1000
Source: python-jsonext
Architecture: source
Version: 0.4.2-3
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Ben Finney 
Closes: 1040852
Changes:
 python-jsonext (0.4.2-3) unstable; urgency=medium
 .
   * The “Sarah Gorelick” release.
   * Declare conformance to “Standards-Version: 4.6.2”.
 No additional changes required.
   * Ensure AutoPkgTest import test executes outside of source tree.
   * Use external package ‘python3-package-smoke-test’ for AutoPkgTest.
 Closes: bug#1040852. Thanks to Matthias Klose for the report.
   * debian/tests/smoke_test.py:
 * Remove unused test helper module, now migrated to external package.
Checksums-Sha1:
 a16862c9a519fcd82fc2ff539a3a949939da966d 2068 python-jsonext_0.4.2-3.dsc
 11d3b3d7ba88f060ccd9363d5d5005590024dc98 6060 
python-jsonext_0.4.2-3.debian.tar.xz
 de0ca5c2f8de944562b3bd7973620a8fc7a1170d 7109 
python-jsonext_0.4.2-3_amd64.buildinfo
Checksums-Sha256:
 84ef5f05382dcc5724140bad1c9600073b78c8c92c2b095734fcaa9110a4267a 2068 
python-jsonext_0.4.2-3.dsc
 81b304e3871553e561bc766e96b9e5efe6b4cf650b0e68832125e8ab3be71172 6060 
python-jsonext_0.4.2-3.debian.tar.xz
 8571224fd87711194b6c16f47817a50353428f7b6971803d46af621de293837d 7109 
python-jsonext_0.4.2-3_amd64.buildinfo
Files:
 0ebb1e9e7a50d138c22bf36d67ff9f74 2068 python optional 
python-jsonext_0.4.2-3.dsc
 e51117483f9c5b0b6ccfcf8d9d1c107d 6060 python optional 
python-jsonext_0.4.2-3.debian.tar.xz
 0b0d22c3a365b8a223f38ced141c3de2 7109 python optional 
python-jsonext_0.4.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYVng8p4vpBLgeVxz+bRqrIRCDIIFAmS6KvcACgkQ+bRqrIRC
DIKagRAAt4iX6aDR2lLM5KrtMLbxhVcyRxdTLWLU6WaCsWcW2EvTE1u1sD1eW98b
TDhHBpN9dEWhHqHc38lwVJIuLRLxWt+noXX4fGCfYZnQtPZ8hlNZAaw5dMr/1mYE
KiMUHHJGixv67ULv7OLFg9zsh6j64h8oZBY/xwX6XOTFNB5FfN+Qw/V9t2XlaGy9
ILLBTMDmLyPEHv7x0OOINESF5Q9hkyxZHVqPFIYWr87q3lFxqQP+H0dFuhoC4Jk/
UWY5yNP55FDlbfaJ6M5SwRWVf8Dp27gOIDbI5s35ITZUHN3d9MZPyxGgdbUV/GAw
dWNLDKkA3hVQCEWSuU+ycPDchc5Z2B+OgwBRduZ1DWKNKiB9n2u8k4dTPo2Db8Be
sZ1cU9WD29oFz6ICmZ7Jm1/utDSr7MDvN2hiwldpr040rcVRSfPKCP7m+1if9c1I
MwDiXMpWRMYA21MdxfOK4HMBOkrafGdjnmSM7MJWGmX1JvlcVhMdjoRJfkSmLHh8
JJXlNlrTTOBTiE/mDlUk6AZzkEbRUIb97Kkqq1W130ef7reVenrzibJSCjSRFU+o
bUhtwrIgFjsa8u4hz0TflmILpdcwJFz/hQBVRGpZxtyMNIATL/KObl8b+6T63ZiH
I5L1a7ren2Ksbf6+BUGeTT90xG5tRqFRnW+gN2Unf+6TSW19lwc=
=k60D
-END PGP 

Bug#1041592: bugs.debian.org: unattended-upgrades removed bind9 and other packages

2023-07-21 Thread Marco Drummer
Package: bugs.debian.org
Severity: grave
Justification: renders package unusable

Dear Maintainer,

today I found DNS in my Network to be degraded.
I quickly figured out that the bind9 service was not running on this debain 
host. In fact the service was masked and the binary missing.

I installed the package via apt and everything worked again.
I found that unattended-upgrades remnoved bind9 and some other packages during 
its autoremove step.
That probably shouldn't happen however I am not sure if this was a bug in 
unattended-upgrades or the dependencies of some of the involved packages.

unattended-upgrade.log:

2023-07-21 06:17:23,880 INFO Starting unattended upgrades script
2023-07-21 06:17:23,881 INFO Allowed origins are: 
origin=Debian,codename=buster,label=Debian, 
origin=Debian,codename=buster,label=Debian-Security
2023-07-21 06:17:29,731 INFO Packages that will be upgraded: bind9 bind9-host 
bind9utils dnsutils libbind9-161 libdns-export1104 libdns1104 libirs-export161 
libirs161 libisc-export1100 libisc1100 libisccc161 libisccfg-export163 
libisccfg163 liblwres161
2023-07-21 06:17:29,732 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2023-07-21 06:17:30,712 WARNING Keeping auto-removable libnss-mdns package(s) 
because it would also remove the following packages which should be kept in 
this step: bind9utils
2023-07-21 06:17:36,767 WARNING Keeping auto-removable liblwres161 package(s) 
because it would also remove the following packages which should be kept in 
this step: bind9utils libbind9-161 libdns1104 libisc1100 libisccc161 
libisccfg163
2023-07-21 06:17:45,067 WARNING Keeping auto-removable net-tools package(s) 
because it would also remove the following packages which should be kept in 
this step: bind9utils libbind9-161 libdns1104 libisc1100 libisccc161 
libisccfg163
2023-07-21 06:17:56,056 INFO Packages that were successfully auto-removed: 
avahi-daemon avahi-utils bind9 bind9-host dnsutils host libavahi-core7 
libdaemon0 libirs161 libnss-mdns
2023-07-21 06:17:56,057 INFO Packages that are kept back: liblwres161 
libnss-mdns net-tools


-- System Information:
Debian Release: 10.13
  APT prefers oldoldstable-updates
  APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-24-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Bug#999936: [pkg-uWSGI-devel] Bug#999936: uwsgi: depends on obsolete pcre3 library

2023-07-21 Thread Jonas Smedegaard
Quoting Alexandre Rossi (2023-07-21 08:33:19)
> > Your package still depends on the old, obsolete PCRE3[0] libraries
> > (i.e. libpcre3-dev). This has been end of life for a while now, and
> > upstream do not intend to fix any further bugs in it. Accordingly, I
> > would like to remove the pcre3 libraries from Debian, preferably in
> > time for the release of Bookworm.
> 
> I gave it go, it compiles.
> https://github.com/unbit/uwsgi/pull/2543
> 
> Hopefully, I will find time in the coming weeks to test with some
> routing patterns.

Sounds great.  Thanks for looking into this!

 - Jonas

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

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

signature.asc
Description: signature


Bug#1040851: marked as done (python-daemon autopkg test fail with setuptools 68)

2023-07-21 Thread Debian Bug Tracking System
Your message dated Fri, 21 Jul 2023 06:53:18 +
with message-id 
and subject line Bug#1040851: fixed in python-daemon 2.3.2-2
has caused the Debian Bug report #1040851,
regarding python-daemon autopkg test fail with setuptools 68
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.)


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

Package: src:python-daemon
Version: 2.3.2-1
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-daemon/35654869/log.gz

[...]
21s autopkgtest [23:39:13]: test smoke-python3:  - - - - - - - - - - results - - 
- - - - - - - -
 21s smoke-python3FAIL stderr: 
/tmp/autopkgtest-lxc.bo7h42l3/downtmp/build.rEJ/src/debian/tests/smoke_test.py:25: 
DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html
--- End Message ---
--- Begin Message ---
Source: python-daemon
Source-Version: 2.3.2-2
Done: Ben Finney 

We believe that the bug you reported is fixed in the latest version of
python-daemon, 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 1040...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ben Finney  (supplier of updated python-daemon 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: Fri, 21 Jul 2023 16:09:30 +1000
Source: python-daemon
Architecture: source
Version: 2.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Ben Finney 
Changed-By: Ben Finney 
Closes: 1040851
Changes:
 python-daemon (2.3.2-2) unstable; urgency=medium
 .
   * Declare conformance to “Standards-Version: 4.6.2”.
 No additional changes needed.
   * Set the Homepage field to the current URL.
   * Ensure AutoPkgTest import test executes outside of source tree.
   * Use external package ‘python3-package-smoke-test’ for AutoPkgTest.
 Closes: bug#1040851. Thanks to Matthias Klose for the report.
   * debian/tests/smoke_test.py:
 * Remove unused test helper module, now migrated to external package.
Checksums-Sha1:
 967a6c655f189e31a2d15246a6059c9adb5b5e56 2106 python-daemon_2.3.2-2.dsc
 ad6658e737410e58b6d00df232e43b277b622484 31140 
python-daemon_2.3.2-2.debian.tar.xz
 d0c0e98dc18d776fff8f4d582d68efad2e72ab7b 8865 
python-daemon_2.3.2-2_amd64.buildinfo
Checksums-Sha256:
 21420c8705694a7130f4dc556c35b41099611c39760f72933ed04423237ac980 2106 
python-daemon_2.3.2-2.dsc
 5e31b71976eba4125773813441ae67e394bbfbf4da08f13f406c0de0c990ce75 31140 
python-daemon_2.3.2-2.debian.tar.xz
 6ba82d08022112fcf99a4b7e7951bb83368fb665535ab4308168885dd778857b 8865 
python-daemon_2.3.2-2_amd64.buildinfo
Files:
 30fcb130a23673dbd4ecc7dd59d59a9b 2106 python optional python-daemon_2.3.2-2.dsc
 6df378622208314f307b8235ea2de64f 31140 python optional 
python-daemon_2.3.2-2.debian.tar.xz
 fbeba983363680738468e5b4193ed871 8865 python optional 
python-daemon_2.3.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYVng8p4vpBLgeVxz+bRqrIRCDIIFAmS6IwYACgkQ+bRqrIRC
DIK1NxAAkhfDzobwwQgAfZCmryWycRjpbKgEyC6h16eldqQVD5+T3n3SC3oHFjr8
8Hj6/hirxJs9aWHwCydYecipKcU0lPy2VxulrDUsCkkyAGXdDiUaKyyTTINJc8f/
VrlycrC5Gt/8LunbYHkHcpJ2mB8njO6Zx1zCqrmuoIKqaIMUOB2qK9PZJCyruCH2
UXpwf8ND02jmCwKO6p/8mUxIDGXBWtdaVJIKf+xSn/eY9xscJ5XuMhb34i8unN9G
PF/K5EXHooQyKFlSb4ZsKuV/LkJnzK7zwPWo78cXRYlIqytRjHt7XzfQCsG5qysm
W5ZaeTvdL40QUxLtQgnlpTRDHR+5L7BiRYjDDT8Sk2sxpxz/JjS16PEmjMpMRB2P
+gWHfNeM/I7q4kgYCVJStEJBVodpKejMOI5TQeaauzwjpiDCNhwxfzB+e8pF7FaI
2T0XVCrwDIGpdvwTdGGbvfEnP2BUKDvDk165LatHJcu+JaRNrRVfP5qt6OtxxHSJ
CBA+g/5Z390FJNahlRmGXNt+memIWNTg83jkU6oyPPM0Za3FuWM+40doUQjrD4XO
0GUZUrMnb/At6UXM/SFacyoRqgC3voiWwI9sGy3XjVe+Xw7Drb9XrsCojv5Qt5Hf
5vozobwnMIyiLeC2E1AFfJeh2lx0f8rTdF7F3R/8TyAsGJpAzRk=
=pexY
-END PGP SIGNATURE End Message ---


  1   2   >