Hi,
As discussed on the list, we wanted to push 7.4.1708 first to CBS/Koji and at the same time to CI (so that what's built against a specific tree can be tested against the same set of pkgs in CI)
We'll so make it 7.4.7108 available within CBS in the next hours, and for *all* arches actually covered within CBS.
That means that we'll switch (before it's pushed to external mirrors and so be announced) the buildroots to start using the following repositories:
7.4.1708/{os,updates,extras}
That will be so done in parallel for x86_64,aarch64,ppc64,ppc64le .
We're just launching some sanity tests against those trees (all in place) and then we'll open this in CBS/Koji (plenty of tasks for this as Koji will have to rebuild internal metadata for those mirrors, aka "koji regen-repo $buildroot")
We'll post an update here when it will be switched and so active. That will let some time for SIGs to build some of the pkgs that were waiting/depending on 7.4.1708 pkgs from the distro, and so be "ready" before we go GA with 7.4.1708 (in the next days)
Hope this will help
2017-09-08 11:10 GMT+02:00 Fabian Arrotin arrfab@centos.org:
Hi,
As discussed on the list, we wanted to push 7.4.1708 first to CBS/Koji and at the same time to CI (so that what's built against a specific tree can be tested against the same set of pkgs in CI)
We'll so make it 7.4.7108 available within CBS in the next hours, and for *all* arches actually covered within CBS.
That means that we'll switch (before it's pushed to external mirrors and so be announced) the buildroots to start using the following repositories:
7.4.1708/{os,updates,extras}
That will be so done in parallel for x86_64,aarch64,ppc64,ppc64le .
We're just launching some sanity tests against those trees (all in place) and then we'll open this in CBS/Koji (plenty of tasks for this as Koji will have to rebuild internal metadata for those mirrors, aka "koji regen-repo $buildroot")
We'll post an update here when it will be switched and so active. That will let some time for SIGs to build some of the pkgs that were waiting/depending on 7.4.1708 pkgs from the distro, and so be "ready" before we go GA with 7.4.1708 (in the next days)
Hope this will help
Still failing to build qemu-kvm-ev:
DEBUG util.py:417: Error: No Package found for libfdt-devel >= 1.4.3 DEBUG util.py:417: Error: No Package found for rdma-core-devel
http://cbs.centos.org/kojifiles/work/tasks/4750/224750/root.log
-- Fabian Arrotin The CentOS Project | http://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 11/09/17 07:30, Sandro Bonazzola wrote:
2017-09-08 11:10 GMT+02:00 Fabian Arrotin <arrfab@centos.org mailto:arrfab@centos.org>:
Hi, As discussed on the list, we wanted to push 7.4.1708 first to CBS/Koji and at the same time to CI (so that what's built against a specific tree can be tested against the same set of pkgs in CI) We'll so make it 7.4.7108 available within CBS in the next hours, and for *all* arches actually covered within CBS. That means that we'll switch (before it's pushed to external mirrors and so be announced) the buildroots to start using the following repositories: 7.4.1708/{os,updates,extras} That will be so done in parallel for x86_64,aarch64,ppc64,ppc64le . We're just launching some sanity tests against those trees (all in place) and then we'll open this in CBS/Koji (plenty of tasks for this as Koji will have to rebuild internal metadata for those mirrors, aka "koji regen-repo $buildroot") We'll post an update here when it will be switched and so active. That will let some time for SIGs to build some of the pkgs that were waiting/depending on 7.4.1708 pkgs from the distro, and so be "ready" before we go GA with 7.4.1708 (in the next days) Hope this will helpStill failing to build qemu-kvm-ev:
DEBUG util.py:417: Error: No Package found for libfdt-devel >= 1.4.3 DEBUG util.py:417: Error: No Package found for rdma-core-devel
http://cbs.centos.org/kojifiles/work/tasks/4750/224750/root.log
Yes, because it's not there (yet) : I initially thought that we'd be able to have it available for *all* arches last friday but it wasn't the case :-( (worth also noting that I initially also said we'd post an updated when it would be done, which we never did)
So after a small discussion it was decided to post-pone that action and so be sure that all arches would have time to catch up, which is now done, so the plan is to discuss this during CBS meeting today, and have it available directly after, then let some time for SIGs to build/test artifacts and then official GA for 7.4.1708.
2017-09-11 8:02 GMT+02:00 Fabian Arrotin arrfab@centos.org:
On 11/09/17 07:30, Sandro Bonazzola wrote:
2017-09-08 11:10 GMT+02:00 Fabian Arrotin <arrfab@centos.org mailto:arrfab@centos.org>:
Hi, As discussed on the list, we wanted to push 7.4.1708 first toCBS/Koji
and at the same time to CI (so that what's built against a specifictree
can be tested against the same set of pkgs in CI) We'll so make it 7.4.7108 available within CBS in the next hours, and for *all* arches actually covered within CBS. That means that we'll switch (before it's pushed to external mirrorsand
so be announced) the buildroots to start using the following repositories: 7.4.1708/{os,updates,extras} That will be so done in parallel for x86_64,aarch64,ppc64,ppc64le . We're just launching some sanity tests against those trees (all in place) and then we'll open this in CBS/Koji (plenty of tasks forthis as
Koji will have to rebuild internal metadata for those mirrors, aka"koji
regen-repo $buildroot") We'll post an update here when it will be switched and so active.That
will let some time for SIGs to build some of the pkgs that were waiting/depending on 7.4.1708 pkgs from the distro, and so be "ready" before we go GA with 7.4.1708 (in the next days) Hope this will helpStill failing to build qemu-kvm-ev:
DEBUG util.py:417: Error: No Package found for libfdt-devel >= 1.4.3 DEBUG util.py:417: Error: No Package found for rdma-core-devel
http://cbs.centos.org/kojifiles/work/tasks/4750/224750/root.log
Yes, because it's not there (yet) : I initially thought that we'd be able to have it available for *all* arches last friday but it wasn't the case :-( (worth also noting that I initially also said we'd post an updated when it would be done, which we never did)
So after a small discussion it was decided to post-pone that action and so be sure that all arches would have time to catch up, which is now done, so the plan is to discuss this during CBS meeting today, and have it available directly after, then let some time for SIGs to build/test artifacts and then official GA for 7.4.1708.
Ok, thanks
-- Fabian Arrotin The CentOS Project | http://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 08/09/17 11:10, Fabian Arrotin wrote:
Hi,
As discussed on the list, we wanted to push 7.4.1708 first to CBS/Koji and at the same time to CI (so that what's built against a specific tree can be tested against the same set of pkgs in CI)
We'll so make it 7.4.7108 available within CBS in the next hours, and for *all* arches actually covered within CBS.
That means that we'll switch (before it's pushed to external mirrors and so be announced) the buildroots to start using the following repositories:
7.4.1708/{os,updates,extras}
That will be so done in parallel for x86_64,aarch64,ppc64,ppc64le .
We're just launching some sanity tests against those trees (all in place) and then we'll open this in CBS/Koji (plenty of tasks for this as Koji will have to rebuild internal metadata for those mirrors, aka "koji regen-repo $buildroot")
We'll post an update here when it will be switched and so active. That will let some time for SIGs to build some of the pkgs that were waiting/depending on 7.4.1708 pkgs from the distro, and so be "ready" before we go GA with 7.4.1708 (in the next days)
Hope this will help
Just to let you know that during the CBS meeting , we discussed this, and so we have now 7.4.1708 content available in all default el7 buildroots
You can start submitting rebuild jobs in CBS, but they'll be in the tasks queue, as first we need to ensure that koji knows about all new repodata from 7.4.1708 for all supported arches.
If you have issue, use this thread or #centos-devel on irc.freenode.net
-
Fabian Arrotin -
Sandro Bonazzola