You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We faced an issue when trying to release packages to AlmaLinux-Kitten-10 platfrom, as the release failed to include any packages and displayed No data available
It appears the problem occurs because the AlmaLinux-Kitten-10 platform is used for the release, while AlmaLinux-10 is used for the build, and currently, these platforms are not cross-compatible for package releases. The goal is to ensure that packages built for AlmaLinux-Kitten-10 can be released on the AlmaLinux-10 platform, and packages built for AlmaLinux-10 can also be released on the AlmaLinux-Kitten-10 platform.
The text was updated successfully, but these errors were encountered:
…lmaLinux-10 platform, and the other way around
ResolvesAlmaLinux/build-system#369:
- For cross-releasing we should include an RPM artifact if the reference platforms of its build task has intersection with the reference platform of base platform which we want to release a build
We faced an issue when trying to release packages to AlmaLinux-Kitten-10 platfrom, as the release failed to include any packages and displayed
No data available
Here is the release - https://build.almalinux.org/release/9097
The release, however, doesn’t contain any packages and shows
No data available
The console from developer mode doesn’t show any errors.
Here is the build we tried to release - https://build.almalinux.org/build/20504
It appears the problem occurs because the AlmaLinux-Kitten-10 platform is used for the release, while AlmaLinux-10 is used for the build, and currently, these platforms are not cross-compatible for package releases. The goal is to ensure that packages built for AlmaLinux-Kitten-10 can be released on the AlmaLinux-10 platform, and packages built for AlmaLinux-10 can also be released on the AlmaLinux-Kitten-10 platform.
The text was updated successfully, but these errors were encountered: