Bug#1026603: foolscap: FTBFS: AttributeError: module 'inspect' has no attribute 'getargspec'

[Andrius Merkys]

Hello,

On Tue, 20 Dec 2022 18:11:51 +0100 Lucas Nussbaum  > 
During a rebuild of all packages in sid, your package failed to build

on amd64.


[skip]

>   File 
"/<>/.pybuild/cpython3_3.11/build/foolscap/remoteinterface.py", 
line 191, in initFromMethod

> names, _, _, typeList = inspect.getargspec(method)
> ^^
> AttributeError: module 'inspect' has no attribute 'getargspec'

inspect.getargspec has been deprecated for some time [1] and most likely 
finally removed in Python 3.11. I have attempted to replace it with 
inspect.getfullargspec as seen somewhere else [2], but this did not work.


[1] https://docs.python.org/3/library/inspect.html
[2] https://github.com/pyinvoke/invoke/issues/833#issuecomment-1293148106

Andrius

Bug#1027127: transition: zxing-cpp

[Johannes Schauer Marin Rodrigues]

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

Hi,

the gstreamer 1.22 release as well as mediastreamer2 5.2 need zxing-cpp
version 1.4. Currently there is 1.2 in unstable and 1.4 in experimental.
Boyuan Yang, the maintainer of zxing-cpp told me to take care of this
transition as they lack the time right now to to so themselves.

I have rebuilt the reverse dependencies of libzxing-dev as listed here:

https://release.debian.org/transitions/html/auto-zxing-cpp.html

The one that FTBFS is libreoffice for which I submitted a bug here that
is already fixed in unstable:

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

Is it too late before the freeze to do this?

Thanks!

cheers, josch

Ben file:

title = "zxing-cpp";
is_affected = .depends ~ "libzxingcore1" | .depends ~ "libzxing2";
is_good = .depends ~ "libzxing2";
is_bad = .depends ~ "libzxingcore1";

Bug#1027126: libzstd FTCBFS: builds again with the build architecture compiler

[Helmut Grohne]

Source: libzstd
Version: 1.5.2+dfsg2-2
Severity: important
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

libzstd fails to cross build from source, because it detects a change in
build environment during dh_auto_install, changes its build directory
and starts the build from scratch. That change is due to dh_auto_install
not supplying a cross compiler. I propose just exporting it for all
targets from dpkg's buildtools.mk and attach a patch for your
convenience.

Helmut
diff -Nru libzstd-1.5.2+dfsg2/debian/changelog 
libzstd-1.5.2+dfsg2/debian/changelog
--- libzstd-1.5.2+dfsg2/debian/changelog2022-12-27 21:54:45.0 
+0100
+++ libzstd-1.5.2+dfsg2/debian/changelog2022-12-28 08:30:35.0 
+0100
@@ -1,3 +1,10 @@
+libzstd (1.5.2+dfsg2-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Export build tools for all targets. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 28 Dec 2022 08:30:35 +0100
+
 libzstd (1.5.2+dfsg2-2) unstable; urgency=medium
 
   * Fix a FTBFS on i386 (and on any arch where DEB_HOST_MULTIARCH is not
diff -Nru libzstd-1.5.2+dfsg2/debian/rules libzstd-1.5.2+dfsg2/debian/rules
--- libzstd-1.5.2+dfsg2/debian/rules2022-12-27 21:47:36.0 +0100
+++ libzstd-1.5.2+dfsg2/debian/rules2022-12-28 08:30:34.0 +0100
@@ -1,5 +1,9 @@
 #!/usr/bin/make -f
 
+# Export build tools for all targets to avoid build hash changes.
+DPKG_EXPORT_BUILDTOOLS=1
+include /usr/share/dpkg/buildtools.mk
+
 export DH_VERBOSE=1
 
 arch ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)

Bug#1027125: kmplayer: desktop entry contains unsuported arguments

[ZHANG Yuntian]

Package: kmplayer
Version: 1:0.12.0b-3+b1
Severity: important
X-Debbugs-Cc: y...@radxa.com

Dear Maintainer,

After installing kmplayer, I found out I cannot open media files via GUI file
manager. After opening the desktop entry, I found out it contains unsupported
command line options "-caption %c %i", which causes the program to fail early.

After removing them the file association works correctly.


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

Kernel: Linux 5.10.110-1-rockchip (SMP w/6 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kmplayer depends on:
ii  dbus-x111.12.24-0+deb11u1
ii  kio 5.78.0-5
ii  libc6   2.31-13+deb11u5
ii  libcairo2   1.16.0-5
ii  libdbus-1-3 1.12.24-0+deb11u1
ii  libdbus-glib-1-20.110-6
ii  libglib2.0-02.66.8-1
ii  libgtk2.0-0 2.24.33-2
ii  libkf5bookmarks55.78.0-2
ii  libkf5completion5   5.78.0-3
ii  libkf5configcore5   5.78.0-4
ii  libkf5configwidgets55.78.0-2
ii  libkf5coreaddons5   5.78.0-4
ii  libkf5i18n5 5.78.0-2
ii  libkf5iconthemes5   5.78.0-2
ii  libkf5kdelibs4support5  5.78.0-2
ii  libkf5kiocore5  5.78.0-5
ii  libkf5kiowidgets5   5.78.0-5
ii  libkf5mediaplayer5  5.78.0-2
ii  libkf5parts55.78.0-3
ii  libkf5textwidgets5  5.78.0-2
ii  libkf5widgetsaddons55.78.0-2
ii  libkf5xmlgui5   5.78.0-2
ii  libphonon4qt5-4 4:4.11.1-4
ii  libqt5core5a5.15.2+dfsg-9
ii  libqt5dbus5 5.15.2+dfsg-9
ii  libqt5gui5  5.15.2+dfsg-9
ii  libqt5network5  5.15.2+dfsg-9
ii  libqt5svg5  5.15.2-3
ii  libqt5widgets5  5.15.2+dfsg-9
ii  libqt5x11extras55.15.2-2
ii  libqt5xml5  5.15.2+dfsg-9
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.2-1
ii  libxcb1 1.14-3
ii  phonon4qt5  4:4.11.1-4

kmplayer recommends no packages.

Versions of packages kmplayer suggests:
pn  ffmpeg 
ii  konqueror  4:20.12.0-4
pn  mplayer
pn  vdr
pn  xawtv  

-- no debconf information

Bug#1026126: Dependencies for crosvm.

[Junichi Uekawa]

Ran cargo debstatus and looked through the output, I think here's what's 
missing:

 remain v0.2.3
 uuid v0.8.2 -- 1.2.1 is packaged
 heck v0.3.3 -- 0.4.0 is packaged
 argh_derive v0.1.8
 argh v0.1.8
 memoffset v0.5.6 -- 0.6.5 is packaged, can we use that instead?
 intrusive-collections v0.9.4
 enumn v0.1.4

-- probably can be removed?
 terminal_size v0.1.17 -- 0.2.1 is packaged.
 document-features v0.2.6

Bug#1021530: wireplumber: No sound after upgrade to 0.4.12-1

[Kurt Meyer]

This is still an issue with the 0.4.13-1 upgrade. I'm downgrading once again to 
0.4.11-5 until the issue gets resolved or a proper workaround is provided, 
preferrably via apt-listchanges News.

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance ulg5 85.202.160.45)

[Sharon Grant]

Thanks for your email!

On Wed, Dec 28, 2022 at 6:18 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: - - Welcome to National Family Auto Insurance ulg5 85.202.160.45

[Sharon Grant]

Thanks for your email!

On Fri, Dec 23, 2022 at 2:11 PM National_Family_Auto <
jros...@radicalflash.com> wrote:

>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance RltC 85.202.160.202)

[Sharon Grant]

Thanks for your email!

On Wed, Dec 28, 2022 at 4:06 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance rzOG 199.68.177.237)

[Sharon Grant]

Thanks for your email!

On Wed, Dec 28, 2022 at 4:03 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance 32Qv 85.202.160.38)

[Sharon Grant]

Thanks for your email!

On Wed, Dec 28, 2022 at 4:03 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance DHlT 85.202.160.199)

[Sharon Grant]

Thanks for your email!

On Wed, Dec 28, 2022 at 4:03 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance Slk7 85.202.160.203)

[Sharon Grant]

Thanks for your email!

On Wed, Dec 28, 2022 at 4:06 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026867: transition: youtube-dl

[Andres Salomon]

On Fri, Dec 23 2022 at 10:55:28 AM +0100, Sebastian Ramacher 
 wrote:

Control: tags -1 moreinfo

Hi Andres

On 2022-12-22 15:23:37 -0500, Andres Salomon wrote:

 Package: release.debian.org
 Severity: normal
 User: release.debian@packages.debian.org 


 Usertags: transition
 X-Debbugs-Cc: 994...@bugs.debian.org 
, debian-de...@lists.debian.org 



 Hi,

 Youtube-dl has mostly stopped development other than basic 
maintenance, and
 development has resumed with the yt-dlp project (which is already 
in debian)

 as documented in <>.

 For the bookworm release, we intend to drop the youtube-dl upstream 
code

 from
 the archive, with an empty transition package that will simply 
depend on

 yt-dlp
 and a NEWS entry informing users of the change. We considered 
attempting a
 seamless transition that provided a wrapper python module for the 
youtube_dl
 library and the /usr/bin/youtube-dl executable, but there are 
complications
 (such slightly different behavior between the two programs even 
when using
 yt-dlp's provided '--compat-options youtube-dl' argument, and 
programs that

 are
 aware of both yt-dlp and youtube-dl that will get confused if we 
pretend

 that
 youtube-dl is yt-dlp). Rather than risk the potential to introduce 
silent

 bugs
 into user setups, we prefer to simply inform users of the change 
and require

 them to manually verify their setups with yt-dlp.

 I filed 13 bugs with packages that have reverse dependencies on 
youtube-dl
 (ignoring those packages that depend on yt-dlp|youtube-dl); half 
have

 already
 been fixed. I plan to bump the severity on remaining bugs once the
 youtube-dl
 transition package is uploaded to sid (for those packages that 
actually

 break
 without a youtube-dl script/library).

 Depends on youtube-dl:
 ytcc: #1024212
 youtubedl-gui: #1024214 (done)
 mkchromecast: #1024216

 Recommends youtube-dl:
 lollypop: #1024217 (done)
 celluloid: #1024222
 lives: #1024229
 libmpv1: #1026866

 Suggests youtube-dl:
 git-annex: #1024226 (done)
 gpodder: #1024227 (done)
 liquidsoap: #1024228 (done)
 ytfzf: #1024230 (done)
 acetoneiso: #1024231
 python3-moviepy: #1024232

 There are no library or ABI concerns with this transition, this is 
mostly

 to get a transition slot and to track the transition.

 Ben file:

 title = "youtube-dl";
 is_affected = .build-depends ~ /youtube-dl/ | .depends ~ 
/youtube-dl/;

 is_good = .build-depends ~ /yt-dlp/ | .depends ~ /yt-dlp/;
 is_bad = .build-depends ~ /youtube-dl/ | .depends ~ /youtube-dl/;

 I can NMU where necessary for the remaining bugs, once the 
transition is

 underway.


I do not see the need for a transition here. There are no rebuilds
involved and all the required uploads are able to migrate on their own
without coordination.

If you want a ben tracker to track the status, we can provide one for
you. You don't have to wait for a transition slot, though.

Cheers
--
Sebastian Ramacher



Okay, that's fine. Given that there's only 6 open bugs left, I guess I 
don't really need a ben tracker.

Bug#1026818: - - Welcome to National Family Auto Insurance Slk7 85.202.160.203

[Sharon Grant]

Thanks for your email!

On Fri, Dec 23, 2022 at 2:11 PM National_Family_Auto <
jros...@lucas.reacthi.com> wrote:

>

Bug#1026818: - - Welcome to National Family Auto Insurance RltC 85.202.160.202

[Sharon Grant]

Thanks for your email!

On Fri, Dec 23, 2022 at 2:11 PM National_Family_Auto 
wrote:

>

Bug#1026818: - - Welcome to National Family Auto Insurance DHlT 85.202.160.199

[Sharon Grant]

Thanks for your email!

On Fri, Dec 23, 2022 at 2:11 PM National_Family_Auto <
jros...@outage.gradientfeed.com> wrote:

>

Bug#1026818: - - Welcome to National Family Auto Insurance 32Qv 85.202.160.38

[Sharon Grant]

Thanks for your email!

On Fri, Dec 23, 2022 at 2:11 PM National_Family_Auto <
jros...@gradientfeed.com> wrote:

>

Bug#1026818: - - Welcome to National Family Auto Insurance rzOG 199.68.177.237

[Sharon Grant]

Thanks for your email!

On Fri, Dec 23, 2022 at 2:11 PM National_Family_Auto <
jros...@beginnersummit.com> wrote:

>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance PuUy 199.68.181.30)

[Sharon Grant]

Thanks for your email!

On Wed, Dec 28, 2022 at 2:57 AM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1027124: should support TLS?

[Marco d'Itri]

Package: netcat-openbsd
Version: 1.219-1
Severity: normal

tls.h is provided by libtls-dev.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1026120: git-buildpackage: issues with upstreams LFS files

[Arnaud Rebillout]

On Wed, 21 Dec 2022 15:04:43 +0700 Arnaud Rebillout  
wrote:


> It's solved by setting --defuse-gitattributes.

I meant: setting --defuse-gitattributes=off, of course.

Bug#1027123: ITP: php-xhprof -- XHProf is a function-level hierarchical profiler for PHP

[Mark A. Hershberger]

Just found the php-xhprof repo[1] after starting to read the the
packaging instructions[2] but, since I want this for php7.4 (at least
for now), I think this is still relevent-ish.

Footnotes:
[1]  
https://salsa.debian.org/php-team/pecl/php-xhprof/-/blob/debian/main/debian/control

[2]  https://wiki.debian.org/PHP/GitUsage

-- 
http://hexmode.com/

I cannot remember the books I've read any more than the meals I have eaten;
even so, they have made me.
-- Ralph Waldo Emerson

Bug#1027123: ITP: php-xhprof -- XHProf is a function-level hierarchical profiler for PHP

[Mark A. Hershberger]

Package: wnpp
Owner: Mark A. Hershberger 
Severity: wishlist

* Package name: php-xhprof
  Version : 2.3.9
  Upstream Author : Xinhui Long
* URL or Web page : https://github.com/longxinH/xhprof/
* License : Apache2
  Description : XHProf is a function-level hierarchical profiler for PHP

-- 
http://hexmode.com/

I cannot remember the books I've read any more than the meals I have eaten;
even so, they have made me.
-- Ralph Waldo Emerson

Bug#1026818: - - Welcome to National Family Auto Insurance PuUy 199.68.181.30

[Sharon Grant]

Thanks for your email!

On Fri, Dec 23, 2022 at 2:11 PM National_Family_Auto <
jros...@sentry.blackburnkings.com> wrote:

>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance s6De 184.105.177.132)

[Sharon Grant]

Thanks for your email!

On Tue, Dec 27, 2022 at 5:54 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance yXnq 199.68.177.237)

[Sharon Grant]

Thanks for your email!

On Tue, Dec 27, 2022 at 5:54 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance 3c7T 199.68.181.30)

[Sharon Grant]

Thanks for your email!

On Tue, Dec 27, 2022 at 5:54 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1027114: docker.io: FTBFS: daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced)

[Tianon Gravi]

On Tue, 27 Dec 2022, 15:18 Sebastian Ramacher,  wrote:

> ---> Making bundle: dynbinary (in bundles/dynbinary)
> Building: bundles/dynbinary-daemon/dockerd-20.10.21+dfsg1
> GOOS="" GOARCH="" GOARM=""
> # github.com/docker/docker/daemon/graphdriver/btrfs
> daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced
> undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method
> max_referenced)
> make[1]: *** [debian/rules:114: override_dh_auto_build] Error 2
> make[1]: Leaving directory '/<>'
>

Looks like it's probably the recently reported
https://github.com/moby/moby/issues/44698 👀

- Tianon

>

Bug#1017020:

[M. Zhou]

Control: fixed -1 2022.07+dfsg-1
Control: close -1

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance XR26 85.202.160.203)

[Sharon Grant]

Thanks for your email!

On Tue, Dec 27, 2022 at 5:54 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance 3fS4 85.202.160.38)

[Sharon Grant]

Thanks for your email!

On Tue, Dec 27, 2022 at 5:54 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance EODq 85.202.160.199)

[Sharon Grant]

Thanks for your email!

On Tue, Dec 27, 2022 at 5:54 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance FjvQ 85.202.160.45)

[Sharon Grant]

Thanks for your email!

On Tue, Dec 27, 2022 at 5:54 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance lBGj 85.202.160.202)

[Sharon Grant]

Thanks for your email!

On Tue, Dec 27, 2022 at 5:54 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1026818: Info received (- - Welcome to National Family Auto Insurance FXqM 184.105.177.132)

[Sharon Grant]

Thanks for your email!

On Tue, Dec 27, 2022 at 5:54 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> Thank you for the additional information you have supplied regarding
> this Bug report.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  w...@debian.org
>  Justin Morgan <2justinmor...@gmail.com>
>
> If you wish to submit further information on this problem, please
> send it to 1026...@bugs.debian.org.
>
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 1026818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026818
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>

Bug#1027113: RM: childsplay -- RoQA; Python2, unmaintained

[Scott Kitterman]

RoQA is a standard removal category.  Anyone doing QA work can request packages 
be removed.  When clearing up the debris from old library removals this is 
normal.

I requested it (and did the removal) because it was an apparently unmaintained 
package that depended on libraries being removed.  The only other package left 
in the archive that needs python2 is gps-gnat since it has at least a partial 
effort at porting to Python 3 in git.

You have no idea how common circumstances like this are.  They happen routinely 
and it's extremely rare that there's an issue.  I'm happy to collaborate with 
maintainers such as yourself to rectify the situation in cases where it's 
needed.

Please let me know once it's in New and I'll have a look.

If the packages are already gone (dinstall needs to run before they're 
completely gone) you can download the binaries from snapshot.d.o, build 
locally, and then do a binary upload (uploads to New need to be with binaries 
in any case).

Scott K


On December 28, 2022 12:26:15 AM UTC, Markus Koschany  wrote:
>Am Dienstag, dem 27.12.2022 um 23:39 + schrieb Scott Kitterman:
>> Because it looked untouched for years.  It seemed unlikely anyone cares.  If
>> you want to upload it back (I'd suggest experimental), ping me and I'll look
>> at it in New.
>> 
>> Absent porting to Python 3, I don't particularly see the point, but I'll add
>> it back if you want.
>
>I don't recall that someone can remove packages from Debian without the consent
>of the maintainer or an explicit decision by the CTTE. We need a procedure not 
>arbitrariness. 
>
>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912485#40
>
>Who requested the removal of childsplay from Debian? Why is this necessary at
>all? 
>
>How can I upload I package to experimental which has not been ported to python3
>yet?
>
>

Bug#1025530: llvm-toolchain-15: FTBFS with grpc 1.51+

[Robin van Westrenen]

Source: llvm-toolchain-15
Version: 1:15.0.6-3
Followup-For: Bug #1025530
X-Debbugs-Cc: trib...@gmail.com

Dear Maintainer,

Where can I download the previous (libllvm15_15.0.6-3_i386.deb) i386 deb file, 
so I can continue my installation?

Regards,

Robin van Westrenen

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

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

Bug#1027113: RM: childsplay -- RoQA; Python2, unmaintained

[Markus Koschany]

Am Dienstag, dem 27.12.2022 um 23:39 + schrieb Scott Kitterman:
> Because it looked untouched for years.  It seemed unlikely anyone cares.  If
> you want to upload it back (I'd suggest experimental), ping me and I'll look
> at it in New.
> 
> Absent porting to Python 3, I don't particularly see the point, but I'll add
> it back if you want.

I don't recall that someone can remove packages from Debian without the consent
of the maintainer or an explicit decision by the CTTE. We need a procedure not 
arbitrariness. 

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912485#40

Who requested the removal of childsplay from Debian? Why is this necessary at
all? 

How can I upload I package to experimental which has not been ported to python3
yet?




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

Bug#1026933: Transition Qt 6.4.2

[Patrick Franz]

Hi,

we have uploaded Qt 6.4.2~rc1 to experimental.
We still don't know when the final release is going to happen, but the 
rc1 version is sufficient to do the transition.

I will update this bug report once everything has been built 
successfully in experimental.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1023697: wolfSSL 5.5.4 uploaded

[Felix Lechner]

Hi,

> there is considerable interest in using WolfSSL

I uploaded version 5.5.4-1, which was released last week, to the archive.

Kind regards
Felix Lechner

Bug#1027116: golang-github-containers-buildah: FTBFS: rc/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no fi

[Sebastian Ramacher]

Control: reassign -1 src:golang-github-containers-storage 1.43.0+ds1-3
Control: affects -1 src:golang-github-containers-buildah src:libpod

On 2022-12-28 00:20:58 +0100, Sebastian Ramacher wrote:
> Source: golang-github-containers-buildah
> Version: 1.28.0+ds1-3
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
> 
> https://buildd.debian.org/status/fetch.php?pkg=golang-github-containers-buildah&arch=amd64&ver=1.28.0%2Bds1-3%2Bb1&stamp=1672115946&raw=0
> 
> # github.com/containers/storage/drivers/btrfs
> src/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: 
> args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has 
> no field or method max_referenced)

The file is from golang-github-containers-storage-dev. Reassigning
accordingly.

Cheers

> github.com/containers/storage/drivers/copy
> github.com/containers/storage/drivers/devmapper
> github.com/containers/common/pkg/supplemented
> database/sql/driver
> github.com/containers/storage/pkg/lockfile
> github.com/containers/storage/drivers/vfs
> github.com/containers/storage/pkg/stringid
> github.com/google/uuid
> github.com/containers/storage/pkg/stringutils
> github.com/containers/storage/pkg/tarlog
> github.com/tchap/go-patricia/patricia
> github.com/mistifyio/go-zfs
> github.com/google/go-intervals/intervalset
> github.com/vbatts/tar-split/tar/asm
> github.com/containers/storage/pkg/truncindex
> github.com/containerd/stargz-snapshotter/estargz/errorutil
> golang.org/x/sync/errgroup
> github.com/cyphar/filepath-securejoin
> github.com/containers/image/directory/explicitfilepath
> github.com/containerd/stargz-snapshotter/estargz
> github.com/containers/storage/drivers/zfs
> github.com/containers/image/directory
> github.com/containers/image/docker/policyconfiguration
> github.com/containers/image/internal/streamdigest
> github.com/containers/image/internal/uploadreader
> github.com/containers/image/pkg/sysregistriesv2
> github.com/docker/docker-credential-helpers/credentials
> golang.org/x/sys/execabs
> golang.org/x/net/internal/socks
> github.com/docker/docker-credential-helpers/client
> github.com/docker/go-connections/tlsconfig
> github.com/containers/image/pkg/docker/config
> golang.org/x/net/proxy
> github.com/docker/distribution/registry/api/errcode
> github.com/docker/go-connections/sockets
> github.com/docker/distribution/digestset
> github.com/gorilla/mux
> github.com/docker/distribution/reference
> github.com/containers/image/pkg/tlsclientconfig
> github.com/docker/distribution/registry/client/auth/challenge
> gopkg.in/yaml.v2
> github.com/containers/image/docker/internal/tarfile
> github.com/docker/docker/api/types/blkiodev
> github.com/docker/distribution/registry/api/v2
> github.com/docker/docker/api/types/mount
> github.com/docker/docker/api/types/strslice
> github.com/docker/go-connections/nat
> github.com/docker/docker/api/types/container
> github.com/docker/docker/api/types/filters
> github.com/containers/image/docker/archive
> github.com/docker/docker/api/types/registry
> github.com/gogo/protobuf/proto
> github.com/docker/docker/api/types/network
> github.com/docker/docker/api/types/time
> github.com/docker/docker/errdefs
> net/http/httputil
> github.com/containers/image/oci/internal
> github.com/containers/image/oci/layout
> github.com/sylabs/sif/pkg/sif
> github.com/containers/image/oci/archive
> github.com/ghodss/yaml
> github.com/containers/image/docker
> github.com/containers/image/tarball
> github.com/containers/image/sif
> github.com/opencontainers/runc/libcontainer/utils
> github.com/opencontainers/runc/libcontainer/apparmor
> text/template/parse
> github.com/containers/common/pkg/apparmor/internal/supported
> github.com/containers/common/pkg/capabilities
> github.com/containers/common/pkg/cgroupv2
> github.com/containers/common/pkg/util
> github.com/containers/common/pkg/download
> github.com/containers/common/pkg/timetype
> github.com/containers/common/pkg/retry
> github.com/containers/common/pkg/filters
> github.com/containers/common/pkg/signal
> github.com/chzyer/readline
> text/template
> github.com/lunixbochs/vtclean
> github.com/juju/ansiterm/tabwriter
> github.com/mattn/go-isatty
> github.com/mattn/go-colorable
> github.com/juju/ansiterm
> github.com/manifoldco/promptui/list
> github.com/containers/common/pkg/apparmor
> github.com/manifoldco/promptui/screenbuf
> github.com/disiqueira/gotree
> github.com/docker/docker/api/types/swarm/runtime
> database/sql
> github.com/containers/common/pkg/config
> github.com/manifoldco/promptui
> github.com/docker/docker/api/types/swarm
> github.com/docker/docker/api/types
> github.com/containers/image/pkg/shortnames
> github.com/docker/docker/api/types/volume
> github.com/docker/docker/client
> github.com/seccomp/libseccomp-golang
> github.com/containers/buildah/docker
> github.com/containers/ocicrypt/helpers
> github.com/jinzhu/copier
> github.com/containers

Bug#1027122: nomad-driver-podman: FTBFS: unknown error

[Sebastian Ramacher]

Source: nomad-driver-podman
Version: 0.1.0-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=nomad-driver-podman&arch=amd64&ver=0.1.0-2%2Bb7&stamp=1672122772&raw=0

cd _build && go install -trimpath -v -p 4 
github.com/hashicorp/nomad-driver-podman 
github.com/hashicorp/nomad-driver-podman/iopodman 
github.com/hashicorp/nomad-driver-podman/version
src/github.com/hashicorp/nomad/vendor/github.com/hashicorp/hcl/v2/pos_scanner.go:7:2:
 cannot find package "github.com/apparentlymart/go-textseg/v12/textseg" in any 
of:

/<>/_build/src/github.com/hashicorp/nomad/vendor/github.com/apparentlymart/go-textseg/v12/textseg
 (vendor tree)
/usr/lib/go-1.19/src/github.com/apparentlymart/go-textseg/v12/textseg 
(from $GOROOT)

/<>/_build/src/github.com/apparentlymart/go-textseg/v12/textseg 
(from $GOPATH)
dh_auto_build: error: cd _build && go install -trimpath -v -p 4 
github.com/hashicorp/nomad-driver-podman 
github.com/hashicorp/nomad-driver-podman/iopodman 
github.com/hashicorp/nomad-driver-podman/version returned exit code 1

Cheers
-- 
Sebastian Ramacher

Bug#1027113: RM: childsplay -- RoQA; Python2, unmaintained

[Scott Kitterman]

Because it looked untouched for years.  It seemed unlikely anyone cares.  If 
you want to upload it back (I'd suggest experimental), ping me and I'll look at 
it in New.

Absent porting to Python 3, I don't particularly see the point, but I'll add it 
back if you want.

Scott K

On December 27, 2022 11:33:18 PM UTC, Markus Koschany  wrote:
>On Tue, 27 Dec 2022 18:15:53 -0500 Scott Kitterman 
>wrote:
>> Package: ftp.debian.org
>> Severity: normal
>> 
>> This is the last external rdepend for python-all and needs to go.  It
>> appears unmaintained both upstream and in Debian.
>> 
>> Scott K
>
>
>Hello Scott,
>
>why did you remove childsplay from Debian without asking the maintainer for his
>consent?
>
>You don't have to remove childsplay as a reverse-dependency of python-all to
>complete the removal request. 
>
>I am aware that childsplay has not been ported to python3 yet. Why can't we
>just keep it in Debian (even if uninstallable) for the time being. We all know
>that a reintroduction to Debian can take several months. This all seems to be a
>lot of make work to me.

Bug#1027121: Got an error: Error in line 2978: file not found

[Joerg Schiermeier, Bielefeld/Germany]

Package: podget
Version: 0.9.0-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi there!

At the end of running a download of new podcasts I get this error message:
Command line:
$ podget

- ---[Message]---
Cleanup old tracks.
Deleting tracks from :
/usr/bin/podget: Zeile 2978: : Datei oder Verzeichnis nicht gefunden

Error:
  Script: podget
  At line:2944
  Exit Status:1

Context:
2941fi
2942fi
2943if (( VERBOSITY >= 2 )) ; then
2944 >>>echo "Deleting tracks from ${FILE}:"
2945fi
2946while read -r LINE ; do
2947if [[ -f "${DIR_LIBRARY}/${LINE}" ]]; then

Closing session and removing lock file.
podget  55,45s user 136,96s system 12% cpu 25:33,64 total
- ---[/Message]---

This should be fixed. Thank you!

Happy new year!

- - --
Yours sincerely
Joerg Schiermeier


- - -- System Information:
Debian Release: bookworm/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.0.0-6-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.utf-8, LC_CTYPE=de_DE.utf-8 (charmap=UTF-8), 
LANGUAGE=de:en_GB:es
Shell: /bin/sh linked to /usr/bin/dash
Init: OpenRC (via /run/openrc), PID 1: init

Versions of packages podget depends on:
ii  bash 5.2-2+b2
ii  coreutils9.1-1
ii  debianutils  5.7-0.4
ii  findutils4.9.0-3
ii  gawk 1:5.1.0-1
ii  grep 3.8-3
ii  mawk 1.3.4.20200120-3.1
ii  sed  4.8-1
ii  wget 1.21.3-1+b2

podget recommends no packages.

Versions of packages podget suggests:
ii  libc-bin  2.36-7

- - -- no debconf information

- -BEGIN PGP SIGNATURE-
Comment: This was created by GnuPG for Linux.

iQIzBAEBCAAdFiEERMHJSMoKBiNrvtXJodFQ9YsO8GMFAmOrgZ8ACgkQodFQ9YsO
8GNsiBAAovOncSRa3nY8MwMdC2ZlXNVa7smPiizsGrd4deSgeFI65csSTcziYyWr
4l3cm2CqPpODx/ES/bkNkjeyHLQJIPVmoqQFi1IDJcVBZBm7ccesT8pINgyGIvtX
MKXMSkxH3/YZO8N7Ph2BX8C8UWel4htW8jF0Cp1L/PBjjDbTR8FoSKe7u2bfp9rh
Wnjj4GmHgLfUdL677OLUyDYUQwNKLQ6EtdrVestQAOEbv+Wtpba/oavPABKJHAZB
VGBllbMk3Il05NOVsUAczoFBaI2aUGDWwhI2InOsZg2QbDTl9+vF1EDz+wADJweu
UxV9qxTlKtO5WlC77bEFW4mRpSIn1PjjlQjhKQArRDgKX0B8foaQ/CzQruf/w6f5
g5rAsIVbpg4IaqUd8MyBf0q2i2wPRMrHzdWrDzRVrPJO/29VG9VrmOSHg7luvK3p
pu0URrp6Xzm4dPu5v1Gi4HEQ0eib4l1wxzeVSMqR7yCbzyYi8Vh/i24bbcZGwzeo
hgTuL3j5jOB3eBlLUnVVsFmHGxWPeoxB2M8bKxhbERu2/F1XW/7YWk9/FK5kYboD
Tp+gjjOq9cHvuLx5Y0ep2NoL3LmkFKyHHS8AF7Xyy6zbfsfATtIqDkaMCL+PBQF1
xA9fvz2Rx28U3doxUWxQF2lOtzPAVvh0wY+GgwdLOk9Vog2ljr0=
=A1pw
- -END PGP SIGNATURE-

-BEGIN PGP SIGNATURE-
Comment: This was created by GnuPG for Linux.

iQIzBAEBCAAdFiEERMHJSMoKBiNrvtXJodFQ9YsO8GMFAmOrgwgACgkQodFQ9YsO
8GPhYg/5ATfG/sdQilPVy9PSe8RNSpejf/Ll4+Vvk4j2g+cyof+A7lQLPfxItQDa
PtybdOjV5YNWFpgNI1xQTt3lcdNISfR5I6NwRSJm1cKSDnw8qOZPFExRTHFrauuM
Xb/NuBKKrElFmO0gAaxISAEucxUt2bmVOMOw9m0nAQswJkwXCriH9vwkgkrH4i3W
K2zaqMS6MVJVQmOAsyVUgOJ9YFZZ0fUxSgy5VxqSbu379cRxl7z7In4VWeRWj93X
2a6TcoX3IjN8kzr4e8HAKRIx1VCvTYMwjiDfZEwVkYIaE8LM0r3InZZbQ8jWZiFc
+ztjs9vypKs8tj+TrzNUSAQo/ZWBBt76rr1V00dERE8uAthlKXVTxHJnP9TPb9Fm
Pt1KdM6YrGXvRD5TveQgeRWurWlaDfA5ZshjxckKKH7GYCBUVhYjkPVJBSxeGAOC
cgS+phsfPyYxH7EhO2dbiSBSeFpoP93yHKrrM06EYv1+ap5Qoc4Ikhl0Es63jjgj
kvPg25mq6zQWDVWBGRDL8xtvR4XU8WjunQ67NtigM3i+9b+iAS0C9bIVKjz/s++d
M/fEr2cGOub/u095cCpmbspyZE+2WiYIVUU7UNtVM28UY5XOii9cb3FWikvRDpJ9
goMHF0u8YbVhwL6Ek8N3bLTveUCBZ5f+hhdYKXbimee7vx8mjU0=
=knXW
-END PGP SIGNATURE-

Bug#1027113: RM: childsplay -- RoQA; Python2, unmaintained

[Markus Koschany]

On Tue, 27 Dec 2022 18:15:53 -0500 Scott Kitterman 
wrote:
> Package: ftp.debian.org
> Severity: normal
> 
> This is the last external rdepend for python-all and needs to go.  It
> appears unmaintained both upstream and in Debian.
> 
> Scott K


Hello Scott,

why did you remove childsplay from Debian without asking the maintainer for his
consent?

You don't have to remove childsplay as a reverse-dependency of python-all to
complete the removal request. 

I am aware that childsplay has not been ported to python3 yet. Why can't we
just keep it in Debian (even if uninstallable) for the time being. We all know
that a reintroduction to Debian can take several months. This all seems to be a
lot of make work to me.


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

Bug#1026598: blocked by NEW queue

[Reinhard Tartler]

In order to fix this issue, I'm waiting for
https://ftp-master.debian.org/new/rust-trust-dns-server_0.22.0-1.html to
make it out of (binary) NEW.



-- 
regards,
Reinhard

Bug#1027120: phcpack: FTBFS: dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && !refd->die_remove' failed.

[Sebastian Ramacher]

Source: phcpack
Version: 2.4.86+dfsg-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=phcpack&arch=amd64&ver=2.4.86%2Bdfsg-2%2Bb3&stamp=1672159517&raw=0

   dh_dwz -a -O--buildsystem=pybuild
dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && 
!refd->die_remove' failed.
dh_dwz: error: dwz 
-mdebian/python3-phcpy/usr/lib/debug/.dwz/x86_64-linux-gnu/python3-phcpy.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/python3-phcpy.debug -- 
debian/python3-phcpy/usr/lib/python3/dist-packages/phcpy/phcpy2c3.cpython-310-x86_64-linux-gnu.so
 
debian/python3-phcpy/usr/lib/python3/dist-packages/phcpy/phcpy2c3.cpython-311-x86_64-linux-gnu.so
 died with signal 6
dwz: ./dwz.c:12035: adjust_exprloc: Assertion `refd != NULL && 
!refd->die_remove' failed.
dh_dwz: error: dwz -- debian/phcpack/usr/bin/phc died with signal 6
dh_dwz: error: Aborting due to earlier error
make: *** [debian/rules:11: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher

Bug#1027117: iem-plugin-suite: FTBFS: error: ‘class juce::AudioProcessorPlayer’ has no member named ‘audioDeviceIOCallback’; did you mean ‘AudioIODeviceCallback’?

[Sebastian Ramacher]

Source: iem-plugin-suite
Version: 1.13.0-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=iem-plugin-suite&arch=amd64&ver=1.13.0-3%2Bb1&stamp=1672120155&raw=0

[  8%] Building CXX object 
AllRADecoder/CMakeFiles/AllRADecoder.dir/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.cpp.o
cd /<>/obj-x86_64-linux-gnu/AllRADecoder && /usr/bin/c++ 
-DDONT_SET_USING_JUCE_NAMESPACE=1 -DJUCE_DISPLAY_SPLASH_SCREEN=0 
-DJUCE_GLOBAL_MODULE_SETTINGS_INCLUDED=1 -DJUCE_MODAL_LOOPS_PERMITTED=1 
-DJUCE_MODULE_AVAILABLE_juce_audio_basics=1 
-DJUCE_MODULE_AVAILABLE_juce_audio_devices=1 
-DJUCE_MODULE_AVAILABLE_juce_audio_formats=1 
-DJUCE_MODULE_AVAILABLE_juce_audio_plugin_client=1 
-DJUCE_MODULE_AVAILABLE_juce_audio_processors=1 
-DJUCE_MODULE_AVAILABLE_juce_audio_utils=1 -DJUCE_MODULE_AVAILABLE_juce_core=1 
-DJUCE_MODULE_AVAILABLE_juce_data_structures=1 
-DJUCE_MODULE_AVAILABLE_juce_dsp=1 -DJUCE_MODULE_AVAILABLE_juce_events=1 
-DJUCE_MODULE_AVAILABLE_juce_graphics=1 
-DJUCE_MODULE_AVAILABLE_juce_gui_basics=1 
-DJUCE_MODULE_AVAILABLE_juce_gui_extra=1 -DJUCE_MODULE_AVAILABLE_juce_opengl=1 
-DJUCE_MODULE_AVAILABLE_juce_osc=1 -DJUCE_SHARED_CODE=1 
-DJUCE_STANDALONE_APPLICATION=JucePlugin_Build_Standalone 
-DJUCE_TARGET_HAS_BINARY_DATA=1 -DJUCE_USE_CURL=0 
-DJUCE_USE_CUSTOM_PLUGIN_STANDALONE_APP=1 -DJUCE_USE_FLAC=0 
-DJUCE_USE_LAME_AUDIO_FORMAT=0 -DJUCE_USE_MP3AUDIOFORMAT=0 
-DJUCE_USE_OGGVORBIS=0 -DJUCE_USE_WINDOWS_MEDIA_FORMAT=0 
-DJUCE_VST3_CAN_REPLACE_VST2=0 -DJUCE_WEB_BROWSER=0 -DJucePlugin_AAXCategory=0 
-DJucePlugin_AAXDisableBypass=0 -DJucePlugin_AAXDisableMultiMono=0 
-DJucePlugin_AAXIdentifier=com.IEM.AllRADecoder 
-DJucePlugin_AAXManufacturerCode=JucePlugin_ManufacturerCode 
-DJucePlugin_AAXProductId=JucePlugin_PluginCode 
-DJucePlugin_ARACompatibleArchiveIDs=\"\" -DJucePlugin_ARAContentTypes=0 
-DJucePlugin_ARADocumentArchiveID=\"com.IEM.AllRADecoder.aradocumentarchive.1\" 
-DJucePlugin_ARAFactoryID=\"com.IEM.AllRADecoder.arafactory.0.9.2\" 
-DJucePlugin_ARATransformationFlags=0 
-DJucePlugin_AUExportPrefix=AllRADecoderAU 
-DJucePlugin_AUExportPrefixQuoted=\"AllRADecoderAU\" 
-DJucePlugin_AUMainType="'aufx'" 
-DJucePlugin_AUManufacturerCode=JucePlugin_ManufacturerCode 
-DJucePlugin_AUSubType=JucePlugin_PluginCode -DJucePlugin_Build_AAX=0 
-DJucePlugin_Build_AU=0 -DJucePlugin_Build_AUv3=0 -DJucePlugin_Build_LV2=0 
-DJucePlugin_Build_Standalone=1 -DJucePlugin_Build_Unity=0 
-DJucePlugin_Build_VST3=0 -DJucePlugin_Build_VST=1 
-DJucePlugin_CFBundleIdentifier=com.IEM.AllRADecoder 
-DJucePlugin_Desc=\"AllRADecoder\" -DJucePlugin_EditorRequiresKeyboardFocus=0 
-DJucePlugin_Enable_ARA=0 -DJucePlugin_IsMidiEffect=0 -DJucePlugin_IsSynth=0 
-DJucePlugin_Manufacturer=\"IEM\" -DJucePlugin_ManufacturerCode=0x49454d41 
-DJucePlugin_ManufacturerEmail=\"\" -DJucePlugin_ManufacturerWebsite=\"\" 
-DJucePlugin_Name=\"AllRADecoder\" -DJucePlugin_PluginCode=0x416c5261 
-DJucePlugin_ProducesMidiOutput=0 -DJucePlugin_VSTCategory=kPlugCategEffect 
-DJucePlugin_VSTNumMidiInputs=16 -DJucePlugin_VSTNumMidiOutputs=16 
-DJucePlugin_VSTUniqueID=JucePlugin_PluginCode -DJucePlugin_Version=0.9.2 
-DJucePlugin_VersionCode=0x902 -DJucePlugin_VersionString=\"0.9.2\" 
-DJucePlugin_Vst3Category=\"Fx\" -DJucePlugin_WantsMidiInput=0 -DLINUX=1 
-DNDEBUG=1 -D_NDEBUG=1 -I/<>/resources 
-I/<>/obj-x86_64-linux-gnu/AllRADecoder/AllRADecoder_artefacts/JuceLibraryCode
 -I/<>/AllRADecoder/Source -I/usr/include/libpng16 
-I/<>/obj-x86_64-linux-gnu/juce_binarydata_LAF_fonts/JuceLibraryCode
 -I/usr/share/juce/modules 
-I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK 
-I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/lv2 
-I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/serd 
-I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/sord 
-I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/sord/src 
-I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/sratom 
-I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/lilv 
-I/usr/share/juce/modules/juce_audio_processors/format_types/LV2_SDK/lilv/src 
-I/usr/include/freetype2 -isystem 
/usr/share/juce/modules/juce_audio_processors/format_types/VST3_SDK -g -O2 
-ffile-
prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DJUCE_JACK=1 
-DJUCE_MODAL_LOOPS_PERMITTED=1 -fPIC -fvisibility=hidden 
-fvisibility-inlines-hidden -MD -MT 
AllRADecoder/CMakeFiles/AllRADecoder.dir/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.cpp.o
 -MF 
CMakeFiles/AllRADecoder.dir/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.cpp.o.d
 -o 
CMakeFiles/AllRADecoder.dir/usr/share/juce/modules/juce_audio_utils/juce_audio_utils.cpp.o
 -c /usr/share/juce/modules/juce_audio_utils/juce_audio_utils.cpp
In file included from 

Bug#1025213: Extra info

[Gert van de Kraats]

I installed  all mesa-packages of previous installed version 22.2.0-1.
I also installed previous installed kernel 5.19.11-1.
With these versions the problem still existed.

Bug#1027119: yara: FTBFS: FAIL: test-magic

[Sebastian Ramacher]

Source: yara
Version: 4.2.3-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=yara&arch=amd64&ver=4.2.3-2&stamp=1672148217&raw=0

FAIL: test-magic


failed to compile rule << import "magic" rule test { condition:   
magic.type() contains "PE32+ executable" and   ( magic.mime_type() == 
"application/x-dosexec" or magic.mime_type() == 
"application/vnd.microsoft.portable-executable" } >>: line 1: syntax error
FAIL test-magic (exit status: 1)

Cheers
-- 
Sebastian Ramacher

Bug#1027118: zabbix: FTBFS: error: invalid use of void expression

[Sebastian Ramacher]

Source: zabbix
Version: 1:6.0.10+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=zabbix&arch=amd64&ver=1%3A6.0.10%2Bdfsg-1%2Bb1&stamp=1672133685&raw=0

simple.c: In function ‘check_https’:
simple.c:180:65: error: invalid use of void expression
  180 | if (CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_USERAGENT, "Zabbix " ZABBIX_VERSION)) ||
  | ^
simple.c:181:69: error: invalid use of void expression
  181 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_URL, https_host)) ||
  | ^
simple.c:182:69: error: invalid use of void expression
  182 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_PORT, (long)port)) ||
  | ^
simple.c:183:69: error: invalid use of void expression
  183 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_NOBODY, 1L)) ||
  | ^
simple.c:184:69: error: invalid use of void expression
  184 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_SSL_VERIFYPEER, 0L)) ||
  | ^
simple.c:185:69: error: invalid use of void expression
  185 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_SSL_VERIFYHOST, 0L)) ||
  | ^
simple.c:186:69: error: invalid use of void expression
  186 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
CURLOPT_TIMEOUT, (long)timeout)) ||
  | ^
simple.c:187:69: error: invalid use of void expression
  187 | CURLE_OK != (err = curl_easy_setopt(easyhandle, opt = 
ZBX_CURLOPT_ACCEPT_ENCODING, "")))
  | ^
simple.c:196:73: error: invalid use of void expression
  196 | if (CURLE_OK != (err = curl_easy_setopt(easyhandle, opt 
= CURLOPT_INTERFACE, CONFIG_SOURCE_IP)))
  | 
^
make[6]: *** [Makefile:500: libsimplesysinfo_a-simple.o] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#1027116: golang-github-containers-buildah: FTBFS: rc/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no fi

[Sebastian Ramacher]

Source: golang-github-containers-buildah
Version: 1.28.0+ds1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=golang-github-containers-buildah&arch=amd64&ver=1.28.0%2Bds1-3%2Bb1&stamp=1672115946&raw=0

# github.com/containers/storage/drivers/btrfs
src/github.com/containers/storage/drivers/btrfs/btrfs.go:385:11: 
args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no 
field or method max_referenced)
github.com/containers/storage/drivers/copy
github.com/containers/storage/drivers/devmapper
github.com/containers/common/pkg/supplemented
database/sql/driver
github.com/containers/storage/pkg/lockfile
github.com/containers/storage/drivers/vfs
github.com/containers/storage/pkg/stringid
github.com/google/uuid
github.com/containers/storage/pkg/stringutils
github.com/containers/storage/pkg/tarlog
github.com/tchap/go-patricia/patricia
github.com/mistifyio/go-zfs
github.com/google/go-intervals/intervalset
github.com/vbatts/tar-split/tar/asm
github.com/containers/storage/pkg/truncindex
github.com/containerd/stargz-snapshotter/estargz/errorutil
golang.org/x/sync/errgroup
github.com/cyphar/filepath-securejoin
github.com/containers/image/directory/explicitfilepath
github.com/containerd/stargz-snapshotter/estargz
github.com/containers/storage/drivers/zfs
github.com/containers/image/directory
github.com/containers/image/docker/policyconfiguration
github.com/containers/image/internal/streamdigest
github.com/containers/image/internal/uploadreader
github.com/containers/image/pkg/sysregistriesv2
github.com/docker/docker-credential-helpers/credentials
golang.org/x/sys/execabs
golang.org/x/net/internal/socks
github.com/docker/docker-credential-helpers/client
github.com/docker/go-connections/tlsconfig
github.com/containers/image/pkg/docker/config
golang.org/x/net/proxy
github.com/docker/distribution/registry/api/errcode
github.com/docker/go-connections/sockets
github.com/docker/distribution/digestset
github.com/gorilla/mux
github.com/docker/distribution/reference
github.com/containers/image/pkg/tlsclientconfig
github.com/docker/distribution/registry/client/auth/challenge
gopkg.in/yaml.v2
github.com/containers/image/docker/internal/tarfile
github.com/docker/docker/api/types/blkiodev
github.com/docker/distribution/registry/api/v2
github.com/docker/docker/api/types/mount
github.com/docker/docker/api/types/strslice
github.com/docker/go-connections/nat
github.com/docker/docker/api/types/container
github.com/docker/docker/api/types/filters
github.com/containers/image/docker/archive
github.com/docker/docker/api/types/registry
github.com/gogo/protobuf/proto
github.com/docker/docker/api/types/network
github.com/docker/docker/api/types/time
github.com/docker/docker/errdefs
net/http/httputil
github.com/containers/image/oci/internal
github.com/containers/image/oci/layout
github.com/sylabs/sif/pkg/sif
github.com/containers/image/oci/archive
github.com/ghodss/yaml
github.com/containers/image/docker
github.com/containers/image/tarball
github.com/containers/image/sif
github.com/opencontainers/runc/libcontainer/utils
github.com/opencontainers/runc/libcontainer/apparmor
text/template/parse
github.com/containers/common/pkg/apparmor/internal/supported
github.com/containers/common/pkg/capabilities
github.com/containers/common/pkg/cgroupv2
github.com/containers/common/pkg/util
github.com/containers/common/pkg/download
github.com/containers/common/pkg/timetype
github.com/containers/common/pkg/retry
github.com/containers/common/pkg/filters
github.com/containers/common/pkg/signal
github.com/chzyer/readline
text/template
github.com/lunixbochs/vtclean
github.com/juju/ansiterm/tabwriter
github.com/mattn/go-isatty
github.com/mattn/go-colorable
github.com/juju/ansiterm
github.com/manifoldco/promptui/list
github.com/containers/common/pkg/apparmor
github.com/manifoldco/promptui/screenbuf
github.com/disiqueira/gotree
github.com/docker/docker/api/types/swarm/runtime
database/sql
github.com/containers/common/pkg/config
github.com/manifoldco/promptui
github.com/docker/docker/api/types/swarm
github.com/docker/docker/api/types
github.com/containers/image/pkg/shortnames
github.com/docker/docker/api/types/volume
github.com/docker/docker/client
github.com/seccomp/libseccomp-golang
github.com/containers/buildah/docker
github.com/containers/ocicrypt/helpers
github.com/jinzhu/copier
github.com/containers/common/pkg/parse
github.com/containers/image/pkg/blobcache
github.com/containers/buildah/pkg/chrootuser
github.com/containers/buildah/pkg/blobcache
github.com/containers/buildah/pkg/overlay
golang.org/x/crypto/chacha20
golang.org/x/crypto/curve25519/internal/field
golang.org/x/crypto/internal/poly1305
golang.org/x/crypto/blowfish
golang.org/x/crypto/curve25519
github.com/containerd/containerd/pkg/userns
golang.org/x/crypto/ssh/internal/bcrypt_pbkdf
github.com/containers/image/docker/daemon
github.com/contain

Bug#1027115: gobgp: FTBFS: unknown error

[Sebastian Ramacher]

Source: gobgp
Version: 2.34.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=gobgp&arch=amd64&ver=2.34.0-1%2Bb4&stamp=1672114096&raw=0


/<>/obj-x86_64-linux-gnu/src/google.golang.org/protobuf/types/known/timestamppb
 (from $GOPATH)
dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
github.com/osrg/gobgp/api github.com/osrg/gobgp/cmd/gobgp 
github.com/osrg/gobgp/cmd/gobgpd github.com/osrg/gobgp/internal/pkg/apiutil 
github.com/osrg/gobgp/internal/pkg/config 
github.com/osrg/gobgp/internal/pkg/table 
github.com/osrg/gobgp/internal/pkg/version 
github.com/osrg/gobgp/internal/pkg/zebra github.com/osrg/gobgp/pkg/config 
github.com/osrg/gobgp/pkg/packet/bgp github.com/osrg/gobgp/pkg/packet/bmp 
github.com/osrg/gobgp/pkg/packet/mrt github.com/osrg/gobgp/pkg/packet/rtr 
github.com/osrg/gobgp/pkg/server returned exit code 1
make: *** [debian/rules:8: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher

Bug#1027114: docker.io: FTBFS: daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced)

[Sebastian Ramacher]

Source: docker.io
Version: 20.10.21+dfsg1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=docker.io&arch=amd64&ver=20.10.21%2Bdfsg1-1%2Bb1&stamp=1672110377&raw=0

---> Making bundle: dynbinary (in bundles/dynbinary)
Building: bundles/dynbinary-daemon/dockerd-20.10.21+dfsg1
GOOS="" GOARCH="" GOARM=""
# github.com/docker/docker/daemon/graphdriver/btrfs
daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined 
(type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced)
make[1]: *** [debian/rules:114: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'

Cheers
-- 
Sebastian Ramacher

Bug#1027113: RM: childsplay -- RoQA; Python2, unmaintained

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal

This is the last external rdepend for python-all and needs to go.  It
appears unmaintained both upstream and in Debian.

Scott K

Bug#1027112: bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()'

[Sebastian Ramacher]

Source: bazel-bootstrap
Version: 4.2.3+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=bazel-bootstrap&arch=amd64&ver=4.2.3%2Bds-1%2Bb1&stamp=1671977092&raw=0

␛[1A␛[K␛[31m␛[1mERROR: ␛[0m/<>/src/main/cpp/BUILD:91:10: Linking 
src/main/cpp/client failed: (Exit 1): gcc failed: error executing command 
  (cd /tmp/bazel_hloBSNSM/out/execroot/io_bazel && \
  exec env - \
CCACHE_DISABLE=1 \
CCACHE_TEMPDIR=/<>/debian/ccachetmp \
LC_ALL=C \

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games \
PWD=/proc/self/cwd \
  /usr/bin/gcc @bazel-out/k8-dbg/bin/src/main/cpp/client-2.params)
Execution platform: //:default_host_platform
␛[32m[111 / 127]␛[0m 3 actions running
//src/main/java/com/google/devtools/build/lib/bazel:BazelServer; 5s local
JavacBootstrap .../devtools/build/singlejar/libbootstrap.jar; 2s local
JavacBootstrap .../devtools/build/buildjar/libstarlark-deps.jar; 2s local

␛[1A␛[K
␛[1A␛[K
␛[1A␛[K
␛[1A␛[K/usr/include/grpcpp/completion_queue.h:119: error: undefined reference 
to 'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 
'absl::debian3::Mutex::~Mutex()'
/usr/include/absl/synchronization/mutex.h:533: error: undefined reference to 
'absl::debian3::Mutex::Lock()'
/usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 
'absl::debian3::Mutex::Unlock()'
/usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 
'absl::debian3::Mutex::Unlock()'
/usr/include/absl/synchronization/mutex.h:533: error: undefined reference to 
'absl::debian3::Mutex::Lock()'
/usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 
'absl::debian3::Mutex::Unlock()'
/usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 
'absl::debian3::Mutex::Unlock()'
collect2: error: ld returned 1 exit status
␛[32m[111 / 127]␛[0m 3 actions running

Cheers
-- 
Sebastian Ramacher

Bug#1027111: wine: FTBFS: error: writing 56 bytes into a region of size 8

[Sebastian Ramacher]

Source: wine
Version: 7.0~repack-11
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=wine&arch=amd64&ver=7.0%7Erepack-11&stamp=1671780374&raw=0

x86_64-w64-mingw32-gcc -c -o dlls/user32/painting.cross.o 
dlls/user32/painting.c -Idlls/user32 -Iinclude -Iinclude/msvcrt -I./libs/png 
-D__WINESRC__ -D_USER32_ -D_WINABLE_ -D_UCRT -D__WINE_PE_BUILD -Wall 
-fno-strict-aliasing -Wdeclaration-after-statement -Wempty-body 
-Wignored-qualifiers -Winit-self -Wno-packed-not-aligned -Wshift-overflow=2 
-Wstrict-prototypes -Wtype-limits -Wunused-but-set-parameter -Wvla 
-Wwrite-strings -Wpointer-arith -Wlogical-op -Wabsolute-value -Wno-format 
-Wformat-overflow -Wnonnull -mcx16 -gdwarf-4 -Werror -Wdate-time -g -O2 
-ffile-prefix-map=/<>=. -Wno-array-bounds -Wno-format
dlls/user32/message.c: In function ‘unpack_message’:
dlls/user32/message.c:1428:9: error: writing 56 bytes into a region of size 8 
[-Werror=stringop-overflow=]
 1428 | memcpy( &ps->mcs, &mcs, sizeof(mcs) );
  | ^
dlls/user32/message.c:197:15: note: destination object ‘szClass’ of size 8
  197 | ULONGLONG szClass;
  |   ^~~
dlls/user32/message.c:1216:9: error: writing 56 bytes into a region of size 4 
[-Werror=stringop-overflow=]
 1216 | memcpy( &ps->cis, &cis, sizeof(cis) );
  | ^
dlls/user32/message.c:113:19: note: destination object ‘CtlType’ of size 4
  113 | UINT  CtlType;
  |   ^~~
dlls/user32/message.c:1201:9: error: writing 32 bytes into a region of size 4 
[-Werror=stringop-overflow=]
 1201 | memcpy( &ps->dls, &dls, sizeof(dls) );
  | ^
dlls/user32/message.c:103:19: note: destination object ‘CtlType’ of size 4
  103 | UINT  CtlType;
  |   ^~~
dlls/user32/message.c:1189:9: error: writing 32 bytes into a region of size 4 
[-Werror=stringop-overflow=]
 1189 | memcpy( &ps->mis, &mis, sizeof(mis) );
  | ^
dlls/user32/message.c:93:19: note: destination object ‘CtlType’ of size 4
   93 | UINT  CtlType;
  |   ^~~
dlls/user32/message.c:1176:9: error: writing 64 bytes into a region of size 4 
[-Werror=stringop-overflow=]
 1176 | memcpy( &ps->dis, &dis, sizeof(dis) );
  | ^
dlls/user32/message.c:78:19: note: destination object ‘CtlType’ of size 4
   78 | UINT  CtlType;
  |   ^~~
dlls/user32/message.c:1142:9: error: writing 80 bytes into a region of size 8 
[-Werror=stringop-overflow=]
 1142 | memcpy( &ps->cs, &cs, sizeof(cs) );
  | ^~
dlls/user32/message.c:59:19: note: destination object ‘lpCreateParams’ of size 8
   59 | ULONGLONG lpCreateParams;
  |   ^~

Cheers
-- 
Sebastian Ramacher

Bug#1019665: ruby-safe-yaml: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: ArgumentError:

[Diederik de Haas]

Control: affects -1 src:jekyll

On Mon, 26 Dec 2022 17:54:13 +0100 Lucas Nussbaum  wrote:
> On 17/12/22 at 14:51 +0100, Diederik de Haas wrote:
> > There is an upstream PR: https://github.com/dtao/safe_yaml/pull/101
> > which tried to address this, but someone who tried it still got errors.
> > 
> > Last upstream commit was from 2019-02-22 and there are several PRs open
> > and it looks like the maintainer hasn't responded to any of them for > 5
> > YEARS
> 
> Since ruby-crack no longer depends on ruby-safe-yaml, ruby-safe-yaml
> should probably just be removed from testing (and Debian)...

And with that jekyll: https://tracker.debian.org/pkg/jekyll
https://bugs.debian.org/1026427 is a bug about that.

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

Bug#1027109: RM: python-pykafka -- ROM; No reverse (b-)depends, RC buggy

[Thomas Goirand]

Package: ftp.debian.org
Severity: normal

Hi,

I used to maintain this package as a (b-)depends for python3-oslo.messaging,
but nowadays, it uses python3-confluent-kafka. I don't have any insentive
to continue to maintain this package anymore.

Cheers,

Thomas Goirand (zigo)

Bug#1027108: RM: python2.7 -- RoQA; Obsolete

[Moritz Muehlenhoff]

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

Removing the last Python 2 remnants, this will need to be forced
since there are some inter dependencies between the final bits:

- gnat-gps (Fix coming when GNAT 12 is complete: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015974#10)
- python-defaults (earlier RM bug)

Cheers,
 Moritz

Bug#1027107: RM: python-defaults -- RoQA; Obsolete

[Moritz Muehlenhoff]

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

Removing the last Python 2 remnants, this will need to be forced
since there are some inter dependencies between the final bits:

- childsplay (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936298#30)
- python-pmw (fixed in NEW)
- python-stdlib-extensions (previous RM bug)

Cheers,
 Moritz

Bug#1027106: RM: python-stdlib-extensions -- RoQA; Obsolete

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: python-stdlib-extensi...@packages.debian.org, d...@debian.org
Control: affects -1 + src:python-stdlib-extensions

Removing the last Python 2 remnants. This will need to be forced
since there are some inter dependencies between the final bits:

- There's a reverse dependency by python-pmw (has a fixed package
in NEW)
- Depends on idle-python2.7 (from src:python2.7)

Cheers,
Moritz

Bug#1027084: blhc: recognize _FORTIFY_SOURCE level 3

[Simon Ruderich]

On Tue, Dec 27, 2022 at 05:48:20PM +0100, Christian Göttsche wrote:
> Please recognize -D_FORTIFY_SOURCE=3 as fortification enabled.

Hi,

should be implemented with [1]. Please test.

Best,
Simon

[1] 
https://ruderich.org/simon/gitweb/?p=blhc/blhc.git;a=commitdiff;h=88f15389b533468857f01490368376b539a598b3
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


signature.asc
Description: PGP signature

Bug#1023830: widelands: FTBFS on s390x

[Tobias Frost]

Control: severity -1 important


On Mon, 26 Dec 2022 17:07:55 +0100 Tobias Frost  wrote:
> Control: block -1 by 1027028
> 
> FWIIW, I've requested removal of widelands on s390x. Once this is done, this 
> bug can be downgraded in severity.
> 

This has happened now. Downgrading severity to "important" to let widelands 
migrate.

-- 
tobi

Bug#1027105: gpodder: Missing '/' in .desktop file

[tony mancill]

On Tue, Dec 27, 2022 at 08:57:36PM +, Ben Morris wrote:
> Package: gpodder
> Version: 3.11.0-4
> Severity: normal
> 
> Dear Maintainer,
> 
> /usr/share/applications/gpodder.desktop contains the following line:
> 
> Exec=usr/bin/gpodder

Thank you Ben!


signature.asc
Description: PGP signature

Bug#1001503: ITP: tlswrapper -- TLS encryption wrapper

[Jérémy Lal]

I know it's a bit superficial, but an upstream release with latest changes
would make it
cleaner for the debian package (copyright and examples).

Le mar. 27 déc. 2022 à 21:59, Jan Mojzis  a écrit :

> Hi,
>
> > The examples are interesting, maybe tlswrapper documentation should
> include them.
> > I can sponsor this, but I have a feeling that won't be accepted before
> freeze. Let's see.
>
> Examples are taken from the upstream repo and from the manual pages,
> I edited the upstream README.md to link to these examples.
>
> >
> > For the salsa repo: let's keep using yours for now, and see in which
> team it should go later.
>
> OK
>
>

Bug#1027094: FTBFS against bind9 9.18.10

[Bernhard Schmidt]

Control: forwarded -1 https://pagure.io/bind-dyndb-ldap/issue/216

On 27/12/22 06:16 PM, Bernhard Schmidt wrote:

Hi,

so this is really massively broken :-(


> ../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
>21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
>   | ^~~

That one has been introduced in 9.18.9+. There is an open pull request
upstream at https://pagure.io/bind-dyndb-ldap/pull-request/215 , which
(together with bumping LIBDNS_VERSION_MAJOR in
d/p/hardcode-version.diff) fixes the logging errors.

> ../../src/ldap_driver.c: In function ‘allrdatasets’:
> ../../src/ldap_driver.c:474:71: error: passing argument 5 of 
> ‘dns_db_allrdatasets’ makes integer from pointer without a cast 
> [-Werror=int-conversion]
>   474 | return dns_db_allrdatasets(ldapdb->rbtdb, node, version, now, 
> iteratorp);
>   |   
> ^
>   |   
> |
>   |   
> dns_rdatasetiter_t ** {aka struct dns_rdatasetiter **}

Those appear to be new issues in 9.18.10. I have filed a new upstream
bugreport at https://pagure.io/bind-dyndb-ldap/issue/216 . Both
dns_db_allrdatasets and dns_zt_apply gained an additional argument

https://gitlab.isc.org/isc-projects/bind9/-/commit/1de9c052107a6f24e565441f53e4d8b33bb2e30a
https://gitlab.isc.org/isc-projects/bind9/-/commit/6f998bbe518ae629685404bcfddcfd6067176660

and while my attempts to monkeypatch the additional 0 argument into
dns_db_allrdatasets cleared most of the warnings I'm lost with the
remaining errors. Does not really help that I barely know C, my
knowledge ends pretty much here and I have no idea how to go further.

In file included from ../../src/zone_register.h:8,
 from ../../src/ldap_convert.c:28:
/usr/include/dns/zt.h:171:28: error: unknown type name ‘isc_rwlocktype_t’; did 
you mean ‘isc_rwlock_t’?
  171 | dns_zt_apply(dns_zt_t *zt, isc_rwlocktype_t lock, bool stop, 
isc_result_t *sub,
  |^~~~
  |isc_rwlock_t


libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror -std=gnu99 -O2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-uninitialized -fvisibility=hidden 
-fno-delete-null-pointer-checks -std=gnu11 -c ../../src/ldap_helper.c  -fPIC 
-DPIC -o .libs/ldap_la-ldap_helper.o
../../src/ldap_driver.c:950:9: error: initialization of ‘isc_result_t 
(*)(dns_db_t *, dns_dbnode_t *, dns_dbversion_t *, unsigned int,  
isc_stdtime_t,  dns_rdatasetiter_t **)’ {aka ‘enum isc_result (*)(struct dns_db 
*, void *, void *, unsigned int,  unsigned int,  struct dns_rdatasetiter **)’} 
from incompatible pointer type ‘isc_result_t (*)(dns_db_t *, dns_dbnode_t *, 
dns_dbversion_t *, isc_stdtime_t,  dns_rdatasetiter_t **)’ {aka ‘enum 
isc_result (*)(struct dns_db *, void *, void *, unsigned int,  struct 
dns_rdatasetiter **)’} [-Werror=incompatible-pointer-types]
  950 | allrdatasets,
  | ^~~~
../../src/ldap_driver.c:950:9: note: (near initialization for 
‘ldapdb_methods.allrdatasets’)

Bug#1027094: FTBFS against bind9 9.18.10

[Bernhard Schmidt]

On 27/12/22 09:43 PM, Santiago Vila wrote:

> > bind-dyndb-ldap has a tight dependency on the upstream version of bind9-libs
> > (built by src:bind9) and needs to be rebuilt on every new upstream version
> > until https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014503 is fixed.
> 
> Hello. I suppose this is the reason it does not build in stable either.
> 
> Should we use the "found" directive with this bug,
> or it is better to file it as a separate bug?

I suspect this is a different bug (possibly for the same reason, changed
API within a stable release of bind9, but since the breaking code is
very fresh I doubt the same thing affects stable). So better file a new
one.

Bernhard

Bug#1001503: ITP: tlswrapper -- TLS encryption wrapper

[Jan Mojzis]

Hi,

> The examples are interesting, maybe tlswrapper documentation should include 
> them.
> I can sponsor this, but I have a feeling that won't be accepted before 
> freeze. Let's see.

Examples are taken from the upstream repo and from the manual pages,
I edited the upstream README.md to link to these examples.

> 
> For the salsa repo: let's keep using yours for now, and see in which team it 
> should go later.

OK

Bug#1027105: gpodder: Missing '/' in .desktop file

[Ben Morris]

Package: gpodder
Version: 3.11.0-4
Severity: normal

Dear Maintainer,

/usr/share/applications/gpodder.desktop contains the following line:

Exec=usr/bin/gpodder

/usr/share/applications/gpodder-url-handler.desktop has a similar
problem:

Exec=usr/bin/gpodder -s %u

Note that both paths start with "usr/" instead of "/usr/".

This causes Plasma to fail to launch gPodder with the message "Could not
find the program 'usr/bin/gpodder'" (presumably, other launchers are
affected similarly).


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

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

Versions of packages gpodder depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.4-1
ii  dbus-x11 [dbus-session-bus]   1.14.4-1
ii  gir1.2-gtk-3.03.24.35-3
ii  python3   3.10.6-3
ii  python3-cairo 1.20.1-5
ii  python3-dbus  1.3.2-3
ii  python3-gi3.42.2-3
ii  python3-gi-cairo  3.42.2-3
ii  python3-mygpoclient   1.9-1
ii  python3-podcastparser 0.6.9-1
ii  python3-requests  2.28.1+dfsg-1

Versions of packages gpodder recommends:
ii  gir1.2-ayatanaappindicator3-0.1  0.5.91-1
ii  libgpod4 0.8.3-17
ii  python3-eyed30.8.10-4
ii  python3-html5lib 1.1-3
ii  python3-simplejson   3.18.0-1

Versions of packages gpodder suggests:
pn  gnome-bluetooth | bluez-gnome  
ii  mplayer2:1.4+ds1-3+b2
ii  yt-dlp 2022.11.11-1

-- no debconf information

Bug#1025530: (no subject)

[Jacob Alexander Tice]

Blocking proper system updates, can't the i386 version be rolled back until 
all other versions are compilable?


--
Sent with Vivaldi Mail. Download Vivaldi for free at vivaldi.com

Bug#1027094: FTBFS against bind9 9.18.10

[Santiago Vila]

El 27/12/22 a las 18:16, Bernhard Schmidt escribió:

Source: bind-dyndb-ldap
Version: 11.10-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: team+...@tracker.debian.org

bind-dyndb-ldap has a tight dependency on the upstream version of bind9-libs
(built by src:bind9) and needs to be rebuilt on every new upstream version
until https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014503 is fixed.


Hello. I suppose this is the reason it does not build in stable either.

Should we use the "found" directive with this bug,
or it is better to file it as a separate bug?

Thanks.

Bug#1027103: virtualbox-ext-pack: Hash mismatch Oracle_VM_VirtualBox_Extension_Pack-6.1.40.vbox-extpack

[Nelson Suniaga Romero]

Package: virtualbox-ext-pack
Version: 6.1.40-1~fto11+1
Severity: normal
X-Debbugs-Cc: nelson.suni...@gmail.com

Dear Maintainer,

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

   * What led up to the situation? The Oracle package
https://download.virtualbox.org/virtualbox/6.1.40/Oracle_VM_VirtualBox_Extension_Pack-6.1.40.vbox-
extpack doesn't have the expected hash by Debian APT.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Nothing.
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'proposed-updates'), (500, 'stable'), (100, 'bullseye-fasttrack'), (100,
'bullseye-backports-staging')
Architecture: amd64 (x86_64)

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

Versions of packages virtualbox-ext-pack depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  virtualbox 6.1.40-dfsg-1~fto11+1
ii  wget   1.21-1+deb11u1

virtualbox-ext-pack recommends no packages.
nelson@slimshadygray:~$ sudo apt install virtualbox-ext-pack
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  virtualbox-ext-pack
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 14.0 kB of archives.
After this operation, 142 kB of additional disk space will be used.
Get:1 https://fasttrack.debian.net/debian-fasttrack bullseye-fasttrack/contrib 
amd64 virtualbox-ext-pack all 6.1.40-1~fto11+1 [14.0 kB]
Fetched 14.0 kB in 1s (9,871 B/s)   
Preconfiguring packages ...
Selecting previously unselected package virtualbox-ext-pack.
(Reading database ... 555669 files and directories currently installed.)
Preparing to unpack .../virtualbox-ext-pack_6.1.40-1~fto11+1_all.deb ...
License has already been accepted.
Unpacking virtualbox-ext-pack (6.1.40-1~fto11+1) ...
Setting up virtualbox-ext-pack (6.1.40-1~fto11+1) ...
virtualbox-ext-pack: downloading: 
https://download.virtualbox.org/virtualbox/6.1.40/Oracle_VM_VirtualBox_Extension_Pack-6.1.40.vbox-extpack
The file will be downloaded into /usr/share/virtualbox-ext-pack
Hash mismatch Oracle_VM_VirtualBox_Extension_Pack-6.1.40.vbox-extpack: expected 
29cf8410e2514ea4393f63f5e955b8311787873679fc23ae9a897fb70ef3f84a, removing the 
file.
dpkg: error processing package virtualbox-ext-pack (--configure):
 installed virtualbox-ext-pack package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
 virtualbox-ext-pack
E: Sub-process /usr/bin/dpkg returned an error code (1)
nelson@slimshadygray:~$

Bug#1027102: openssl: CVE-2022-3996: X.509 Policy Constraints Double Locking

[Salvatore Bonaccorso]

Source: openssl
Version: 3.0.7-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for openssl.

As this is a low severity issue it is basically sufficient to have it
fixed once 3.0.8 is released, just filling for tracking in the BTS.

CVE-2022-3996[0]:
| If an X.509 certificate contains a malformed policy constraint and
| policy processing is enabled, then a write lock will be taken twice
| recursively. On some operating systems (most widely: Windows) this
| results in a denial of service when the affected process hangs. Policy
| processing being enabled on a publicly facing server is not considered
| to be a common setup. Policy processing is enabled by passing the
| `-policy' argument to the command line utilities or by calling either
| `X509_VERIFY_PARAM_add0_policy()' or
| `X509_VERIFY_PARAM_set1_policies()' functions.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-3996
https://www.cve.org/CVERecord?id=CVE-2022-3996
[1] https://www.openssl.org/news/secadv/20221213.txt

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1027101: coreutils: wc: -c no longer optimises to st_size for regular files

[наб]

Package: coreutils
Version: 9.1-1
Severity: normal

Dear Maintainer,

This is a regression against 8.32-4+b1 (bullseye).

To repro this, run truncate -s 2E a, then wc -c a;
this completes instantly on bullseye and spins in a read(2) loop on sid.

Found as part of #1027100.

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-2
ii  libattr1 1:2.5.1-3
ii  libc62.36-6
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b3

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#1025910: libcommons-net-java: CVE-2021-37533

[tony mancill]

On Tue, Dec 27, 2022 at 07:55:52PM +0100, Markus Koschany wrote:
> Hello tony,
> 
> 
> Am Dienstag, dem 27.12.2022 um 08:40 -0800 schrieb tony mancill:
> > On Sun, Dec 11, 2022 at 09:02:16PM +0100, Salvatore Bonaccorso wrote:
> > > Source: libcommons-net-java
> > > Version: 3.6-1
> > > Severity: important
> > > Tags: security upstream
> > > Forwarded: https://issues.apache.org/jira/browse/NET-711
> > > X-Debbugs-Cc: car...@debian.org, Debian Security Team
> > > 
> > 
> > I see that there has been an upload of 3.9.0 on 2022-12-26.
> > 
> > I'm just noting here that I prepared a 3.9.0 package locally but hadn't
> > uploaded it yet because several of the build r-deps failed to compile.
> > (Maybe I was just doing it wrong, but we may see some FTBFS.)
> 
> I noticed two FTBFS of wagon and nrepl-clojure. Both of them seemed unrelated
> to me. I guess they will be fixed eventually. Everything else built fine. 
> Sorry
> for the double work.

Hey Markus,

No problem with the double-work.  I could have (and should have) claimed
the bug as an owner.

I double-checked that I could run ratt against 3.6.0 successfully, but
not against 3.9.0, but the reason for the build failure wasn't clear to
me either.  (My initial impression was that we're missing some transitive
includes because we don't have org.apache.ftpserver:ftpserver-core, but
I haven't followed up on it yet.)

Best regards, and *thank you* for handling the update!
tony


signature.asc
Description: PGP signature

Bug#1025096: nanoc: FTBFS in bullseye, and will also FTBFS in bookworm next year

[Santiago Vila]

reopen 1025096
found 1025096 4.11.23-1
fixed 1025096 4.12.14-1
thanks

Please consider fixing this in stable as well.

I attach a proposal for a 4.11.23-1+deb11u1 version,
which is just a backport of the fix applied in 4.12.14-1.

Thanks.diff -Nru nanoc-4.11.23/debian/changelog nanoc-4.11.23/debian/changelog
--- nanoc-4.11.23/debian/changelog  2021-02-06 15:28:54.0 +0100
+++ nanoc-4.11.23/debian/changelog  2022-12-23 15:24:01.0 +0100
@@ -1,3 +1,9 @@
+nanoc (4.11.23-1+deb11u1) bullseye; urgency=medium
+
+  * Disable test that checks for the current year (Closes: #1025096)
+
+ -- Antonio Terceiro   Fri, 23 Dec 2022 11:24:01 -0300
+
 nanoc (4.11.23-1) unstable; urgency=medium
 
   * New upstream version 4.11.23
diff -Nru 
nanoc-4.11.23/debian/patches/0018-Disable-test-that-requires-a-given-file-to-contain-t.patch
 
nanoc-4.11.23/debian/patches/0018-Disable-test-that-requires-a-given-file-to-contain-t.patch
--- 
nanoc-4.11.23/debian/patches/0018-Disable-test-that-requires-a-given-file-to-contain-t.patch
1970-01-01 01:00:00.0 +0100
+++ 
nanoc-4.11.23/debian/patches/0018-Disable-test-that-requires-a-given-file-to-contain-t.patch
2022-12-23 15:24:01.0 +0100
@@ -0,0 +1,21 @@
+From: Antonio Terceiro 
+Date: Fri, 23 Dec 2022 11:20:14 -0300
+Subject: Disable test that requires a given file to contain the current year
+
+This is a time bomb for any downstream distributors
+
+Forwarded: not-needed
+---
+ nanoc-core/spec/nanoc/core_spec.rb | 1 +
+ 1 file changed, 1 insertion(+)
+
+--- a/nanoc-core/spec/nanoc/core_spec.rb
 b/nanoc-core/spec/nanoc/core_spec.rb
+@@ -4,6 +4,7 @@
+ 
+ describe Nanoc::Core do
+   it 'has up-to-date version information' do
++skip "This is a time bomb for downstream distributors"
+ current_year = Date.today.year
+ expect(described_class.version_information).to match(/–#{current_year} /)
+   end
diff -Nru nanoc-4.11.23/debian/patches/series 
nanoc-4.11.23/debian/patches/series
--- nanoc-4.11.23/debian/patches/series 2021-02-06 15:28:54.0 +0100
+++ nanoc-4.11.23/debian/patches/series 2022-12-23 15:24:01.0 +0100
@@ -15,3 +15,4 @@
 0015-nanoc-core-skip-tests-that-fail-under-autopkgtest.patch
 0016-filesystem_spec-skip-tests-that-fail-on-debian.patch
 0017-nanoc-core-require-nanoc-version-for-test.patch
+0018-Disable-test-that-requires-a-given-file-to-contain-t.patch

Bug#1027100: coreutils: wc: total overflows unchecked

[наб]

Package: coreutils
Version: 8.32-4+b1
Severity: normal

Dear Maintainer,

-- >8 --
$ truncate -s 2E a
$ wc -c a a a a a a a | uniq -c
   7  2305843009213693952 a
   1 16140901064495857664 total
$ wc -c a a a a a a a a | uniq -c
   8 2305843009213693952 a
   1   0 total
$ wc -c a a a a a a a a a | uniq -c
   9 2305843009213693952 a
   1 2305843009213693952 total
$ wc -c a a a a a a a a a a | uniq -c
  10 2305843009213693952 a
   1 4611686018427387904 total
-- >8 --

Which is obviously wrong. One of the sensible solutions would be to just
saturate the totals, which would yield:
-- >8 --
$ wc -c a a a a a a a | uniq -c
  7  2305843009213693952 a
  1 16140901064495857664 total
$ wc -c a a a a a a a a | uniq -c
  8 2305843009213693952 a
  1 18446744073709551615 total
$ wc -c a a a a a a a a a | uniq -c
  9 2305843009213693952 a
  1 18446744073709551615 total
$ wc -c a a a a a a a a a a | uniq -c
 10 2305843009213693952 a
  1 18446744073709551615 total
-- >8 --

Which is just about the best solution here,
since this is hardly a common occurrence.

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.2.53-10
ii  libattr1 1:2.4.48-6
ii  libc62.31-13+deb11u5
ii  libgmp10 2:6.2.1+dfsg-1+deb11u1
ii  libselinux1  3.1-3

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature

Bug#990533: f2fs-tools: suggestions for the packaging

[Nicolas Boulenguez]

Source: f2fs-tools
Followup-For: Bug #990533

Hello.
Some suggestions have been applied from other sources.
The attached commits are rebased on 6b860197.
>From 529b36f439ab5445897c2399b260c0885fb79b74 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Thu, 1 Jul 2021 11:09:38 +0200
Subject: [PATCH 1/6] debian: remove get-orig-source target from debian/rules

Uscan is preferred when possible.
---
 debian/rules | 7 ---
 1 file changed, 7 deletions(-)

diff --git a/debian/rules b/debian/rules
index c106ea6..8e3aee4 100755
--- a/debian/rules
+++ b/debian/rules
@@ -19,13 +19,6 @@ execute_before_dh_install:
 	find -name "*.la" -delete
 	rm debian/tmp/sbin/sg_write_buffer
 
-get-orig-source:
-	wget http://git.kernel.org/cgit/linux/kernel/git/jaegeuk/f2fs-tools.git/snapshot/f2fs-tools-$(DEB_VERSION_UPSTREAM).tar.gz
-	gunzip < f2fs-tools-$(DEB_VERSION_UPSTREAM).tar.gz | \
-		xz > f2fs-tools-$(DEB_VERSION_UPSTREAM).tar.xz
-	rm f2fs-tools-$(DEB_VERSION_UPSTREAM).tar.gz
-	mv f2fs-tools-$(DEB_VERSION_UPSTREAM).tar.xz f2fs-tools_$(DEB_VERSION_UPSTREAM).orig.tar.xz
-
 # dh_dwz when run on f2fs-tools-udeb ends up installing the
 # /usr/lib/debug/.dwz files into the udeb.  I think that's a bug,
 # but for now, override it by just saying... just don't.
-- 
2.30.2

>From e0958c92b6d4964f6e438d4062b552ec03816a3f Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Thu, 1 Jul 2021 11:12:22 +0200
Subject: [PATCH 2/6] debian: remove redundant libdir option from
 dh_auto_configure override

---
 debian/rules | 1 -
 1 file changed, 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 8e3aee4..f514ced 100755
--- a/debian/rules
+++ b/debian/rules
@@ -12,7 +12,6 @@ include /usr/share/dpkg/default.mk
 
 override_dh_auto_configure:
 	dh_auto_configure -- --sbindir=/sbin --disable-shared \
-		--libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \
 		--with-root-libdir=/lib/$(DEB_HOST_MULTIARCH)
 
 execute_before_dh_install:
-- 
2.30.2

>From fc6730a6e26d284088808906322ca04af4c2a47d Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Thu, 1 Jul 2021 11:14:00 +0200
Subject: [PATCH 3/6] debian: stop exporting build flags from debian/rules

Dh_auto_* tools already export the build flags, whether debian/rules
knowns about them or not.

In this case, debian/rules does not need to interfer.

The test_printenv target seems to have been introduced in order to
check the removed export.
---
 debian/rules | 6 +-
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/debian/rules b/debian/rules
index f514ced..8216eb8 100755
--- a/debian/rules
+++ b/debian/rules
@@ -4,8 +4,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS ?= hardening=+all
 
-DPKG_EXPORT_BUILDFLAGS = 1
-include /usr/share/dpkg/default.mk
+include /usr/share/dpkg/architecture.mk
 
 %:
 	dh $@
@@ -23,6 +22,3 @@ execute_before_dh_install:
 # but for now, override it by just saying... just don't.
 override_dh_dwz:
 	dh_dwz -N f2fs-tools-udeb
-
-test_printenv:
-	printenv | sort
-- 
2.30.2

>From ae0819ea18e4b7c15e0c7c267d0c9d1ada1b6ef8 Mon Sep 17 00:00:00 2001
From: Nicolas Boulenguez 
Date: Fri, 5 Nov 2021 14:19:03 +0100
Subject: [PATCH 4/6] debian: prevent installation of sg_write_buffer from
 debian/not-installed

This declarative style is more readable than removal commands.
---
 debian/f2fs-tools-udeb.install | 3 ++-
 debian/f2fs-tools.install  | 4 +++-
 debian/not-installed   | 5 +
 debian/rules   | 4 
 4 files changed, 10 insertions(+), 6 deletions(-)
 create mode 100644 debian/not-installed

diff --git a/debian/f2fs-tools-udeb.install b/debian/f2fs-tools-udeb.install
index d48cf30..5779210 100644
--- a/debian/f2fs-tools-udeb.install
+++ b/debian/f2fs-tools-udeb.install
@@ -1 +1,2 @@
-/sbin
+# All but sbin/sg_write_buffer
+sbin/*f2fs*
diff --git a/debian/f2fs-tools.install b/debian/f2fs-tools.install
index c5dbdb2..1b7999a 100644
--- a/debian/f2fs-tools.install
+++ b/debian/f2fs-tools.install
@@ -1,2 +1,4 @@
-sbin/*
+# All but sbin/sg_write_buffer
+sbin/*f2fs*
+
 usr/share/man/man8/*.8
diff --git a/debian/not-installed b/debian/not-installed
new file mode 100644
index 000..5cb77ca
--- /dev/null
+++ b/debian/not-installed
@@ -0,0 +1,5 @@
+# Policy recommends not to install libtool .la files
+usr/lib/*/libf2fs*.la
+
+# See f2fs-tools.install and f2fs-tools-udeb.install
+sbin/sg_write_buffer
diff --git a/debian/rules b/debian/rules
index 8216eb8..c13326d 100755
--- a/debian/rules
+++ b/debian/rules
@@ -13,10 +13,6 @@ override_dh_auto_configure:
 	dh_auto_configure -- --sbindir=/sbin --disable-shared \
 		--with-root-libdir=/lib/$(DEB_HOST_MULTIARCH)
 
-execute_before_dh_install:
-	find -name "*.la" -delete
-	rm debian/tmp/sbin/sg_write_buffer
-
 # dh_dwz when run on f2fs-tools-udeb ends up installing the
 # /usr/lib/debug/.dwz files into the udeb.  I think that's a bug,
 # but for now, override it by just saying... just don't.
-- 
2.30.2

>From e6f63491644644f877a950a907ac7d892d925436 Mon Sep 17 00:00:00 2001
From: Nicolas Bouleng

Bug#1025910: libcommons-net-java: CVE-2021-37533

[Markus Koschany]

Hello tony,


Am Dienstag, dem 27.12.2022 um 08:40 -0800 schrieb tony mancill:
> On Sun, Dec 11, 2022 at 09:02:16PM +0100, Salvatore Bonaccorso wrote:
> > Source: libcommons-net-java
> > Version: 3.6-1
> > Severity: important
> > Tags: security upstream
> > Forwarded: https://issues.apache.org/jira/browse/NET-711
> > X-Debbugs-Cc: car...@debian.org, Debian Security Team
> > 
> 
> I see that there has been an upload of 3.9.0 on 2022-12-26.
> 
> I'm just noting here that I prepared a 3.9.0 package locally but hadn't
> uploaded it yet because several of the build r-deps failed to compile.
> (Maybe I was just doing it wrong, but we may see some FTBFS.)

I noticed two FTBFS of wagon and nrepl-clojure. Both of them seemed unrelated
to me. I guess they will be fixed eventually. Everything else built fine. Sorry
for the double work.



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

Bug#1024041: mariadb-10.6: FTBFS on riscv64: rocksdb/db/memtable.cc:129: undefined reference to `__atomic_compare_exchange_1'

[Manuel A. Fernandez Montecelo]

Hi,

On Tue, 15 Nov 2022 at 22:39, Manuel A. Fernandez Montecelo
 wrote:
>
> Source: mariadb-10.6
> Version: 1:10.6.10-1
> Followup-For: Bug #1024041
> X-Debbugs-Cc: m...@debian.org, tsu.y...@gmail.com
>
> Hi,
>
> @Otto: thanks for paying attention to the riscv64 arch, even if not one of the
>main ones [yet] :-)
>
>
> To provide info, with the patch from Bo Yu (thanks for the patch!) I can build
> successfully in hardware and in my case the tests pass fine (unless the 
> skipped
> ones cause any worry)

It would be nice if the patch could be applied to fix this problem, as
this package keeps failing with the same error, and we don't see if
there are important regressions in other areas, e.g. failures to
compile in later stages, or failing tests, etc.


Cheers.
-- 
Manuel A. Fernandez Montecelo 

Bug#1027099: gccrs-13: Broken symlink /usr/bin/gccrs-13

[John Paul Adrian Glaubitz]

Source: gcc-13
Version: 13-20221226-1
Severity: normal
User: debian-i...@lists.debian.org
Usertags: ia64
X-Debbugs-Cc: debian-i...@lists.debian.org

Hello!

I just gave it a first try with the gccrs package on ia64 and it turns
out the gccrs-13 symlink in /usr/bin is broken as shown below. Manually
invoking ia64-linux-gnu-gccrs-13 works without any problems and I can
actually compile a working program.

glaubitz@electron:~$ dpkg -l gccrs-13
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--=
ii  gccrs-13   13-20221226-1 ia64 GNU Rust compiler
glaubitz@electron:~$ gccrs-13
-bash: gccrs-13: command not found
glaubitz@electron:~$ ls -l /usr/bin/gccrs-13
lrwxrwxrwx 1 root root 21 Dec 26 16:33 /usr/bin/gccrs-13 -> 
ia64-linux-gnu-grs-13
glaubitz@electron:~$ /usr/bin/ia64-linux-gnu-gccrs-13
ia64-linux-gnu-gccrs-13: fatal error: no input files
compilation terminated.
glaubitz@electron:~$

Proof that gccrs works on ia64:

glaubitz@electron:~$ cat rust42.rs
fn main() -> i32 {
return 42;
}
glaubitz@electron:~$ ia64-linux-gnu-gccrs-13 
-frust-incomplete-and-experimental-compiler-do-not-use rust42.rs -o rust42
glaubitz@electron:~$ ./rust42 
glaubitz@electron:~$ echo $?
42
glaubitz@electron:~$

Thanks,
Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1027098: vagrant: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: expect(env).to receive(:[]=).with(:machine_ssh_info, host: "ADDRESS")

[Antonio Terceiro]

Source: vagrant
Version: 2.2.19+dfsg-3
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
vagrant failed to build.

Relevant part of the build log (hopefully):
>  Failure/Error: expect(env).to receive(:[]=).with(:machine_ssh_info, 
> host: "ADDRESS")
>  
>    {:ui=># @logger=# @fullname="vagrant::ui::interface", @outputters=[], @additive=true, 
> @name="interface", @path="vagrant::ui", 
> @parent=#, 
> @level=0, @trace=false>, @opts={}, @stdin=#>, 
> @stdout=#>, @stderr=#>>, :machine=># "machine">} received :[]= with unexpected arguments
>  expected: (:machine_ssh_info, {:host=>"ADDRESS"}) (keyword 
> arguments)
>   got: (:machine_ssh_info, {:host=>"ADDRESS"}) (options 
> hash)
>  # 
> /<>/test/unit/plugins/providers/hyperv/action/read_guest_ip_test.rb:34:in
>  `block (3 levels) in '
> 
> Finished in 4 minutes 58.9 seconds (files took 1.27 seconds to load)
> 2940 examples, 3 failures, 9 pending
> 
> Failed examples:
> 
> rspec 
> /<>/test/unit/plugins/commands/package/command_test.rb:65 
> # VagrantPlugins::CommandPackage::Command#execute with single argument 
> with --output option packages default machine inside specified folder
> rspec 
> /<>/test/unit/plugins/commands/package/command_test.rb:98 
> # VagrantPlugins::CommandPackage::Command#execute with --base option and 
> option value packages vm defined within virtualbox
> rspec 
> /<>/test/unit/plugins/providers/hyperv/action/read_guest_ip_test.rb:33
>  # VagrantPlugins::HyperV::Action::ReadGuestIP with machine ID set 
> should set the host information into the env
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern test/unit/\{plugins\}/\*\*/\*_test.rb  --exclude-pattern 
> \{test/unit/vagrant/action/builtin/box_add_test.rb,test/unit/plugins/communicators/winrm/\*_test.rb,test/unit/plugins/pushes/ftp/\*_test.rb\}
>  -I/<>/debian/lib failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


vagrant.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#992792: rbldnsd: key can only be set to dash

[Marco d'Itri]

On Aug 23, neonknight  wrote:

> However, setting "key" to any other value than - (dash) will cause rbldnsd to
> be unable to start.
User error:

> invalid config:
> RBLDNSD='mycustomkey -b 127.0.0.2/530 example.net:generic:/dev/null'
> 
> output of journalctl -u rbldnsd:

But you started rbldnsd.service instead of rbldnsd@mycustomkey.service.

I will add an explanatory error message.

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#1027097: xfwm4: taskbar is visible, when using borderless fullscreen

[Beta Version]

Package: xfwm4
Version: 4.18.0-1
Severity: normal
X-Debbugs-Cc: betaversion...@gmail.com

Dear Maintainer,

after updating xfwm4 from 4.16.1-1 to 4.18.0-1 taskbar now is always visible,
when using borderless fullscreen, like when watching video fullscreen in MPV or
on youtube in browser, or playing games with borderless fullscreen. If game
uses exclusive fullscreen, taskbar is not visible.

I tried using Openbox instead of xfwm4 and with Openbox taskbar works as
expected: not visible in borderless fullsreen.

DE is LXQt.


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

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

Versions of packages xfwm4 depends on:
ii  libc6 2.36-5
ii  libcairo2 1.16.0-6
ii  libepoxy0 1.5.10-1
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1
ii  libglib2.0-0  2.74.1-2
ii  libgtk-3-03.24.34-5
ii  libpango-1.0-01.50.10+ds-1
ii  libpangocairo-1.0-0   1.50.10+ds-1
ii  libstartup-notification0  0.12-6+b1
ii  libwnck-3-0   43.0-2
ii  libx11-6  2:1.8.3-3
ii  libxcomposite11:0.4.5-1
ii  libxdamage1   1:1.1.5-2
ii  libxext6  2:1.3.4-1+b1
ii  libxfce4ui-2-04.18.0-1
ii  libxfce4util7 4.18.0-1
ii  libxfconf-0-3 4.18.0-1
ii  libxfixes31:6.0.0-2
ii  libxinerama1  2:1.1.4-3
ii  libxpresent1  1.0.0-2+b10
ii  libxrandr22:1.5.2-2+b1
ii  libxrender1   1:0.9.10-1.1
ii  libxres1  2:1.2.1-1

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

Versions of packages xfwm4 suggests:
pn  xfce4  

-- no debconf information

Bug#1027096: ruby-webmock: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: @headers = Util::Headers.normalize_headers(@headers)

[Antonio Terceiro]

Source: ruby-webmock
Version: 3.8.3-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-webmock failed to build.

Relevant part of the build log (hopefully):
>  Failure/Error: @headers = Util::Headers.normalize_headers(@headers)
> 
># received :normalize_headers with 
> unexpected arguments
>  expected: ({"A"=>"a"}) (keyword arguments)
>   got: ({"A"=>"a"}) (options hash)
>  # ./lib/webmock/response.rb:31:in `headers='
>  # ./lib/webmock/response.rb:76:in `options='
>  # ./lib/webmock/response.rb:20:in `initialize'
>  # ./spec/unit/response_spec.rb:35:in `new'
>  # ./spec/unit/response_spec.rb:35:in `block (2 levels) in  (required)>'
> 
> Finished in 5.14 seconds (files took 1.09 seconds to load)
> 3440 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/unit/request_signature_spec.rb:20 # WebMock::RequestSignature 
> initialization assigns normalized headers
> rspec ./spec/unit/response_spec.rb:33 # WebMock::Response should report 
> normalized headers
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> spec/acceptance/curb/curb_spec.rb 
> spec/acceptance/em_http_request/em_http_request_spec.rb 
> spec/acceptance/httpclient/httpclient_spec.rb 
> spec/acceptance/manticore/manticore_spec.rb 
> spec/acceptance/net_http/net_http_spec.rb 
> spec/acceptance/net_http/real_net_http_spec.rb 
> spec/acceptance/typhoeus/typhoeus_hydra_spec.rb spec/unit/api_spec.rb 
> spec/unit/errors_spec.rb 
> spec/unit/http_lib_adapters/http_lib_adapter_registry_spec.rb 
> spec/unit/http_lib_adapters/http_lib_adapter_spec.rb 
> spec/unit/matchers/hash_excluding_matcher_spec.rb 
> spec/unit/matchers/hash_including_matcher_spec.rb 
> spec/unit/rack_response_spec.rb spec/unit/request_body_diff_spec.rb 
> spec/unit/request_execution_verifier_spec.rb 
> spec/unit/request_pattern_spec.rb spec/unit/request_registry_spec.rb 
> spec/unit/request_signature_snippet_spec.rb 
> spec/unit/request_signature_spec.rb spec/unit/request_stub_spec.rb 
> spec/unit/response_spec.rb spec/unit/stub_registry_spec.rb 
> spec/unit/stub_request_snippet_spec.rb spec/unit/util/hash_counter_spec.rb 
> spec/unit/util/hash_keys_stringifier_spec.rb spec/unit/util/headers_spec.rb 
> spec/unit/util/json_spec.rb spec/unit/util/query_mapper_spec.rb 
> spec/unit/util/uri_spec.rb spec/unit/util/version_checker_spec.rb 
> spec/unit/webmock_spec.rb -c -f progress -r ./spec/spec_helper.rb failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


ruby-webmock.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#1027095: ruby-vcr: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: /<>/lib/vcr/library_hooks/webmock.rb:36:in `block in global_hook_disabled_requests': wrong number of argum

[Antonio Terceiro]

Source: ruby-vcr
Version: 6.0.0+really5.0.0-4
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-vcr failed to build.

Relevant part of the build log (hopefully):
> /<>/lib/vcr/library_hooks/webmock.rb:36:in `block in 
> global_hook_disabled_requests': wrong number of arguments (given 1, expected 
> 0) (ArgumentError)
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


ruby-vcr.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#1025907: package-update-indicator no longer alerts user to available updates

[Alf]

This Bug is caused by upgrading from packagekit_1.2.5-3_amd64.deb to 
packagekit_1.2.6-1_amd64.deb when it migrated to testing on 2022-12-07.
I downloaded the latest 1.2.5* version from 
https://snapshot.debian.org/package/packagekit/1.2.5-4/#packagekit_1.2.5-4, 
downgraded and apt-pinned it and:

-> package-update-indicator works like a charm as it used to do since long

So this Bug should be assigned to packagekit_1.2.6-1 rather.

Bug#1027094: FTBFS against bind9 9.18.10

[Bernhard Schmidt]

Source: bind-dyndb-ldap
Version: 11.10-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: team+...@tracker.debian.org

bind-dyndb-ldap has a tight dependency on the upstream version of bind9-libs
(built by src:bind9) and needs to be rebuilt on every new upstream version
until https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014503 is fixed.

This worked fine until bind9 9.18.8, but fails in 9.18.10

https://buildd.debian.org/status/fetch.php?pkg=bind-dyndb-ldap&arch=amd64&ver=11.10-1%2Bb5&stamp=1671812545&raw=0

This is rather serious as it prevents the migration of 9.18.10 to testing
which includes systemd notify support and upstream bugfixes. Also bind9 has
followed upstream security releases during bullseye already, so it will
break later if 9.18.10 misses the freeze due to this issue.

Possible commits:
https://gitlab.isc.org/isc-projects/bind9/-/compare/v9_18_8...v9_18_10?from_project_id=1

In file included from ../../src/zone_register.h:8,
 from ../../src/ldap_convert.c:28:
/usr/include/dns/zt.h:171:28: error: unknown type name ‘isc_rwlocktype_t’; did 
you mean ‘isc_rwlock_t’?
  171 | dns_zt_apply(dns_zt_t *zt, isc_rwlocktype_t lock, bool stop, 
isc_result_t *sub,
  |^~~~
  |isc_rwlock_t
make[3]: *** [Makefile:592: ldap_la-ldap_convert.lo] Error 1
make[3]: *** Waiting for unfinished jobs
In file included from ../../src/util.h:17,
 from ../../src/bindcfg.h:10,
 from ../../src/ldap_driver.c:39:
../../src/ldap_driver.c: In function ‘beginload’:
../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
   21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
  | ^~~
../../src/ldap_driver.c:220:9: note: in expansion of macro ‘fatal_error’
  220 | fatal_error("ldapdb: method beginload() should never be 
called");
  | ^~~
In file included from /usr/include/isc/util.h:312,
 from /usr/include/isc/atomic.h:22,
 from /usr/include/isc/refcount.h:19,
 from ../../src/ldap_driver.c:16:
/usr/include/isc/error.h:42:1: note: declared here
   42 | isc_error_fatal(const char *, int, const char *, const char *, ...)
  | ^~~
../../src/ldap_driver.c: In function ‘endload’:
../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
   21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
  | ^~~
../../src/ldap_driver.c:237:9: note: in expansion of macro ‘fatal_error’
  237 | fatal_error("ldapdb: method endload() should never be called");
  | ^~~
/usr/include/isc/error.h:42:1: note: declared here
   42 | isc_error_fatal(const char *, int, const char *, const char *, ...)
  | ^~~
../../src/ldap_driver.c: In function ‘dump’:
../../src/log.h:21:9: error: too few arguments to function ‘isc_error_fatal’
   21 | isc_error_fatal(__FILE__, __LINE__, __VA_ARGS__)
  | ^~~
../../src/ldap_driver.c:266:9: note: in expansion of macro ‘fatal_error’
  266 | fatal_error("ldapdb: method dump() should never be called");
  | ^~~
/usr/include/isc/error.h:42:1: note: declared here
   42 | isc_error_fatal(const char *, int, const char *, const char *, ...)
  | ^~~
../../src/ldap_driver.c: In function ‘allrdatasets’:
../../src/ldap_driver.c:474:71: error: passing argument 5 of 
‘dns_db_allrdatasets’ makes integer from pointer without a cast 
[-Werror=int-conversion]
  474 | return dns_db_allrdatasets(ldapdb->rbtdb, node, version, now, 
iteratorp);
  |   
^
  |   |
  |   
dns_rdatasetiter_t ** {aka struct dns_rdatasetiter **}
In file included from ../../src/ldap_driver.c:22:
/usr/include/dns/db.h:1162:57: note: expected ‘isc_stdtime_t’ {aka ‘unsigned 
int’} but argument is of type ‘dns_rdatasetiter_t **’ {aka ‘struct 
dns_rdatasetiter **’}
 1162 | unsigned int options, isc_stdtime_t now,
  |   ~~^~~
../../src/ldap_driver.c:474:16: error: too few arguments to function 
‘dns_db_allrdatasets’
  474 | return dns_db_allrdatasets(ldapdb->rbtdb, node, version, now, 
iteratorp);
  |^~~
/usr/include/dns/db.h:1161:1: note: declared here
 1161 | dns_db_allrdatasets(dns_db_t *db, dns_dbnode_t *node, dns_dbversion_t 
*version,
  | ^~~
../../src/ldap_driver.c: In function ‘node_isempty’:
../../src/ldap_driver.c:517:62: error: passing argument 5 of 
‘dns_db_allrdatasets’ makes integer from po

Bug#1027093: ruby-thor: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: result = Thor::LineEditor.readline(message, options)

[Antonio Terceiro]

Source: ruby-thor
Version: 1.2.1-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-thor failed to build.

Relevant part of the build log (hopefully):
>   Failure/Error: result = Thor::LineEditor.readline(message, options)
> 
> Thor::LineEditor received :readline with unexpected arguments
>   expected: ("Overwrite foo? (enter \"h\" for help) [Ynaqdhm] ", 
> {:add_to_history=>false}) (keyword arguments)
>got: ("Overwrite foo? (enter \"h\" for help) [Ynaqdhm] ", 
> {:add_to_history=>false}) (options hash)
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib/rspec/support.rb:102:in
>  `block in '
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib/rspec/support.rb:111:in
>  `notify_failure'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/error_generator.rb:348:in
>  `notify'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/error_generator.rb:332:in
>  `__raise'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/error_generator.rb:55:in
>  `raise_unexpected_message_args_error'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/message_expectation.rb:555:in
>  `raise_unexpected_message_args_error'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/proxy.rb:216:in
>  `message_received'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/proxy.rb:360:in
>  `message_received'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/method_double.rb:91:in
>  `proxy_method_invoked'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/method_double.rb:67:in
>  `block (2 levels) in define_proxy_method'
>   # ./lib/thor/shell/basic.rb:460:in `ask_simply'
>   # ./lib/thor/shell/basic.rb:85:in `ask'
>   # ./lib/thor/shell/basic.rb:290:in `block in file_collision'
>   # ./lib/thor/shell/basic.rb:289:in `loop'
>   # ./lib/thor/shell/basic.rb:289:in `file_collision'
>   # ./spec/shell/basic_spec.rb:492:in `block (4 levels) in  (required)>'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:263:in
>  `instance_exec'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:263:in
>  `block in run'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:511:in
>  `block in with_around_and_singleton_context_hooks'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:468:in
>  `block in with_around_example_hooks'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/hooks.rb:486:in
>  `block in run'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/hooks.rb:624:in
>  `run_around_example_hooks_for'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/hooks.rb:486:in
>  `run'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:468:in
>  `with_around_example_hooks'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:511:in
>  `with_around_and_singleton_context_hooks'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:259:in
>  `run'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:646:in
>  `block in run_examples'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:642:in
>  `map'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:642:in
>  `run_examples'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:607:in
>  `run'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:608:in
>  `block in run'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:608:in
>  `map'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:608:in
>  `run'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:608:in
>  `block in run'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:608:in
>  `map'
>   # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:608:in
>  `run'

Bug#1027092: ruby-stomp: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:

[Antonio Terceiro]

Source: ruby-stomp
Version: 1.4.10-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-stomp failed to build.

Relevant part of the build log (hopefully):
>  Failure/Error:
>expect(Stomp::Connection).to receive(:new).with(:hosts => [{:login 
> => 'testlogin',
>:passcode 
> => 'testpasscode',
>:host => 
> 'host.foobar.com',
>:port => 
> 12345}],
>:logger => null_logger,
>:reliable => false,
>:client_main => @cli_thread)
> 
># received :new with unexpected arguments
>  expected: ({:client_main=>#, 
> :hosts=>[{:host=>"host.foobar.com", :login=>"testlog...code=>"testpasscode", 
> :port=>12345}], :logger=>#, 
> :reliable=>false}) (keyword arguments)
>   got: ({:client_main=>#, 
> :hosts=>[{:host=>"host.foobar.com", :login=>"testlog...code=>"testpasscode", 
> :port=>12345}], :logger=>#, 
> :reliable=>false}) (options hash)
>  # ./spec/client_spec.rb:273:in `block (3 levels) in '
> 
> Finished in 0.19699 seconds (files took 0.14394 seconds to load)
> 150 examples, 7 failures
> 
> Failed examples:
> 
> rspec ./spec/client_spec.rb:138 # Stomp::Client (created with positional 
> params) should properly parse the URL provided
> rspec ./spec/client_spec.rb:159 # Stomp::Client (created with 
> non-authenticating stomp:// URL and non-TLD host) should properly parse the 
> URL provided
> rspec ./spec/client_spec.rb:181 # Stomp::Client (created with 
> non-authenticating stomp:// URL and a host with a '-') should properly parse 
> the URL provided
> rspec ./spec/client_spec.rb:203 # Stomp::Client (created with authenticating 
> stomp:// URL and non-TLD host) should properly parse the URL provided
> rspec ./spec/client_spec.rb:225 # Stomp::Client (created with authenticating 
> stomp:// URL and a host with a '-') should properly parse the URL provided
> rspec ./spec/client_spec.rb:250 # Stomp::Client (created with 
> non-authenticating stomp:// URL and TLD host) should properly parse the URL 
> provided
> rspec ./spec/client_spec.rb:272 # Stomp::Client (created with authenticating 
> stomp:// URL and non-TLD host) should properly parse the URL provided
> 
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


ruby-stomp.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#1027091: ruby-slack-notifier: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: client.post endpoint, params

[Antonio Terceiro]

Source: ruby-slack-notifier
Version: 1.5.1-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-slack-notifier failed to build.

Relevant part of the build log (hopefully):
>  Failure/Error: client.post endpoint, params
> 
># received :post with unexpected arguments
>  expected: (#, 
> {:payload=>"{\"text\":\"the message\"}"}) (keyword arguments)
>   got: (#, 
> {:payload=>"{\"text\":\"the message\"}"}) (options hash)
>  # ./lib/slack-notifier.rb:41:in `ping'
>  # ./spec/lib/slack-notifier_spec.rb:137:in `block (4 levels) in  (required)>'
> 
> Finished in 0.03858 seconds (files took 0.14786 seconds to load)
> 29 examples, 5 failures
> 
> Failed examples:
> 
> rspec ./spec/lib/slack-notifier_spec.rb:49 # Slack::Notifier#ping allows 
> sending only an attachment
> rspec ./spec/lib/slack-notifier_spec.rb:93 # Slack::Notifier#ping with a 
> default channel set uses default channel
> rspec ./spec/lib/slack-notifier_spec.rb:101 # Slack::Notifier#ping with a 
> default channel set allows override channel to be set
> rspec ./spec/lib/slack-notifier_spec.rb:112 # Slack::Notifier#ping with 
> default webhook posts with the correct endpoint & data
> rspec ./spec/lib/slack-notifier_spec.rb:127 # Slack::Notifier#ping with a 
> custom http_client set uses it
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


ruby-slack-notifier.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#1027090: ruby-slack-messenger: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:

[Antonio Terceiro]

Source: ruby-slack-messenger
Version: 2.3.4-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-slack-messenger failed to build.

Relevant part of the build log (hopefully):
>  Failure/Error:
>expect(mock_http).to receive(:post).with(
>  URI.parse("http://example.com";),
>  payload: '{"channel":"new","user":"ship","text":"hello"}'
>)
> 
># 
> received :post with unexpected arguments
>  expected: (#http://example.com>, 
> {:payload=>"{\"channel\":\"new\",\"user\":\"ship\",\"text\":\"hello\"}"}) 
> (keyword arguments)
>   got: (#http://example.com>, 
> {:payload=>"{\"channel\":\"new\",\"user\":\"ship\",\"text\":\"hello\"}"}) 
> (options hash)
>  # ./spec/lib/slack-messenger_spec.rb:72:in `block (3 levels) in  (required)>'
> 
> Finished in 0.05301 seconds (files took 0.13642 seconds to load)
> 83 examples, 6 failures
> 
> Failed examples:
> 
> rspec ./spec/end_to_end_spec.rb:83 # Slack::Messenger applies options given 
> to middleware
> rspec ./spec/lib/slack-messenger/payload_middleware/stack_spec.rb:67 # 
> Slack::Messenger::PayloadMiddleware::Stack#set creates a stack from hashes 
> passing them as opts
> rspec ./spec/lib/slack-messenger_spec.rb:40 # Slack::Messenger#ping calls 
> #post with the message as the text key in #post
> rspec ./spec/lib/slack-messenger_spec.rb:80 # Slack::Messenger#post calls the 
> middleware stack with the payload
> rspec ./spec/lib/slack-messenger_spec.rb:58 # Slack::Messenger#post uses the 
> defaults set on initialization
> rspec ./spec/lib/slack-messenger_spec.rb:69 # Slack::Messenger#post allows 
> overriding the set defaults
> 
> Randomized with seed 261
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


ruby-slack-messenger.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#1027089: ruby-simplecov: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: Coverage.start(start_arguments)

[Antonio Terceiro]

Source: ruby-simplecov
Version: 0.21.2-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-simplecov failed to build.

Relevant part of the build log (hopefully):
>  Failure/Error: Coverage.start(start_arguments)
> 
>Coverage received :start with unexpected arguments
>  expected: ({:branches=>true, :lines=>true}) (keyword arguments)
>   got: ({:branches=>true, :lines=>true}) (options hash)
>  # ./lib/simplecov.rb:354:in `start_coverage_with_criteria'
>  # ./lib/simplecov.rb:343:in `start_coverage_measurement'
>  # ./spec/simplecov_spec.rb:340:in `block (3 levels) in '
> 
> Finished in 4.22 seconds (files took 0.19229 seconds to load)
> 385 examples, 2 failures
> 
> Failed examples:
> 
> rspec ./spec/simplecov_spec.rb:329 # SimpleCov.start_coverage_measurement 
> starts coverage in lines mode by default
> rspec ./spec/simplecov_spec.rb:335 # SimpleCov.start_coverage_measurement 
> starts coverage with lines and branches if branches is activated
> 
> Randomized with seed 22418
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb  --exclude-pattern 
> ./spec/default_formatter_spec.rb,./spec/gemspec_spec.rb --format 
> documentation failed
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> mv test_projects/monorepo/.gem2deb.Gemfile.lock 
> test_projects/monorepo/Gemfile.lock
> mv test_projects/parallel_tests/.gem2deb.Gemfile.lock 
> test_projects/parallel_tests/Gemfile.lock
> mv test_projects/rails/rspec_rails/.gem2deb.Gemfile.lock 
> test_projects/rails/rspec_rails/Gemfile.lock
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


ruby-simplecov.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#1027087: ruby-rubocop-performance: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: subject(:config) { RuboCop::ConfigLoader.load_file('config/default.yml') }

[Antonio Terceiro]

Source: ruby-rubocop-performance
Version: 1.7.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-rubocop-performance failed to build. I retried with the version in
the archive, and obtained the same failure so this is not related to
ruby-rspec.

Relevant part of the build log (hopefully):
>  Failure/Error: subject(:config) { 
> RuboCop::ConfigLoader.load_file('config/default.yml') }
> 
>  RuboCop::ValidationError:
>`Performance` cops have been extracted to the `rubocop-performance` 
> gem.
>(obsolete configuration found in config/default.yml, please update it)
>  # 
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_obsoletion.rb:43:in
>  `reject_obsolete!'
>  # 
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_validator.rb:78:in
>  `check_obsoletions'
>  # 
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_validator.rb:44:in
>  `validate'
>  # 
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config.rb:49:in
>  `check'
>  # 
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config.rb:38:in
>  `create'
>  # 
> /usr/share/rubygems-integration/all/gems/rubocop-1.39.0/lib/rubocop/config_loader.rb:57:in
>  `load_file'
>  # ./spec/project_spec.rb:5:in `block (3 levels) in '
>  # ./spec/project_spec.rb:34:in `block (4 levels) in '
>  # ./spec/project_spec.rb:33:in `each'
>  # ./spec/project_spec.rb:33:in `block (3 levels) in '
> 
> Finished in 24.75 seconds (files took 2.65 seconds to load)
> 7975 examples, 5 failures
> 
> Failed examples:
> 
> rspec ./spec/project_spec.rb:40 # RuboCop Performance Project default 
> configuration file sorts configuration keys alphabetically
> rspec ./spec/project_spec.rb:22 # RuboCop Performance Project default 
> configuration file requires a nicely formatted `VersionAdded` metadata for 
> all cops
> rspec ./spec/project_spec.rb:14 # RuboCop Performance Project default 
> configuration file has a nicely formatted description for all cops
> rspec ./spec/project_spec.rb:47 # RuboCop Performance Project default 
> configuration file has a SupportedStyles for all EnforcedStyle and 
> EnforcedStyle is valid
> rspec ./spec/project_spec.rb:32 # RuboCop Performance Project default 
> configuration file has a period at EOL of description
> 
> Randomized with seed 20775
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


ruby-rubocop-performance.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#1027088: ruby-seamless-database-pool: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: master_connection = send("#{master_config[:adapter]}_connection".to_sym, master_

[Antonio Terceiro]

Source: ruby-seamless-database-pool
Version: 1.0.20-3
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-seamless-database-pool failed to build.

Relevant part of the build log (hopefully):
>  Failure/Error: master_connection = 
> send("#{master_config[:adapter]}_connection".to_sym, master_config)
> 
># received :writer_connection with 
> unexpected arguments
>  expected: ({"adapter"=>"writer", "host"=>"master_host", 
> "pool_weight"=>1, "username"=>"user"}) (keyword arguments)
>   got: ({"adapter"=>"writer", "host"=>"master_host", 
> "pool_weight"=>1, "username"=>"user"}) (options hash)
>  # 
> ./lib/active_record/connection_adapters/seamless_database_pool_adapter.rb:15:in
>  `seamless_database_pool_connection'
>  # ./spec/seamless_database_pool_adapter_spec.rb:72:in `block (2 levels) 
> in '
> 
> Finished in 0.76099 seconds (files took 0.48193 seconds to load)
> 64 examples, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/seamless_database_pool_adapter_spec.rb:38 # 
> SeamlessDatabasePoolAdapter ActiveRecord::Base extension should establish the 
> connections in the pool merging global options into the connection options
> 
> Randomized with seed 55666
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


ruby-seamless-database-pool.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#1027085: linux-image-5.10.0-20-amd64: failed to load zfs modules - after automatic update

[DoubleHP]

Package: src:linux
Version: 5.10.158-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: ben...@demaine.info

Installed this machine 12 months ago, and never did any manual update. 
Obviously, there are background automatic updates, because these kernels are 
more recent than my install:
-rw-r--r--  1 root root 6.7M  2 sept. 15:54 vmlinuz-5.10.0-18-amd64
-rw-r--r--  1 root root 6.7M 13 déc.  21:46 vmlinuz-5.10.0-20-amd64
which are not default for a machine installed in december 2021.

I rarely reboot; but last week the computer refused to reboot with message:
failed to load zfs modules

I forgot to remove QUIET option; I will record screen with quiet removed.

So:

vmlinuz-5.10.0-20-amd64 bugs

vmlinuz-5.10.0-18-amd64 works (now)

vmlinuz-5.10.0-16-amd64 had been auto-removed; and when I reinstalled it, it 
did not work. This means the bug may not be in linux-image-5.10.0-20-amd64 but 
either in a dep, or an other system utility.

When I will bring the bootlog, I will check deeper against #1015295 #1017399 
#1019544 #1022202

Issue was discussed here, but no-one have a clue about ZFS specifics:
https://forums.debian.net/viewtopic.php?p=764805

Installation had been done following
https://wiki.debian.org/ZFS
https://arstechnica.com/gadgets/2021/06/a-quick-start-guide-to-openzfs-native-encryption/

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: Dell Inc.
product_name: Latitude E6430
product_version: 01
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A24
board_vendor: Dell Inc.
board_name: 0H3MT5
board_version: A00

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 3rd Gen Core processor DRAM 
Controller [8086:0154] (rev 09)
Subsystem: Dell 3rd Gen Core processor DRAM Controller [1028:0534]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: ivb_uncore

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port [8086:0151] (rev 09) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core 
processor PCI Express Root Port [1028:0534]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00238  Data: 
Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit 
Latency L0s <256ns, L1 <8us
ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+
LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes, Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 5GT/s (downgraded), Width x16 (ok)
TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCap: CRSVisible-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- 
NROPrPrP- LTR-
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- 
EETLPPrefix-
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS- LN System CLS Not Supported, TPHComp- ExtTPHComp- 
ARIFwd-
 AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
   

Bug#1027086: ruby-rest-client: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:

[Antonio Terceiro]

Source: ruby-rest-client
Version: 2.1.0-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12

Hi,

I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-rest-client failed to build.

Relevant part of the build log (hopefully):
>  Failure/Error:
>Request.execute(options.merge(
>:method => :head,
>:url => url,
>:headers => headers,
>:log => log), &(block || @block))
> 
># received :execute with unexpected 
> arguments
>  expected: ({:headers=>{"X-Something"=>"1"}, :log=>nil, 
> :method=>:head, :password=>"mypass", :url=>"http://some/resource";, 
> :user=>"jane"}) (keyword arguments)
>   got: ({:headers=>{"X-Something"=>"1"}, :log=>nil, 
> :method=>:head, :password=>"mypass", :url=>"http://some/resource";, 
> :user=>"jane"}) (options hash)
>  # ./lib/restclient/resource.rb:60:in `head'
>  # ./spec/unit/resource_spec.rb:16:in `block (3 levels) in  (required)>'
> 
> Finished in 0.90862 seconds (files took 0.46198 seconds to load)
> 286 examples, 8 failures
> 
> Failed examples:
> 
> rspec ./spec/unit/request_spec.rb:506 # RestClient::Request class method 
> execute wraps constructor
> rspec ./spec/unit/resource_spec.rb:39 # RestClient::Resource Resource 
> delegation overrides resource headers
> rspec ./spec/unit/resource_spec.rb:19 # RestClient::Resource Resource 
> delegation POST
> rspec ./spec/unit/resource_spec.rb:29 # RestClient::Resource Resource 
> delegation PATCH
> rspec ./spec/unit/resource_spec.rb:9 # RestClient::Resource Resource 
> delegation GET
> rspec ./spec/unit/resource_spec.rb:24 # RestClient::Resource Resource 
> delegation PUT
> rspec ./spec/unit/resource_spec.rb:34 # RestClient::Resource Resource 
> delegation DELETE
> rspec ./spec/unit/resource_spec.rb:14 # RestClient::Resource Resource 
> delegation HEAD
> 
> Randomized with seed 8137
> 
> /usr/bin/ruby3.1 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed: 


The full build log is attached.

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


ruby-rest-client.log.gz
Description: application/gzip


signature.asc
Description: PGP signature

Bug#1026818: - - Welcome to National Family Auto Insurance FXqM 184.105.177.132

[Sharon Grant]

Thanks for your email!

On Fri, Dec 23, 2022 at 2:11 PM National_Family_Auto <
jros...@serv.newstarmanager.com> wrote:

>