are nightly-composes/desktop/ built from F14 branch?

[Marius Andreiana]

Hello,

We're wondering if
http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/
are built from F14 branch or rawhide. Could somebody clarify this?

Reason: A fix for https://bugzilla.redhat.com/show_bug.cgi?id=528232 was
committed, but it doesn't appear fixed.

Thanks,
M

[Adam Williamson]

On Sun, 2010-09-12 at 00:43 +0300, Marius Andreiana wrote:
>  Hello,
>  
>  We're wondering if
>  http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/
>  are built from F14 branch or rawhide. Could somebody clarify this? 
dist-f14.

>  Reason: A fix for https://bugzilla.redhat.com/show_bug.cgi?id=528232
>  was committed, but it doesn't appear fixed.  
Because a kernel update hasn't gone to dist-f14 - in fact, one hasn't
even been submitted as an update - since 2010-09-28:

https://admin.fedoraproject.org/updates/kernel-2.6.35.4-12.fc14

for a Branched release, 'a fix was committed' isn't enough. The package
has to be built (which obviously applies to any branch), and then
submitted as an update (which doesn't apply to Rawhide).
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net

[Marius Andreiana]

On Sun, Sep 12, 2010 at 1:20 AM, Adam Williamson <awilliam(a)redhat.com&gt;wrote:

>  > Reason: A fix for
> https://bugzilla.redhat.com/show_bug.cgi?id=528232
>  > was committed, but it doesn't appear fixed.
>
>  Because a kernel update hasn't gone to dist-f14 - in fact, one hasn't
>  even been submitted as an update - since 2010-09-28:
>  
Could this bug be added to F14 blocker bugs ?

[Adam Williamson]

On Sun, 2010-09-12 at 12:05 +0300, Marius Andreiana wrote:
>  On Sun, Sep 12, 2010 at 1:20 AM, Adam Williamson
> <awilliam(a)redhat.com&gt;
>  wrote:
>          > Reason: A fix for
>          https://bugzilla.redhat.com/show_bug.cgi?id=528232
>          > was committed, but it doesn't appear fixed.
>          
>          
>          Because a kernel update hasn't gone to dist-f14 - in fact, one
>          hasn't
>          even been submitted as an update - since 2010-09-28:
>  
>  
>  Could this bug be added to F14 blocker bugs ? 
You can nominate it for blocker status by setting it to block the bug
'F14Blocker'. Then when we get to reviewing the final release blocker
bugs we'll argue about whether it's a blocker or not and make a
decision. You can nominate it to block the beta by setting it to block
'F14Beta'. In practice, since a fix has been committed, I wouldn't worry
about it; there's no way we'll ship F14 final with the current kernel,
we'll take at least one more update from the kernel team before we ship,
and that build - whichever it happens to be - will certainly be one that
includes this fix. But if you want to be super safe, by all means
propose it as a blocker.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net