There were discussions on irc about it but I lost track of who I should speak with etc so decided to write to mailing list instead.
The goal is to rebuild OpenStack 'mitaka' packages for AArch64 (AltArch) in CBS (there is one builder for this architecture).
Question is how to make it in best way?
One of ideas was:
1. create new tag (cloud7-openstack-mitaka-candidate-aarch64?) 2. import all 'noarch' builds from cloud7-openstack-mitaka-* tags 3. send all required packages to the builder 4. test resulting packages 5. import/merge all of them to proper cloud7-openstack-mitaka-* tag
Other was about doing scratch builds and merging them with x86-64 ones.
How we can proceed? I think that first idea is good as it allows us to do builds without touching x86-64 tag before we are ready for merging. But I do not have koji experience so may be wrong.
adding rdo-list
On Fri, Jun 10, 2016 at 1:14 PM, Marcin Juszkiewicz marcin.juszkiewicz@linaro.org wrote:
There were discussions on irc about it but I lost track of who I should speak with etc so decided to write to mailing list instead.
The goal is to rebuild OpenStack 'mitaka' packages for AArch64 (AltArch) in CBS (there is one builder for this architecture).
Question is how to make it in best way?
One of ideas was:
- create new tag (cloud7-openstack-mitaka-candidate-aarch64?)
- import all 'noarch' builds from cloud7-openstack-mitaka-* tags
- send all required packages to the builder
- test resulting packages
- import/merge all of them to proper cloud7-openstack-mitaka-* tag
Other was about doing scratch builds and merging them with x86-64 ones.
How we can proceed? I think that first idea is good as it allows us to do builds without touching x86-64 tag before we are ready for merging. But I do not have koji experience so may be wrong.
New tag is the way to go, we don't want to block x86_64.
Cheers, Alan
Hi,
How we can proceed? I think that first idea is good as it allows us to do builds without touching x86-64 tag before we are ready for merging. But I do not have koji experience so may be wrong.
New tag is the way to go, we don't want to block x86_64.
+1
The status, we have a blocker with mergerepo / mergerepo_c [1] which are not merging package with a dist tag different on the source package and the binary.
e.g:
I had to leave the problem on the side during 6.8 cycle but we are resuming some work this week with Brian and hope to understand better the problem.
On 10/06/16 14:04, Thomas Oulevey wrote:
How we can proceed? I think that first idea is good as it allows us to do builds without touching x86-64 tag before we are ready for merging. But I do not have koji experience so may be wrong.
New tag is the way to go, we don't want to block x86_64.
+1
The status, we have a blocker with mergerepo / mergerepo_c [1] which are not merging package with a dist tag different on the source package and the binary.
[1]:
$ repoquery --repofrompath=reponame,http://cbs.centos.org/kojifiles/repos/storage7-ceph-jewel-el7-build/latest/a... --repoid=reponame -q json-c
return no result
The mergerepo tasks (mergerepo_c because it is more verbose, same issue with mergerepo): https://cbs.centos.org/kojifiles/work/tasks/4276/94276/mergerepos.log
""" 19:33:02: Reading metadata for json-c (0.11-4.el7.aarch64) 19:33:02: Package json-c has forbidden srpm json-c-0.11-4.el7.src.rpm """
This is because of 0.11-4.el7_0 on x86 compared to 0.11-4.el7 on aarch64, right? Should be fixable if we rebuild json-c 0.11-4.el7_0 on aarch64 and update repositories?
Is there a tool to use which would list such differences?
On 15/06/16 10:31, Marcin Juszkiewicz wrote:
19:33:02: Reading metadata for json-c (0.11-4.el7.aarch64) 19:33:02: Package json-c has forbidden srpm json-c-0.11-4.el7.src.rpm """
This is because of 0.11-4.el7_0 on x86 compared to 0.11-4.el7 on aarch64, right? Should be fixable if we rebuild json-c 0.11-4.el7_0 on aarch64 and update repositories?
Is there a tool to use which would list such differences?
Checked a bit, compared list of packages in os/ repo and looks like many packages may need syncing ;(
El mié, 15-06-2016 a las 11:10 +0100, Marcin Juszkiewicz escribió:
On 15/06/16 10:31, Marcin Juszkiewicz wrote:
19:33:02: Reading metadata for json-c (0.11-4.el7.aarch64) 19:33:02: Package json-c has forbidden srpm json-c-0.11- 4.el7.src.rpm """
This is because of 0.11-4.el7_0 on x86 compared to 0.11-4.el7 on aarch64, right? Should be fixable if we rebuild json-c 0.11-4.el7_0 on aarch64 and update repositories?
Is there a tool to use which would list such differences?
Checked a bit, compared list of packages in os/ repo and looks like many packages may need syncing ;(
I would like to help with this effort but i'm not shure where to start Alan, what can be done?
Cheers, Ivan
-
Alan Pevec -
Iván Chavero -
Marcin Juszkiewicz -
Thomas Oulevey