Your message dated Sun, 29 Nov 2020 06:48:38 +
with message-id
and subject line Bug#952190: fixed in gemma 0.98.3+dfsg-1
has caused the Debian Bug report #952190,
regarding gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> tags 975842 + unreproducible
Bug #975842 [src:google-api-client-java] google-api-client-java: FTBFS: Could
not resolve dependencies for project
com.google.api-client:google-api-client:jar:1.27.1
Added tag(s) unreproducible.
> thanks
Stopping
On Wed, Nov 25, 2020 at 09:56:24PM +0100, Lucas Nussbaum wrote:
> Source: google-api-client-java
> Version: 1.27.1-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201125 ftbfs-bullseye
Apologies for the earlier noise on this bug - I mistakenly
Control: reassign -1 src:ms-gsl 3.1.0-3
On Sb, 28 nov 20, 17:21:05, Matthias Klose wrote:
> Source: src:ms-gsl
> Version: 3.1.0-3
> Severity: serious
>
> $ cat debian/tests/control
> Tests: with-gcc8-std14 with-gcc8-std17
> Depends: cmake, g++-8, libgtest-dev, pkg-config
> Restrictions:
Processing commands for cont...@bugs.debian.org:
> reopen 975842
Bug #975842 {Done: tony mancill }
[src:google-api-client-java] google-api-client-java: FTBFS: Could not resolve
dependencies for project com.google.api-client:google-api-client:jar:1.27.1
'reopen' may be inappropriate when a bug
Processing commands for cont...@bugs.debian.org:
> close 975846 1.28.0-1
Bug #975846 [src:google-oauth-client-java] google-oauth-client-java: FTBFS:
Could not resolve dependencies for project
com.google.oauth-client:google-oauth-client:jar:1.27.0
The source 'google-oauth-client-java' and
Your message dated Sun, 29 Nov 2020 04:49:22 +
with message-id
and subject line Bug#975842: fixed in google-oauth-client-java 1.28.0-1
has caused the Debian Bug report #975842,
regarding google-api-client-java: FTBFS: Could not resolve dependencies for
project
Processing commands for cont...@bugs.debian.org:
> reopen 975842
Bug #975842 [src:google-api-client-java] google-api-client-java: FTBFS: Could
not resolve dependencies for project
com.google.api-client:google-api-client:jar:1.27.1
Bug 975842 is not marked as done; doing nothing.
> thanks
Processing control commands:
> tag -1 pending
Bug #975842 [src:google-api-client-java] google-api-client-java: FTBFS: Could
not resolve dependencies for project
com.google.api-client:google-api-client:jar:1.27.1
Added tag(s) pending.
--
975842:
Control: tag -1 pending
Hello,
Bug #975842 in google-oauth-client-java reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing commands for cont...@bugs.debian.org:
> Tags 942737 security
Bug #942737 [libapache2-mod-gnutls] libapache2-mod-gnutls: mod_gnutls consumes
100% cpu
Added tag(s) security.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942737:
With 1.2.22-1, we've got e.g.:
Processing triggers for libc-bin (2.31-4) ...
(Reading database ... 14094 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [06:16:57]: test blockdev-nonroot: echo "blockdev -v" |
growlight-readline --notroot
autopkgtest
Tags 942737 security
thanks
--
Atte. Félix Arreola
Firmado con GPG 0x1e249ee4
pgppIF_bZVjam.pgp
Description: Firma digital OpenPGP
there is a 4th option, see below
Il 28/11/20 20:28, Pirate Praveen ha scritto:
...
So some options I can think,
1. Port yarn 1.x to build with babel 7 (but this has not been successfull)
2. Try to run ES6 code directly somehow, may be with newer nodejs and patches.
I think Paolo tried this
Your message dated Sat, 28 Nov 2020 22:48:30 +
with message-id
and subject line Bug#961335: fixed in rust-ppv-lite86 0.2.6-2
has caused the Debian Bug report #961335,
regarding rust-ppv-lite86 FTBFS on s390x: test failure
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 28 Nov 2020 22:02:08 +
with message-id
and subject line Bug#968366: fixed in libproxy 0.4.15-5+deb10u1
has caused the Debian Bug report #968366,
regarding libproxy: CVE-2020-26154: buffer overflow when PAC is enabled
to be marked as done.
This means that you claim
Your message dated Sat, 28 Nov 2020 21:21:35 +
with message-id
and subject line Bug#975875: fixed in x11vnc 0.9.16-5
has caused the Debian Bug report #975875,
regarding x11vnc: CVE-2020-29074
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Sat, 28 Nov 2020 21:21:02 +
with message-id
and subject line Bug#959602: fixed in gtkmm3.0 3.24.2-2
has caused the Debian Bug report #959602,
regarding gtkmm3.0: FTBFS: gtk-demo/demowindow.cc:54:1: error: ‘demo_columns’
function uses ‘auto’ type specifier without trailing
See below
Il 28/11/20 20:28, Pirate Praveen ha scritto:
On Thu, 19 Nov 2020 23:50:24 +0530 Pirate Praveen
wrote:
...
So some options I can think,
1. Port yarn 1.x to build with babel 7 (but this has not been successfull)
2. Try to run ES6 code directly somehow, may be with newer nodejs and
Package: mailutils
Version: 1:3.10-3
Severity: serious
After an "apt-get source mailutils/sid" with current unstable,
"debian/rules binary" fails here like this:
Creating popauth.1...
/home/vagrant/mailutils/mailutils-3.10/debian/tmp/usr/bin/popauth: error
while loading shared libraries:
Now I think this bug, this could be used as DOS, should we call the
security team to handle this?
--
Atte. Félix Arreola
Firmado con GPG 0x1e249ee4
pgprkMFhW5CS_.pgp
Description: Firma digital OpenPGP
Processing control commands:
> tag -1 pending
Bug #959602 [src:gtkmm3.0] gtkmm3.0: FTBFS: gtk-demo/demowindow.cc:54:1: error:
‘demo_columns’ function uses ‘auto’ type specifier without trailing return type
Added tag(s) pending.
--
959602:
Control: tag -1 pending
Hello,
Bug #959602 in gtkmm3.0 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:
On Mon, 16 Dec 2019 02:37:50 +0100 =?UTF-8?Q?Bernhard_=c3=9cbelacker?=
wrote:
> Dear Maintainer,
> tried to reconstruct the given backtrace with debug symbols
> in a gdb session and came to following, maybe it could be
> of some help.
> (Still a proper backtrace with dbgsym packages
> installed
Your message dated Sat, 28 Nov 2020 20:52:53 +
with message-id
and subject line Bug#973741: fixed in node-yarnpkg 1.22.4-4
has caused the Debian Bug report #973741,
regarding gitlab: Yarn hasn't been able to find a cache folder it can use
to be marked as done.
This means that you claim that
Source: ros-ros-comm
Version: 1.15.9+ds1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent change in testing (I believe the support of Python3.9) the
autopkgtest of ros-ros-comm started to fail. I
Processing control commands:
> affects -1 python3-defaults
Bug #976047 [src:shoogle] shoogle: flaky autopkgtest on ci.debian.net and
missing needs-internet restriction
Added indication that 976047 affects python3-defaults
--
976047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976047
Source: shoogle
Version: 0.1.4-9
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Control: affects -1 python3-defaults
Dear maintainer(s),
shoogle has an autopkgtest, great. However, it fails more often than it
passes [1].
Because the
Processing control commands:
> block 975839 by -1
Bug #975839 {Done: Paul Gevers } [src:kore] src:kore: fails
to migrate to testing for too long: existing binaries are not rebuild or removed
975839 was not blocked by any bugs.
975839 was not blocking any bugs.
Added blocking bug(s) of 975839:
Source: bind9
Version: 1:9.11.5.P4+dfsg-5.1+deb10u2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Control: found -1 1:9.16.8-1
Dear maintainer(s),
bind9 has an autopkgtest, great. However, your test (correctly) has the
restriction
Processing control commands:
> found -1 1:9.16.8-1
Bug #976045 [src:bind9] bind9: flaky autopkgtest on ci.debian.net
Marked as found in versions bind9/1:9.16.8-1.
--
976045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Le 28/11/2020 à 20:28, Pirate Praveen a écrit :
> On Thu, 19 Nov 2020 23:50:24 +0530 Pirate Praveen
> wrote:
>>
>>
>> On Thu, Nov 19, 2020 at 18:58, Xavier wrote:
>> > we opened bugs to upstream repo and are waiting for...
>>
>> I don't think upstream will make any significant changes to 1.x
Your message dated Sat, 28 Nov 2020 19:36:12 +
with message-id
and subject line Bug#975912: fixed in ufw 0.36-7.1
has caused the Debian Bug report #975912,
regarding ufw: autopkgtests fail with Python 3.9
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 28 Nov 2020 19:32:07 +
with message-id
and subject line Bug#975875: fixed in x11vnc 0.9.13-6+deb10u1
has caused the Debian Bug report #975875,
regarding x11vnc: CVE-2020-29074
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Thu, 19 Nov 2020 23:50:24 +0530 Pirate Praveen
wrote:
>
>
> On Thu, Nov 19, 2020 at 18:58, Xavier wrote:
> > we opened bugs to upstream repo and are waiting for...
>
> I don't think upstream will make any significant changes to 1.x
branch
> any more. Someone who want to see yarn in debian
Your message dated Sat, 28 Nov 2020 19:09:27 +
with message-id
and subject line Bug#959907: fixed in rust-derive-builder 0.9.0-3
has caused the Debian Bug report #959907,
regarding librust-derive-builder+env-logger-dev: cannot be installed
to be marked as done.
This means that you claim that
Package: adb
Version: 1:8.1.0+r23-8
Followup-For: Bug #976007
X-Debbugs-Cc: pitsior...@gmail.com
As expected, downgrading android-libboringssl to its previous version
(8.1.0+r23-3) makes adb usable again, and fdroidcl too.
$ adb devices
List of devices attached
ABCDEF1234567890device
I
Your message dated Sat, 28 Nov 2020 17:19:39 +
with message-id
and subject line Bug#957380: fixed in istgt 0.4~20111008-4
has caused the Debian Bug report #957380,
regarding istgt: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Source: src:ms-gsl
Version: 3.1.0-3
Severity: serious
$ cat debian/tests/control
Tests: with-gcc8-std14 with-gcc8-std17
Depends: cmake, g++-8, libgtest-dev, pkg-config
Restrictions: allow-stderr, skip-not-installable
Tests: with-gcc9-std14 with-gcc9-std17
Depends: cmake, g++-9, libgtest-dev,
Your message dated Sat, 28 Nov 2020 16:19:22 +
with message-id
and subject line Bug#975411: fixed in meson 0.56.0-1.1
has caused the Debian Bug report #975411,
regarding meson: autopkgtest arm64 regression: #error gas syntax assembly for
this test needs to be written
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> block 975178 with 976035
Bug #975178 [src:mitmproxy] mitmproxy: FTBFS: E: Build killed with signal TERM
after 150 minutes of inactivity
975178 was not blocked by any bugs.
975178 was not blocking any bugs.
Added blocking bug(s) of 975178: 976035
Processing control commands:
> forwarded -1 https://github.com/mitmproxy/mitmproxy/issues/4021
Bug #976035 [mitmproxy] Doesn't work with Python 3.9
Set Bug forwarded-to-address to
'https://github.com/mitmproxy/mitmproxy/issues/4021'.
--
976035:
Package: mitmproxy
Version: 5.1.1-2
Severity: grave
Tags: upstream fixed-upstream
Control: forwarded -1 https://github.com/mitmproxy/mitmproxy/issues/4021
[...]
File "/usr/lib/python3/dist-packages/mitmproxy/utils/typecheck.py", line 73,
in check_option_type
elif not isinstance(value,
Processing control commands:
> retitle -1 enigmail should not be shipped in bookworm
Bug #975926 [enigmail] enigmail should not be shipped in bullseye
Changed Bug title to 'enigmail should not be shipped in bookworm' from
'enigmail should not be shipped in bullseye'.
> tags -1 - bullseye
Bug
Control: retitle -1 enigmail should not be shipped in bookworm
Control: tags -1 - bullseye
Control: tags -1 bookworm
On Fri, Nov 27, 2020 at 06:41:03PM +0100, Michael Biebl wrote:
>...
> I don't see the problem with shipping the migration wizard for one stable
> release cycle and dropping it
Hi Antoni,
On Fri, Nov 27, 2020 at 02:24:16PM +, Antoni Villalonga wrote:
> Control: tag -1 pending
>
> Hello,
>
> Bug #975875 in x11vnc 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
Your message dated Sat, 28 Nov 2020 15:33:48 +
with message-id
and subject line Bug#975805: fixed in intelhex 2.1-2.1
has caused the Debian Bug report #975805,
regarding intelhex: FTBFS: AttributeError: type object 'array.array' has no
attribute 'tostring'
to be marked as done.
This means
Processing control commands:
> tags -1 + patch
Bug #975411 [src:meson] meson: autopkgtest arm64 regression: #error gas syntax
assembly for this test needs to be written
Added tag(s) patch.
--
975411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975411
Debian Bug Tracking System
Contact
Control: tags -1 + patch
please find a possible fix attached. However when I enable the patch in
debian/patches/series, I get:
$ dpkg-buildpackage -sd -S -d
dpkg-buildpackage: info: source package meson
dpkg-buildpackage: info: source version 0.56.0-1.1
dpkg-buildpackage: info: source
On Fri, Nov 27, 2020 at 02:21:04PM +0500, Andrey Rahmatullin wrote:
> >>> import libtorrent
> Traceback (most recent call last):
> File "", line 1, in
> ImportError:
> /usr/lib/python3/dist-packages/libtorrent.cpython-39-x86_64-linux-
> gnu.so: undefined symbol: _ZNK10libtorrent5entry4dictEv
>
Your message dated Sat, 28 Nov 2020 15:28:20 +0100
with message-id <6660286d-74e4-b73f-0e6d-4bdfa6915...@debian.org>
and subject line
has caused the Debian Bug report #975773,
regarding rust-ctr: FTBFS: unsatisfiable build-dependencies:
librust-generic-array-0.12+default-dev,
Your message dated Sat, 28 Nov 2020 15:28:20 +0100
with message-id <6660286d-74e4-b73f-0e6d-4bdfa6915...@debian.org>
and subject line
has caused the Debian Bug report #975768,
regarding rust-sha3: FTBFS: unsatisfiable build-dependencies:
librust-block-buffer-0.7+default-dev
to be marked as done.
Your message dated Sat, 28 Nov 2020 15:28:20 +0100
with message-id <6660286d-74e4-b73f-0e6d-4bdfa6915...@debian.org>
and subject line
has caused the Debian Bug report #975767,
regarding rust-block-modes: FTBFS: build-dependency not installable:
librust-generic-array-0.12+default-dev
to be marked
Your message dated Sat, 28 Nov 2020 15:28:20 +0100
with message-id <6660286d-74e4-b73f-0e6d-4bdfa6915...@debian.org>
and subject line
has caused the Debian Bug report #975772,
regarding rust-hkdf: FTBFS: unsatisfiable build-dependencies:
librust-digest-0.8+default-dev,
Processing control commands:
> tags 976022 + pending
Bug #976022 [src:mupdf] mupdf-dev: install pkgconfig file in wrong directory
Ignoring request to alter tags of bug #976022 to the same tags previously set
--
976022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976022
Debian Bug Tracking
Control: tags 976022 + pending
Dear maintainer,
I've prepared an NMU for mupdf (versioned as 1.17.0+ds1-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Note the change of chmod +x is not represented in the debdiff itself,
which is as Gianfranco
Processing control commands:
> tags 976022 + pending
Bug #976022 [src:mupdf] mupdf-dev: install pkgconfig file in wrong directory
Added tag(s) pending.
--
976022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sat, 28 Nov 2020 13:48:54 +
with message-id
and subject line Bug#975993: fixed in survivor 1.0.7-2
has caused the Debian Bug report #975993,
regarding survivor: autopkgtest regression: unclear why
to be marked as done.
This means that you claim that the problem has been
Source: mupdf
Version: 1.17.0+ds1-1.1
Severity: serious
tags: patch
/usr/lib/${DEB_HOST_MULTIARCH}/pkgconfig/mupdf.pc
looks like the install file needs a +x
chmod +x debian/libmupdf-dev.install
G.
Wookey writes:
> On 2020-11-27 10:28 -0400, David Bremner wrote:
>
>> I'm talking about remove polymake/arm64, not perl.
>
> Right, but perl build-depends on polymake, so with no polymake we
> can't update perl (e.g. for security reasons)
>
That doesn't make sense to me. Polymake is software
Processing commands for cont...@bugs.debian.org:
> reassign 975891 python3-libtorrent
Bug #975891 [deluge] deluge: error from deluge/_libtorrent.py
Bug reassigned from package 'deluge' to 'python3-libtorrent'.
No longer marked as found in versions deluge/2.0.3-3.
Ignoring request to alter fixed
Your message dated Sat, 28 Nov 2020 11:17:08 +
with message-id
and subject line Bug#975862: fixed in lacme 0.5-1+deb10u2
has caused the Debian Bug report #975862,
regarding lacme: Upcoming changes in the Let's Encrypt chain of trust break
lacme
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> forcemerge 975953 975891
Bug #975953 [python3-libtorrent] Can't be imported, undefined symbol:
_ZNK10libtorrent5entry4dictEv
Unable to merge bugs because:
package of #975891 is 'deluge' not 'python3-libtorrent'
Failed to forcibly merge 975953:
On Fri, 27 Nov 2020 18:34:13 -0800
Vagrant Cascadian wrote:
> On 2020-11-23, Benedikt Spranger wrote:
> > On Sun, 22 Nov 2020 14:34:33 -0800
> > Vagrant Cascadian wrote:
>
> > U-Boot 2020.10+dfsg-1 (Oct 05 2020 - 19:13:28 +) Allwinner
> > Technology
> ...
> > Found U-Boot script /boot.scr
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding tyxml: FTBFS: Error: Library "re" not found.
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding typerep: FTBFS: Error: Library "base" not found.
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding sexplib310: FTBFS: Error: Library "sexplib0" not found.
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding ocp-indent: FTBFS: Error: Library "findlib" not found.
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding headache: FTBFS: Error: Library "camomile" not found.
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding ocaml-domain-name: FTBFS: Error: Library "astring" not found.
to be marked as done.
This means that you claim that the
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding ocaml-fileutils: FTBFS: Error: Library "stdlib-shims" not found.
to be marked as done.
This means that you claim that
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding ocaml-mew: FTBFS: Error: Library "trie" not found.
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding ocaml-atd: FTBFS: Error: Library "re" not found.
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding ocaml-parsexp: FTBFS: Error: Library "base.caml" not found.
to be marked as done.
This means that you claim that the
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding ocaml-mew-vi: FTBFS: Error: Library "react" not found.
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding ocaml-stdio: FTBFS: Error: Library "base.caml" not found.
to be marked as done.
This means that you claim that the
Your message dated Sat, 28 Nov 2020 11:03:57 +
with message-id
and subject line Bug#975894: fixed in ocaml-dune 2.7.1-2
has caused the Debian Bug report #975894,
regarding Breaks build of many reverse dependencies
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> severity 975153 important
Bug #975153 [gcc-10] peg: FTBFS: src/peg.peg-c:5:1: internal compiler error: in
notice_source_line, at final.c:3237
Severity set to 'important' from 'serious'
> severity 975219 important
Bug #975219 [gfortran-10] elkcode: FTBFS: internal
Control: severity 975153 important
Control: severity 975219 important
Control: severity 974073 important
Control: severity 972789 important
Control: severity 975142 important
compiler is now built again with release checkings enabled.
Your message dated Sat, 28 Nov 2020 10:48:22 +
with message-id
and subject line Bug#971134: fixed in devscripts 2.20.5
has caused the Debian Bug report #971134,
regarding devscripts: FTBFS: dh_auto_test: error: make -j4 test returned exit
code 2
to be marked as done.
This means that you
Processing control commands:
> tag -1 pending
Bug #975894 [ocaml-dune] Breaks build of many reverse dependencies
Bug #975780 [ocaml-dune] ocaml-stdio: FTBFS: Error: Library "base.caml" not
found.
Bug #975781 [ocaml-dune] ocaml-mew-vi: FTBFS: Error: Library "react" not found.
Bug #975783
Control: tag -1 pending
Hello,
Bug #975894 in jbuilder 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:
Your message dated Sat, 28 Nov 2020 10:18:57 +
with message-id
and subject line Bug#975757: fixed in rust-stream-cipher 0.3.2-2
has caused the Debian Bug report #975757,
regarding rust-stream-cipher: FTBFS: build-dependency not installable:
librust-generic-array-0.12+default-dev
to be marked
Your message dated Sat, 28 Nov 2020 11:04:04 +0100
with message-id <7c9cbcf5-6c56-fddd-e4ce-f3f66ec14...@debian.org>
and subject line fixed
has caused the Debian Bug report #975751,
regarding rust-sequoia-sop: FTBFS: unsatisfiable build-dependencies:
librust-sha2-dev (= 0.8.0-1+b1),
Your message dated Sat, 28 Nov 2020 11:04:04 +0100
with message-id <7c9cbcf5-6c56-fddd-e4ce-f3f66ec14...@debian.org>
and subject line fixed
has caused the Debian Bug report #975766,
regarding rust-sequoia-sqv: FTBFS: unsatisfiable build-dependencies:
librust-sha2-dev (= 0.8.0-1+b1),
Your message dated Sat, 28 Nov 2020 11:06:16 +0100
with message-id <50572c22-9e92-7254-921b-6f51b3cb8...@debian.org>
and subject line fixed
has caused the Debian Bug report #975749,
regarding rust-lalrpop: FTBFS: unsatisfiable build-dependencies:
librust-sha2-dev (= 0.8.0-1+b1),
Your message dated Sat, 28 Nov 2020 11:04:04 +0100
with message-id <7c9cbcf5-6c56-fddd-e4ce-f3f66ec14...@debian.org>
and subject line fixed
has caused the Debian Bug report #975743,
regarding rust-sequoia-openpgp: FTBFS: unsatisfiable build-dependencies:
librust-sha2-dev (= 0.8.0-1+b1),
Processing commands for cont...@bugs.debian.org:
> fixed 975749 0.17.2-7
Bug #975749 [src:rust-lalrpop] rust-lalrpop: FTBFS: unsatisfiable
build-dependencies: librust-sha2-dev (= 0.8.0-1+b1), librust-digest-0.8+std-dev
Marked as fixed in versions rust-lalrpop/0.17.2-7.
> thanks
Stopping
Package: deluge
Version: 2.0.3-3
Followup-For: Bug #975899
X-Debbugs-Cc: rockst...@gmx.com
Dear Maintainer,
I'm facing the exact same issue reported by Ara. However I don't think
the deluge is to blame for this since the latest revision of deluge
dates back to July 2020. Nonetheless, the package
Your message dated Sat, 28 Nov 2020 09:19:45 +
with message-id
and subject line Bug#975769: fixed in rust-crypto-mac 0.7.0-3
has caused the Debian Bug report #975769,
regarding rust-crypto-mac: FTBFS: build-dependency not installable:
librust-generic-array-0.12+default-dev
to be marked as
90 matches
Mail list logo
