Could all arches, please check exim-4.67 for compilation, especially against the new libdomainkeys dependancy which will also require testing. Reproducible: Always
~ia64 done
added ~ppc64
~sparc'd. Check libdomainkeys though, it's forcing/filtering CFLAGS and could be an issue.
I'm not sure whether this is a bug or not, but it would seem that on my arch (x86) exim has now been marked stable. However, if I select the domainkeys use flag, it won't upgrade, as libdomainkeys is still ~x86. Is there a convention that says that if foo is marked stable, and foo can depend on bar if your use flags are set like so that bar must be stable too?
I'll have to check to confirm, but I could have sworn I commited the stable version of libdomainkeys to the tree. I'll see if another dev can commit, if not it will have to wait until I get home from work this evening, until then as long as libdomainkeys is installed, (or not in USE), then it should still work.
ia64 needs to mark net-dialup/radiusclient ~ia64 too.
Sorry, stale tree.
All three marked ~hppa.
I've installed libdomainkeys and exim (with the use flag) on my amd64 machine the first day it hit the tree and I've not found problems with both packages since the emerge process. Are needed another tests to consider marking ~amd64 too?
We're running our own overlay on a set of amd64 machines. We added exim-4.67 which compiles just fine, as does libdomainkeys. What will it take to get ~amd64 added to the exim-4.67 ebuild?
amd64 done
~ppc'd
~alpha done, closing.
Can you please STOP dropping keywords for no reason? amd64,ppc: please readd your keyword to exim-4.67-r2. ~alpha done again
Sorry guys, that was a mistake on my part, I hadn't intentionally dropped them. I'll re-add them myself.
exim-4.67-r2.ebuild:KEYWORDS="~alpha ~amd64 ~hppa ~ia64 ~ppc ~ppc64 ~sparc ~x86"
