Your message dated Fri, 5 Jun 2026 12:55:04 +0000
with message-id <[email protected]>
and subject line Re: Bug#1116273: buildd.debian.org: please provide API for 
getbuildlog
has caused the Debian Bug report #1116273,
regarding buildd.debian.org: please provide API for getbuildlog
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1116273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1116273
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: buildd.debian.org
Severity: wishlist

Hi,

getbuildlog from devscripts currently parses the HTML generated by 
fetch.php. This is unsurprisingly brittle, and causes bugs like 
#651286.

I think it would be nicer if buildd.d.o would expose some 
semi-stable (JSON?) API which getbuidlog could use.

getbuildlog, per its documentation, wants to support filtering by 
these things:

- package name (mandatory)
- optional version, as a grep -E pattern, or "last"
- optional arch, as a grep -E pattern

The filtering could be done server- or client-side. It would be good 
to get things like "+" in version numbers right.

Thanks,
Chris

--- End Message ---
--- Begin Message ---
On Sun, Apr 12, 2026 at 06:25:13PM +0000, Philipp Kern wrote:
> On Wed, Sep 24, 2025 at 11:30:21PM +0200, Chris Hofstaedtler wrote:
> > getbuildlog from devscripts currently parses the HTML generated by 
> > fetch.php. This is unsurprisingly brittle, and causes bugs like 
> > #651286.
> > 
> > I think it would be nicer if buildd.d.o would expose some 
> > semi-stable (JSON?) API which getbuidlog could use.
> > 
> > getbuildlog, per its documentation, wants to support filtering by 
> > these things:
> > 
> > - package name (mandatory)
> > - optional version, as a grep -E pattern, or "last"
> > - optional arch, as a grep -E pattern
> > 
> > The filtering could be done server- or client-side. It would be good 
> > to get things like "+" in version numbers right.
> 
> I wrote a small script that dumps the database content as a JSON. It's
> reachable with https://buildd.debian.org/api/buildlogs/<pkg>
> 
> One advantage of this is that we should in theory be able to pregenerate
> the content if needed - i.e. on regenerate the package's file on every
> injected build log. But for now just dumping the DB should do.
> 
> I'd guess that we also want to dump all the information.
> 
> (I still need to properly commit this, but it seems to keep working
> so far.)

It has been committed to https://salsa.debian.org/wb-team/wbpy/ in the
meantime, so resolving the bug.

Kind regards
Philipp kern

--- End Message ---

Reply via email to