Hi Adrian,
> I've prepared an NMU for grfcodec (versioned as 6.0.6-5.1) and uploaded
> it to DELAYED/15. Please feel free to tell me if I should cancel it, or
> to use the changes for a maintainer upload instead.
Thanks for your interest and picking this up!
However, I had actually *just*
Hi,
On 2021-11-23 20:20, Adrian Bunk wrote:
> /usr/lib/python3/dist-packages/phonopy/qha/eos.py:137: SystemExit
> - Captured stdout call
> -
> You need to install python-scipy.
> === short test summary info
>
Source: frama-c
Version: 20201209+titanium-4.1
Severity: serious
Tags: ftbfs
Dear Maintainer,
Frama-c FTBFS with Why3 1.4.0:
> [...]
> File "src/plugins/wp/Why3Provers.ml", line 31, characters 19-61:
> 31 | let config = Why3.Whyconf.load_default_config_if_needed config in
>
Hi Scott
> > The tests look easy enough to fix, so it's worth trying to do that. (and
> > it's in the Debian group on salsa to make that easy :)
I've looked at them and fixed most of the tests locally without issues. I guess
I should push that somewhere so that it is visible. I'll start a draft
On Tue, 16 Nov 2021 01:30:55 +1100 Stuart Prescott wrote:
> Hi Scott & Tobias
>
> On Monday, 15 November 2021 21:13:09 AEDT Dr. Tobias Quathamer wrote:
> > On Sun, 14 Nov 2021 20:30:06 -0500 Scott Kitterman
> >
> > wrote:
> > > I looked at this a bit today and it looks like the test failures
Your message dated Wed, 24 Nov 2021 05:18:31 +
with message-id
and subject line Bug#996239: fixed in ruby-hashie 3.5.5-3
has caused the Debian Bug report #996239,
regarding ruby-hashie: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError:
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> tags 996319 + unreproducible moreinfo
Bug #996319 [src:ruby-mini-magick] ruby-mini-magick: FTBFS: ERROR: Test
"ruby2.7" failed: Failure/Error:
expect(described_class.new(output_path.to_s)).to be_valid
Added tag(s) moreinfo and
Control: tag -1 pending
Hello,
Bug #996239 in ruby-hashie 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 #996239 [src:ruby-hashie] ruby-hashie: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed: ArgumentError:
Added tag(s) pending.
--
996239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996239
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> tags 997933 + patch
Bug #997933 [offlineimap3] offlineimap3: 'int' object is not subscriptable when
connecting to outlook.office365.com
Added tag(s) patch.
> forwarded 997933 https://github.com/OfflineIMAP/offlineimap3/pull/98
>
Your message dated Wed, 24 Nov 2021 03:19:34 +
with message-id
and subject line Bug#996370: fixed in ruby-rgen 0.9.0-1
has caused the Debian Bug report #996370,
regarding ruby-rgen: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
to be marked as done.
This means that you claim that the
Control: tag -1 pending
Hello,
Bug #996370 in ruby-rgen 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 #996370 [src:ruby-rgen] ruby-rgen: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed.
Added tag(s) pending.
--
996370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> tags 996383 + fixed-upstream
Bug #996383 [src:ruby-semantic-puppet] ruby-semantic-puppet: FTBFS with
ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError:
Added tag(s) fixed-upstream.
> forwarded 996383
>
Processing control commands:
> tags 998471 + patch
Bug #998471 [src:gpgme1.0] gpgme1.0: b-d on python3-all-dev, but not built for
all supported Python3 versions
Added tag(s) patch.
> tags 998471 + pending
Bug #998471 [src:gpgme1.0] gpgme1.0: b-d on python3-all-dev, but not built for
all
Control: tags 998471 + patch
Control: tags 998471 + pending
Dear maintainer,
Turns out the bug is actually that autoconf has a hardcoded list of
Python versions and 3.10 isn't in the list. When it is in the list,
there is also a bug somewhere that treats it as python 3.1.
But... Let's just
Processing commands for cont...@bugs.debian.org:
> tags 997635 + pending
Bug #997635 [src:flask-openid] flask-openid: FTBFS: error in Flask-OpenID setup
command: use_2to3 is invalid.
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997635:
Processing commands for cont...@bugs.debian.org:
> forwarded 996370 https://github.com/mthiede/rgen/issues/35
Bug #996370 [src:ruby-rgen] ruby-rgen: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed.
Set Bug forwarded-to-address to 'https://github.com/mthiede/rgen/issues/35'.
> thanks
Stopping
Control: tag 1000421 pending
Hi!
Bug #1000421 in package dpkg reported by you has been fixed in
the dpkg/dpkg.git Git repository. You can see the changelog below, and
you can check the diff of the fix at:
https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=ecbd9f1b1
---
Dpkg::Shlibs::Objdump:
Processing control commands:
> tag 1000421 pending
Bug #1000421 [dpkg-dev] dpkg-shlibdeps: Wrong minimum version requirement on
libc6
Added tag(s) pending.
--
1000421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> tags 1000419 + ftbfs
Bug #1000419 [src:pymatgen] pymatgen: FTBFS - Test failure:
BSPlotterProjectedTest.test_methods
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000419:
Processing commands for cont...@bugs.debian.org:
> tags 1000428 + ftbfs
Bug #1000428 [src:gammapy] gammapy: FTBFS with matplotlib 3.5
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000428:
Your message dated Wed, 24 Nov 2021 01:20:07 +
with message-id
and subject line Bug#996381: fixed in ruby-sanitize 5.2.3-1
has caused the Debian Bug report #996381,
regarding ruby-sanitize: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError: wrong number of arguments (given 4,
Your message dated Wed, 24 Nov 2021 01:19:49 +
with message-id
and subject line Bug#995040: fixed in iverilog 11.0-1.1
has caused the Debian Bug report #995040,
regarding iverilog FTBFS: configure: error: C preprocessor "/lib/cpp" fails
sanity check
to be marked as done.
This means that you
Your message dated Wed, 24 Nov 2021 01:20:00 +
with message-id
and subject line Bug#1000488: fixed in ruby-nokogumbo 2.0.2-3
has caused the Debian Bug report #1000488,
regarding nokogumbo/html5.rb:74: warning: Using the last argument as keyword
parameters is deprecated
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> tags 1000360 + ftbfs
Bug #1000360 [src:segyio] segyio: FTBFS with Python 3.10
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000360
Processing control commands:
> tag -1 pending
Bug #996381 [src:ruby-sanitize] ruby-sanitize: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected
1..3)
Added tag(s) pending.
--
996381:
Control: tag -1 pending
Hello,
Bug #996381 in ruby-sanitize 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 #1000488 [ruby-nokogumbo] nokogumbo/html5.rb:74: warning: Using the last
argument as keyword parameters is deprecated
Added tag(s) pending.
--
1000488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000488
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #1000488 in ruby-nokogumbo 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 commands for cont...@bugs.debian.org:
> tags 1000423 + ftbfs
Bug #1000423 [src:python-biom-format] python-biom-format: FTBFS with Python
3.10 - Test failures
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000423:
Processing commands for cont...@bugs.debian.org:
> clone 996381 -1
Bug #996381 [src:ruby-sanitize] ruby-sanitize: FTBFS with ruby3.0: ERROR: Test
"ruby3.0" failed: ArgumentError: wrong number of arguments (given 4, expected
1..3)
Bug 996381 cloned as bug 1000488
> reassign -1 ruby-nokogumbo
Your message dated Tue, 23 Nov 2021 23:33:35 +
with message-id
and subject line Bug#996524: fixed in ruby-whitequark-parser 3.0.2.0-1
has caused the Debian Bug report #996524,
regarding ruby-whitequark-parser: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed.
to be marked as done.
This
Your message dated Tue, 23 Nov 2021 23:21:43 +
with message-id
and subject line Bug#996526: fixed in rubygems 3.2.27-3
has caused the Debian Bug report #996526,
regarding rubygems: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.
to be marked as done.
This means that you claim that the
Control: tag -1 pending
Hello,
Bug #996524 in ruby-whitequark-parser 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 #996524 [src:ruby-whitequark-parser] ruby-whitequark-parser: FTBFS with
ruby3.0: ERROR: Test "ruby3.0" failed.
Added tag(s) pending.
--
996524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996524
Debian Bug Tracking System
Contact
Processing control commands:
> tag -1 pending
Bug #996526 [src:rubygems] rubygems: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed.
Added tag(s) pending.
--
996526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #996526 in rubygems 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, 23 Nov 2021 22:37:30 +
with message-id
and subject line Bug#1000471: fixed in glewlwyd 2.6.0-1
has caused the Debian Bug report #1000471,
regarding glewlwyd FTBFS can't find functions.
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> reopen 997311
Bug #997311 {Done: Daniel Leidert }
[src:ruby-rufus-scheduler] ruby-rufus-scheduler: FTBFS: ERROR: Test "ruby2.7"
failed: Failure/Error: expect(job.last_work_time).to be < 0.099
'reopen' may be inappropriate when a bug has been
Hello,
On Wed 24 Nov 2021 at 02:21AM +0530, Nilesh Patra wrote:
> Hi Sean, Richard,
>
> On Wed, 27 Oct 2021 12:20:04 -0700 Sean Whitton
> wrote:
>> Source: git-annex
>> Version: 8.20210223-2
>> Severity: serious
>> git-annex recently began to FTBFS on 32-bit ARM architectures, and I am
>> not
Hello,
Le 2021-11-23 à 15 h 20, peter green a écrit :
Package: glewlwyd
Version: 2.5.2-3
Severity: serious
Tags: ftbfs
Unfortunately it seems that even after the cross-fetch fix, glewlwyd
still FTBFS as a
result of changes in iddawc/rhonabwy.
Thanks, that's because the dependencies were
Processing control commands:
> tags -1 + pending
Bug #1000476 [src:lintian] lintian: autopkgtest regression:
autopkgtest_tmp/build-and-evaluate-test-packages/eval/checks/binaries/corrupted/legacy-debug/generic.t
Added tag(s) pending.
--
1000476:
Control: tags -1 + pending
Hi,
Thanks for this message.
On Tue, Nov 23, 2021 at 12:48 PM Paul Gevers wrote:
>
> ../../autopkgtest_tmp/build-and-evaluate-test-packages/eval/odd-inputs/strings-elf-detection/generic.t
That test was already dropped from Lintian. [1]
>
i'm not, i'm using intel drivers
Le sam. 20 nov. 2021, 18 h 43, Gunnar Hjalmarsson a
écrit :
> Are you possibly using a NVIDIA driver? Asking because of this:
>
> https://github.com/NVIDIA/egl-wayland/issues/27#issuecomment-951725683
>
> --
> Cheers,
> Gunnar Hjalmarsson
>
Hi Sean, Richard,
On Wed, 27 Oct 2021 12:20:04 -0700 Sean Whitton
wrote:
> Source: git-annex
> Version: 8.20210223-2
> Severity: serious
> git-annex recently began to FTBFS on 32-bit ARM architectures, and I am
> not really in a position atm to dig deeply into the problem.
> [.. log ..]
This
Source: lintian
Version: 2.113.0
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of lintian the autopkgtest of lintian fails in
testing when that autopkgtest is run with the binary
Source: minimac4
Version: 1.0.2-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of minimac4 the autopkgtest of minimac4 fails in
testing when that autopkgtest is run with the binary
On Tue, Nov 23, 2021 at 08:45:47PM +0100, Hannes von Haugwitz wrote:
Is there any progress with this bug?
Mutt 2.1.3 included the corrected sort commit referenced in my last
email. So, for unstable/testing it would be nice to get 2.1.3 uploaded.
For stable/oldstable I guess it rests in the
Processing control commands:
> reassign -1 src:python-mpv 0.5.2-1
Bug #1000255 [src:mpv] mpv: autopkgtest failures
Bug reassigned from package 'src:mpv' to 'src:python-mpv'.
No longer marked as found in versions mpv/0.34.0-1.
Ignoring request to alter fixed versions of bug #1000255 to the same
Control: reassign -1 src:python-mpv 0.5.2-1
Control: forwarded -1 https://github.com/jaseg/python-mpv/issues/187
On 2021-11-21 23:21:24, Sebastian Ramacher wrote:
> Control: tags -1 help
>
> On 2021-11-20 09:34:37 +0100, Gianfranco Costamagna wrote:
> > Source: mpv
> > Version: 0.34.0-1
> >
Package: glewlwyd
Version: 2.5.2-3
Severity: serious
Tags: ftbfs
Unfortunately it seems that even after the cross-fetch fix, glewlwyd still
FTBFS as a
result of changes in iddawc/rhonabwy.
/usr/bin/cc -D_GNU_SOURCE -Dschememodoauth2_EXPORTS -I/include -g -O2
-ffile-prefix-map=/<>=.
Hello,
Is there any progress with this bug?
Best regards
Hannes
Your message dated Tue, 23 Nov 2021 19:34:35 +
with message-id
and subject line Bug#997311: fixed in ruby-rufus-scheduler 3.8.0-1
has caused the Debian Bug report #997311,
regarding ruby-rufus-scheduler: FTBFS: ERROR: Test "ruby2.7" failed:
Failure/Error: expect(job.last_work_time).to be <
Your message dated Tue, 23 Nov 2021 14:24:53 -0500
with message-id
and subject line Re: Bug#997467: python-certbot-dns-rfc2136: FTBFS:
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
has caused the Debian Bug report #997467,
regarding
Processing control commands:
> tags 984166 + patch
Bug #984166 [src:hashdeep] hashdeep: ftbfs with GCC-11
Added tag(s) patch.
> tags 984166 + pending
Bug #984166 [src:hashdeep] hashdeep: ftbfs with GCC-11
Added tag(s) pending.
--
984166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984166
Control: tags 984166 + patch
Control: tags 984166 + pending
Dear maintainer,
I've prepared an NMU for hashdeep (versioned as 4.4-7.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru hashdeep-4.4/debian/changelog hashdeep-4.4/debian/changelog
Processing commands for cont...@bugs.debian.org:
> reassign 1000388 src:parlatype 3.0-1
Bug #1000388 [parlatype] FTBFS on s390x due to whitespace damage
Bug reassigned from package 'parlatype' to 'src:parlatype'.
No longer marked as found in versions parlatype/3.0-1.
Ignoring request to alter
Package: rpm
Version: 4.17.0+dfsg1-1
Severity: serious
The new version of rpm added an autopkgtest, but unfortunately it's failing on
armhf
and blocking the migration to testing (and hence blocking the fixes for two
other rc bugs).
autopkgtest [04:40:50]: test rpmbuild: env
Source: phonopy
Version: 2.12.0-1
Severity: serious
https://ci.debian.net/data/autopkgtest/testing/amd64/p/phonopy/16901578/log.gz
...
=== FAILURES ===
_ test_QHA_Si __
Processing commands for cont...@bugs.debian.org:
> close 998706 6.0~rc0-1
Bug #998706 [mercurial] git breaks mercurial autopkgtest: Failed
test-convert-git.t: output changed
Marked as fixed in versions mercurial/6.0~rc0-1.
Bug #998706 [mercurial] git breaks mercurial autopkgtest: Failed
Processing control commands:
> reassign -1 mercurial 5.9.3-1
Bug #998706 [src:git, src:mercurial] git breaks mercurial autopkgtest: Failed
test-convert-git.t: output changed
Bug reassigned from package 'src:git, src:mercurial' to 'mercurial'.
No longer marked as found in versions
Control: reassign -1 mercurial 5.9.3-1
Control: close -1 mercurial/6.0~rc0-1
On Sat, Nov 06, 2021 at 09:57:34PM +0100, Paul Gevers wrote:
> Source: git, mercurial
> Control: found -1 git/1:2.33.1-1
> Control: found -1 mercurial/5.9.3-1
> Severity: serious
> Tags: sid bookworm
> X-Debbugs-CC:
Processing control commands:
> tags 984158 + patch
Bug #984158 [src:grfcodec] grfcodec: ftbfs with GCC-11
Added tag(s) patch.
> tags 984158 + pending
Bug #984158 [src:grfcodec] grfcodec: ftbfs with GCC-11
Added tag(s) pending.
--
984158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984158
Control: tags 984158 + patch
Control: tags 984158 + pending
Dear maintainer,
I've prepared an NMU for grfcodec (versioned as 6.0.6-5.1) and uploaded
it to DELAYED/15. Please feel free to tell me if I should cancel it, or
to use the changes for a maintainer upload instead.
cu
Adrian
diff -Nru
Processing commands for cont...@bugs.debian.org:
> block 984145 with 998143
Bug #984145 {Done: Andreas Tille } [src:gatb-core] gatb-core:
ftbfs with GCC-11
984145 was not blocked by any bugs.
984145 was not blocking any bugs.
Added blocking bug(s) of 984145: 998143
> thanks
Stopping processing
Control: tags 984382 + patch
Control: tags 984382 + pending
Dear maintainer,
I've prepared an NMU for vdr (versioned as 2.4.1-4.2) and uploaded
it to DELAYED/7. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru vdr-2.4.1/debian/changelog vdr-2.4.1/debian/changelog
---
Processing control commands:
> tags 984382 + patch
Bug #984382 [src:vdr] vdr: ftbfs with GCC-11
Added tag(s) patch.
> tags 984382 + pending
Bug #984382 [src:vdr] vdr: ftbfs with GCC-11
Added tag(s) pending.
--
984382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984382
Debian Bug Tracking
Processing control commands:
> severity -1 serious
Bug #1000439 [fcitx5] fcitx5: icons of individual input methods are not being
displayed
Severity set to 'serious' from 'normal'
--
1000439: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000439
Debian Bug Tracking System
Contact
Your message dated Tue, 23 Nov 2021 16:48:49 +
with message-id
and subject line Bug#995015: fixed in dnsdiag 1.7.0-1.1
has caused the Debian Bug report #995015,
regarding dnsdiag: Error when running: DeprecationWarning
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 23 Nov 2021 16:48:49 +
with message-id
and subject line Bug#995015: fixed in dnsdiag 1.7.0-1.1
has caused the Debian Bug report #995015,
regarding dnsdiag: Error when running: DeprecationWarning
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> forwarded 997488 https://github.com/qiime2/q2cli/issues/259
Bug #997488 [src:q2cli] q2cli: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
Ignoring request to change the
Dear Adrian,
Thank you for the upload, this is appreciated as I don't have much time atm.
Ana
On 23/11/2021 16:19, Adrian Bunk wrote:
Control: tags 995015 + patch
Control: tags 995015 + pending
Dear maintainer,
I've prepared an NMU for dnsdiag (versioned as 1.7.0-1.1) and uploaded
it to
I _think_ this would expected with 22.3.0-1 and python 3.10, since that
package was built only for python 3.9.
Can you reproduce this with 22.3.0-1+b1 now the python 3.10 binNMUs have
(mostly) happened? I can certainly import `zmq` in python3.10 without
immediate errors.
Processing control commands:
> tags 995015 + patch
Bug #995015 [dnsdiag] dnsdiag: Error when running: DeprecationWarning
Bug #995016 [dnsdiag] dnsdiag: Error when running: DeprecationWarning
Added tag(s) patch.
Added tag(s) patch.
> tags 995015 + pending
Bug #995015 [dnsdiag] dnsdiag: Error when
Control: tags 995015 + patch
Control: tags 995015 + pending
Dear maintainer,
I've prepared an NMU for dnsdiag (versioned as 1.7.0-1.1) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru dnsdiag-1.7.0/debian/changelog
Source: tf
Version: 1:4.0s1-21
Severity: serious
Justification: policy 4.6
When building tf fails, the failure is not propagated and debian/rules
proceeds with dh_auto_install after a failed dh_auto_build. Such
behaviour violates policy section 4.6 and thus this issue deserves
rc-severity.
At
Processing commands for cont...@bugs.debian.org:
> notfixed 1000427 2.1.1-1
Bug #1000427 {Done: Stefano Rivera } [src:pyregion]
pyregion: FTBFS with setuptools >= 58
No longer marked as fixed in versions 2.1.1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Tue, 23 Nov 2021 15:49:04 +
with message-id
and subject line Bug#984270: fixed in onednn 2.2.2+ds-3
has caused the Debian Bug report #984270,
regarding onednn: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> notfound 1000427 pyregion/2.1.1-1
Bug #1000427 {Done: Stefano Rivera } [src:pyregion]
pyregion: FTBFS with setuptools >= 58
No longer marked as found in versions pyregion/2.1.1-1.
> thanks
Stopping processing here.
Please contact me if you need
Your message dated Tue, 23 Nov 2021 11:37:42 -0400
with message-id <20211123153742.orlfycl7pid2y...@haydn.kardiogramm.net>
and subject line Re: Bug#1000427: pyregion: FTBFS with setuptools >= 58
has caused the Debian Bug report #1000427,
regarding pyregion: FTBFS with setuptools >= 58
to be marked
On Sat 23 Oct 2021, Lucas Nussbaum wrote:
> Source: pixmap
> Version: 2.6pl4-20
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20211023 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to
Package: virtualbox
Version: 6.1.28-dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Trying to upgrade virtualbox to Version: 6.1.28-dfsg-1 aptitude was not
able to resolve dependencies. I uninstalled the previous version and
then tryed to install again, but foud
Processing commands for cont...@bugs.debian.org:
> forwarded 1000419 https://github.com/materialsproject/pymatgen/issues/2305
Bug #1000419 [src:pymatgen] pymatgen: FTBFS - Test failure:
BSPlotterProjectedTest.test_methods
Set Bug forwarded-to-address to
Processing control commands:
> tag -1 patch
Bug #997414 [src:debomatic] debomatic: FTBFS: '! LaTeX Error: File
`tgtermes.sty' not found.'
Added tag(s) patch.
--
997414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Package: debomatic
Followup-For: Bug #997414
Control: tag -1 patch
Hello.
This issue is fixed by tex-gyre in Build-Depends.
Your message dated Tue, 23 Nov 2021 13:03:40 +
with message-id
and subject line Bug#997718: fixed in node-i18next-http-backend 1.3.1+dfsg-3
has caused the Debian Bug report #997718,
regarding glewlwyd: FTBFS: Module not found: Error: Can't resolve 'cross-fetch'
in
Processing control commands:
> tag -1 pending
Bug #1000210 [devscripts] [regression] uscan die: filenamemangle failed
Bug #999543 [devscripts] devscripts: uscan crash with cmus package
Added tag(s) pending.
Added tag(s) pending.
--
1000210:
Control: tag -1 pending
Hello,
Bug #1000210 in devscripts 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, 23 Nov 2021 12:03:45 +
with message-id
and subject line Bug#999534: fixed in python-bayespy 0.5.22-1
has caused the Debian Bug report #999534,
regarding python-bayespy: FTBFS with matplotlib 3.5 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i
Processing commands for cont...@bugs.debian.org:
> tags 1000417 + pending
Bug #1000417 [src:devscripts] devscripts: autopkgtest regression: zstd: not
found
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000417:
The module is still failing to build on my machine.
I believe the problem is that ddcci_device_remove() returns in two
different places. The new patch wraps the return at the end of the
function in an #if, but does not fix the mid-function `return -EINVAL;`.
(In case it is useful: there is a
Your message dated Tue, 23 Nov 2021 11:33:39 +
with message-id
and subject line Bug#1000350: fixed in macaulay2 1.19+ds-2
has caused the Debian Bug report #1000350,
regarding macaulay2: FTBFS on s390x: i49 : saturate(sing2, sub(irrelTot, ring
sing2)) -- SIGSEGV
to be marked as done.
This
Your message dated Tue, 23 Nov 2021 11:33:39 +
with message-id
and subject line Bug#1000348: fixed in macaulay2 1.19+ds-2
has caused the Debian Bug report #1000348,
regarding macaulay2: FTBFS on mips64el: assert(timer((m, n) -> apply(m, i ->
M(offset,n,1)), (1,294)) < 1.5) -- timing test
Your message dated Tue, 23 Nov 2021 10:34:30 +
with message-id
and subject line Bug#984403: fixed in warzone2100 4.2.1-2
has caused the Debian Bug report #984403,
regarding warzone2100: 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, 23 Nov 2021 10:34:11 +
with message-id
and subject line Bug#999537: fixed in python-matplotlib-venn 0.11.6-2
has caused the Debian Bug report #999537,
regarding python-matplotlib-venn: FTBFS with matplotlib 3.5 (in experimental):
dh_auto_test: error: pybuild --test
Source: nomad
Version: 0.12.10+dfsg1-3
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: z...@debian.org
Rebuilding nomad in bullseye chroot, it FTBFS with:
=== RUN TestConfig_wrapTLS_OK
config_test.go:560: wrapTLS err: x509: certificate has expired or is not
yet valid:
Processing commands for cont...@bugs.debian.org:
> fixed 997776 1.1.1+2021-11-10-1
Bug #997776 {Done: Christoph Berg } [src:pgsphere] pgsphere:
FTBFS: Error: debian/control needs updating from debian/control.in. Run
'pg_buildext updatecontrol'.
Marked as fixed in versions
Processing control commands:
> block -1 by 1000422
Bug #999525 [src:bmtk] bmtk: FTBFS with numpy 1.21 (in experimental):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
999525 was not blocked by any bugs.
999525 was not blocking any bugs.
Added
Processing control commands:
> block -1 by 1000422
Bug #1000423 [src:python-biom-format] python-biom-format: FTBFS with Python
3.10 - Test failures
1000423 was blocked by: 1000422
1000423 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #1000423 to the same blocks
1 - 100 of 102 matches
Mail list logo
