I have this problem building gnome-base/librsvg-2.55.1 (but not previous versions of librsvg) inside a rootless (buildah) container: ``` ... [ ok ] * Loading bit-vec-0.6.3.crate into Cargo registry ... [ ok ] * Loading bitflags-1.3.2.crate into Cargo registry ... [ ok ] * Loading block-0.1.6.crate into Cargo registry ... tar: block-0.1.6/Cargo.toml: Cannot change ownership to uid 133864, gid 1758687: Invalid argument tar: block-0.1.6/README.md: Cannot change ownership to uid 133864, gid 1758687: Invalid argument tar: block-0.1.6/src/lib.rs: Cannot change ownership to uid 133864, gid 1758687: Invalid argument tar: block-0.1.6/src/test_utils.rs: Cannot change ownership to uid 133864, gid 1758687: Invalid argument ``` ``` tar -t --verbose -f block-0.1.6.crate -rw-r--r-- 133864/1758687 531 2016-05-08 13:32 block-0.1.6/Cargo.toml -rw-r--r-- 133864/1758687 1264 2015-05-17 17:41 block-0.1.6/README.md -rw-r--r-- 133864/1758687 12647 2016-05-08 01:52 block-0.1.6/src/lib.rs -rw-r--r-- 133864/1758687 754 2016-05-07 23:24 block-0.1.6/src/test_utils.rs ``` If I look at other .crate files in my DISTDIR they have owner/group ids of 0/0: ``` tar -t --verbose -f matches-0.1.9.crate -rw-r--r-- 0/0 875 1969-12-31 18:00 matches-0.1.9/Cargo.toml -rw-r--r-- 0/0 350 1973-11-29 15:33 matches-0.1.9/Cargo.toml.orig -rw-r--r-- 0/0 1060 1973-11-29 15:33 matches-0.1.9/LICENSE -rw-r--r-- 0/0 3046 1973-11-29 15:33 matches-0.1.9/lib.rs -rw-r--r-- 0/0 314 1973-11-29 15:33 matches-0.1.9/tests/macro_use_one.rs -rw-r--r-- 0/0 168 1973-11-29 15:33 matches-0.1.9/tests/use_star.rs ``` I don't know why the block crate is wonky. I could change the subuid/subgid range of my buildah user but 1758687 seems like a rather large number just to extract a tarball, and that number may change in time, so perhaps adding `--no-same-owner` to the tar extraction command in cargo.eclass makes more sense.
I should add that I'm mostly using -user* in FEATURES because the container is already running rootless wrt the host.
