I wanted to provide a bit of warning for upcoming aarch64/arm64 repository changes, as they may impact users with local mirrors.
1. I'm re-spinning the install media based on newer kernel patches I've pulled in from some vendors. This will allow the installer to support some of the newer hardware that's recently become available.
2. In order to enable the aarch64 community builder, I've had to more closely align some of the aarch64 packages with the main distribution packages. This is primarily to deal with how noarch packages are handled.
The end result of this change is that the repo file will now contain two gpg keys, so if you've set up your own mirror and customized the repo file, you'll need to modify your updated file similarly.
I expect to be able to release the updated tree early next week so these changes will happen reasonably soon.
On 2016-03-16 12:16, Jim Perrin wrote:
I wanted to provide a bit of warning for upcoming aarch64/arm64 repository changes, as they may impact users with local mirrors.
- I'm re-spinning the install media based on newer kernel patches I've
pulled in from some vendors. This will allow the installer to support some of the newer hardware that's recently become available.
- In order to enable the aarch64 community builder, I've had to more
closely align some of the aarch64 packages with the main distribution packages. This is primarily to deal with how noarch packages are handled.
The end result of this change is that the repo file will now contain two gpg keys, so if you've set up your own mirror and customized the repo file, you'll need to modify your updated file similarly.
I expect to be able to release the updated tree early next week so these changes will happen reasonably soon.
Will there be an updated centos-release package that brings those changes transparently via yum update? Or is manual intervention required?
Also, you mention respinning the installer image. Can you please point me at the scripts used for building the installer ISO?
Many thanks.
Gordan
On 03/16/2016 07:27 AM, Gordan Bobic wrote:
Will there be an updated centos-release package that brings those changes transparently via yum update? Or is manual intervention required?
Yes, but it's only transparent if the .repo files aren't modified. I don't want to forcibly overwrite people's altered configs.
Also, you mention respinning the installer image. Can you please point me at the scripts used for building the installer ISO?
It's all just lorax and mkisofs. We went through some of the discussion on the -devel list late last year. You can follow it here ->
https://lists.centos.org/pipermail/centos-devel/2015-December/014150.html