Re: f28/f29 container composes failure since a while, is it already tracked by an issue ?

2019-04-04 Thread Clement Verna
On Thu, 4 Apr 2019 at 11:31, Normand wrote: > > > In fedora registry (1) we have f30/rawhide containers updated from last > compose (2) >but f28 last dated 20181007 >but f29 last dated 20190218 >Probably related to the DOOMED status reported in Container compose > (3) Where f28/f29

f28/f29 container composes failure since a while, is it already tracked by an issue ?

2019-04-04 Thread Normand
In fedora registry (1) we have f30/rawhide containers updated from last compose (2) but f28 last dated 20181007 but f29 last dated 20190218 Probably related to the DOOMED status reported in Container compose (3) Where f28/f29 traceback.global file reports failures. Is there already