kernel in rawhide (f15) : crash

"Jóhann B. Guðmundsson" johannbg at
Wed Jan 26 17:42:17 UTC 2011

On 01/26/2011 05:10 PM, Kevin Fenzi wrote:
> On Wed, 26 Jan 2011 15:14:40 +0000
> "Jóhann B. Guðmundsson"<johannbg at>  wrote:
>> On 01/26/2011 02:42 PM, Bruno Wolff III wrote:
>>> On Wed, Jan 26, 2011 at 13:49:41 +0000,
>>>     "\"Jóhann B. Guðmundsson\""<johannbg at>   wrote:
>>>> Hum I'm not so sure releng is using koji repo for nightly spins I
>>>> think they actually need to get pushed somewhere before they get
>>>> picked up what I'm meaning is that when you build something in
>>>> koji and that build was successful it will get pulled into on of
>>>> the nightly spins for that day.
>>> Just as a side note, releng isn't directly responsible for the
>>> nightly composes, it's really under infrastructure. Kevin Fenzi
>>> does most or all of the maintenance. I'm not sure who his backup is
>>> for this.
> Nightly composes are using rawhide currently.
> So, the only difference between that and a koji static repo is that
> it's been pushed out in a rawhide. Using koji static repos could result
> in some spins using some bits and others using other bits as builds
> landed, which I think could be confusing. Also, things that appear in
> koji static repos might be broken to the point where they are untagged
> and don't appear in rawhide the next day (see perl today), which might
> result in some spins building and using them before they are untagged.
> So, I think rawhide is the right thing to use. ;)

So how does this work do build get automatically tagged ( good ) which 
maintainers then need to untag if they dont want to push it or is it the 
otherway around maintainers need to tag builds for rawhide ( bad ) which 
then they may or may not forget to do?


More information about the test mailing list