Processing commands for cont...@bugs.debian.org:
> # Failing test has been disabled upstream.
> # I've rebuilt your package without issues with the commit applied.
> # Thanks for your work.
> forwarded 1031438 https://invent.kde.org/libraries/qca/-/merge_requests/93
Bug #1031438 [src:qca2] qca2:
Package: mps-youtube
Followup-For: Bug #952583
X-Debbugs-Cc: pitsior...@outlook.com
Speaking of progress from upstream, and only 2 days after my comment here, a
new version was released from upstream!
https://github.com/mps-youtube/yewtube/releases/tag/v2.9.4
The project was renamed to yewtube
Control: tags 1030047 + patch
Control: tags 1030047 + pending
Dear maintainer,
I've prepared an NMU for ruby-sanitize (versioned as 6.0.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Salvatore
diff -Nru
Processing control commands:
> tags 1030047 + patch
Bug #1030047 [src:ruby-sanitize] ruby-sanitize: CVE-2023-23627
Added tag(s) patch.
> tags 1030047 + pending
Bug #1030047 [src:ruby-sanitize] ruby-sanitize: CVE-2023-23627
Added tag(s) pending.
--
1030047:
Hi,
在 2023-02-21星期二的 01:16 +0200,Peter Pentchev写道:
> On Tue, Feb 21, 2023 at 12:39:53AM +0200, Peter Pentchev wrote:
> > On Mon, Feb 20, 2023 at 05:23:28PM -0500, Boyuan Yang wrote:
> > > Hi,
> > >
> > > 在 2023-02-21星期二的 00:38 +0530,Nilesh Patra写道:
> > > > On Fri, 17 Feb 2023 07:51:48 +0100
Package: python3-dateutil
Followup-For: Bug #1003044
I'm unable to replicate a matplotlib failure so far when using:
* python3-dateutil 2.8.2-1
* python3-matplotlib 3.6.3-1+b1
The repro step attempted was to open a Python interpreter session and to enter:
from matplotlib.dates import
Source: feynmf
Followup-For: Bug #1029439
Hi Thorsten,
I'm not completely sure yet (my TeX-foo isn't that great), but I have narrowed
the cause of the problem down.
It looks like the problem is something to do with the '\textlogo' command that
is used when the 'mflogo.sty' TeX package is
On Tue, Feb 21, 2023 at 12:39:53AM +0200, Peter Pentchev wrote:
> On Mon, Feb 20, 2023 at 05:23:28PM -0500, Boyuan Yang wrote:
> > Hi,
> >
> > 在 2023-02-21星期二的 00:38 +0530,Nilesh Patra写道:
> > > On Fri, 17 Feb 2023 07:51:48 +0100 Lucas Nussbaum
> > > wrote:
> > > > Source: python-zstandard
> > >
Your message dated Mon, 20 Feb 2023 23:05:05 +
with message-id
and subject line Bug#1031293: fixed in python-zstandard 0.20.0-1
has caused the Debian Bug report #1031293,
regarding augur: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.11 returned exit code
Your message dated Mon, 20 Feb 2023 23:04:42 +
with message-id
and subject line Bug#1031371: fixed in curl 7.88.1-1
has caused the Debian Bug report #1031371,
regarding curl: CVE-2023-23914 CVE-2023-23915 CVE-2023-23916
to be marked as done.
This means that you claim that the problem has
Your message dated Mon, 20 Feb 2023 23:05:05 +
with message-id
and subject line Bug#1031293: fixed in python-zstandard 0.20.0-1
has caused the Debian Bug report #1031293,
regarding conda-package-streaming: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11
Your message dated Mon, 20 Feb 2023 23:05:05 +
with message-id
and subject line Bug#1031293: fixed in python-zstandard 0.20.0-1
has caused the Debian Bug report #1031293,
regarding python-zstandard: FTBFS: ImportError: zstd C API versions mismatch;
Python bindings were not compiled/linked
Your message dated Mon, 20 Feb 2023 23:05:05 +
with message-id
and subject line Bug#1031293: fixed in python-zstandard 0.20.0-1
has caused the Debian Bug report #1031293,
regarding python-scrapy: FTBFS: ImportError: zstd C API versions mismatch;
Python bindings were not compiled/linked
Your message dated Mon, 20 Feb 2023 23:05:05 +
with message-id
and subject line Bug#1031293: fixed in python-zstandard 0.20.0-1
has caused the Debian Bug report #1031293,
regarding conda-package-handling: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.11
Your message dated Mon, 20 Feb 2023 23:05:05 +
with message-id
and subject line Bug#1031293: fixed in python-zstandard 0.20.0-1
has caused the Debian Bug report #1031293,
regarding python3-zstandard 0.19.0-3 supports only libzstd 1.5.2
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> severity 1031478 important
Bug #1031478 {Done: Lucas Nussbaum } [src:nrepl-clojure]
nrepl-clojure: FTBFS: E: Build killed with signal TERM after 150 minutes of
inactivity
Severity set to 'important' from 'serious'
> retitle 1031478
severity 1031478 important
retitle 1031478 nrepl-clojure: FTBFS: Build randomly either hangs or fails with
test errors
reopen 1031478
thanks
Hello.
I can't build this package reliably. At some point I was able to get
the "Build killed with signal TERM" error reported by Lucas.
But now that I
control: tag -1 confirmed
I have been able to confirm the test failure in an unstable/amd64
schroot environment.
Cheers,
-Hilko
Processing control commands:
> tag -1 confirmed
Bug #1031471 [src:guestfs-tools] guestfs-tools: FTBFS: make[5]: ***
[Makefile:1073: test-suite.log] Error 1
Added tag(s) confirmed.
--
1031471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031471
Debian Bug Tracking System
Contact
On Mon, Feb 20, 2023 at 05:23:28PM -0500, Boyuan Yang wrote:
> Hi,
>
> 在 2023-02-21星期二的 00:38 +0530,Nilesh Patra写道:
> > On Fri, 17 Feb 2023 07:51:48 +0100 Lucas Nussbaum
> > wrote:
> > > Source: python-zstandard
> > > Version: 0.19.0-3
> > > Severity: serious
> > > Justification: FTBFS
> > >
Hi,
在 2023-02-21星期二的 00:38 +0530,Nilesh Patra写道:
> On Fri, 17 Feb 2023 07:51:48 +0100 Lucas Nussbaum
> wrote:
> > Source: python-zstandard
> > Version: 0.19.0-3
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20230216
Package: python3-optuna
Severity: serious
Control: affects -1 python3-pandas
test_create_new_trial (both parts) sometimes fails on s390x, failing the
autopkgtest.
It might make sense to remove this package on s390x, if it isn't
reasonable to actually fix this.
Processing control commands:
> affects -1 python3-pandas
Bug #1031706 [python3-optuna] optuna: test_create_new_trial randomly fails on
s390x
Added indication that 1031706 affects python3-pandas
--
1031706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031706
Debian Bug Tracking System
Package: python3-pymatgen
Severity: serious
Control: affects -1 python3-pandas
The autopkgtest sometimes times out, and when it does, the last line is
io/tests/test_babel.py and 6 'pass' dots, implying that the 7th item hung.
All known instances are on amd64.
Processing control commands:
> affects -1 python3-pandas
Bug #1031705 [python3-pymatgen] pymatgen: 7th item of test_babel randomly hangs
autopkgtest
Added indication that 1031705 affects python3-pandas
--
1031705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031705
Debian Bug Tracking
Your message dated Mon, 20 Feb 2023 22:00:32 +0100
with message-id
and subject line Re: Bug#1031478: nrepl-clojure: FTBFS: E: Build killed with
signal TERM after 150 minutes of inactivity
has caused the Debian Bug report #1031478,
regarding nrepl-clojure: FTBFS: E: Build killed with signal TERM
Sorry on my phone, but thank you and please do go ahead with the change!
Paul Gevers schrieb am Mo., 20. Feb. 2023, 16:24:
> Control: tags -1 patch
>
> Hi,
>
> On 19-02-2023 21:22, Paul Gevers wrote:
> > On Sat, 28 Jan 2023 00:51:39 +0100 Lee Garrett
> > wrote:
> >> This is already fixed in
Package: openjdk-17-jre-headless
Followup-For: Bug #1029342
Looking at codesearch[1] for the word 'jexec', most of the contexts that appear
are from one of a few categories:
* The code of OpenJDK itself
* Scripts/code intended to run in FreeBSD environments (where 'jexec' is
used to run
On Fri, 17 Feb 2023 07:51:48 +0100 Lucas Nussbaum wrote:
> Source: python-zstandard
> Version: 0.19.0-3
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230216 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid,
Processing commands for cont...@bugs.debian.org:
> severity 1030047 grave
Bug #1030047 [src:ruby-sanitize] ruby-sanitize: CVE-2023-23627
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1030047:
Attempting to fix Pjotr's address. Pjotr: if you are reading this, could
you comment on it?
Thanks
Nilesh
On Mon, 20 Feb 2023 17:21:59 +0100 Andreas Tille wrote:
> Hi Pjotr,
>
> in contrast to the bug reporter I get in my unstable chroot
>
> ...
> [15:53:57] Checking version: bcftools
On Mon, 20 Feb 2023 at 17:37:48 +0100, Roderich Schupp wrote:
> On Mon, Feb 20, 2023 at 5:27 PM Simon McVittie <[1]s...@debian.org> wrote:
>
> > Feb 20 15:18:32 nuc8 gnome-shell[7963]: Running GNOME Shell (using
> mutter
> > 44.beta) as a X11 window and compositing manager
> >
Processing commands for cont...@bugs.debian.org:
> tags 1031478 moreinfo unreproducible
Bug #1031478 [src:nrepl-clojure] nrepl-clojure: FTBFS: E: Build killed with
signal TERM after 150 minutes of inactivity
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.
Please
tags 1031478 moreinfo unreproducible
thanks
Hi!
Thanks for the rebuild. I can't reproduce this issue on my machine, but
I see that neither DebCI (which runs the same exact testsuite, as an
autopkgtest) nor Reproducible builds [2] (which just rebuilds the
package) have had issues with this...
Processing commands for cont...@bugs.debian.org:
> owner 979090 !
Bug #979090 [avrdude] avrdude: inaccurate copyright file
Owner recorded as Milan Kupcevic .
> tags 979090 + pending
Bug #979090 [avrdude] avrdude: inaccurate copyright file
Added tag(s) pending.
> thanks
Stopping processing here.
Your message dated Mon, 20 Feb 2023 16:49:53 +
with message-id
and subject line Bug#1031688: fixed in mutter 44~beta-2
has caused the Debian Bug report #1031688,
regarding gnome-shell 44~beta crashes immediately unless mutter-common-bin is
installed
to be marked as done.
This means that you
On Mon, Feb 20, 2023 at 5:27 PM Simon McVittie wrote:
> > Feb 20 15:18:32 nuc8 gnome-shell[7963]: Running GNOME Shell (using mutter
> > 44.beta) as a X11 window and compositing manager
> >??? why X11, should be Wayland
>
> mutter is a Wayland compositor, but it's also an X11 window and
Processing control commands:
> tag -1 pending
Bug #1031688 [libmutter-12-0] gnome-shell 44~beta crashes immediately unless
mutter-common-bin is installed
Added tag(s) pending.
--
1031688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031688
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1031688 in mutter reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> reassign -1 libmutter-12-0 44~beta-1
Bug #1031688 [gnome-shell] gnome-shell 44~beta crashes immediately unless
mutter-common-bin is installed
Bug reassigned from package 'gnome-shell' to 'libmutter-12-0'.
No longer marked as found in versions gnome-shell/44~beta-1.
Control: reassign -1 libmutter-12-0 44~beta-1
Control: severity -1 grave
Control: tags -1 + experimental
Control: affects -1 + gdm3 gnome-shell
On Mon, 20 Feb 2023 at 16:41:06 +0100, Roderich Schupp wrote:
> gnome-shell (the gdm login screen) crashes immediately if
> you don't have
Processing commands for cont...@bugs.debian.org:
> severity 1031688 grave
Bug #1031688 [gnome-shell] gnome-shell 44~beta crashes immediately unless
mutter-common-bin is installed
Severity set to 'grave' from 'important'
> tags 1031688 + experimental
Bug #1031688 [gnome-shell] gnome-shell 44~beta
Hi Pjotr,
in contrast to the bug reporter I get in my unstable chroot
...
[15:53:57] Checking version: bcftools --version is >= 1.7 - ok, have 1.16
[15:53:57] Checking version: freebayes --version is >= 1.1 - ok, have 1.3.6
[15:53:57] Checking version: snpEff -version is >= 4.3 - ok, have 5.1
Your message dated Mon, 20 Feb 2023 16:20:24 +
with message-id
and subject line Bug#1031625: fixed in gdb 13.1-1
has caused the Debian Bug report #1031625,
regarding gdb: Should the upstream snapshot currently in unstable be shipped in
bookworm?
to be marked as done.
This means that you
Processing control commands:
> tags -1 patch
Bug #1029803 [command-not-found] command-not-found breaks dist-upgrade bullseye
→ bookworm
Ignoring request to alter tags of bug #1029803 to the same tags previously set
--
1029803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029803
Debian
Control: tags -1 patch
Hi,
On 19-02-2023 21:22, Paul Gevers wrote:
On Sat, 28 Jan 2023 00:51:39 +0100 Lee Garrett
wrote:
This is already fixed in unstable, but in it's current form this will
break the
upgrade path from bullseye to bookworm. The fix is trivial, adding
`'non-free-firmware':
Package: libtycho-java
Version: 1.6.0-3
Severity: serious
Justification: fais to install
Dear maintainer,
You package depends on libeclipse-osgi-util-java but that no longer
exists in unstable.
Paul
Your message dated Mon, 20 Feb 2023 14:39:24 +
with message-id
and subject line Bug#1031308: fixed in redmine 5.0.4-4
has caused the Debian Bug report #1031308,
regarding redmine FTBFS: test failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
It's possible that I missed it, but it would have been very nice if
this showed up in apt-changelog. I let this sit as an issue for a
number of days assuming it was just churn in unstable. It wasn't until
a friend mentioned they hit it too that I went looking for a bug and
found the first to
Hi Adrian,
Adrian Bunk wrote:
> Is the upstream snapshot that was binNMUed into unstable better
> than 12.1 currently in bookworm, or should bookworm stay at 12.1?
JFTR: This was not an "binNMU", it was an "NMU". Confused me initially
and had to look at https://tracker.debian.org/pkg/gdb to
On Wed, Aug 10, 2022 at 08:03:45AM +0200, Andreas Beckmann wrote:
> dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_client: Unknown
> debugging section .debug_addr
> dwz: debian/assaultcube/usr/lib/games/assaultcube/ac_server: Unknown
> debugging section .debug_addr
FWIW this kind of
Your message dated Mon, 20 Feb 2023 13:04:07 +
with message-id
and subject line Bug#1031464: fixed in python-schema-salad 8.4.20230213094415-1
has caused the Debian Bug report #1031464,
regarding python-schema-salad: FTBFS: schema_salad/ref_resolver.py:845: error:
Unused "type: ignore"
Your message dated Mon, 20 Feb 2023 13:49:46 +0100
with message-id <1541b31f6a22f216941441bcdaba5...@bzed.de>
and subject line Re: Bug#1031440: open-vm-tools: FTBFS: fuse_config.h:42:
error: "PACKAGE_VERSION" redefined [-Werror]
has caused the Debian Bug report #1031440,
regarding open-vm-tools:
Your message dated Mon, 20 Feb 2023 12:34:01 +
with message-id
and subject line Bug#1030360: fixed in diamond-aligner 2.1.1-1
has caused the Debian Bug report #1030360,
regarding diamond-aligner FTBFS on !amd64
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> tags 614497 + bookworm-ignore
Bug #614497 [doc-debian] doc-debian: The OPL-licensed documents taken from
Debian website are non-free
Added tag(s) bookworm-ignore.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
David Bremner writes:
> I don't think these are the same as previously encountered
> native-compilation related failures. I get the same / similar failures
> when running
>
> EMACS_INHIBIT_AUTOMATIC_NATIVE_COMPILATION=t emacs -q -batch -L . -l
> buttercup -f buttercup-run-discover
>
> as a
Source: libkiwix
Version: 12.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
libkiwix/experimental started to FTBFS after sid reverted to libzim-dev
8.1.0+really8.0.0-1. Please bump the version in the build-dependency to
Source: uranium
Version: 5.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
uranium/experimental started to FTBFS after Python 3.11 was made the
default (and only) Python interpreter:
dh_auto_configure -- -DGETTEXT_MSGINIT_EXECUTABLE=msginit
Hi László,
On Sun, Feb 19, 2023 at 09:08:03PM +0100, László Böszörményi (GCS) wrote:
> Hi Salvatore,
>
> On Sun, Feb 19, 2023 at 4:39 PM Salvatore Bonaccorso
> wrote:
> > The following vulnerabilities were published for tiff. Strictly
> > speaking it might be disputed to fill this as RC level,
Your message dated Mon, 20 Feb 2023 11:04:02 +
with message-id
and subject line Bug#1031466: fixed in grml2usb 0.19.2
has caused the Debian Bug report #1031466,
regarding grml2usb: FTBFS: make[2]: *** [Makefile:44: codecheck] Error 1
to be marked as done.
This means that you claim that the
Your message dated Mon, 20 Feb 2023 11:03:56 +
with message-id
and subject line Bug#1031416: fixed in grml-debootstrap 0.103
has caused the Debian Bug report #1031416,
regarding e2fsprogs: generates filesystems that grub-install doesn't recognize
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> affects 1031416 - vmdb2
Bug #1031416 [grml-debootstrap] e2fsprogs: generates filesystems that
grub-install doesn't recognize
Removed indication that 1031416 affects vmdb2
> thanks
Stopping processing here.
Please contact me if you need
Processing commands for cont...@bugs.debian.org:
> tags 1031466 + pending
Bug #1031466 [src:grml2usb] grml2usb: FTBFS: make[2]: *** [Makefile:44:
codecheck] Error 1
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1031466:
Hi There
Would you be so kind as to provide an ETA for the above mentioned bug that
was reported.
This would be greatly appreciated.
Regards
--
Andries Malan
Platform Engineer: Managed Hosting
xneelo (Pty) Ltd
SA Contact Centre: 0861 0861 08
International: +27 21 970 2000
All,
> calendar.c forks, so there is no need to regain privileges post
> setuid(). I'm kinda with tg in that setres[ug]id() makes the intent
> clearer instead of relying on uid==0 behavior.
FYI I just uploaded a new version of the package.
It turned out setres[ug]id() are not declared in the
Your message dated Mon, 20 Feb 2023 10:53:44 +0100
with message-id <20230220095344.czcirjeiv26fo...@mraw.org>
and subject line Re: Bug#1030007: installation-guide: must document
non-free-firmware support
has caused the Debian Bug report #1030007,
regarding installation-guide: must document
Your message dated Mon, 20 Feb 2023 09:48:55 +
with message-id
and subject line Bug#998206: fixed in bsdmainutils 12.1.8
has caused the Debian Bug report #998206,
regarding calendar: cronjob processes all users’ calendars as root, allowing
information disclosure
to be marked as done.
This
Processing commands for cont...@bugs.debian.org:
> unmerge 1016728
Bug #1016728 [src:freespace2] freespace2: missing B-D: pkg-config,
libglu1-mesa-dev
Bug #1012232 [src:freespace2] freespace2: missing B-D: pkg-config,
libglu1-mesa-dev
Disconnected #1016728 from all other report(s).
> reassign
Package: collectd-core
Version: 5.12.0-13
Severity: serious
Tags: patch
Hi BZ and friends,
Looks like a change in dh_installinit / dh_installsystemd made the package
loose its systemd service / init.d script.
The attached patch fixes the situation. If you have no time to build and
upload, just
Processing control commands:
> reassign -1 src:freespace2 3.7.4+repack-1.1
Bug #1012232 [autoconf] freespace2: FTBFS: ./configure: line 17040: syntax
error near unexpected token `ax_cxx_compile_cxx11_required=falsednl'
Bug #1016728 [autoconf] autoconf: _AC_PROG_CXX_STDCXX_EDITION_TRY test is
Followup-For: Bug #1012232
Control: reassign -1 src:freespace2 3.7.4+repack-1.1
Control: tag -1 sid bookworm
Control: retitle -1 freespace2: missing B-D: pkg-config, libglu1-mesa-dev
The autoconf error is a red herring.
The actual problem are missing
Build-Depends: pkg-config, libglu1-mesa-dev
71 matches
Mail list logo