Bug 492634 - anaconda doesn't handle repo=hd::/path (preupgrade special case)
Summary: anaconda doesn't handle repo=hd::/path (preupgrade special case)
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Lehman
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 492516 F11AnacondaBlocker
TreeView+ depends on / blocked
 
Reported: 2009-03-27 19:09 UTC by Will Woods
Modified: 2009-04-16 17:17 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-04-16 17:17:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Will Woods 2009-03-27 19:09:28 UTC
In Fedora 10 and earlier, there's a special case in yuminstall.py (see line 401 in current git) for handling "repo=hd:device:/path" when the system is booted with "preupgrade" on the commandline:

      (device, fstype, path) = m[3:].split(":")

  if flags.cmdline.has_key("preupgrade"):
      self._baseRepoURL = "file:///mnt/sysimage/%s" % path

As you can see, the device name is discarded and yum is instructed to get its packages from the given path, on the mounted system. Hence preupgrades are booted with:
  
  preupgrade repo=hd::/var/cache/yum/preupgrade [etc]

The new anaconda storage code needs to handle this special case, or provide another way for preupgrade to specify that the upgrade should get its packages from a certain path on the filesystem being upgraded - for example, "repo=file:///..."

Comment 1 Chris Lumens 2009-03-27 19:18:04 UTC
dlehman had a plan for dealing with this that involved making an empty path resolve to a FileDevice.

Comment 2 David Lehman 2009-04-16 16:09:57 UTC
Can you retest with anaconda-11.5.0.40-1 or later?

Comment 3 Will Woods 2009-04-16 17:17:55 UTC
I have an upgrade from F10->Rawhide (anaconda 11.5.0.44 IIRC) at the "Finishing upgrade process step." Everything seems have worked as expected.


Note You need to log in before you can comment on or make changes to this bug.