Your message dated Sat, 18 Feb 2023 07:04:05 +
with message-id
and subject line Bug#1031524: fixed in fuse3 3.14.0-2
has caused the Debian Bug report #1031524,
regarding fuse3: setxattr is broken
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Hello Santiago,
Santiago Vila [2023-02-18 0:26 +0100]:
> Martin Pitt wrote:
> > The "flock: not found" is #1014662, but that is already present in our
> > current
> > image with cloud-initramfs-tools 0.18.debian8, and does not seem fatal. So
> > far
> > the "wait-for-root: not found" seems to b
Processing control commands:
> reassign -1 python3-zstandard 0.19.0-3
Bug #1031434 [src:conda-package-handling] conda-package-handling: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11
returned exit code 13
Bug reassigned from package 'src:conda-package-handlin
Control: reassign -1 python3-zstandard 0.19.0-3
Control: affects -1 + conda-package-handling
Control: forcemerge -1 1031293
On Fri, 17 Feb 2023 06:30:57 +0100 Lucas Nussbaum wrote:
> Source: conda-package-handling
> Version: 2.0.1-2
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid
On Fri, Feb 17, 2023 at 10:34:29PM +0200, Adrian Bunk wrote:
>
> The same general problem applies in various "building non-Debian
> embedded Linux filesystem on Debian" situations where the target
> chroot does not contain mkfs.ext4.
In practice, if the root file system is using ext4, the target
Your message dated Sat, 18 Feb 2023 01:05:42 +
with message-id
and subject line Bug#1031432: fixed in rhino 1.7.14-2
has caused the Debian Bug report #1031432,
regarding datatables-extensions: FTBFS: make[1]: *** [debian/rules:10:
override_dh_install] Error 254
to be marked as done.
This mea
Your message dated Sat, 18 Feb 2023 01:05:42 +
with message-id
and subject line Bug#1031432: fixed in rhino 1.7.14-2
has caused the Debian Bug report #1031432,
regarding ckeditor: FTBFS: make[1]: *** [debian/rules:24:
debian/builddir/core/ckeditor_base.min.js] Error 254
to be marked as done.
Your message dated Sat, 18 Feb 2023 01:05:42 +
with message-id
and subject line Bug#1031432: fixed in rhino 1.7.14-2
has caused the Debian Bug report #1031432,
regarding dojo: FTBFS: make[1]: *** [debian/rules:48: override_dh_auto_test]
Error 1
to be marked as done.
This means that you claim
Your message dated Sat, 18 Feb 2023 01:05:42 +
with message-id
and subject line Bug#1031432: fixed in rhino 1.7.14-2
has caused the Debian Bug report #1031432,
regarding jquery-i18n-properties: FTBFS: make[1]: *** [debian/rules:15:
override_dh_auto_build] Error 254
to be marked as done.
This
Your message dated Sat, 18 Feb 2023 01:05:42 +
with message-id
and subject line Bug#1031432: fixed in rhino 1.7.14-2
has caused the Debian Bug report #1031432,
regarding prettify.js: FTBFS: java.util.MissingResourceException: Can't find
bundle for base name com.google.javascript.rhino.head.re
Your message dated Sat, 18 Feb 2023 01:05:42 +
with message-id
and subject line Bug#1031432: fixed in rhino 1.7.14-2
has caused the Debian Bug report #1031432,
regarding mediaelement: FTBFS: FileNotFoundError: [Errno 2] No such file or
directory: '../build/mediaelement.min.js'
to be marked as
Your message dated Sat, 18 Feb 2023 00:39:51 +
with message-id
and subject line Bug#1031522: fixed in yt-dlp 2023.02.17-1
has caused the Debian Bug report #1031522,
regarding yt-dlp: Unable to extract uploader id
to be marked as done.
This means that you claim that the problem has been dealt
Control: tags -1 + pending
On Tue, 14 Feb 2023 at 14:53:34 -0500, john amidon wrote:
> I set shadowconfig to 'off' when I edited '/etc/group'
I would strongly recommend not doing this: it makes the hashed passwords
of all users visible in /etc/passwd, defeating the purpose of having
/etc/shadow,
Processing control commands:
> tags -1 + pending
Bug #1031309 [accountsservice] accountsservice: accounts-daemon service will
prevent system boot if shadowconfig is off
Added tag(s) pending.
--
1031309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031309
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> forwarded 1031309
> https://gitlab.freedesktop.org/accountsservice/accountsservice/-/merge_requests/121
Bug #1031309 [accountsservice] accountsservice: accounts-daemon service will
prevent system boot if shadowconfig is off
Set Bug forwarded-to-
Control: tag -1 pending
Hello,
Bug #1030966 in ruby-jekyll-remote-theme reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/ruby-team/ruby-jekyll-remote-theme/-/com
Processing control commands:
> tag -1 pending
Bug #1030966 [src:ruby-jekyll-remote-theme] ruby-jekyll-remote-theme accesses
the internet during the build
Added tag(s) pending.
--
1030966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030966
Debian Bug Tracking System
Contact ow...@bugs.deb
Processing commands for cont...@bugs.debian.org:
> severity 1014662 important
Bug #1014662 [cloud-initramfs-growroot] cloud-initramfs-growroot: Initramfs
hook does not include `flock` command
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you n
severity 1014662 important
thanks
Note: I'm restoring the original severity because Martin Pitt says
in #1027050 that the fatal failure is due to wait-for-root, not flock.
(However, I could not imagine an upload fixing #1027050 which
would not fix this one in the same upload as well).
Thanks.
Processing commands for cont...@bugs.debian.org:
> forcemerge 1031432 1031452
Bug #1031432 [rhino] mediaelement: FTBFS: FileNotFoundError: [Errno 2] No such
file or directory: '../build/mediaelement.min.js'
Bug #1031470 [rhino] jquery-i18n-properties: FTBFS: make[1]: ***
[debian/rules:15: overri
Processing commands for cont...@bugs.debian.org:
> severity 1027050 serious
Bug #1027050 [cloud-initramfs-growroot] growing image fails to boot:
/scripts/local-bottom/growroot: line 97: wait-for-root: not found
Severity set to 'serious' from 'important'
> tags 1027050 + patch
Bug #1027050 [cloud-
Processing control commands:
> reassign -1 rhino
Bug #1031432 [closure-compiler] mediaelement: FTBFS: FileNotFoundError: [Errno
2] No such file or directory: '../build/mediaelement.min.js'
Bug reassigned from package 'closure-compiler' to 'rhino'.
Ignoring request to alter found versions of bug #
Processing control commands:
> reassign -1 rhino
Bug #1031452 [closure-compiler] prettify.js: FTBFS:
java.util.MissingResourceException: Can't find bundle for base name
com.google.javascript.rhino.head.resources.Messages, locale en
Bug #1031458 [closure-compiler] dojo: FTBFS: make[1]: *** [debia
Control: reassign -1 rhino
I have recently updated src:rhino and it seems this is caused by the rhino
script or one of the other scripts in the rhino binary package. Initially I
assumed that the error
java.util.MissingResourceException: Can't find bundle for base name
com.google.javascript.rhino
El 17/2/23 a las 22:57, Ross Vandegrift escribió:
On Fri, Feb 17, 2023 at 09:54:08PM +0100, Santiago Vila wrote:
After applying the suggested patch, the reported error
does not show anymore.
Instead, I get this:
/scripts/local-bottom/growroot: line 97: wait-for-root: not found
Where does this
I just rebuilt ruby-github-api by relaxing the dependency on oauth2. I
pulled the test cases from github to check if anything happens. It
built just fine. 6 tests failed, but none related to OAuth2 (seems some
keywords/options mismatch).
I think we could fix this by relaxing the dep on oauth2 for
Your message dated Fri, 17 Feb 2023 23:07:06 +
with message-id
and subject line Bug#1031533: fixed in simka 1.5.3-7
has caused the Debian Bug report #1031533,
regarding simka B-D on libgatbcore-dev which doesn't exist on s390x
to be marked as done.
This means that you claim that the problem h
Your message dated Fri, 17 Feb 2023 23:05:01 +
with message-id
and subject line Bug#1031532: fixed in minia 3.2.6-3
has caused the Debian Bug report #1031532,
regarding minia B-D on libgatbcore-dev which doesn't exist on several
architectures
to be marked as done.
This means that you claim t
Your message dated Fri, 17 Feb 2023 23:04:53 +
with message-id
and subject line Bug#1031531: fixed in mindthegap 2.3.0-2
has caused the Debian Bug report #1031531,
regarding mindthegap B-D on libgatbcore-dev which doesn't exist on several
architectures
to be marked as done.
This means that y
Your message dated Fri, 17 Feb 2023 23:04:44 +
with message-id
and subject line Bug#1031530: fixed in discosnp 1:2.6.2-2
has caused the Debian Bug report #1031530,
regarding discosnp B-D on libgatbcore-dev which doesn't exist on several
architectures
to be marked as done.
This means that you
Your message dated Fri, 17 Feb 2023 23:04:03 +
with message-id
and subject line Bug#1031529: fixed in bcalm 2.2.3-4
has caused the Debian Bug report #1031529,
regarding bcalm B-D on libgatbcore-dev which doesn't exist on several
architectures
to be marked as done.
This means that you claim t
Possibly useful here: gdb disassemble works inside pocl kernels, see
#920497 for an example.
Control: tag -1 unreproducible
On Wed, 9 Feb 2005 17:12:21 +0100 Mike Hommey wrote:
> On Dec 27, 2004, Vincent Lefevre wrote:
> > Package: xsltproc
> > Version: 1.1.8-5
> >
> > Here xsltproc takes up to 138 MB, making the whole system slow down
> > due to swapping. This problem occurs when gene
Processing control commands:
> tag -1 unreproducible
Bug #287371 [xsltproc] xsltproc: DTD should be cached when included several
times, or used memory should be limited
Added tag(s) unreproducible.
--
287371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287371
Debian Bug Tracking System
Co
Gregor Riepl (2023-02-17):
> > https://www.debian.org/releases/bookworm/amd64/release-notes/ch-information.en.html#non-free-split
>
> Oh, I just saw that this page mentions that apt should have shown a
> notice to previous users of firmware-linux-nonfree, but I never saw
> this notice.
Note the
Processing commands for cont...@bugs.debian.org:
> forwarded 1031441 https://github.com/piotrmurach/github/issues/386
Bug #1031441 [src:ruby-github-api] ruby-github-api: FTBFS: ERROR: Test
"ruby3.1" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1413:in
`rescue in block in activate_
Processing commands for cont...@bugs.debian.org:
> severity 1031457 important
Bug #1031457 [src:ruby-redis] ruby-redis: FTBFS: ERROR: Test "ruby3.1" failed.
Severity set to 'important' from 'serious'
> # builds just fine
> tags 1031457 + moreinfo unreproducible
Bug #1031457 [src:ruby-redis] ruby-r
Hello Paul,
If it is better for the release, please remove my try to fix it.
Kind regards
--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F
Your message dated Fri, 17 Feb 2023 23:02:40 +0100
with message-id
and subject line Re: Bug#1031534: firmware-linux-nonfree: Package removed from
sid and bookworm
has caused the Debian Bug report #1031534,
regarding firmware-linux-nonfree: Package removed from sid and bookworm
to be marked as don
On Fri, Feb 17, 2023 at 09:54:08PM +0100, Santiago Vila wrote:
> After applying the suggested patch, the reported error
> does not show anymore.
>
> Instead, I get this:
>
> /scripts/local-bottom/growroot: line 97: wait-for-root: not found
>
> Where does this "wait-for-root" come from?
> I can't
Given that upstream changes to this package haven't been integrated in
years and this bug being pretty limiting to users, Mobian moved to
systemd-repart. If it's possible for you I might recommend the same
solution.
Our experience has been that once implemented it is far more reliable.
The sw
Package: firmware-linux-nonfree
Version: 20221214-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
With the recent upgrade to version 20230210 (or 20230117 on testing), the
package has vanished from the apt cache of two of my bookworm/sid
Your message dated Fri, 17 Feb 2023 21:49:48 +
with message-id
and subject line Bug#1031480: fixed in libreflectasm-java 1.11.9+dfsg-4
has caused the Debian Bug report #1031480,
regarding libreflectasm-java: FTBFS: make: *** [debian/rules:4: binary] Error 25
to be marked as done.
This means t
Source: simka
Version: 1.5.3-6
Severity: serious
Hi,
simka build-depends on libgatbcore-dev, but gatb-core has been recently
patched and stopped building on several architectures, including s390x.
simka's build will FTBFS on those architectures.
Thank you,
--
Sergio
GPG key ID: 237A 54B1 0287
Source: minia
Version: 3.2.6-2
Severity: serious
Hi,
minia build-depends on libgatbcore-dev, but gatb-core has been recently
patched and stopped building on several architectures, including
e.g. s390x, armhf, etc. bcalm's build will FTBFS on those
architectures.
Thank you,
--
Sergio
GPG key I
Source: mindthegap
Version: 2.3.0-1
Severity: serious
Hi,
mindthegap build-depends on libgatbcore-dev, but gatb-core has been
recently patched and stopped building on several architectures,
including e.g. s390x, armhf, etc. bcalm's build will FTBFS on those
architectures.
Thank you,
--
Sergio
Source: discosnp
Version: 1:2.6.2-1
Severity: serious
Hi,
discosnp build-depends on libgatbcore-dev, but gatb-core has been
recently patched and stopped building on several architectures,
including e.g. s390x, armhf, etc. bcalm's build will FTBFS on those
architectures.
Thank you,
--
Sergio
G
Source: bcalm
Version: 2.2.3-3
Severity: serious
Hi,
bcalm build-depends on libgatbcore-dev, but gatb-core has been recently
patched and stopped building on several architectures, including
e.g. s390x, armhf, etc. bcalm's build will FTBFS on those
architectures.
Thank you,
--
Sergio
GPG key I
Hi Gabriel,
On Thu, Feb 16, 2023 at 11:37:57PM +0100, Gabriel Corona wrote:
> Hi,
>
> Thanks for the patch!
Thanks for staying on top of the issue!
>
> This has been fixed in Debian testing and sid. However, stable is still
> affected. I believe it would make sense to port the patch to stable a
On Fri, Feb 17, 2023 at 12:43:01PM -0700, Sam Hartman wrote:
>
> I am not entirely convinced that using current rather than guest
> tools for image building is an anti-pattern. You've been working on
> filesystems for a long time; I've been working on various image
> building projects since my fi
Processing control commands:
> found -1 2.1.dfsg-1
Bug #1029260 [src:vice] vice: missing font license in d/copyright
Marked as found in versions vice/2.1.dfsg-1.
> severity -1 important
Bug #1029260 [src:vice] vice: missing font license in d/copyright
Severity set to 'important' from 'serious'
--
Control: found -1 2.1.dfsg-1
Control: severity -1 important
On Sun, Jan 29, 2023 at 4:03 PM Bastian Germann wrote:
> So if that font is not GPL-compibly licensed, CBM cannot be GPL licensed.
It's mentioned as '100% free' and was added to the VICE project in
its 1.22.9 release. The first package
After applying the suggested patch, the reported error
does not show anymore.
Instead, I get this:
/scripts/local-bottom/growroot: line 97: wait-for-root: not found
Where does this "wait-for-root" come from?
I can't find it in any package.
Thanks.
Hi,
On 17/02/23 at 20:17 +0100, Timo Röhling wrote:
> Control: tags -1 + moreinfo
>
> Hi Lucas,
>
> this seems to be bug #1030493 again.
>
> On Fri, 17 Feb 2023 07:50:37 +0100 Lucas Nussbaum wrote:
> > > E - '')]
> > > E ? ^
> > > E > E + ''),
>
On Fri, Feb 17, 2023 at 02:08:28PM -0500, Theodore Ts'o wrote:
>...
> So enabling what may be
> convenient, but ultimately an anti-pattern is something that hopefully
> in the long-term Debian should be striving towards. Yes, it's
> annoying and and extra work. So is using build chroots if we are
Processing control commands:
> affects -1 src:ostree
Bug #1031524 [src:fuse3] fuse3: setxattr is broken
Added indication that 1031524 affects src:ostree
--
1031524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: fuse3
Version: 3.13.0-1
Severity: serious
Forwarded: https://github.com/libfuse/libfuse/issues/730
Control: affects -1 src:ostree
Hi Maintainer
Since the upload of 3.13.0-1, the 'name' string passed to
fs->op.setxattr has the first 8 characters missing.
Steps to reproduce:
$ dget https:
On Wed, Feb 15, 2023 at 05:45:26AM +0800, Roy Clark (kralcyor) wrote:
> Package: libjpeg9
> Version: 1:9d-1.1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> /usr/lib/*/{libjpeg.so.9,libjpeg.so.9.4.0} are missing in the package, making
> it completely unusabl
Processing commands for cont...@bugs.debian.org:
> tags 1031509 + security upstream fixed-upstream
Bug #1031509 {Done: Sebastian Andrzej Siewior }
[clamav] clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0),
CVE-2023-20032/CVE-2023-20052
Bug #1031513 {Done: Sebastian Andrzej Siewior }
[clamav] clamav
Hi,
On 16-02-2023 23:34, Andreas Beckmann wrote:
@elbrus: Why does britney try to migrate clinfo together with pocl?
Honestly, I don't know. The logic that does that *is* rather greedy as
often it helps (but not always).
IMO clinfo should be able to migrate on its own without causing new
r
Your message dated Fri, 17 Feb 2023 19:49:38 +
with message-id
and subject line Bug#1031509: fixed in clamav 1.0.1+dfsg-1
has caused the Debian Bug report #1031509,
regarding clamav: new upstream security release, CVE-2023-20032
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 17 Feb 2023 19:49:38 +
with message-id
and subject line Bug#1031509: fixed in clamav 1.0.1+dfsg-1
has caused the Debian Bug report #1031509,
regarding clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0),
CVE-2023-20032/CVE-2023-20052
to be marked as done.
This means that you
> "Theodore" == Theodore Ts'o writes:
Theodore> So enabling what may be convenient, but ultimately an
Theodore> anti-pattern is something that hopefully in the long-term
Theodore> Debian should be trying to *avoid*.
That's certainly true.
I am not entirely convinced that using c
On Fri, Feb 17, 2023 at 02:08:28PM -0500, Theodore Ts'o wrote:
> So enabling what may be
> convenient, but ultimately an anti-pattern is something that hopefully
> in the long-term Debian should be striving towards.
Sigh, I managed to invert the sense of what I was trying to say. This
should have
Your message dated Fri, 17 Feb 2023 19:19:34 +
with message-id
and subject line Bug#1031469: fixed in botch 0.24-2
has caused the Debian Bug report #1031469,
regarding botch: FTBFS: make[2]: *** [Makefile:339: test-python] Error 1
to be marked as done.
This means that you claim that the probl
Your message dated Fri, 17 Feb 2023 19:19:56 +
with message-id
and subject line Bug#1031455: fixed in fuse3 3.14.0-1
has caused the Debian Bug report #1031455,
regarding charliecloud: FTBFS: config.h:38: error: "PACKAGE_VERSION" redefined
[-Werror]
to be marked as done.
This means that you c
Processing commands for cont...@bugs.debian.org:
> severity 1014662 serious
Bug #1014662 [cloud-initramfs-growroot] cloud-initramfs-growroot: Initramfs
hook does not include `flock` command
Severity set to 'serious' from 'important'
> tags 1014662 + patch
Bug #1014662 [cloud-initramfs-growroot] c
Processing control commands:
> tags -1 + moreinfo
Bug #1031435 [src:python-inotify] python-inotify: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) moreinfo.
--
1031435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031
Control: tags -1 + moreinfo
Hi Lucas,
this seems to be bug #1030493 again.
On Fri, 17 Feb 2023 07:50:37 +0100 Lucas Nussbaum wrote:
> E - '')]
> E ? ^
> E
> E + ''),
> E ? ^
> E
> E + (_INOTIFY_EVENT(wd=1,
Processing commands for cont...@bugs.debian.org:
> forcemerge 1031509 1031513
Bug #1031509 [clamav] clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0),
CVE-2023-20032/CVE-2023-20052
Bug #1031513 [clamav] clamav: new upstream security release, CVE-2023-20032
Severity set to 'important' from 'grave'
Mark
On Fri, Feb 17, 2023 at 08:51:33AM -0800, Russ Allbery wrote:
> Adrian Bunk writes:
>
> > The image creators could just set the features they enable to what they
> > copied from /etc/mke2fs.conf from the target distribution, a label with
> > a timestamp wouldn'tbring much benefit here.
>
> That'
Package: yt-dlp
Version: 2023.01.06-1
Severity: grave
Tags: fixed-upstream
Justification: renders package unusable
Dear Maintainer,
it seems that version 2023.01.06-1 of yt-dlp suffers from the issue
described in:
https://github.com/yt-dlp/yt-dlp/issues/6247
Upstream has provided a fix for this
Your message dated Fri, 17 Feb 2023 18:08:08 +
with message-id
and subject line Bug#1028840: fixed in weather-util 2.4.4-1
has caused the Debian Bug report #1028840,
regarding weather-util: FTBFS: ValueError: invalid mode: 'rUb'
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> forwarded 1031460
> https://github.com/Rockhopper-Technologies/enlighten/commit/1ede6ff4
Bug #1031460 [src:enlighten] enlighten: FTBFS: AssertionError: '1.00[31
chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 K[105 chars] s/B' !=
'1.00[31 ch
Processing control commands:
> forcemerge -1 1031293 1031449
Bug #1031443 [python3-zstandard] python-zstandard: FTBFS: ImportError: zstd C
API versions mismatch; Python bindings were not compiled/linked against
expected zstd version (10504 returned by the lib, 10504 hardcoded in zstd
headers, 1
Package: python3-zstandard
Followup-For: Bug #1031443
Control: forcemerge -1 1031293 1031449
Hi,
I am not the package maintainer, but this bug report is almost useless.
What's the issue? Is kaffeine not starting? Is it crashing? Or is just
not showing what you expect?
Which kind of DVB device are you using? Have you checked the device to
work with other apps?
Before flagging this
Processing commands for cont...@bugs.debian.org:
> tags 982123 + buster
Bug #982123 [src:librsvg] librsvg: FTBFS on ppc64el in buster
Added tag(s) buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
982123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982
Dear Maintainer,
After adding python3-setuptools-scm to build depends, I was able to
build your package in a sid chroot environment.
Please note that the build creates a "aiomysql/_scm_version.py" file
which prevents the next build:
...
dpkg-source: info: using options from aiomysql-0.1.1/debian
Your message dated Fri, 17 Feb 2023 17:19:48 +
with message-id
and subject line Bug#1031433: fixed in diffoscope 236
has caused the Debian Bug report #1031433,
regarding diffoscope: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.11 returned exit code 13
to be
Processing control commands:
> reassign -1 src:fuse3
Bug #1031455 [src:charliecloud] charliecloud: FTBFS: config.h:38: error:
"PACKAGE_VERSION" redefined [-Werror]
Bug reassigned from package 'src:charliecloud' to 'src:fuse3'.
No longer marked as found in versions charliecloud/0.31-1.
Ignoring re
Control: reassign -1 src:fuse3
Control: found -1 3.13.1-1
Control: forwarded -1 https://github.com/libfuse/libfuse/issues/729
Control: tags -1 + fixed-upstream
Control: affects -1 src:charliecloud
Dear Lucas,
thanks for reporting this problem. It seems that the root cause of this
FTBFS issue is
Processing commands for cont...@bugs.debian.org:
> tags 1022015 + patch
Bug #1022015 [src:elasticsearch-curator] elasticsearch-curator: Uses deprecated
yaml.load
Bug #1026566 [src:elasticsearch-curator] elasticsearch-curator: FTBFS:
TypeError: load() missing 1 required positional argument: 'Load
Your message dated Fri, 17 Feb 2023 16:57:47 +
with message-id
and subject line Bug#1030174: fixed in iminuit 2.11.2-4
has caused the Debian Bug report #1030174,
regarding iminuit FTBFS with scipy 1.10
to be marked as done.
This means that you claim that the problem has been dealt with.
If th
Adrian Bunk writes:
> The image creators could just set the features they enable to what they
> copied from /etc/mke2fs.conf from the target distribution, a label with
> a timestamp wouldn'tbring much benefit here.
That's a very good point and I'm embarrassed it wasn't immediately obvious
to me.
Processing commands for cont...@bugs.debian.org:
> merge 1031509 1031513
Bug #1031509 [clamav] clamav: 2 RCE bugs in ClamAV 0.103 (+ 1.0.0),
CVE-2023-20032/CVE-2023-20052
Unable to merge bugs because:
severity of #1031513 is 'grave' not 'important'
Failed to merge 1031509: Did not alter merged bu
Your message dated Fri, 17 Feb 2023 15:56:00 +
with message-id
and subject line Bug#1031396: fixed in pipewire 0.3.65-3
has caused the Debian Bug report #1031396,
regarding Unable to upgrade to *gnome* 1:43+1 with `apt full-upgrade`
to be marked as done.
This means that you claim that the pro
Package: clamav
Severity: grave
Hi,
As you'll likely know there is
https://security-tracker.debian.org/tracker/CVE-2023-20032 and
https://blog.clamav.net/2023/02/clamav-01038-01052-and-101-patch.html
"CVE-2023-20032: Fixed a possible remote code execution vulnerability in the
HFS+ file parser. T
Source: docbook-defguide
Severity: serious
Version: 2.0.17+svn9912-2
Some files in the package are licensed under the non-free variant of the GFDL
with explicit Invariant Section.
Please repack to remove them.
Your message dated Fri, 17 Feb 2023 14:38:35 +
with message-id
and subject line Bug#1030967: fixed in vip-manager2 2.1.0-4
has caused the Debian Bug report #1030967,
regarding vip-manager2: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been dealt wit
Processing control commands:
> tag -1 fixed-upstream pending
Bug #1029261 [dm-writeboost-dkms] dm-writeboost-dkms: module fails to build for
Linux 6.1: error: ‘struct dm_io_request’ has no member named ‘bi_op’
Added tag(s) fixed-upstream and pending.
> tag 1027870 pending
Bug #1027870 [src:dm-wri
Control: tag -1 fixed-upstream pending
Control: tag 1027870 pending
On Fri, 20 Jan 2023 13:37:01 +0100 Andreas Beckmann wrote:
/var/lib/dkms/dm-writeboost/2.2.15/build/dm-writeboost.h:506:46: error: ‘struct
dm_io_request’ has no member named ‘bi_op’; did you mean ‘bi_opf’?
This is fixed in a
Control: tag -1 pending
Hello,
Bug #1027870 in dm-writeboost reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian/dm-writeboost/-/commit/3415bc8e6372b6bf3b3aa
Processing control commands:
> tag -1 pending
Bug #1027870 [src:dm-writeboost] dm-writeboost: please switch to B-D:
dh-sequence-dkms (or dh-dkms)
Added tag(s) pending.
--
1027870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027870
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tag -1 pending
Hello,
Bug #1031396 in pipewire reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/utopia-team/pipewire/-/commit/cdd78bc461a98e96ac8a96d6fc
Processing control commands:
> tag -1 pending
Bug #1031396 [pipewire] Unable to upgrade to *gnome* 1:43+1 with `apt
full-upgrade`
Added tag(s) pending.
--
1031396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031396
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> affects -1 = src:python-scrapy src:libzstd src:rpmlint src:python-zstandard
Bug #1031443 [python3-zstandard] python-zstandard: FTBFS: ImportError: zstd C
API versions mismatch; Python bindings were not compiled/linked against
expected zstd version (10504 returned b
Package: python3-zstandard
Followup-For: Bug #1031443
Control: affects -1 = src:python-scrapy src:libzstd src:rpmlint
src:python-zstandard
Control: merge -1 1031293
Should be fixed by [1]
- FC
[1] https://salsa.debian.org/reproducible-builds/diffoscope/-/merge_requests/126
Processing control commands:
> affects -1 - src:rpmlint
Bug #1031443 [python3-zstandard] python-zstandard: FTBFS: ImportError: zstd C
API versions mismatch; Python bindings were not compiled/linked against
expected zstd version (10504 returned by the lib, 10504 hardcoded in zstd
headers, 10502
1 - 100 of 139 matches
Mail list logo
