Control: reopen -1
Control: severity -1 important
Matthias Klose wrote:
> GCC 11 defaults to the GNU++17 standard. If your package installs
> header files in /usr/include, please don't work around C++17 issues by
> choosing a lower C++ standard for the package build, but fix these
> issues to
Processing control commands:
> reopen -1
Bug #984209 [src:libsynthesis] libsynthesis: ftbfs with GCC-11
Bug 984209 is not marked as done; doing nothing.
> severity -1 important
Bug #984209 [src:libsynthesis] libsynthesis: ftbfs with GCC-11
Severity set to 'important' from 'serious'
--
984209:
Control: reopen -1
Control: severity -1 important
Matthias Klose wrote:
> GCC 11 defaults to the GNU++17 standard. If your package installs
> header files in /usr/include, please don't work around C++17 issues by
> choosing a lower C++ standard for the package build, but fix these
> issues to
Processing control commands:
> reopen -1
Bug #983963 {Done: Jonas Smedegaard } [src:aiksaurus] aiksaurus:
ftbfs with GCC-11
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked
Your message dated Sun, 07 Nov 2021 03:18:27 +
with message-id
and subject line Bug#983963: fixed in aiksaurus 1.2.1+dev-0.12-7
has caused the Debian Bug report #983963,
regarding aiksaurus: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 07 Nov 2021 03:04:26 +
with message-id
and subject line Bug#998564: fixed in ncmpc 0.45-2
has caused the Debian Bug report #998564,
regarding ncmpc: FTBFS: ../meson.build:1:0: ERROR: Unknown options:
"artist_screen"
to be marked as done.
This means that you claim
Your message dated Sat, 6 Nov 2021 23:06:05 -0400
with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org>
and subject line Mass closing clojure FTBFS bugs
has caused the Debian Bug report #998535,
regarding shell-utils-clojure: FTBFS: Cannot access central
Your message dated Sat, 6 Nov 2021 23:06:05 -0400
with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org>
and subject line Mass closing clojure FTBFS bugs
has caused the Debian Bug report #998523,
regarding bidi-clojure: FTBFS: Cannot access central
(https://repo1.maven.org/maven2/) in
Your message dated Sat, 6 Nov 2021 23:06:05 -0400
with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org>
and subject line Mass closing clojure FTBFS bugs
has caused the Debian Bug report #997784,
regarding rbac-client-clojure: FTBFS: Cannot access central
Your message dated Sat, 6 Nov 2021 23:06:05 -0400
with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org>
and subject line Mass closing clojure FTBFS bugs
has caused the Debian Bug report #997753,
regarding puppetlabs-ring-middleware-clojure: FTBFS: Cannot access central
Your message dated Sat, 6 Nov 2021 23:06:05 -0400
with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org>
and subject line Mass closing clojure FTBFS bugs
has caused the Debian Bug report #997731,
regarding trapperkeeper-webserver-jetty9-clojure: FTBFS: Cannot access central
Your message dated Sat, 6 Nov 2021 23:06:05 -0400
with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org>
and subject line Mass closing clojure FTBFS bugs
has caused the Debian Bug report #997734,
regarding trapperkeeper-authorization-clojure: FTBFS: Cannot access central
Your message dated Sat, 6 Nov 2021 23:06:05 -0400
with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org>
and subject line Mass closing clojure FTBFS bugs
has caused the Debian Bug report #997711,
regarding puppetlabs-http-client-clojure: FTBFS: Cannot access central
Your message dated Sat, 6 Nov 2021 23:06:05 -0400
with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org>
and subject line Mass closing clojure FTBFS bugs
has caused the Debian Bug report #997705,
regarding trapperkeeper-metrics-clojure: FTBFS: Cannot access central
Your message dated Sat, 6 Nov 2021 23:06:05 -0400
with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org>
and subject line Mass closing clojure FTBFS bugs
has caused the Debian Bug report #997714,
regarding trapperkeeper-status-clojure: FTBFS: Cannot access central
Your message dated Sun, 07 Nov 2021 01:33:58 +
with message-id
and subject line Bug#998503: fixed in ruby-twitter-stream 0.1.16-4
has caused the Debian Bug report #998503,
regarding ruby-twitter-stream: FTBFS: ERROR: Test "ruby3.0" failed:
NoMethodError:
to be marked as done.
This means
Processing control commands:
> tag -1 moreinfo
Bug #998224 [hplip] hplip: HPLIP incorrectly links to obsolete or missing
libhpdiscovery.so
Added tag(s) moreinfo.
--
998224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 moreinfo
Hi Troy,
thanks for your bugreport. Unfortunately I have problems understanding
what is going on.
How can HPLIP link to a missing libhpdiscovery.so.
I assume you are building the package in a minimal chroot. How can there
be an old version of libhpdiscovery.so
Your message dated Sun, 07 Nov 2021 02:23:08 +0100
with message-id <6f10ab4efe3b65cb28db30c05baf0f7a7453a6fc.ca...@debian.org>
and subject line Bug report does not apply anymore
has caused the Debian Bug report #952616,
regarding ruby-concurrent-ext: FTBFS: ERROR: Test "ruby2.5" failed.
to be
Control: tag -1 pending
Hello,
Bug #998503 in ruby-twitter-stream 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 #998503 [src:ruby-twitter-stream] ruby-twitter-stream: FTBFS: ERROR: Test
"ruby3.0" failed: NoMethodError:
Added tag(s) pending.
--
998503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998503
Debian Bug Tracking System
Contact
Source: irrlicht
Version: 1.8.4+dfsg1-2
Severity: serious
Justification: Policy 5.6.3
irrlicht 1.8.4+dfsg1-2 introduced an invalid uploaders field, that is
missing a comma between Vincent Cheng and Julien Puydt.
$ apt-cache showsrc irrlicht | grep -E '^$|^Version|^Uploaders'
Version:
Processing commands for cont...@bugs.debian.org:
> reassign 997638 xutils-dev
Bug #997638 [imake] nas: FTBFS: ar: libdeps specified more than once
Warning: Unknown package 'imake'
Bug reassigned from package 'imake' to 'xutils-dev'.
Ignoring request to alter found versions of bug #997638 to the
I was advised a week ago that the app I maintain is not building in
unstable as the compiler (fpc) has been updated.
However, Testing still has the 'older' compiler and it builds fine with
that. How do I test my build against tools only available in sid ?
Background -
---
tomboy-ng is
Processing control commands:
> reassign -1 imake
Bug #997638 [src:nas] nas: FTBFS: ar: libdeps specified more than once
Bug reassigned from package 'src:nas' to 'imake'.
Warning: Unknown package 'imake'
Warning: Unknown package 'imake'
No longer marked as found in versions nas/1.9.4-7.
Warning:
Control: reassign -1 imake
Control: forcemerge -1 997628
Control: affects 997628 src:nas
So I've looked into this and I can see that this is not a bug in nas
directly, but a disagreement between imake and binutils. Assigning to
imake for now, in the same fashion as #997628
On Sat, Oct 23, 2021
Your message dated Sun, 07 Nov 2021 00:06:15 +
with message-id
and subject line Bug#983229: fixed in survex 1.4.0-1
has caused the Debian Bug report #983229,
regarding survex: FTBFS with PROJ 8.0.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sun, 07 Nov 2021 00:04:28 +
with message-id
and subject line Bug#997799: fixed in feynmf 1.08-13
has caused the Debian Bug report #997799,
regarding feynmf: Use disappeared /bin/tempfile in debian patch
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 06 Nov 2021 23:33:32 +
with message-id
and subject line Bug#998359: fixed in age 1.0.0-1
has caused the Debian Bug report #998359,
regarding age fails reading passphrase-protected key files
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 06 Nov 2021 23:33:45 +
with message-id
and subject line Bug#997230: fixed in dateutils 0.4.5-2
has caused the Debian Bug report #997230,
regarding dateutils: FTBFS: yuck.c:68:10: fatal error: sys/sysctl.h: No such
file or directory
to be marked as done.
This means
On Sat, 23 Oct 2021 22:42:41 +0200 Lucas Nussbaum wrote:
> […]
> > FAIL: tests.sh
> > ==
> >
> > ./tests.sh: 35: tempfile: not found
Looks like it's breaking because `tempfile` is gone, but that's an easy
fix I just committed upstream, see
Your message dated Sat, 06 Nov 2021 22:18:53 +
with message-id
and subject line Bug#998489: fixed in xastir 2.1.6-4
has caused the Debian Bug report #998489,
regarding xastir: FTBFS: configure.ac:35: error: AM_INIT_AUTOMAKE expanded
multiple times
to be marked as done.
This means that you
Your message dated Sat, 06 Nov 2021 21:48:48 +
with message-id
and subject line Bug#998561: fixed in sip4 4.19.25+dfsg-3
has caused the Debian Bug report #998561,
regarding krita: FTBFS: sip:
/usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax
error
to be marked as
Your message dated Sat, 06 Nov 2021 21:48:48 +
with message-id
and subject line Bug#998561: fixed in sip4 4.19.25+dfsg-3
has caused the Debian Bug report #998561,
regarding pyqwt3d: FTBFS: SIP failed to generate the C++ code.
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 06 Nov 2021 21:48:48 +
with message-id
and subject line Bug#998561: fixed in sip4 4.19.25+dfsg-3
has caused the Debian Bug report #998561,
regarding ros-rviz: FTBFS: call to 'sip' fails
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 06 Nov 2021 21:48:48 +
with message-id
and subject line Bug#998561: fixed in sip4 4.19.25+dfsg-3
has caused the Debian Bug report #998561,
regarding qgis: FTBFS: sip:
/usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax
error
to be marked as
Processing commands for cont...@bugs.debian.org:
> reassign 998561 sip-dev 4.19.25+dfsg-2
Bug #998561 [src:ros-rviz] ros-rviz: FTBFS: call to 'sip' fails
Bug reassigned from package 'src:ros-rviz' to 'sip-dev'.
No longer marked as found in versions ros-rviz/1.14.10+dfsg-2.
Ignoring request to
Processing control commands:
> tag -1 pending
Bug #998561 [src:ros-rviz] ros-rviz: FTBFS: call to 'sip' fails
Added tag(s) pending.
--
998561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #998561 in sip4 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 Sat, 6 Nov 2021 22:08:53 +0100
with message-id <302c150e-bb8a-f226-ba1c-312a14eae...@debian.org>
and subject line Re: osmnx: autopkgtest regression on armhf: iteration over a
0-d array
has caused the Debian Bug report #995021,
regarding osmnx: autopkgtest regression on armhf:
Dear Paul,
Thank you very much for noticing this and marking the bug as fixed.
Also, I really appreciate the great explanation of the significance of
such situations, I completely agree.
The delay originated from the Debian version freezing: version 0.15 of
Gnuastro came in that time slot
Source: pcs
Version: 0.10.8-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, pacema...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:pacemaker
Dear maintainer(s),
With a recent upload of pacemaker the
Processing control commands:
> affects -1 src:pacemaker
Bug #998707 [src:pcs] pcs: autopkgtest needs update for new version of
pacemaker: error and warning message text changed
Added indication that 998707 affects src:pacemaker
--
998707:
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: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of git the autopkgtest
Processing control commands:
> found -1 git/1:2.33.1-1
Bug #998706 [src:git, src:mercurial] git breaks mercurial autopkgtest: Failed
test-convert-git.t: output changed
Marked as found in versions git/1:2.33.1-1.
> found -1 mercurial/5.9.3-1
Bug #998706 [src:git, src:mercurial] git breaks
Source: lintian-brush
Version: 0.109
Severity: serious
Control: close -1 0.114
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
Processing control commands:
> close -1 0.114
Bug #998704 [src:lintian-brush] src:lintian-brush: fails to migrate to testing
for too long: blocked by breezy
Marked as fixed in versions lintian-brush/0.114.
Bug #998704 [src:lintian-brush] src:lintian-brush: fails to migrate to testing
for too
Processing control commands:
> close -1 0.15-1
Bug #998703 [src:gnuastro] src:gnuastro: fails to migrate to testing for too
long: ftbfs on mips64el
Marked as fixed in versions gnuastro/0.15-1.
Bug #998703 [src:gnuastro] src:gnuastro: fails to migrate to testing for too
long: ftbfs on mips64el
Source: gnuastro
Version: 0.14-1
Severity: serious
Control: close -1 0.15-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
Processing commands for cont...@bugs.debian.org:
> reassign 994257 src:django-ldapdb 1.5.1-2
Bug #994257 {Done: Carsten Schoenert }
[src:python-django, src:django-ldapdb] python-django breaks django-ldapdb
autopkgtest: 'Field' object has no attribute 'attname'
Bug reassigned from package
Processing commands for cont...@bugs.debian.org:
> reassign 994266 src:azure-cli 2.18.0-2
Bug #994266 {Done: Luca Boccassi } [src:pyjwt, src:azure-cli]
pyjwt breaks azure-cli autopkgtest: Could not deserialize key data. The data
may be in an incorrect format or it may be encrypted with an
Hi Ximin,
On 05-11-2021 21:43, Ximin Luo wrote:
> In other words, I don't see what value these bug reports are adding.
Most maintainers appreciate them. I'll try to remember to *not* file
them for rust packages anymore.
Please remember to resolve these issues in a timely fashion thou. Being
Your message dated Sat, 06 Nov 2021 19:32:22 +
with message-id
and subject line Bug#992973: fixed in plib 1.8.5-8+deb10u1
has caused the Debian Bug report #992973,
regarding plib: CVE-2021-38714
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 06 Nov 2021 19:17:31 +
with message-id
and subject line Bug#993622: fixed in open3d 0.9.0+ds-5+deb11u1
has caused the Debian Bug report #993622,
regarding python3-open3d: Missing dependency on python3-numpy
to be marked as done.
This means that you claim that the
Your message dated Sat, 06 Nov 2021 19:17:31 +
with message-id
and subject line Bug#992973: fixed in plib 1.8.5-8+deb11u1
has caused the Debian Bug report #992973,
regarding plib: CVE-2021-38714
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Sat, 06 Nov 2021 19:03:47 +
with message-id
and subject line Bug#983981: fixed in bamtools 2.5.1+dfsg-10
has caused the Debian Bug report #983981,
regarding bamtools: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> tags -1 + pending
Bug #983981 [src:bamtools] bamtools: ftbfs with GCC-11
Ignoring request to alter tags of bug #983981 to the same tags previously set
--
983981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983981
Debian Bug Tracking System
Contact
Your message dated Sat, 6 Nov 2021 19:15:57 +0100
with message-id
and subject line Re: firefox exits with SIGFPE on startup (no user interaction)
has caused the Debian Bug report #996922,
regarding firefox exits with SIGFPE on startup (no user interaction)
to be marked as done.
This means that
Your message dated Sat, 06 Nov 2021 18:03:53 +
with message-id
and subject line Bug#984260: fixed in nut 2.7.4-14
has caused the Debian Bug report #984260,
regarding nut: ftbfs with GCC-11
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
On Nov 06, dirdi wrote:
> As a first step it would be good to have a method - e.g. a crafted
> HTML page - to crash firefox instantly and reproducible. This would
> enable us to bisect the changes between 93.0-1 and 93.0-1+b1.
I do not think that this would be possible because after restarting
Package: firefox
Version: 94.0-1
Followup-For: Bug #998108
Problem is still here after dist-upgrade on sid. Firefox hangs and becomes
unresponsive. Had to downgrade to verison 93.0-1
Your message dated Sat, 06 Nov 2021 16:49:29 +
with message-id
and subject line Bug#997328: fixed in shaarli 0.12.0+dfsg-4
has caused the Debian Bug report #997328,
regarding shaarli: FTBFS: jinja2.exceptions.UndefinedError: list object has no
element 0
to be marked as done.
This means that
On Fri, Jan 10, 2020 at 07:28:01PM -0300, Emmanuel Arias wrote:
> Hi,
>
> The last upstream release version was on 2009 [1]. Seems to be not longer
> supported.
>
> And there is not python3 version.
>
> I believe that should be use the forks mentioned on:
>
I guess I just got lucky then. I can't think of anything that I've changed. For
the record, I still have not re-experienced this problem.
Adon
On Sat, Nov 06, 2021 at 03:43:09AM +0100, Christoph Anton Mitterer wrote:
> > I was also experiencing this problem and was monitoring this bug
> > report
Package: firefox
Version: 94.0-1
Followup-For: Bug #998108
X-Debbugs-Cc: deb...@dirdi.name
As a first step it would be good to have a method - e.g. a crafted HTML page -
to crash firefox instantly and reproducible. This would enable us to bisect the
changes between 93.0-1 and 93.0-1+b1.
Processing commands for cont...@bugs.debian.org:
> retitle 998413 gap-float: failed to build on i386 arch: object must be an
> MPFR, not a integer
Bug #998413 [src:gap-float] gap-float: autopkgtest regression: object must be
an MPFR, not a integer
Changed Bug title to 'gap-float: failed to
Control: tags -1 + upstream fixed-upstream patch
Control: forwarded -1
https://github.com/tatsuhiro-t/wslay/commit/43fda1207ea5977043630500e0c8e77b98b35320
Hi Anton, Lucas,
* Lucas Nussbaum [211106 12:55]:
> Source: wslay
> > File "/<>/doc/sphinx/conf.py", line 305, in setup
> >
Processing control commands:
> tags -1 + upstream fixed-upstream patch
Bug #997384 [src:wslay] wslay: FTBFS: AttributeError: 'Sphinx' object has no
attribute 'add_stylesheet'
Added tag(s) upstream, patch, and fixed-upstream.
> forwarded -1
>
Hi Bob, hi Jérôme,
On Fri, 05 Nov 2021, Jérôme Pouiller wrote:
> Is there a way to avoid this problem happen in the future?
Yes of course:
* take a VM
* for each package in the set of Plasma, that is about 150 or so, do
- upgrade the package and all necessary dependencies
- reboot the vm
-
Processing control commands:
> tag -1 pending
Bug #997607 {Done: Carsten Schoenert }
[src:python-fudge] python-fudge: FTBFS: error in fudge setup command: use_2to3
is invalid.
Added tag(s) pending.
--
997607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997607
Debian Bug Tracking System
Control: tag -1 pending
Hello,
Bug #997607 in python-fudge 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 Sat, 06 Nov 2021 12:35:02 +
with message-id
and subject line Bug#997607: fixed in python-fudge 1.1.1-1
has caused the Debian Bug report #997607,
regarding python-fudge: FTBFS: error in fudge setup command: use_2to3 is
invalid.
to be marked as done.
This means that you
Your message dated Sat, 06 Nov 2021 11:19:11 +
with message-id
and subject line Bug#998580: fixed in mako-notifier 1.6-2
has caused the Debian Bug report #998580,
regarding mako-notifier: FTBFS: ../meson.build:1:0: ERROR: Unknown options:
"apparmor"
to be marked as done.
This means that you
Your message dated Sat, 06 Nov 2021 11:03:53 +
with message-id
and subject line Bug#970870: fixed in postgresql-autodoc 1.41+20200921-1
has caused the Debian Bug report #970870,
regarding postgresql-autodoc: incompatible with PostgreSQL >= 12
to be marked as done.
This means that you claim
Your message dated Sat, 06 Nov 2021 09:49:31 +
with message-id
and subject line Bug#997206: fixed in irrlicht 1.8.4+dfsg1-2
has caused the Debian Bug report #997206,
regarding irrlicht: FTBFS: COSOperator.cpp:17:10: fatal error: sys/sysctl.h: No
such file or directory
to be marked as done.
Package: firefox-esr
Version: 91.3.0esr-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after upgrading to esr91 I'm experiencing the same symptoms as
described in bug #998108 for firefox.
Regards,
GLG
-- Package-specific info:
-- Extensions information
Name:
Control: tag -1 pending
Hello,
Bug #997206 in irrlicht 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 #997206 [src:irrlicht] irrlicht: FTBFS: COSOperator.cpp:17:10: fatal error:
sys/sysctl.h: No such file or directory
Added tag(s) pending.
--
997206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997206
Debian Bug Tracking System
Contact
78 matches
Mail list logo
