There are now 2 qmail ebuilds (mail-mta/qmail and virtual/qmail). After completing emerge of mail-mta/qmail you are advised to: * To setup qmail to run out-of-the-box on your system, run: * emerge --config =qmail-1.03-r16 The config in this case is ambiguous and will return: Traceback (most recent call last): File "/usr/bin/emerge", line 2817, in ? pkgs = portage.db[portage.root]["vartree"].dbapi.match(myfiles[0]) File "/usr/lib/portage/pym/portage.py", line 4822, in match mydep=dep_expand(origdep,mydb=self,use_cache=use_cache) File "/usr/lib/portage/pym/portage.py", line 3768, in dep_expand return prefix+cpv_expand(mydep,mydb=mydb,use_cache=use_cache)+postfix File "/usr/lib/portage/pym/portage.py", line 3712, in cpv_expand raise ValueError, matches ValueError: ['mail-mta/qmail', 'virtual/qmail'] The post-emerge notice needs to be the fully-qualified ebuild name. In my case, it would be: * emerge --config =mail-mta/qmail-1.03-r16
@portage - should this really traceback? :)
Fixed in svn r3219.
Fixed in qmail-1.03-r{15,16} and netqmail-1.05-r1. Thanks for reporting.
*** Bug 131557 has been marked as a duplicate of this bug. ***
*** Bug 129931 has been marked as a duplicate of this bug. ***