Johnny Hughes <johnny@xxxxxxxxxx> schrieb am 26.08.2009 15:56:08:
> Karanbir Singh wrote:
> > On 08/26/2009 02:25 PM, Frank.Brodbeck@xxxxxxxxxx wrote:
> >> Nice... same problem here. yum upgrade probably sets a new
> >> /etc/yum.repos.d/CentOS-Base.repo in place,
> >
> > That should not happen, if you have edited or changes the .repo file
> > yourself. A yum update should leave you with a .rpmnew file to handle
> > as you wish. If this is not the case, and you have a situation where
the
> > .repo file is being replaced by the yum update - please file an issue
> > report at bugs.centos.org.
> >
> > The only place where this might be acceptable is if you have a yum
> > plugin like mergeconf that is trying to but failing at doing the right
> > thing. An issue report for that, if that is indeed the case.
> >
>
> One important thing is NOT to change the NAME of the .repo file ... Or,
> if you do change the name, make sure that you put a CentOS-Base.repo
> file there so that a new one is not placed in your yum.repos.d directory
> (as KB said, if there is a modified file, it will not be replaced ...
> if there is no file with that name, a new one will be put there).
Boy, now that's kinda embarrasing. While provisioning I really do mv the
CentOS-Base.repo out of the way, no wonder a new .repo showed up
after my upgrade. Sorry for the noise.
Frank.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
