Hello.

While updating the gettext package, which now has build-depends
on those two packages, I looked at this package first and
noticed the [linux-any] restrictions in debian/control.

Are those restrictions really needed?

Apparently the packages do exist for all architectures,
including the Hurd:

https://buildd.debian.org/status/package.php?p=acl
https://buildd.debian.org/status/package.php?p=attr

so if they are not usable, I'd like to know.

Cc to Samuel, who maybe knows the answer.

Thanks.

IIRC they were for kfreebsd.

I don't know what happens if they're enabled on hurd (which I think is
now the only platform affected?) If someone reports that coreutils works
does something useful built that way on hurd I'm happy to make the
change.

Hello,

Santiago Vila, le mer. 15 janv. 2025 17:49:55 +0100, a ecrit:

It doesn't seem so.

Here is the changelog entry:

  * [50,51] acl support
    - libacl1-dev build dependency
    - probably won't work on non-linux, patches welcome for hurd et al. if
      they break
  * [52] extended attribute support
    - libattr1-dev build dependency (still necessary with new libc?)
    - not sure about this one, it might come out (is it always valid to
      preserve ea's even if we don't know what they are for?)

I don't know more, it's probably worth checking whether that would
actually work.

Samuel