Integrate dormant fedora-legacy in up2date/yum packages before EOL

Axel Thimm Axel.Thimm at ATrpms.net
Mon Aug 9 11:14:17 UTC 2004


On Mon, Aug 09, 2004 at 03:00:12AM -0300, Alexandre Oliva wrote:
> On Aug  7, 2004, Jesse Krijthe <j.krijthe at tiscali.nl> wrote:
> 
> > How about doing an update of these configs say 2 months before a release
> > turns EOL.
> 
> Why not do so as the last update issued for an FC release?

That would be already a nice option, but considering that probably all
FC users are modding their yum.conf an update will drop the new
yum.conf onto an yum.conf.rpmnew file which may go unnoticed (unlike
rpm/apt most Fedora update tools don't mention this upon upgrades).

Having the dormant fedora legacy entry from the very beginning
uncommented would be the smoothest and safest transition mechanism,
but it will generate unneccessary hits & load on the fedora legacy
server. OTOH it is only one hit (an empty header.info) per yum
invocation, so it is probably still managable.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-devel-list/attachments/20040809/c3583afc/attachment.sig>


More information about the fedora-devel-list mailing list