Hi Matthias,
I think it would be enough to add the tzdata-legacy dependency to
libpython3.11-testsuite.
I've also send a patch upstream to switch to the normal name:
https://github.com/python/cpython/pull/108533
Cheers Jochen
* Debian Bug Tracking System [2023-08-26 19:09]:
This is an aut
Source: dpf-plugins
Version: 1.6+ds-2
Severity: serious
Control: close -1 1.7+ds-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
Processing control commands:
> close -1 1.7+ds-1
Bug #1050614 [src:dpf-plugins] src:dpf-plugins: fails to migrate to testing for
too long: uploader built arch:all binaries
Marked as fixed in versions dpf-plugins/1.7+ds-1.
Bug #1050614 [src:dpf-plugins] src:dpf-plugins: fails to migrate to testing
Processing control commands:
> close -1 0.57.1+dfsg-1
Bug #1050613 [src:numba] src:numba: fails to migrate to testing for too long:
triggers autopkgtest failure
Marked as fixed in versions numba/0.57.1+dfsg-1.
Bug #1050613 [src:numba] src:numba: fails to migrate to testing for too long:
triggers
Source: numba
Version: 0.56.4+dfsg-2
Severity: serious
Control: close -1 0.57.1+dfsg-1
X-Debbugs-CC: python-spa...@packages.debian.org
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: affects -1 src:python-sparse
Dear maintainer(s),
The Release Team co
Dirk Eddelbuettel 于2023年8月27日周日 00:15写道：
>
>
> Hi all,
>
> As the test failures for complex valued variables appeared to be systemic on
> the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and
> conditioned the number of failing tests away via
>
> @pytest.mark.skipif(platfo
Your message dated Sun, 27 Aug 2023 04:18:53 +
with message-id
and subject line Bug#1041128: fixed in qcodeeditor 1.0+1gitdc644d-2
has caused the Debian Bug report #1041128,
regarding qcodeeditor FTBFS with googletest 1.13.0
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 27 Aug 2023 03:18:58 +
with message-id
and subject line Bug#1041090: fixed in valijson 1.0+repack-3
has caused the Debian Bug report #1041090,
regarding valijson FTBFS with googletest 1.13.0
to be marked as done.
This means that you claim that the problem has been deal
On Aug 26, Jon Westgate <0...@fsck.tv> wrote:
> The error message it gave was "decompresson failed with status 6"
Status 6 is XZ_OPTIONS_ERROR, which means "Input was encoded with
settings that are not supported by this XZ decoder".
So it looks like you have compressed the modules (how?) with XZ
Package: xcb
Version: 2.4-8
Severity: grave
Justification: renders package unusable
Dear Maintainer,
With standard bookworm Gnome desktop...
[farlap.949] $ whence xcb
'xcb -n 33 -l v -geometry -0+0'
[farlap.950] $ which xcb
/bin/xcb
[farlap.951] $ strings /bin/xcb | grep "^lib"
libXaw.so.7
libXt
Your message dated Sat, 26 Aug 2023 23:18:56 +
with message-id
and subject line Bug#1050526: fixed in dask 2023.8.0+dfsg-2
has caused the Debian Bug report #1050526,
regarding dask: autopkgtest regression on s390x
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> forwarded 1050526 https://github.com/dask/dask/issues/10423
Bug #1050526 [src:dask] dask: autopkgtest regression on s390x
Set Bug forwarded-to-address to 'https://github.com/dask/dask/issues/10423'.
> thanks
Stopping processing here.
Please conta
Processing control commands:
> tag -1 pending
Bug #1050526 [src:dask] dask: autopkgtest regression on s390x
Added tag(s) pending.
--
1050526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1050526 in dask 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:
https://salsa.debian.org/python-team/packages/dask/-/commit/08ffea1b7b53e9c71c9a926d5
Dear Marco,
I'm using XZ if I turn off compression my initrd fails it's too big.
Jon
On 26/08/2023 22:25, Marco d'Itri wrote:
On Aug 26, Jon Westgate wrote:
Yes I am using compressed modules
And are these modules compressed with xz or something else?
This new code was introduced in the lat
Package: cryptsetup-suspend
Version: 2:2.6.1-4
Severity: serious
The cryptsetup-suspend wrapper makes unconditional use of the
/lib/systemd/system-sleep directory.
This directory was removed from the systemd package as a result of the
discussion in https://salsa.debian.org/systemd-team/systemd/-/
Package: src:linux
Version: 6.4.11-1
Severity: grave
Justification: renders package unusable
The recent update of linux-image to version 6.4.0-3 causes this laptop unable to
boot. As the boot was not successful I could not check the log through dmesg so
I will attach a photo later.
The relevant
Processing commands for cont...@bugs.debian.org:
> clone 1049983 -1
Bug #1049983 {Done: Shengjing Zhu } [syncthing] panic:
connection already exists
Bug 1049983 cloned as bug 1050603
> severity -1 normal
Bug #1050603 {Done: Shengjing Zhu } [syncthing] panic:
connection already exists
Severity se
Processing commands for cont...@bugs.debian.org:
> retitle 1050582 kmod is broken with custom kernels with
> CONFIG_MODULE_COMPRESS_*=y
Bug #1050582 [kmod] kmod update corrupts systemd uefi boot
Bug #1050586 [kmod] kmod: Updating to kmod to 30+20230601-1 results in a non
booting system modules c
On Aug 26, Jon Westgate wrote:
> Yes I am using compressed modules
And are these modules compressed with xz or something else?
This new code was introduced in the latest snapshot, and apparently it
fails when used with kernels with compressed modules support enabled
(which so far is not the de
Yes I am using compressed modules
On 26/08/2023 18:34, Marco d'Itri wrote:
On Aug 26, Jon Westgate <0...@fsck.tv> wrote:
The system partially booted but systemd then prevented boot due to missing
modules,
The error message it gave was "decompresson failed with status 6"
Are you using compress
CONFIG_MODULE_SIG=y
# CONFIG_MODULE_SIG_FORCE is not set
# CONFIG_MODULE_SIG_ALL is not set
# CONFIG_MODULE_SIG_SHA1 is not set
# CONFIG_MODULE_SIG_SHA224 is not set
CONFIG_MODULE_SIG_SHA256=y
# CONFIG_MODULE_SIG_SHA384 is not set
# CONFIG_MODULE_SIG_SHA512 is not set
CONFIG_MODULE_SIG_HASH="sha25
Source: eja
Severity: serious
Version: 9.5.20-1
eja does not seem to be used a lot anymore. I intend to file a RM bug. If you have any reasons to keep it in Debian
please voice them here. To get people's attention, I am filing as a serious bug and will reassign to the FTP team when
the package
Your message dated Sat, 26 Aug 2023 19:05:36 +
with message-id
and subject line Bug#1050530: fixed in python3.11 3.11.5-2
has caused the Debian Bug report #1050530,
regarding python3.11: autopkgtest needs update for new version of tzdata
to be marked as done.
This means that you claim that th
Found this:
# CONFIG_MODULE_COMPRESS_NONE is not set
# CONFIG_MODULE_COMPRESS_GZIP is not set
CONFIG_MODULE_COMPRESS_XZ=y
# CONFIG_MODULE_COMPRESS_ZSTD is not set
Il 26/08/23 19:57, Marco d'Itri ha scritto:
On Aug 26, antonio wrote:
Kernel: Linux 6.4.12-1-liquorix-amd64 (SMP w/24 CPU thread
Package: perl
Version: 5.36.0-8
Severity: serious
X-Debbugs-Cc: debian-powe...@lists.debian.org
Control: affects -1 libfile-fcntllock-perl
Hi,
debugging an unexpected autopkgtest failure of
libfile-fcntllock-perl_0.22-4+b1 with perl_5.36.0-8 on ppc64el [1] I found
it's because the old perl binary
Processing control commands:
> affects -1 libfile-fcntllock-perl
Bug #1050592 [perl] perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking
libfile-fcntllock-perl
Added indication that 1050592 affects libfile-fcntllock-perl
--
1050592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050592
On Aug 26, Jon Westgate <0...@fsck.tv> wrote:
> Kernel: Linux 6.4.11 (SMP w/12 CPU threads; PREEMPT)
I see that you are using a custom kernel. What is the status of the
CONFIG_MODULE_COMPRESS_* kernel configuration options?
--
ciao,
Marco
signature.asc
Description: PGP signature
On Aug 26, antonio wrote:
> Kernel: Linux 6.4.12-1-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
I see that you are using a custom kernel. What is the status of the
CONFIG_MODULE_COMPRESS_* kernel configuration options?
--
ciao,
Marco
signature.asc
Description: PGP signature
On Aug 26, Jon Westgate <0...@fsck.tv> wrote:
> The system partially booted but systemd then prevented boot due to missing
> modules,
> The error message it gave was "decompresson failed with status 6"
Are you using compressed modules?
--
ciao,
Marco
signature.asc
Description: PGP signature
Processing commands for cont...@bugs.debian.org:
> forcemerge 1050586 1050582
Bug #1050586 [kmod] kmod: Updating to kmod to 30+20230601-1 results in a non
booting system modules cannot be decompressed
Bug #1050582 [kmod] kmod update corrupts systemd uefi boot
Severity set to 'grave' from 'normal'
Your message dated Sat, 26 Aug 2023 16:37:36 +
with message-id
and subject line Bug#1050432: fixed in rpy2 3.5.13-4
has caused the Debian Bug report #1050432,
regarding rpy2: FTBFS on mips64el
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Hi all,
As the test failures for complex valued variables appeared to be systemic on
the 'mips64el' platform, I buckled down, taught myself some Python ==:-) and
conditioned the number of failing tests away via
@pytest.mark.skipif(platform.machine() == 'mips64' and sys.byteorder ==
'little',
Package: kmod
Version: 30+20230601-1
Severity: grave
Justification: renders system unusable
Dear Maintainer,
I just did a normal apt upgrade and the following packages were upgraded:
kmod 30+20230519-1 to 30-2.230601-1
libkmod2 30+20230519-1 to 30-2.230601-1
The system partially booted but syste
On Fri, Aug 25, 2023 at 08:52:49PM +0200, François Mazen wrote:
> Dear Antonio,
>
> thanks for the crash report! I can reproduce it easily with unstable
> distribution and the call stack points to pango_font_description_to_string
> method.
>
> The issues seems to have been already reported upstre
Source: trocla
Version: 0.5.1-1
Severity: serious
Hi,
I just uploaded ruby-highline 2.1.0-1. While testing reverse
dependencies, I noticed that it breaks this package.
Lucas
Source: ruby-commander
Version: 4.6.0-1
Severity: serious
Hi,
I just uploaded ruby-highline 2.1.0-1. While testing reverse
dependencies, I noticed that it breaks this package.
Lucas
Hi Emanuele,
Am Fri, Aug 25, 2023 at 02:33:28PM +0200 schrieb Emanuele Rocca:
> > btllib (1.4.10+dfsg-1) unstable; urgency=medium
>
> [...]
>
> > So I'm wondering why this bug came up at all and closing it hereby.
>
> Ah yes, the reason why it came up is that btllib-tools is still Architectur
Source: ruby-html-proofer
Version: 3.19.2-7
Severity: serious
Hi,
I just uploaded ruby-nokogiri 1.15.4, and while testing reverse
dependencies, noticed that it breaks this package.
Lucas
Source: ruby-roxml
Version: 4.2.0-1
Severity: serious
Hi,
I just uploaded ruby-nokogiri 1.15.4, and while testing reverse
dependencies, noticed that it breaks this package.
Lucas
Your message dated Sat, 26 Aug 2023 13:04:06 +
with message-id
and subject line Bug#1050366: fixed in opencolorio 2.1.2+dfsg1-4.1
has caused the Debian Bug report #1050366,
regarding opencolorio: FTBFS with newer yaml-cpp [PATCH]
to be marked as done.
This means that you claim that the proble
control: tags -1 patch pending
Hello, attached debdiff uploaded to sid.
diff -Nru opencolorio-2.1.2+dfsg1/debian/changelog
opencolorio-2.1.2+dfsg1/debian/changelog
--- opencolorio-2.1.2+dfsg1/debian/changelog2022-08-20 23:39:40.0
+0200
+++ opencolorio-2.1.2+dfsg1/debian/changelog
Processing control commands:
> tags -1 patch pending
Bug #1050366 [src:opencolorio] opencolorio: FTBFS with newer yaml-cpp [PATCH]
Added tag(s) pending.
--
1050366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sat, 26 Aug 2023 12:36:30 +
with message-id
and subject line Bug#1043500: fixed in rust-winnow 0.5.15-1
has caused the Debian Bug report #1043500,
regarding librust-winnow-dev: impossible to install
to be marked as done.
This means that you claim that the problem has been d
Thank you for your detailed bug report.
I built the nsis_3.09-1 and nsis-common_3.09-1 packages on Debian
Bookworm, installed the resulting packages and can confirm with the two
Nullsoft Installer (.nsi) scripts provided by you that the resulting
installer executables no longer show the "(.rel
Processing control commands:
> severity -1 important
Bug #1042048 [src:python-ase] python-ase: FTBFS: E: Build killed with signal
TERM after 150 minutes of inactivity
Severity set to 'important' from 'serious'
> tags -1 + unreproducible
Bug #1042048 [src:python-ase] python-ase: FTBFS: E: Build ki
Control: severity -1 important
Control: tags -1 + unreproducible
Hi Lucas
I'm unable to reproduce this failure locally, also python-ase builds
successfully on reproducible builds [1].
Regards
Graham
[1] https://tests.reproducible-builds.org/debian/rb-pkg/python-ase.html
Your message dated Sat, 26 Aug 2023 11:05:14 +
with message-id
and subject line Bug#1050557: fixed in abyss 2.3.7-2
has caused the Debian Bug report #1050557,
regarding abyss: FTBFS: error: possibly dangling reference to a temporary
[-Werror=dangling-reference]
to be marked as done.
This mea
Your message dated Sat, 26 Aug 2023 10:50:15 +
with message-id
and subject line Bug#1017663: fixed in ghc 9.4.6-1
has caused the Debian Bug report #1017663,
regarding Please upgrade to llvm-toolchain-14
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Processing control commands:
> tag -1 pending
Bug #1050557 [src:abyss] abyss: FTBFS: error: possibly dangling reference to a
temporary [-Werror=dangling-reference]
Added tag(s) pending.
--
1050557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050557
Debian Bug Tracking System
Contact ow..
Control: tag -1 pending
Hello,
Bug #1050557 in abyss 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:
https://salsa.debian.org/med-team/abyss/-/commit/6b436c46ac14f056dec7d35f7ed70f0caeb
Processing control commands:
> tags -1 + confirmed
Bug #1050557 [src:abyss] abyss: FTBFS: error: possibly dangling reference to a
temporary [-Werror=dangling-reference]
Added tag(s) confirmed.
--
1050557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050557
Debian Bug Tracking System
Conta
Control: tags -1 + confirmed
Hi Aurélien,
Aurelien Jarno, on 2023-08-26:
> | GfaIO.h:182:27: error: possibly dangling reference to a temporary
> [-Werror=dangling-reference]
Thank you for your report, this seems to be one of those cases
where the newly introduced warnings in gcc 13 are getting
Processing commands for cont...@bugs.debian.org:
> affects 1050185 rust-derive-builder-macro rust-derive-builder
> rust-cargo-metadata rust-skeptic rust-err-derive
Bug #1050185 [rust-derive-builder-core] rust-derive-builder-core - depends on
old version of darling.
Added indication that 1050185
Source: abyss
Version: 2.3.7-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
abyss fails to build from source. From my build log on amd64:
| Making all in Graph
| make[4]: Entering directory '/<>/Graph'
| g++ -std=c+
55 matches
Mail list logo
