Hi,
On Wed, 15 May 2024 10:16:55 +0200 Emilio Pozuelo Monfort
wrote:
If this can't be fixed in the
short term by adding some type of restriction to the autopkgtest
or by mocking the devices, then the tests should be removed until
they can be made to work on our infrastructure.
The autopkgtes
Processing control commands:
> close -1 5.73-1
Bug #1072270 [src:bluez] src:bluez: fails to migrate to testing for too long:
autopkgtest failure
Marked as fixed in versions bluez/5.73-1.
Bug #1072270 [src:bluez] src:bluez: fails to migrate to testing for too long:
autopkgtest failure
Marked Bug
Source: python-arrow
Version: 1.2.3-1
Severity: serious
Control: close -1 1.3.0-1
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 3
Source: bluez
Version: 5.71-1
Severity: serious
Control: close -1 5.73-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1071147
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for
Processing control commands:
> close -1 1.3.0-1
Bug #1072269 [src:python-arrow] src:python-arrow: fails to migrate to testing
for too long: uploader built arch:all binaries
Marked as fixed in versions python-arrow/1.3.0-1.
Bug #1072269 [src:python-arrow] src:python-arrow: fails to migrate to test
Processing control commands:
> close -1 13.2.1-1
Bug #1072268 [src:rake] src:rake: fails to migrate to testing for too long:
causes autopkgtest issues
Marked as fixed in versions rake/13.2.1-1.
Bug #1072268 [src:rake] src:rake: fails to migrate to testing for too long:
causes autopkgtest issues
Source: rake
Version: 13.0.6-3
Severity: serious
Control: close -1 13.2.1-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 days as havi
severity -1 important
Hi Ralph,
Thanks for reporting this bug.
Further comments below...
Quoting Ralf Jung (2024-05-27 08:54:53)
> Severity: grave
> Justification: causes non-serious data loss
[...]
> after upgrading radicale, my devices are no longer able to access my
> calendar. The same cal
Hi,
Thanks for your build test.
I fixed bug in salsa:
https://salsa.debian.org/atzlinux-guest/psensor/-/commit/8da335a77089e65b265f09e39732bc60005c6f15
Reuploaded:
https://mentors.debian.net/package/psensor/
Regards,
在 2024/5/31 01:11, Santiago Vila 写道:
Hi.
The new release still FTBFS
Your message dated Fri, 31 May 2024 02:35:07 +
with message-id
and subject line Bug#1072246: fixed in libcloud 3.8.0+repack-2
has caused the Debian Bug report #1072246,
regarding libcloud: regression with pytest 8.2
to be marked as done.
This means that you claim that the problem has been dea
Your message dated Thu, 30 May 2024 20:05:55 -0400
with message-id
and subject line Thanks
has caused the Debian Bug report #999646,
regarding squid-deb-proxy-client: uncaptured python exception breaks client
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Installing the new SID version worked fine on Bookworm.
Thanks.
On Sat, May 25, 2024 at 10:32 AM Michael Vogt wrote:
> Hey,
>
> Thanks for your kind offer to help! I uploaded a new version to unstable
> today that adds the patch, so if you could double check that things are
> good now (and ma
Package: python3-vitrage
Version: 12.0.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package is no longer
installable in sid:
python3-vitrage depends on python-pysnmp-lextudio and python3-pysnmp4,
but these two are not co
Non the bug seems resolved.
BR
Le 31 mai 2024 00:40:24 GMT+02:00, "Jeremy Bícha"
a écrit :
>Are you still experiencing this crash with evolution 3.52.1 in Debian
>Testing (or 3.52.2 which will reach Testing in a few days)?
>
>Thank you,
>Jeremy Bícha
--
Envoyé de mon appareil Android avec Cou
Are you still experiencing this crash with evolution 3.52.1 in Debian
Testing (or 3.52.2 which will reach Testing in a few days)?
Thank you,
Jeremy Bícha
Your message dated Thu, 30 May 2024 22:05:50 +
with message-id
and subject line Bug#1072140: fixed in rust-bytecodec 0.4.15-2
has caused the Debian Bug report #1072140,
regarding rust-bytecodec: FTBFS: error: doctest failed
to be marked as done.
This means that you claim that the problem has
Source: libcloud
Version: 3.8.0+repack-1
Severity: serious
Tags: ftbfs patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
pytest 8.2 has begun relying on the fact that unittest.TestCase objects should
be instantiable with (empty) default arguments, which does not work for th
Package: wxglade
Version: 1.0.5+repack-2
Severity: grave
Tags: patch
Wxglade crashes with a segmentation fault on startup. See below for the
output. This is fixed upstream by this commit:
https://github.com/wxGlade/wxGlade/commit/05943a8374a24b862e76f03643a775c09582703f
I also attached this as a
Processing control commands:
> close -1 0.9.9+ds.1-2
Bug #1072243 [src:zmat] src:zmat: fails to migrate to testing for too long:
FTBFS on non-x86
Marked as fixed in versions zmat/0.9.9+ds.1-2.
Bug #1072243 [src:zmat] src:zmat: fails to migrate to testing for too long:
FTBFS on non-x86
Marked Bug
Source: zmat
Version: 0.9.8+ds-8
Severity: serious
Control: close -1 0.9.9+ds.1-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1068683
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and uns
Your message dated Thu, 30 May 2024 20:35:47 +
with message-id
and subject line Bug#1072139: fixed in rust-bytecheck 0.6.12-1
has caused the Debian Bug report #1072139,
regarding rust-bytecheck: FTBFS: error: doctest failed
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 30 May 2024 20:37:43 +
with message-id
and subject line Bug#1072209: fixed in slurm-wlm-contrib 23.11.7-2
has caused the Debian Bug report #1072209,
regarding slurm-wlm-contrib: uninstallable in sid
to be marked as done.
This means that you claim that the problem has b
Hi,
On Sun, 19 May 2024 16:25:01 +0100 "Rebecca N. Palmer"
wrote:
Filing a bug against two packages means that it could be fixed in
*either* of them, *not* that it requires changes to both of them.
Hence, it is correct that this bug was closed.
While I recall it's documented like this, this
Source: git-delta
Version: 0.16.5-5
Severity: serious
Control: close -1 0.17.0-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 d
Processing control commands:
> close -1 0.17.0-1
Bug #1072242 [src:git-delta] src:git-delta: fails to migrate to testing for too
long: FTBFS on arm64, armel and ppc64el
Marked as fixed in versions git-delta/0.17.0-1.
Bug #1072242 [src:git-delta] src:git-delta: fails to migrate to testing for too
Source: manpages
Version: 6.05.01-1
Severity: serious
Control: close -1 6.8-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1072158
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstabl
Processing control commands:
> close -1 6.8-1
Bug #1072241 [src:manpages] src:manpages: fails to migrate to testing for too
long: RC bug and B-D not in testing
Marked as fixed in versions manpages/6.8-1.
Bug #1072241 [src:manpages] src:manpages: fails to migrate to testing for too
long: RC bug a
Hi.
[Just in case you're not aware, the BTS doesn't forward replies to the
bug submitter unless they are subscribed. If you want to have the
submitters attention, please add them explicitly.]
On Wed, 29 May 2024 19:55:19 +0200 Philippe SWARTVAGHER
wrote:
Well, this issue is "normal".
Curr
Source: dracut
Version: 060+5-8
Followup-For: Bug #1071182
Tags: patch
The following patch addresses the case where /usr and possibly /etc are
mounted read-only in the initrd, and therefore fixes the error messsages
mentioned in my previous email.
From: Holger Weiss
Date: Thu, 30 May 2024 21
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:scikit-fmm
> # 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
Hi.
The new release still FTBFS in AWS machines of type m6a.large
and r6a.large. See attach.
I still recommend that you address this bug if you plan to make
a new upload. If you need a machine to reproduce the failure,
please contact me privately.
Thanks.
psensor_1.2.1-1_amd64.build.gz
Descrip
On 2024-05-27 Daniel Kahn Gillmor wrote:
[...]
> Would anyone be willing to try to backport the patches from upstream's
> fixes for T6481 to the 2.2.x series?
Hello Daniel,
the issue report refers to two patches, one of these is already part of
2.2.43. The other one[1] seemed pretty straightforw
The new upstream version 1.2.1-1 build success in my local notebook now.
There are many change between version 1.1.5-1.4 and 1.2.1-1.
If 1.2.1-1 upload and build success, this FTBFS bug will fixed.
If FTBFS still exist in 1.2.1-1, I'll address this bug.
在 2024/5/30 21:57, Santiago Vila 写道:
El
Processing commands for cont...@bugs.debian.org:
> tags 1071378 + upstream
Bug #1071378 [src:linux] linux-image-6.7.12-686-pae: Crash during early boot
Added tag(s) upstream.
> forwarded 1071378
> https://lore.kernel.org/regressions/ebb0791c-60a5-4fe3-bc85-4921ad026...@heusipp.de/
Bug #1071378 [s
Your message dated Thu, 30 May 2024 15:35:11 +
with message-id
and subject line Bug#1060572: fixed in wireguard 1.0.20210914-1.1
has caused the Debian Bug report #1060572,
regarding wireguard: Please switch Build-Depends to systemd-dev
to be marked as done.
This means that you claim that the
Processing control commands:
> tags -1 pending patch
Bug #1060572 [src:wireguard] wireguard: Please switch Build-Depends to
systemd-dev
Added tag(s) pending and patch.
--
1060572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060572
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tags -1 pending patch
On Thu, 11 Jan 2024 23:36:53 +0100 bi...@debian.org wrote:
> Source: wireguard
> Version: 1.0.20210914-1
> Severity: normal
> User: pkg-systemd-maintain...@lists.alioth.debian.org
> Usertags: systemd-dev
>
> Hi,
>
> your package wireguard declares a Build-Depends o
El 30/5/24 a las 15:24, xiao sheng wen(肖盛文) escribió:
I'm ITS psensor package, it's upload to mentor.d.n now.
https://mentors.debian.net/package/psensor/
In my opinion, if you are going to make a new upload
to become the new maintainer, then you should really
address this bug.
Thanks.
Hi Paul,
On 2024-04-06 11:38, Paul Gevers wrote:
> I noticed you "binNMU"-ed siridb-server in Ubuntu where it built
> successfully on all arches. In Debian I got the bug below reported. Any idea
> what the difference could be between the state of Debian and the state of
> Ubuntu that causes this?
Hi,
I'm ITS psensor package, it's upload to mentor.d.n now.
https://mentors.debian.net/package/psensor/
Welcome to review and upload.
Thanks!
在 2024/5/30 19:10, Santiago Vila 写道:
reopen 1071336
thanks
El 30/5/24 a las 11:15, xiao sheng wen(肖盛文) escribió:
psensor can build success now:
Hey,
On 2023-11-05 04:12, Hervé Werner wrote:
> I faced this issue on real data but I struggled to find a reliable scenario
> to reproduce it. Here is what I just came up with:
> sudo mkfs -t ext4 -O fast_commit,inline_data /dev/sdb
> sudo mount /dev/sdb /mnt/
> sudo install -d -o myuser /m
Processing commands for cont...@bugs.debian.org:
> tags 1032555 + ftbfs
Bug #1032555 [nvda2speechd] nvda2speechd fails to build due to the external
network access
Added tag(s) ftbfs.
> tags 1036369 + ftbfs
Bug #1036369 [ruby-rest-client] ruby-rest-client: network-dependent tests fail
Added tag(s)
Followup-For: Bug #1070429
Control: tag -1 patch pending
Hi,
I've just uploaded the attached patch to DELAYED/5. Please let me know
if I should delay it longer.
Andreas
diff -Nru libcapi20-3-3.27/debian/changelog libcapi20-3-3.27/debian/changelog
--- libcapi20-3-3.27/debian/changelog 2024-02-
Processing control commands:
> tag -1 patch pending
Bug #1070429 [libcapi20-dev] libcapi20-dev: copyright file missing (policy 12.5)
Added tag(s) patch and pending.
--
1070429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
On Thu, 2024-05-16 at 08:09 +0200, Paul Gevers wrote:
> Hi Ben (and all the rest),
>
> On 15-05-2024 9:56 p.m., Ben Hutchings wrote:
> > Apologies for leaving this bug for so long.
>
> NP, part of live I guess.
>
> > Is this bug still occurring?
>
> I don't know. The problem was severe enough f
Package: python3-proto-plus
Version: 1.23.0-2
Severity: serious
Justification: policy 10.1
python3-proto-plus declares a conflict with nanopb. Doing so violates
Debian policy section 10.1. More background can be found in #1072073.
Helmut
Processing commands for cont...@bugs.debian.org:
> reopen 1071336
Bug #1071336 {Done: xiao sheng wen(肖盛文) } [src:psensor]
psensor: FTBFS: FAIL test-cppcheck.sh
Bug reopened
Ignoring request to alter fixed versions of bug #1071336 to the same values
previously set
> thanks
Stopping processing her
reopen 1071336
thanks
El 30/5/24 a las 11:15, xiao sheng wen(肖盛文) escribió:
psensor can build success now:
https://buildd.debian.org/status/fetch.php?pkg=psensor&arch=amd64&ver=1.1.5-1.4%2Bb1&stamp=1710303742&raw=0
No, that was 78 days ago.
The build failure started to happen recently, this
Package: slurm-wlm-contrib
Version: 23.11.7-1
Severity: Serious
Hello, can you please also consider relaxing a bit the dependency between them?
I'm not even sure if they are compatible or not, this is why I'm not tagging
"patch"
diff -Nru slurm-wlm-contrib-23.11.7/debian/control
slurm-wlm-con
Package: click
Version: 0.5.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'bookworm'.
It installed fine in 'bookworm', then the upgrade to 'trixie' fails.
>From the attached log (scroll to th
Hello, I'm attaching a patch that applies cleanly.
I'm testing the build
G.
On Wed, 29 May 2024 23:31:23 +0200 =?utf-8?q?Timo_R=C3=B6hling?=
wrote:
Source: fenics-dolfinx
Version: 1:0.8.0-6
Severity: serious
Tags: patch
Dear maintainer,
upgrading to nanobind 2.0 made your package FTBFS. I a
Your message dated Thu, 30 May 2024 17:15:06 +0800
with message-id <2fbb9635-a768-4b84-9e8f-215699156...@sina.com>
and subject line Verison: 1.1.5-1.4+b1
has caused the Debian Bug report #1071336,
regarding psensor: FTBFS: FAIL test-cppcheck.sh
to be marked as done.
This means that you claim that
On 30.05.24 10:45, Jörn Heusipp wrote:
>
> On 30/05/2024 09:27, Linux regression tracking (Thorsten Leemhuis) wrote:
>> On 30.05.24 08:55, Jörn Heusipp wrote:
>>> commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 ("x86/sev-es: Set
>>> x86_virt_bits to the correct value straight away, instead of a tw
Hello!
On 30/05/2024 09:27, Linux regression tracking (Thorsten Leemhuis) wrote:
On 30.05.24 08:55, Jörn Heusipp wrote:
commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 ("x86/sev-es: Set
x86_virt_bits to the correct value straight away, instead of a two-phase
approach") crashes during boot f
Processing control commands:
> tags -1 patch pending
Bug #1072201 [rtags] rtags: autopkgtest failure due to missing depends on emacs
Added tag(s) patch and pending.
--
1072201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> tags -1 patch pending
Bug #1072201 [rtags] rtags: autopkgtest failure due to missing depends on emacs
Ignoring request to alter tags of bug #1072201 to the same tags previously set
--
1072201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072201
Debian Bug Tra
Control: tags -1 patch pending
Xiyue Deng writes:
> Package: rtags
> Version: 2.38-10
> Severity: serious
>
> Dear Maintainer,
>
> rtags is now failing autopkgtest due to missing dependency on emacs.
> See the autopkgtest regression test from flycheck[1]. It used to work
> because it pulls in e
On 30.05.24 08:55, Jörn Heusipp wrote:
>
> Hello x86 maintainers!
>
> commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 ("x86/sev-es: Set
> x86_virt_bits to the correct value straight away, instead of a two-phase
> approach") crashes during boot for me on this 32bit x86 system.
FWIW, not my area o
Hello x86 maintainers!
commit fbf6449f84bf5e4ad09f2c09ee70ed7d629b5ff6 ("x86/sev-es: Set
x86_virt_bits to the correct value straight away, instead of a two-phase
approach") crashes during boot for me on this 32bit x86 system.
Updating a Debian testing system resulted in a hang during boot bef
59 matches
Mail list logo
