#6149 Fedora secondary arches .composeinfos are missing and need to be made
Closed: Fixed 7 years ago Opened 8 years ago by alemay.

Fedora secondary arches .composeinfo are missing and need to be made.

Red Hat uses the .composeinfo to import distros into beaker for automated testing.
Without the .composeinfo s390x ppc64 ppc64le and aarch64 are not getting imported.
Which means inside Red Hat they are not being tested.

Example of a .composeinfo
http://dl.fedoraproject.org/pub/fedora-secondary/releases/20/Fedora/ppc64/.composeinfo

Example of a .composeinfo mia
http://dl.fedoraproject.org/pub/fedora-secondary/releases/21/Server/ppc64/.composeinfo

Thanks


I've checked the master source for F-21/s390x and .composeinfo is there - http://s390.koji.fedoraproject.org/tree/releases/21/.composeinfo

but the master mirror at http://alt.fedoraproject.org/pub/fedora-secondary/releases/21/ contains the last .composeinfo, this time from the ppc hub (http://alt.fedoraproject.org/pub/fedora-secondary/releases/21/.composeinfo) and the composeinfos from aarch64 and s390x hubs are lost

.composeinfo 's are still missing what's the status on this.

They'll be there for f23 GA

secondary arches need to put .composeinfo files in their arch directories, the way secondary arches work it is not possible to make one .composeinfo file for all arches

Well then they need to be manually made. So they get imported internally.

Replying to [comment:7 alemay]:

Well then they need to be manually made. So they get imported internally.

Or beaker could be updated to use .treeinfo like all other tools, .composeinfo is EOL, it's only used by beaker. Everything else uses .treeinfo, the later also has the advantage of being signed and verifiable:

{{{
https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/aarch64/os/.treeinfo.signed
https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/ppc64/os/.treeinfo.signed
https://dl.fedoraproject.org/pub/fedora-secondary/releases/23/Server/ppc64le/os/.treeinfo.signed
}}}

Metadata Update from @alemay:
- Issue assigned to pbrobinson

7 years ago

everything should be correct today. and will be going forward

Metadata Update from @ausil:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

7 years ago

Login to comment on this ticket.

Metadata