Hi Scott,
On Mon, Dec 02, 2019 at 12:18:38PM -0500, Scott Talbert wrote:
> On Tue, 8 Oct 2019, Andreas Tille wrote:
>
> > Hi Flávio,
> >
> > Varun Hiremath once cared for Debian packages of ModelBuilder[1]. His
> > effort seemed to have been stalled and so Debian remained at version
> > 0.4.1.
Your message dated Tue, 03 Dec 2019 05:19:47 +
with message-id
and subject line Bug#945345: fixed in therion 5.4.4ds1-3
has caused the Debian Bug report #945345,
regarding therion: Missing build-dep on python; build-depend on python3 instead
to be marked as done.
This means that you claim
Processing control commands:
> tags -1 + patch pending
Bug #944947 [src:python-uinput] python-uinput: needs an explicit build
dependency on dh-python
Bug #945233 [src:python-uinput] python-uinput: needs an explicit build
dependency on dh-python
Added tag(s) patch.
Added tag(s) patch.
--
Control: tags -1 + patch pending
Dear maintainer,
I've prepared an NMU for python-uinput (versioned as 0.11.2-2.1) and
uploaded it to DELAYED/1. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru python-uinput-0.11.2/debian/changelog python-uinput-
Processing commands for cont...@bugs.debian.org:
> tags 945345 + pending
Bug #945345 [therion] therion: Missing build-dep on python; build-depend on
python3 instead
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
945345:
Processing control commands:
> reassign -1 ftp.debian.org
Bug #937476 [src:pymappergui] pymappergui: Python2 removal in sid/bullseye
Bug reassigned from package 'src:pymappergui' to 'ftp.debian.org'.
No longer marked as found in versions pymappergui/0.1-2.
Ignoring request to alter fixed versions
Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: pymappergui -- RoQA; dead upstream; unmaintained; low
popcon; blocking py2 removal
--
Grüße Herr / Frau,
Benötigen Sie finanzielle Unterstützung (Darlehen)?
Sprechen Sie mit uns bei Banca IMI S.P.A., wir werden Ihre finanziellen
Probleme lösen.
Unser Zinssatz beträgt 1,3% Bitte bewerben Sie sich jetzt und füllen
Sie die folgenden Bewerbungsdetails aus:
Vollständiger
On Mon, 2 Dec 2019, Scott Talbert wrote:
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html
Your package either build-depends, depends on Python2, or uses Python2
in the
On Fri, 30 Aug 2019, Matthias Klose wrote:
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html
Your package either build-depends, depends on Python2, or uses Python2
in the
Your message dated Mon, 02 Dec 2019 20:23:51 -0700
with message-id <878snuum60@iris.silentflame.com>
and subject line Re: Bug#834026: libghc-yi-rope-dev: links against libicu but
doesn't depend on it
has caused the Debian Bug report #834026,
regarding libghc-yi-rope-dev: links against libicu
Processing control commands:
> severity -1 serious
Bug #834026 [libghc-yi-rope-dev] libghc-yi-rope-dev: links against libicu but
doesn't depend on it
Severity set to 'serious' from 'important'
> tag -1 - moreinfo
Bug #834026 [libghc-yi-rope-dev] libghc-yi-rope-dev: links against libicu but
Processing commands for cont...@bugs.debian.org:
> forwarded 938600 https://github.com/sunpinyin/sunpinyin/issues/94
Bug #938600 [src:sunpinyin] sunpinyin: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to
'https://github.com/sunpinyin/sunpinyin/issues/94'.
> quit
Stopping
Package: gitlab-workhorse
Version: 8.8.1+debian-3
Severity: serious
Tags: patch
gitlab-workhorse build-depends on golang-logrus (>= 1.0~), golang-logrus used
to be a transitional package, but is now (in testing) only an unversioned virtual
package that does not satisfy your build-dependency.
Processing commands for cont...@bugs.debian.org:
> severity 938909 serious
Bug #938909 [src:zope.interface] zope.interface: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
938909:
Package: qtpass
Version: 1.3.0-2
Severity: grave
Justification: renders package unusable
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Scott Jacobs
To: Debian Bug Tracking System
Subject: qtpass: Invoking results in SegFault
Bcc: Scott
Package: zeroinstall-injector
Version: 2.14.1-3
Severity: serious
zeroinstall-injector build-depends on libcurl-ocaml-dev which is not currently
in testing, either libcurl-ocaml-dev needs to be fixed so it can return to
testing, zeroinstall-injector needs to eliminate the dependency (no idea
Package: rust-rusty-tags
Version: 3.5.1-1
Severity: serious
Tags: bullseye, sid
rust-rusty-tags build-depends on librust-dirs-1+default-dev which is no longer
provided by rust-dirs. It seems to have been replaced by
librust-dirs-2+default-dev.
Processing commands for cont...@bugs.debian.org:
> severity 937901 serious
Bug #937901 [src:python-lz4] python-lz4: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937901:
Source: opencpn
Version: 4.8.8+dfsg.2-1
Severity: grave
Justification: renders package unusable
opencpn build-depends on libwxgtk3.0-dev, but that's been dropped
(there are still some crufty remnants in unstable, but libwxgtk3.0-dev
is no longer built by the wxwidgets3.0 source package, and isn't
Your message dated Mon, 02 Dec 2019 23:56:11 +
with message-id
and subject line Bug#945450: fixed in python-urllib3 1.25.6-3
has caused the Debian Bug report #945450,
regarding python-urllib3: FTBFS under C locale
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 02 Dec 2019 23:26:40 +
with message-id
and subject line Bug#945836: fixed in zanshin 0.5.0-3
has caused the Debian Bug report #945836,
regarding zanshin does not built with new KDEPIM 19.08
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> forwarded 946003 https://github.com/pytroll/pyresample/issues/237
Bug #946003 [src:pyresample] pyresample: autopkgtest failures
Set Bug forwarded-to-address to
'https://github.com/pytroll/pyresample/issues/237'.
> thanks
Stopping processing
Your message dated Mon, 02 Dec 2019 23:05:30 +
with message-id
and subject line Bug#945419: fixed in libpillowfight 0.3.0-3
has caused the Debian Bug report #945419,
regarding libpillowfight ftbfs on all architectures
to be marked as done.
This means that you claim that the problem has been
X-Debbugs-CC: Gürkan Myczko
Dear Gürkan,
On Thu, 28 Nov 2019 20:50:08 + nodiscc wrote:
> Thqnk you, is there any chance for this fix to land in Debian stable?
> Or do we have to wait for the next release (i believe it will be
> available in stable due to the high severity)
I am proposing
Hi,
thanks, it's exactly that! Adding the version number in the egg file
fixed my issue also!
Merci!
u
On Mon, 02 Dec 2019 19:38:57 +0100 Patrice Duroux
wrote:
>
> Hi,
>
> It is may be the same bug as the one in my bug report here:
>
Processing control commands:
> tags -1 patch
Bug #945976 [octave-dicom] octave-dicom: fails to find GDCM on many
architectures.
Added tag(s) patch.
--
945976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
control: tags -1 patch
On Mon, 2 Dec 2019 00:58:19 + peter green wrote:
> Package: octave-dicom
> Version: 0.2.2-4
> Severity: serious
>
> octave-dicom failed to build on armel, armhf, i386 and mips64el. It seems the
> problem was a failure to find gdcm.
>
> > checking for GDCM... CMake
Hi Chris,
On Mon, Dec 02, 2019 at 09:30:49PM +0100, Chris Lamb wrote:
> Chris Lamb wrote:
>
> > Package: python-django
> > Version: 1.7.11-1+deb8u7
> […]
> > CVE-2019-19118[0]:
> > | Django 2.1 before 2.1.15 and 2.2 before 2.2.8 allows unintended model
> > | editing. A Django model admin
Processing commands for cont...@bugs.debian.org:
> found 946011 2:2.1-1
Bug #946011 [python-django] python-django: CVE-2019-19118
There is no source info for the package 'python-django' at version '2:2.1-1'
with architecture ''
Unable to make a source version for version '2:2.1-1'
Marked as
On Wed, Nov 27, 2019 at 10:25:36AM -0800, Yi-Hung Wei wrote:
> On Wed, Oct 9, 2019 at 10:35 AM Ben Pfaff wrote:
> >
> > The list of copyright holders was incomplete and out of date. This
> > updates it based on a "grep" for copyright notices, which I reviewed by
> > hand.
> >
> > CC:
Processing commands for cont...@bugs.debian.org:
> notfixed 946011 2:3.0-1
Bug #946011 [python-django] python-django: CVE-2019-19118
There is no source info for the package 'python-django' at version '2:3.0-1'
with architecture ''
Unable to make a source version for version '2:3.0-1'
No longer
Processing commands for cont...@bugs.debian.org:
> fixed 946011 2:3.0-1
Bug #946011 [python-django] python-django: CVE-2019-19118
There is no source info for the package 'python-django' at version '2:3.0-1'
with architecture ''
Unable to make a source version for version '2:3.0-1'
Marked as
Processing commands for cont...@bugs.debian.org:
> fixed 946011 2:3.0-1
Bug #946011 [python-django] python-django: CVE-2019-19118
There is no source info for the package 'python-django' at version '2:3.0-1'
with architecture ''
Unable to make a source version for version '2:3.0-1'
Ignoring
Processing commands for cont...@bugs.debian.org:
> tags 946011 + upstream fixed-upstream
Bug #946011 [python-django] python-django: CVE-2019-19118
Added tag(s) fixed-upstream and upstream.
> fixed 946011 2:2.2.8-1
Bug #946011 [python-django] python-django: CVE-2019-19118
There is no source info
Processing commands for cont...@bugs.debian.org:
> fixed 946011 2:3.0-1
Bug #946011 [python-django] python-django: CVE-2019-19118
There is no source info for the package 'python-django' at version '2:3.0-1'
with architecture ''
Unable to make a source version for version '2:3.0-1'
Marked as
Processing commands for cont...@bugs.debian.org:
> tags 944775 + ftbfs
Bug #944775 [src:pprepair] FTBFS with CGAL 5.0
Added tag(s) ftbfs.
> tags 944776 + ftbfs
Bug #944776 [src:prepair] FTBFS with CGAL 5.0
Added tag(s) ftbfs.
> tags 944197 + ftbfs
Bug #944197 [src:rheolef] FTBFS: LaTeX Error:
Chris Lamb wrote:
> Package: python-django
> Version: 1.7.11-1+deb8u7
[…]
> CVE-2019-19118[0]:
> | Django 2.1 before 2.1.15 and 2.2 before 2.2.8 allows unintended model
> | editing. A Django model admin displaying inline related models, where
> | the user has view-only permissions to a parent
Package: python-django
Version: 1.7.11-1+deb8u7
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security
Hi,
The following vulnerability was published for python-django.
CVE-2019-19118[0]:
| Django 2.1 before 2.1.15 and 2.2 before 2.2.8 allows unintended model
| editing. A Django
On Mon, Dec 02, 2019 at 07:37:02PM +, Chris Lamb wrote:
> Hi Julien,
>
> > It seems to me the test is inherently extremely sensitive to the exact
> > version of black used, so it probably shouldn't be part of autopkgtests?
>
> Mmm, except I anticipated this at the time with the following
>
Control: tag -1 pending
Hello,
Bug #945993 in diffoscope 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 #945993 [diffoscope] diffoscope: FAILED
tests/test_source.py::test_code_is_black_clean - assert 228381 == 0
Added tag(s) pending.
--
945993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945993
Debian Bug Tracking System
Contact
Hi Julien,
> It seems to me the test is inherently extremely sensitive to the exact
> version of black used, so it probably shouldn't be part of autopkgtests?
Mmm, except I anticipated this at the time with the following
commit:
Processing control commands:
> tags -1 ftbfs
Bug #946004 [src:satpy] satpy: autopkgtest failures
Added tag(s) ftbfs.
--
946004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 ftbfs
On 12/2/19 7:36 PM, Bas Couwenberg wrote:
> The autopkgtest for your package are failing which block testing migration of
> its dependencies.
>
> The log shows:
>
> ==
> FAIL:
Your message dated Mon, 02 Dec 2019 19:21:16 +
with message-id
and subject line Bug#945878: fixed in openni2 2.2.0.33+dfsg-13
has caused the Debian Bug report #945878,
regarding libopenni2: uses too much TLS memory on arm64 and ppc64el
to be marked as done.
This means that you claim that the
Processing control commands:
> tags -1 ftbfs
Bug #946003 [src:pyresample] pyresample: autopkgtest failures
Added tag(s) ftbfs.
--
946003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 ftbfs
On 12/2/19 7:34 PM, Bas Couwenberg wrote:
> The autopkgtest for your package are failing which block testing migration of
> its dependencies.
>
> The log shows:
>
> ==
> FAIL: test_custom
Processing commands for cont...@bugs.debian.org:
> reassign 945878 openni2
Bug #945878 [libopenni2] libopenni2: uses too much TLS memory on arm64 and
ppc64el
Warning: Unknown package 'libopenni2'
Bug reassigned from package 'libopenni2' to 'openni2'.
Ignoring request to alter found versions of
Control: tag -1 pending
Hello,
Bug #945878 in openni2 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 #945878 [libopenni2] libopenni2: uses too much TLS memory on arm64 and
ppc64el
Warning: Unknown package 'libopenni2'
Added tag(s) pending.
Warning: Unknown package 'libopenni2'
--
945878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945878
Processing control commands:
> reassign -1 libopenni2
Bug #945878 [src:python-pcl] python-pcl: FTBFS on arm64 and ppc64el
Bug reassigned from package 'src:python-pcl' to 'libopenni2'.
Warning: Unknown package 'libopenni2'
Warning: Unknown package 'libopenni2'
No longer marked as found in versions
Control: reassign -1 libopenni2
Control: retitle -1 libopenni2: uses too much TLS memory on arm64 and ppc64el
Control: affects -1 python-pcl
Hi,
* Graham Inggs [2019-11-30 13:49]:
Recent builds of python-pcl have been failing on arm64 and ppc64el
[1][2], where it built previously.
line 2,
Hi,
It is may be the same bug as the one in my bug report here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945887
I found a solution by editing the following file after installation:
/usr/lib/python3/dist-packages/testpath-.egg-info
(provided by python3-testpath)
The 'Version:' field
Source: pyresample
Version: 1.13.2-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Dear Maintainer,
The autopkgtest for your package are failing which block testing migration of
its dependencies.
The log shows:
Source: satpy
Version: 0.16.1-4
Severity: serious
Justification: makes the package in question unusable or mostly so
Dear Maintainer,
The autopkgtest for your package are failing which block testing migration of
its dependencies.
The log shows:
Your message dated Mon, 02 Dec 2019 17:51:09 +
with message-id
and subject line Bug#937458: fixed in pyicu 2.2-3
has caused the Debian Bug report #937458,
regarding pyicu: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Wed, 23 Oct 2019, mo...@debian.org wrote:
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html
Your package either build-depends, depends on Python2, or uses Python2
in the
On Tue, 8 Oct 2019, Andreas Tille wrote:
Hi Flávio,
Varun Hiremath once cared for Debian packages of ModelBuilder[1]. His
effort seemed to have been stalled and so Debian remained at version
0.4.1. In the process of migrating all Debian packages from Python2 to
Python3 I stumbled upon this
Hi,
I also ran into this bug after updating my machines during the weekend,
both machines run on Debian Sid.
The issue appeared with some "pip3 install XXX", but is also present on
simple "pip3 list"
I thought it was an issue with Debian shifting to Python 3.8, so I tried
to reinstall a
A future Seqan3 release will need liblemon, so I'll look into it.
On Mon, Dec 2, 2019 at 12:36 PM Andreas Tille wrote:
> Control: tags -1 help
>
> Hi,
>
> I wonder if there might be some remaining interest in liblemon. The
> Debian Med team who introduced it into Debian does not need it any
There are indeed a LOT of errors in there (and a sprinkling of
harmless warnings which ought really to be silenced within the test
framework).
Picking on the very last one as a simple case, you got:
```
==
FAIL: test_ColumnUnit
Hi Peter,
On Wed, Nov 20, 2019 at 01:36:50PM +0100, Andreas Tille wrote:
> >
> > https://github.com/biopython/biopython/issues/2350
Since I urgently need Biopython >= 1.74 to fix some other bugs I decided
to try to ignore those issues we discussed here and made sure that build
time tests will
On Mon, Oct 07, 2019 at 09:36:56AM +0200, Miroslav Kravec wrote:
> Hello Markus,
>
> thank you for informing about this issue. Is this blocking you? Are
> you releasing a new version of jackson databind to Debian?
Hi Miroslav,
I opened a merge request for this issue [1], since this bug is
Processing commands for cont...@bugs.debian.org:
> tags 941687 + patch
Bug #941687 [lablie] lablie: FTBFS with jackson-databind 2.10.0
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
941687:
Am 02.12.19 um 12:37 schrieb Matthew Vernon:
> Hi,
>
> I've pushed a -2 with a patch from upstream that fixes an ARM issue; I'm
> not sure it'll be what we need, but we'll see.
>
Thank you.
Is see that you made a binary upload for i386.
Those binary uploads can not migrate to testing (anymore):
Your message dated Mon, 2 Dec 2019 13:41:44 +
with message-id <034d8054-b6c6-a225-4654-c2647e9ef...@chiark.greenend.org.uk>
and subject line Fixed with upstream patch
has caused the Debian Bug report #945972,
regarding FTBFS on armel: test-suite failure
to be marked as done.
This means that
Your message dated Mon, 02 Dec 2019 13:51:18 +
with message-id
and subject line Bug#942716: fixed in nml 0.4.5-2
has caused the Debian Bug report #942716,
regarding nml ftbfs (test errors)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Mon, 02 Dec 2019 13:38:38 +
with message-id
and subject line Bug#945743: fixed in velvet 1.2.10+dfsg1-6
has caused the Debian Bug report #945743,
regarding velvet: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 02 Dec 2019 13:38:54 +
with message-id
and subject line Bug#944134: fixed in vistrails 3.0~git+9dc22bd-2
has caused the Debian Bug report #944134,
regarding vistrails Depends on python-vtk6 which is no longer build from source
to be marked as done.
This means that you
Package: diffoscope
Severity: serious
Tags: bullseye sid
X-Debbugs-Cc: bl...@packages.debian.org
diffoscope autopkgtests fail with the current version of "black" in sid:
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/diffoscope/3557636/log.gz
It seems to me the test is inherently
Your message dated Mon, 02 Dec 2019 12:51:30 +
with message-id
and subject line Bug#945704: fixed in ray 2.3.1-7
has caused the Debian Bug report #945704,
regarding ray: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 02 Dec 2019 12:34:40 +
with message-id
and subject line Bug#945495: fixed in ocaml 4.08.1-5
has caused the Debian Bug report #945495,
regarding ocaml-nox: missing Breaks+Replaces: ocaml-compiler-libs (<< 4.08)
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #945495 [ocaml-nox] ocaml-nox: missing Breaks+Replaces: ocaml-compiler-libs
(<< 4.08)
Added tag(s) pending.
--
945495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Hi Andreas,
I think that is the moment where the skimage build should be simplified
to the "official" build process: Python convention is that symbols
starting with an underscore are internal only (and ofcourse subject to
quick and unannounced changes). debian/bin/process_pyx.py however
depends
Control: tag -1 pending
Hello,
Bug #945495 in ocaml 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,
I've pushed a -2 with a patch from upstream that fixes an ARM issue; I'm
not sure it'll be what we need, but we'll see.
Regards,
Matthew
Your message dated Mon, 02 Dec 2019 11:34:31 +
with message-id
and subject line Bug#935287: fixed in obitools 1.2.13+dfsg-2
has caused the Debian Bug report #935287,
regarding obitools: FTBFS on amd64
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> tags -1 help
Bug #925749 [src:liblemon] liblemon: ftbfs with GCC-9
Added tag(s) help.
--
925749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 help
Hi,
I wonder if there might be some remaining interest in liblemon. The
Debian Med team who introduced it into Debian does not need it any more
for any of its packages. It seems it us orphaned upstream. I'd be
willing to keep the package alive if someone might provide a
Interesting, let's hear it
On Fri, Nov 29, 2019, 10:12 PM Smadar Barber-Tsadik
wrote:
> Sorry to break into your privacy in this manner,
> I'm Smadar Barber-Tsadik, Deputy Chief Executive Officer
> of First International Bank of Israel Ltd (FIBI).
> I am getting in touch with you regarding an
Package: apngdis
Version: 2.5-2
Severity: grave
Tags: a11y
Justification: renders package unusable
Dear Maintainer,
apngdis is not working properly on Debian Buster.
It's producing a list of blang (black) images. It happened to any apng files I
tested.
First I discovered this issue on
Your message dated Mon, 02 Dec 2019 10:51:36 +
with message-id
and subject line Bug#945924: fixed in qemu 1:4.1-3
has caused the Debian Bug report #945924,
regarding qemu-system-data: Should "Provides: sgabios"?
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 02 Dec 2019 10:49:45 +
with message-id
and subject line Bug#945851: fixed in ocaml-num 1.3-1
has caused the Debian Bug report #945851,
regarding libnum-ocaml-dev: missing Breaks+Replaces: ocaml-nox (<< 4.08)
to be marked as done.
This means that you claim that the
Control: tags -1 help
Hi,
I tried my luck with #945389 since two Debian Med packages are depending
from skimage. So at first I tried to upgrade to the latest upstream
version to possibly forward some reasonable bug report. Unfortunately
the build starts very early:
...
debian/rules build
Processing control commands:
> tags -1 help
Bug #945389 [src:skimage] skimage: FTBFS with python3.8 (test failures)
Added tag(s) help.
--
945389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 02 Dec 2019 10:06:08 +
with message-id
and subject line Bug#945933: fixed in mpich 3.3.2-2
has caused the Debian Bug report #945933,
regarding mpich FTBFS on armel, armhf and mipsel
to be marked as done.
This means that you claim that the problem has been dealt with.
forwarded 945972 https://bugs.exim.org/show_bug.cgi?id=2478
quit
On 01/12/2019 23:15, Michael Biebl wrote:
> pcre2 FTBFS on armel:
> https://buildd.debian.org/status/fetch.php?pkg=pcre2=armel=10.34-1=1574962559=0
Thanks for the bug report; I've forwarded it upstream. I'm afraid I
don't know
Processing commands for cont...@bugs.debian.org:
> forwarded 945972 https://bugs.exim.org/show_bug.cgi?id=2478
Bug #945972 [src:pcre2] FTBFS on armel: test-suite failure
Set Bug forwarded-to-address to 'https://bugs.exim.org/show_bug.cgi?id=2478'.
> quit
Stopping processing here.
Please contact
Processing commands for cont...@bugs.debian.org:
> # this is causing autopkgtest regressions in diffoscope, which usese
> # guestfs. let's prevent test migration.
> severity 945924 serious
Bug #945924 [qemu-system-data] qemu-system-data: Should "Provides: sgabios"?
Severity set to 'serious' from
Your message dated Mon, 02 Dec 2019 09:04:05 +
with message-id
and subject line Bug#945980: fixed in obfs4proxy 0.0.8-1
has caused the Debian Bug report #945980,
regarding obfs4proxy, build-depends on package that is no longer in testing.
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> tags 945423 + upstream
Bug #945423 [src:duplicity] duplicity fails tests with Python 3.8
Added tag(s) upstream.
> forwarded 945423 https://bugs.launchpad.net/duplicity/+bug/1853809
Bug #945423 [src:duplicity] duplicity fails tests with Python 3.8
tags 945423 + upstream
forwarded 945423 https://bugs.launchpad.net/duplicity/+bug/1853809
thanks
On Sun, 24 Nov 2019 17:17:46 +0100, Matthias Klose writes:
>Package: src:duplicity
>Version: 0.8.07-1
>Severity: serious
>Tags: sid bullseye ftbfs
>User: debian-pyt...@lists.debian.org
>Usertags:
93 matches
Mail list logo
