On 08/16/2011 11:30 AM, Dennis Jacobfeuerborn wrote:
> Is it really worth the hassle to add and remove the repo just to get the
> packages a few days early?
you need to add it in, one time. You wont need to remove anything. As
long as you do not edit that file it will be managed by
centos-release-5-7 and centos-release-cr-5-7 etc.
Because, as step 1, we did not want to default everyone over into moving
a machine's state unexpectedly : we created this one time manual step.
Depending on how things go and how people feel we could potentially
remove that manual step in the future.
The important thing here is that you have an option to either get onto
or not get onto the cr/ release process, and you can opt out whenever
you like by removing the file. But as long as you are 'in', you wont
need to do anything manual from this point on.
And yes, I think its worth getting the security fix's at least out to as
many people as possible, as quickly as possible. Segregating these
security fixs, their build deps and their link chains is super complex
and in many cases of dubious value in the EL release frame. Which is why
we have the security, bugfix and enhancement updates rolled in here.
> What bugs me about this is the manual overhead for adding and removing the
> repo on the systems. I presume when TUV 5.8 gets released and I want to be
> up-to-date I have to add the CentOS cr repo again and then remove it when
> CentOS 5.8 is out?
no, if you leave the centos-release-cr installed on your machine, you
wont need to do anything. just keep the yum updates going
> That way people interested in the rolling release would only have to enable
> this only once on their systems and stay on this rolling release train
> until they deliberately deactivate the repo again.
What we have now should be pretty much the same thing. You can make a
decision based on site and system role policy, once you opt-in, you stay
opted-in.
- KB
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
08-17-2011, 08:31 AM
Kai Schaetzl
cr repository when running your own mirror
Karanbir Singh wrote on Tue, 16 Aug 2011 12:21:06 +0100:
> You wont need to remove anything. As
> long as you do not edit that file it will be managed by
> centos-release-5-7 and centos-release-cr-5-7 etc.
Well, surely those people using their own mirrors will have to do
something ...
Kai
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
08-17-2011, 04:21 PM
Karanbir Singh
cr repository when running your own mirror
On 08/17/2011 09:31 AM, Kai Schaetzl wrote:
>> You wont need to remove anything. As
>> long as you do not edit that file it will be managed by
>> centos-release-5-7 and centos-release-cr-5-7 etc.
>
> Well, surely those people using their own mirrors will have to do
> something ...
Sure, but then if someone is going to hardwire urls to point at specific
content, its reasonable to expect them to manage that content locally.
the /cr/ repo isnt going to go away, the content from inside it will, so
depending on how you rehash the baseurl, leave the $releasever tag in,
and things should be fine. As long as you mirror the entire repo
structure from centos.org
- KB
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
08-17-2011, 05:42 PM
cr repository when running your own mirror
On Wed, 17 Aug 2011, Karanbir Singh wrote:
> On 08/17/2011 09:31 AM, Kai Schaetzl wrote:
>>> You wont need to remove anything. As
>>> long as you do not edit that file it will be managed by
>>> centos-release-5-7 and centos-release-cr-5-7 etc.
>>
>> Well, surely those people using their own mirrors will have to do
>> something ...
>
> Sure, but then if someone is going to hardwire urls to point at specific
> content, its reasonable to expect them to manage that content locally.
>
> the /cr/ repo isnt going to go away, the content from inside it will, so
> depending on how you rehash the baseurl, leave the $releasever tag in,
> and things should be fine. As long as you mirror the entire repo
> structure from centos.org
So to be clear, all you are going to do is empty the cr repo and have an empty
set of repodata in its place so that yum does not throw errors. Is this
correct?
If this is true, is it your plan to NOT update the centos-release-cr-5* rpm
with each point release?
Regards,
--
Tom me@tdiehl.org Spamtrap address me123@tdiehl.org
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
08-18-2011, 11:15 PM
Ross Walker
cr repository when running your own mirror
On Aug 17, 2011, at 12:21 PM, Karanbir Singh <mail-lists@karan.org> wrote:
> On 08/17/2011 09:31 AM, Kai Schaetzl wrote:
>>> You wont need to remove anything. As
>>> long as you do not edit that file it will be managed by
>>> centos-release-5-7 and centos-release-cr-5-7 etc.
>>
>> Well, surely those people using their own mirrors will have to do
>> something ...
>
> Sure, but then if someone is going to hardwire urls to point at specific
> content, its reasonable to expect them to manage that content locally.
>
> the /cr/ repo isnt going to go away, the content from inside it will, so
> depending on how you rehash the baseurl, leave the $releasever tag in,
> and things should be fine. As long as you mirror the entire repo
> structure from centos.org
I wonder if this wouldn't cause a lot more unnecessary download traffic from the mirrors as most people who replicate the tree will automatically pull in /cr even if they don't need/want it?
For real rolling releases I might have just created a /cr repo at the top level for each branch like someone else suggested, but instead of wiping it out between point releases just keep throwing the updated packages in there and createrepo it.
You would have dozens of versions of the same package in there after a while, but on the bright side on can 'yum downgrade' a package all the way back to 5.0. Of course you would probably purge packages older then X-Y revisions old to keep things sane.
Just my $.02
-Ross
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
08-18-2011, 11:20 PM
Always Learning
cr repository when running your own mirror
I successfully upgraded desktops using the CR repo and 'yum update'.
However after installing the CR repo on 2 VPS's running C 5.6 and doing
a reboot I got a load of Kernel messages, for the first time ever.
--------------------------
--------------------- Kernel Begin ------------------------
WARNING: Kernel Errors Present
rtc_cmos: probe of rtc_cmos failed with error -16 ...: 1 Time(s)
cr repository when running your own mirror
