| Summary: | sys-cluster/galera, sys-cluster/gasnet: drop older ebuilds | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Marco Scardovi (scardracs) <mscardovi> |
| Component: | Current packages | Assignee: | Gentoo Cluster Team <cluster> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | zlogene |
| Priority: | Normal | Keywords: | PullRequest |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://github.com/gentoo/gentoo/pull/23154 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Marco Scardovi (scardracs)
2021-12-02 21:22:57 UTC
EDIT Used same PR for both openmpi and rdma-core Added gasnet to cleanup list Added galera to cleanup list Added k3s to cleanup list openmpi/rdma must stay as there are problems even between minor versions. They all are different. (In reply to Mikle Kolyada from comment #5) > openmpi/rdma must stay as there are problems even between minor versions. > They all are different. so we can't remove them in any way? Removed rdma-core from the drop list Added sys-cluster/legion to cleanup list (In reply to Marco Scardovi (scardracs) from comment #6) > (In reply to Mikle Kolyada from comment #5) > > openmpi/rdma must stay as there are problems even between minor versions. > > They all are different. > > so we can't remove them in any way? for now, no, openmpi list must be carefully considered and it is really hard :/ (In reply to Mikle Kolyada from comment #9) > (In reply to Marco Scardovi (scardracs) from comment #6) > > (In reply to Mikle Kolyada from comment #5) > > > openmpi/rdma must stay as there are problems even between minor versions. > > > They all are different. > > > > so we can't remove them in any way? > > for now, no, openmpi list must be carefully considered and it is really hard > :/ Could I know why it's so hard? s/know/ask/ @zlogene removed the openmpi drop The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=efbe5d0c5d1df90ea9453756b553dc8d9d650c76 commit efbe5d0c5d1df90ea9453756b553dc8d9d650c76 Author: Marco Scardovi <marco@scardovi.com> AuthorDate: 2021-12-11 21:05:37 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2021-12-11 21:08:58 +0000 sys-cluster/k3s: drop older ebuilds Bug: https://bugs.gentoo.org/828032 Package-Manager: Portage-3.0.28, Repoman-3.0.3 Signed-off-by: Marco Scardovi <marco@scardovi.com> Signed-off-by: Zac Medico <zmedico@gentoo.org> sys-cluster/k3s/Manifest | 247 ------ sys-cluster/k3s/k3s-1.19.15.ebuild | 1513 ------------------------------- sys-cluster/k3s/k3s-1.20.11.ebuild | 1628 ---------------------------------- sys-cluster/k3s/k3s-1.21.5.ebuild | 1710 ------------------------------------ sys-cluster/k3s/k3s-1.22.2.ebuild | 1688 ----------------------------------- 5 files changed, 6786 deletions(-) @scardracs I've preserved one of each of the k3s-1.19.x, k3s-1.20.x, k3s-1.21.x, and k3s-1.22.x ebuilds, since my intention is to keep one for each series that is still supported upstream. @zmedico thanks :), I see sys-cluster/ is a mess, as explained by zlogene, but would be awesome to make it a bit more cleaner Thanks @ulm for merging it |