Bug#997927: marked as done (Please re-enable RTTI support in leveldb)

Your message dated Mon, 01 Nov 2021 19:18:36 + with message-id and subject line Bug#997927: fixed in leveldb 1.23-3 has caused the Debian Bug report #997927, regarding Please re-enable RTTI support in leveldb to be marked as done. This means that you claim that the problem has been dealt

Bug#996486: marked as done (bitcoind: fails to start with undefined symbol: _ZTIN7leveldb6LoggerE)

Your message dated Mon, 01 Nov 2021 19:18:36 + with message-id and subject line Bug#997927: fixed in leveldb 1.23-3 has caused the Debian Bug report #997927, regarding bitcoind: fails to start with undefined symbol: _ZTIN7leveldb6LoggerE to be marked as done. This means that you claim that

Bug#998261: marked as done (jsbundle-web-interfaces: autopkgtest regression: node: command not found)

Your message dated Mon, 01 Nov 2021 19:18:30 + with message-id and subject line Bug#998261: fixed in jsbundle-web-interfaces 1.1.0+~2.0.1~ds+~7.0.0+~0~20180821-2 has caused the Debian Bug report #998261, regarding jsbundle-web-interfaces: autopkgtest regression: node: command not found to

Bug#985314: marked as done (asterisk spams console output to syslog due to systemd misconfiguration)

Your message dated Mon, 01 Nov 2021 22:50:07 + with message-id and subject line Bug#985314: fixed in asterisk 1:16.16.1~dfsg-4 has caused the Debian Bug report #985314, regarding asterisk spams console output to syslog due to systemd misconfiguration to be marked as done. This means that

Bug#971090: marked as done (asterisk: syslog logging print double linees, one with colouring escapes...)

Your message dated Mon, 01 Nov 2021 22:50:07 + with message-id and subject line Bug#971090: fixed in asterisk 1:16.16.1~dfsg-4 has caused the Debian Bug report #971090, regarding asterisk: syslog logging print double linees, one with colouring escapes... to be marked as done. This means

Bug#997983: marked as done (Please upload version 3 from experimental to unstable)

Your message dated Mon, 01 Nov 2021 22:48:32 + with message-id and subject line Bug#997983: fixed in aom 3.2.0-1 has caused the Debian Bug report #997983, regarding Please upload version 3 from experimental to unstable to be marked as done. This means that you claim that the problem has been

Bug#998238: marked as done (syncany: FTBFS: Could not resolve commons-io:commons-io:2.4.)

Your message dated Mon, 01 Nov 2021 21:19:18 + with message-id and subject line Bug#998238: fixed in syncany 0.4.9~alpha-4 has caused the Debian Bug report #998238, regarding syncany: FTBFS: Could not resolve commons-io:commons-io:2.4. to be marked as done. This means that you claim that the

Bug#997195: marked as done (cpl-plugin-vimos: FTBFS: vimos_flat_normalise.cc:479:23: error: aggregate ‘std::stringstream ss’ has incomplete type and cannot be defined)

Your message dated Mon, 01 Nov 2021 16:49:00 + with message-id and subject line Bug#997195: fixed in cpl-plugin-vimos 4.1.6+dfsg-1 has caused the Debian Bug report #997195, regarding cpl-plugin-vimos: FTBFS: vimos_flat_normalise.cc:479:23: error: aggregate ‘std::stringstream ss’ has

Bug#997214: marked as done (cpl-plugin-fors: FTBFS: fors_flat_normalise.cc:582:23: error: aggregate ‘std::stringstream ss’ has incomplete type and cannot be defined)

Your message dated Mon, 01 Nov 2021 16:48:54 + with message-id and subject line Bug#997214: fixed in cpl-plugin-fors 5.5.7+dfsg-1 has caused the Debian Bug report #997214, regarding cpl-plugin-fors: FTBFS: fors_flat_normalise.cc:582:23: error: aggregate ‘std::stringstream ss’ has incomplete

Bug#997292: marked as done (wsclean: FTBFS: ld: libwsclean.so.2: undefined reference to `H5::DataSpace::selectAll() const')

Your message dated Mon, 01 Nov 2021 16:50:04 + with message-id and subject line Bug#997292: fixed in wsclean 3.0-1 has caused the Debian Bug report #997292, regarding wsclean: FTBFS: ld: libwsclean.so.2: undefined reference to `H5::DataSpace::selectAll() const' to be marked as done. This

Bug#972639: marked as done (maxima-src: Incorrect file contents.hhc is generated)

Your message dated Mon, 01 Nov 2021 18:48:39 + with message-id and subject line Bug#972639: fixed in maxima 5.45.1-1 has caused the Debian Bug report #972639, regarding maxima-src: Incorrect file contents.hhc is generated to be marked as done. This means that you claim that the problem has

Bug#992809: marked as done (maxima: please migrate away from autoconf2.13)

Your message dated Mon, 01 Nov 2021 18:48:39 + with message-id and subject line Bug#992809: fixed in maxima 5.45.1-1 has caused the Debian Bug report #992809, regarding maxima: please migrate away from autoconf2.13 to be marked as done. This means that you claim that the problem has been

Bug#997330: marked as done (cpl-plugin-amber: FTBFS: configure: error: Installed cfitsio (unknown) is too old)

Your message dated Mon, 01 Nov 2021 16:48:48 + with message-id and subject line Bug#997330: fixed in cpl-plugin-amber 4.4.1+dfsg-1 has caused the Debian Bug report #997330, regarding cpl-plugin-amber: FTBFS: configure: error: Installed cfitsio (unknown) is too old to be marked as done. This

Processed: src:osslsigncode: fails to migrate to testing for too long: unresolved RC bugs

Processing control commands: > close -1 2.2-1 Bug #998259 [src:osslsigncode] src:osslsigncode: fails to migrate to testing for too long: unresolved RC bugs Marked as fixed in versions osslsigncode/2.2-1. Bug #998259 [src:osslsigncode] src:osslsigncode: fails to migrate to testing for too long:

Processed: src:phosh: fails to migrate to testing for too long

Processing control commands: > close -1 0.13.1-1 Bug #998293 [src:phosh] src:phosh: fails to migrate to testing for too long Marked as fixed in versions phosh/0.13.1-1. Bug #998293 [src:phosh] src:phosh: fails to migrate to testing for too long Marked Bug as done -- 998293:

Bug#997167: marked as done (ncdc: FTBFS: src/uit_dl.c:227:25: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Mon, 01 Nov 2021 22:04:00 + with message-id and subject line Bug#997167: fixed in ncdc 1.22.1-3 has caused the Debian Bug report #997167, regarding ncdc: FTBFS: src/uit_dl.c:227:25: error: format not a string literal and no format arguments [-Werror=format-security] to be

Bug#997136: marked as done (asterisk: FTBFS: configure: error: *** ANSI C header files not found.)

Your message dated Mon, 01 Nov 2021 22:03:29 + with message-id and subject line Bug#997136: fixed in asterisk 1:16.16.1~dfsg-3 has caused the Debian Bug report #997136, regarding asterisk: FTBFS: configure: error: *** ANSI C header files not found. to be marked as done. This means that you

Bug#986013: marked as done (asterisk: codec_amr not built)

Your message dated Mon, 01 Nov 2021 22:03:28 + with message-id and subject line Bug#986013: fixed in asterisk 1:16.16.1~dfsg-3 has caused the Debian Bug report #986013, regarding asterisk: codec_amr not built to be marked as done. This means that you claim that the problem has been dealt

Bug#996402: marked as done (asterisk-modules: MP3 playback does not work due to incompatibility with mpg123)

Your message dated Mon, 01 Nov 2021 22:03:28 + with message-id and subject line Bug#996402: fixed in asterisk 1:16.16.1~dfsg-3 has caused the Debian Bug report #996402, regarding asterisk-modules: MP3 playback does not work due to incompatibility with mpg123 to be marked as done. This means

Bug#996242: marked as done (liquidprompt: new upstream version 2.0.3)

Your message dated Mon, 01 Nov 2021 21:33:40 + with message-id and subject line Bug#996242: fixed in liquidprompt 2.0.3-1 has caused the Debian Bug report #996242, regarding liquidprompt: new upstream version 2.0.3 to be marked as done. This means that you claim that the problem has been

Bug#997309: marked as done (django-countries: FTBFS: AttributeError: 'CountryField' object has no attribute 'db_collation')

Your message dated Mon, 01 Nov 2021 17:34:32 + with message-id and subject line Bug#997309: fixed in django-countries 7.2.1-1 has caused the Debian Bug report #997309, regarding django-countries: FTBFS: AttributeError: 'CountryField' object has no attribute 'db_collation' to be marked as

Bug#996387: marked as done (ruby-sigar: FTBFS with ruby3.0: sigar_util.c:742:10: fatal error: rpc/rpc.h: No such file or directory)

Your message dated Mon, 01 Nov 2021 18:04:37 + with message-id and subject line Bug#996387: fixed in ruby-sigar 0.7.3-3 has caused the Debian Bug report #996387, regarding ruby-sigar: FTBFS with ruby3.0: sigar_util.c:742:10: fatal error: rpc/rpc.h: No such file or directory to be marked as

Bug#996723: marked as done (src:python-pluggy: fails to migrate to testing for too long: uploader built arch:all binaries)

Your message dated Mon, 01 Nov 2021 20:36:29 + with message-id and subject line Bug#996723: fixed in python-pluggy 0.13.0-7.1 has caused the Debian Bug report #996723, regarding src:python-pluggy: fails to migrate to testing for too long: uploader built arch:all binaries to be marked as

Bug#996721: marked as done (src:pyzbar: fails to migrate to testing for too long: uploader build arch:all binaries)

Your message dated Mon, 01 Nov 2021 20:36:34 + with message-id and subject line Bug#996721: fixed in pyzbar 0.1.8-3.1 has caused the Debian Bug report #996721, regarding src:pyzbar: fails to migrate to testing for too long: uploader build arch:all binaries to be marked as done. This means

Bug#998285: marked as done (libgig: fails to clean after build)

Your message dated Mon, 01 Nov 2021 22:34:57 + with message-id and subject line Bug#998285: fixed in libgig 4.3.0~ds1-2 has caused the Debian Bug report #998285, regarding libgig: fails to clean after build to be marked as done. This means that you claim that the problem has been dealt with.

Bug#997411: marked as done (libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Mon, 01 Nov 2021 17:20:12 + with message-id and subject line Bug#997411: fixed in libstatgen 1.0.15-2 has caused the Debian Bug report #997411, regarding libstatgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output

Bug#994989: marked as done (ITP: ruby-uc.micro-rb -- Micro subset of unicode data files for motion-markdown-it projects)

Your message dated Mon, 01 Nov 2021 19:00:10 + with message-id and subject line Bug#994989: fixed in ruby-uc.micro-rb 1.0.5-1 has caused the Debian Bug report #994989, regarding ITP: ruby-uc.micro-rb -- Micro subset of unicode data files for motion-markdown-it projects to be marked as done.

Bug#994988: marked as done (ITP: ruby-mdurl-rb -- MDUrl for motion-markdown-it in Ruby)

Your message dated Mon, 01 Nov 2021 19:00:09 + with message-id and subject line Bug#994988: fixed in ruby-mdurl-rb 1.0.5-1 has caused the Debian Bug report #994988, regarding ITP: ruby-mdurl-rb -- MDUrl for motion-markdown-it in Ruby to be marked as done. This means that you claim that the

Bug#995380: marked as done (ITP: ruby-activerecord-precounter -- Yet Another N+1 COUNT Query Killer for ActiveRecord)

Your message dated Mon, 01 Nov 2021 19:00:09 + with message-id and subject line Bug#995380: fixed in ruby-activerecord-precounter 0.4.0-1 has caused the Debian Bug report #995380, regarding ITP: ruby-activerecord-precounter -- Yet Another N+1 COUNT Query Killer for ActiveRecord to be marked

Bug#995388: marked as done (ITP: ruby-glob -- Create a list of hash paths that match a given pattern)

Your message dated Mon, 01 Nov 2021 19:00:09 + with message-id and subject line Bug#995388: fixed in ruby-glob 0.2.0-1 has caused the Debian Bug report #995388, regarding ITP: ruby-glob -- Create a list of hash paths that match a given pattern to be marked as done. This means that you claim

Bug#995955: marked as done (ITP: ruby-warning -- Add custom processing for warnings)

Your message dated Mon, 01 Nov 2021 19:00:10 + with message-id and subject line Bug#995955: fixed in ruby-warning 1.2.1-1 has caused the Debian Bug report #995955, regarding ITP: ruby-warning -- Add custom processing for warnings to be marked as done. This means that you claim that the

Bug#996731: marked as done (src:golang-github-go-macaron-i18n: fails to migrate to testing for too long: uploader built arch:all binaries)

Your message dated Mon, 01 Nov 2021 21:04:23 + with message-id and subject line Bug#996731: fixed in golang-github-go-macaron-i18n 0.0~git20160612.0.ef57533-8.1 has caused the Debian Bug report #996731, regarding src:golang-github-go-macaron-i18n: fails to migrate to testing for too long:

Bug#998271: marked as done (Please switch the dependency from ttf-bitstream-vera to fonts-dejavu-core)

Your message dated Mon, 01 Nov 2021 21:04:39 + with message-id and subject line Bug#998271: fixed in mupen64plus-core 2.5-8 has caused the Debian Bug report #998271, regarding Please switch the dependency from ttf-bitstream-vera to fonts-dejavu-core to be marked as done. This means that you

Bug#997618: marked as done (python-jsmin: FTBFS: error in jsmin setup command: use_2to3 is invalid.)

Your message dated Mon, 01 Nov 2021 22:19:33 + with message-id and subject line Bug#997618: fixed in python-jsmin 3.0.0-1 has caused the Debian Bug report #997618, regarding python-jsmin: FTBFS: error in jsmin setup command: use_2to3 is invalid. to be marked as done. This means that you

Bug#997163: marked as done (nudoku: FTBFS: main.c:546:89: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Mon, 01 Nov 2021 22:19:14 + with message-id and subject line Bug#997163: fixed in nudoku 2.1.0-0.1 has caused the Debian Bug report #997163, regarding nudoku: FTBFS: main.c:546:89: error: format not a string literal and no format arguments [-Werror=format-security] to be

Bug#996371: marked as done (ruby-roo: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError:)

Your message dated Tue, 02 Nov 2021 03:19:59 + with message-id and subject line Bug#996371: fixed in ruby-roo 2.8.3-2 has caused the Debian Bug report #996371, regarding ruby-roo: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError: to be marked as done. This means that you

Bug#960223: marked as done (taskd: Unsuitable for stable release)

Your message dated Tue, 2 Nov 2021 00:26:51 -0300 with message-id <20211102032651.sn2lyyg6duvodsg7@debian> and subject line Re: taskd: Unsuitable for stable release has caused the Debian Bug report #960223, regarding taskd: Unsuitable for stable release to be marked as done. This means that you

Bug#846012: marked as done (libnss3: Should libfreebl3.so be provided in /usr/lib/$(DEB_HOST_MULTIARCH)/)

Your message dated Tue, 02 Nov 2021 04:04:23 + with message-id and subject line Bug#846012: fixed in nss 2:3.72-1 has caused the Debian Bug report #846012, regarding libnss3: Should libfreebl3.so be provided in /usr/lib/$(DEB_HOST_MULTIARCH)/ to be marked as done. This means that you claim

Bug#963136: marked as done (libnss3-dev:amd64 not coinstallable with libnss3-dev:armhf)

Your message dated Tue, 02 Nov 2021 04:04:23 + with message-id and subject line Bug#963136: fixed in nss 2:3.72-1 has caused the Debian Bug report #963136, regarding libnss3-dev:amd64 not coinstallable with libnss3-dev:armhf to be marked as done. This means that you claim that the problem

Bug#979159: marked as done (nss: pkg build fails on m68k due to insufficient LD_LIBRARY_PATH)

Your message dated Tue, 02 Nov 2021 04:04:24 + with message-id and subject line Bug#979159: fixed in nss 2:3.72-1 has caused the Debian Bug report #979159, regarding nss: pkg build fails on m68k due to insufficient LD_LIBRARY_PATH to be marked as done. This means that you claim that the

Bug#888764: marked as done (libfreebl3.so should be public, not in the nss subdir)

Your message dated Tue, 02 Nov 2021 04:04:23 + with message-id and subject line Bug#846012: fixed in nss 2:3.72-1 has caused the Debian Bug report #846012, regarding libfreebl3.so should be public, not in the nss subdir to be marked as done. This means that you claim that the problem has

Bug#737855: marked as done (libnss3-dev: arch-dependent file in "Multi-Arch: same" package)

Your message dated Tue, 02 Nov 2021 04:04:23 + with message-id and subject line Bug#737855: fixed in nss 2:3.72-1 has caused the Debian Bug report #737855, regarding libnss3-dev: arch-dependent file in "Multi-Arch: same" package to be marked as done. This means that you claim that the

Bug#990058: marked as done (libnss3: increase symbol version for SSL_GetChannelInfo when SSLChannelInfo size changes)

Your message dated Tue, 02 Nov 2021 04:04:24 + with message-id and subject line Bug#990058: fixed in nss 2:3.72-1 has caused the Debian Bug report #990058, regarding libnss3: increase symbol version for SSL_GetChannelInfo when SSLChannelInfo size changes to be marked as done. This means

Bug#997605: marked as done (pprofile: FTBFS: error in pprofile setup command: use_2to3 is invalid.)

Your message dated Mon, 01 Nov 2021 23:36:48 + with message-id and subject line Bug#997605: fixed in pprofile 2.1.0-1 has caused the Debian Bug report #997605, regarding pprofile: FTBFS: error in pprofile setup command: use_2to3 is invalid. to be marked as done. This means that you claim

Bug#993680: marked as done (transition: proj)

Your message dated Tue, 2 Nov 2021 00:28:28 +0100 with message-id and subject line Re: Bug#993680: transition: proj has caused the Debian Bug report #993680, regarding transition: proj to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#996814: marked as done (Missing import and export in Kaddressbook)

Your message dated Tue, 02 Nov 2021 05:19:01 + with message-id and subject line Bug#996814: fixed in kdepim-addons 21.08.1-2 has caused the Debian Bug report #996814, regarding Missing import and export in Kaddressbook to be marked as done. This means that you claim that the problem has been

Processed: RFS: elementary-theme/5.4.2-1~exp1 [ITP] -- GTK stylesheet from elementary OS and Pantheon

Processing commands for cont...@bugs.debian.org: > close 989819 Bug #989819 [sponsorship-requests] RFS: elementary-theme/5.4.2-1~exp1 [ITP] -- GTK stylesheet from elementary OS and Pantheon Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 989819:

Bug#995979: marked as done (pamix FTBFS: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Mon, 01 Nov 2021 23:04:39 + with message-id and subject line Bug#995979: fixed in pamix 1.6~git20180112.ea4ab3b-4 has caused the Debian Bug report #995979, regarding pamix FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] to be

Bug#995863: marked as done (libmediainfo-dev: Missing tfsxml_* symbols)

Your message dated Mon, 01 Nov 2021 07:33:28 + with message-id and subject line Bug#995863: fixed in libmediainfo 21.09+dfsg-2 has caused the Debian Bug report #995863, regarding libmediainfo-dev: Missing tfsxml_* symbols to be marked as done. This means that you claim that the problem has

Bug#997251: marked as done (ocaml-taglib: FTBFS: ld: cannot find -lz)

Your message dated Mon, 01 Nov 2021 08:23:00 + with message-id and subject line Bug#997251: fixed in ocaml-taglib 0.3.6-2 has caused the Debian Bug report #997251, regarding ocaml-taglib: FTBFS: ld: cannot find -lz to be marked as done. This means that you claim that the problem has been

Bug#988170: marked as done (libwbclient0: please add Breaks+Replaces: libsamba-util0)

Your message dated Mon, 01 Nov 2021 08:25:51 + with message-id and subject line Bug#988170: fixed in samba 2:4.13.13+dfsg-1 has caused the Debian Bug report #988170, regarding libwbclient0: please add Breaks+Replaces: libsamba-util0 to be marked as done. This means that you claim that the

Bug#984123: marked as done (fityk: ftbfs with GCC-11)

Your message dated Mon, 01 Nov 2021 08:21:55 + with message-id and subject line Bug#984123: fixed in fityk 1.3.1-7 has caused the Debian Bug report #984123, regarding fityk: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#850518: marked as done (tcptrack: Homepage points to unresolvable url)

Your message dated Mon, 01 Nov 2021 08:49:03 + with message-id and subject line Bug#850518: fixed in tcptrack 1.4.3-1 has caused the Debian Bug report #850518, regarding tcptrack: Homepage points to unresolvable url to be marked as done. This means that you claim that the problem has been

Bug#997254: marked as done (tcptrack: FTBFS: TextUI.cc:312:34: error: format ‘%d’ expects argument of type ‘int’, but argument 2 has type ‘time_t’ {aka ‘long int’} [-Werror=format=])

Your message dated Mon, 01 Nov 2021 08:49:03 + with message-id and subject line Bug#997254: fixed in tcptrack 1.4.3-1 has caused the Debian Bug report #997254, regarding tcptrack: FTBFS: TextUI.cc:312:34: error: format ‘%d’ expects argument of type ‘int’, but argument 2 has type ‘time_t’

Bug#984836: marked as done (logiops: Plase also ship TESTED.md)

Your message dated Mon, 01 Nov 2021 09:05:09 + with message-id and subject line Bug#984836: fixed in logiops 0.2.2-2 has caused the Debian Bug report #984836, regarding logiops: Plase also ship TESTED.md to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#997234: marked as done (logiops: FTBFS: Device.cpp:86:23: error: ‘sleep_for’ is not a member of ‘std::this_thread’)

Your message dated Mon, 01 Nov 2021 09:05:09 + with message-id and subject line Bug#997234: fixed in logiops 0.2.2-2 has caused the Debian Bug report #997234, regarding logiops: FTBFS: Device.cpp:86:23: error: ‘sleep_for’ is not a member of ‘std::this_thread’ to be marked as done. This

Processed: closing 984184

Processing commands for cont...@bugs.debian.org: > close 984184 21.09+dfsg-2 Bug #984184 [src:libmediainfo] libmediainfo: ftbfs with GCC-11 Ignoring request to alter fixed versions of bug #984184 to the same values previously set Bug #984184 [src:libmediainfo] libmediainfo: ftbfs with GCC-11

Bug#983967: marked as done (aoflagger: ftbfs with GCC-11)

Your message dated Mon, 01 Nov 2021 09:33:33 + with message-id and subject line Bug#983967: fixed in aoflagger 3.1.0-2 has caused the Debian Bug report #983967, regarding aoflagger: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#997453: marked as done (cysignals: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.')

Your message dated Mon, 01 Nov 2021 09:33:38 + with message-id and subject line Bug#997453: fixed in cysignals 1.10.2+ds-7 has caused the Debian Bug report #997453, regarding cysignals: FTBFS: '! LaTeX Error: File `tgtermes.sty' not found.' to be marked as done. This means that you claim

Bug#990532: marked as done (RFS: eta/1.0.1-2 [ITP] -- Utility for monitoring ETA and progress of an arbitrary process)

Your message dated Mon, 1 Nov 2021 11:38:26 +0100 with message-id <99b89c70-4b98-eb7b-0d95-d4c70ca75...@debian.org> and subject line Re: RFS: eta/1.0.1-1 [ITP] -- Utility for monitoring ETA and progress of an arbitrary process has caused the Debian Bug report #990532, regarding RFS: eta/1.0.1-2

Processed: Re: Bug#998118: plocate: add an option to show all paths including those that don't exist

Processing control commands: > close -1 Bug #998118 [plocate] plocate: add an option to show all paths including those that don't exist Marked Bug as done > tags -1 + wontfix Bug #998118 {Done: Paul Wise } [plocate] plocate: add an option to show all paths including those that don't exist Added

Bug#753666: marked as done (sqlalchemy 0.9.x broke out parameters in postgresql stored procedures)

Your message dated Mon, 1 Nov 2021 13:16:13 +0100 with message-id <420fcb72-faa8-7b5f-fc51-4473ec606...@debian.org> and subject line Closing bug has caused the Debian Bug report #753666, regarding sqlalchemy 0.9.x broke out parameters in postgresql stored procedures to be marked as done. This

Bug#998217: marked as done (RM: ksysguard/4:5.21.5-2)

Your message dated Mon, 1 Nov 2021 13:24:25 +0100 with message-id <964cfd50-186b-1e17-94f5-e6c8c73ef...@debian.org> and subject line Re: Bug#998217: RM: ksysguard/4:5.21.5-2 has caused the Debian Bug report #998217, regarding RM: ksysguard/4:5.21.5-2 to be marked as done. This means that you

Bug#997256: marked as done (rdfind: FTBFS: rdfind.cc:225:30: error: ‘numeric_limits’ is not a member of ‘std’)

Your message dated Mon, 01 Nov 2021 11:05:04 + with message-id and subject line Bug#997256: fixed in rdfind 1.5.0-1.1 has caused the Debian Bug report #997256, regarding rdfind: FTBFS: rdfind.cc:225:30: error: ‘numeric_limits’ is not a member of ‘std’ to be marked as done. This means that

Bug#966611: marked as done (pelican: New upstream version available)

Your message dated Mon, 01 Nov 2021 11:20:51 + with message-id and subject line Bug#966611: fixed in pelican 4.7.1+dfsg-1 has caused the Debian Bug report #966611, regarding pelican: New upstream version available to be marked as done. This means that you claim that the problem has been

Bug#940734: marked as done (please drop transitional package python-pelican from src:pelican)

Your message dated Mon, 01 Nov 2021 11:20:51 + with message-id and subject line Bug#940734: fixed in pelican 4.7.1+dfsg-1 has caused the Debian Bug report #940734, regarding please drop transitional package python-pelican from src:pelican to be marked as done. This means that you claim that

Bug#997376: marked as done (pelican: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet')

Your message dated Mon, 01 Nov 2021 11:20:51 + with message-id and subject line Bug#997376: fixed in pelican 4.7.1+dfsg-1 has caused the Debian Bug report #997376, regarding pelican: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' to be marked as done. This means

Bug#997785: marked as done (python-sshoot: FTBFS: shellcheck error)

Your message dated Mon, 01 Nov 2021 11:34:35 + with message-id and subject line Bug#997785: fixed in python-sshoot 1.4.2-2 has caused the Debian Bug report #997785, regarding python-sshoot: FTBFS: shellcheck error to be marked as done. This means that you claim that the problem has been

Bug#997244: marked as done (ncmpcpp: FTBFS: ld: cannot find -lz)

Your message dated Mon, 01 Nov 2021 11:34:17 + with message-id and subject line Bug#997244: fixed in ncmpcpp 0.9.2-2 has caused the Debian Bug report #997244, regarding ncmpcpp: FTBFS: ld: cannot find -lz to be marked as done. This means that you claim that the problem has been dealt with.

Bug#488233: marked as done (python-sqlalchemy: integrity errors with enthought traits)

Your message dated Mon, 1 Nov 2021 13:17:48 +0100 with message-id <658aa8f6-15cd-2f27-db76-df95b145c...@debian.org> and subject line Closing bug has caused the Debian Bug report #488233, regarding python-sqlalchemy: integrity errors with enthought traits to be marked as done. This means that you

Bug#997305: marked as done (harminv: FTBFS: configure: error: BLAS library not found)

Your message dated Mon, 01 Nov 2021 12:33:33 + with message-id and subject line Bug#997305: fixed in harminv 1.4.1-3 has caused the Debian Bug report #997305, regarding harminv: FTBFS: configure: error: BLAS library not found to be marked as done. This means that you claim that the problem

Bug#997651: marked as done (python-ara: FTBFS: TypeError: 'AnsibleYamlJinjaLexer' object is not callable)

Your message dated Mon, 01 Nov 2021 14:30:03 + with message-id and subject line Bug#997651: fixed in python-ara 1.5.7-1 has caused the Debian Bug report #997651, regarding python-ara: FTBFS: TypeError: 'AnsibleYamlJinjaLexer' object is not callable to be marked as done. This means that you

Bug#984015: marked as done (cif-tools: ftbfs with GCC-11)

Your message dated Mon, 01 Nov 2021 14:49:08 + with message-id and subject line Bug#984015: fixed in cif-tools 1.0.0-4 has caused the Debian Bug report #984015, regarding cif-tools: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#998170: marked as done (watch file does not support multiple release directories)

Your message dated Mon, 1 Nov 2021 15:50:28 +0100 with message-id and subject line Re: Bug#998170: watch file does not support multiple release directories has caused the Debian Bug report #998170, regarding watch file does not support multiple release directories to be marked as done. This

Bug#996952: marked as done (libkolabxml ftbfs with GCC 11)

Your message dated Mon, 01 Nov 2021 15:04:50 + with message-id and subject line Bug#996952: fixed in libkolabxml 1.2.0-3 has caused the Debian Bug report #996952, regarding libkolabxml ftbfs with GCC 11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#997377: marked as done (python-biom-format: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_javascript')

Your message dated Mon, 01 Nov 2021 13:04:10 + with message-id and subject line Bug#997377: fixed in python-biom-format 2.1.10-2 has caused the Debian Bug report #997377, regarding python-biom-format: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_javascript' to be marked as

Bug#996145: marked as done (ruby-byebug: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: "/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': cannot load such file -- byeb

Your message dated Mon, 01 Nov 2021 12:53:12 + with message-id and subject line Bug#996145: fixed in ruby-byebug 11.1.3-2 has caused the Debian Bug report #996145, regarding ruby-byebug: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:

Bug#998230: marked as done (gsl-doc: LaTeX Error: File `tgtermes.sty' not found.)

Your message dated Mon, 01 Nov 2021 12:52:23 + with message-id and subject line Bug#998230: fixed in gsl-doc 2.6-2 has caused the Debian Bug report #998230, regarding gsl-doc: LaTeX Error: File `tgtermes.sty' not found. to be marked as done. This means that you claim that the problem has

Bug#997470: marked as done (python-argh: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

Your message dated Mon, 01 Nov 2021 12:52:55 + with message-id and subject line Bug#997470: fixed in python-argh 0.26.2-2 has caused the Debian Bug report #997470, regarding python-argh: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

Bug#963763: marked as done (debian/copyright discrepancies for some files)

Your message dated Mon, 1 Nov 2021 14:08:49 +0100 with message-id and subject line Re: Bug#963763: debian/copyright discrepancies for some files has caused the Debian Bug report #963763, regarding debian/copyright discrepancies for some files to be marked as done. This means that you claim that

Bug#997443: marked as done (libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Mon, 01 Nov 2021 13:18:29 + with message-id and subject line Bug#997443: fixed in libbpp-core 2.4.1-7 has caused the Debian Bug report #997443, regarding libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output

Bug#997413: marked as done (libbpp-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Mon, 01 Nov 2021 13:34:03 + with message-id and subject line Bug#997413: fixed in libbpp-qt 2.4.1-6 has caused the Debian Bug report #997413, regarding libbpp-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

Bug#997202: marked as done (deepin-movie-reborn: FTBFS: compositing_manager.cpp:48:10: fatal error: mpv/qthelper.hpp: No such file or directory)

Your message dated Mon, 01 Nov 2021 13:33:28 + with message-id and subject line Bug#997202: fixed in deepin-movie-reborn 5.7.15-1 has caused the Debian Bug report #997202, regarding deepin-movie-reborn: FTBFS: compositing_manager.cpp:48:10: fatal error: mpv/qthelper.hpp: No such file or

Bug#997447: marked as done (libbpp-popgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Mon, 01 Nov 2021 13:33:57 + with message-id and subject line Bug#997447: fixed in libbpp-popgen 2.4.1-6 has caused the Debian Bug report #997447, regarding libbpp-popgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff

Bug#997444: marked as done (libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Mon, 01 Nov 2021 13:33:51 + with message-id and subject line Bug#997444: fixed in libbpp-phyl 2.4.1-6 has caused the Debian Bug report #997444, regarding libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output

Bug#998175: marked as done (please upgrade to latest upstream release)

Your message dated Mon, 01 Nov 2021 15:34:40 + with message-id and subject line Bug#998175: fixed in mpd 0.23.3-1 has caused the Debian Bug report #998175, regarding please upgrade to latest upstream release to be marked as done. This means that you claim that the problem has been dealt

Bug#996530: marked as done (yard: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick)

Your message dated Mon, 01 Nov 2021 15:35:32 + with message-id and subject line Bug#996530: fixed in yard 0.9.26-1 has caused the Debian Bug report #996530, regarding yard: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: cannot load such file -- webrick to be marked as done. This means

Bug#997249: marked as done (mpsolve: FTBFS: ./conftest.c:34: undefined reference to `yywrap')

Your message dated Mon, 01 Nov 2021 16:04:26 + with message-id and subject line Bug#997249: fixed in mpsolve 3.2.1-5 has caused the Debian Bug report #997249, regarding mpsolve: FTBFS: ./conftest.c:34: undefined reference to `yywrap' to be marked as done. This means that you claim that the

Bug#987327: marked as done (autopkgtests for debian-edu-doc binary packages)

Your message dated Mon, 01 Nov 2021 16:18:45 + with message-id and subject line Bug#987327: fixed in debian-edu-doc 2.12.3 has caused the Debian Bug report #987327, regarding autopkgtests for debian-edu-doc binary packages to be marked as done. This means that you claim that the problem has

Bug#997450: marked as done (libseqlib: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Mon, 01 Nov 2021 16:18:58 + with message-id and subject line Bug#997450: fixed in libseqlib 1.2.0+dfsg-7 has caused the Debian Bug report #997450, regarding libseqlib: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output

Bug#989936: marked as done (make clean should clean images-tmp dir)

Your message dated Mon, 01 Nov 2021 16:18:45 + with message-id and subject line Bug#989936: fixed in debian-edu-doc 2.12.3 has caused the Debian Bug report #989936, regarding make clean should clean images-tmp dir to be marked as done. This means that you claim that the problem has been

Processed: closing 989315

Processing commands for cont...@bugs.debian.org: > close 989315 2.0.11-1 Bug #989315 [composer] composer: Needs update for GitHub token format change Marked as fixed in versions composer/2.0.11-1. Bug #989315 [composer] composer: Needs update for GitHub token format change Marked Bug as done >

Processed: closing 955485

Processing commands for cont...@bugs.debian.org: > close 955485 Bug #955485 [composer] composer: Backport GitHub access_token fix before API removal Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 955485:

Processed: closing 984735

Processing commands for cont...@bugs.debian.org: > close 984735 1.8.5-1 Bug #984735 [composer] composer: fails on installed.json format used in Composer v2 Marked as fixed in versions composer/1.8.5-1. Bug #984735 [composer] composer: fails on installed.json format used in Composer v2 Marked

Bug#998219: marked as done (ssh-tools: please make the build reproducible)

Your message dated Mon, 01 Nov 2021 16:36:16 + with message-id and subject line Bug#998219: fixed in ssh-tools 1.7-2 has caused the Debian Bug report #998219, regarding ssh-tools: please make the build reproducible to be marked as done. This means that you claim that the problem has been

Bug#997294: marked as done (skesa: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libncbi-vdb.so: undefined reference to `ZSTD_freeDCtx')

Your message dated Mon, 01 Nov 2021 16:36:10 + with message-id and subject line Bug#997294: fixed in skesa 2.4.0-3 has caused the Debian Bug report #997294, regarding skesa: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libncbi-vdb.so: undefined reference to