Bug 629703
Summary: | No good way to go from tigervnc-server -> tigervnc-server-minimal | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jesse Keating <jkeating> |
Component: | tigervnc | Assignee: | Adam Tkac <atkac> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 14 | CC: | atkac, dcantrell, ovasik |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-04-12 12:12:15 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: |
Description
Jesse Keating
2010-09-02 18:35:46 UTC
Which mechanism anaconda uses for package installation? AFAIK it uses "yum --installroot" so everything should be fine, shouldn't it? May I ask you for quick description how to reproduce this issue, please? Take a system that was installed prior to your split up and had anaconda the rpm installed. Try to yum update. Get above error. I believe this issue no longer exists, closing as WORKSFORME. If you still hit this issue, please reopen this bug. |