ferringb

@bgloyer your ask is addressable, but it's problematic since portage tends to do things w/out coordination; point blank, they tend to do things without concern for pkgcore leaving pkgcore broken...

@arthurzam this may be of interest for you to take over

after the question of black formatted code is addressed, I'll add this. A quick pyflakes scan is showing a couple of things warranting cleanup anyways.

Binpkg creation is atomic. As to the original failure- on a guess, it relates to "system crashed while merging". Ext4 from that era was known to leave empty files in...

Revisiting this 7 years later: the raise from logic is correct. Chaining errors is what should happen here since if we start summarizing/wrapping, we lose the error chain from the...

> the library should be chaining the exception. it isn't. ergo the module still needs improving doesn't it ? Yeah, that wasn't obvious in the post, my bad. In the...

> the library should be chaining the exception. it isn't. ergo the module still needs improving doesn't it ? Pardon, but at the time of this bug report- this was...

As to the original bug report; we used a compatibility 'raise from' back in py2k which wasn't properly support for error reporting. I'm *assuming* this error report was from that...

@mgorny or @ulm ; what's PMS's stance on this? Specifically, should pkgcore be taking a USE_EXPAND'd list and updating the the underlying variable with that content? IE, should pkgcore rewrite...

What behaviour should occur when someone has multiple repositories with the same repo_id in their config? Should this be treated as 'bad' config? Pebuild has a check for what you're...