On a virgin system with NO mta installed you are unable to install postfix without portage requesting you to install ssmtp. Reproducible: Always Steps to Reproduce: 1. unmerge any mta's on your system or start with a fresh system 2. emerge postfix without the mailwrapper flag Actual Results: portage blocks the installation of postfix as it is trying to install ssmtp Expected Results: postfix to be installed
*** This bug has been marked as a duplicate of bug 1343 ***
I'm confused as to how that bug #1343 is relevant to this? All I want to do is emerge postfix on a system with no MTA. Portage is checking for a virtual/mta and as this doesn't exist is trying to install ssmtp to meet this requirement even tho it is met via postfix. Bug #1343 was opened in 2002.... the problem I am having is a recent one that has only been around for the past month or so. If you roll back your portage to at least the 22nd of October then all works as it should do!
Read the bug more carefully and please avoid more noise here. *** This bug has been marked as a duplicate of bug 1343 ***
I have read the bug and it stated that it should be fixed on 2.0.51! As its not I opened a bug report. I have since found a fix tho.... downgrade to sys-apps/portage-2.1.3.16 and all works well! So, back to me telling you guys that there is a bug in the latest verison of portage ;-)
You read the bug plain wrong. Bug 1343 affects every single portage version out there. That's why it is still OPEN. So now move there and leave this DUPLICATE alone. *** This bug has been marked as a duplicate of bug 1343 ***
(In reply to comment #2) > If you roll back your portage to at least the 22nd of October then all works as > it should do! There was a code change that can explain that. The previous code may have worked better in some cases but it wasn't guaranteed to work and it could also lead to problems in some cases. I'm working on a fix for bug 1343 that should handle most cases pretty well.
