Essentially, whoever added this for dkimproxy failed to see dev-perl/net-server sitting there, and now we've got 2 different packages for the same upstream package. Sure, 'net-server' doesn't fit our recent naming scheme, but its a legacy problem. Additionally, Net-Server doesn't use the perl teams versioning scheme, and its presence will possibly cause weird bugs if anyones unfortunate enough to use portage on a case-insensitive file-system. cat /usr/portage/dev-perl/Net-Server/ChangeLog # ChangeLog for dev-perl/Net-Server # Copyright 1999-2013 Gentoo Foundation; Distributed under the GPL v2 # $Header: /var/cvsroot/gentoo-x86/dev-perl/Net-Server/ChangeLog,v 1.1 2013/02/28 19:12:15 zx2c4 Exp $ *Net-Server-2.007 (28 Feb 2013) 28 Feb 2013; Jason A. Donenfeld <zx2c4@gentoo.org> +Net-Server-2.007.ebuild, +metadata.xml: Initial commit for dkimproxy. cat /usr/portage/dev-perl/Net-Server/metadata.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> <pkgmetadata> <herd>perl</herd> <upstream> <remote-id type="cpan">Net-Server</remote-id> <remote-id type="cpan-module">Net::Server</remote-id> </upstream> </pkgmetadata> cat /usr/portage/dev-perl/net-server/metadata.xml <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> <pkgmetadata> <herd>perl</herd> <upstream> <remote-id type="cpan">Net-Server</remote-id> <remote-id type="cpan-module">Net::Server</remote-id> ... </upstream> </pkgmetadata> emerge --info Portage 2.2.0_alpha161 (default/linux/amd64/13.0, gcc-4.7.2, glibc-2.15-r3, 3.8.0-gentoo x86_64) ================================================================= System uname: Linux-3.8.0-gentoo-x86_64-Intel-R-_Core-TM-_i5-2410M_CPU_@_2.30GHz-with-gentoo-2.1 KiB Mem: 3891996 total, 704556 free KiB Swap: 20478972 total, 20079220 free Timestamp of tree: Fri, 01 Mar 2013 14:00:01 +0000 <everything else irrelevant to this bug>
Quickly band-aided by just straight up removing the new package and adjusting dkimproxy, before other things rely on it. As it's brand new anyway, I don't think this should cause issue and warrants skirting the usual thirty day policy.