I don’t have CR enabled and a heap of available updates means CentOS 6.7
has been released or what?
Did I miss the announcement?
7 thoughts on - 6.7
6.7 is there most places … since we have more than 500 external mirrors (right now 593) not all of them are updated. (looks like 4%
still are not completely updated)
If we announce too soon, people look for it and don’t get it … if we wait a bit longer, some people see it on the mirrors before the announcement.
Announcement should follow soonish, in the mean time .. here are the release notes:
(where the 6.7 rpms for CR were released {into 6.6} … SCORE)
That is only for NEW packages built … not things carried over from older trees.
Thanks, Johnny Hughes
Well,
As releasing the main distro is using quite some bandwidth (during release, the aggregated bandwidth for our msync nodes is ~4Gbits/s, during several hours), we wait for the msync network to go back to normal mode, before pushing the SRPMS to Vault.
6.6 has already been copied to vault, so will disappear from mirror.CentOS.org soon. SRPMS will be synced to vault soon too, probably later today.
because that update was in 6.6 updates, not 6.7 updates. They (Red Hat)
released it before they released released 6.7. It is carried forward from 6.6. Red Hat included an older version on their 6.7 isos.
I will get all the SRPMs in the right places .. but they are all somewhere else in vault right now, so nothing is missing. They just need to be gathered from the other places and hardlinked into the 6.7 trees.
7 thoughts on - 6.7
6.7 is there most places … since we have more than 500 external mirrors (right now 593) not all of them are updated. (looks like 4%
still are not completely updated)
If we announce too soon, people look for it and don’t get it … if we wait a bit longer, some people see it on the mirrors before the announcement.
Announcement should follow soonish, in the mean time .. here are the release notes:
http://wiki.CentOS.org/Manuals/ReleaseNotes/CentOS6.7
Thanks, Johnny Hughes
what about the src.rpms? it seems http://vault.CentOS.org/6.7/os/ and http://vault.CentOS.org/6.7/cr/Source/ is empty and while http://vault.CentOS.org/6.7/updates/Source/SPackages/ also seems to very outdated.
thanks in advance. regards.
I think it would make more sense to wait for the actual release announcement first before asking about missing files.
Regards,
Denis
6.7/updates SRPMs are not outdated .. they are new updates for 6.7
6.7/cr does not get populated until 6.8 is released, of course it is empty
now, if you look here:
http://vault.CentOS.org/6.6/cr/Source/SPackages/
(where the 6.7 rpms for CR were released {into 6.6} … SCORE)
That is only for NEW packages built … not things carried over from older trees.
Thanks, Johnny Hughes
Well,
As releasing the main distro is using quite some bandwidth (during release, the aggregated bandwidth for our msync nodes is ~4Gbits/s, during several hours), we wait for the msync network to go back to normal mode, before pushing the SRPMS to Vault.
6.6 has already been copied to vault, so will disappear from mirror.CentOS.org soon. SRPMS will be synced to vault soon too, probably later today.
Cheers,
–
eg: there is a
6.7/updates/x86_64/Packages/firefox-38.1.0-1.el6.CentOS.x86_64.rpm for which there is no src.rpm in http://vault.CentOS.org/6.7/updates/Source/SPackages/ so that’s what i mean is outdated.
because that update was in 6.6 updates, not 6.7 updates. They (Red Hat)
released it before they released released 6.7. It is carried forward from 6.6. Red Hat included an older version on their 6.7 isos.
I will get all the SRPMs in the right places .. but they are all somewhere else in vault right now, so nothing is missing. They just need to be gathered from the other places and hardlinked into the 6.7 trees.