Hi,
On 05/04/21 at 15:14 +0100, Jelmer Vernooij wrote:
> The python3-buildlog-consultant package now has a "analyse-sbuild-log"
> command that can parse and analyse sbuild logs and in most cases
> identity the line or lines that explain why a build failed.
>
> E.g.:
>
> % analyse-sbuild-log --jso
Processing commands for cont...@bugs.debian.org:
> forcemerge 761077 977367
Bug #761077 [qa.debian.org] debsources: support tarball-in-tarball
Bug #977367 [qa.debian.org] debsources: search results point to not existing
sources?
Severity set to 'wishlist' from 'normal'
Merged 761077 977367
> user
Control: usertag -1 debsources
Control: merge 761077 -1
Hi Tomas,
On Mon, Dec 14, 2020 at 02:13:49PM +0100, Tomas Pospisek wrote:
> Go to
> https://codesearch.debian.net/search?q=Client+sent+an+HTTP+request+to+an+HTTPS+server
> select first link
> https://codesearch.debian.net/show?file=gcc-10_
Processing control commands:
> usertag -1 debsources
Unknown command or malformed arguments to command.
> merge 761077 -1
Bug #761077 [qa.debian.org] debsources: support tarball-in-tarball
Unable to merge bugs because:
severity of #977367 is 'normal' not 'wishlist'
Failed to merge 761077: Did not
The python3-buildlog-consultant package now has a "analyse-sbuild-log"
command that can parse and analyse sbuild logs and in most cases
identity the line or lines that explain why a build failed.
E.g.:
% analyse-sbuild-log --json ~/build.log
{"stage": "build", "section": "Build", "lineno": 857, "
5 matches
Mail list logo