Missing expected images:
Atomic raw-xz x86_64
Kde raw-xz armhfp
Images in this compose but not Rawhide-20160308.n.0:
Cloud vagrant-libvirt x86_64
Cloud vagrant-virtualbox x86_64
Cloud raw-xz i386
Cloud vagrant-virtualbox i386
Cloud vagrant-libvirt i386
Cloud qcow2 i386
Cloud qcow2 x86_64
Cloud r
The following Fedora 24 Security updates need testing:
Age URL
0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-4b55f00d00
samba-4.4.0-0.7.rc4.fc24
0 https://bodhi.fedoraproject.org/updates/FEDORA-2016-9d6b6d0689
php-pecl-http-2.5.6-1.fc24
0 https://bodhi.fedoraproject.org/
OLD: Fedora-Rawhide-20160308.n.0
NEW: Fedora-Rawhide-20160309.n.2
= SUMMARY =
Added packages: 6
Dropped packages:1
Upgraded packages: 154
Downgraded packages: 0
Size of added packages: 1.29 MiB
Size of dropped packages:433.54 KiB
Size of upgraded packages: 1.63 GiB
OLD: Fedora-24-20160308.n.0
NEW: Fedora-24-20160309.n.1
= SUMMARY =
Added packages: 0
Dropped packages:2
Upgraded packages: 32
Downgraded packages: 1
Size of added packages: 0.00 B
Size of dropped packages:1.50 MiB
Size of upgraded packages: 85.41 MiB
Size of
On Wed, 2016-03-09 at 13:57 -0700, Chris Murphy wrote:
>
> So if "RC-1.8" passes all tests and is a go, how is this renamed? Or
> is it not renamed?
> I assume you don't want to do a production compose at this point
> because then it's a compose that isn't tested, while ostensibly
> identical the
On Wed, 2016-03-09 at 13:52 -0500, John Dulaney wrote:
> > == 2. N indicates TC/RC, R indicates number ==
> > > >
> > > > In this scheme, we'd build e.g. 'Alpha 1.1' (Alpha TC1), 'Alpha
> > > > 1.2'
> > > > (Alpha TC2), 'Alpha 2.1' (Alpha RC1), 'Alpha 2.2' (Alpha RC2).
> > > >
> > > > This seems
On Wed, 2016-03-09 at 13:47 -0700, Chris Murphy wrote:
> a. Work with Pungi's currently-expected label format
> In this format option, MILESTONE-N.R would be
> MILESTONE= alpha, beta, RC
> N = arbitrary integer
> R = arbitrary integer
>
> Can N and R be 0? Or must it be 1-9?
At least according t
On Wed, Mar 9, 2016 at 1:47 PM, Chris Murphy wrote:
> On Wed, Mar 9, 2016 at 11:16 AM, Adam Williamson
> wrote:
>> Hi folks!
>>
>> So we're now frozen for Alpha and we have an anaconda build with
>> blocker fixes in updates-testing...I guess this means it's a good time
>> to decide what to do abo
On Wed, Mar 9, 2016 at 11:16 AM, Adam Williamson
wrote:
> Hi folks!
>
> So we're now frozen for Alpha and we have an anaconda build with
> blocker fixes in updates-testing...I guess this means it's a good time
> to decide what to do about milestone builds with Pungi 4. :)
>
> I'm assuming here tha
> Subject: Re: Pungi 4 milestone builds: proposals
> From: adamw...@fedoraproject.org
> To: test@lists.fedoraproject.org; rel-...@lists.fedoraproject.org
> Date: Wed, 9 Mar 2016 10:33:41 -0800
>
> On Wed, 2016-03-09 at 13:26 -0500, John Dulaney wrote:
>> .
>>>
>>>
>>> == 2. N indicates TC/RC, R ind
On Wed, 2016-03-09 at 13:26 -0500, John Dulaney wrote:
> .
> >
> >
> > == 2. N indicates TC/RC, R indicates number ==
> >
> > In this scheme, we'd build e.g. 'Alpha 1.1' (Alpha TC1), 'Alpha 1.2'
> > (Alpha TC2), 'Alpha 2.1' (Alpha RC1), 'Alpha 2.2' (Alpha RC2).
> >
> > This seems like the close
.
>
> == 2. N indicates TC/RC, R indicates number ==
>
> In this scheme, we'd build e.g. 'Alpha 1.1' (Alpha TC1), 'Alpha 1.2'
> (Alpha TC2), 'Alpha 2.1' (Alpha RC1), 'Alpha 2.2' (Alpha RC2).
>
> This seems like the closest possible way to map to our current system.
> Again it's a bit weird at Final
Hi folks!
So we're now frozen for Alpha and we have an anaconda build with
blocker fixes in updates-testing...I guess this means it's a good time
to decide what to do about milestone builds with Pungi 4. :)
I'm assuming here that we're going to use more or less the same "TCs
and RCs" approach for
Fedora-SoaS-Live-x86_64-24-20160308.0.iso now has sugar
108.1 and renders correctly but liveinst crashes and NM does not connect
* satellit_e qemu/kvm f23
On 03/09/2016 09:47 AM, Adam Williamson wrote:
[again, an event was created but the notification email got lost. I've
figured out why now -
[again, an event was created but the notification email got lost. I've
figured out why now - they're being sent from an address that wasn't
subscribed to the list. I've fixed that, so future notification emails
should work. Again sending this one manually.]
Announcing the creation of a new nightly
Hello everyone,
I'm working on beginner QA and Automation training curricula for a local hack
school in Sofia (https://github.com/atodorov/QA-101). I'm looking for examples
of badly written bug reports which students can read and discuss what
information is missing from them (e.g. why are they
16 matches
Mail list logo
