Your message dated Wed, 27 Oct 2021 05:03:32 +
with message-id
and subject line Bug#997779: fixed in node-test 0.6.0-11
has caused the Debian Bug report #997779,
regarding node-retape: FTBFS: Error: Cannot find module 'test/test/fail-fast'
to be marked as done.
This means that you claim that
Control: tag -1 pending
Hello,
Bug #997779 in node-test 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 #997779 [node-test] node-retape: FTBFS: Error: Cannot find module
'test/test/fail-fast'
Added tag(s) pending.
--
997779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> affects 997779 node-retape
Bug #997779 [node-test] node-retape: FTBFS: Error: Cannot find module
'test/test/fail-fast'
Added indication that 997779 affects node-retape
> thanks
Stopping processing here.
Please contact me if you need assistance.
Processing commands for cont...@bugs.debian.org:
> reassign 997779 node-test
Bug #997779 [src:node-retape] node-retape: FTBFS: Error: Cannot find module
'test/test/fail-fast'
Bug reassigned from package 'src:node-retape' to 'node-test'.
No longer marked as found in versions node-retape/0.0.3-4.
Hi Nilesh,
Nilesh Patra, on 2021-10-27:
> On 27 October 2021 2:54:02 am IST, "Étienne Mollier"
> wrote:
> >Maarten, I'm sorry that the round trip to NEW I contributed to
> >trigger stalled your package to not make it in the end.
> >On the good news side, now that the package cleared NEW
>
Control: tags -1 pending
(fixed in Salsa, as far as I consider it my bug)
It looks like both of these originate further down the stack, not in
libgpuarray:
The *ger error code is an OpenCL compile failure from inside clblast, so
likely either pocl or clblast.
The *gemv problem appears to
Hi,
On 27 October 2021 2:54:02 am IST, "Étienne Mollier"
wrote:
>Maarten, I'm sorry that the round trip to NEW I contributed to
>trigger stalled your package to not make it in the end.
>On the good news side, now that the package cleared NEW
^
Uhh, sorry but I don't see how this
The piuparts regression is
https://piuparts.debian.org/sid/source/s/slurm-wlm.html
0m23.7s DEBUG: Starting command: ['chroot',
'/srv/piuparts.debian.org/tmp/tmp5ugph549', '/usr/sbin/logrotate',
'/etc/logrotate.d/slurmctld']
0m23.7s DUMP:
/etc/logrotate.d/slurmctld:12 keyword 'size' not
Hi Thorsten, Hi Maarten,
Thorsten Alteholz, on 2021-10-26:
> please update the links in the PDB license block in your debian/copyright.
> They don't seem to be valid anymore.
>
> This is one of the reasons why all license information should be added to the
> package.
Thanks Thorsten for your
Control: tags -1 confirmed
So, there is indeed an ABI breakage in libgclib. I pushed some
changes on Salsa to bump the SONAME to version 3 [1]. Since
this would require a round trip through NEW, I also made some
welcome updates to the copyright file. I haven't uploaded yet,
in case someone
Your message dated Wed, 27 Oct 2021 00:18:41 +
with message-id
and subject line Bug#997909: fixed in xapian-bindings 1.4.18-2
has caused the Debian Bug report #997909,
regarding xapian-bindings: FTBFS with ruby3.0: diff:
debian/tmp/usr/lib/ruby/vendor_ruby/3.0.0/xapian.rb: No such file or
On Tue, Oct 26, 2021 at 06:34:06PM -0300, Antonio Terceiro wrote:
> > rb=debian/tmp`/usr/bin/ruby3.0 -rrbconfig -e 'puts
> > RbConfig::CONFIG["vendorlibdir"]'`/xapian.rb; \
> > for v in 2.7; do \
> > if [ "$v" != "3.0" ] ; then \
> > set -e; \
> > rb_old=debian/tmp`/usr/bin/ruby$v
Control: affects -1 src:gffread 0.12.1-4
Hi Paul,
On Tue, 26 Oct 2021 16:58:28 +0200 Paul Gevers wrote:
> [1] https://qa.debian.org/excuses.php?package=libgclib
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/c/cdbfasta/16212088/log.gz
>
> + cdbfasta ebola.fasta
> cdbfasta: symbol
Processing commands for cont...@bugs.debian.org:
> tags 997382 pending
Bug #997382 [src:theano] theano: FTBFS: AttributeError: 'Sphinx' object has no
attribute 'add_stylesheet'
Added tag(s) pending.
> tags 997026 pending
Bug #997026 [src:libgpuarray] libgpuarray: FTBFS with sphinx 4.2.0
Added
Processing control commands:
> tags -1 pending
Bug #992673 [src:libgpuarray] libgpuarray: *gemv broken on libclblast
Added tag(s) pending.
--
992673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> reassign 997303 python3-dulwich
Bug #997303 [src:xandikos] xandikos: FTBFS: dh_auto_test: error: pybuild --test
-i python{version} -p 3.9 returned exit code 13
Bug reassigned from package 'src:xandikos' to 'python3-dulwich'.
No longer marked as
On Tue, 26 Oct 2021 at 21:54:51 +0200, Sylvestre Ledru wrote:
> Le 26/10/2021 à 20:57, Simon McVittie a écrit :
> > The check that is failing is
> >
> >> if test /usr/share/man/man1/llc-$VERSION.1.gz; then
> > but I assume this should have been something more like:
> > if ! test -f
Source: xapian-bindings
Version: 1.4.18-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, xapian-bindings was found to fail to build in
Your message dated Tue, 26 Oct 2021 21:18:34 +
with message-id
and subject line Bug#997065: fixed in libpmemobj-cpp 1.13.0-3
has caused the Debian Bug report #997065,
regarding libpmemobj-cpp: FTBFS: test failed
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> owner 997412 !
Bug #997412 [src:opencc] opencc: FTBFS: dpkg-gensymbols: error: some symbols or
patterns disappeared in the symbols file: see diff output below
Owner recorded as Gunnar Hjalmarsson .
>
End of message, stopping processing here.
Your message dated Tue, 26 Oct 2021 22:51:18 +0200
with message-id
and subject line Re: mesa: FTBFS on i386 with llvm 13: ‘class
llvm::TargetOptions’ has no member named ‘StackAlignmentOverride’
has caused the Debian Bug report #995786,
regarding mesa: FTBFS on i386 with llvm 13: ‘class
Processing control commands:
> tags -1 confirmed
Bug #997884 [src:libgclib] libgclib breaks cdbfasta autopkgtest: ABI breakage?
Added tag(s) confirmed.
--
997884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi,
On Sun, 24 Oct 2021 23:28:33 +0200 Sebastian Ramacher
wrote:
> Source: aom
> Version: 1.0.0-errata1.avif-1
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
>
> From ffmpeg's autopkgtest:
> | [libaom-av1 @ 0x55ab8a773940] Failed to initialize encoder: ABI version
mismatch
Given that
Processing control commands:
> tag -1 pending
Bug #997884 [src:libgclib] libgclib breaks cdbfasta autopkgtest: ABI breakage?
Added tag(s) pending.
--
997884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #997884 in gclib 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:
Your message dated Tue, 26 Oct 2021 20:35:32 +
with message-id
and subject line Bug#997741: fixed in listparser 0.18-3
has caused the Debian Bug report #997741,
regarding listparser: FTBFS: There is a syntax error in your configuration
file: invalid syntax (conf.py, line 171)
to be marked as
Le 26/10/2021 à 20:57, Simon McVittie a écrit :
> Source: llvm-toolchain-13
> Version: 1:13.0.0-6
> Severity: serious
> Justification: Release Team policy
> Tags: patch
>
> The autopkgtest that uses debian/qualify-clang.sh seems to be failing.
> I think this is a bug in debian/qualify-clang.sh
Hi Ole (2021.10.26_11:38:38_-0700)
> All of that said, there's an easy option for you. If you know your
> package needs network access and you're confident that it's not going to
> try to access the internet, you can just 'export http_proxy=' in
> debian/rules, and that will suppress pybuild
Processing control commands:
> tag -1 pending
Bug #997469 [dh-python] dh-python doesn't allow local connections via urllib
Added tag(s) pending.
--
997469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #997469 in dh-python 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:
Your message dated Tue, 26 Oct 2021 19:33:32 +
with message-id
and subject line Bug#997147: fixed in chroma 1.19-1
has caused the Debian Bug report #997147,
regarding chroma: FTBFS: cursesdisplay.c:497:29: error: format not a string
literal and no format arguments [-Werror=format-security]
Processing control commands:
> close -1 8.16-1
Bug #997905 [src:iwyu] src:iwyu: fails to migrate to testing for too long:
depends on llvm-toolchain-12
Marked as fixed in versions iwyu/8.16-1.
Bug #997905 [src:iwyu] src:iwyu: fails to migrate to testing for too long:
depends on llvm-toolchain-12
Source: iwyu
Version: 8.15-2
Severity: serious
Control: close -1 8.16-1
Tags: sid bookworm
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 as having
Source: llvm-toolchain-13
Version: 1:13.0.0-6
Severity: serious
Justification: Release Team policy
Tags: patch
The autopkgtest that uses debian/qualify-clang.sh seems to be failing.
I think this is a bug in debian/qualify-clang.sh rather than a bug in
the actual packages:
Source: golang-github-go-xorm-builder
Version: 0.3.3-2
Severity: serious
Control: close -1 0.3.3-3
X-Debbugs-CC: jel...@debian.org
Tags: sid bookworm pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are
Processing control commands:
> close -1 0.3.3-3
Bug #997900 [src:golang-github-go-xorm-builder]
src:golang-github-go-xorm-builder: fails to migrate to testing for too long:
uploader built arch:all binaries
Marked as fixed in versions golang-github-go-xorm-builder/0.3.3-3.
Bug #997900
Processing control commands:
> close -1 20.11.8-1
Bug #997899 [src:slurm-wlm] src:slurm-wlm: fails to migrate to testing for too
long: piuparts regression and unresolved RC bug
Marked as fixed in versions slurm-wlm/20.11.8-1.
Bug #997899 [src:slurm-wlm] src:slurm-wlm: fails to migrate to testing
Source: slurm-wlm
Version: 20.11.7+really20.11.4-2
Severity: serious
Control: close -1 20.11.8-1
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 997267
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between
Processing control commands:
> close -1 1.3.5-7
Bug #997898 [src:etbemon] src:etbemon: fails to migrate to testing for too
long: FTBFS everywhere
The source 'etbemon' and version '1.3.5-7' do not appear to match any binary
packages
Marked as fixed in versions etbemon/1.3.5-7.
Bug #997898
Source: etbemon
Version: 1.3.5-6
Severity: serious
Control: close -1 1.3.5-7
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 992896
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable
Processing control commands:
> affects -1 src:gffread 0.12.1-4
Bug #997884 [src:libgclib] libgclib breaks cdbfasta autopkgtest: ABI breakage?
Added indication that 997884 affects src:gffread and 0.12.1-4
--
997884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997884
Debian Bug Tracking
Control: notfound -1 dh-python/5.20211022.1
Not starting a reassign war, but also, this shouldn't block testing
migration of an unrelated version.
This is the expected behaviour of dh-python. It exports http_proxy,
https_proxy, and no_proxy environment variables.
Processing control commands:
> notfound -1 dh-python/5.20211022.1
Bug #997469 [dh-python] dh-python doesn't allow local connections via urllib
No longer marked as found in versions dh-python/5.20211022.1.
--
997469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997469
Debian Bug Tracking
Your message dated Tue, 26 Oct 2021 11:18:48 -0700
with message-id
and subject line Re: llvm-toolchain-12: FTBFS on mipsel|powerpc since
1:12.0.1-10: undefined reference to `_Unwind_Resume' etc.
has caused the Debian Bug report #996798,
regarding llvm-toolchain-12: FTBFS on mipsel|powerpc since
control: severity -1 important
Hi Paul,
Thanks for reporting
On Sun, 17 Oct 2021 21:52:24 +0200 Paul Gevers wrote:
If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally,
Your message dated Tue, 26 Oct 2021 18:00:10 +
with message-id
and subject line Bug#996887: fixed in cmark 0.30.2-2
has caused the Debian Bug report #996887,
regarding gnome-builder does not start up (missing library)
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 26 Oct 2021 18:00:10 +
with message-id
and subject line Bug#996887: fixed in cmark 0.30.2-2
has caused the Debian Bug report #996887,
regarding libcmark0.30.1: 0.30.2 bumps SONAME without changing package name
to be marked as done.
This means that you claim that the
Your message dated Tue, 26 Oct 2021 18:00:26 +
with message-id
and subject line Bug#984330: fixed in sight 21.0.0-1
has caused the Debian Bug report #984330,
regarding sight: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> reopen 997894
Bug #997894 {Done: yokota } [pyqt5-sip] pyqt5-sip:
appears to declare the wrong API version (should be 12.9)
Bug reopened
Ignoring request to alter fixed versions of bug #997894 to the same values
previously set
> severity 997894
reopen 997894
severity 997894 important
affects 997894 calibre
thanks
I'm downgrading severity to important as a humble courtesy, but if my
hypothesis is correct then it really is RC.
Regards,
Nicholas
signature.asc
Description: PGP signature
Control: unblock -1 by 987379
> Processing commands for cont...@bugs.debian.org:
>
>> block 984066 with 987379
> Bug #984066 {Done: Adrian Bunk } [src:irony-mode]
> irony-mode: ftbfs with GCC-11
> 984066 was not blocked by any bugs.
> 984066 was not blocking any bugs.
> Added blocking bug(s) of
Processing control commands:
> unblock -1 by 987379
Bug #984066 {Done: Adrian Bunk } [src:irony-mode] irony-mode:
ftbfs with GCC-11
984066 was blocked by: 987379
984066 was not blocking any bugs.
Removed blocking bug(s) of 984066: 987379
--
984066:
Lucas,
Thanks for reporting. This issue has actually been resolved upstream but
it seems that I uploaded an invalid orig tarball for version 1.11.1 for
the Debian package. Instead of the new upstream tarball 1.11.1, 1.11.0
was still used (when opening the tarball from [0] the folder name is
still
Processing commands for cont...@bugs.debian.org:
> clone 997660 -1
Bug #997660 {Done: yokota } [src:calibre] calibre:
FTBFS: -c: Unable to find file "QtWidgets/QtWidgetsmod.sip"
Bug 997660 cloned as bug 997894
> reassign -1 pyqt5-sip 12.9.0-1
Bug #997894 {Done: yokota } [src:calibre] calibre:
Processing commands for cont...@bugs.debian.org:
> block 984066 with 987379
Bug #984066 {Done: Adrian Bunk } [src:irony-mode] irony-mode:
ftbfs with GCC-11
984066 was not blocked by any bugs.
984066 was not blocking any bugs.
Added blocking bug(s) of 984066: 987379
> thanks
Stopping processing
Processing commands for cont...@bugs.debian.org:
> block 984016 with 996589
Bug #984016 {Done: Adrian Bunk } [src:cloudcompare]
cloudcompare: ftbfs with GCC-11
984016 was not blocked by any bugs.
984016 was not blocking any bugs.
Added blocking bug(s) of 984016: 996589
> thanks
Stopping
Control: affects -1 + tldr
Got the same error msg when running tldr. Downgrading to the testing version
fixed it (aptitude install libcmark0.30.1=0.30.1-2).
signature.asc
Description: This is a digitally signed message part.
Processing control commands:
> affects -1 + tldr
Bug #996887 [libcmark0.30.1] libcmark0.30.1: 0.30.2 bumps SONAME without
changing package name
Bug #997055 [libcmark0.30.1] gnome-builder does not start up (missing library)
Added indication that 996887 affects tldr
Added indication that 997055
clone 997660 -1
reassign -1 pyqt5-sip 12.9.0-1
retitle -1 pyqt5-sip: appears to declare the wrong API version (should be 12.9)
thanks
Alex Relis writes:
> I'm on version 5.30.0+dfsg-1 and I am still experiencing this bug. It hasn't
> been fixed quite yet. Here's the error I seem to be getting:
On Sun, 24 Oct 2021 at 22:30, Paul Gevers wrote:
> I copied some of the output at the bottom of this report. It seems that
> the actual test passes, but there's output on stderr and the default
> behavior of autopkgtest is to fail on output to stderr. If in general
> output to stderr is harmless
Package: calibre
Version: 5.30.0+dfsg-1
Followup-For: Bug #997660
Dear Maintainer,
I'm on version 5.30.0+dfsg-1 and I am still experiencing this bug. It hasn't
been fixed quite yet. Here's the error I seem to be getting:
alex@alex-pc:~$ calibre
Traceback (most recent call last):
File
Source: r-cran-effectsize
Version: 0.5-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of r-cran-effectsize the autopkgtest of
r-cran-effectsize fails in testing on ppc64el when that
Processing control commands:
> tag -1 pending
Bug #996510 [src:ruby-spring] ruby-spring: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed: Errno::ENOENT: No such file or directory @
rb_check_realpath_internal - /tmp/d20211005-1582813-mce9ae
Added tag(s) pending.
--
996510:
Control: tag -1 pending
Hello,
Bug #996510 in ruby-spring 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: prottest
Version: 3.4.2+dfsg-6
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of prottest the autopkgtest of prottest fails in
testing when that autopkgtest is run with the binary
Processing control commands:
> found -1 libgclib/0.12.7+ds-2
Bug #997884 [src:libgclib] libgclib breaks cdbfasta autopkgtest: ABI breakage?
Marked as found in versions libgclib/0.12.7+ds-2.
> affects -1 src:cdbfasta
Bug #997884 [src:libgclib] libgclib breaks cdbfasta autopkgtest: ABI breakage?
Source: python-moreorless
Version: 0.4.0-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of python-moreorless the autopkgtest of
python-moreorless fails in testing when that autopkgtest is
Source: libgclib
Control: found -1 libgclib/0.12.7+ds-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks
Control: affects -1 src:cdbfasta
Dear maintainer(s),
With a recent upload of libgclib the autopkgtest of
Processing control commands:
> affects -1 src:puma
Bug #997883 [src:rails] rails: autopkgtest needs update for new version of
puma: Could not find gem 'puma (~> 4.1)'
Added indication that 997883 affects src:puma
--
997883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997883
Debian Bug
Source: rails
Version: 2:6.0.3.7+dfsg-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, p...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:puma
Dear maintainer(s),
With a recent upload of puma the autopkgtest of
[1] https://qa.debian.org/excuses.php?package=licensecheck
https://ci.debian.net/data/autopkgtest/testing/amd64/l/licensecheck/16222812/log.gz
t/OSI.t .. # Seeded srand with seed '20211026' from
local date.
1..26
ok 1 - Corpus file t/OSI/MPL-1.0
ok 2 - Corpus file t/OSI/EPL-1.0
ok
Your message dated Tue, 26 Oct 2021 14:35:00 +
with message-id
and subject line Bug#997540: fixed in console-data 2:1.12-9
has caused the Debian Bug report #997540,
regarding console-data: FTBFS: ./debian/trim_keymaps.sh: 1: tempfile: not found
to be marked as done.
This means that you claim
Your message dated Tue, 26 Oct 2021 14:35:15 +
with message-id
and subject line Bug#997204: fixed in gtkextra 3.3.4-6
has caused the Debian Bug report #997204,
regarding gtkextra: FTBFS: configure.ac:64: error: AC_CONFIG_MACRO_DIR can only
be used once
to be marked as done.
This means that
Your message dated Tue, 26 Oct 2021 14:36:35 +
with message-id
and subject line Bug#996293: fixed in ruby-httparty 0.18.1-3
has caused the Debian Bug report #996293,
regarding ruby-httparty: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError:
to be marked as done.
This
Source: lebiniou-data
Version: 3.62.2-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of lebiniou-data the autopkgtest of lebiniou-data
fails in testing when that autopkgtest is run with
Processing commands for cont...@bugs.debian.org:
> reopen 993042
Bug #993042 {Done: Federico Ceratto } [src:nim] nim FTBFS
on armhf when built on arm64 hardware
Bug reopened
Ignoring request to alter fixed versions of bug #993042 to the same values
previously set
> fixed 993042 1.6.0-1
Bug
reopen 993042
fixed 993042 1.6.0-1
close 993042
thanks
Closing with the right version
Nilesh
signature.asc
Description: PGP signature
Hi Diederik, all,
On 26-10-2021 08:34, Diederik de Haas wrote:
> Therefor it may be worth trying whether this bug is resolved as well.
Well, it's not fixed in the Debian archive:
https://ci.debian.net/data/autopkgtest/unstable/armhf/l/llvm-toolchain-12/16229260/log.gz
Paul
OpenPGP_signature
Processing control commands:
> severity -1 important
Bug #996734 {Done: Paul Gevers } [src:nim] src:nim: fails to
migrate to testing for too long: ftbfs on armhf
Severity set to 'important' from 'serious'
--
996734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996734
Debian Bug Tracking
Processing control commands:
> found -1 python-click/8.0.2-1
Bug #997878 [src:python-click, src:python-softlayer] python-click breaks
python-softlayer autopkgtest: 'NoneType' object is not iterable
Marked as found in versions python-click/8.0.2-1.
> found -1 python-softlayer/5.8.5-2
Bug #997878
Source: python-click, python-softlayer
Control: found -1 python-click/8.0.2-1
Control: found -1 python-softlayer/5.8.5-2
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent
Processing control commands:
> affects -1 src:python-click
Bug #997877 [src:mailman3] mailman3: autopkgtest needs update for new version
of python-click: changed messages
Added indication that 997877 affects src:python-click
--
997877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997877
Source: mailman3
Version: 3.3.3-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-click
[X-Debbugs-CC: debian...@lists.debian.org, python-cl...@packages.debian.org]
Dear maintainer(s),
With a recent upload of
Your message dated Tue, 26 Oct 2021 13:48:56 +
with message-id
and subject line Bug#997168: fixed in scottfree 1.14-11
has caused the Debian Bug report #997168,
regarding scottfree: FTBFS: ScottCurses.c:402:32: error: format not a string
literal and no format arguments
Processing control commands:
> found -1 astroid/2.8.2-1
Bug #997875 [src:astroid] astroid breaks pylint-flask autopkgtest: No module
named 'typing_extensions'
Marked as found in versions astroid/2.8.2-1.
--
997875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997875
Debian Bug Tracking
Source: astroid
Control: found -1 astroid/2.8.2-1
Severity: serious
Tags: sid bookworm
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks
Dear maintainer(s),
With a recent upload of astroid the autopkgtest of pylint-flask fails in
testing when that
Source: django-uwsgi
Version: 1.1.2-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of django-uwsgi the autopkgtest of django-uwsgi
fails in testing when that autopkgtest is run with the
Processing control commands:
> tag -1 pending
Bug #996293 [src:ruby-httparty] ruby-httparty: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed: ArgumentError:
Added tag(s) pending.
--
996293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996293
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #996293 in ruby-httparty 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 #997168 [src:scottfree] scottfree: FTBFS: ScottCurses.c:402:32: error:
format not a string literal and no format arguments [-Werror=format-security]
Added tag(s) pending.
--
997168: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997168
Control: tag -1 pending
Hello,
Bug #997168 in scottfree 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:
Control: tag -1 + wontfix
On Sat, 23 Oct 2021, Lucas Nussbaum wrote:
> Source: logidee-tools
> Version: 1.2.19
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Note that I requested removal of this package so I will not handle this
bug. See
Processing control commands:
> tag -1 + wontfix
Bug #997522 [src:logidee-tools] logidee-tools: FTBFS: make[2]: kpsepath: No
such file or directory
Added tag(s) wontfix.
--
997522: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997522
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Your message dated Tue, 26 Oct 2021 12:49:10 +
with message-id
and subject line Bug#997295: fixed in pacemaker 2.1.1-1
has caused the Debian Bug report #997295,
regarding pacemaker: FTBFS: crmadmin.c:340:1: error: function declaration isn’t
a prototype [-Werror=strict-prototypes]
to be
Processing commands for cont...@bugs.debian.org:
> # Fixed by version 1.6.0
> close 993042
Bug #993042 [src:nim] nim FTBFS on armhf when built on arm64 hardware
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
993042:
Your message dated Tue, 26 Oct 2021 12:35:31 +
with message-id
and subject line Bug#997052: fixed in libocxl 1.2.1-2
has caused the Debian Bug report #997052,
regarding libocxl: binary-all FTBFS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Tue, 26 Oct 2021 12:04:57 +
with message-id
and subject line Bug#984111: fixed in libgrokj2k 9.5.0-1
has caused the Debian Bug report #984111,
regarding libgrokj2k: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 26 Oct 2021 11:03:44 +
with message-id
and subject line Bug#997423: fixed in python-sphinxcontrib.plantuml 0.5-7
has caused the Debian Bug report #997423,
regarding python-sphinxcontrib.plantuml: FTBFS: error in sphinxcontrib-plantuml
setup command: use_2to3 is
Processing control commands:
> tag -1 pending
Bug #997423 [src:python-sphinxcontrib.plantuml] python-sphinxcontrib.plantuml:
FTBFS: error in sphinxcontrib-plantuml setup command: use_2to3 is invalid.
Added tag(s) pending.
--
997423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997423
1 - 100 of 151 matches
Mail list logo
