Bug 1031322
| Summary: | [abrt] dnf-0.4.7-1.fc20: comps.py:29:<module>:ImportError: No module named libcomps | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | diego brizuela <brizuela.diego10> | ||||||
| Component: | fedup | Assignee: | Will Woods <wwoods> | ||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 20 | CC: | akozumpl, brizuela.diego10, packaging-team-maint, pnemade, rholy, tflink, wwoods | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/a57a42b09284ded3c781f6fe7c98fc19b86408a2 | ||||||||
| Whiteboard: | abrt_hash:1a1a7fbc60f773dddcca48b9da74f2fb09f1c22d | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-06-24 01:33:57 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
diego brizuela
2013-11-16 20:24:50 UTC
Created attachment 824970 [details]
File: backtrace
Created attachment 824971 [details]
File: environ
Hello, how often does this happen, can you reproduce? what does 'rpm -q libcomps' output? Same core problem as bug 1029892. (if this happens on a proper installation where all the requirements are present, the theory I would incline to is that systemd activates the timer before all DNF components are in place during an rpm transaction and that (through OnBootSec=10min) immediately fires up 'dnf makecache' which is still missing some parts) (Turns out systemd does not activate the timer, it merely enables it.) another question diego, how do you update your system? libcomps not installed on my system, just install it I update a with fedora 19 to fedora 20 netwok fedup ok, its a fedup problem then. No, it's an upgrade problem. All fedup does is install packages; you are responsible for making sure your packages handle upgrades cleanly. For example: if the timer needs to be activated on upgrades, then you need to handle that in a %pre/%post script. Or: if there's missing dependencies, then you need to change your package dependencies to avoid that. Fedup can provide ways for you to fix these problems, but it's not responsible for fixing upgrade problems in other packages. the issue of timers was a false suspect, we cleared that up with the plumbers team.
The libcomps dependencies are not missing, they've been in f20 since late August. And they're correctly flagged in the dnf.spec:
Requires: python-libcomps >= %{libcomps_version}
Yet the users don't get it installed on their systems, see comment 7.
Works fine here: [ 28.057] (II) fedup.cli:inst_open_file() installing libcomps-0.1.4-4.fc20.x86_64.rpm (382/1300) [ 28.139] (II) fedup.cli:inst_open_file() installing python-libcomps-0.1.4-4.fc20.x86_64.rpm (741/1300) Can you attach your fedup.log and upgrade.log? it might or not be relevant that DNF is an Anaconda dep now (but so are indirectly libcomps, hawkey and librpeo). after fedup you need install libcomps |