Processing control commands:
> reopen -1
Bug #1064232 {Done: Jonas Smedegaard } [src:rust-axum]
rust-axum: Failing autopkgtests
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer mark
Control: reopen -1
> Oh - now after I did a release without the feature-fencing patch, I
> found the relevant build log:
> https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-axum/47457177/log.gz
the most recent run at
https://ci.debian.net/packages/r/rust-axum/testing/amd64/49206913/
fai
Your message dated Fri, 19 Jul 2024 05:51:04 +
with message-id
and subject line Bug#1076490: fixed in snapd 2.63-4
has caused the Debian Bug report #1076490,
regarding src:snapd: fails to migrate to testing for too long: autopkgtest
regression
to be marked as done.
This means that you claim
Package: hplip-gui
Version: 3.22.10+dfsg0-5
Followup-For: Bug #1075760
dear maintainer please release a new build with the patch from
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075760#22, i have patched
locally and was able to configure my hp multifunctional on a fresh testing
suite instal
Package: pkg-kde-tools
Version: 0.17.4
Severity: serious
I just started working towards updating one of my packages to Qt6 and
KF6 and I was shocked to find that dh-sequence-kf6 doesn't append
"-DQT_MAJOR_VERSION=6" to cmake configure arguments.
KF6 + "-DQT_MAJOR_VERSION=5" is nonsensical, so the
Your message dated Thu, 18 Jul 2024 22:22:53 +
with message-id
and subject line Bug#1029189: fixed in kpatch 0.9.9-1
has caused the Debian Bug report #1029189,
regarding kpatch: FTBFS with shellcheck 0.9.0
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Hi,
On 2024-05-06 23:14, Aurelien Jarno wrote:
> Dear maintainers,
>
> glibc 2.38 introduced changes to the bits/math-vector.h file on arm64 in
> order to support math vector functions. This unfortunately caused the
> FTBFS of your packages.
>
> The change has been temporarily reverted in versio
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package libuv1
> # 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
Setting
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:binutils
> # 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
Se
Your message dated Thu, 18 Jul 2024 19:01:07 +
with message-id
and subject line Bug#1076112: Removed package(s) from unstable
has caused the Debian Bug report #1074276,
regarding Depends on gpac
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
Processing commands for cont...@bugs.debian.org:
> close 1064022 0.12.7-0.1
Bug #1064022 [src:editorconfig-core] editorconfig-core: FTBFS on i386: error:
Could not create output directory /<>/obj-i686-linux-gnu/doc/man
Marked as fixed in versions editorconfig-core/0.12.7-0.1.
Bug #1064022 [src:ed
On Tue, Jul 09, 2024 at 07:41:11PM +0200, Sebastian Ramacher wrote:
> Source: elpa
> Version: 2022.11.001-3
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
>...
> GetSockInterfaceAddr(369)...
On Thu, Jul 18, 2024 at 06:55:03PM +0200, Paul Gevers wrote:
> Release Team member here. mono is a key package [1], meaning it's hard to
> remove. I note that src:mono is at least needed for src:gdcm which is at
> least needed for src:opencv which is at least needed for src:ffmpeg.
src:gdcm could
Hello,
>I guess the proper fix consists in adding a dependency on the
>"dcmtk-data" package (with a fixed version of dcmtk) in the
>"orthanc-wsi" package. I fear that the same issue will be detected on
>other DCMTK-related packages. I will now try to add this dependency,
>in the hope it will solve
Hi all,
On Mon, 3 Jun 2024 23:06:45 +0500 Andrey Rakhmatullin
wrote:
> keeping the current outdated build is much more useful than not having
> access to Mono at all from Debian repositories.
Considering the amount of packages depending on mono, removing it from
testing is probably out of ques
Your message dated Thu, 18 Jul 2024 16:19:56 +
with message-id
and subject line Bug#1075961: fixed in kamailio 5.8.2-3
has caused the Debian Bug report #1075961,
regarding FTBFS: hep.c:985:41: error: implicit declaration of function
‘inet_ntop’
to be marked as done.
This means that you claim
Looking more closely at the fine print in the upstream issues, the issue
here refers to a different line number (and in test_syscall not
test_syscall_swap). But I guess the same principle applies for dealing
with it.
Processing commands for cont...@bugs.debian.org:
> forwarded 1076418 https://github.com/tokio-rs/axum/issues/2835
Bug #1076418 {Done: Jonas Smedegaard } [src:rust-axum] FTBFS:
undeclared type `TestClient`
Set Bug forwarded-to-address to 'https://github.com/tokio-rs/axum/issues/2835'.
> thanks
Sto
I should be more specific. "long chain" is subjective.
Cluster installations need autofs,
which is blocked by sssd
which is blocked by this arm-32 issue with uid-wrapper.
Processing commands for cont...@bugs.debian.org:
> forwarded 1069425 https://bugzilla.samba.org/show_bug.cgi?id=15445
Bug #1069425 [src:uid-wrapper] uid-wrapper: FTBFS on armhf: 15: [ LINE ]
--- ./tests/test_syscall.c:53: error: Failure!
Set Bug forwarded-to-address to
'https://bugzilla.samb
forwarded 1069425 https://bugzilla.samba.org/show_bug.cgi?id=15445
thanks
see also https://bugzilla.samba.org/show_bug.cgi?id=15448
Please skip test_syscall (at least on arm-32) as suggested in the
upstream issue if you think it's not a meaningful test.
This bug is holding up a long chain of
Processing commands for cont...@bugs.debian.org:
> forwarded 1075961 https://github.com/kamailio/kamailio/issues/3927
Bug #1075961 [src:kamailio] FTBFS: hep.c:985:41: error: implicit declaration of
function ‘inet_ntop’
Set Bug forwarded-to-address to
'https://github.com/kamailio/kamailio/issues/
Le jeu. 18 juil. 2024 à 17:03, Сергей Сёмин a
écrit :
> I built source package nodejs_18.19.0+dfsg-6~deb12u2 in Debian
> Bookworm i386 and installed result deb packages into system.
> Packages with dbgsym were also installed.
> Then I tried to reproduce segfault with simple way explained earlier
Your message dated Thu, 18 Jul 2024 15:06:22 +
with message-id
and subject line Bug#1076418: fixed in rust-axum 0.6.20-23
has caused the Debian Bug report #1076418,
regarding FTBFS: undeclared type `TestClient`
to be marked as done.
This means that you claim that the problem has been dealt wi
I built source package nodejs_18.19.0+dfsg-6~deb12u2 in Debian
Bookworm i386 and installed result deb packages into system.
Packages with dbgsym were also installed.
Then I tried to reproduce segfault with simple way explained earlier
and now I see better more informative backtrace with mentioned s
Quoting Reinhard Tartler (2024-07-18 06:44:00)
> Reinhard Tartler writes:
> > Why does this error not reproduce outside of autopkgtest? -- either some
> > dependency mismatch in debian, or somethign really subtle in
> > autopkgtest. In either case, I'd like to keep my suggestion to disable
> > the
Hi Micah,
Le 11 juillet 2024 13:06:48 UTC, micah anderson a écrit :
>
>Hello,
>
>In April you had said that you were going to try and upload a new
>version of torsocks, which fixes the FTBFS, but you were trying to fix a
>few lintian issues first.
Sorry about that, the issues that prevented
Processing control commands:
> tags -1 + patch pending
Bug #1060545 [src:drbd-utils] drbd-utils: Please switch Build-Depends to
systemd-dev
Added tag(s) pending and patch.
--
1060545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060545
Debian Bug Tracking System
Contact ow...@bugs.debian.
Control: tags -1 + patch pending
I've uploaded an updated package to DELAYED/14.
Please find a debdiff attached.
Regards,
Michael
diff -Nru drbd-utils-9.22.0/debian/changelog drbd-utils-9.22.0/debian/changelog
--- drbd-utils-9.22.0/debian/changelog 2023-01-09 15:51:18.0 +0100
+++ drbd-
Your message dated Thu, 18 Jul 2024 13:34:28 +
with message-id
and subject line Bug#1060568: fixed in fence-agents 4.12.1-1.1
has caused the Debian Bug report #1060568,
regarding fence-agents: Please switch Build-Depends to systemd-dev
to be marked as done.
This means that you claim that the
Your message dated Thu, 18 Jul 2024 13:20:15 +
with message-id
and subject line Bug#1070350: fixed in xorg 1:7.7+23.1
has caused the Debian Bug report #1070350,
regarding xorg-dev: drop dependency on libdmx-dev
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Thu, 18 Jul 2024 13:04:39 +
with message-id
and subject line Bug#1076541: fixed in orthanc-wsi 2.0+dfsg-4
has caused the Debian Bug report #1076541,
regarding orthanc-wsi: autopkgtest failures (binNMU needed)
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> tags 1073001 patch fixed-upstream
Bug #1073001 [src:buildbot] buildbot FTBFS: python3-sqlalchemy (<< 1.5) no
longer satisfiable
Added tag(s) fixed-upstream and patch.
>
End of message, stopping processing here.
Please contact me if you need assi
It is fixed upstream:
https://github.com/buildbot/buildbot/commit/291df50dc3f27adb47a001fc154cf4c55490687e
Dear Gianfranco,
Thanks for your report. From my understanding, this issue is related
to the creation of the "dcmtk-data" package by the following changeset
in the "dcmtk" package:
https://salsa.debian.org/med-team/dcmtk/-/commit/f0f9dfaa22ad85fe8d3cee302fb6ba766f703c8e
This changeset has the eff
Your message dated Thu, 18 Jul 2024 11:20:15 +
with message-id
and subject line Bug#1073352: fixed in ruby-libxml 5.0.3-1
has caused the Debian Bug report #1073352,
regarding ruby-libxml: FTBFS: ruby_xml_encoding.h:12:27: error: unknown type
name ‘xmlChar’
to be marked as done.
This means th
Your message dated Thu, 18 Jul 2024 11:20:15 +
with message-id
and subject line Bug#1072017: fixed in ruby-libxml 5.0.3-1
has caused the Debian Bug report #1072017,
regarding ruby-libxml: new upstream release, addressing test failures with
libxml2 >= 2.12
to be marked as done.
This means tha
I found a very simple way to reproduce segfault in nodejs when using browserify.
Take Debian Bookworm i386, upgraded in to last versions of packages
with this repos:
deb http://deb.debian.org/debian bookworm contrib main non-free-firmware
deb-src http://deb.debian.org/debian bookworm contrib main
Control: severity -1 minor
On 18 Jul 2024 09:43:38 +0200 Bastian Venthur wrote:
> Package: plymouth
> Version: 24.004.60-2
> Severity: important
> X-Debbugs-Cc: vent...@debian.org
>
> Dear Maintainer,
>
> trying to update plymouth fails with "No space left on device":
>
> sudo aptitude -u
> Pe
Processing control commands:
> severity -1 minor
Bug #1076539 [firmware-misc-nonfree] plymouth: Updating plymouth fails with "No
space left on device"
Severity set to 'minor' from 'serious'
--
1076539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076539
Debian Bug Tracking System
Contact
Source: nodejs
Version: 20.15.1+dfsg-1
Severity: serious
Hello, two tests are now failing:
https://ci.debian.net/packages/n/nodejs/testing/amd64/49188413/
45s not ok 253 parallel/test-cli-permission-multiple-allow
45s ---
45s duration_ms: 715.29500
45s severity: fail
45s exitcode: 1
Source: orthanc-wsi
Version: 2.0+dfsg-3
Severity: serious
Hello, looks like orthanc-wsi detects the path of the dicom dictionary at build
time.
So, it needs to be tied to a specific libdcmtk library, and needs a binNMU
every time dcmtk changes version.
43s autopkgtest [14:07:35]: test run-
Processing commands for cont...@bugs.debian.org:
> reassign 1076539 firmware-misc-nonfree 20240610-1
Bug #1076539 [plymouth] plymouth: Updating plymouth fails with "No space left
on device"
Bug reassigned from package 'plymouth' to 'firmware-misc-nonfree'.
No longer marked as found in versions pl
Source: ucx
Version: 1.16.0+ds-5
Severity: serious
Control: close -1 1.17.0+ds-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: affects -1 src:openmpi
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and u
Processing control commands:
> close -1 1.17.0+ds-2
Bug #1076537 [src:ucx] src:ucx: fails to migrate to testing for too long:
unhandled architecture drop
Marked as fixed in versions ucx/1.17.0+ds-2.
Bug #1076537 [src:ucx] src:ucx: fails to migrate to testing for too long:
unhandled architecture
Processing control commands:
> close -1 1.0.35+~cs11.0.28-1
Bug #1076535 [src:node-websocket] src:node-websocket: fails to migrate to
testing for too long: FTBFS on armel
Marked as fixed in versions node-websocket/1.0.35+~cs11.0.28-1.
Bug #1076535 [src:node-websocket] src:node-websocket: fails to
Source: node-websocket
Version: 1.0.34+~cs10.0.25-2
Severity: serious
Control: close -1 1.0.35+~cs11.0.28-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
Processing control commands:
> close -1 6.4.0-1
Bug #1076534 [src:importlib-resources] src:importlib-resources: fails to
migrate to testing for too long: autopkgtest regression on s390x
Marked as fixed in versions importlib-resources/6.4.0-1.
Bug #1076534 [src:importlib-resources] src:importlib-r
Source: importlib-resources
Version: 6.0.1-1
Severity: serious
Control: close -1 6.4.0-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 2024.5.2+ds.1-2
Bug #1076533 [src:dask.distributed] src:dask.distributed: fails to migrate to
testing for too long: autopkgtest regression
Marked as fixed in versions dask.distributed/2024.5.2+ds.1-2.
Bug #1076533 [src:dask.distributed] src:dask.distributed
Source: dask.distributed
Version: 2023.12.1+ds-4
Severity: serious
Control: close -1 2024.5.2+ds.1-2
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
51 matches
Mail list logo
