Your message dated Sat, 22 Feb 2020 09:40:34 +0200
with message-id
and subject line Re: Bug#951809: nmu: kworkflow_20191112-1
has caused the Debian Bug report #951809,
regarding nmu: kworkflow_20191112-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
Hello,
something gone wrong when rebuild on amd64 after sponsorship. So please
build it on that arch.
nmu kworkflow_20191112-1 . amd64 . unstable . -m "build on amd64
after a failure"
On Fri, 21 Feb 2020 at 21:36, Lucas Kanashiro wrote:
> Could you please also rebuild src:mecab? It FTBFS due to this swig bug
> #951623 and the fix was already uploaded to unstable [1]. I rebuilt it
> locally and it works fine now.
Given back, thanks.
Could you please also rebuild src:mecab? It FTBFS due to this swig bug
#951623 and the fix was already uploaded to unstable [1]. I rebuilt it
locally and it works fine now.
[1]
https://tracker.debian.org/news/1103378/accepted-swig-401-4-source-into-unstable/
--
Lucas Kanashiro
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Hi,
we’d like to fix #946847 in buster (which is where we found it in
production and tested a fix locally, which was later discovered to
be identical to a recent upstream fix)
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Dear Release Managers,
It has been brought to my attention that opam doesn't work in buster
out of the box. This has been tracked in [1] (fixed in testing) and
[2]. See in
6 matches
Mail list logo
