Your message dated Wed, 27 Jul 2022 06:06:22 +
with message-id
and subject line Bug#1011918: fixed in ktimer 4:22.04.3-1
has caused the Debian Bug report #1011918,
regarding ktimer: FTBFS: "The list of supported platorms is ''" (empty)
to be marked as done.
This means that you claim that the
Your message dated Wed, 27 Jul 2022 05:35:45 +
with message-id
and subject line Bug#1011865: fixed in kmouth 4:22.04.3-1
has caused the Debian Bug report #1011865,
regarding kmouth: FTBFS: "The list of supported platorms is ''" (empty)
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> forwarded 1005672 https://github.com/bgrabitmap/lazpaint/issues/512
Bug #1005672 [src:lazpaint] lazpaint: FTBFS:
/<>/lazpaint/ufilesystem.pas(1054,26) Error: (5038) identifier
idents no member "GetFilesInDir"
Set Bug forwarded-to-address to
'ht
Package: libdrm
Version: 2.4.110-1
Severity: serious
Hi,
unfortunately the last upload of libdrm failed to build on all arm
architectures:
https://buildd.debian.org/status/package.php?p=libdrm&suite=unstable
Regards,
Daniel
Processing commands for cont...@bugs.debian.org:
> tags 1011918 + pending
Bug #1011918 [src:ktimer] ktimer: FTBFS: "The list of supported platorms is ''"
(empty)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011918: https://bugs.debian.or
Processing commands for cont...@bugs.debian.org:
> tags 1011865 + pending
Bug #1011865 [src:kmouth] kmouth: FTBFS: "The list of supported platorms is ''"
(empty)
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011865: https://bugs.debian.or
Processing commands for cont...@bugs.debian.org:
> close 989011
Bug #989011 [src:ksudoku] ksudoku FTBFS on armhf in buster
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
989011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989011
Debian Bu
Hello,
> I rewrite my patch to enable all string test.
New patch was already uploaded to salsa.
https://salsa.debian.org/debian/libpodofo/-/merge_requests/2
--
YOKOTA
Processing commands for cont...@bugs.debian.org:
> forwarded 1013421 https://github.com/salsaman/LiVES/issues/49
Bug #1013421 [src:lives] lives FTBFS with ffmpeg 5.0.1
Set Bug forwarded-to-address to 'https://github.com/salsaman/LiVES/issues/49'.
> thanks
Stopping processing here.
Please contact
Processing control commands:
> found -1 python-django/2:4.0.6-1
Bug #1016090 [src:python-django] python-django breaks lots of autopkgtests
Marked as found in versions python-django/2:4.0.6-1.
> affects -1 django-mailman3 django-invitations
Bug #1016090 [src:python-django] python-django breaks lots
Source: python-django
Control: found -1 python-django/2:4.0.6-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks
Control: affects -1 django-mailman3 django-invitations
Control: affects -1 django-oauth-toolkit django-tables
Control: affects -1 djangorestframewo
Source: mistune
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for mistune.
CVE-2022-34749[0]:
| In mistune through 2.0.2, support of inline markup is implemented by
| using regular expressions that can involve a high amount of
Quoting Paul Gevers (2022-07-26 22:24:55)
> That worker (ci-worker13) has 7 TB of disk available, so space shouldn't be
> the problem. I'm also not seeing [1] the disk usage anytime higher than 7%
> (and it's actually that /mnt/lxc-containers that's being used and that
> doesn't peak above 1.2% sin
Dear Maintainer,
I backported the work merged upstream around ffmpeg 5. Please see attached.
This was sufficient to address the FTBFS both for Sid and Ubuntu Kinetic.
-Dan
Description: Backport ffmpeg 5 fixes.
Author: Dan Bungert
Origin: https://github.com/Motion-Project/motion/pull/1
Hi,
On 26-07-2022 13:28, Luca Boccassi wrote:
The autopkgtest run for sbuild keeps failing in debci, blocking other
packages migrations. The failure manifests in two different error
types, but both related to "No space left on device" when running
mmdebstrap.
This seems to have started on July
Your message dated Tue, 26 Jul 2022 19:04:44 +
with message-id
and subject line Bug#1015174: fixed in lvm2 2.03.16-1
has caused the Debian Bug report #1015174,
regarding lvm2-udeb: uninstallable, depends on non-udeb libsystemd0
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 26 Jul 2022 19:00:09 +
with message-id
and subject line Bug#1012981: fixed in libkiwix 11.0.0-1
has caused the Debian Bug report #1012981,
regarding libkiwix: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Your message dated Tue, 26 Jul 2022 19:00:09 +
with message-id
and subject line Bug#1012894: fixed in apertium 3.8.2-1
has caused the Debian Bug report #1012894,
regarding apertium: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Package: libqt5network5
Version: 5.15.4+dfsg-4
Severity: serious
Justification: Policy 3.5
I have libssl 3.0.4-2 (satisfying the dependency of libqt5network5),
but libssl-dev 1.1.1n-0+deb11u3.
Starting QT applications gets on stdout/stderr stuff like
07-26 20:08:33:071 [ warning qt.network.ssl ]
Processing control commands:
> tags -1 + patch
Bug #1015174 [lvm2-udeb] lvm2-udeb: uninstallable, depends on non-udeb
libsystemd0
Added tag(s) patch.
> user de...@kali.org
Unknown command or malformed arguments to command.
> usertags -1 + kali-patch
Unknown command or malformed arguments to comm
Control: tags -1 + patch
Control: user de...@kali.org
Control: usertags -1 + kali-patch
On Sun, 17 Jul 2022 05:50:20 +0200 Cyril Brulebois wrote:
> I suppose the journal bits could be patched out for the udeb build (right
> now, configure ends up defining SYSTEMD_JOURNAL_SUPPORT to 1 there), but
Your message dated Tue, 26 Jul 2022 17:35:03 +
with message-id
and subject line Bug#1015268: fixed in olm 3.2.12~dfsg-1
has caused the Debian Bug report #1015268,
regarding olm: jasmine tests fail with nodejs 18
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Tue, 26 Jul 2022 16:49:22 +
with message-id
and subject line Bug#965765: fixed in pacparser 1.3.6-1.3
has caused the Debian Bug report #965765,
regarding pacparser: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that
Your message dated Tue, 26 Jul 2022 16:19:44 +
with message-id
and subject line Bug#1013051: fixed in tensorpipe 0.0~git20220513.bb1473a-3
has caused the Debian Bug report #1013051,
regarding tensorpipe: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has be
Source: haskell-genvalidity-property
Version: 1.0.0.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=haskell-genvalidity-property&ver=1.0.0.0-1
...
Running debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct
Non-zero exit code 1.
Running 1 test suit
Processing commands for cont...@bugs.debian.org:
> close 1015721 1.0.0.0-1
Bug #1015721 [src:haskell-genvalidity-property] haskell-genvalidity-property
FTBFS: error: Not in scope: type constructor or class ‘GenUnchecked’
Marked as fixed in versions haskell-genvalidity-property/1.0.0.0-1.
Bug #101
On Tue, 2022-07-26 at 15:43 +0200, Johannes Schauer Marin Rodrigues
wrote:
> Hi,
>
> Quoting Luca Boccassi (2022-07-26 15:27:35)
> > If it's not appropriate, please do update it accordingly, but IIRC it's what
> > gets used in these cases.
>
> a bunch of sbuild issues piled up during the last wee
Hi,
Quoting Luca Boccassi (2022-07-26 15:27:35)
> If it's not appropriate, please do update it accordingly, but IIRC it's what
> gets used in these cases.
a bunch of sbuild issues piled up during the last weeks so I'll be doing an
upload soon and will include a fix for this as well.
> > I put th
On Tue, 2022-07-26 at 15:15 +0200, Johannes Schauer Marin Rodrigues
wrote:
> Hi,
>
> thank you for your bug report!
>
> Quoting Luca Boccassi (2022-07-26 13:28:50)
> > Severity: serious
>
> why is an autopkgtest failure "serious"?
Because it blocks other packages from migrating to testing, e.g.
Your message dated Tue, 26 Jul 2022 13:20:40 +
with message-id
and subject line Bug#965792: fixed in raptor2 2.0.15-1
has caused the Debian Bug report #965792,
regarding raptor2: Removal of obsolete debhelper compat 5 and 6 in bookworm
to be marked as done.
This means that you claim that the
Hi,
thank you for your bug report!
Quoting Luca Boccassi (2022-07-26 13:28:50)
> Severity: serious
why is an autopkgtest failure "serious"?
> The autopkgtest run for sbuild keeps failing in debci, blocking other
> packages migrations. The failure manifests in two different error
> types, but bo
Your message dated Tue, 26 Jul 2022 13:03:53 +
with message-id
and subject line Bug#1012911: fixed in dbus-c++ 0.9.0-10
has caused the Debian Bug report #1012911,
regarding dbus-c++: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Processing control commands:
> tags -1 + patch
Bug #1015039 [src:mesa] gtk4 memorytexture test-case regresses with Mesa 22.1
Added tag(s) patch.
--
1015039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
On Tue, 19 Jul 2022 at 11:56:43 +0100, Simon McVittie wrote:
> A straightforward revert of 6bbbe15a applies cleanly to 22.1.x and
> appears to solve this.
Alternatively, upstream merge request
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/17702 is waiting
for
Your message dated Tue, 26 Jul 2022 12:34:39 +
with message-id
and subject line Bug#1013551: fixed in mdevctl 1.1.0-2
has caused the Debian Bug report #1013551,
regarding mdevctl: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build
returned exit code 101
to be marked as done.
This m
Your message dated Tue, 26 Jul 2022 11:36:14 +
with message-id
and subject line Bug#1007962: fixed in sslsplit 0.5.5-2.1
has caused the Debian Bug report #1007962,
regarding sslsplit FTBFS when only loopback interface is configured
to be marked as done.
This means that you claim that the prob
Source: sbuild
Version: 0.83.1
Severity: serious
X-Debbugs-Cc: jo...@debian.org, debian...@lists.debian.org
Dear Maintainer(s),
The autopkgtest run for sbuild keeps failing in debci, blocking other
packages migrations. The failure manifests in two different error
types, but both related to "No sp
Package: rpcbind
Version: 1.2.6-4
Severity: grave
Justification: renders package unusable
Hi,
since the d/postinst file has been removed, on a fresh VM rpcbind can no longer
be installed:
--8<--
root@kvmsid:~# apt install rpcbind
Reading package lists... Done
Building d
in
[1] https://logs.cockpit-project.org/logs/image-refresh-3664-20220726-100606/log
signature.asc
Description: PGP signature
Your message dated Tue, 26 Jul 2022 11:19:47 +0100
with message-id <2365fc75-35aa-ff11-bf44-afd4a29bb...@sceal.ie>
and subject line close
has caused the Debian Bug report #1013316,
regarding early transition to gcc-12 breaks src:pcl on armhf/el
to be marked as done.
This means that you claim that
Package: rpcbind
Version: 1.2.6-4
Severity: serious
A fresh installation of rpcbind fails to start the service:
systemd[1]: Starting RPC bind portmap service...
rpcbind[314]: cannot get uid of '_rpc': Success
systemd[1]: rpcbind.service: Main process exited, code=exited,
status=1/FAI
Source: haskell-cborg
Version: 0.2.7.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=haskell-cborg&ver=0.2.7.0-1
...
src/Codec/CBOR/Decoding.hs:341:19: error:
• Couldn't match expected type ‘Int64#’ with actual type ‘Int#’
• In the first argument of ‘I64#’,
This FTFBS which - as reported - is good if build from git is fixed by
commit 69c911989e4752c3b56851877cfcf7cc6a23bde2
Author: Athos Ribeiro
Date: Tue Jun 7 19:44:38 2022 -0300
d/control: depend on librust-uuid+rand-dev for v4
I'll mark that as fixing this bug
--
Christian Ehrhardt
Seni
fixed 1013551 1.1.0-2
tags 1013551 +pending
Processing commands for cont...@bugs.debian.org:
> fixed 1013551 1.1.0-2
Bug #1013551 [src:mdevctl] mdevctl: FTBFS: dh_auto_test: error:
/usr/share/cargo/bin/cargo build returned exit code 101
The source 'mdevctl' and version '1.1.0-2' do not appear to match any binary
packages
Marked as fixed i
Hi,
sorry that I didn't see that bug earlier :-/
Well better late than never ... I at least saw the removal :-(
I had a look and I'm confused by how your re-build broke here.
> searched package name: `rand`
That should be provided by librust-rand-dev and all its variations.
The build dependency
Your message dated Tue, 26 Jul 2022 08:49:07 +
with message-id
and subject line Bug#1012930: fixed in flextra 5.0-16
has caused the Debian Bug report #1012930,
regarding flextra: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Tue, 26 Jul 2022 08:39:16 +
with message-id
and subject line Bug#1013019: fixed in pyferret 7.6.5-2
has caused the Debian Bug report #1013019,
regarding pyferret: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 26 Jul 2022 08:34:29 +
with message-id
and subject line Bug#1016010: fixed in ecflow 5.8.4-2
has caused the Debian Bug report #1016010,
regarding ecflow FTBFS with gcc 12
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Your message dated Tue, 26 Jul 2022 10:25:51 +0200
with message-id <82b8da9d-5249-96cf-44b9-bcb49259b...@debian.org>
and subject line Re: balboa: regression + flaky autopkgtest: regularly times
out on amd64, i386 and s390x
has caused the Debian Bug report #1013938,
regarding balboa: regression + f
Your message dated Tue, 26 Jul 2022 07:33:55 +
with message-id
and subject line Bug#1012924: fixed in ferret-vis 7.6.0-5
has caused the Debian Bug report #1012924,
regarding ferret-vis: ftbfs with GCC-12
to be marked as done.
This means that you claim that the problem has been dealt with.
If
51 matches
Mail list logo
