Your message dated Sun, 23 Oct 2022 09:16:27 +0530
with message-id <4f5a5092-7dbd-47cd-93d6-96b74afb8...@debian.org>
and subject line Re: ionit: FTBFS dh_auto_test: error: pybuild --test -i
python{version} -p 3.10 returned exit code 13
has caused the Debian Bug report #1021923,
regarding ionit:
Processing control commands:
> severity -1 normal
Bug #1022250 [qtox] qtox: AppArmor profile breaks qTox under NVIDIA propiertary
drivers
Severity set to 'normal' from 'grave'
--
1022250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022250
Debian Bug Tracking System
Contact
Control: severity -1 normal
Remark as normal, since it's related to non-free software.
Control: tags 1020150 + patch
Control: tags 1020150 + pending
X-Debbugs-CC: Michael Vogt
Dear maintainer,
I've prepared an NMU for unattended-upgrades (versioned as 2.9.1+nmu2) and
uploaded it to DELAYED/4. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru
Processing control commands:
> tags 1020150 + patch
Bug #1020150 [src:unattended-upgrades] unattended-upgrades: FTBFS: make[1]: ***
[debian/rules:33: override_dh_auto_clean] Error 1
Added tag(s) patch.
> tags 1020150 + pending
Bug #1020150 [src:unattended-upgrades] unattended-upgrades: FTBFS:
Your message dated Sun, 23 Oct 2022 00:50:46 +
with message-id
and subject line Bug#1021895: fixed in pylint 2.15.5-1
has caused the Debian Bug report #1021895,
regarding pylint: fails to honor "--" argument
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> tag -1 pending
Bug #1021895 [pylint] pylint: fails to honor "--" argument
Added tag(s) pending.
--
1021895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1021895 in pylint 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:
Your message dated Sat, 22 Oct 2022 23:50:56 +
with message-id
and subject line Bug#937234: fixed in pam-python 1.1.0~git20220701.1d4e111-0.1
has caused the Debian Bug report #937234,
regarding pam-python: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that
Control: retitle 1022254 sagemath autopkgtest regressed
Control: reassign 1022254 src:sagemath 9.5-4
On Sat, 22 Oct 2022 21:35:11 +0200 Paul Gevers wrote:
With a recent upload of eclib the autopkgtest of sagemath fails in
testing when that autopkgtest is run with the binary packages of eclib
Processing control commands:
> retitle 1022254 sagemath autopkgtest regressed
Bug #1022254 [src:eclib, src:sagemath] eclib breaks sagemath autopkgtest on
i386: Error: 363 tests failed, up to 100 failures are tolerated
Changed Bug title to 'sagemath autopkgtest regressed' from 'eclib breaks
Source: python-xarray, satpy
Control: found -1 python-xarray/2022.10.0-1
Control: found -1 satpy/0.37.1-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of python-xarray the autopkgtest of satpy fails
Hi,
I think it would be a pity to release bookworm without openscenegraph,
also because there a quite a lot of reverse dependencies.
Unfortunately, there hasn't been much progress yet, and the freeze is
coming nearer.
I've just spotted how Ubuntu solved this:
Source: eclib, sagemath
Control: found -1 eclib/20221012-1
Control: found -1 sagemath/9.5-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of eclib the autopkgtest of sagemath fails in
testing when
Processing control commands:
> found -1 python-xarray/2022.10.0-1
Bug #1022255 [src:python-xarray, src:satpy] python-xarray breaks satpy
autopkgtest
Marked as found in versions python-xarray/2022.10.0-1.
> found -1 satpy/0.37.1-1
Bug #1022255 [src:python-xarray, src:satpy] python-xarray breaks
Processing control commands:
> found -1 eclib/20221012-1
Bug #1022254 [src:eclib, src:sagemath] eclib breaks sagemath autopkgtest on
i386: Error: 363 tests failed, up to 100 failures are tolerated
Marked as found in versions eclib/20221012-1.
> found -1 sagemath/9.5-4
Bug #1022254 [src:eclib,
Processing control commands:
> found -1 swi-prolog/8.4.3+dfsg-2
Bug #1022253 [src:swi-prolog, src:logol] swi-prolog breaks logol autopkgtest on
s390x
Marked as found in versions swi-prolog/8.4.3+dfsg-2.
> found -1 logol/1.7.9+dfsg-5
Bug #1022253 [src:swi-prolog, src:logol] swi-prolog breaks
Source: swi-prolog, logol
Control: found -1 swi-prolog/8.4.3+dfsg-2
Control: found -1 logol/1.7.9+dfsg-5
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of swi-prolog the autopkgtest of logol fails in
Processing control commands:
> tags -1 + help
Bug #1019682 [src:schleuder] schleuder: FTBFS with ruby3.1: ERROR: Test
"ruby3.1" failed: Failure/Error: expect(error).to be_empty
Added tag(s) help.
--
1019682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019682
Debian Bug Tracking
Control: tags -1 + help
Hi Antonio, all,
Thanks for your report. I had a look, and I'm able to reproduce locally if
building the package, although so far I haven't been able to find out what is
causing this. I would be happy if someone is able to support me in debugging
this.
Looking at [1],
Workaround is to import nvidia abstraction into local include file you can
create:
```
$ cat /etc/apparmor.d/local/usr.bin.qtox
include
```
Package: qtox
Version: 1.17.6-0.1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
After upgrading to nvidia-tesla-470-driver, qTox fails to start.
See https://github.com/qTox/qTox/pull/ for more details.
Marked as grave as AppArmor profile for qTox
On Fri, Oct 07, 2022 at 02:16:35PM -0300, Antonio Terceiro wrote:
>...
> But nothing in ruby-ahoy-email codebase uses net/smtp explicitly, so
> this is a bit weird. Our version is also quite outated wrt upstream, so
> my first attempt would be to just update the latest upstream (there are
> no
Package: cloop-src
Version: 3.14.1.3
Followup-For: Bug #1005414
X-Debbugs-Cc: witold.bary...@gmail.com
Any updates? There is a patch.
https://debian-knoppix.alioth.debian.org/packages/cloop/ doesn't work,
but you can find it in /usr/src on CD images:
Source: scummvm
Version: 2.6.0+dfsg-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Debian Fonts Task Force , Gürkan
Myczko
https://buildd.debian.org/status/fetch.php?pkg=scummvm=amd64=2.6.0%2Bdfsg-1%2Bb1=1666456981=0
...
debian/rules execute_before_dh_auto_build
make[1]: Entering directory
Processing commands for cont...@bugs.debian.org:
> affects 1022233 rsass
Bug #1022233 [librust-tracing-subscriber-dev] librust-tracing-subscriber-dev:
impossible to install
Added indication that 1022233 affects rsass
> thanks
Stopping processing here.
Please contact me if you need assistance.
Processing control commands:
> tags -1 patch
Bug #1009031 [libgit-raw-perl] libgit-raw-perl: FTBFS with libgit2 1.3.0
Added tag(s) patch.
--
1009031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
Hi,
Taking the approach of refreshing the test suite to match the
output produced by the new libgit2 seems to do the job to
address the test suite failure. I also checked this has no
adverse effects on reverse dependencies. Variations between the
reference and the new
Your message dated Sat, 22 Oct 2022 16:39:14 +
with message-id
and subject line Bug#1019622: fixed in ruby-factory-bot 6.2.1-1
has caused the Debian Bug report #1019622,
regarding ruby-factory-bot: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
expected NoMethodError with
Simon McVittie 于2022年10月21日周五 19:36写道：
>
> Source: llvm-toolchain-15
> Version: 1:15.0.2-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source, making mesa unbuildable
> User: debian-m...@lists.debian.org
> Usertags: mipsel mips64el
> X-Debbugs-Cc:
Processing control commands:
> severity -1 critical
Bug #1022232 [libffi8] libffi8 3.4.3-3 breaks all wayland clients on
arm64/aarch64
Severity set to 'critical' from 'important'
--
1022232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022232
Debian Bug Tracking System
Contact
Hi Paul,
Ying-Chun Liu (PaulLiu) wrote:
> Neither szqdong nor kenorb-contrib is working.
> I've tried both.
Meh. I had hope because at least their build CI seems to have been
passed.
Thanks a lot for having a look at it and testing!
Regards, Axel
--
,''`. | Axel Beckert ,
Your message dated Sat, 22 Oct 2022 16:55:47 +0200
with message-id <166645054798.2543.14296466229415952...@auryn.jones.dk>
and subject line Re: crash converting PDF to PNG
has caused the Debian Bug report #1010051,
regarding ghostscript: crash converting PDF to PNG
to be marked as done.
This
Processing control commands:
> severity -1 important
Bug #1022239 [src:festival] festival FTBFS: make[2]: ***
[/usr/lib/speech_tools/config/rules/targets.mak:55: src] Error 2
Severity set to 'important' from 'serious'
> tags -1 + moreinfo
Bug #1022239 [src:festival] festival FTBFS: make[2]: ***
Control: severity -1 important
Control: tags -1 + moreinfo
Hello,
Nilesh Patra, le sam. 22 oct. 2022 19:40:52 +0530, a ecrit:
> Festival fails to build from source with:
[no actual error message]
Please post the whole log, otherwise we can't see anything.
I have tried to build festival both
Source: festival
Version: 1:2.5.0-8
Severity: serious
X-Debbugs-Cc: sthiba...@debian.org
Hi,
Festival fails to build from source with:
look at library Festival UniSyn.o us_prosody.o us_unit.o ps_synthesis.o
us_mapping.o us_features.o
Update library Festival UniSyn.o us_prosody.o us_unit.o
Processing commands for cont...@bugs.debian.org:
> tags 1022025 - moreinfo
Bug #1022025 [src:linux] Can't enable amdgpu driver in
linux-image-5.10.0-19-amd64
Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails
to boot on machines with AMD integrated graphics
Bug
Your message dated Sat, 22 Oct 2022 13:41:06 +
with message-id
and subject line Bug#1022152: fixed in postgresql-14 14.5-3
has caused the Debian Bug report #1022152,
regarding postgresql-14 rejected
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> block 996464 with 1022233
Bug #996464 [wnpp] ITP: atomic-data-rust -- graph database server to share
Atomic Data on the web
996464 was blocked by: 1019090 1013104 1013100 1019144 1013108 1022219 1013109
1013103 969609 1020407 1013106 951683
A local rebuild with wx-widgets 3.0 makes the crash go away.
Upstream states [1] that prusa-slicer is not ready for wxwidgets 3.2 -- maybe
#1019825 should be reverted?
As the crash happens in imgui:
I did not check, if the embedded imgui library is the culprit. Embedded version
is at 1.83,
Your message dated Sat, 22 Oct 2022 13:34:35 +
with message-id
and subject line Bug#1012361: fixed in electrum 4.3.2+dfsg1-1
has caused the Debian Bug report #1012361,
regarding electrum: Please package new upstream release
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 22 Oct 2022 13:34:35 +
with message-id
and subject line Bug#1012361: fixed in electrum 4.3.2+dfsg1-1
has caused the Debian Bug report #1012361,
regarding New upstream version 4.2.2
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 22 Oct 2022 13:34:35 +
with message-id
and subject line Bug#1001064: fixed in electrum 4.3.2+dfsg1-1
has caused the Debian Bug report #1001064,
regarding electrum: Please package new upstream release
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 22 Oct 2022 13:34:35 +
with message-id
and subject line Bug#1001064: fixed in electrum 4.3.2+dfsg1-1
has caused the Debian Bug report #1001064,
regarding New upstream version 4.2.2
to be marked as done.
This means that you claim that the problem has been dealt with.
Control: tag -1 pending
Hello,
Bug #1022152 in postgresql 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:
> tag -1 pending
Bug #1022152 [src:postgresql-14] postgresql-14 rejected
Added tag(s) pending.
--
1022152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022152
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sat, 22 Oct 2022 13:06:21 +
with message-id
and subject line Bug#947425: fixed in incron 0.5.12-3
has caused the Debian Bug report #947425,
regarding Incron crash with an "*** unhandled exception occurred ***"
to be marked as done.
This means that you claim that the
Your message dated Sat, 22 Oct 2022 13:06:21 +
with message-id
and subject line Bug#947425: fixed in incron 0.5.12-3
has caused the Debian Bug report #947425,
regarding incron SEGV when monitoring directories
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 22 Oct 2022 13:06:21 +
with message-id
and subject line Bug#947425: fixed in incron 0.5.12-3
has caused the Debian Bug report #947425,
regarding incron crashes in IncronTabEntry::GetSafePath due to use-after-free
bug
to be marked as done.
This means that you claim
Your message dated Sat, 22 Oct 2022 13:06:21 +
with message-id
and subject line Bug#1021850: fixed in incron 0.5.12-3
has caused the Debian Bug report #1021850,
regarding incron FTBFS with gcc 11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Hi Clément,
On Sat, Oct 22, 2022 at 02:50:53PM +0200, Clément Hermann wrote:
> Hi Salvatore,
>
> Le 22/10/2022 à 13:49, Salvatore Bonaccorso a écrit :
> >
> > > For further information see:
> > >
> > > [0] https://security-tracker.debian.org/tracker/CVE-2021-41867
> > >
Processing control commands:
> close -1 2.18-1
Bug #1022235 [src:zeroinstall-injector] src:zeroinstall-injector: fails to
migrate to testing for too long: FTBFS on armel, mips64el and mipsel
Marked as fixed in versions zeroinstall-injector/2.18-1.
Bug #1022235 [src:zeroinstall-injector]
Source: zeroinstall-injector
Version: 2.16-2
Severity: serious
Control: close -1 2.18-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more
Package: prusa-slicer
Version: 2.5.0+dfsg-2
Severity: grave
Justification: renders package unusable
prusa-slicer SEGV at start. (in the last stackframe, in imgui, this is a
nullptr…)
backtrace:
Thread 1 "slic3r_main" received signal SIGSEGV, Segmentation fault.
0x568b12d3 in
Hi Salvatore,
Le 22/10/2022 à 13:49, Salvatore Bonaccorso a écrit :
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2021-41867
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41867
[1] https://security-tracker.debian.org/tracker/CVE-2021-41868
Processing commands for cont...@bugs.debian.org:
> block 1008016 with 1022233
Bug #1008016 [wnpp] ITP: safe-network -- network routing and service daemon for
the Safe Network
1008016 was blocked by: 1013142 1013109 1016409 1020418 984864 1013106 1010275
1013138 1010212 1020407 1013144 974118
Your message dated Sat, 22 Oct 2022 12:43:37 +
with message-id
and subject line Bug#1012809: fixed in openboard 1.6.4+dfsg-1
has caused the Debian Bug report #1012809,
regarding openboard: Update for Poppler 22.06
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 22 Oct 2022 12:43:36 +
with message-id
and subject line Bug#1004764: fixed in openboard 1.6.4+dfsg-1
has caused the Debian Bug report #1004764,
regarding openboard: FTBFS with ffmpeg 5.0
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 22 Oct 2022 12:35:28 +
with message-id
and subject line Bug#1021995: fixed in fastqtl 2.184+v7+dfsg-3
has caused the Debian Bug report #1021995,
regarding fastqtl: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 22 Oct 2022 12:35:28 +
with message-id
and subject line Bug#1021994: fixed in fastqtl 2.184+v7+dfsg-3
has caused the Debian Bug report #1021994,
regarding fastqtl: binary-all FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> severity 1022200 normal
Bug #1022200 [perl] cpan: cannot check signatures
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1022200:
Hi!
Thanks for your report.
I could reproduce your issue if I enable check_sigs option in CPAN
(which is _not_ the default).
Thing is, it's not a bug, really. Or not quite. It's a result of the
correction of a bug in CPAN < 2.29 who would succeed silently if there
is no signature/no way to
Processing commands for cont...@bugs.debian.org:
> forcemerge 947425 962278
Bug #947425 [incron] incron crashes in IncronTabEntry::GetSafePath due to
use-after-free bug
Bug #973927 [incron] incron SEGV when monitoring directories
Bug #973927 [incron] incron SEGV when monitoring directories
Your message dated Sat, 22 Oct 2022 14:02:12 +0200
with message-id <20221022120212.d53m4acijxel3...@enricozini.org>
and subject line Fixed in 1.6-1
has caused the Debian Bug report #949756,
regarding staticsite FTBFS: FAIL: test_site
(tests.test_page_filter.TestPageFilter)
to be marked as done.
Hi,
This libffi upgrade also completely breaks all use of Wayland on
aarch64. We use libffi to dispatch protocol messages (requests
received by the server and events received by the client) to
native-code handlers, and we are now getting completely nonsensical
values from it.
Can this upgrade
Control: tag -1 pending
Hello,
Bug #1021994 in fastqtl 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:
> tag -1 pending
Bug #1021995 [src:fastqtl] fastqtl: autopkgtest regression
Added tag(s) pending.
--
1021995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021995
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1021995 in fastqtl 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:
> tag -1 pending
Bug #1021994 [src:fastqtl] fastqtl: binary-all FTBFS
Added tag(s) pending.
--
1021994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi,
On Fri, Jul 15, 2022 at 02:04:38PM +0200, Moritz Mühlenhoff wrote:
> Source: onionshare
> X-Debbugs-CC: t...@security.debian.org
> Severity: grave
> Tags: security
>
> Hi,
>
> The following vulnerabilities were published for onionshare.
>
> CVE-2021-41867[0]:
> | An information disclosure
Your message dated Sat, 22 Oct 2022 11:39:25 +
with message-id
and subject line Bug#1022137: fixed in wike 1.8.1+ds-2
has caused the Debian Bug report #1022137,
regarding wike: Wike does not run due to missing python3-requests
to be marked as done.
This means that you claim that the problem
Same problem on update to Kernel: 5.10.0-19-amd64 x86_64, Boots OK on
18. Architecture:
x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 43 bits physical, 48 bits virtual
CPU(s):
Your message dated Sat, 22 Oct 2022 10:00:11 +
with message-id
and subject line Bug#997499: fixed in onionshare 2.5-1
has caused the Debian Bug report #997499,
regarding onionshare: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p 3.9 returned exit code 13
to be
Thanks Tobias for the quick fix!
François
signature.asc
Description: This is a digitally signed message part
Source: libxml2
Version: 2.9.14+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for libxml2.
CVE-2022-40304[0]:
| dict corruption caused by entity reference cycles
If you fix the vulnerability
Source: libxml2
Version: 2.9.14+dfsg-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for libxml2.
CVE-2022-40303[0]:
| Integer overflows with XML_PARSE_HUGE
If you fix the vulnerability please also
Your message dated Sat, 22 Oct 2022 15:10:16 +0530
with message-id <4ve5kr.pitrv36uhg...@onenetbeyond.org>
and subject line Re: ruby-redis: FTBFS: ERROR: Test "ruby3.0" failed.
has caused the Debian Bug report #1013473,
regarding ruby-redis: FTBFS: ERROR: Test "ruby3.0" failed.
to be marked as
Source: haskell-pipes-zlib
Version: 0.4.4.2-3
Severity: serious
I intend to remove this package:
* It has no rev dependencies
* The current version FTBFS (see #1015280)
* It's not part of the latest Stackage LTS
If you believe we should keep this package in Debian, please close this
bug
Processing control commands:
> affects -1 src:qtmir
Bug #102 [valgrind-if-available] valgrind-if-available shouldn't stop
providing valgrind on mipsel
Added indication that 102 affects src:qtmir
--
102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=102
Debian Bug Tracking
Package: valgrind-if-available
Version: 3.18.1-1-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Alessandro Ghedini , Debian UBports Team
Control: affects -1 src:qtmir
valgrind-if-available (3.18.1-1-1) unstable; urgency=medium
...
* Drop mipsel as valgrind disagrees about blah blah baseline
Your message dated Sat, 22 Oct 2022 09:04:30 +
with message-id
and subject line Bug#983010: fixed in debiman 0.0~git20220907.a582536-1
has caused the Debian Bug report #983010,
regarding mdocml breaks debiman autopkgtest: different output
to be marked as done.
This means that you claim that
Control: tag -1 pending
Hello,
Bug #983010 in debiman 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:
> tag -1 pending
Bug #983010 [src:debiman] mdocml breaks debiman autopkgtest: different output
Added tag(s) pending.
--
983010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> fixed -1 1:0.1.9998svn3571+dfsg-2
Bug #1022214 [src:kbuild] kbuild FTBFS
The source 'kbuild' and version '1:0.1.9998svn3571+dfsg-2' do not appear to
match any binary packages
Marked as fixed in versions kbuild/1:0.1.9998svn3571+dfsg-2.
> close -1
Bug #1022214
control: fixed -1 1:0.1.9998svn3571+dfsg-2
control: close -1
thanks!
G.
On Sat, 22 Oct 2022 09:19:29 +0300 Adrian Bunk wrote:
Source: kbuild
Version: 1:0.1.9998svn3571+dfsg-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=kbuild=1%3A0.1.9998svn3571%2Bdfsg-1
...
Prusa Slicer 2.5.0+dfsg-2 still SIGSEGV's during startup on Bookworm
with some sid.
A local rebuild does also runs into Segfault. However, it also reports
that it is unable to init glew.
I'm quite sure it is a different issue, but the result is quite the
same. So i was unsure if I should open a
Processing commands for cont...@bugs.debian.org:
> severity 1021658 serious
Bug #1021658 [latexml] latexml: AutoPKG test suite fails since latest upload of
TLive
Severity set to 'serious' from 'important'
> block 1019353 by 1021658
Bug #1019353 [release.debian.org] transition: perl 5.36
1019353
Your message dated Sat, 22 Oct 2022 07:34:03 +
with message-id
and subject line Bug#1021858: fixed in drf-yasg-nonfree 1.21.4-1
has caused the Debian Bug report #1021858,
regarding drf-yasg-nonfree: FTBFS: AttributeError: module
'rest_framework.serializers' has no attribute
Your message dated Sat, 22 Oct 2022 10:26:26 +0300
with message-id
and subject line Re: Bug#1021833: nbdkit: FTBFS: FAIL test-partitioning3.sh
(exit status: 1)
has caused the Debian Bug report #1021833,
regarding nbdkit: FTBFS: FAIL test-partitioning3.sh (exit status: 1)
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> affects 1021735 src:gjs src:glib2.0 src:gnustep-base src:libffi-platypus-perl
> src:libglib-object-introspection-perl src:lua-lgi src:pypy3 src:python2.7
> ruby-ffi src:ruby3.0 src:ruby3.1
Bug #1021735 [src:libffi] libffi breaks python3.10
Source: kbuild
Version: 1:0.1.9998svn3571+dfsg-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=kbuild=1%3A0.1.9998svn3571%2Bdfsg-1
...
kBuild: Compiling kmk_sed - /<>/src/sed/sed/compile.c
The failing command:
@gcc -c -O2 -g -O3 -m64
91 matches
Mail list logo
