Re: Please publish security buildd logs after the packages/DSAs have been published
* Kurt Roeckx (kurt@roeckx.be) [130612 23:11]:
> On Wed, Jun 12, 2013 at 10:05:40PM +0200, Andreas Barth wrote:
> > * Kurt Roeckx (kurt@roeckx.be) [130612 21:00]:
> > > On Wed, Jun 12, 2013 at 07:34:25PM +0200, Axel Beckert wrote:
> > > > it would be nice if the build logs of DSA builds would be available,
> > > > too, at least after the DSA has been published.
> > > >
> > > > A discussion on IRC suggested that the release of the security buildd
> > > > logs could be triggered by the releases of the DSA on security-master.
> > >
> > > We currently don't have the logs available on buildd.debian.org, they only
> > > get send to the security team.
> > >
> > > Assuming we have the logs available, I'm not sure on what we can trigger
> > > them being available.
> > >
> > > You would also need to be able to find the url for the log file, so I guess
> > > the status/ pages would need to be able to show you information about what
> > > is the status of packages in the security dists. Currently all this
> > > information is restricted to a few people.
> >
> > Apart from "when do we make them available", I would think of the
> > following:
> >
> > send all logs to buildd.d.o, hide them away into a seperate
> > protected maildir (by the inject script) and re-inject with an
> > appropriate flag after they should be public and then put them to the
> > usual locations, so that they're available via the http://buildd.d.o service.
> >
> > What do you think about that?
>
> I guess that
> https://buildd.debian.org/status/logs.php?pkg=$package would be
> enough to find the logs?
Only after publication. Before they would be in the maildir
/srv/buildd.d.o/hidden-mail/ (or so) with only access for admins.
Andi
Reply to: