Your message dated Fri, 27 Mar 2020 05:53:51 +
with message-id
and subject line Bug#938839: fixed in xcb-proto 1.14-1
has caused the Debian Bug report #938839,
regarding xcb-proto: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> owner 954713 tmanc...@debian.org
Bug #954713 [src:commons-configuration2] commons-configuration2: CVE-2020-1953
Owner recorded as tmanc...@debian.org.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
954713:
> So the test expects no error. Since the commit mention there is an
> error where earlier there was none. From the Changes file:
>
> | *) Properly detect EOF while reading in libssl. Previously if we hit an EOF
> |while reading in libssl then we would report an error back to the
> |
Your message dated Fri, 27 Mar 2020 03:25:09 +
with message-id
and subject line Bug#955024: Removed package(s) from unstable
has caused the Debian Bug report #936570,
regarding funkload: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 27 Mar 2020 03:22:32 +
with message-id
and subject line Bug#954963: Removed package(s) from unstable
has caused the Debian Bug report #942777,
regarding nitroshare: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 27 Mar 2020 03:23:20 +
with message-id
and subject line Bug#954967: Removed package(s) from unstable
has caused the Debian Bug report #920811,
regarding wfrog: Depends on removed pygooglechart
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 27 Mar 2020 03:23:20 +
with message-id
and subject line Bug#954967: Removed package(s) from unstable
has caused the Debian Bug report #939478,
regarding wfrog: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 27 Mar 2020 03:22:32 +
with message-id
and subject line Bug#954963: Removed package(s) from unstable
has caused the Debian Bug report #942777,
regarding nitroshare-nautilus: Please port to python3-nautlius
to be marked as done.
This means that you claim that the
Your message dated Fri, 27 Mar 2020 03:22:32 +
with message-id
and subject line Bug#954963: Removed package(s) from unstable
has caused the Debian Bug report #917840,
regarding nitroshare-nautilus: missing Depends: python-requests
to be marked as done.
This means that you claim that the
Your message dated Fri, 27 Mar 2020 03:18:57 +
with message-id
and subject line Bug#954890: Removed package(s) from unstable
has caused the Debian Bug report #849087,
regarding gourmet: Port to Python 3 and python3-gst-1.0
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 27 Mar 2020 03:18:24 +
with message-id
and subject line Bug#954889: Removed package(s) from unstable
has caused the Debian Bug report #937175,
regarding nxt-python: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 27 Mar 2020 03:18:57 +
with message-id
and subject line Bug#954890: Removed package(s) from unstable
has caused the Debian Bug report #886276,
regarding gourmet: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 27 Mar 2020 03:18:24 +
with message-id
and subject line Bug#954889: Removed package(s) from unstable
has caused the Debian Bug report #885467,
regarding python-nxt-filer: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 27 Mar 2020 03:20:47 +
with message-id
and subject line Bug#954946: Removed package(s) from unstable
has caused the Debian Bug report #936561,
regarding freshen: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 27 Mar 2020 03:18:57 +
with message-id
and subject line Bug#954890: Removed package(s) from unstable
has caused the Debian Bug report #849087,
regarding gourmet: Port to Python 3 and python3-gst-1.0
to be marked as done.
This means that you claim that the problem has
Package: php-recode
Version: 2:7.4+74
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The php-recode package is currently not installable because it depends
on php7.4-recode, which doesn't exist.
-- System Information:
Debian Release: bullseye/sid
APT prefers
Your message dated Thu, 26 Mar 2020 23:42:26 +
with message-id
and subject line Bug#952329: fixed in sndobj 2.6.7+ds1-3
has caused the Debian Bug report #952329,
regarding sndobj: FTBFS: ModuleNotFoundError: No module named
'distutils.sysconfig':
to be marked as done.
This means that you
Your message dated Thu, 26 Mar 2020 23:34:50 +
with message-id
and subject line Bug#954702: fixed in acorn 6.2.1+ds+~cs11.24.3-1
has caused the Debian Bug report #954702,
regarding acorn: FTBFS: You have passed an unrecognized option
to be marked as done.
This means that you claim that the
Dear Maintainer,
I tried to collect some more information and might have found something.
The allocator aborts at the backtrace below.
A valgrind run points to the same function txt_add_fragment.
There is seems that in line 2121 the allocation takes place with
12 bytes total, then a memset is
On Fri, Aug 30, 2019 at 07:11:19AM +, Matthias Klose wrote:
> Package: src:bbqsql
> Version: 1.1-4
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the
On Tue, Jan 21, 2020 at 12:02:45AM +1100, Stuart Prescott wrote:
> It seems that the upstream for src:sx has disappeared and so I guess the
> porting work to change this package to be Python 3 compatible has not been
> done.
>
> At a quick glance, the porting doesn't look that hard to do, but
Processing control commands:
> block 954831 with -1
Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9
954831 was blocked by: 944170 944172 944169 944177 944167
954831 was not blocking any bugs.
Added blocking bug(s) of 954831: 944181
> severity -1 serious
Bug #944181 [ghdl] ghdl:
Processing control commands:
> block 954831 with -1
Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9
954831 was blocked by: 944177 944172 944169 944170
954831 was not blocking any bugs.
Added blocking bug(s) of 954831: 944167
> severity -1 serious
Bug #944167 [gcc-mingw-w64]
Processing control commands:
> block 954831 with -1
Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9
954831 was blocked by: 944170 944177
954831 was not blocking any bugs.
Added blocking bug(s) of 954831: 944169
> severity -1 serious
Bug #944169 [open-ath9k-htc-firmware]
Processing control commands:
> block 954831 with -1
Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9
954831 was blocked by: 944169 944170 944177
954831 was not blocking any bugs.
Added blocking bug(s) of 954831: 944172
> severity -1 serious
Bug #944172 [openzwave] openzwave:
Processing control commands:
> block 954831 with -1
Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9
954831 was blocked by: 944170
954831 was not blocking any bugs.
Added blocking bug(s) of 954831: 944177
> severity -1 serious
Bug #944177 [mysql-workbench] mysql-workbench:
Processing control commands:
> block 954831 with -1
Bug #954831 [ftp.debian.org] RM: gcc-8 -- ROM; superseded by gcc-9
954831 was not blocked by any bugs.
954831 was not blocking any bugs.
Added blocking bug(s) of 954831: 944170
> severity -1 serious
Bug #944170 [kfreebsd-10] kfreebsd-10:
Jens, the log indicates the machine has an Intel(R) HD Graphics 530
(Skylake GT2) GPU. Is this the same for the other machines? I have
been trying to reproduce for several days, also running on Intel
drivers, but with a 5500 series GPU and also I am on "testing" so I
have newer Xorg and kernel.
Your message dated Thu, 26 Mar 2020 20:53:24 +
with message-id
and subject line Bug#950090: fixed in gcc-mingw-w64 22~exp3
has caused the Debian Bug report #950090,
regarding gcc-mingw-w64: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
to be marked as done.
This means
Processing control commands:
> tags -1 pending
Bug #944365 [src:frama-c] FTBFS with OCaml 4.08.1 (implementation/interface
mismatch)
Added tag(s) pending.
--
944365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
control: tags -1 pending
in deferred/5
G.
On Fri, 08 Nov 2019 16:54:04 +0100 =?utf-8?q?St=C3=A9phane_Glondu?=
wrote:
> Package: src:frama-c
> Version: 20171101+sulfur+dfsg-2
> Severity: serious
> Tags: ftbfs
> User: debian-ocaml-ma...@lists.debian.org
> Usertags: ocaml-4.08-transition
>
>
Control: tag -1 pending
Hello,
Bug #952329 in sndobj 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 #952329 [src:sndobj] sndobj: FTBFS: ModuleNotFoundError: No module named
'distutils.sysconfig':
Added tag(s) pending.
--
952329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952329
Debian Bug Tracking System
Contact ow...@bugs.debian.org
On 3/26/20 8:51 PM, Colomban Wendling wrote:
> Hi,
>
> Sorry if I'm too far off the tree, but isn't this just an overlook of
> the dependency switch from libgcc1 (which has an "1" epoch) to the
> libgcc-s1 (which doesn't have an epoch)?
>
> ATM at least clang-9 (which is still the default in
Hi,
Sorry if I'm too far off the tree, but isn't this just an overlook of
the dependency switch from libgcc1 (which has an "1" epoch) to the
libgcc-s1 (which doesn't have an epoch)?
ATM at least clang-9 (which is still the default in unstable) depends on
libgcc-8-dev, and while I probably miss
Control: reassign -1 src:mono 6.8.0.105+dfsg-2
Control: retitle -1 CLI binding packages fail to install: Unhandled Exception:
System.TypeInitializationException: The type initializer for 'Sys' threw an
exception
Control: affects -1 src:golang-github-thecreeper-go-notify libglib2.0-cil
Processing control commands:
> fixed -1 3.0.0-1
Bug #955012 [src:librouteros] src:librouteros: fails to migrate to testing for
too long
Marked as fixed in versions librouteros/3.0.0-1.
--
955012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955012
Debian Bug Tracking System
Contact
Source: boxer-data
Version: 10.8.11
Severity: serious
Control: fixed -1 10.8.12
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between
Processing control commands:
> reassign -1 src:mono 6.8.0.105+dfsg-2
Bug #954635 [src:golang-github-thecreeper-go-notify]
golang-github-thecreeper-go-notify: FTBFS: Errors while processing:
libdbus2.0-cil libglib2.0-cil libgtk2.0-cil libdbus-glib2.0-cil
libnotify0.4-cil libnotify-cil-dev
Source: librouteros
Version: 2.2.0-1
Severity: serious
Control: fixed -1 3.0.0-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between
Processing control commands:
> fixed -1 10.8.12
Bug #955013 [src:boxer-data] src:boxer-data: fails to migrate to testing for
too long
Marked as fixed in versions boxer-data/10.8.12.
--
955013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955013
Debian Bug Tracking System
Contact
Your message dated Thu, 26 Mar 2020 19:20:00 +
with message-id
and subject line Bug#954774: fixed in mozjs68 68.6.0-1
has caused the Debian Bug report #954774,
regarding mozjs68: FTBFS on armel: rust/cargo using
armv7-unknown-linux-gnueabi, should be armv5te-unknown-linux-gnueabi
to be
Your message dated Thu, 26 Mar 2020 18:42:04 +
with message-id
and subject line Bug#954992: fixed in gdcm 3.0.5-1.1
has caused the Debian Bug report #954992,
regarding gdcm: b-dep on cli-common-dev, which is unavailable on mips64el
to be marked as done.
This means that you claim that the
Package: src:ruby-graffiti
Followup-For: Bug #952016
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
After some digging one issue is in
/tmp/build-area/ruby-graffiti-2.3.1/debian/ruby-graffiti/usr/lib/ruby/vendor_ruby/graffiti/squish.rb:106:in
`upcase!'
Error: [..]: FrozenError: can't modify
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:ghdl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:todoman
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Your message dated Thu, 26 Mar 2020 17:50:51 +
with message-id
and subject line Bug#952084: fixed in ruby-twitter-text 1.14.7+conformance-2
has caused the Debian Bug report #952084,
regarding ruby-twitter-text: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:
to be marked as done.
This
Your message dated Thu, 26 Mar 2020 17:49:16 +
with message-id
and subject line Bug#954623: fixed in dask-sphinx-theme 1.3.1-2
has caused the Debian Bug report #954623,
regarding dask: FTBFS: dh_sphinxdoc: error:
debian/python-dask-doc/usr/share/doc/python-dask-doc/html/_static/js/custom.js
Control: tag -1 pending
Hello,
Bug #952084 in ruby-twitter-text 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 #952084 [src:ruby-twitter-text] ruby-twitter-text: FTBFS: ERROR: Test
"ruby2.7" failed: Failure/Error:
Added tag(s) pending.
--
952084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952084
Debian Bug Tracking System
Contact
Processing control commands:
> fixed -1 2.4.1-1
Bug #955006 [src:gubbins] src:gubbins: fails to migrate to testing for too
long: ftbfs on i386
Marked as fixed in versions gubbins/2.4.1-1.
--
955006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955006
Debian Bug Tracking System
Contact
Source: gubbins
Version: 2.3.5-1
Severity: serious
Control: fixed -1 2.4.1-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and
Well I did some more digging.
I believe it's the Python variables which are wrong. Specifically the
${Python_INCLUDE_DIR}
I believe the correct variable is ${Python_INCLUDE_DIRS}
I made a patch, which patches the old patch.
I created a merge request in salsa with the change.
Håvard
Control: severity -1 important
On Tue, 18 Feb 2020, Sergio Durigan Junior wrote:
> Thanks for the report.
>
> It's not clear from your description whether tmpa_crtoef.htm is the
> only file that triggers this behaviour, or if this happens with any file
> when you try opening it with Midori.
>
>
Processing control commands:
> severity -1 important
Bug #944553 [midori] midori deletes my files
Severity set to 'important' from 'grave'
--
944553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Thu, 26 Mar 2020 16:49:25 +
with message-id
and subject line Bug#952011: fixed in bitstruct 8.9.0-1
has caused the Debian Bug report #952011,
regarding bitstruct: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.8 3.7" --system=custom
Processing commands for cont...@bugs.debian.org:
> close 952080 1.9.1-2
Bug #952080 [src:ruby-faker] ruby-faker: FTBFS: ERROR: Test "ruby2.7" failed.
Marked as fixed in versions ruby-faker/1.9.1-2.
Bug #952080 [src:ruby-faker] ruby-faker: FTBFS: ERROR: Test "ruby2.7" failed.
Marked Bug as done
>
Package: azure-cli
Version: 2.0.81+ds-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Note: Using the FTBFS tag because it is the closest one we have.
Now that humanfriendly is fixed to provide the missing files, azure-cli
has what
close 952080 1.9.1-2
# the bug was closed by ruby-faker (1.9.1-2)
# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952080#19
# ruby-fakefs later just addressed the same bug by accident
thanks
Your message dated Thu, 26 Mar 2020 16:07:15 +
with message-id
and subject line Bug#952043: fixed in ruby-ole 1.2.11.8-2
has caused the Debian Bug report #952043,
regarding ruby-ole: FTBFS: ERROR: Test "ruby2.7" failed:
/<>/lib/ole/storage/base.rb:352:in `': superclass
mismatch for class
Package: eclipse-titan
Version: 6.6.1-1
Severity: serious
Tags sid bullseye
eclipse-titan still encodes an upper dependency on gcc. The changelog says this
is fixed upstream, nevertheless the package still has this dependency.
Plus this dependency is bogus. The gcc-9 package changed to 9.3, and
Package: src:ruby-ole
Followup-For: Bug #952043
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The issue seems to be that every test file prepends lib/ to the LOAD_PATH
leading to conflicting/duplicate definitions. Changing from
d/ruby-test-files.yaml to d/ruby-tests.rake fixes the issue.
Your message dated Thu, 26 Mar 2020 15:04:21 +
with message-id
and subject line Bug#951688: fixed in aspell-ta 20040424-1-2.1
has caused the Debian Bug report #951688,
regarding src:aspell-ta: fails to migrate to testing for too long
to be marked as done.
This means that you claim that the
Your message dated Thu, 26 Mar 2020 14:46:33 +
with message-id
and subject line Bug#951945: fixed in cramfsswap 1.4.1-1.2
has caused the Debian Bug report #951945,
regarding cramfsswap: FTBFS: cramfsswap.c:348: undefined reference to `crc32'
to be marked as done.
This means that you claim
Processing control commands:
> reassign -1 gcc-9 9.2.1-28
Bug #952628 [src:hepmc3] hepmc3: FTBFS: Feature.h:296:69: internal compiler
error: in get_fns, at cp/tree.c:2455
Bug reassigned from package 'src:hepmc3' to 'gcc-9'.
No longer marked as found in versions hepmc3/3.1.2-2.
Ignoring request
Control: reassign -1 gcc-9 9.2.1-28
Control: affects -1 src:hepmc3
Looks like a gcc regression somewhere after 9.2.1-24 and no later than 9.2.1-28:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hepmc3.html
cu
Adrian
Processing commands for cont...@bugs.debian.org:
> tags 954992 sid bullseye
Bug #954992 [src:gdcm] gdcm: b-dep on cli-common-dev, which is unavailable on
mips64el
Added tag(s) sid and bullseye.
> user debian-pyt...@lists.debian.org
Setting user to debian-pyt...@lists.debian.org (was
Bug introduced during clean-up:
*
https://salsa.debian.org/med-team/gdcm/-/commit/13759c10cd9b560f12c454e05dd8d5e6fa133420
Your message dated Thu, 26 Mar 2020 13:04:30 +
with message-id
and subject line Bug#954685: fixed in node-rollup-plugin-babel 3.0.7-1
has caused the Debian Bug report #954685,
regarding node-rollup-plugin-babel: FTBFS: dh_auto_test: error: /bin/sh -e
debian/tests/pkg-js/test returned exit
Processing control commands:
> tags -1 patch confirmed
Bug #954992 [src:gdcm] gdcm: b-dep on cli-common-dev, which is unavailable on
mips64el
Added tag(s) patch and confirmed.
--
954992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954992
Debian Bug Tracking System
Contact
Control: tags -1 patch confirmed
$ touch debian/control.in
$ make -f ./debian/rules debian/control
thanks
package: src:gdcm
version: 3.0.5-1
severity: serious
tags: ftbfs
Hi,
The latest upload of gdcm to unstable cannot be built on mips64el:
https://buildd.debian.org/status/package.php?p=gdcm
It build-depends on cli-common-dev, which depends on mono-utils, which is
unavailable on mips64el.
Please
Your message dated Thu, 26 Mar 2020 12:34:43 +
with message-id
and subject line Bug#954589: fixed in seqan3 3.0.1+ds-9
has caused the Debian Bug report #954589,
regarding seqan3: FTBFS: two_dimensional_matrix_test.cpp:43:15: error: invalid
type ‘__vector(1) int’ as initializer for a vector
Your message dated Thu, 26 Mar 2020 12:20:44 +
with message-id
and subject line Bug#942633: fixed in gitlab 12.8.6-1
has caused the Debian Bug report #942633,
regarding gitlab ssh access broken with protobuf 3.10
to be marked as done.
This means that you claim that the problem has been dealt
Processing commands for cont...@bugs.debian.org:
> notfound 952693 dbusada/0.5.0-3
Bug #952693 {Done: Nicolas Boulenguez }
[src:dbusada,src:ahven] dbusada: unbuildable in unstable: requires experimental
libahven
No longer marked as found in versions dbusada/0.5.0-3.
> thanks
Stopping processing
Your message dated Thu, 26 Mar 2020 11:22:44 +
with message-id
and subject line Bug#948974: fixed in logging-tree 1.8.1-0.1
has caused the Debian Bug report #948974,
regarding logging-tree ftbfs, failing tests
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 26 Mar 2020 11:56:45 +0100
with message-id <20200326105645.ga6...@tsipinakis.com>
and subject line Re: Bug#954502: newsboat: FTBFS: unsatisfiable
build-dependencies: librust-regex-1-dev librust-gettext-rs-0.4-dev
has caused the Debian Bug report #954502,
regarding
Processing commands for cont...@bugs.debian.org:
> tags 954712 - sid bullseye
Bug #954712 [src:consul] consul: FTBFS: dh_auto_test: error: cd _build && go
test -vet=off -v -p 4 -short -failfast -timeout 8m github.com/hashicorp/consul
[...] github.com/hashicorp/consul/version returned exit code
Control: severity -1 important
The autopkgtests seem to work now:
https://ci.debian.net/user/britney/jobs?package=buildbot[]=testing[]=amd64
The bug may have been fixed by: python3-defaults 3.8.2-2
Lets leave it open for a while to see if the tests are stable now.
--
Robin
Processing control commands:
> severity -1 important
Bug #953966 [src:buildbot] buildbot: autopkgtest failure with Python 3.8 as
default
Severity set to 'important' from 'serious'
--
953966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953966
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> reassign 953897 libncbi-vdb2 2.10.3+dfsg-1
Bug #953897 [src:ncbi-vdb, src:sra-sdk] ncbi-vdb breaks sra-sdk autopkgtest:
undefined symbol: vdb_mbedtls_md_setup
Bug reassigned from package 'src:ncbi-vdb, src:sra-sdk' to 'libncbi-vdb2'.
No longer
Processing commands for cont...@bugs.debian.org:
> forcemerge 952619 954624
Bug #952619 [src:deltachat-core] deltachat-core: FTBFS: dh_auto_configure:
error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
Processing control commands:
> severity -1 important
Bug #952614 [src:dropwatch] dropwatch: FTBFS: E: Build killed with signal TERM
after 150 minutes of inactivity
Severity set to 'important' from 'serious'
--
952614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952614
Debian Bug Tracking
Control: severity -1 important
On Wed, Feb 26, 2020 at 05:13:29PM +0100, Lucas Nussbaum wrote:
> Source: dropwatch
> Version: 1.5.1-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200225 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all
Processing commands for cont...@bugs.debian.org:
> tags 951779 + fixed
Bug #951779 {Done: Gianfranco Costamagna }
[src:pitivi] pitivi: missing libpython link?
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
951779:
Your message dated Thu, 26 Mar 2020 08:46:33 +
with message-id
and subject line Bug#954697: fixed in node-debbundle-insert-module-globals
7.2.0+ds+~1.0.0+~1.2.0+~1.1.3-3
has caused the Debian Bug report #954697,
regarding node-debbundle-insert-module-globals: FTBFS: Error: ENOENT: no such
Your message dated Thu, 26 Mar 2020 07:19:23 +
with message-id
and subject line Bug#952610: fixed in meson 0.54.0~rc1-1
has caused the Debian Bug report #952610,
regarding meson: autopkgtests regressions
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Package: evolution
Version: 3.36.0-1
Severity: grave
I am currently seeing the following error come up in evolution when
trying to connect to my gmail accounts. Presumably it is a knock on
effect of increased usage brought on by the lock down for COVID-19.
Someone needs to get the quota bumped
88 matches
Mail list logo
