On Tue, 2017-07-11 at 11:12 -0700, Adam Williamson wrote:
>
> The best resolution to a situation like this is simply to fix the
> problem that's causing images to fail to build in the first place.
I should note for the record that both the images missing from RC-1.4
were present in RC-1.5, which
On Tue, 2017-07-11 at 11:24 -0400, Matthew Miller wrote:
> On Tue, Jul 11, 2017 at 01:10:52PM +0200, Kevin Kofler wrote:
> > > But we can't "just ignore the compose tools", because we want the
> > > metadata to actually be correct and consistent. If we dump an ISO into
> > > a compose link this,
On Tue, Jul 11, 2017 at 01:10:52PM +0200, Kevin Kofler wrote:
> > But we can't "just ignore the compose tools", because we want the
> > metadata to actually be correct and consistent. If we dump an ISO into
> > a compose link this, it won't be.
>
> Real users don't care about metadata that you
Adam Williamson wrote:
> But we can't "just ignore the compose tools", because we want the
> metadata to actually be correct and consistent. If we dump an ISO into
> a compose link this, it won't be.
Real users don't care about metadata that you upload to some obscure server
like pdc.fp.o that
On Thu, 2017-07-06 at 10:05 -0400, Matthew Miller wrote:
> On Wed, Jul 05, 2017 at 02:33:01PM -0700, Adam Williamson wrote:
> > With Pungi 4 we really can't do that any more. Composes have a much
> > more solid identity as an actual thing. 'A compose' has a compose ID,
> > production composes have
On Mon, 2017-07-10 at 00:05 +0200, Kevin Kofler wrote:
> Adam Williamson wrote:
> > Note that for dumb reasons that I hate we actually strip the metadata
> > from the final compose when it's actually approved and shipped out to
> > mirrors, but when a compose completes, the metadata related to
Adam Williamson wrote:
> Note that for dumb reasons that I hate we actually strip the metadata
> from the final compose when it's actually approved and shipped out to
> mirrors, but when a compose completes, the metadata related to that
> compose is uploaded to PDC: https://pdc.fedoraproject.org/
On Wed, Jul 05, 2017 at 02:33:01PM -0700, Adam Williamson wrote:
> With Pungi 4 we really can't do that any more. Composes have a much
> more solid identity as an actual thing. 'A compose' has a compose ID,
> production composes have a label, and these can't really be duplicated.
> There is a
On Wed, Jul 05, 2017 at 03:04:36PM -0600, Chris Murphy wrote:
> Nope. This came up last cycle or two where compose had a weird bug
> preventing umount of the installation root fs image file, resulting in
> a corrupt file system and ensuing boot failure of the ISO. And
> actually there were some
On Wed, 2017-07-05 at 15:04 -0600, Chris Murphy wrote:
> On Wed, Jul 5, 2017 at 12:50 PM, Josh Boyer wrote:
> > So... this prompts a question in my head. I understand we don't block
> > release for non-blocking spins. That is obvious.
> >
> > What is not obvious to
On Wed, 2017-07-05 at 14:50 -0400, Josh Boyer wrote:
> On Tue, Jul 4, 2017 at 6:41 PM, Kevin Fenzi wrote:
> > On 07/04/2017 03:46 PM, Adam Williamson wrote:
> > > On Tue, 2017-07-04 at 09:32 +0200, Christian Dersch wrote:
> > > > Looks like one compose failed *again* for some
On Wed, Jul 5, 2017 at 12:50 PM, Josh Boyer wrote:
> So... this prompts a question in my head. I understand we don't block
> release for non-blocking spins. That is obvious.
>
> What is not obvious to me is if we would go back and do a compose
> later for those spins
On Tue, Jul 4, 2017 at 6:41 PM, Kevin Fenzi wrote:
> On 07/04/2017 03:46 PM, Adam Williamson wrote:
>> On Tue, 2017-07-04 at 09:32 +0200, Christian Dersch wrote:
>>> Looks like one compose failed *again* for some mirror issue… This time
>>> it is Robotic [1] , but i've seen these
On Tue, Jul 4, 2017 at 11:41 PM, Kevin Fenzi wrote:
> On 07/04/2017 03:46 PM, Adam Williamson wrote:
>> On Tue, 2017-07-04 at 09:32 +0200, Christian Dersch wrote:
>>> Looks like one compose failed *again* for some mirror issue… This time
>>> it is Robotic [1] , but i've seen
On 07/04/2017 03:46 PM, Adam Williamson wrote:
> On Tue, 2017-07-04 at 09:32 +0200, Christian Dersch wrote:
>> Looks like one compose failed *again* for some mirror issue… This time
>> it is Robotic [1] , but i've seen these random failures several times,
>> also for Astronomy for example. So a
On Tue, 2017-07-04 at 09:32 +0200, Christian Dersch wrote:
> Looks like one compose failed *again* for some mirror issue… This time
> it is Robotic [1] , but i've seen these random failures several times,
> also for Astronomy for example. So a new compose should be done here to
> ensure the Spin
Looks like one compose failed *again* for some mirror issue… This time
it is Robotic [1] , but i've seen these random failures several times,
also for Astronomy for example. So a new compose should be done here to
ensure the Spin gets in properly, it is not an issue with the Spin here
but an issue
17 matches
Mail list logo