On 07/12/2011 11:49 PM, Markus Falb wrote: > On 11.7.2011 17:51, Karanbir Singh wrote: >> On 07/11/2011 09:26 AM, Farkas Levente wrote: >>> unsupported method upstream, right. >>> working in upstream, right. >>> working in centos, not. >> To me, 'it' amounts to being able to upgrade from >> C5 to C6 or EL5 to EL6, without a wipe+reinstall. And 'it' works in >> just about exactly the same way on CentOS as on RHEL - you need to >> custom build rpm, its dep chain. then get py26 in place, with yum that >> uses that py26 ( on c5 ), then go through 2 reboot cycles in order to >> make the process work. At the second boot stage, you need the >> centos-release rpm to be replaced. Also important at this stage is that >> having a $releasever at '5' does not break your machine, so a manual >> choice being needed to come into effect for $releasecer to move to '6' >> isnt a bad thing, I'd even venture a bit closer to the edge and say its >> a 'feature'. > What happened with the > "aims to be 100% binary compatible" > goal of centos ? I am not 100% sure but I'd say we are hit by a side effect of the fact that centos-release.el5 has epoch = 10 while redhat-release in rhel 5 has none.