Hi,
As announced (https://lists.centos.org/pipermail/centos-announce/2018-December/023082.html) , CentOS 7.6.1810 is now available and realeased for the following arches : x86_64, aarch64, ppc64le, armhfp So that release is now the default one for the CBS/koji build tasks (and all koji regen-repos tasks are currently running)
That means that for your next builds, you'll be building against 7.6.1810 (even if technically that was already the case with the 7.5.1804+updates+CR repositories)
That should also mean the end of the "freeze" wrt pushing tagged pkgs for release to mirror.centos.org
On 03/12/2018 17:04, Fabian Arrotin wrote:
Hi,
As announced (https://lists.centos.org/pipermail/centos-announce/2018-December/023082.html) , CentOS 7.6.1810 is now available and realeased for the following arches : x86_64, aarch64, ppc64le, armhfp So that release is now the default one for the CBS/koji build tasks (and all koji regen-repos tasks are currently running)
That means that for your next builds, you'll be building against 7.6.1810 (even if technically that was already the case with the 7.5.1804+updates+CR repositories)
That should also mean the end of the "freeze" wrt pushing tagged pkgs for release to mirror.centos.org
Just to add that , due to upstream decision, some packages are now removed from the base os, and so can't be found anymore So please read the upstream Release Notes about which pkgs were deprecated and removed as that can mean also changing the way you build on CBS/koji.
One example that was clear : I saw one build failing now because :
DEBUG util.py:417: Error: No Package found for golang >= 1.8
That's because golang was removed, so if your build needs it, you need to tag-build one of the golang build that exists in CBS (fyi)
hi, is there any description (or is there anybody who can told me) how file under centos/7/os/x86_64/images/pxeboot/ especially initrd.img are generated? which tools are you using? thanks in advance. regards.
On Mon, Dec 3, 2018 at 5:16 PM Fabian Arrotin arrfab@centos.org wrote:
Hi,
As announced ( https://lists.centos.org/pipermail/centos-announce/2018-December/023082.html ) , CentOS 7.6.1810 is now available and realeased for the following arches : x86_64, aarch64, ppc64le, armhfp So that release is now the default one for the CBS/koji build tasks (and all koji regen-repos tasks are currently running)
That means that for your next builds, you'll be building against 7.6.1810 (even if technically that was already the case with the 7.5.1804+updates+CR repositories)
That should also mean the end of the "freeze" wrt pushing tagged pkgs for release to mirror.centos.org -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 04/12/2018 13:49, Farkas Levente wrote:
hi, is there any description (or is there anybody who can told me) how file under centos/7/os/x86_64/images/pxeboot/ especially initrd.img are generated? which tools are you using? thanks in advance. regards.
nothing special : lorax and it's all documented too :-)
Hi Fabian,
It looks like the sources are not yet present on vault.centos.org. is there an ETA for that?
Thanks,
Jacco
On Monday, 03 December, 2018 17:04 CET, Fabian Arrotin arrfab@centos.org wrote:
Hi,
As announced (https://lists.centos.org/pipermail/centos-announce/2018-December/023082.html) , CentOS 7.6.1810 is now available and realeased for the following arches : x86_64, aarch64, ppc64le, armhfp So that release is now the default one for the CBS/koji build tasks (and all koji regen-repos tasks are currently running)
That means that for your next builds, you'll be building against 7.6.1810 (even if technically that was already the case with the 7.5.1804+updates+CR repositories)
That should also mean the end of the "freeze" wrt pushing tagged pkgs for release to mirror.centos.org -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 05/12/2018 12:01, Jacco Ligthart wrote:
Hi Fabian,
It looks like the sources are not yet present on vault.centos.org. is there an ETA for that?
Thanks,
Jacco
Usually Johnny waits some days before pushing those to vault to let your mirror network going back to normal mode, and then it's possible for him to push to vault nodes.
OTOH, as everything is available through git as authoritative source, and also that src.rpm pkgs are also pushed to https://buildlogs.centos.org for *all* builds and *all* arches, the only difference would be on vault to have the same src.rpm pkg signed
BTW, we start suffering from some HDD space on donated nodes with the mirror network, especially for roles like debuginfo.centos.org and vault.centos.org (containing also now SIGs src.rpm, so much more than just the centos distro those days) : so we have to remove some nodes and so the load is then shared between less nodes, meaning that it's not sustainable .. I was even considering announcing shutting down those services, due to lack of bandwidth/space .....
-
Fabian Arrotin -
Farkas Levente -
Jacco Ligthart