Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Print warning if dnf5 is used to manage the system #2125

Open
kontura opened this issue Aug 27, 2024 · 2 comments
Open

Print warning if dnf5 is used to manage the system #2125

kontura opened this issue Aug 27, 2024 · 2 comments
Labels
Priority:LOW RFE Request for Enhancement (as opposed to a bug)

Comments

@kontura
Copy link
Contributor

kontura commented Aug 27, 2024

On transaction operations we could check that dnf5 system state nevras.toml is present/non empty (its what libdnf5::dnf4converter does) and if true print a warning that it is not recommended to manage one system with both dnf4 and dnf5.

@ppisar
Copy link
Contributor

ppisar commented Aug 27, 2024

Do you want to hard code a path to nevras.tml in DNF4 sources, or parse dnf5 --dump-main-config output?

@ppisar ppisar added Priority:LOW RFE Request for Enhancement (as opposed to a bug) labels Aug 27, 2024
@kontura
Copy link
Contributor Author

kontura commented Aug 27, 2024

I did not consider parsing the dnf5 --dump-main-config output, that is an interesting idea.

On the other hand perhaps it would be enough to hard code it. Its simpler and if someone moves the system state I would assume they are a more advanced user.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:LOW RFE Request for Enhancement (as opposed to a bug)
Projects
None yet
Development

No branches or pull requests

2 participants