Bug 163704 - request: platform <-> noarch updates
Summary: request: platform <-> noarch updates
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-20 15:07 UTC by Joe Harrington
Modified: 2014-01-21 22:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-07-20 21:27:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Joe Harrington 2005-07-20 15:07:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.21

Description of problem:
Occasionally, a package switches from architecture-specific to noarch, or possibly vice-versa.  Yum update does not handle these situations.  For example, recently system-config-netboot went to noarch.  Nightly yum updates did not take the update, and yum update did not issue an error or warning when executed manually (nor should it have, officially).  Up2date did detect the situation, and wanted to do the update (but nightly updates use yum).

It would be good either to detect this situation and warn about it, or simply to do the update.  If that's not possible, it should be possible to put into the updated package a flag telling yum that it obsoletes architecture-specific versions, so that yum then does the update automatically.  Likely, what works for up2date will work for yum.


Version-Release number of selected component (if applicable):
yum-2.2.1-0.fc3

How reproducible:
Always

Steps to Reproduce:
1. Install FC3
2. Do a yum update
3. Notice that system-config-netboot didn't update
  

Actual Results:  system-config-netboot didn't update


Expected Results:  system-config-netboot should have updated


Additional info:

--jh--

Comment 1 Seth Vidal 2005-07-20 18:13:10 UTC
Yum 2.3.X fixes this problem.
I doubt this change will be backported.


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