I would also prefer to standardize everything, unless necessary.<br>But for now Glezos requests that publictest4 be upgraded to F7, since he needs some packages that exist in F7 and not in FC6.<br><br><br>Thanks,<br>Paulo<br>
<br><br><div><span class="gmail_quote">On 6/7/07, <b class="gmail_sendername">Toshio Kuratomi</b> <<a href="mailto:a.badger@gmail.com">a.badger@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, 2007-06-07 at 11:53 -0400, Jesse Keating wrote:<br>> On Thursday 07 June 2007 11:49:57 Mike McGrath wrote:<br>> > I agree, I had no plans on upgrading any of our RHEL boxes (except for<br>> > cvs and db1 but will stay in the RHEL upgrade path). For those of you
<br>> > that are new on the list we've had a lot of discussions about this in<br>> > the past. Our team, for the most part, agrees that its about picking<br>> > the right tool for the job. For boxes that don't need brand new
<br>> > technologies (like cvs) its nice to be able to set them up and forget<br>> > about them. But for some boxes that do need the latest and greatest<br>> > (like our builders) we've always had and kept them on Fedora.
<br>><br>> With RHEL5 out, I question the need for Fedora on the builders. In fact,<br>> before the merge, all the internal Core builders were running RHEL4. Can we<br>> not use RHEL5 on the builders now?<br>
><br>Will we want to pull in new features for the builders? Something like a<br>change in rpm is needed for a new version of mock. We want that change<br>and so we need to upgrade?<br><br>I just want to avoid flip-flopping between RHEL and Fedora.
<br><br>-Toshio<br><br>_______________________________________________<br>Fedora-infrastructure-list mailing list<br><a href="mailto:Fedora-infrastructure-list@redhat.com">Fedora-infrastructure-list@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list">
https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list</a><br><br><br></blockquote></div><br>