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
Upgrade process fails with ENOENT #18
Comments
...I'd need to see a lot more logs to have any idea what's going on there. Maybe look at Also, what versions of dnf-plugin-system-upgrade / dnf / PackageKit are installed? |
Ah, thanks for telling me about dnf.log. Apparently it's because there's no Plymouth.
I have
|
The upgrade worked with Plymouth installed. By the way, I wish DNF shared the rpm cache instead of letting its downloads get wiped. |
Good to know - I'll see about fixing this in a minute.
DNF and this plugin do share their package/metadata cache, mostly. Except it seems that DNF 1.1 moves the location of its package cache and/or deletes any RPMs left in the cache if you perform any other operation (see issue #5). Oh, and the next version of the |
If there's no /usr/bin/plymouth then subprocess.call will raise OSError; we should have a test case that makes sure that we handle this cleanly. We actually fail this test right now, which illustrates issue #18.
Thanks! |
After dnf reboot, the system boots twice without installing anything, I have the following logs:
This is from an up-to-date Fedora 22.
It's a fairly small VM, maybe some implicit dependencies are missing?
The text was updated successfully, but these errors were encountered: