glib ebuilds >=2.30.2 use non-POSIX argument to mv that can cause emerge to fail in the prepare phase when using mv implementations that do not support the argument. Solution: remove -v argument to mv in glib ebuild
dev-libs/glib is keyworded on linux and freebsd. On linux, gnu coreutils is part of the base profile package set that all ebuilds can assume is installed, and coreutils supports "mv -v". Similarly, on freebsd, "mv -v" is supported by sys-freebsd/freebsd-bin which is part of the freebsd base profile package set. Please describe the system where you experienced a failure due to "mv -v", and provide the "emerge --info" output. And verify that removing the "mv -v" is sufficient to allow glib to build on that system.
(In reply to comment #1) > dev-libs/glib is keyworded on linux and freebsd. On linux, gnu coreutils is > part of the base profile package set that all ebuilds can assume is > installed, and coreutils supports "mv -v". Similarly, on freebsd, "mv -v" is > supported by sys-freebsd/freebsd-bin which is part of the freebsd base > profile package set. > > Please describe the system where you experienced a failure due to "mv -v", > and provide the "emerge --info" output. And verify that removing the "mv -v" > is sufficient to allow glib to build on that system.
Created attachment 323536 [details] emerge --info
(In reply to comment #1) > dev-libs/glib is keyworded on linux and freebsd. On linux, gnu coreutils is > part of the base profile package set that all ebuilds can assume is > installed, and coreutils supports "mv -v". Similarly, on freebsd, "mv -v" is > supported by sys-freebsd/freebsd-bin which is part of the freebsd base > profile package set. > > Please describe the system where you experienced a failure due to "mv -v", > and provide the "emerge --info" output. And verify that removing the "mv -v" > is sufficient to allow glib to build on that system. The system uses portage for package-management and busybox for most of the user utilities. I realize that supporting non-standard, feature-limited utilities is not a goal of Gentoo. Removing the "-v" argument resolves the problem.
(In reply to comment #4) Lots of gnome-related ebuilds assume non-posix utilities, and that's unlikely to change. However, glib is a core library that even embedded/feature-limited users will find hard to avoid, and since "mv -v" in this case was basically decorative, I say we drop the "-v" to make things a bit easier for you :) > 11 Sep 2012; Alexandre Rostovtsev <tetromino@gentoo.org> glib-2.30.2.ebuild, > glib-2.30.3.ebuild, glib-2.32.3.ebuild, glib-2.32.4.ebuild: > Avoid 'mv -v' for embedded users with busybox (bug #432628).
Not sure if maybe a repoman check could search for expressions like "mv -v" that we should not use per problems like this. Otherwise, this is likely to occur again when we forget "-v" is not supported in busybox :|
