Am 13.10.22 um 01:23 schrieb Peter Green:
3. Apply the upstream fix as Debian packages, hope any resulting API breakage
is manageable.
I did a quick regex search on https://codesearch.debian.not/ for
"\bshndx\b package:^rust*", and that only revealed two source packages, namely
Your message dated Thu, 13 Oct 2022 01:49:09 +
with message-id
and subject line Bug#1019292: fixed in gnome-calls 43.0-2
has caused the Debian Bug report #1019292,
regarding gnome-calls FTBFS on IPV6-only buildds
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 13 Oct 2022 01:34:08 +
with message-id
and subject line Bug#1020024: fixed in pydoctor 22.9.1-2
has caused the Debian Bug report #1020024,
regarding git-buildpackage: FTBFS: ModuleNotFoundError: No module named
'filelock'
to be marked as done.
This means that you
https://ci.debian.net/data/autopkgtest/testing/s390x/r/rust-object/26973632/log.gz
test round_trip::elf::symtab_shndx ... FAILED
I noticed this and filed a bug upstream soon after the package was uploaded.
https://github.com/gimli-rs/object/issues/456
And a fix appeared fairly shortly.
Control: tag -1 pending
Hello,
Bug #1019292 in gnome-calls 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 #1019292 [src:gnome-calls] gnome-calls FTBFS on IPV6-only buildds
Added tag(s) pending.
--
1019292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: zxing-cpp
Version: 1.4.0-1~exp2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
zxing-cpp/experimental recently started to FTBFS (but the version in sid
is not affected).
...
[ 90%] Building CXX object
On Wed, Oct 12, 2022 at 10:40:29PM +0200, László Böszörményi (GCS) wrote:
> On Wed, Oct 12, 2022 at 10:36 PM Olly Betts wrote:
> > On Tue, Oct 11, 2022 at 11:28:53PM +0200, Sebastian Ramacher wrote:
> > > The following packages have unmet dependencies:
> > > libwxsqlite3-3.2-dev : Breaks:
Your message dated Wed, 12 Oct 2022 21:18:18 +
with message-id
and subject line Bug#1021622: fixed in wxsqlite3 3.4.1~dfsg-9
has caused the Debian Bug report #1021622,
regarding libwxsqlit3-3.0-dev: not coinstallable
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 12 Oct 2022 21:11:51 +
with message-id
and subject line Bug#953224: fixed in golang-github-xanzy-go-gitlab 0.73.1-1
has caused the Debian Bug report #953224,
regarding golang-github-xanzy-go-gitlab: autopkgtest failure: certificate
signed by unknown authority
to be
Your message dated Wed, 12 Oct 2022 21:14:26 +
with message-id
and subject line Bug#1021407: fixed in python-pretend 1.0.9-2.1
has caused the Debian Bug report #1021407,
regarding python-pretend: please drop pypy-pretend to support python2.7 removal
to be marked as done.
This means that you
On Wed, Oct 12, 2022 at 10:36 PM Olly Betts wrote:
> On Tue, Oct 11, 2022 at 11:28:53PM +0200, Sebastian Ramacher wrote:
> > The following packages have unmet dependencies:
> > libwxsqlite3-3.2-dev : Breaks: libwxsqlite3-3.0-dev but 3.4.1~dfsg-8 is to
> > be installed
> > E: Unable to correct
title -1 libwxsqlite3-3.0-dev: not coinstallable
On Tue, Oct 11, 2022 at 11:28:53PM +0200, Sebastian Ramacher wrote:
> The following packages have unmet dependencies:
> libwxsqlite3-3.2-dev : Breaks: libwxsqlite3-3.0-dev but 3.4.1~dfsg-8 is to
> be installed
> E: Unable to correct problems, you
Control: severity -1 normal
Control: tags -1 unreproducible
Control: close -1
Am 12.10.22 um 21:38 schrieb Matteo Settenvini:
Okay, I retried and I cannot reproduce it now.
I think what happened is:
* my system was hanging at the beginning due to some unrelated problem
with video (mesa).
*
Processing control commands:
> severity -1 normal
Bug #1021672 [udev] udev: No USB (no keyboard nor FIDO token!) at boot after
update from udev 251.5-1 to 252.5-2
Severity set to 'normal' from 'critical'
> tags -1 unreproducible
Bug #1021672 [udev] udev: No USB (no keyboard nor FIDO token!) at
Processing control commands:
> tag -1 pending
Bug #953224 [src:golang-github-xanzy-go-gitlab] golang-github-xanzy-go-gitlab:
autopkgtest failure: certificate signed by unknown authority
Added tag(s) pending.
--
953224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953224
Debian Bug
Control: tag -1 pending
Hello,
Bug #953224 in golang-github-xanzy-go-gitlab 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:
Source: rust-object
Version: 0.29.0-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
https://ci.debian.net/data/autopkgtest/testing/s390x/r/rust-object/26973632/log.gz
test round_trip::elf::symtab_shndx ... FAILED
failures:
round_trip::elf::symtab_shndx stdout
thread
Okay, I retried and I cannot reproduce it now.
I think what happened is:
* my system was hanging at the beginning due to some unrelated problem
with video (mesa).
* I rebooted from a pendrive, and regenerated the initrd with dracut
and hostonly=yes.
* I believe this somehow messed up the
How can I instruct the kernel to save the logs to a file?
The rootfs is not mounted (so the logs cannot be persisted by
journald), and I have no keyboard to be dropped to a init shell and
save e.g. /run/initramfs/rdsosreport.txt or the output of any log in
RAM to an unencrypted partition.
I
Hi Benjamin,
we discussed this in #debian-devel yesterday and found:
For armel it fails at:
https://github.com/audacity/audacity/blob/master/libraries/lib-utility/MemoryX.h#L622
which was introduced here:
https://github.com/audacity/audacity/pull/3028
And for s390x it is:
124 | #error
Processing commands for cont...@bugs.debian.org:
> forwarded 1021675 https://github.com/sanger-pathogens/ariba/issues/327
Bug #1021675 [src:ariba] ariba: autopkgtest regression and ftbfs with samtools
1.16
Set Bug forwarded-to-address to
'https://github.com/sanger-pathogens/ariba/issues/327'.
>
Processing commands for cont...@bugs.debian.org:
> tags 1017157 + pending
Bug #1017157 [libowfat-dev] libowfat byte.h incompatible with glibc 2.34
Bug #1017316 [libowfat-dev] libowfat byte.h incompatible with glibc 2.34
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing
Processing commands for cont...@bugs.debian.org:
> tags 1018739 + pending
Bug #1018739 {Done: Paul Gevers } [src:libowfat]
src:libowfat: fails to migrate to testing for too long: FTBFS
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing control commands:
> block 1019706 by -1
Bug #1019706 {Done: Paul Gevers } [src:r-bioc-monocle]
src:r-bioc-monocle: fails to migrate to testing for too long: new dependency
not ready to migrate
1019706 was not blocked by any bugs.
1019706 was not blocking any bugs.
Added blocking
Source: r-cran-leidenbase
Version: 0.1.12-1
Severity: serious
Control: block 1019706 by -1
https://ci.debian.net/data/autopkgtest/testing/arm64/r/r-cran-leidenbase/26869942/log.gz
...
BEGIN TEST testthat.R
R version 4.2.1 (2022-06-23) -- "Funny-Looking Kid"
Copyright (C) 2022 The R Foundation
Source: ariba
Version: 2.14.6+ds-3
Severity: serious
Tags: ftbfs upstream help
Justification: fails to build from source (but built successfully in the past)
Greetings,
Following the upgrade of htslib, samtools and bcftools from
versions 1.13 to 1.16, ariba hits autopkgtest regressions which
are
Processing commands for cont...@bugs.debian.org:
> severity 1021174 serious
Bug #1021174 [src:unrar-free] unrar-free: non-source file in Debian tests
Severity set to 'serious' from 'important'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1021174:
Control: fixed -1 1:27.2~
On Mon, 25 Apr 2022 15:40:26 +0200 Vincent Lefevre
wrote:
Control: forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42827
On 2022-04-25 15:37:08 +0200, Vincent Lefevre wrote:
> This is also fixed in upstream's 27.2.
2020-08-17 Robert Pluim
Fix
Processing control commands:
> close -1 3.8.1-1
Bug #1021674 [src:kpcli] src:kpcli: fails to migrate to testing for too long:
uploader built arch:all binary
Marked as fixed in versions kpcli/3.8.1-1.
Bug #1021674 [src:kpcli] src:kpcli: fails to migrate to testing for too long:
uploader built
Processing control commands:
> fixed -1 1:27.2~
Bug #1010152 [emacs-gtk] emacs-gtk: tries to read a config file from another
user's home dir
There is no source info for the package 'emacs-gtk' at version '1:27.2~' with
architecture ''
Unable to make a source version for version '1:27.2~'
Marked
Source: kpcli
Version: 3.7-1
Severity: serious
Control: close -1 3.8.1-1
Tags: sid bookworm 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 60 days
Am 12.10.22 um 20:18 schrieb Michael Biebl:
Please remove "debug" from the kernel command line and capture the log
messages
I meant to say "quiet".
You can also add "systemd.log_level=debug" to increase the verbosity.
See man kernel-command-line.
OpenPGP_signature
Description: OpenPGP
On Wed, 12 Oct 2022 19:39:40 +0200 Matteo Settenvini
wrote:
Package: udev
Version: 251.5-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
I have a root partition (separate from the boot partition) which is
encrypted with LUKS and unlocked at boot.
After an
Your message dated Wed, 12 Oct 2022 17:50:40 +
with message-id
and subject line Bug#1020161: fixed in golang-golang-x-net
1:0.0+git20221012.0b7e1fb+dfsg-1
has caused the Debian Bug report #1020161,
regarding golang-golang-x-net: FTBFS: make: *** [debian/rules:11: binary] Error
25
to be
Your message dated Wed, 12 Oct 2022 17:05:06 +
with message-id
and subject line Bug#1020145: fixed in prometheus 2.33.5+ds1-3
has caused the Debian Bug report #1020145,
regarding prometheus: FTBFS: make[1]: *** [debian/rules:74:
override_dh_auto_build] Error 25
to be marked as done.
This
On Wed, Oct 12, 2022 at 12:31:58PM +0200, Bernhard Schmidt wrote:
> Am 11.10.22 um 18:19 schrieb Dennis Filder:
>
> > The change in 5.0.37-6 was tiny and I doubt it broke something. But
> > maybe you're running into #1021125: liblinphone10:amd64 5.0.37-6 is
> > already linked against
Source: lnav
Version: 0.11.1~rc1-1~exp1
Severity: serious
Tags: help
Justification: FTBFS
X-Debbugs-Cc: car...@debian.org,debian-m...@lists.debian.org
Hi
lnav/0.11.1~rc1-1~exp1 in experimental with the new upstream version
0.11.1~rc1 FTBFS on mipsel:
Processing control commands:
> tags -1 patch
Bug #1020081 [src:aft] aft: FTBFS: make: *** [debian/rules:47: binary-indep]
Error 25
Added tag(s) patch.
--
1020081: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020081
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: aft
Followup-For: Bug #1020081
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Control: tags -1 patch
Dear Maintainer,
The last upload of aft changed the format of a doc file from HTML to
RTF. The packaging was not updated accordingly.
This prevents the
Am 12.10.2022 um 11:22 teilte Cédric Boutillier mit:
Hi,
For the record, please find attached one of the latex files produced
with kramdown which was causing the problematic character, together with
the output of the failing compilation log with latex from
texlive-latex-base/2022.20220722-1,
Package: gcc-12-offload-nvptx
Version: 12.2.0-5
Severity: grave
Justification: renders package unusable for nvidia
Dear Maintainer,
the nvptx plugin for gcc-12 currently available for sid mandates a
cuda level sm_30, which is no longer available in cuda 11 (the one
now in sid). This means that
Your message dated Wed, 12 Oct 2022 15:08:09 +
with message-id
and subject line Bug#1020032: fixed in gdb 12.1-4
has caused the Debian Bug report #1020032,
regarding gdb-bpf: FTBFS: completer.c:2014:10: error: invalid conversion from
‘const char*’ to ‘char*’ [-fpermissive]
to be marked as
Your message dated Wed, 12 Oct 2022 15:08:09 +
with message-id
and subject line Bug#1020001: fixed in gdb 12.1-4
has caused the Debian Bug report #1020001,
regarding gdb-bpf: FTBFS: completer.c:2014:10: error: invalid conversion from
‘const char*’ to ‘char*’ [-fpermissive]
to be marked as
Your message dated Wed, 12 Oct 2022 15:08:09 +
with message-id
and subject line Bug#1020001: fixed in gdb 12.1-4
has caused the Debian Bug report #1020001,
regarding gdb: FTBFS: completer.c:2014:10: error: invalid conversion from
‘const char*’ to ‘char*’ [-fpermissive]
to be marked as done.
Your message dated Wed, 12 Oct 2022 15:08:09 +
with message-id
and subject line Bug#1020032: fixed in gdb 12.1-4
has caused the Debian Bug report #1020032,
regarding gdb: FTBFS: completer.c:2014:10: error: invalid conversion from
‘const char*’ to ‘char*’ [-fpermissive]
to be marked as done.
Your message dated Wed, 12 Oct 2022 15:08:09 +
with message-id
and subject line Bug#1020032: fixed in gdb 12.1-4
has caused the Debian Bug report #1020032,
regarding gdb: FTBFS with readline 8.2 due to constness changes
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 12 Oct 2022 15:08:09 +
with message-id
and subject line Bug#1020001: fixed in gdb 12.1-4
has caused the Debian Bug report #1020001,
regarding gdb: FTBFS with readline 8.2 due to constness changes
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 12 Oct 2022 15:08:09 +
with message-id
and subject line Bug#1018821: fixed in gdb 12.1-4
has caused the Debian Bug report #1018821,
regarding gdb: FTBFS: completer.c:2014:10: error: invalid conversion from
‘const char*’ to ‘char*’ [-fpermissive]
to be marked as done.
Your message dated Wed, 12 Oct 2022 15:08:09 +
with message-id
and subject line Bug#1018821: fixed in gdb 12.1-4
has caused the Debian Bug report #1018821,
regarding gdb-bpf: FTBFS: completer.c:2014:10: error: invalid conversion from
‘const char*’ to ‘char*’ [-fpermissive]
to be marked as
Your message dated Wed, 12 Oct 2022 15:08:09 +
with message-id
and subject line Bug#1018821: fixed in gdb 12.1-4
has caused the Debian Bug report #1018821,
regarding gdb: FTBFS with readline 8.2 due to constness changes
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> severity -1 normal
Bug #940139 [nautilus] nautilus: open files by double clicking or right click
"open"
Severity set to 'normal' from 'serious'
> tags -1 -moreinfo
Bug #940139 [nautilus] nautilus: open files by double clicking or right click
"open"
Ignoring
Control: severity -1 normal
Control: tags -1 -moreinfo
Are you still experiencing this issue?
Could you make a new user, log in as the new user and verify whether
the new user is affected by this issue?
Thank you,
Jeremy Bicha
Your message dated Wed, 12 Oct 2022 14:50:49 +
with message-id
and subject line Bug#1020131: fixed in pyfftw 0.13.0-2
has caused the Debian Bug report #1020131,
regarding pyfftw: FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_clean]
Error 25
to be marked as done.
This means that you
Your message dated Wed, 12 Oct 2022 14:36:27 +
with message-id
and subject line Bug#1002314: fixed in genx 3.0.2-2
has caused the Debian Bug report #1002314,
regarding genx: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.10 3.9" --dir genx returned exit
Your message dated Wed, 12 Oct 2022 13:04:56 +
with message-id
and subject line Bug#1012769: fixed in intel-mkl 2020.4.304-3
has caused the Debian Bug report #1012769,
regarding intel-mkl: autopkgtest regression in testing
to be marked as done.
This means that you claim that the problem has
This appears to be fixed locally for me by rebuilding openmpi against
the latest pmix.
I'm doing a rebuild now
Alastair
On 11/10/2022 16:50, Andreas Beckmann wrote:
Package: libpmix2
Version: 4.2.1-2
Severity: serious
Hi,
the new pmix version in sid causes autopkgtest regressions, e.g.
Am 11.10.22 um 18:19 schrieb Dennis Filder:
The change in 5.0.37-6 was tiny and I doubt it broke something. But
maybe you're running into #1021125: liblinphone10:amd64 5.0.37-6 is
already linked against soci/4.0.3-1, but liblime0 5.0.37+dfsg-4 is
still linked against soci/4.0.1-5 and there was
Control: notfound -1 2022.20220923-1
Am 12.10.2022 um 11:22 teilte Cédric Boutillier mit:
This bug seems caused by a transient bug due to a non-UTF8 character in
one of the included files by latex(?). This problem was present with
texlive-latex-base 2022.20220722-1, but after the recent
Processing control commands:
> notfound -1 2022.20220923-1
Bug #1016272 [texlive-latex-base] ruby-kramdown: FTBFS: ERROR: Test "ruby3.0"
failed: ArgumentError: invalid byte sequence in UTF-8
Ignoring request to alter found versions of bug #1016272 to the same values
previously set
--
1016272:
This bug seems caused by a transient bug due to a non-UTF8 character in
one of the included files by latex(?). This problem was present with
texlive-latex-base 2022.20220722-1, but after the recent upgrade to
2022.20220923-1, the problem has disappeared, and all tests pass.
For the record, please
Processing commands for cont...@bugs.debian.org:
> found 1016272 texlive-latex-base/2022.20220722-1
Bug #1016272 [texlive-latex-base] ruby-kramdown: FTBFS: ERROR: Test "ruby3.0"
failed: ArgumentError: invalid byte sequence in UTF-8
The source texlive-latex-base and version 2022.20220722-1 do not
Processing commands for cont...@bugs.debian.org:
> notfound 1016272 texlive-latex-base/2022.20220923-1
Bug #1016272 [texlive-latex-base] ruby-kramdown: FTBFS: ERROR: Test "ruby3.0"
failed: ArgumentError: invalid byte sequence in UTF-8
The source texlive-latex-base and version 2022.20220923-1 do
Processing commands for cont...@bugs.debian.org:
> reassign 1016272 texlive-latex-base
Bug #1016272 [src:ruby-kramdown] ruby-kramdown: FTBFS: ERROR: Test "ruby3.0"
failed: ArgumentError: invalid byte sequence in UTF-8
Bug reassigned from package 'src:ruby-kramdown' to 'texlive-latex-base'.
No
Processing control commands:
> reassign -1 ftp.debian.org
Bug #994212 [ftpmaster.debian.org] ROM: r-cran-gprofiler: Obsolete package,
replaced with r-cran-gprofiler2
Warning: Unknown package 'ftpmaster.debian.org'
Bug reassigned from package 'ftpmaster.debian.org' to 'ftp.debian.org'.
Ignoring
Control: reassign -1 ftp.debian.org
Please remove falcon and r-cran-gprofiler
Processing control commands:
> reassign -1 ftp.debian.org
Bug #1015978 [ftpmaster.debian.org] RM: falcon -- RoM; Depends on Python 2
Warning: Unknown package 'ftpmaster.debian.org'
Bug reassigned from package 'ftpmaster.debian.org' to 'ftp.debian.org'.
Ignoring request to alter found versions of
Processing commands for cont...@bugs.debian.org:
> forwarded 1021062
> http://git.savannah.gnu.org/cgit/readline.git/commit/?id=7274faabe97ce53d6b464272d7e6ab6c1392837b
Bug #1021062 [libreadline8] bash: non existent locale crashes bash
Set Bug forwarded-to-address to
Your message dated Wed, 12 Oct 2022 06:12:53 +
with message-id
and subject line Bug#1020702: fixed in slic3r-prusa 2.5.0+dfsg-2
has caused the Debian Bug report #1020702,
regarding prusa-slicer: SEGV on start
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> forwarded 1021109
> http://git.savannah.gnu.org/cgit/bash.git/commit/?id=a99d905216cc0aac5de0c3050f4afc54e21c6bc5
Bug #1021109 [bash] bash: non existent locale crashes bash
Set Bug forwarded-to-address to
70 matches
Mail list logo
