Summary: | kde-apps/akonadi-config and kde-apps/akonadi don't check each others database USE-flags | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | J. Roeleveld <joost> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | joost |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
J. Roeleveld
2025-03-06 07:40:51 UTC
It's because the flags are gone from akonadi, configuration moved to akonadi-config. You should have received a nice explanatory ewarn message from akonadi-config. (In reply to Andreas Sturmlechner from comment #1) > It's because the flags are gone from akonadi, configuration moved to > akonadi-config. Why was this not hanbdled with an automatic adjustment in the package.use files like other renames? > You should have received a nice explanatory ewarn message from > akonadi-config. I caught this earlier because I was surprised an updated wanted to install mariadb and its dependencies. Because there was no rename. (In reply to Andreas Sturmlechner from comment #3) > Because there was no rename. I think for this, a news-item would be a better option instead of an ewarn. With the amount of messages at the end of an upgrade, it gets lost in the bundle. And if this is not immediately spotted, it's gone when the console is closed. |