On Fri, 2019-08-09 at 19:04 -0700, Adam Williamson wrote:
> On Fri, 2019-08-09 at 18:26 -0700, Adam Williamson wrote:
> > On Wed, 2019-07-24 at 10:04 -0400, pmkel...@frontier.com wrote:
> > > I got feedback from Adam and Ben today; so the following changes have
> > > been made:
> > >
> > > I have
On 8/29/19 3:15 PM, Dusty Mabe wrote:
>
> On 8/29/19 2:36 PM, Daniel Walsh wrote:
>> On 8/29/19 2:16 PM, Mairi Dulaney wrote:
>>> On Lùna 29, 2019 aig 10:33:09m -0400, sgrìobh Dusty Mabe:
I don't know the formal process for proposal but here is a shot at a bare
minimum
start for try
On 8/29/19 2:36 PM, Daniel Walsh wrote:
> On 8/29/19 2:16 PM, Mairi Dulaney wrote:
>> On Lùna 29, 2019 aig 10:33:09m -0400, sgrìobh Dusty Mabe:
>>> I don't know the formal process for proposal but here is a shot at a bare
>>> minimum
>>> start for trying to add containers to the existing release
On 8/29/19 2:16 PM, Mairi Dulaney wrote:
> On Lùna 29, 2019 aig 10:33:09m -0400, sgrìobh Dusty Mabe:
>> I don't know the formal process for proposal but here is a shot at a bare
>> minimum
>> start for trying to add containers to the existing release criteria. This is
>> a suggestion
>> after we
On 8/29/19 2:28 PM, Adam Williamson wrote:
> On Thu, 2019-08-29 at 20:15 +0200, Julen Landa Alustiza wrote:
>> Could we go on a more generic fashion?
>>
>> Something like "Supported container engines must work on their basic
>> features on all the blocker deliverables were they are installed by
>>
On Thu, 2019-08-29 at 20:15 +0200, Julen Landa Alustiza wrote:
> Could we go on a more generic fashion?
>
> Something like "Supported container engines must work on their basic
> features on all the blocker deliverables were they are installed by
> default"
>
> Our supported engines are, podman?
On Lùna 29, 2019 aig 10:33:09m -0400, sgrìobh Dusty Mabe:
> I don't know the formal process for proposal but here is a shot at a bare
> minimum
> start for trying to add containers to the existing release criteria. This is
> a suggestion
> after we found podman can't pull containers from a regist
Could we go on a more generic fashion?
Something like "Supported container engines must work on their basic features
on all the blocker deliverables were they are installed by default"
Our supported engines are, podman? cri-o?
On August 29, 2019 6:40:21 PM GMT+02:00, Matthew Miller
wrote:
>O
On Thu, Aug 29, 2019 at 11:45:44AM -0400, Dusty Mabe wrote:
> Certainly anywhere where podman is shipped on media. Does podman ship in the
> server DVD? yes [1]
> It looks like workstation also ships it if I'm reading the logs [2] correctly.
Yeah, it's needed for Toolbox, which is a vital feature
On 8/29/19 11:13 AM, Adam Williamson wrote:
> On Thu, 2019-08-29 at 10:33 -0400, Dusty Mabe wrote:
>> I don't know the formal process for proposal
>
> Congratulations, you found it - mail this list, ideally including at
> least one of the strings 'criter' or 'propos'. :P
>
>> but here is a sho
On Thu, 2019-08-29 at 10:33 -0400, Dusty Mabe wrote:
> I don't know the formal process for proposal
Congratulations, you found it - mail this list, ideally including at
least one of the strings 'criter' or 'propos'. :P
> but here is a shot at a bare minimum
> start for trying to add containers t
> I don't know the formal process for proposal but here is a shot at a bare
> minimum
> start for trying to add containers to the existing release criteria.
There is at least one deliverable that delivers podman in the image
(Silverblue). Silverblue
isn't release blocking. I don't know if there
I don't know the formal process for proposal but here is a shot at a bare
minimum
start for trying to add containers to the existing release criteria. This is a
suggestion
after we found podman can't pull containers from a registry in f31 [1].
New section for Containers and Container tools:
- A
OLD: Fedora-Rawhide-20190828.n.0
NEW: Fedora-Rawhide-20190829.n.0
= SUMMARY =
Added images:2
Dropped images: 0
Added packages: 23
Dropped packages:24
Upgraded packages: 91
Downgraded packages: 0
Size of added packages: 209.44 MiB
Size of dropped packages
No missing expected images.
Compose FAILS proposed Rawhide gating check!
9 of 45 required tests failed, 6 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Unsatisfied gating requirements that could not be mapped to openQA tests:
MISSING: fedora.Wor
over last couple days, several installations of pre-release fedora
images 201908{26,28,29} on this dell tower have produced the following
two symptoms.
first, this is a dual HD system and, when selecting the disk layout,
i would select both HDs, then select "I would like to make additional
sp
16 matches
Mail list logo
