Your message dated Thu, 02 Apr 2020 12:06:12 +0530
with message-id <9140fe7c-ccf4-454c-ac9c-9b40b751e...@onenetbeyond.org>
and subject line Closing
has caused the Debian Bug report #951265,
regarding ruby-vips: autopkgtest fails on arm64: expected Vips::Error but
nothing was raised
to be marked as
Processing commands for cont...@bugs.debian.org:
> fixed 951265 2.017-1
Bug #951265 [src:ruby-vips] ruby-vips: autopkgtest fails on arm64: expected
Vips::Error but nothing was raised
The source 'ruby-vips' and version '2.017-1' do not appear to match any binary
packages
Marked as fixed in versio
Control: done -1 2.0.17-1
Tracker now shows "Required age reduced by 3 days because of
autopkgtest" indicating autopkgtest now passes.
Processing commands for cont...@bugs.debian.org:
> block 953852 with 936148
Bug #953852 [ardentryst] ardentryst: should this package be removed?
953852 was not blocked by any bugs.
953852 was not blocking any bugs.
Added blocking bug(s) of 953852: 936148
> thanks
Stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
> severity 948018 normal
Bug #948018 [src:getfem++] getfem++: b-d on python3-all-dev, but not built for
all supported Python3 versions
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assista
Your message dated Thu, 02 Apr 2020 06:18:31 +
with message-id
and subject line Bug#950560: fixed in apertium-oc-es 1.0.6~r57551-4
has caused the Debian Bug report #950560,
regarding apertium-oc-es FTBFS with apertium 3.6.1
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tags 951624 + patch
Bug #951624 [src:webdis] webdis, build-depends on removed package
Added tag(s) patch.
> tags 951624 + pending
Bug #951624 [src:webdis] webdis, build-depends on removed package
Added tag(s) pending.
--
951624: https://bugs.debian.org/cgi-bin/bugr
Control: tags 951624 + patch
Control: tags 951624 + pending
Dear maintainer,
I've prepared an NMU for webdis (versioned as 0.1.4+dfsg-1.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should cancel it.
cu
Adrian
diff -Nru webdis-0.1.4+dfsg/debian/changelog webdis-0.1.4+dfsg/de
Your message dated Thu, 02 Apr 2020 04:04:09 +
with message-id
and subject line Bug#937671: fixed in python-crypto 2.6.1-13.1
has caused the Debian Bug report #937671,
regarding python-crypto: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 02 Apr 2020 03:48:41 +
with message-id
and subject line Bug#937643: fixed in python-characteristic 14.3.0-7
has caused the Debian Bug report #937643,
regarding python-characteristic: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that t
Your message dated Thu, 02 Apr 2020 03:48:24 +
with message-id
and subject line Bug#936329: fixed in constantly 15.1.0-2
has caused the Debian Bug report #936329,
regarding constantly: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been de
Your message dated Thu, 02 Apr 2020 03:48:36 +
with message-id
and subject line Bug#952131: fixed in pyhamcrest 1.9.0-3
has caused the Debian Bug report #952131,
regarding pyhamcrest: FTBFS: build-dependency not installable: python-pytest-cov
to be marked as done.
This means that you claim th
Your message dated Thu, 02 Apr 2020 03:48:35 +
with message-id
and subject line Bug#937456: fixed in pyhamcrest 1.9.0-3
has caused the Debian Bug report #937456,
regarding pyhamcrest: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dea
Control: tags 937671 + patch
Dear maintainer,
I've prepared an NMU for python-crypto (versioned as 2.6.1-13.1). The diff
is attached to this message.
Regards.
diff -Nru python-crypto-2.6.1/debian/changelog python-crypto-2.6.1/debian/changelog
--- python-crypto-2.6.1/debian/changelog 2019-11-16
Processing control commands:
> tags 937671 + patch
Bug #937671 [src:python-crypto] python-crypto: Python2 removal in sid/bullseye
Added tag(s) patch.
--
937671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #936329 [src:constantly] constantly: Python2 removal in sid/bullseye
Added tag(s) pending.
--
936329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Thu, 02 Apr 2020 03:33:29 +
with message-id
and subject line Bug#937415: fixed in pycurl 7.43.0.2-3
has caused the Debian Bug report #937415,
regarding pycurl: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt wi
Control: tag -1 pending
Hello,
Bug #936329 in constantly 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:
https://salsa.debian.org/python-team/modules/constantly/-/commit/417ef27432fa2f7
Control: tag -1 pending
Hello,
Bug #952131 in pyhamcrest 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:
https://salsa.debian.org/python-team/modules/pyhamcrest/-/commit/ac4aa2ffdc72e88
Processing control commands:
> tag -1 pending
Bug #937456 [src:pyhamcrest] pyhamcrest: Python2 removal in sid/bullseye
Added tag(s) pending.
--
937456: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #937456 in pyhamcrest 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:
https://salsa.debian.org/python-team/modules/pyhamcrest/-/commit/ac4aa2ffdc72e88
Processing control commands:
> tag -1 pending
Bug #952131 [src:pyhamcrest] pyhamcrest: FTBFS: build-dependency not
installable: python-pytest-cov
Added tag(s) pending.
--
952131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952131
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Processing control commands:
> tag -1 pending
Bug #937415 [src:pycurl] pycurl: Python2 removal in sid/bullseye
Added tag(s) pending.
--
937415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937415
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #937415 in pycurl 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:
https://salsa.debian.org/python-team/modules/pycurl/-/commit/b180abc9189cd40674e8128
Your message dated Thu, 02 Apr 2020 03:18:27 +
with message-id
and subject line Bug#936714: fixed in hyperlink 19.0.0-2
has caused the Debian Bug report #936714,
regarding hyperlink: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Thu, 02 Apr 2020 03:18:32 +
with message-id
and subject line Bug#938487: fixed in singledispatch 3.4.0.3-3
has caused the Debian Bug report #938487,
regarding singledispatch: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem ha
Control: tag -1 pending
Hello,
Bug #938487 in singledispatch 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:
https://salsa.debian.org/python-team/modules/singledispatch/-/commit/10bb7fe
Processing control commands:
> tag -1 pending
Bug #938487 [src:singledispatch] singledispatch: Python2 removal in sid/bullseye
Added tag(s) pending.
--
938487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #936714 in hyperlink 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:
https://salsa.debian.org/python-team/modules/hyperlink/-/commit/12b108324c4503d6e
Processing control commands:
> tag -1 pending
Bug #936714 [src:hyperlink] hyperlink: Python2 removal in sid/bullseye
Added tag(s) pending.
--
936714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936714
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-an
Package: kernelshark
Version: 2.8.3-5
Severity: grave
X-Debbugs-CC: sudipm.mukher...@gmail.com
Dear Debian kernelshark (trace-cmd) maintainer,
When I perform the following actions in kernelshark in Debian Sid, kernel
shark will crash:
1. Open kernelshark
2. Click the "+" button
Partial traceba
> I've just requested access to the telepathy team in salsa, so that i
> can push my changes there.
for now, attached the patch for the just uploaded package
diff --git a/debian/changelog b/debian/changelog
index 1550f7159..e398df2c1 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,
On Thu, 26 Mar 2020 21:02:59 +0100 Matthias Klose wrote:
> yes, but we cannot rebuild the package, because it build-depends on gnat-8.
> Filed a removal bug for gcc-8 instead.
An easy fix would probably be to temporarily add a versioned
Provides: libgcc-s1 (= 1:${binary:Version})
to libgcc-s1 i
Your message dated Wed, 1 Apr 2020 18:20:44 -0400
with message-id
and subject line Re: rabbitvcs: Depends on unmaintained pygtk
has caused the Debian Bug report #885476,
regarding rabbitvcs: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has been d
Your message dated Wed, 01 Apr 2020 22:03:43 +
with message-id
and subject line Bug#937638: fixed in python-certifi 2019.11.28-2
has caused the Debian Bug report #937638,
regarding python-certifi: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 01 Apr 2020 22:03:54 +
with message-id
and subject line Bug#938483: fixed in simplegeneric 0.8.1-3
has caused the Debian Bug report #938483,
regarding simplegeneric: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 01 Apr 2020 22:03:48 +
with message-id
and subject line Bug#938278: fixed in python-xmltodict 0.12.0-2
has caused the Debian Bug report #938278,
regarding python-xmltodict: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
On Fri, 30 Aug 2019 07:37:18 + Matthias Klose wrote:
> Package: src:python-certifi
> Version: 2018.8.24-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
Consider maintain this package under the Debian python modules team umbrella
On Fri, 30 Aug 2019 07:48:50 + Matthias Klose wrote:
> Package: src:python-xmltodict
> Version: 0.11.0-2
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
Consider maintain this package under the Debian python modules team umbrella
Control: tag -1 pending
Hello,
Bug #938483 in simplegeneric 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:
https://salsa.debian.org/python-team/modules/simplegeneric/-/commit/2f3c66ede
Processing control commands:
> tag -1 pending
Bug #938483 [src:simplegeneric] simplegeneric: Python2 removal in sid/bullseye
Added tag(s) pending.
--
938483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-an
Processing commands for cont...@bugs.debian.org:
> tags 955432 + moreinfo unreproducible
Bug #955432 [src:gnome-shell-xrdesktop] gnome-shell-xrdesktop: FTBFS:
dh_missing: warning: usr/share/bash-completion/completions/gnome-extensions
exists in debian/tmp but is not installed to anywhere
Added t
Hello,
telepathy-gabble and telepathy-salut are the last 2 reverse
dependencies for python-twisted in Debian unstable, and i'd very much
like to remove that package soon.
It looks like twisted is only used for tests in both those packages
and it looks like they are not being run in d/rules anyway.
Processing commands for cont...@bugs.debian.org:
> fixed 945171 1:9.15.6-1
Bug #945171 {Done: Salvatore Bonaccorso } [src:bind9] bind9:
CVE-2019-6477: TCP-pipelined queries can bypass tcp-clients limit
The source 'bind9' and version '1:9.15.6-1' do not appear to match any binary
packages
Marked
On Mon, Oct 07, 2019 at 04:53:03PM +0200, Thibaut Paumard wrote:
> Dear Jeremy,
>
> Thanks, I have warned upstream that YAO will be removed if not updated
> to Python 3 and Gtk 3.
It's now the last package blocking the removal of pygtk, let's remove it.
Cheers,
Moritz
On Tue, Mar 24, 2020 at 10:13:33PM +0100, Moritz Mühlenhoff wrote:
> On Sun, Oct 06, 2019 at 06:00:02PM -0400, Jeremy Bicha wrote:
> > Control: severity -1 serious
> > Tags: fixed-upstream
> >
> > It looks to me like upstream has ported gasp to Python3 and GObject
> > Introspection.
> >
> > https
Source: xbmc-pvr-addons
Severity: serious
Hi,
The source builds only transitional packages and they are not needed anymore.
After removing them from testing they can be removed from unstable as well.
Cheers,
Balint
--
Balint Reczey
Ubuntu & Debian Developer
Processing control commands:
> severity -1 important
Bug #954402 [m2crypto] m2crypto: FTBFS since openssl 1.1.1e
Severity set to 'important' from 'serious'
--
954402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 important
Bug #954416 [python3.8] python3.8: FTBFS since openssl 1.1.1e
Severity set to 'important' from 'serious'
--
954416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 important
Bug #954418 [python2.7] python2.7: FTBFS since openssl 1.1.1e
Severity set to 'important' from 'serious'
--
954418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> severity -1 important
Bug #954419 [ruby2.7] ruby2.7: FTBFS since openssl 1.1.1e
Severity set to 'important' from 'serious'
--
954419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 important
OpenSSL 1.1.1f is in unstable now which reverts the unexpected EOF
reporting via SSL_ERROR_SSL.
In the OpenSSL 3.0 release it will be reported again as SSL_ERROR_SSL
with reason code SSL_R_UNEXPECTED_EOF_WHILE_READING.
Therefore the severity is downgraded to `importa
Processing control commands:
> severity -1 important
Bug #954417 [python3.7] python3.7: FTBFS since openssl 1.1.1e
Severity set to 'important' from 'serious'
--
954417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Wed, 1 Apr 2020 22:09:29 +0200
with message-id <9fd18286-a935-e7de-5654-a4b2cc195...@debian.org>
and subject line Re: src:fuzzywuzzy: fails to migrate to testing for too long
has caused the Debian Bug report #953347,
regarding src:fuzzywuzzy: fails to migrate to testing for too l
Your message dated Wed, 1 Apr 2020 22:07:19 +0200
with message-id <69e20560-d250-66d6-cf9a-2d2b0c94f...@debian.org>
and subject line Re: src:python-django-rest-hooks: fails to migrate to testing
for too long
has caused the Debian Bug report #953186,
regarding src:python-django-rest-hooks: fails to
Your message dated Wed, 1 Apr 2020 21:59:35 +0200
with message-id <20200401195935.ga32...@jadzia.comodo.priv.at>
and subject line Re: Bug#954495: libpoe-component-sslify-perl: FTBFS:
dh_auto_test: error: perl Build test --verbose 1 returned exit code 1
has caused the Debian Bug report #954495,
reg
Control: reassign -1 libio-socket-ssl-perl 2.067-1
Control: severity -1 important
Hi,
On Wed, Apr 01, 2020 at 08:40:05PM +0200, Sebastian Andrzej Siewior wrote:
> On 2020-03-31 21:49:51 [+0200], Salvatore Bonaccorso wrote:
> > Hi Kurt,
> Hi Salvatore,
>
> > I see, but then I prefer to loop in St
Processing control commands:
> reassign -1 libio-socket-ssl-perl 2.067-1
Bug #954371 [src:openssl] libio-socket-ssl-perl: FTBFS since openssl 1.1.1e
Bug reassigned from package 'src:openssl' to 'libio-socket-ssl-perl'.
No longer marked as found in versions openssl/1.1.1e-1.
Ignoring request to alt
Your message dated Wed, 01 Apr 2020 19:27:52 +
with message-id
and subject line Bug#955337: Removed package(s) from unstable
has caused the Debian Bug report #907453,
regarding irda-utils: No IrDA support in the buster kernel
to be marked as done.
This means that you claim that the problem ha
Your message dated Wed, 01 Apr 2020 19:29:28 +
with message-id
and subject line Bug#955344: Removed package(s) from unstable
has caused the Debian Bug report #937523,
regarding pyrit-opencl: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has b
Your message dated Wed, 01 Apr 2020 19:10:09 +
with message-id
and subject line Bug#955404: Removed package(s) from unstable
has caused the Debian Bug report #947298,
regarding ipython-py2: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 01 Apr 2020 19:09:33 +
with message-id
and subject line Bug#955382: Removed package(s) from unstable
has caused the Debian Bug report #938567,
regarding starpy: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been de
Your message dated Wed, 01 Apr 2020 19:11:15 +
with message-id
and subject line Bug#955503: Removed package(s) from unstable
has caused the Debian Bug report #937726,
regarding python-elements: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem ha
Your message dated Wed, 01 Apr 2020 19:11:15 +
with message-id
and subject line Bug#955503: Removed package(s) from unstable
has caused the Debian Bug report #899900,
regarding python-elements: Invalid maintainer address
debian-olpc-de...@lists.alioth.debian.org
to be marked as done.
This me
Your message dated Wed, 01 Apr 2020 19:07:24 +
with message-id
and subject line Bug#955350: Removed package(s) from unstable
has caused the Debian Bug report #895520,
regarding libunique-1.0-0: deprecated and unmaintained upstream
to be marked as done.
This means that you claim that the probl
Your message dated Wed, 01 Apr 2020 19:08:19 +
with message-id
and subject line Bug#955372: Removed package(s) from unstable
has caused the Debian Bug report #952035,
regarding ruby-ridley: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError:
to be marked as done.
This means that you clai
Your message dated Wed, 01 Apr 2020 19:06:12 +
with message-id
and subject line Bug#955349: Removed package(s) from unstable
has caused the Debian Bug report #885813,
regarding xfce4-notes-plugin: Depends on libunique
to be marked as done.
This means that you claim that the problem has been d
Your message dated Wed, 01 Apr 2020 19:04:22 +
with message-id
and subject line Bug#955252: Removed package(s) from unstable
has caused the Debian Bug report #936720,
regarding identicurse: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 01 Apr 2020 19:04:43 +
with message-id
and subject line Bug#955305: Removed package(s) from unstable
has caused the Debian Bug report #937267,
regarding pebl: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Wed, 01 Apr 2020 19:05:02 +
with message-id
and subject line Bug#955334: Removed package(s) from unstable
has caused the Debian Bug report #719916,
regarding Getting "Unexpected title page format Error" from yahoo2mbox
to be marked as done.
This means that you claim that th
Your message dated Wed, 01 Apr 2020 19:03:57 +
with message-id
and subject line Bug#955251: Removed package(s) from unstable
has caused the Debian Bug report #938202,
regarding python-stompy: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 01 Apr 2020 19:03:16 +
with message-id
and subject line Bug#955199: Removed package(s) from unstable
has caused the Debian Bug report #885282,
regarding gameclock: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has been d
Your message dated Wed, 01 Apr 2020 19:03:37 +
with message-id
and subject line Bug#955200: Removed package(s) from unstable
has caused the Debian Bug report #938210,
regarding python-tcpwrap: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 01 Apr 2020 19:03:16 +
with message-id
and subject line Bug#955199: Removed package(s) from unstable
has caused the Debian Bug report #936577,
regarding gameclock: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 01 Apr 2020 19:02:55 +
with message-id
and subject line Bug#955195: Removed package(s) from unstable
has caused the Debian Bug report #754377,
regarding eeepc-acpi-scripts: fails to install due to insserv rejecting the
script header
to be marked as done.
This means th
Your message dated Wed, 01 Apr 2020 19:00:10 +
with message-id
and subject line Bug#954897: Removed package(s) from unstable
has caused the Debian Bug report #954897,
regarding RM: pydxcluster - RoQA; python2-only; no upstream release since 2016;
low popcon; no rdeps
to be marked as done.
Th
Your message dated Wed, 01 Apr 2020 19:00:15 +
with message-id
and subject line Bug#954897: Removed package(s) from unstable
has caused the Debian Bug report #912495,
regarding pydxcluster: Please migrate to python3-pygame
to be marked as done.
This means that you claim that the problem has b
Your message dated Wed, 01 Apr 2020 19:00:15 +
with message-id
and subject line Bug#954897: Removed package(s) from unstable
has caused the Debian Bug report #912495,
regarding pydxcluster: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has be
Your message dated Wed, 01 Apr 2020 19:02:13 +
with message-id
and subject line Bug#955179: Removed package(s) from unstable
has caused the Debian Bug report #938461,
regarding securepass-tools: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem h
Your message dated Wed, 01 Apr 2020 19:02:13 +
with message-id
and subject line Bug#955179: Removed package(s) from unstable
has caused the Debian Bug report #899689,
regarding securepass-tools: Invalid maintainer address
pkg-securepass-de...@lists.alioth.debian.org
to be marked as done.
Thi
On 2020-03-31 21:49:51 [+0200], Salvatore Bonaccorso wrote:
> Hi Kurt,
Hi Salvatore,
> I see, but then I prefer to loop in Steffen Ullrich into the loop
> (upstream of IO::Socket::SSL). Steffen, see the above comment from
> Kurt in the Debian bug, so it looks we cannot close
> https://github.com/n
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-an
Your message dated Wed, 01 Apr 2020 16:48:37 +
with message-id
and subject line Bug#946771: fixed in librdf-doap-perl 0.104-2
has caused the Debian Bug report #946771,
regarding librdf-doap-perl: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been dea
Control: tag -1 pending
Hello,
Bug #946771 in librdf-doap-perl 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:
https://salsa.debian.org/perl-team/modules/packages/librdf-doap-perl/-/com
Processing control commands:
> tag -1 pending
Bug #946771 [src:librdf-doap-perl] librdf-doap-perl: autopkgtest failure
Added tag(s) pending.
--
946771: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> severity 936612 serious
Bug #936612 [src:gimp-plugin-registry] gimp-plugin-registry: Python2 removal in
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936612:
Processing commands for cont...@bugs.debian.org:
> severity 937103 serious
Bug #937103 [src:nagios-plugins-contrib] nagios-plugins-contrib: Python2
removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937
Processing commands for cont...@bugs.debian.org:
> tags 954673 - sid
Bug #954673 {Done: Lev Lamberov } [src:swi-prolog]
swi-prolog: FTBFS: E: Build killed with signal TERM after 150 minutes of
inactivity
Removed tag(s) sid.
> tags 954673 - bullseye
Bug #954673 {Done: Lev Lamberov } [src:swi-prol
Your message dated Wed, 01 Apr 2020 20:56:22 +0500
with message-id <87h7y319p5.fsf@localhost>
and subject line
has caused the Debian Bug report #954673,
regarding swi-prolog: FTBFS: E: Build killed with signal TERM after 150 minutes
of inactivity
to be marked as done.
This means that you claim t
Your message dated Wed, 1 Apr 2020 17:24:42 +0200
with message-id <20200401152442.ga1...@jadzia.comodo.priv.at>
and subject line Re: Bug#954626: libnet-server-mail-perl: FTBFS: dh_auto_test:
error: make -j4 test TEST_VERBOSE=1 returned exit code 2
has caused the Debian Bug report #954626,
regardin
Your message dated Wed, 01 Apr 2020 15:11:44 +
with message-id
and subject line Bug#944592: fixed in ocaml-deriving-ocsigen 0.7.1-1.1
has caused the Debian Bug report #944592,
regarding FTBFS with OCaml 4.08.1 (safe strings)
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> severity -1 normal
Bug #955490 [libvirt-daemon] libvirt-daemon: ERRORinternal error: child
reported (status=125): Kernel does not provide mount namespace: Permission
denied
Severity set to 'normal' from 'grave'
--
955490: https://bugs.debian.org/cgi-bin/bugre
control: severity -1 normal
Hi,
On Wed, Apr 01, 2020 at 04:39:34PM +0200, usuario wrote:
> Package: libvirt-daemon
> Version: 6.0.0-4
> Severity: grave
> Tags: a11y
> Justification: renders package unusable
certainly not unusable since others ore running just fine.
-- Guido
>
> Dear Maintainer
Processing control commands:
> tags -1 patch pending
Bug #944592 [src:ocaml-deriving-ocsigen] FTBFS with OCaml 4.08.1 (safe strings)
Added tag(s) patch and pending.
--
944592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with p
control: tags -1 patch pending
diff uploaded
G.
On Tue, 12 Nov 2019 10:22:55 +0100 =?utf-8?q?St=C3=A9phane_Glondu?=
wrote:
> Package: src:ocaml-deriving-ocsigen
> Version: 0.7.1-1
> Severity: serious
> Tags: ftbfs
> User: debian-ocaml-ma...@lists.debian.org
> Usertags: ocaml-4.08-transition
>
Package: libvirt-daemon
Version: 6.0.0-4
Severity: grave
Tags: a11y
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
sudo virt-install \
-n vm1 \
-r 512 \
--vcpus=2 \
--os-v
I debugged this case and looked into the FTBFS of ruby-handlebas-assets. I
checked out the upstream git repository and it tests just fine even when I
raise the haml and rake gem versions to match the ones in Debian. But it fails
with exactly the same error if I replace the javascript files in
vendo
Processing commands for cont...@bugs.debian.org:
> retitle 952026 ruby-handlebars-assets: FTBFS with current libjs-handlebars
> version: ERROR: ExecJS::ProgramError: ReferenceError: Handlebars is not
> defined
Bug #952026 [src:ruby-handlebars-assets] ruby-handlebars-assets: FTBFS: ERROR:
Test "
1 - 100 of 120 matches
Mail list logo