Your message dated Sat, 04 Apr 2020 05:18:37 +
with message-id
and subject line Bug#943077: fixed in fonts-lohit-deva 2.95.4-4
has caused the Debian Bug report #943077,
regarding fonts-lohit-deva: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #955669 [src:rdkit] rdkit: FTBFS: make[2]: opt-9: Command not found
Added tag(s) pending.
--
955669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #955669 in rdkit 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:
> reassign -1 src:pandas
Bug #955679 [src:python-geotiepoints] python-geotiepoints: FTBFS:
ModuleNotFoundError: No module named 'matplotlib'
Bug reassigned from package 'src:python-geotiepoints' to 'src:pandas'.
No longer marked as found in versions
Control: reassign -1 src:pandas
Control: found -1 0.25.3+dfsg-8
Control: affects -1 src:python-geotiepoints
On 4/3/20 9:42 PM, Lucas Nussbaum wrote:
>> File "/usr/lib/python3/dist-packages/pandas/util/testing.py", line 18, in
>>
>> from matplotlib.cbook import MatplotlibDeprecationWarning
Your message dated Sat, 04 Apr 2020 02:54:57 +
with message-id
and subject line Bug#955639: fixed in rss-bridge 2020-02-26+dfsg1-2
has caused the Debian Bug report #955639,
regarding rss-bridge: autopkgtest regression: non-zero exit status 1
to be marked as done.
This means that you claim
Control: severity -1 normal
On Sun, Mar 22, 2020 at 02:57:54PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> [...]
> > Trailer-Test: f
> > 140691743627136:error:14095126:SSL
Processing control commands:
> severity -1 normal
Bug #954698 [src:serf] serf: FTBFS: 1)
test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138:
expected <0> but was <120199>
Severity set to 'normal' from 'serious'
--
954698:
Processing commands for cont...@bugs.debian.org:
> found 954916 3.67-3.1
Bug #954916 [src:lgrind] lgrind: FTBFS with current texlive
Marked as found in versions lgrind/3.67-3.1.
> found 93 2.0.13-2
Bug #93 [src:haproxy] haproxy - unreachable maintainer
Marked as found in versions
Your message dated Fri, 03 Apr 2020 21:49:12 +
with message-id
and subject line Bug#955662: fixed in python-biom-format 2.1.8+dfsg-2
has caused the Debian Bug report #955662,
regarding python-biom-format: FTBFS: ERROR: Failure: ModuleNotFoundError (No
module named 'matplotlib')
to be marked
On Fri, 3 Apr 2020 23:28:04 +0200 Stephen Kitt wrote:
> On Fri, 3 Apr 2020 21:45:28 +0200, Lucas Nussbaum wrote:
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
> > Relevant part (hopefully):
> > > checking for amd64-w64-mingw32-gcc... no
> > >
On 4/3/20 9:55 PM, Lucas Nussbaum wrote:
> Source: python-tablib
> Version: 0.13.0-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200402 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on
On Fri, 3 Apr 2020 21:45:28 +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > checking for amd64-w64-mingw32-gcc... no
> > checking for x86_64-mingw32msvc-gcc... no
> > checking for
On 2020-04-03 22:39:20 +0200, Tino Mettler wrote:
> Package: libdvdread7
> Version: 6.1.0-1
> Followup-For: Bug #955367
>
> Hi,
>
> as mentioned in the above videolan bug tracker, the crash can be fixed by
> just rebuilding libdvdnav against libdvdread7. No changes to the package
> are needed.
Your message dated Fri, 03 Apr 2020 20:50:46 +
with message-id
and subject line Bug#955634: Removed package(s) from unstable
has caused the Debian Bug report #885135,
regarding pygtk: Unmaintained, use GObject Introspection instead
to be marked as done.
This means that you claim that the
Your message dated Fri, 03 Apr 2020 20:50:46 +
with message-id
and subject line Bug#955634: Removed package(s) from unstable
has caused the Debian Bug report #885135,
regarding pygtk: Unmaintained, should not be released with Debian
to be marked as done.
This means that you claim that the
Your message dated Fri, 03 Apr 2020 20:50:46 +
with message-id
and subject line Bug#955634: Removed package(s) from unstable
has caused the Debian Bug report #937452,
regarding pygtk: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 03 Apr 2020 20:49:03 +
with message-id
and subject line Bug#955645: fixed in diffoscope 139
has caused the Debian Bug report #955645,
regarding diffoscope: FTBFS: build-dependency not installable: python3-dumppdf
to be marked as done.
This means that you claim that
Your message dated Fri, 03 Apr 2020 20:48:19 +
with message-id
and subject line Bug#955048: Removed package(s) from unstable
has caused the Debian Bug report #954564,
regarding ruby-em-hiredis: FTBFS: ERROR: Test "ruby2.7" failed: ArgumentError:
to be marked as done.
This means that you
Your message dated Fri, 03 Apr 2020 20:49:41 +
with message-id
and subject line Bug#955623: Removed package(s) from unstable
has caused the Debian Bug report #938328,
regarding rabbyt: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Package: libdvdread7
Version: 6.1.0-1
Followup-For: Bug #955367
Hi,
as mentioned in the above videolan bug tracker, the crash can be fixed by
just rebuilding libdvdnav against libdvdread7. No changes to the package
are needed. The build-dependency should be adjusted for correctness, though.
Your message dated Fri, 03 Apr 2020 20:34:21 +
with message-id
and subject line Bug#955367: fixed in libdvdread 6.1.0+really6.0.2-1
has caused the Debian Bug report #955367,
regarding libdvdread7: crashes vlc when trying to read a DVD iso image
to be marked as done.
This means that you claim
Source: haskell-brick
Version: 0.46-2
Severity: serious
Control: fixed -1 0.47.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and
Processing control commands:
> fixed -1 1.0.5-1
Bug #955699 [src:lldpd] src:lldpd: fails to migrate to testing for too long:
ftbfs on multiple arches
Marked as fixed in versions lldpd/1.0.5-1.
--
955699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955699
Debian Bug Tracking System
Source: lldpd
Version: 1.0.4-1
Severity: serious
Control: fixed -1 1.0.5-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and
Processing control commands:
> fixed -1 0.47.1-1
Bug #955698 [src:haskell-brick] src:haskell-brick: fails to migrate to testing
for too long: ftbfs on armhf
Marked as fixed in versions haskell-brick/0.47.1-1.
--
955698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955698
Debian Bug
Source: dh-ada-library
Version: 6.19
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory
Processing commands for cont...@bugs.debian.org:
> reopen 954645
Bug #954645 {Done: Lucas Nussbaum } [src:behave] behave:
FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p
"3.7 3.8" returned exit code 13
Bug reopened
Ignoring request to alter fixed versions of bug
Source: pcscada
Version: 0.7.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
reopen 954645
thanks
> I'm closing those bugs: those failures are no longer reproducible,
> checking again 12 hours later. Either they were caused by another
> package that was fixed in the meantime, or they are random failures.
Actually, this is reproducible.
Lucas
Processing commands for cont...@bugs.debian.org:
> reopen 954620
Bug #954620 {Done: Lucas Nussbaum } [src:apertium-es-gl]
apertium-es-gl: FTBFS: mkdir: cannot create directory
‘/<>/debian/apertium-es-gl/usr/share/apertium/modes/’: No such
file or directory
Bug reopened
Ignoring request to
Source: libtexttools
Version: 2.1.0-16
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory
Source: ruby-mail-room
Version: 0.10.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error:
>
Source: wala
Version: 1.5.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
Source: haskell-gi-pango
Version: 1.0.19-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> test
Source: wacomtablet
Version: 3.2.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory
>
Source: node-tippex
Version: 3.0.0+ds-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: freeboard
Version: 1.1.0+dfsg.1-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules
reopen 954620
thanks
On 22/03/20 at 14:21 +0100, Lucas Nussbaum wrote:
> Hi,
>
> I'm closing those bugs: those failures are no longer reproducible,
> checking again 12 hours later. Either they were caused by another
> package that was fixed in the meantime, or they are random failures.
This is
Source: libgaminggear
Version: 0.15.1-9
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd
Source: python-geotiepoints
Version: 1.1.8-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: anet
Version: 0.4.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
Source: python-pymeasure
Version: 0.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory
Source: libncursesada
Version: 6.1.20180127-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> checking for
Source: ruby-fakeredis
Version: 0.7.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> ArgumentError:
>
Source: libflorist
Version: 2017-7
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
Source: ruby-slim
Version: 4.0.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> LoadError: cannot load such file
Source: golang-github-vbatts-go-mtree
Version: 0.4.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules
Source: birdfont
Version: 2.28.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
Source: wine-development
Version: 5.5-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> checking for
Source: expeyes
Version: 4.7.6+repack-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory
Source: libcatmandu-filestore-perl
Version: 1.13-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
Source: cinnamon-control-center
Version: 4.4.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> checking for
Source: lemonldap-ng
Version: 2.0.7+ds-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory
Source: python-apptools
Version: 4.5.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory
Source: txtorcon
Version: 19.0.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
Source: adabrowse
Version: 4.0.3-12
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
Source: ahven
Version: 2.7-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory
Source: dbusada
Version: 0.5.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
Source: python-peakutils
Version: 1.3.3+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: ofxstatement-plugins
Version: 20191114
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: influxdb-python
Version: 5.2.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh
Source: adacgi
Version: 1.6-24
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
Source: libalog
Version: 0.6.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
Source: python-biom-format
Version: 2.1.8+dfsg-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: rdkit
Version: 201909.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory
Source: drms
Version: 0.5.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with
Source: ufo2ft
Version: 2.12.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
Source: libinput
Version: 1.15.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
Source: mender-client
Version: 2.2.0-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory
Source: dvdbackup
Version: 0.4.2-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I..
Source: diffoscope
Version: 138
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: tripwire
Version: 2.4.3.7-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[4]: Entering directory '/<>'
Source: python-tablib
Version: 0.13.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory
Source: python-cobra
Version: 0.14.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build
Source: nordugrid-arc
Version: 6.5.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[7]: Entering directory
Source: libxmlezout
Version: 1.06.2-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory
Source: pangox-compat
Version: 0.0.2-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /bin/bash ./libtool --tag=CC
Source: liblog4ada
Version: 1.3.1.b6dafb49-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering
Source: seqsero
Version: 1.0.1+dfsg-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
Source: pynwb
Version: 1.2.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200402 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with
Package: src:gcc-9
Followup-For: Bug #954681
Control: reopen -1
Hello.
The initial symptom is cured, but the fix lets
debian/patches/ada-lib-info-source-date-epoch.diff modify
gcc/ada/libgnat/s-os_lib.ad[bs].
This invalidates the checksums embedded in the .ali files of
libgnat-9, causing a
Processing control commands:
> reopen -1
Bug #954681 {Done: Matthias Klose } [src:gcc-9] [gnat-9] crash
caused by SOURCE_DATE_EPOCH patch
'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
Source: qevercloud
Version: 3.0.3+ds-5
Severity: serious
Tags: ftbfs
This essentially is a duplicate of #921297. That bug was reassigned to
texlive-latex-extra and it was resolved by having texlive-latex-extra
now recommend texlive-plain-generic. However, Build-Depends don't care
for Recommends.
Hi Alex,
On Fri, Apr 03, 2020 at 05:21:57PM +0100, Alex Dewar wrote:
> Maybe try patching configure.ac so it looks for opencv4 rather than
> opencv. I'd like to also address this in my PR, only I'm not sure how to
> get autotools to look for opencv4 OR opencv without failing... Any ideas?
Please
Source: r-cran-uwot
Version: 0.1.8-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of r-cran-uwot the autopkgtest of r-cran-uwot fails
in testing when that autopkgtest is run with the
Source: rss-bridge
Version: 2020-02-26+dfsg1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of rss-bridge the autopkgtest of rss-bridge fails
in testing when that autopkgtest is run with
Processing commands for cont...@bugs.debian.org:
> tags 954244 + ftbfs
Bug #954244 [src:mpich] mpich FTBFS on armel, armhf, i386, mipsel: static
assertion failed: "MPL_COMPILE_TIME_ASSERT failure"
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
On Fri, Apr 03, 2020 at 07:58:03PM +0200, Paul Gevers wrote:
> Hi Antonio,
>
> On 03-04-2020 15:38, Antonio Terceiro wrote:
> >> Bundle complete! 19 Gemfile dependencies, 77 gems now installed.
> >> Use `bundle info [gemname]` to see where a bundled gem is installed.
> >> + bundle exec rake
Hi Antonio,
On 03-04-2020 15:38, Antonio Terceiro wrote:
>> Bundle complete! 19 Gemfile dependencies, 77 gems now installed.
>> Use `bundle info [gemname]` to see where a bundled gem is installed.
>> + bundle exec rake assets:precompile
>> rake aborted!
>> TypeError: no implicit conversion of
Package: python-pykka
Severity: serious
Tags: sid bullseye patch
User: debian-pyt...@lists.debian.org
Usertags: py2removal
the package still build-depends on python-doc, while it depends on python3 for
everything else.
patch at
Your message dated Fri, 03 Apr 2020 17:06:52 +
with message-id
and subject line Bug#937596: fixed in python-babel 2.8.0+dfsg.1-3
has caused the Debian Bug report #937596,
regarding python-babel: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 03 Apr 2020 16:50:17 +
with message-id
and subject line Bug#937459: fixed in pyinotify 0.9.6-1.3
has caused the Debian Bug report #937459,
regarding pyinotify: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 03 Apr 2020 16:34:56 +
with message-id
and subject line Bug#813821: fixed in pynn 0.9.5-2
has caused the Debian Bug report #813821,
regarding pynn: FTBFS: TypeError: 'float' object cannot be interpreted as an
index
to be marked as done.
This means that you claim that
Hi,
On Fri, Apr 3, 2020 at 4:21 PM Boyuan Yang wrote:
>
> Hi,
>
> 在 2020-04-02星期四的 16:53 +0100，Sudip Mukherjee写道：
> > X-Debbugs-CC: by...@debian.org
> >
> > I can reproduce the problem when I have kernelshark open without any
> > trace file. But the error is not seen if the trace file is opened
Control: tags 937459 + patch
Dear maintainer,
I've prepared an NMU for pyinotify (versioned as 0.9.6-1.3). The diff
is attached to this message.
Regards.
diff -Nru pyinotify-0.9.6/debian/changelog pyinotify-0.9.6/debian/changelog
--- pyinotify-0.9.6/debian/changelog 2019-08-07
Processing control commands:
> tags 937459 + patch
Bug #937459 [src:pyinotify] pyinotify: Python2 removal in sid/bullseye
Added tag(s) patch.
--
937459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 3 Apr 2020 11:44:07 -0400
with message-id
and subject line Re: jcc: Python2 removal in sid/bullseye
has caused the Debian Bug report #936761,
regarding jcc: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Hi,
在 2020-04-02星期四的 16:53 +0100，Sudip Mukherjee写道：
> X-Debbugs-CC: by...@debian.org
>
> I can reproduce the problem when I have kernelshark open without any
> trace file. But the error is not seen if the trace file is opened
> using kernelshark (which is the normal usecase).
>
> Can you
Dear s3cmd maintainer,
I have successfully been able to reproduce this issue with a basic setup. I
forked the current source on salsa and committed a working patch [0] based
on the upstream fix [1].
User "jrtc27" #debian-mentors suggested I use the actual patch from [2]
instead of my own. They
1 - 100 of 135 matches
Mail list logo
