Package: monit
Version: 1:5.20.0-6
Severity: grave
Dear maintainers,
Many thanks for the packaging of this application on Debian Gnu/Linux.
It seems there is one dependancy change (?) on recent monit Buster 10.2.
As a result, it is not more possible to install monit Debian package
on Buster
Your message dated Wed, 05 Feb 2020 03:04:39 +
with message-id
and subject line Bug#842882: fixed in jp2a 1.0.8-1
has caused the Debian Bug report #842882,
regarding jp2a: Version 1.0.7 improper to be released
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> forwarded 938746
> https://git.launchpad.net/ufw/commit/?id=0074e3c44ff122bd320d0d631e68e8964d293557
Bug #938746 [src:ufw] ufw: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to
Your message dated Wed, 05 Feb 2020 00:55:46 +
with message-id
and subject line Bug#937525: Removed package(s) from unstable
has caused the Debian Bug report #937525,
regarding RM: pyro -- removal triggered by the Python2 removal
to be marked as done.
This means that you claim that the
Your message dated Wed, 05 Feb 2020 00:54:20 +
with message-id
and subject line Bug#950658: Removed package(s) from unstable
has caused the Debian Bug report #921384,
regarding node-stringprep breaks node-xmpp autopkgtest
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 05 Feb 2020 00:51:42 +
with message-id
and subject line Bug#950515: Removed package(s) from unstable
has caused the Debian Bug report #896206,
regarding python-sciscipy: scilab fails to import
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 05 Feb 2020 00:51:42 +
with message-id
and subject line Bug#950515: Removed package(s) from unstable
has caused the Debian Bug report #884535,
regarding sciscipy FTBFS with scilab 6.0.0-1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 05 Feb 2020 00:51:42 +
with message-id
and subject line Bug#950515: Removed package(s) from unstable
has caused the Debian Bug report #938445,
regarding sciscipy: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 05 Feb 2020 00:47:56 +
with message-id
and subject line Bug#949859: Removed package(s) from unstable
has caused the Debian Bug report #949859,
regarding RM: google-apputils-python -- RoQA; leaf package; deprecated
upstream; RC buggy
to be marked as done.
This means
Your message dated Wed, 05 Feb 2020 00:49:04 +
with message-id
and subject line Bug#950445: Removed package(s) from unstable
has caused the Debian Bug report #950445,
regarding RM: python-couchdb -- RoQA; python2-only; leaf package; deprecated
upstream
to be marked as done.
This means that
Your message dated Wed, 05 Feb 2020 00:47:31 +
with message-id
and subject line Bug#946602: Removed package(s) from unstable
has caused the Debian Bug report #950064,
regarding pyxb FTBFS with Python 3.8 as supported version
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 05 Feb 2020 00:48:03 +
with message-id
and subject line Bug#949859: Removed package(s) from unstable
has caused the Debian Bug report #899527,
regarding google-apputils-python: Invalid maintainer address
cloud-packa...@lists.alioth.debian.org
to be marked as done.
Your message dated Wed, 05 Feb 2020 00:48:03 +
with message-id
and subject line Bug#949859: Removed package(s) from unstable
has caused the Debian Bug report #936637,
regarding google-apputils-python: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Wed, 05 Feb 2020 00:49:10 +
with message-id
and subject line Bug#950445: Removed package(s) from unstable
has caused the Debian Bug report #937664,
regarding python-couchdb: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 05 Feb 2020 00:48:38 +
with message-id
and subject line Bug#950436: Removed package(s) from unstable
has caused the Debian Bug report #937393,
regarding pyblosxom: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 05 Feb 2020 00:47:31 +
with message-id
and subject line Bug#946602: Removed package(s) from unstable
has caused the Debian Bug report #933483,
regarding python3-pyxb: missing Breaks+Replaces: python-pyxb
to be marked as done.
This means that you claim that the problem
Package: python3-seaborn
Version: 0.9.0-2
Severity: serious
Found during statsmodels transition testing, but also occurs without
statsmodels. I have not investigated further.
__ TestFacetGrid.test_set_ticklabels
___
self =
def
Processing commands for cont...@bugs.debian.org:
> severity 950637 normal
Bug #950637 [src:xtables-addons] update build-dep on iptables-dev
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950637:
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
Your message dated Tue, 04 Feb 2020 21:36:27 +
with message-id
and subject line Bug#950688: fixed in boost1.71 1.71.0-6
has caused the Debian Bug report #950688,
regarding boost1.71: python autopkgtest fails
to be marked as done.
This means that you claim that the problem has been dealt
On Sat, Feb 01, 2020 at 08:51:08PM +0100, Salvatore Bonaccorso wrote:
> Hi Hilko,
>
> On Sat, Feb 01, 2020 at 12:57:27AM +0100, Hilko Bengen wrote:
> > * Moritz Mühlenhoff:
> >
> > >> FTR, this was as well raised back in [1]. AFAIK there was no direct
> > >> feedback to the question from Moritz
Your message dated Tue, 04 Feb 2020 20:46:45 +
with message-id
and subject line Bug#949081: fixed in wget2 1.99.1-2.1
has caused the Debian Bug report #949081,
regarding wget2 FTBFS: makeinfo: command not found
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 04 Feb 2020 20:46:13 +
with message-id
and subject line Bug#950640: fixed in pycdio 2.1.0-1
has caused the Debian Bug report #950640,
regarding pycdio FTBFS with more than one supported python3 version
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 04 Feb 2020 20:44:18 +
with message-id
and subject line Bug#950389: fixed in glibc 2.29-10
has caused the Debian Bug report #950389,
regarding libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole
system
to be marked as done.
This means that you claim
Your message dated Tue, 04 Feb 2020 20:44:18 +
with message-id
and subject line Bug#946599: fixed in glibc 2.29-10
has caused the Debian Bug report #946599,
regarding libc6 s390x preinstall script fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 04 Feb 2020 20:44:18 +
with message-id
and subject line Bug#950389: fixed in glibc 2.29-10
has caused the Debian Bug report #950389,
regarding libc6 s390x preinstall script fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 04 Feb 2020 20:44:18 +
with message-id
and subject line Bug#946599: fixed in glibc 2.29-10
has caused the Debian Bug report #946599,
regarding libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole
system
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> found 950512 0.3-4
Bug #950512 [src:quotecolors] quotecolors: not usable anymore with TB>= 68.x
Marked as found in versions quotecolors/0.3-4.
> fixed 950535 1.8.3-2
Bug #950535 [iptables] iptables-restore segfaults on nat table
Marked as fixed
Processing commands for cont...@bugs.debian.org:
> tags 947034 + pending
Bug #947034 [src:python-passlib] Fails to build with python3.8
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947034:
Your message dated Tue, 04 Feb 2020 19:35:28 +
with message-id
and subject line Bug#949939: fixed in custodia 0.6.0-5
has caused the Debian Bug report #949939,
regarding custodia build depends on the removed pep8 transitional package
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #946599 [libc6] libcrypt1: failure to switch from libc6 to libcrypt1 hoses
the whole system
Bug #950389 [libc6] libc6 s390x preinstall script fails
Added tag(s) pending.
Added tag(s) pending.
--
946599:
Control: tag -1 pending
Hello,
Bug #946599 in glibc 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 commands for cont...@bugs.debian.org:
> forcemerge 950389 946599
Bug #950389 [libc6] libc6 s390x preinstall script fails
Bug #946599 [libc6] libcrypt1: failure to switch from libc6 to libcrypt1 hoses
the whole system
Severity set to 'grave' from 'important'
Marked as found in versions
Processing commands for cont...@bugs.debian.org:
> merge 950389 946599
Bug #950389 [libc6] libc6 s390x preinstall script fails
Unable to merge bugs because:
severity of #946599 is 'important' not 'grave'
Failed to merge 950389: Did not alter merged bugs.
> thanks
Stopping processing here.
Your message dated Tue, 04 Feb 2020 18:50:59 +
with message-id
and subject line Bug#892558: fixed in ruby-rspec-puppet 2.7.8-1
has caused the Debian Bug report #892558,
regarding ruby-rspec-puppet FTBFS with Ruby 2.5
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> severity 893735 important
Bug #893735 [src:paraview] paraview FTBFS on armel/armhf:
QVTKOpenGLWidget.cxx:458:3: error: 'QOpenGLFunctions_3_2_Core' was not declared
in this scope
Severity set to 'important' from 'serious'
> thanks
Stopping
Source: boost1.71
Version: 1.71.0-5
Severity: serious
The boost1.71 python autopkgtest fails with cmake >= 3.16 because the python
include path isn't added correctly.
In debian/tests/srcs/python/CMakeLists.txt the variable Python_INCLUDE_DIR
is used but the correct variable is
Processing commands for cont...@bugs.debian.org:
> notfound 950677 211
Bug #950677 [src:pglogical-ticker] pglogical-ticker FTBFS with PostgreSQL 12
The source 'pglogical-ticker' and version '211' do not appear to match any
binary packages
No longer marked as found in versions
Processing commands for cont...@bugs.debian.org:
> block 950677 with 948942
Bug #950677 [src:pglogical-ticker] pglogical-ticker FTBFS with PostgreSQL 12
950677 was not blocked by any bugs.
950677 was not blocking any bugs.
Added blocking bug(s) of 950677: 948942
> thanks
Stopping processing here.
Control: tag -1 pending
Hello,
Bug #892558 in ruby-rspec-puppet 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 #892558 [src:ruby-rspec-puppet] ruby-rspec-puppet FTBFS with Ruby 2.5
Added tag(s) pending.
--
892558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
I cannot build pglogical-ticker for postgres 12 because it depends on
pglogical, which is still not available for postgres 12.
Thank you,
*Jeremy Finzel*
*Database Administrator Tech Lead*
*M* 630-777-4520
On Tue, Feb 4, 2020 at 11:15 AM Adrian Bunk wrote:
> Source: pglogical-ticker
>
Source: coccinelle
Version: 1.0.4.deb-3
Hi everybody,
This issue was forward to upstream [1].
The dependency will be remove from coccinelle soon
[1] https://systeme.lip6.fr/pipermail/cocci/2020-February/006836.html
Cheers,
eamanu
Your message dated Tue, 04 Feb 2020 18:04:20 +
with message-id
and subject line Bug#949981: fixed in budgie-extras 0.92.0-2
has caused the Debian Bug report #949981,
regarding budgie-extras: Build-Depends on pep8 which has been removed
to be marked as done.
This means that you claim that the
Hi Tianon (2020.02.04_17:18:33_+)
> I'm hoping to get 0.18.0 packaged soon, which (as you mentioned)
> should make this moot, but I don't see any harm in getting a fix in
> sooner (really, feel free to skip DELAYED entirely if you want to get
> this fixed faster).
Thanks, rescheduled to 0.
On Tue, 4 Feb 2020 at 08:57, Stefano Rivera wrote:
> I've prepared an NMU for hy (versioned as 0.17.0-1.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should delay it longer.
Nice, I think this is perfectly reasonable, thanks!
I'm hoping to get 0.18.0 packaged soon, which
Your message dated Tue, 04 Feb 2020 17:20:48 +
with message-id
and subject line Bug#950594: fixed in flang 20190329-5
has caused the Debian Bug report #950594,
regarding flang FTBFS: dwz: Too many DIEs, not optimizing
to be marked as done.
This means that you claim that the problem has been
Source: pglogical-ticker
Version: 211
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pglogical-ticker.html
...
fakeroot debian/rules clean
pg_buildext checkcontrol
--- debian/control 2019-09-12 03:21:00.0 -1200
+++
Source: s3ql
Version: 3.3.2+dfsg-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/s3ql.html
...
fakeroot debian/rules clean
dh clean --with python3,sphinxdoc
dh: error: unable to load addon python3: Can't locate
clone 943423 -1
reassign -1 doxygen
retitle -1 doxygen-latex is now useless, should be removed from the archive?
block 943423 by -1
thanks
On 2019-11-05 20:54, Aurelien Jarno wrote:
> tag 943423 + moreinfo
>
> Hi,
>
> On 2019-10-24 18:59, Paolo Greppi wrote:
> > Package: libccfits-doc
> >
Processing commands for cont...@bugs.debian.org:
> clone 943423 -1
Bug #943423 [src:ccfits] libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from
experimental)
Bug 943423 cloned as bug 950675
> reassign -1 doxygen
Bug #950675 [src:ccfits] libccfits-doc: FTBFS with doxygen 1.8.16-1~exp3 from
Processing control commands:
> tags 950672 + pending
Bug #950672 [src:hy] FTBFS: Tests fail with Python 3.8
Added tag(s) pending.
--
950672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 950672 + pending
Dear maintainer,
I've prepared an NMU for hy (versioned as 0.17.0-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
SR
diff -Nru hy-0.17.0/debian/changelog hy-0.17.0/debian/changelog
---
Processing commands for cont...@bugs.debian.org:
> found 946289 1.8.4-1
Bug #946289 {Done: Arturo Borrero Gonzalez } [iptables] ufw:
fails to start with iptables 1.8.4
Marked as found in versions iptables/1.8.4-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Tue, 04 Feb 2020 16:35:05 +
with message-id
and subject line Bug#950581: fixed in python-django 2:2.2.10-1
has caused the Debian Bug report #950581,
regarding python-django: CVE-2020-7471: Potential SQL injection via
StringAgg(delimiter)
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> reassign 943451 src:ppl 1:1.2-7
Bug #943451 [libppl-doc] libppl-doc: FTBFS with doxygen 1.8.16-1~exp3 from
experimental
Bug reassigned from package 'libppl-doc' to 'src:ppl'.
No longer marked as found in versions ppl/1:1.2-7.
Ignoring request to
Control: tag -1 pending
Hello,
Bug #950581 in python-django 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 #950581 [src:python-django] python-django: CVE-2020-7471: Potential SQL
injection via StringAgg(delimiter)
Added tag(s) pending.
--
950581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950581
Debian Bug Tracking System
Contact
Your message dated Tue, 04 Feb 2020 16:20:15 +
with message-id
and subject line Bug#950660: fixed in python-pyproj 2.4.2+ds-3
has caused the Debian Bug report #950660,
regarding python-pyproj FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> retitle 950662 pybel FTBFS: test failures
Bug #950662 {Done: Adrian Bunk } [src:pybel] pybel FTBFS; test
failures
Changed Bug title to 'pybel FTBFS: test failures' from 'pybel FTBFS; test
failures'.
> thanks
Stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
> tags 950662 + ftbfs
Bug #950662 {Done: Adrian Bunk } [src:pybel] pybel FTBFS: test
failures
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950662:
Source: node-terser
Version: 4.1.2-4
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-terser.html
...
231 passing (47s)
4 pending
7 failing
1) bin/uglifyjs (2)
Should dump AST as JSON:
Uncaught Command failed:
Your message dated Tue, 04 Feb 2020 15:20:58 +
with message-id
and subject line Bug#950101: fixed in python-xarray 0.15.0-1
has caused the Debian Bug report #950101,
regarding python-xarray-doc: FTBFS with new ipython
to be marked as done.
This means that you claim that the problem has been
Source: empy
Version: 3.3.2-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/empy.html
...
install -m 755
/build/1st/empy-3.3.2/debian/python-empy/usr/lib/python2.*/dist-packages/em.py
/build/1st/empy-3.3.2/debian/python-empy/usr/bin/empy
Your message dated Tue, 04 Feb 2020 15:19:36 +
with message-id
and subject line Bug#950579: fixed in gcc-10 10-20200204-1
has caused the Debian Bug report #950579,
regarding libgcc1: multiple packages FTBFS on s390x: /usr/bin/ld: cannot find
-lgcc_s
to be marked as done.
This means that you
Source: pybel
Version: 0.12.1-1
Severity: serious
Tags: ftbgs bullseye sid
Control: close -1 0.13.1-1
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pybel.html
...
==
FAIL: test_gmod_unabbreviated
Processing control commands:
> close -1 0.13.1-1
Bug #950662 [src:pybel] pybel FTBFS; test failures
Marked as fixed in versions pybel/0.13.1-1.
Bug #950662 [src:pybel] pybel FTBFS; test failures
Marked Bug as done
--
950662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950662
Debian Bug
Source: python-pyproj
Version: 2.4.2+ds-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pyproj.html
...
=== FAILURES ===
__ test_datum
Source: pytest-bdd
Version: 3.1.1-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pytest-bdd.html
...
dh_auto_test -- --system=custom --test-args="{interpreter} -m pytest"
I: pybuild base:217: python3.8 -m pytest
Traceback (most recent call
Your message dated Tue, 04 Feb 2020 15:04:29 +
with message-id
and subject line Bug#950628: fixed in cryptsetup 2:2.2.2-3
has caused the Debian Bug report #950628,
regarding cryptsetup-initramfs: can't unlock argon2 keyslots: incompatible with
libgcc1 1:10-20200202-1
to be marked as done.
Source: python-deeptoolsintervals
Version: 0.1.9-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-deeptoolsintervals.html
...
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g
Your message dated Tue, 4 Feb 2020 15:51:52 +0100
with message-id
and subject line node-sinon requires node-array-from
has caused the Debian Bug report #950422,
regarding node-sinon: (build-)depends on node-array-from which has been
requested to be removed
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> notfound 950540 1.9.8-2
Bug #950540 [haveged] System hangs at startup
No longer marked as found in versions haveged/1.9.8-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950540:
Processing commands for cont...@bugs.debian.org:
> found 950540 1.9.8-3
Bug #950540 [haveged] System hangs at startup
Marked as found in versions haveged/1.9.8-3.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950540:
Your message dated Tue, 04 Feb 2020 14:43:18 +
with message-id
and subject line Bug#950657: fixed in node-eslint-plugin-flowtype 2.25.0-2
has caused the Debian Bug report #950657,
regarding node-eslint-plugin-flowtype: needed files not built
to be marked as done.
This means that you claim
Your message dated Tue, 04 Feb 2020 14:41:47 +
with message-id
and subject line Bug#947563: fixed in glob2 0.9.4.4-3
has caused the Debian Bug report #947563,
regarding FTBFS with scons 3.1.2-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Tue, 04 Feb 2020 14:41:25 +
with message-id
and subject line Bug#787350: fixed in fontmatrix 0.6.1+git20190730-2
has caused the Debian Bug report #787350,
regarding [RC][cc-by-nc-sa] Please clarify license of a few svg files
to be marked as done.
This means that you claim
Your message dated Tue, 04 Feb 2020 14:43:56 +
with message-id
and subject line Bug#950339: fixed in powder 118+dfsg1-3
has caused the Debian Bug report #950339,
regarding src:powder: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 04 Feb 2020 14:44:03 +
with message-id
and subject line Bug#948418: fixed in pyrit 0.5.1+git20180801-2
has caused the Debian Bug report #948418,
regarding pyrit ftbfs in unstable
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> retitle 950628 cryptsetup-initramfs: can't unlock argon2 keyslots:
> incompatible with libgcc1 1:10-20200202-1
Bug #950628 [cryptsetup-initramfs] System with encrypted root unbootable
because initramfs hooks don't include libgcc located in /lib
Package: node-eslint-plugin-flowtype
Version: 2.25.0-1
Severity: serious
Package is unusable since files are not built during build
Package: node-copy-webpack-plugin
Version: 4.3.0-6
Followup-For: Bug #950568
This package depends on webpack-log which is not packaged.
Package: node-eslint-plugin-html
Version: 3.2.1-1
Severity: serious
This package seems unusable without eslint. See
https://ci.debian.net/data/autopkgtest/unstable/amd64/n/node-eslint-plugin-html/3801441/log.gz
Control: tag -1 pending
Hello,
Bug #948418 in pyrit 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 #948418 [src:pyrit] pyrit ftbfs in unstable
Added tag(s) pending.
--
948418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> block -1 by 950542 950545 950547 950549 950550
Bug #950652 [wnpp] ITP: gcc64 -- compiler host64 and target 32 with multilib
950652 was not blocked by any bugs.
950652 was not blocking any bugs.
Added blocking bug(s) of 950652: 950550, 950549, 950542, 950547, and
Package: gnome-books
Version: 3.31.90-3
Severity: serious
Justification: Policy 3.5
Dear Maintainer,
Trying to launch gnome-books from Xfce desktop it fails with
(org.gnome.Books:18574): GLib-GIO-ERROR **: 13:57:13.838: Settings schema
'org.freedesktop.Tracker.Miner.Files' is not installed
Processing commands for cont...@bugs.debian.org:
> # fix title
> retitle 937525 RM: pyro -- removal triggered by the Python2 removal
Bug #937525 [ftp.debian.org] RM: PKG -- removal triggered by the Python2 removal
Changed Bug title to 'RM: pyro -- removal triggered by the Python2 removal'
from
Source: pymupdf
Version: 1.14.16-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=pymupdf
...
fitz/fitz_wrap.c:4630:28: error: ‘FZ_ERROR_TRYLATER’ undeclared (first use in
this function); did you mean ‘FZ_ERROR_SYNTAX’?
...
Hi,
As the 'pyro' maintainer, it should be removed from debian/unstable.
Its only rdep is 'cylc', and the latest version of cylc (unstable) does
not use pyro; pyro is already removed from testing.
(cylc is awaiting a full new release that will be python3 clean, that
version (due now) will
Processing commands for cont...@bugs.debian.org:
> reassign 937525 ftp.debian.org
Bug #937525 [src:pyro] pyro: Python2 removal in sid/bullseye
Bug reassigned from package 'src:pyro' to 'ftp.debian.org'.
No longer marked as found in versions pyro/1:3.16-3.
Ignoring request to alter fixed versions
Source: pycdio
Version: 2.0.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=pycdio
...
creating build/temp.linux-arm64-3.8/swig
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
Source: pykwalify
Version: 1.7.0-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pykwalify.html
...
=== FAILURES ===
___
Source: xtables-addons
Version: 3.7-1
Severity: serious
It seems xtables-addons build-deps on iptables-dev, which no longer exists.
Please update the build-deps of xtables-addons. You probably need the
libxtables-dev package instead.
This is apparently preventing the migration of iptables from
Your message dated Tue, 04 Feb 2020 12:19:19 +
with message-id
and subject line Bug#950632: fixed in gcc-8 8.3.0-28
has caused the Debian Bug report #950632,
regarding gcc-8/8.3.0-27 binaries not built from 8.3.0-27 sources on s390x
to be marked as done.
This means that you claim that the
Package: morris
Version: 0.2-5
Severity: serious
Tags: ftbfs
Dear Maintainer,
boost1.71 has removed the deprecated signals library, thus morris
cannot be build against the upcoming boost ABI.
Given how old the libraries it uses are, maybe we should even remove
morris from the archive, as it is
Source: gcc-8
Version: 8.3.0-27
Severity: serious
gcc-8/s390x has been manually uploaded to fix the breakage introduced
by gcc-10. However it has not been built from the 8.3.0-27 sources. At
least the changelog file is different from other architectures, causing
multiarch co-installability
Package: cryptsetup-initramfs
Version: 2:2.2.2-2
Severity: critical
The side effect of initramfs logic used to find libgcc leads to
unbootable system if libgcc is in different location than libc. Maybe
something like "ldconfig -p | grep libgcc_s.so.1" should be used to
locate libgcc instead?
Package: libgcc-s1
Version: 10-20200202-1
Severity: serious
On systems where /lib is a symlink to /usr/lib (which is the case for
every new buster installation, for instance), it can easily happen that
/usr/lib/$DEB_HOST_MUTIARCH/libgcc_s.so.1 disappears on upgrades. This
happens whenever
Processing commands for cont...@bugs.debian.org:
> tags 950622 + bullseye sid
Bug #950622 [src:python-sqt] python-sqt FTBFS with more than one supported
python3 version
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950622:
1 - 100 of 104 matches
Mail list logo
