Bug 244487
Summary: | gschem missing needed dependencies in rpm | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chris Caudle <chris> | ||||||
Component: | geda-gschem | Assignee: | Chitlesh GOORAH <chitlesh> | ||||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | rawhide | ||||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2007-06-17 02:58:11 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
Chris Caudle
2007-06-16 01:17:39 UTC
Something is broken somewhere, because yum should pull those dependencies by itself. Can you give me the output of rpm -qR geda-gschem please ? Was your installation successfully ? Created attachment 157195 [details]
yum log
This is the log showing geda-gschem being installed on June 14. Libgeda was
not installed until June 15 when I installed in by hand.
Created attachment 157196 [details]
the output of rpm -qR geda-gschem
The output of rpm -qR geda-gschem shows libgeda and libstroke, so it is not
obvious why yum did not pull those two libraries in automatically.
I removed libgeda and libstroke using yum, and it correctly insisted on removing all the geda-* packages because of dependencies. I re-installed geda-gschem using yum, and it pulled in libstroke and libgeda like it should. I have no idea why it failed the first time. Maybe I was pulling from an out of date mirror or something. Anyway, since the behavior can not be duplicated, this bug can be closed. |