Description of problem: First transaction printed by dnf when updating packages is: "Running scriptlet: None" How reproducible: Steps to Reproduce: 1. dnf update Actual results: ~~~ Running transaction Running scriptlet: None 1/1 Preparing : 1/1 ~~~ Expected results: The message with "None" to be skipped.
Can you re-run it with --rpmverbosity=debug and paste output? It's interesting which scriptlet is running..
How dnf identify package for scriplets? rpm callback provide: 1. string with package nevra 2. Object that can be used to find out the package nevra 3. None. In this case dnf can identify object according to running element in transaction, but this approach cannot be applied for the case, because transaction technically didn't start. What we can do: 1. in the case report only "Running scriptlet:" and not "Running scriptlet: None" 2. Request for rpm team to always provide package string in callbacks and not None for any cases.
(In reply to Igor Gnatenko from comment #1) > Can you re-run it with --rpmverbosity=debug and paste output? It's > interesting which scriptlet is running.. I am unable to reproduce it for my current state of updated packages. I will keep an eye on the debug output and share it if the issue arises.
Thanks, if you will be able to reproduce it -- please reopen bug with additional details!
Unfortunately those problems cannot be reproduced, because they appear during performing of transaction, therefore the next transaction handles different packages. Only reverting the last transaction could produce the reproducer, but in Fedora environment, this is quite difficult.
Reproduced when removing `abrt` package (abrt.x86_64 2.10.3-1.fc26): ~~~ Running transaction Running scriptlet: None 1/1 D: closed db index /var/lib/rpm/Packages D: closed db index /var/lib/rpm/Enhancename D: closed db index /var/lib/rpm/Supplementname D: closed db index /var/lib/rpm/Suggestname D: closed db index /var/lib/rpm/Recommendname D: closed db index /var/lib/rpm/Transfiletriggername D: closed db index /var/lib/rpm/Filetriggername D: closed db index /var/lib/rpm/Sha1header D: closed db index /var/lib/rpm/Sigmd5 D: closed db index /var/lib/rpm/Installtid D: closed db index /var/lib/rpm/Dirnames D: closed db index /var/lib/rpm/Triggername D: closed db index /var/lib/rpm/Obsoletename D: closed db index /var/lib/rpm/Conflictname D: closed db index /var/lib/rpm/Providename D: closed db index /var/lib/rpm/Requirename D: closed db index /var/lib/rpm/Group D: closed db index /var/lib/rpm/Basenames D: closed db index /var/lib/rpm/Name D: closed db environment /var/lib/rpm D: opening db environment /var/lib/rpm cdb:0x401 D: opening db index /var/lib/rpm/Packages (none) mode=0x42 D: sanity checking 6 elements D: Plugin: calling hook tsm_pre in selinux plugin D: Plugin: calling hook tsm_pre in systemd_inhibit plugin D: System shutdown blocked (fd 20) D: opening db index /var/lib/rpm/Transfiletriggername (none) mode=0x42 D: opening db index /var/lib/rpm/Dirnames (none) mode=0x42 D: %triggerun(systemd-233-6.fc26.x86_64): running <lua> scriptlet. Preparing : 1/1ufdio: 2 reads, 957 total ~~~
The problem is that with (file) trigger scriptlets, rpm doesn't always supply a header to the callback because there's no transaction element associated with these items.
Oops, wrong take button.
The fundamental issue fixed upstream now: https://github.com/rpm-software-management/rpm/commit/6d610e9b9a906548ce44265d7f36199441ea8bca: [...] Transaction test succeeded. Running transaction Running scriptlet: systemd 1/1 Preparing : 1/1 Erasing : abrt-dbus-2.10.3-1.fc26.x86_64 1/8 [...] There are various related issues due to the limitations of the python binding callback but that's beyond the scope of this bug.
Fixed in rawhide now as per above, plus F27 once the beta freeze lifts. We can consider backporting to older versions later once it's clear there are no unexpected side-effects.
rpm-4.13.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2018-d4cacdf9bc
rpm-4.13.1-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-d4cacdf9bc
rpm-4.13.1-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.