* Fixing packlist file /usr/lib64/perl5/vendor_perl/5.30.1/x86_64-linux/auto/MogileFS/Server/.packlist usage: doins.py [-h] [-g GROUP] [-o OWNER] [-m MODE] [-p] doins.py: error: argument -g/--group: invalid _parse_group value: 'mogile' * ERROR: dev-perl/MogileFS-Server-2.730.0::gentoo failed (install phase): * doins failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_desktop_gnome_systemd-20200216-141645 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-9.2.0 * clang: clang version 9.0.1 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/9/bin llvm: 9.0.1 Available Python interpreters, in order of preference: [1] python3.8 [2] python3.6 [3] python3.7 (fallback) [4] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) [2] ruby25 (with Rubygems) * Available Rust versions: [1] rust-1.41.0 * java-config: The following VMs are available for generation-2: Available Java Virtual Machines: (none found) ghc: The Glorious Glasgow Haskell Compilation System, version 8.0.2 repository: ==> /var/db/repos/gentoo/metadata/timestamp.chk <== Fri, 21 Feb 2020 02:08:21 +0000 emerge -qpvO dev-perl/MogileFS-Server [ebuild N ] dev-perl/MogileFS-Server-2.730.0 USE="sqlite -mysql -postgres -test"
Created attachment 614872 [details] emerge-info.txt
Created attachment 614874 [details] dev-perl:MogileFS-Server-2.730.0:20200221-040719.log
Created attachment 614876 [details] emerge-history.txt
Created attachment 614878 [details] environment
Created attachment 614880 [details] etc.portage.tbz2
Created attachment 614882 [details] temp.tbz2
This package doesn't directly call "doins.py", and none of your logs provide any context to why. The call looks to be blamed on the "newins" invocations, but those are being called following documentation. As-is, it looks like you have a broken portage install. Re-open if you can provide something more concrete.
I rescheduled that package and it failed at another image too - does the attached files provdies more useful information?
Created attachment 614964 [details] emerge-info.txt
Created attachment 614966 [details] dev-perl:MogileFS-Server-2.730.0:20200221-203931.log
Created attachment 614968 [details] emerge-history.txt
Created attachment 614970 [details] environment
Created attachment 614972 [details] etc.portage.tbz2
Created attachment 614974 [details] temp.tbz2
(In reply to Toralf Förster from comment #8) > I rescheduled that package and it failed at another image too - does the > attached files provdies more useful information? No, none of the attached files are helpful, because none of them give an explanation as to why _portage_ is emitting an error based on _portage_ calling _portage_ code. Nothing in any of these ebuilds invokes "doins.py", that's a *portage* thing, wherein, it implements one of the documented and defined functions in PMS in terms of Python. This is likely to the the acct-*/ migrations happening. But this package shouldn't be magically broken either. Please stop attaching files willy nilly without looking as to see if any of them contain remotely illuminating details.
@portage, can you shed some light?
(In reply to Toralf Förster from comment #0) > usage: doins.py [-h] [-g GROUP] [-o OWNER] [-m MODE] [-p] > doins.py: error: argument -g/--group: invalid _parse_group value: 'mogile' The ebuild passes ${MOGILE_USER} as a group here, but it's not a valid group: > insopts -m 600 -o root -g ${MOGILE_USER}
(In reply to Zac Medico from comment #17) > (In reply to Toralf Förster from comment #0) > > usage: doins.py [-h] [-g GROUP] [-o OWNER] [-m MODE] [-p] > > doins.py: error: argument -g/--group: invalid _parse_group value: 'mogile' > > The ebuild passes ${MOGILE_USER} as a group here, but it's not a valid group: > > > insopts -m 600 -o root -g ${MOGILE_USER} So I'm guessing enewuser changed behaviour: https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-perl/MogileFS-Server/MogileFS-Server-2.730.0.ebuild?id=79ed04f6035936a7eb99a4b4b3af101e25ebf53f#n48 https://gitweb.gentoo.org/repo/gentoo.git/commit/eclass/user.eclass?id=3afc0d7b8b5e90c50d66c5a845b96c33e521e6e8 So at least now we know why it used to work, and why it no longer does.
Dear treecleaner@: I'm still able to reproduce this issue right now. Since it has not been fixed for a long time, I'd suggest to evaluate if it is the case to remove this package from the tree. Thanks
Created attachment 684837 [details] sucessful build log It works fine here, and the service has continued to work for many years.
It's configurable (in shadow I think) whether creating a "mogile" user also creates a group with the same name; seems like ago's settings are different. And the ebuild does not enforce the existence of the group but silently assumes it's there. *** This bug has been marked as a duplicate of bug 688554 ***
