unhadled trailing '/' in repo definitions in classes.conf
Brought to you by:
dmakovey
Consider config
rpm_db_path=%(rpm_base)s:%(yum_cache)s/rpmforge/packages/
updates_exclude=%(yum_cache)s/rpmforge/packages
if you remove trailing slash in the first line (rpm_db_path) - than class behaves as expected, otherwise updates_exclude totally misses out on this and lets rpmforge packages through.
Trailing slashes are not handled well at all in all path definitions (inside of classes.conf and 2install). For example manually crafted 2install with trailing slash in the path would be rejected by policy since that path is not "defined" in classes.conf according to CPacMan.
fixed in 0.7 branch (203:204)
bug was accepted to be addressed in next release (see group tag of the bug).