Recent change to remove slotted builds in postgresql breaks Pentoo Metasploit ebuilds.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Recent change to remove slotted builds in postgresql breaks Pentoo 
Metasploit ebuilds.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

Remove "[server]" text from Pentoo Metasploit ebuilds to fix this.

THanks.

Original issue reported on code.google.com by willard....@gmail.com on 3 Jan 2015 at 1:54

[GoogleCodeExporter]

please update before opening bugs, this has been fixed for days.

Original comment by sidhayn on 3 Jan 2015 at 3:33

• Changed state: Invalid

[GoogleCodeExporter]

If you say so.  I updated just a few hours ago and it was not fixed from what I 
could see.  I had to manually uninstall my previous postgresql install, 
manually edit / redigest these ebuilds to get it updated.  Just now, I blew 
away my /var/lib/layman/pentoo/net-analyzer/metasploit folder and resync from 
scratch, but it seems still not to be fixed - these ebuilds still reference 
slotted builds.

pentoo ~ # fgrep '[server]' 
/var/lib/layman/pentoo/net-analyzer/metasploit/metasploit-*
/var/lib/layman/pentoo/net-analyzer/metasploit/metasploit-4.10.0-r1.ebuild:COMMO
N_DEPEND="dev-db/postgresql[server]
/var/lib/layman/pentoo/net-analyzer/metasploit/metasploit-4.11.0-r1.ebuild:COMMO
N_DEPEND="dev-db/postgresql[server]
/var/lib/layman/pentoo/net-analyzer/metasploit/metasploit-9999.ebuild:COMMON_DEP
END="dev-db/postgresql[server]

On the other hand, with a "clean" 
/var/lib/layman/pentoo/net-analyzer/metasploit/ folder resync'd from scratch, I 
am able to build metasploit-9999 just fine as of now, so I must obviously 
accept your claim.

The assumption that I had not tried at all is a bit off-putting, though.

Original comment by willard....@gmail.com on 3 Jan 2015 at 6:19

[GoogleCodeExporter]

I'm sorry that it was broken for you.  There have been multiple near-retard 
level changes in gentoo related to postgres lately.  While I didn't notice any 
breakage, it is difficult to keep up and I think we have done a good job.  It 
is possible that you had an older version of portage or some such which doesn't 
handle things as well as ~arch portage does.  portage 2.2.15 seems to be 
working well and there are even more changes coming to fix some of the 
brain-dead dep solving wrt dynamic deps and changes to deps.

Original comment by sidhayn on 3 Jan 2015 at 7:00