On Tue, 2016-04-26 at 18:11 +0100, Sérgio Basto wrote:
>
> On Seg, 2016-04-25 at 12:46 +0200, Vít Ondruch wrote:
> >
> >
> > Dne 25.4.2016 v 07:08 Adam Williamson napsal(a):
> > >
> > >
> > > On Mon, 2016-04-25 at 02:27 +0100, Sérgio Basto wrote:
> > > >
> > > >
> > > > On Sáb, 2016-04-23 at 07:02 -0700, Adam Williamson wrote:
> > > > >
> > > > >
> > > > > On Sat, 2016-04-23 at 03:32 +0100, Sérgio Basto wrote:
> > > > > >
> > > > > >
> > > > > >
> > > > > > Hello we need rebuild in rawhide :
> > > > > >
> > > > > > os-autoinst
> > > > > Just sent this, sorry, I missed the announce.
> > > > How we know the broken deps that we have on rawhide ?
> > > The daily 'compose report' emails contain a full list of broken
> > > deps.
> > You wanted to say "should" or "used to" contain I assume,
since
> > it
> > does
> > not contain the log for several days/weeks already :/
> yes, that is my point , email with reports don't report broken
> deps,
> but we could have somewhere that reports of broken deps ..., have
> we ?
> If we don't have the reports how I could check broken deps in
> rawhide (
> without install all rawhide )
Ah, sorry. I hadn't noticed. Well, here's one thing you can look at
(Dennis may have a better idea):
https://kojipkgs.fedoraproject.org/compose/rawhide/latest-Fedora-/log
s/global/repoclosure-builddeps.global.log
I'm not sure when that 'latest-Fedora-' symlink is updated so I dunno
if that URL will always be valid; you can always go to
https://kojipkgs.fedoraproject.org/compose/rawhide/ and poke into the
latest completed compose from there (check the STATUS file, look for
FINISHED_INCOMPLETE or FINISHED) and then open that log file. The
'Everything' tree repoclosure should be pretty close to a full list
of
broken deps, I *think*.
--
Sérgio M. B.