Processing control commands:
> affects -1 + facet-analyser
Bug #982601 [python3-paraview] python3-paraview Conflicts: python3-vtk9
Added indication that 982601 affects facet-analyser
> block 1040334 by -1
Bug #1040334 [facet-analyser] facet-analyser - build-depends on conflicting
packages
Your message dated Fri, 10 May 2024 02:51:31 +
with message-id
and subject line Bug#1069358: fixed in font-manager 0.8.8+git20240505-1
has caused the Debian Bug report #1069358,
regarding font-manager: FTBFS:
../src/font-manager/ArchiveManager.vala:26.97-26.106: error: internal: invalid
Your message dated Fri, 10 May 2024 02:41:18 +
with message-id
and subject line Bug#1052780: fixed in python-pyramid-chameleon 0.3-8
has caused the Debian Bug report #1052780,
regarding python-pyramid-chameleon: FTBFS: FileNotFoundError: [Errno 2] No such
file or directory:
Your message dated Fri, 10 May 2024 02:41:19 +
with message-id
and subject line Bug#1056499: fixed in python-pyramid-chameleon 0.3-8
has caused the Debian Bug report #1056499,
regarding python-pyramid-chameleon's autopkg tests fail with Python 3.12
to be marked as done.
This means that you
Control: tag -1 pending
Hello,
Bug #1056499 in python-pyramid-chameleon 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 #1056499 [src:python-pyramid-chameleon] python-pyramid-chameleon's autopkg
tests fail with Python 3.12
Ignoring request to alter tags of bug #1056499 to the same tags previously set
--
1056499:
Processing control commands:
> tag -1 pending
Bug #1052780 [src:python-pyramid-chameleon] python-pyramid-chameleon: FTBFS:
FileNotFoundError: [Errno 2] No such file or directory:
'/<>/.pybuild/cpython3_3.11_pyramid-chameleon/build/pyramid_chameleon/tests/fixtures/withmacro.pt'
Ignoring request
Control: tag -1 pending
Hello,
Bug #1052780 in python-pyramid-chameleon 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 commands for cont...@bugs.debian.org:
> tags 1052780 + pending
Bug #1052780 [src:python-pyramid-chameleon] python-pyramid-chameleon: FTBFS:
FileNotFoundError: [Errno 2] No such file or directory:
Processing commands for cont...@bugs.debian.org:
> tags 1056499 + pending
Bug #1056499 [src:python-pyramid-chameleon] python-pyramid-chameleon's autopkg
tests fail with Python 3.12
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1056499:
Hi gregor,
> > The thing is that maybe a hint on libaio will be needed?
>
> What do you mean be "hint" here?
When I uploaded 1.83-3 the migration to testing was blocked
because oracle-instantclient12.1-devel in B-D was replaced by
oracle-instantclient-devel, and a force hint was needed:
A Maintained version is here:
http://git.zerfleddert.de/cgi-bin/gitweb.cgi/micropolis
It even includes Markus' patches.
Package: legiond
Version: 0.0.10+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
legiond in main depends on lenovolegionlinux-dkms in contrib, which is
not permitted by the policy.
BTW, why is the -dkms package in contrib?
The -dkms package looks overly complicated:
-
Source: ocrmypdf
Version: 16.1.2+dfsg1-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
https://ci.debian.net/packages/o/ocrmypdf/testing/amd64/46448482/
425s === FAILURES
===
425s _
Source: docker.io
Version: 20.10.25+dfsg1-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=docker.io=amd64=20.10.25%2Bdfsg1-3=1715080704=0
=== Failed
Your message dated Thu, 09 May 2024 19:36:51 +
with message-id
and subject line Bug#1070711: fixed in python-werkzeug 3.0.3-1
has caused the Debian Bug report #1070711,
regarding python-werkzeug: CVE-2024-34069
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 09 May 2024 19:07:41 +
with message-id
and subject line Bug#1041206: fixed in python-clickhouse-driver 0.2.5-2
has caused the Debian Bug report #1041206,
regarding python-clickhouse-driver: FTBFS if source is included: aborting due
to unexpected upstream changes
to be
Processing control commands:
> close -1 0.10.2-1.2
Bug #1070818 [src:libcbor] src:libcbor: fails to migrate to testing for too
long: FTBFS on mips64el
Marked as fixed in versions libcbor/0.10.2-1.2.
Bug #1070818 [src:libcbor] src:libcbor: fails to migrate to testing for too
long: FTBFS on
Source: libcbor
Version: 0.10.2-1.1
Severity: serious
Control: close -1 0.10.2-1.2
Tags: sid trixie 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 than
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:sssd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Source: wsdd
Version: 2:0.7.0-2.1
Severity: serious
Control: close -1 2:0.7.1-5
Tags: sid trixie pending
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 than 30
Processing control commands:
> close -1 2:0.7.1-5
Bug #1070816 [src:wsdd] src:wsdd: fails to migrate to testing for too long:
uploader built arch:all binaries
Marked as fixed in versions wsdd/2:0.7.1-5.
Bug #1070816 [src:wsdd] src:wsdd: fails to migrate to testing for too long:
uploader built
Processing control commands:
> close -1 12.3-1
Bug #1070814 [src:snapraid] src:snapraid: fails to migrate to testing for too
long: FTBFS on mips64el
Marked as fixed in versions snapraid/12.3-1.
Bug #1070814 [src:snapraid] src:snapraid: fails to migrate to testing for too
long: FTBFS on mips64el
Source: snapraid
Version: 12.2-1
Severity: serious
Control: close -1 12.3-1
Tags: sid trixie 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 than 30 days
Your message dated Thu, 09 May 2024 17:19:32 +
with message-id
and subject line Bug#1070690: fixed in pupnp 1:1.14.19-2
has caused the Debian Bug report #1070690,
regarding libupnp-dev: pkgconfig file no longer carries version information
to be marked as done.
This means that you claim that
Source: camelot-py
Version: 0.11.0-3
Severity: serious
Control: close -1 0.11.0-4
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1063891
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and
Processing control commands:
> close -1 0.11.0-4
Bug #1070813 [src:camelot-py] src:camelot-py: fails to migrate to testing for
too long: autopkgtest failure on ppc64el
Marked as fixed in versions camelot-py/0.11.0-4.
Bug #1070813 [src:camelot-py] src:camelot-py: fails to migrate to testing for
On Mon, 6 May 2024 01:28:47 +0300 Jussi Pakkanen wrote:
> Filed:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070470
>
Thanks!
Do you think it's worth it it to file the bug to rust
upstream too: https://github.com/rust-lang/rust/issues
May be wider Rust developers can have an insight.
Source: llvm-toolchain-18
Version: 1:18.1.5-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=llvm-toolchain-18=armel=1%3A18.1.5-2=1714875266=0
1 warning
Processing control commands:
> close -1 2.10
Bug #1070810 [src:unattended-upgrades] src:unattended-upgrades: fails to
migrate to testing for too long: FTBFS
The source 'unattended-upgrades' and version '2.10' do not appear to match any
binary packages
Marked as fixed in versions
Source: unattended-upgrades
Version: 2.9.1+nmu4
Severity: serious
Control: close -1 2.10
Tags: sid trixie 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
Source: multiqc
Version: 1.14+dfsg-1.1
Severity: serious
Control: close -1 1.18+dfsg-1
Tags: sid trixie
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 than 30
Processing control commands:
> close -1 1.18+dfsg-1
Bug #1070809 [src:multiqc] src:multiqc: fails to migrate to testing for too
long: depends on package that doesn't migrate
Marked as fixed in versions multiqc/1.18+dfsg-1.
Bug #1070809 [src:multiqc] src:multiqc: fails to migrate to testing for
On Thu, 09 May 2024 16:41:10 +0200, Alex Muntada wrote:
> > > It turns out that it's oracle-instantclient-basic that needs
> > > libaio.so.1. I'm not sure what could be done to address this
> > > issue, since the soname renaming to libaio.so.1t64 is Debian
> > > specific.
>
> I came up with an
[actually cc the bugreport this time]
On Thu, May 09, 2024 at 07:40:20AM -0700, Darrick J. Wong wrote:
> On Thu, May 09, 2024 at 10:51:03AM +, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> >
> > > tags 1070795 + d-i
> > Bug #1070795 [xfsprogs-udeb]
[Cc to debian-perl for feedback]
Hi Sebastian,
> > > libdbd-oracle-perl depends on libaio1
> >
> > It turns out that it's oracle-instantclient-basic that needs
> > libaio.so.1. I'm not sure what could be done to address this
> > issue, since the soname renaming to libaio.so.1t64 is Debian
> >
Processing commands for cont...@bugs.debian.org:
> # as can be seen on r-b infrastructure
> found 1069391 7.94+git20230807.3be01efb1+dfsg-2
Bug #1069391 [src:nmap] nmap: FTBFS on arm64: i686-w64-mingw32-gcc: error:
unrecognized command-line option ‘-mbranch-protection=standard’
Marked as found
[Sebastian Ramacher]
> I gave it back on the buildds. Let's see if it works now.
Seem to still fail. I suspect the trigger is this code in d/rules:
override_dh_auto_test:
@if [ "$$(cat /proc/sys/kernel/perf_event_paranoid)" -le 2 ] ; then \
$(MAKE) check; \
else \
Hi,
On Thu, Nov 23, 2023 at 03:00:58PM +0100, Paul Slootman wrote:
On Fri 27 Oct 2023, Lucas Nussbaum wrote:
...
on libxpm:
Explicitly mark non-static symbols as export or hidden
Hides private API from external linkage
Signed-off-by: Alan Coopersmith
That commit marks those functions as
Processing commands for cont...@bugs.debian.org:
> found 1070395 1.11.1-1
Bug #1070395 {Done: Salvatore Bonaccorso } [src:tinyproxy]
tinyproxy: CVE-2023-49606
Marked as found in versions tinyproxy/1.11.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing control commands:
> severity -1 important
Bug #998197 [kdeconnect] kdeconnectd: should not listen on all interfaces by
default
Severity set to 'important' from 'serious'
--
998197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998197
Debian Bug Tracking System
Contact
Control: severity -1 important
Hi Witold,
On Tue, 07 May 2024 02:36:46 + Witold Baryluk
wrote:
[...]
> Elevating severity, because it looks like I didn't even installed this
> package (I did inspect all apt-get install invokations since system
> creation), and it kdeconnect could only be
On Mon, 29 Apr 2024 16:56:55 +0200 "M. van Brummelen" wrote:
Hi,
On 2024-04-29 10:28, Bo YU wrote:
> Tags: patch
>
> hi,
> On Thu, Apr 18, 2024 at 10:00:30PM +0200, Sebastian Ramacher wrote:
>>
>> checking for libconfig... no
>> checking for main in -llibconfig... no
>> configure: error:
Hi Wouter,
On Wed, 03 Apr 2024 14:17:38 +0200 Wouter Verhelst wrote:
tags 1066831 + upstream fixed-upstream pending
thanks
Can we have a fix for this in sid? That would help with some ongoing
transitions, and probably with some installability issues on arm* on testing.
Thanks,
Emilio
Processing commands for cont...@bugs.debian.org:
> found 1070745 2.74.6-2+deb12u1
Bug #1070745 {Done: Simon McVittie } [libglib2.0-0] Bug on
Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my
keyboard no longer work
Ignoring request to alter found versions of bug
Processing commands for cont...@bugs.debian.org:
> found 1070743 2.74.6-2+deb12u1
Bug #1070743 {Done: Simon McVittie } [src:glib2.0] glib2.0:
Can't type special characters in most applications
Marked as found in versions glib2.0/2.74.6-2+deb12u1.
> found 1070743 2.80.0-10
Bug #1070743 {Done:
Your message dated Thu, 9 May 2024 12:12:20 +0100
with message-id
and subject line Re: Bug#1070730 etc.: libglib2.0-0: ibus input regression
has caused the Debian Bug report #1070745,
regarding Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the
dead keys on my keyboard no
Your message dated Thu, 9 May 2024 12:12:20 +0100
with message-id
and subject line Re: Bug#1070730 etc.: libglib2.0-0: ibus input regression
has caused the Debian Bug report #1070743,
regarding glib2.0: Can't type special characters in most applications
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> tags 1070795 + d-i
Bug #1070795 [xfsprogs-udeb] xfsprogs-udeb: the udeb is empty (size 904 bytes)
so does not contain mkfs.xfs
Added tag(s) d-i.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1070795:
Ñ la Kate de casa de mi hermana. N. 3344
55
Processing commands for cont...@bugs.debian.org:
> found 1070769 1.36.3-1
Bug #1070769 [src:nbdkit] nbdkit: BD-Uninstallable on armel: linux-image-marvell
Marked as found in versions nbdkit/1.36.3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1070769:
Package: xfsprogs-udeb
Version: 6.7.0-2
Severity: grave
User: debian...@lists.debian.org
Usertags: openqa
Hi,
Recent openQA tests show that it is not currently possible to create an XFS
filesystem using the latest debian-installer:
https://openqa.debian.net/tests/259699#step/install_base/13
Processing commands for cont...@bugs.debian.org:
> # t64 changes are active in trixie
> severity 1064284 serious
Bug #1064284 {Done: Benjamin Drung } [src:pcp] pcp: NMU diff
for 64-bit time_t transition
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact
On 2024-05-09 11:19:59 +0200, Petter Reinholdtsen wrote:
> I am unable to replicate this in the current unstable chroot. Any idea
> how to reproduce the problem?
I gave it back on the buildds. Let's see if it works now.
Cheers
--
Sebastian Ramacher
I am unable to replicate this in the current unstable chroot. Any idea
how to reproduce the problem?
--
Happy hacking
Petter Reinholdtse
Your message dated Thu, 09 May 2024 08:51:26 +
with message-id
and subject line Bug#1064672: fixed in virt-manager 1:4.1.0-4
has caused the Debian Bug report #1064672,
regarding virt-manager: FTBFS: AssertionError: Command was: ./virt-xml
test-for-virtxml --add-device --host-device
Your message dated Thu, 09 May 2024 10:11:02 +0200
with message-id <6be4b5ffbabbdaf4dff25f1164bbf...@debian.org>
and subject line Re: Bug#1062383 dolfinx-mpc: NMU diff for 64-bit time_t
transition
has caused the Debian Bug report #1062383,
regarding dolfinx-mpc: NMU diff for 64-bit time_t
close 1070395 1.11.1-4
found 1070395 1.11.1-2.1
thanks
Processing commands for cont...@bugs.debian.org:
> close 1070395 1.11.1-4
Bug #1070395 [src:tinyproxy] tinyproxy: CVE-2023-49606
Marked as fixed in versions tinyproxy/1.11.1-4.
Bug #1070395 [src:tinyproxy] tinyproxy: CVE-2023-49606
Marked Bug as done
> found 1070395 1.11.1-2.1
Bug #1070395 {Done:
Processing control commands:
> retitle -1 tinyproxy: CVE-2023-49606
Bug #1070395 [src:tinyproxy] tinyproxy: CVE-2023-40533 CVE-2023-49606
Changed Bug title to 'tinyproxy: CVE-2023-49606' from 'tinyproxy:
CVE-2023-40533 CVE-2023-49606'.
--
1070395:
Control: retitle -1 tinyproxy: CVE-2023-49606
Hi,
CVE-2023-40533 as a duplicate of CVE-2022-40468 .
Regards,
Salvatore
Hi all,
it indeed seems that this issue hasn't been caused by any recent
cpp-httplib update, since I've been able to reproduce it on versions as
old as 0.10.8+ds-1.
I suspect maybe an OpenSSL update broke something for this package? Why
didn't ci.d.n notice the breakage?
I'll try to see if I
Hello,
On Sat, 2024-04-20 at 14:05 +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on arm64.
> (...)
> The full build log is available from:
> http://qa-logs.debian.net/2024/04/20/kiwi_9.25.22-1_unstable-arm64.log
>
> All bugs filed during
Source: coq-corn
Version: 8.19.0-1
Severity: serious
Hello, looks like there are at least two issues:
1) fta directory was stripped on tarball import, not sure how and why, because
the upstream repo still contains it
(this makes autopkgtest fail)
2) the produced binary package looks empty
64 matches
Mail list logo
