Processing control commands:
> tags -1 help
Bug #937657 [src:python-colormap] python-colormap: Python2 removal in
sid/bullseye
Added tag(s) help.
--
937657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 help
Hi,
I have dropped the Python2 package in Git[1] and tried to build which
ended up in:
...
I: pybuild base:217: cd
/build/python-colormap-1.0.2/.pybuild/cpython3_3.8_colormap/build; python3.8 -m
nose -v test
nose.config: INFO: Ignoring files matching ['^\\.', '^_',
Processing control commands:
> severity -1 serious
Bug #941920 [src:jellyfish] jellyfish: FTBFS on ppc64el
Severity set to 'serious' from 'important'
> retitle -1 FTBFS intermittently on buildds ppc64el and amd64
Bug #941920 [src:jellyfish] jellyfish: FTBFS on ppc64el
Changed Bug title to 'FTBFS
Processing commands for cont...@bugs.debian.org:
> severity 931697 serious
Bug #931697 {Done: Jongmin Kim }
[src:golang-gopkg-libgit2-git2go.v28] golang-gopkg-libgit2-git2go.v27: libgit2
0.28 transition
Severity set to 'serious' from 'important'
> severity 931695 serious
Bug #931695
Your message dated Sat, 16 Nov 2019 11:48:09 +0530
with message-id <4f8751c9-379a-c458-72c8-138fe8b25...@onenetbeyond.org>
and subject line closing old bug
has caused the Debian Bug report #902726,
regarding 2018/06/25 security release
to be marked as done.
This means that you claim that the
Your message dated Sat, 16 Nov 2019 02:48:23 +
with message-id
and subject line Bug#943965: fixed in gnuradio 3.8.0.0-6
has caused the Debian Bug report #943965,
regarding gnuradio/block.h depends on gmpxx.h, but no dep on libgmp-dev
to be marked as done.
This means that you claim that the
Package: thonny
Version: 0.14.1-1
Severity: serious
Tags: bullseye, sid, patch
thonny depends and build-depends on the pylint3 binary package which is no
longer built by the pylint source package. The python 3 pylint functionality is
now in the pylint binary package.
These
Package: salt-pylint
Version: 0.14.1-1
Severity: serious
Tags: bullseye, sid, patch
python3-saltpylint depends on and the salt-pylint source package build-depends
on the pylint3 binary package which is no longer built by the pylint source
package. The python 3 pylint functionality is now in
Package: pylint-common
Version: 0.2.5-2
Severity: serious
Tags: bullseye, sid, patch
python3-plint-common depends on and the pylint-common source package
build-depends on the pylint3 binary package which is no longer built by the
pylint source package. The python 3 pylint functionlity is now
Package: pylint-celery
Version: 0.3-4
Severity: serious
Tags: bullseye, sid, patch
python3-plint-celery depends on and the pylint-celery source package
build-depends on the pylint3 binary package which is no longer built by the
pylint source package. The python 3 pylint functionlity is now in
Source: popper.js
Version: 1.14.6+ds2-2
Severity: serious
The /usr/share/javascript/popper.js proper directory became a symlink in
the latest version, but dpkg does not support it, and it wasn’t handled
in maintainer scripts (nor documented in d/changelog).
Upgrading from 1.14.6+ds2-2 to
Your message dated Fri, 15 Nov 2019 23:36:39 +
with message-id
and subject line Bug#922599: fixed in uprightdiff 1.3.0-3
has caused the Debian Bug report #922599,
regarding FTBFS against opencv 4.0.1 (exp)
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 15 Nov 2019 22:50:42 +
with message-id
and subject line Bug#944127: fixed in libcgns 3.4.0-1~exp2
has caused the Debian Bug report #944127,
regarding gfortran-9 causes libcgns FTBFS on ppc64el
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 15 Nov 2019 23:07:08 +0100
with message-id <20191115220708.zfaydfhdwtix3...@fatal.se>
and subject line nm 1.20.6 (with iwd 1.0 compatibility) now in both testing and
unstable
has caused the Debian Bug report #944069,
regarding block iwd 1.0 testing migration
to be marked
Control: forwarded -1 https://bugs.freepascal.org/view.php?id=36318
I've tried to debug this issue but it seems more difficult than I thought.
It looks like some class instance is freed twice which results in access
violation on the second attempt to free it.
Modified code results in the
Processing control commands:
> forwarded -1 https://bugs.freepascal.org/view.php?id=36318
Bug #943600 [src:lazarus] lazarus autopkgtest intermittedly fails due to
EAccessViolation: Access violation
Set Bug forwarded-to-address to 'https://bugs.freepascal.org/view.php?id=36318'.
--
943600:
Your message dated Fri, 15 Nov 2019 21:50:52 +
with message-id
and subject line Bug#942717: fixed in libpreludedb 5.1.0-2
has caused the Debian Bug report #942717,
regarding libpreludedb ftbfs with more than one supported python3 version
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> close 943534 0.13.0+ds-2
Bug #943534 [python3-lesscpy] python3-lesscpy: fails to install:
update-alternatives: error: alternative path /usr/bin/python3-lesscpy doesn't
exist
There is no source info for the package 'python3-lesscpy' at version
Your message dated Fri, 15 Nov 2019 20:46:33 +
with message-id
and subject line Bug#942666: fixed in pycairo 1.16.2-2
has caused the Debian Bug report #942666,
regarding fix ftbfs with python3.8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 15 Nov 2019 20:43:11 +
with message-id
and subject line Bug#925748: fixed in libkolabxml 1.1.6-5
has caused the Debian Bug report #925748,
regarding libkolabxml: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Hi both Moritz!
On Fri, Oct 18, 2019 at 09:33:47AM +0200, Moritz Mühlenhoff wrote:
> On Wed, Oct 16, 2019 at 11:19:36AM +0200, Moritz Schlarb wrote:
> > Hi everyone,
> >
> > I have prepared a backport of the patches for the version packaged in
> > Buster:
> >
Control: tag -1 pending
Hello,
Bug #943428 in pygobject 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 #943428 [src:pygobject] autopkg test calls python instead of python2
Added tag(s) pending.
--
943428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 15 Nov 2019 19:06:01 +
with message-id
and subject line Bug#937159: fixed in nosexcover 1.0.11-1.2
has caused the Debian Bug report #937159,
regarding nosexcover: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 15 Nov 2019 19:06:01 +
with message-id
and subject line Bug#906083: fixed in nosexcover 1.0.11-1.2
has caused the Debian Bug report #906083,
regarding python3-nosexcover shouldn't depend on python-nose and python-coverage
to be marked as done.
This means that you
Your message dated Fri, 15 Nov 2019 23:51:48 +0530
with message-id <64a5cfa5-48a0-619b-9591-a996b0a7f...@onenetbeyond.org>
and subject line closing
has caused the Debian Bug report #944596,
regarding gitlab: Upgrading to 12.2.9-1 fails
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #942666 [src:pycairo] fix ftbfs with python3.8
Added tag(s) pending.
--
942666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #942666 in pycairo 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:
Hi Bernhard,
On Fri, Nov 15, 2019 at 04:53:28PM +0100, Bernhard Übelacker wrote:
> Dear Maintainer,
> I tried to find out what happens and I think it is
> related to the changes from #928467.
> Because of these the configure script searches now
> for libdb-5.3.a in directory
Processing commands for cont...@bugs.debian.org:
> severity 942666 serious
Bug #942666 [src:pycairo] fix ftbfs with python3.8
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942666:
Dear Maintainer,
I tried to find out what happens and I think it is
related to the changes from #928467.
Because of these the configure script searches now
for libdb-5.3.a in directory /usr/lib/i686-linux-gnu
(in configure "$dir/lib/${host_cpu}-${host_os}").
Unfortunately that library lives in
Control: fixed -1 12.2.9-1+fto10+2
On Fri, 15 Nov 2019 12:59:37 +0100 David L wrote:
> Package: gitlab
> Version: 12.2.9-1+fto10+1
> Followup-For: Bug #944596
>
> More info about the bug:
> - Deleting file active_record_mysql_timestamp.rb, fails on
> active_record_mysql_timestamp.rb,
Processing control commands:
> fixed -1 12.2.9-1+fto10+2
Bug #944596 [gitlab] gitlab: Upgrading to 12.2.9-1 fails
There is no source info for the package 'gitlab' at version '12.2.9-1+fto10+2'
with architecture ''
Unable to make a source version for version '12.2.9-1+fto10+2'
Marked as fixed in
Processing commands for cont...@bugs.debian.org:
> reopen 944748
Bug #944748 {Done: Arturo Borrero Gonzalez } [nftables]
nftables: no init script
Bug reopened
Ignoring request to alter fixed versions of bug #944748 to the same values
previously set
> severity 944748 serious
Bug #944748
ktp-contact-list has been kept out of testing for over a year, though this
issue is fixed by the patch and new upstream version. If help is wanted with
this, please let it be known.
Package: python3-hijra
Version: 0.4.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwrite other
Package: fst-dev
Version: 0.115.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
src:fst (builds fst-dev) and src:openfst (builds libfst-dev) are
Acknowledged.
DPL is taking up all my Debian time at the moment.
It's not the end of the world if moonshot-trust-router falls out of
testing, but hopefully I'll get to this before it happens.
It's almost certainly simple.
Processing control commands:
> retitle -1 trilinos: intrepid2 package is not shipped
Bug #944688 [src:deal.ii] deal.ii ftbfs everywhere it build before during
binNMU's for assimp 5.0.0
Changed Bug title to 'trilinos: intrepid2 package is not shipped' from 'deal.ii
ftbfs everywhere it build
Package: gitlab
Version: 12.2.9-1+fto10+1
Followup-For: Bug #944596
More info about the bug:
- Deleting file active_record_mysql_timestamp.rb, fails on
active_record_mysql_timestamp.rb, because the same error, "undefined method
mysql?".
Error MSG:
NoMethodError: undefined method
Control: retitle -1 trilinos: intrepid2 package is not shipped
Control: reassign -1 src:trilinos 12.14.1-1
Control: affects -1 src:deal.ii
On 2019/11/14 20:05, Adrian Bunk wrote:
So that's caused by the new trilinos.
Indeed, the new trilinos package introduces, and builds, the new
intrepid2
Package: gitlab
Version: 12.2.9-1+fto10+1
Followup-For: Bug #944596
Hi,
I have exactly the same problem. Installation are originally on gitlab 8, until
yesterday working without problem on 12.1
NoMethodError: undefined method `mysql?' for Gitlab::Database:Module
Processing commands for cont...@bugs.debian.org:
> tags 944692 + sid bullseye
Bug #944692 [src:thin-provisioning-tools] thin-provisioning-tools version
0.7.6-2.1 FTBFS
Added tag(s) sid and bullseye.
> found 944683 0.6+dfsg-1
Bug #944683 {Done: Sebastien Jodogne } [orthanc-dicomweb]
FTBFS:
Le 13/11/2019 à 00:25, Shmerl a écrit :
I am aware of the issue. No resend the same content as the bug.
It was a long week end here and I have a $$$ job.
Don't hesitate to step in to help, this is opensource ;)
Thanks! Do you have any hints about what to experiment with to address
it? I'm
Processing control commands:
> tags -1 wontfix
Bug #944748 [nftables] nftables: no init script
Added tag(s) wontfix.
> severity -1 normal
Bug #944748 [nftables] nftables: no init script
Severity set to 'normal' from 'serious'
--
944748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944748
Control: tags -1 wontfix
Control: severity -1 normal
On 11/14/19 7:00 PM, Thorsten Glaser wrote:
>
[..]
>
> However, nftables appears to ship a systemd unit, which is a
> clear violation of Policy §9.11:
> “However, any package integrating with other init systems
> must also be
Your message dated Fri, 15 Nov 2019 08:52:49 +0100
with message-id <84e3044a-5006-7ce5-56a8-8f1e5b624...@orthanc-labs.com>
and subject line Closing
has caused the Debian Bug report #944671,
regarding orthanc-dicomweb: missing build on armel
to be marked as done.
This means that you claim that the
47 matches
Mail list logo
