Bug#896528: libcpg-dev: missing dependency on libcorosync-common-dev

Package: libcpg-dev Version: 2.4.4-2 Severity: serious Control: affects -1 src:sbd https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/sbd.html ... gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/pacemaker -I/usr/include/heartbeat -I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/

Processed: libcpg-dev: missing dependency on libcorosync-common-dev

Processing control commands: > affects -1 src:sbd Bug #896528 [libcpg-dev] libcpg-dev: missing dependency on libcorosync-common-dev Added indication that 896528 affects src:sbd -- 896528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896528 Debian Bug Tracking System Contact ow...@bugs.debi

Processed: tagging 894277

Processing commands for cont...@bugs.debian.org: > tags 894277 + pending Bug #894277 [gitaly] gitaly is not configured and not starting with a custom configuration Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 894277: https://bugs.debian.o

Bug#896313: python-pymediainfo: pymediainfo fails to import

On Sat, Apr 21, 2018 at 08:05:53PM -0400, Antoine Beaupre wrote: > So I don't quite understand how this can possibly happen: setuptools is > required to build the package in the first place, why can't dh-python > figure that out on its own? Thank you for your attention to detail. I admit having l

Processed: found 891450 in 0.5.0-3

Processing commands for cont...@bugs.debian.org: > found 891450 0.5.0-3 Bug #891450 [custodia] custodia FTBFS: TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType Marked as found in versions custodia/0.5.0-3. > thanks Stopping processing here. Please contact me if

Bug#895776: This is a test email, please ignore

Sorry for the noise. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed

Bug#893050: pyopencl FTBFS: ModuleNotFoundError: No module named 'pyopencl'

Dear Tomasz, Please find attached the debdiff for an NMU that I have uploaded to DELAYED/5. In the absence of a working test suite for pyopencl, I've tested the packages with sasview which is an rdep of pyopencl. This NMU addresses both the FTBFS (#893050) and also the inability for the docume

Bug#896355: marked as done (python-ufl: ufl fails to import)

Your message dated Sun, 22 Apr 2018 04:34:52 + with message-id and subject line Bug#896355: fixed in ufl 2017.2.0.0-3 has caused the Debian Bug report #896355, regarding python-ufl: ufl fails to import to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#896278: marked as done (python3-ufl: ufl fails to import)

Your message dated Sun, 22 Apr 2018 04:34:52 + with message-id and subject line Bug#896278: fixed in ufl 2017.2.0.0-3 has caused the Debian Bug report #896278, regarding python3-ufl: ufl fails to import to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#896363: marked as done (python3-instant: instant fails to import)

Your message dated Sun, 22 Apr 2018 04:19:40 + with message-id and subject line Bug#896363: fixed in instant 2017.2.0.0-3 has caused the Debian Bug report #896363, regarding python3-instant: instant fails to import to be marked as done. This means that you claim that the problem has been deal

Bug#896415: marked as done (python-fiat: FIAT fails to import)

Your message dated Sun, 22 Apr 2018 04:19:30 + with message-id and subject line Bug#896415: fixed in fiat 2017.2.0.0-3 has caused the Debian Bug report #896415, regarding python-fiat: FIAT fails to import to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#896416: marked as done (python3-fiat: FIAT fails to import)

Your message dated Sun, 22 Apr 2018 04:19:30 + with message-id and subject line Bug#896416: fixed in fiat 2017.2.0.0-3 has caused the Debian Bug report #896416, regarding python3-fiat: FIAT fails to import to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#896318: marked as done (python-instant: instant fails to import)

Your message dated Sun, 22 Apr 2018 04:19:40 + with message-id and subject line Bug#896318: fixed in instant 2017.2.0.0-3 has caused the Debian Bug report #896318, regarding python-instant: instant fails to import to be marked as done. This means that you claim that the problem has been dealt

Bug#884134: marked as done (rpy: do not ship with buster)

Your message dated Sun, 22 Apr 2018 04:12:05 + with message-id and subject line Bug#896283: Removed package(s) from unstable has caused the Debian Bug report #884134, regarding rpy: do not ship with buster to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#896397: marked as done (python-casmoothing: ca_smoothing fails to import)

Your message dated Sun, 22 Apr 2018 04:04:56 + with message-id and subject line Bug#895877: Removed package(s) from unstable has caused the Debian Bug report #896397, regarding python-casmoothing: ca_smoothing fails to import to be marked as done. This means that you claim that the problem ha

Bug#674107: marked as done (mx: Consider dropping libcluttergesture-dev build-depends)

Your message dated Sun, 22 Apr 2018 03:58:42 + with message-id and subject line Bug#895796: Removed package(s) from unstable has caused the Debian Bug report #674107, regarding mx: Consider dropping libcluttergesture-dev build-depends to be marked as done. This means that you claim that the p

Bug#811306: marked as done (FTBFS: mmpong-gl-data missing files: usr/share/games/mmpong-gl)

Your message dated Sun, 22 Apr 2018 03:58:07 + with message-id and subject line Bug#895780: Removed package(s) from unstable has caused the Debian Bug report #811306, regarding FTBFS: mmpong-gl-data missing files: usr/share/games/mmpong-gl to be marked as done. This means that you claim that

Bug#889271: marked as done (lua-sandbox-extensions-dev is empty)

Your message dated Sun, 22 Apr 2018 03:56:40 + with message-id and subject line Bug#891192: Removed package(s) from unstable has caused the Debian Bug report #889271, regarding lua-sandbox-extensions-dev is empty to be marked as done. This means that you claim that the problem has been dealt

Bug#871094: marked as done (openhackware: FTBFS: src/bloc.c:1251:18: error: this statement may fall through [-Werror=implicit-fallthrough=])

Your message dated Sun, 22 Apr 2018 03:04:08 + with message-id and subject line Bug#871094: fixed in openhackware 0.4.1+git-20140423.c559da7c-4.1 has caused the Debian Bug report #871094, regarding openhackware: FTBFS: src/bloc.c:1251:18: error: this statement may fall through [-Werror=impli

Bug#893604: mumble: Add support to build with upcoming Ice 3.7.0 release

Jose Gutierrez de la Concha: [...] > With Ice 3.7.0 IceUtil library was removed, I fixed the .pro file to not > longer include it in the link libraries, you might want to check Ice > Version < 3.7 and add it, but I'm not sure what is the best way to do this > check with qmake. Probably it is better

Bug#896454: gfal2 FTBFS with googletest >= 1.8.0-7

On Saturday, April 21, 2018 3:44:49 AM CDT you wrote: > make[1]: Entering directory '/build/1st/gfal2-2.15.4' > dh_missing --fail-missing > dh_missing: usr/lib/x86_64-linux-gnu/libgtest_main.a exists in debian/tmp > but is not installed to anywhere dh_missing: > usr/lib/x86_64-linux-gnu/libgtest.a

Bug#896453: davix FTBFS with googletest >= 1.8.0-7

The googletest binaries now use the "triplet" library path, so the rules need adjusting from rm debian/tmp/usr/lib/libgtest.a rm debian/tmp/usr/lib/libgtest_main.a to something like rm debian/tmp/usr/lib/*/libgtest.a rm debian/tmp/usr/lib/*/libgtest_main.a -Steve s

Bug#896467: nfstrace FTBFS with TeX Live 2018

Well, it is in fact good, because before these words were ignored and pieces were missing in the output I guess, which is even worse ;-) Best Norbert On April 22, 2018 12:24:54 AM GMT+09:00, Adrian Bunk wrote: >On Sun, Apr 22, 2018 at 12:14:33AM +0900, Norbert Preining wrote: >> > It always w

Bug#896071: debootstrap fails to retrive Release file over https

On 21 April 2018 at 21:32, Hideki Yamane wrote: > > Thanks for the report, and here's a proposal fix. > > [ ! "$VERBOSE" ] && NVSWITCH="-nv" > local ret=0 > if [ "$USE_DEBIANINSTALLER_INTERACTION" ] && [ "$PROGRESS_NEXT" ]; > then > - wget "$@" 2>&1 >/dev/nu

Processed: Re: Bug#891450: custodia FTBFS: TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType

Processing control commands: > reassign -1 custodia Bug #891450 [python-coverage] custodia FTBFS: TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType Bug reassigned from package 'python-coverage' to 'custodia'. No longer marked as found in versions python-coverage/

Bug#896313: python-pymediainfo: pymediainfo fails to import

On Fri, Apr 20, 2018 at 10:01:07PM +0200, Helmut Grohne wrote: > After installing python-pymediainfo importing the module pymediainfo > into a python interpreter fails with the following error: > > Traceback (most recent call last): > File "", line 1, in > File "/usr/lib/python2.7/dist-packag

Bug#893697:

> What's the status of the updated package to fix the missing dependency? new upstream release of networkx requires several new dependencies to be added, and it takes time to pass them thru NEW. -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroT

Bug#896517: python-ccnet: missing Breaks+Replaces: libccnet0 (<< 6.1.7)

Package: python-ccnet Version: 6.1.7-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other

Bug#889188: marked as done (haskell-misfortune is empty)

Your message dated Sat, 21 Apr 2018 23:34:51 + with message-id and subject line Bug#881657: fixed in haskell-misfortune 0.1.1.2-7 has caused the Debian Bug report #881657, regarding haskell-misfortune is empty to be marked as done. This means that you claim that the problem has been dealt wit

Bug#881657: marked as done (haskell-misfortune: No executable shipped, doh!)

Your message dated Sat, 21 Apr 2018 23:34:51 + with message-id and subject line Bug#881657: fixed in haskell-misfortune 0.1.1.2-7 has caused the Debian Bug report #881657, regarding haskell-misfortune: No executable shipped, doh! to be marked as done. This means that you claim that the proble

Bug#893697:

On Sat, 14 Apr 2018 17:25:47 -0400 Sandro Tosi wrote: Hello, > > this is also a problem in iva [1]. Patch attached — any comments? I don’t have too much experience with NMUs, would that be OK here? What delay would you recommend? > > please hold your NMU, i'll prepare the new upstream release

Processed: reassign 896235 to python3-networkx, forcibly merging 893697 896235

Processing commands for cont...@bugs.debian.org: > reassign 896235 python3-networkx 1.11-2 Bug #896235 [python3-setoolsgui] python3-setoolsgui: setoolsgui fails to import Bug reassigned from package 'python3-setoolsgui' to 'python3-networkx'. No longer marked as found in versions setools/4.1.1-3.

Processed (with 1 error): merging 896233 893697

Processing commands for cont...@bugs.debian.org: > merge 896233 893697 Bug #896233 [python3-networkx] python3-networkx: networkx fails to import Unable to merge bugs because: affects of #893697 is 'src:setools,setools,iva' not '' affects of #896235 is 'src:setools,setools,iva' not '' affects of #8

Processed: reassign 896302 to python3-networkx, forcibly merging 893697 896302

Processing commands for cont...@bugs.debian.org: > reassign 896302 python3-networkx 1.11-2 Bug #896302 [python3-setools] python3-setools: setools fails to import Bug reassigned from package 'python3-setools' to 'python3-networkx'. No longer marked as found in versions setools/4.1.1-3. Ignoring req

Processed: reassign 896212 to python3-networkx, forcibly merging 893697 896212

Processing commands for cont...@bugs.debian.org: > reassign 896212 python3-networkx 1.11-2 Bug #896212 [python3-sepolicy] python3-sepolicy: sepolicy fails to import Bug reassigned from package 'python3-sepolicy' to 'python3-networkx'. No longer marked as found in versions selinux-python/2.7-2. Ign

Bug#896502: marked as done (libxml-structured-perl: missing dependency on libxml-parser-perl)

Your message dated Sat, 21 Apr 2018 22:06:09 + with message-id and subject line Bug#896502: fixed in libxml-structured-perl 1.01-3 has caused the Debian Bug report #896502, regarding libxml-structured-perl: missing dependency on libxml-parser-perl to be marked as done. This means that you cla

Processed: Bug #896502 in libxml-structured-perl marked as pending

Processing control commands: > tag -1 pending Bug #896502 [libxml-structured-perl] libxml-structured-perl: missing dependency on libxml-parser-perl Added tag(s) pending. -- 896502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896502 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#896502: Bug #896502 in libxml-structured-perl marked as pending

Control: tag -1 pending Hello, Bug #896502 in libxml-structured-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/libxml-structur

Bug#896338: marked as done (python3-gribapi: gribapi fails to import)

Your message dated Sat, 21 Apr 2018 21:35:11 + with message-id and subject line Bug#896338: fixed in grib-api 1.26.1-1 has caused the Debian Bug report #896338, regarding python3-gribapi: gribapi fails to import to be marked as done. This means that you claim that the problem has been dealt w

Bug#896277: marked as done (python-gribapi: gribapi fails to import)

Your message dated Sat, 21 Apr 2018 21:35:11 + with message-id and subject line Bug#896277: fixed in grib-api 1.26.1-1 has caused the Debian Bug report #896277, regarding python-gribapi: gribapi fails to import to be marked as done. This means that you claim that the problem has been dealt wi

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 893039 ccnet/6.1.5-2 Bug #893039 {Done: Moritz Schlarb } [libccnet0] libccnet0: contains a python module The source ccnet and version 6.1.5-2 do not appear to match any binary packages Marked as fixed in versions ccnet/6.1.5-2. > fixed 8930

Bug#896497: marked as done (openimageio FTBFS with TeX Live 2018)

Your message dated Sat, 21 Apr 2018 21:21:16 + with message-id and subject line Bug#896497: fixed in openimageio 1.8.10~dfsg0-2 has caused the Debian Bug report #896497, regarding openimageio FTBFS with TeX Live 2018 to be marked as done. This means that you claim that the problem has been de

Bug#896200: marked as done (python-rviz: rviz fails to import)

Your message dated Sat, 21 Apr 2018 21:21:34 + with message-id and subject line Bug#896200: fixed in ros-rviz 1.12.4+dfsg-3 has caused the Debian Bug report #896200, regarding python-rviz: rviz fails to import to be marked as done. This means that you claim that the problem has been dealt wit

Bug#895512: marked as done (taskcoach FTBFS with wxpython3.0 3.0.2.0+dfsg-7)

Your message dated Sat, 21 Apr 2018 21:06:19 + with message-id and subject line Bug#895512: fixed in taskcoach 1.4.3-6 has caused the Debian Bug report #895512, regarding taskcoach FTBFS with wxpython3.0 3.0.2.0+dfsg-7 to be marked as done. This means that you claim that the problem has been

Bug#893989: marked as done (python3-neutron-vpnaas installation failure under puiparts.)

Your message dated Sat, 21 Apr 2018 21:02:59 + with message-id and subject line Bug#893989: fixed in neutron-vpnaas 2:12.0.0-2 has caused the Debian Bug report #893989, regarding python3-neutron-vpnaas installation failure under puiparts. to be marked as done. This means that you claim that t

Bug#896477: marked as done (qliss3d FTBFS: configure: error: *** Couldn't find any Qt libraries)

Your message dated Sat, 21 Apr 2018 21:03:57 + with message-id and subject line Bug#896477: fixed in qliss3d 1.4-4 has caused the Debian Bug report #896477, regarding qliss3d FTBFS: configure: error: *** Couldn't find any Qt libraries to be marked as done. This means that you claim that the p

Bug#892745: marked as done (python-os-testr FTBFS: test failure)

Your message dated Sat, 21 Apr 2018 21:03:36 + with message-id and subject line Bug#892745: fixed in python-os-testr 1.0.0-4 has caused the Debian Bug report #892745, regarding python-os-testr FTBFS: test failure to be marked as done. This means that you claim that the problem has been dealt

Bug#896461: marked as done (fig2dev should depend on ghostscript and netpbm (not only recommend them))

Your message dated Sat, 21 Apr 2018 20:54:24 + with message-id and subject line Bug#896461: fixed in fig2dev 1:3.2.7-3 has caused the Debian Bug report #896461, regarding fig2dev should depend on ghostscript and netpbm (not only recommend them) to be marked as done. This means that you claim

Processed: Re: Bug#896443: connectagram FTBFS with Qt 5.10

Processing commands for cont...@bugs.debian.org: > tags 896443 fixed-upstream Bug #896443 [src:connectagram] connectagram FTBFS with Qt 5.10 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 896443: https://bugs.debian.org/cgi-bin/bugrep

Processed: Re: Bug#891450: custodia FTBFS: TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType

Processing control commands: > severity -1 normal Bug #891450 [python-coverage] custodia FTBFS: TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType Severity set to 'normal' from 'serious' -- 891450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891450 Debian

Bug#891450: custodia FTBFS: TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType

Control: severity -1 normal On 25-Feb-2018, Adrian Bunk wrote: > Source: custodia > Version: 0.5.0-3 > Severity: serious This bug report affects only the upstream unit tests suite, and (as reported) shows no effect on the run-time use of the package. It does not meet the definition of the BTS “se

Bug#891450: custodia FTBFS: TypeError: stat: path should be string, bytes, os.PathLike or integer, not NoneType

On 25-Feb-2018, Adrian Bunk wrote: > Source: custodia I Think this is the correct assignment for this bug report. See the command-line used to invoke the coverage module: > ERROR: InvocationError: '/build/1st/custodia-0.5.0/.tox/py36/bin/python -m > coverage run --parallel -m pytest --capture=n

Bug#896507: qpid-proton: missing Breaks+Replaces and ships badly placed doc symlinks

Source: qpid-proton Version: 0.22.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at

Bug#896505: FTBFS: needs to be patched for newer feed API

Package: rss2irc Version: 1.1-3 Severity: serious Types have changed

Processed: Bug #892745 in python-os-testr marked as pending

Processing control commands: > tag -1 pending Bug #892745 [src:python-os-testr] python-os-testr FTBFS: test failure Ignoring request to alter tags of bug #892745 to the same tags previously set -- 892745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892745 Debian Bug Tracking System Contact

Bug#892745: Bug #892745 in python-os-testr marked as pending

Control: tag -1 pending Hello, Bug #892745 in python-os-testr 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/openstack-team/libs/python-os-testr/commit/9dfe7b

Processed: Bug #892745 in python-os-testr marked as pending

Processing control commands: > tag -1 pending Bug #892745 [src:python-os-testr] python-os-testr FTBFS: test failure Ignoring request to alter tags of bug #892745 to the same tags previously set -- 892745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892745 Debian Bug Tracking System Contact

Processed: Bug #892745 in python-os-testr marked as pending

Processing control commands: > tag -1 pending Bug #892745 [src:python-os-testr] python-os-testr FTBFS: test failure Added tag(s) pending. -- 892745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#892745: Bug #892745 in python-os-testr marked as pending

Control: tag -1 pending Hello, Bug #892745 in python-os-testr 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/openstack-team/libs/python-os-testr/commit/9dfe7b

Bug#892745: Bug #892745 in python-os-testr marked as pending

Control: tag -1 pending Hello, Bug #892745 in python-os-testr 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/openstack-team/libs/python-os-testr/commit/878567

Processed: Bug #893989 in neutron-vpnaas marked as pending

Processing control commands: > tag -1 pending Bug #893989 [python3-neutron-vpnaas] python3-neutron-vpnaas installation failure under puiparts. Ignoring request to alter tags of bug #893989 to the same tags previously set -- 893989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893989 Debian

Bug#896228: marked as done (python-nose-testconfig: testconfig fails to import)

Your message dated Sat, 21 Apr 2018 19:49:50 + with message-id and subject line Bug#896228: fixed in python-nose-testconfig 0.9-2 has caused the Debian Bug report #896228, regarding python-nose-testconfig: testconfig fails to import to be marked as done. This means that you claim that the pro

Bug#893989: Bug #893989 in neutron-vpnaas marked as pending

Control: tag -1 pending Hello, Bug #893989 in neutron-vpnaas 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/openstack-team/services/neutron-vpnaas/commit/772e

Bug#893989: Bug #893989 in neutron-vpnaas marked as pending

Control: tag -1 pending Hello, Bug #893989 in neutron-vpnaas 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/openstack-team/services/neutron-vpnaas/commit/772e

Processed: Bug #893989 in neutron-vpnaas marked as pending

Processing control commands: > tag -1 pending Bug #893989 [python3-neutron-vpnaas] python3-neutron-vpnaas installation failure under puiparts. Added tag(s) pending. -- 893989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893989 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Bug #896228 in python-nose-testconfig marked as pending

Processing control commands: > tag -1 pending Bug #896228 [python-nose-testconfig] python-nose-testconfig: testconfig fails to import Added tag(s) pending. -- 896228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#896228: Bug #896228 in python-nose-testconfig marked as pending

Control: tag -1 pending Hello, Bug #896228 in python-nose-testconfig 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/openstack-team/python/python-nose-testconf

Bug#896325: marked as done (python3-stringtemplate3: stringtemplate3 fails to import)

Your message dated Sat, 21 Apr 2018 21:33:09 +0200 with message-id <437c3adb-5a0d-97ed-8634-94fe5329e...@debian.org> and subject line Already fixed has caused the Debian Bug report #896325, regarding python3-stringtemplate3: stringtemplate3 fails to import to be marked as done. This means that you

Bug#876614: marked as done (libfm FTBFS with gtk-doc-tools 1.26: fm-module.xml:72: parser error : error parsing attribute name)

Your message dated Sat, 21 Apr 2018 19:36:01 + with message-id and subject line Bug#876614: fixed in libfm 1.3.0-1 has caused the Debian Bug report #876614, regarding libfm FTBFS with gtk-doc-tools 1.26: fm-module.xml:72: parser error : error parsing attribute name to be marked as done. This

Bug#896503: libx2go-server-db-perl: missing dependency on libx2go-server-perl

Package: libx2go-server-db-perl Version: 4.1.0.0-3 Severity: serious User: debian-p...@lists.debian.org Usertags: use-failure This package is missing a dependency on libx2go-server-perl: # perl -e 'use X2Go::Server::DB' Can't locate X2Go/Config.pm in @INC (you may need to install the X2Go::Co

Bug#896504: libx2go-log-perl: missing dependency on libx2go-server-perl

Package: libx2go-log-perl Version: 4.1.0.0-3 Severity: serious User: debian-p...@lists.debian.org Usertags: use-failure This package is missing a dependency on libx2go-server-perl: # perl -e 'use X2Go::Log' Can't locate X2Go/Config.pm in @INC (you may need to install the X2Go::Config module)

Bug#896316: marked as done (python3-ldappool: ldappool fails to import)

Your message dated Sat, 21 Apr 2018 21:21:16 +0200 with message-id <3854ab0a-da73-057c-dd0d-a955c4cce...@debian.org> and subject line Already fixed has caused the Debian Bug report #896316, regarding python3-ldappool: ldappool fails to import to be marked as done. This means that you claim that th

Bug#896502: libxml-structured-perl: missing dependency on libxml-parser-perl

Package: libxml-structured-perl Version: 1.01-2 Severity: serious User: debian-p...@lists.debian.org Usertags: use-failure This package is missing a dependency on libxml-parser-perl: # perl -e 'use XML::Structured' Can't locate XML/Parser.pm in @INC (you may need to install the XML::Parser mod

Bug#896201: marked as done (python3-traceback2: traceback2 fails to import)

Your message dated Sat, 21 Apr 2018 21:20:20 +0200 with message-id and subject line Already fixed has caused the Debian Bug report #896201, regarding python3-traceback2: traceback2 fails to import to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#896377: marked as done (python-traceback2: traceback2 fails to import)

Your message dated Sat, 21 Apr 2018 21:18:54 +0200 with message-id <4bd7264a-da72-7fd5-3bfc-893099e46...@debian.org> and subject line Already fixed has caused the Debian Bug report #896377, regarding python-traceback2: traceback2 fails to import to be marked as done. This means that you claim that

Bug#896501: libcrcutil FTBFS with TeX Live 2018

Source: libcrcutil Version: 1.0-4 Severity: serious Tags: patch buster sid https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcrcutil.html ... ! Package inputenc Error: Invalid UTF-8 byte 150. See the inputenc package documentation for explanation. Type H for immediate help

Bug#896500: libnet-whois-ripe-perl: Can't use 'defined(@array)'

Package: libnet-whois-ripe-perl Version: 1.23-2 Severity: grave Justification: renders package unusable User: debian-p...@lists.debian.org Usertags: use-failure perl-5.22-transition This Perl module seems to be unusable: # perl -e 'use Net::Whois::RIPE' Can't use 'defined(@array)' (Maybe you sh

Bug#896339: marked as done (python3-editor: editor fails to import)

Your message dated Sat, 21 Apr 2018 21:19:27 +0200 with message-id <85221e6b-c53c-9e53-f27d-5a49caeee...@debian.org> and subject line Already fixed has caused the Debian Bug report #896339, regarding python3-editor: editor fails to import to be marked as done. This means that you claim that the pr

Bug#896499: libopenscap-perl: Can't locate loadable object for module openscap_pm

Package: libopenscap-perl Version: 1.2.15-1 Severity: grave Justification: renders package unusable User: debian-p...@lists.debian.org Usertags: use-failure The Perl module in this package seems to be unusable: # perl -e 'use openscap' Can't locate loadable object for module openscap_pm in @I

Processed: bug 896313 is forwarded to https://github.com/sbraz/pymediainfo/pull/50

Processing commands for cont...@bugs.debian.org: > forwarded 896313 https://github.com/sbraz/pymediainfo/pull/50 Bug #896313 [python-pymediainfo] python-pymediainfo: pymediainfo fails to import Set Bug forwarded-to-address to 'https://github.com/sbraz/pymediainfo/pull/50'. > thanks Stopping proces

Bug#896497: openimageio FTBFS with TeX Live 2018

Source: openimageio Version: 1.8.10~dfsg0-1 Severity: serious Tags: patch https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openimageio.html ... ! Package inputenc Error: Unicode character ¨ (U+A8) (inputenc)not set up for use with LaTeX. See the inputenc package

Bug#896496: ganeti FTBFS with sphinx 1.7.2

Source: ganeti Version: 2.16.0~rc2-3 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ganeti.html ... checking for ip... /sbin/ip checking for pandoc... /usr/bin/pandoc checking for sphinx-build... /usr/bin/sphinx-build configure: error: Unable to determine Sph

Bug#876614: libfm FTBFS with gtk-doc-tools 1.26: fm-module.xml:72: parser error : error parsing attribute name

On Sat, Apr 21, 2018 at 06:50:05PM +0300, Andriy Grytsenko wrote: > Thank you for a NMU but that isn't needed, I think 1.3.0 will come pretty > soon where this issue is fixed. > Cheers! Sounds good, I have cancelled my NMU. cu Adrian -- "Is there not promise of rain?" Ling Tan asked sud

Processed: affects 895882

Processing commands for cont...@bugs.debian.org: > affects 895882 - src:pygments src:python-click src:pyfr src:python-biom-format Bug #895882 [python3-sphinxcontrib.bibtex] sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex (Unknown node: bibliography) Removed indication that 89588

Processed: affects 896485

Processing commands for cont...@bugs.debian.org: > affects 896485 src:pygments src:python-click src:pyfr src:python-biom-format Bug #896485 [src:sphinx] FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive' Added indication that 896485 affects src:pygments, src:python-click, src:pyfr

Processed: affects 895882

Processing commands for cont...@bugs.debian.org: > affects 895882 src:pygments src:python-click src:pyfr src:python-biom-format Bug #895882 [python3-sphinxcontrib.bibtex] sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex (Unknown node: bibliography) Added indication that 895882 af

Bug#893039: marked as done (libccnet0: contains a python module)

Your message dated Sat, 21 Apr 2018 19:58:28 +0200 with message-id and subject line has caused the Debian Bug report #893039, regarding libccnet0: contains a python module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#896494: FTBFS: test-suite failures

Source: libqtdbusmock Version: 0.7+bzr49+repack1-2 Severity: serious Hi, libqtdbusmock fails to pass its test-suite, resulting in a FTBFS: https://buildd.debian.org/status/package.php?p=libqtdbusmock /usr/bin/ctest --force-new-ctest-process -j4 Test project /<>/libqtdbusmock-0.7+bzr49+repack1/ob

Bug#895454: marked as done (osmo-bts FTBFS with libosmocore 0.10.2)

Your message dated Sat, 21 Apr 2018 17:52:32 + with message-id and subject line Bug#895454: fixed in osmo-bts 0.7.0-1 has caused the Debian Bug report #895454, regarding osmo-bts FTBFS with libosmocore 0.10.2 to be marked as done. This means that you claim that the problem has been dealt with

Processed: tags 873108 pending

Processing commands for cont...@bugs.debian.org: > tags 873108 pending Bug #873108 [src:xscreensaver] xscreensaver does not trap errors from intltool-update Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 873108: https://bugs.debian.org/cgi-

Processed: tags 876087 pending

Processing commands for cont...@bugs.debian.org: > tags 876087 pending Bug #876087 [xscreensaver] xscreensaver: source-less and unlicensed code at hacks/images/m6502/dmsc.asm Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 876087: https://bu

Bug#896489: python-zxcvbn,python3-zxcvbn: both ship /usr/bin/zxcvbn

Package: python-zxcvbn,python3-zxcvbn Version: 4.4.25-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom.

Bug#896144: marked as done (tpm2-tss FTBFS on big endian: test failures)

Your message dated Sat, 21 Apr 2018 16:09:43 + with message-id and subject line Bug#896144: fixed in tpm2-tss 1.4.0-2 has caused the Debian Bug report #896144, regarding tpm2-tss FTBFS on big endian: test failures to be marked as done. This means that you claim that the problem has been dealt

Bug#896487: datamash FTBFS on !x86/ia64: FAIL: tests/datamash-output-format

Source: datamash Version: 1.3-1 Severity: serious https://buildd.debian.org/status/package.php?p=datamash&suite=sid ... FAIL: tests/datamash-output-format == datamash (GNU datamash) 1.3 Copyright (C) 2018 Assaf Gordon License GPLv3+: GNU GPL version 3 or later

Processed: Re: Bug#895769: skimage: autopkgtest fails since matplotlib 2.2.2-1 due to new deprecation warning

Processing control commands: > severity -1 serious Bug #895769 [src:skimage] skimage: autopkgtest fails since matplotlib 2.2.2-1 due to new deprecation warning Severity set to 'serious' from 'normal' -- 895769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895769 Debian Bug Tracking System

Bug#876614: libfm FTBFS with gtk-doc-tools 1.26: fm-module.xml:72: parser error : error parsing attribute name

Thank you for a NMU but that isn't needed, I think 1.3.0 will come pretty soon where this issue is fixed. Cheers!

Bug#896486: maffilter FTBFS with libbpp-phyl-omics-dev 2.4.0

Source: maffilter Version: 1.2.1+dfsg-1 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/maffilter.html ... CMake Error at CMakeLists.txt:66 (find_package): Could not find a configuration file for package "bpp-phyl-omics" that is compatible with requested v

Bug#896485: FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'

Hi, > Could not import extension changelog (exception: cannot import name > 'Directive') According to the release notes of Sphinx 1.6 [0]: sphinx.util.compat.Directive class is now deprecated. Please use instead docutils.parsers.rst.Directive [0] http://www.sphinx-doc.org/en/master/ch

Processed: Re: Bug#895880: sphinxcontrib-websupport: autopkgtest fails since sphinx 1.7.2-1 (RemovedInSphinx17Warning)

Processing control commands: > severity -1 serious Bug #895880 [src:sphinxcontrib-websupport] sphinxcontrib-websupport: autopkgtest fails since sphinx 1.7.2-1 (RemovedInSphinx17Warning) Severity set to 'serious' from 'normal' -- 895880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895880 D

Processed: FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'

Processing control commands: > affects -1 src:alembic src:bcfg2 src:bottleneck src:dipy src:heat src:julia > src:mako src:prospector src:pyevolve src:pymvpa2 src:python-cryptography > src:python-expyriment src:python-numpy src:python-scipy Bug #896485 [src:sphinx] FTBFS with sphinx 1.7.2: except

  1   2   3   >