Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 950680 - kde-apps/akonadi-config and kde-apps/akonadi don't check each others database USE-flags
Summary: kde-apps/akonadi-config and kde-apps/akonadi don't check each others database...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo KDE team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-06 07:40 UTC by J. Roeleveld
Modified: 2025-03-06 18:32 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description J. Roeleveld 2025-03-06 07:40:51 UTC
kde-apps/akonadi-config does not check if selected database(s) matches flags for kde-apps/akonadi

Reproducible: Always

Steps to Reproduce:
1. Set USE flags for kde-apps/akonadi to "-mysql postgres"
2. Install akonadi (or upgrade system)
3.
Actual Results:  
kde-apps/akonadi-config  wants to install with use-flags "mysql -postgres"

Expected Results:  
kde-apps/akonadi-config  complains about a mismatch

With a mismatch between the different parts, functionality will not work as expected.
Comment 1 Andreas Sturmlechner gentoo-dev 2025-03-06 17:15:55 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.
Comment 2 J. Roeleveld 2025-03-06 17:19:18 UTC
(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.
Comment 3 Andreas Sturmlechner gentoo-dev 2025-03-06 17:23:01 UTC
Because there was no rename.
Comment 4 J. Roeleveld 2025-03-06 18:32:48 UTC
(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.