Closed inode64 closed 2 weeks ago
The behaviour changed? I have been only using the last released version for a while so I was unaware.
Definitely would prefer that the failed package get logged at error level but not raise.
Tomorrow I'll try to prepare a commit and see if it's correct.
Now in any ebuild that cannot be updated a raise is generated and this means that you have to exclude the packages that cannot be automatically searched I have thought about changing the "raise" to "logger.debug" so you can analyze an entire portage without interruptions
What do you think?