Hey,
(@debian-release, pls CC me)
Am 27.06.2023 um 20:13 schrieb Sergio Durigan Junior:
Source: glusterfs
Version: 10.3-5
Severity: important
Hi,
Upstream glusterfs has given several indications that they do not
care about/support 32-bit architectures, as can be seen in this
(non-exhaustive) list of issues:
- https://github.com/gluster/glusterfs/issues/3911
- https://github.com/gluster/glusterfs/issues/702
Moreover, in Ubuntu, where glusterfs is built for armhf, some issues
have been filed about problems related to this lack of 32-bit support,
like:
- https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1991441
- https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1951408
The underlying issue in these two bugs happen to be correlated:
glusterfs requires that the host supports 64-bit atomic operations, but
armhf and other 32-bit architectures don't offer such feature.
Therefore, I would like to request that the support for 32-bit
architecture in Debian's glusterfs package be dropped, please.
A quick investigation tells me that these packages will likely need to
be adjusted because they depend on glusterfs:
Reverse-Build-Depends
* fio (for libglusterfs-dev)
* libvirt (for libglusterfs-dev)
* nfs-ganesha (for libglusterfs-dev)
* qemu (for libglusterfs-dev)
* qemu (for glusterfs-common)
* tgt (for libglusterfs-dev)
* uwsgi (for libglusterfs-dev)
Reverse-Build-Depends-Arch
* samba (for libglusterfs-dev)
Let me know if there's anything I can do to help here.
Thanks,
OK I think this is a realy bad situation, also just so short after the
bookworm release..
@Release team:
What is your opinion about it, should we remove glusterfs on 32 bit
platforms from bookworm? How should we coordinate it also with the other
reverse dependencies? Or should we leave it as it is (for bookworm) and
change it for the upcoming releases?
