http://sources.gentoo.org/viewcvs.py/gentoo-x86/net-libs/libproxy/ChangeLog?r1=1.15&r2=1.16 For some reason, "-libproxy-0.2.3-r1.ebuild +libproxy-0.2.3-r2.ebuild" and "*libproxy-0.2.3-r2 (29 Jun 2009)" didn't make it into the ChangeLog. portage doesn't display anything useful with its --changelog option when upgrading from -r1 because of this. This could be an echangelog bug, or this could be a result of running echangelog too early. Is there any way for you to check? If so, and if echangelog is somewhat broken, please also reassign as appropriate.
Weird, I did run it early until waiting for the necessary xulrunner revbump to hit the tree, but I'm quite sure I had everything cvs added and cvs removed (and echangelog complains if something is stale in CVS), except one stale patch I fixed as a follow-up commit. So I was only repoman committing 12 hours later. I'll see about fixing it up and my echangelog is probably from an older gentoolkit-dev anyway right now, so don't think we should take this as a still existing bug in gentoolkit-dev in this weird single occasion with an older version. I did have some weird CVS freezings for a few pure CVS commands that morning though iirc, hmm...
Fixed, I think...
