Bug 160381
Summary: | "Upgrade on next boot" rpm | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | John <jsk29> |
Component: | anaconda-images | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | Keywords: | FutureFeature |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-06-16 20:15:25 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
John
2005-06-14 20:04:58 UTC
The problem is that this can't be done, eg, on FC3 for the upgrade to FC4 and it's entirely possible that a package built for FC4 won't work with FC3 Sorry, I don't get why it won't work... why would you need to install an FC4 package under FC3? The idea would be, once FC5, say, becomes available, push an FC4 package to the FC4 mirrors which only contains a boot image for the FC5 installer. Package installation installs the appropriate grub menu entry, too. Upon booting using that menu entry, an FC5 network boot proceeds as usual. It has worked previously by hand... is there some problem I don't get which precludes the packaging? |