[atomic-wg] Issue #241 `static deltas not working from released images`

2017-03-10 Thread Dusty Mabe

dustymabe added a new comment to an issue you are following:
``
This has merged upstream - I'll close this after our next release when we prove 
everything works as desired.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/241
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org


[atomic-wg] Issue #249 `The build system should provide an automatically populated VERSION label`

2017-03-10 Thread Adam Miller

The issue: `The build system should provide an automatically populated VERSION 
label` of project: `atomic-wg` has been assigned to `maxamillion` by 
maxamillion.

https://pagure.io/atomic-wg/issue/249
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org


[atomic-wg] Issue #236 `container scratch build without a dist-git`

2017-03-10 Thread Adam Miller

maxamillion added a new comment to an issue you are following:
``
We can not currently, absolutely need to. I'll add this to the TODO list. Will 
update later with a Taiga card in the Fedora RelEng Tools space for context and 
on-going work.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/236
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org


[atomic-wg] Issue #236 `container scratch build without a dist-git`

2017-03-10 Thread Dusty Mabe

The issue: `container scratch build without a dist-git` of project: `atomic-wg` 
has been assigned to `maxamillion` by dustymabe.

https://pagure.io/atomic-wg/issue/236
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org


[atomic-wg] Issue #242 `Clarify requirements for INSTALL / UNINSTALL labels`

2017-03-10 Thread Josh Berkus

The issue: `Clarify requirements for INSTALL / UNINSTALL labels` of project: 
`atomic-wg` has been assigned to `dustymabe` by jberkus.

https://pagure.io/atomic-wg/issue/242
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org


Re: Fedora 26-20170309.n.0 compose check report

2017-03-10 Thread Dusty Mabe


On 03/09/2017 10:32 PM, Adam Williamson wrote:
> On Thu, 2017-03-09 at 21:41 -0500, Dusty Mabe wrote:
>>
>> On 03/09/2017 05:21 PM, Adam Williamson wrote:
>>> On Thu, 2017-03-09 at 20:10 +, Fedora compose checker wrote:
 Missing expected images:

 Atomic qcow2 x86_64
 Server dvd i386
 Workstation live i386
 Server boot i386
 Atomic raw-xz x86_64
 Workstation live x86_64
>>>
>>> Atomic image builds seem to be failing in anaconda, with a blank screenshot:
>>> https://koji.fedoraproject.org/koji/taskinfo?taskID=18277586
>>> https://koji.fedoraproject.org/koji/taskinfo?taskID=18277589
>>
>> *note* I'm replying all - but some of my emails get rejected.
> 
> I try to CC all the lists that *some* of the info is relevant to, but
> if you're just replying about one specific bit, feel free to limit the
> reply to the relevant list...
> 
>> I'll try to look at this weekend. Let me know if anyone else is
>> looking at this or already knows what the issue is.
> 
>  adamw: we need patches in koji and pungi
>  because ostree changed behaviour under us again
>  without notification
>  well I think it was bwrap but either way things changed
> under us again

yep. I'm aware of this issue. It's actually something we fixed in
bodhi some time back, but since pungi and bodhi use different
processes to create ostrees, we got bit by it again.

We're hoping to make them both use the same process in the future.

> 
> That was when I posted the create-ostree-repo log, though, which also
> shows an error:
> 
> https://kojipkgs.fedoraproject.org/compose/branched/Fedora-26-20170309.n.0/logs/x86_64/Atomic/ostree-2/create-ostree-repo.log
> 
> not sure what the relationship is between that error and the
> image creation failure.
> 

Since the ostree generation fails it's possible there is no ostree to
build the image from and that could explain the failure.

Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org


Re: Schedule for Container Policy VFAD

2017-03-10 Thread Daniel J Walsh
Sounds good.


On 03/09/2017 11:02 AM, Josh Berkus wrote:
> On 03/09/2017 07:50 AM, Daniel J Walsh wrote:
>> Sure I can help on this depending on the date.
>>
> Tommorrow.  Can you dial in at 2pm?
>
>
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to cloud-le...@lists.fedoraproject.org