Bug 506702

Summary: zypper complains about not finding packages that could be downgraded via YaST.
Product: [openSUSE] openSUSE 11.1 Reporter: Elmar Stellnberger <estellnb>
Component: libzyppAssignee: Jan Kupec <jkupec>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P4 - Low CC: dmacvicar
Version: Final   
Target Milestone: ---   
Hardware: All   
OS: openSUSE 11.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: zypper log
y2log

Description Elmar Stellnberger 2009-05-23 09:54:24 UTC 
User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10 (like Gecko) SUSE

zypper in -f refuses to downgrade packages (Perhaps this should better/as well be handled by an own downgrade option: see Enh 506701).

> zypper in -f libdrm
Loading repository data...
Reading installed packages...
Package libdrm-2.4.11-1.1.x86_64 not found in repositories, cannot reinstall.
Resolving package dependencies...
Nothing to do.
... downgrading via Yast ...
> rpm -q libdrm
libdrm-2.4.1-1.13


Reproducible: Always
Comment 1 Elmar Stellnberger 2009-05-23 10:08:34 UTC 
Created attachment 294050 [details]
zypper log
Comment 2 Elmar Stellnberger 2009-05-23 10:09:36 UTC 
Created attachment 294052 [details]
y2log
Comment 3 Jan Kupec 2009-05-25 08:13:57 UTC 
(In reply to comment #0)
> zypper in -f refuses to downgrade packages

Because it's not supposed to. At least not now, but we'll improve the --force option in the future.

*** This bug has been marked as a duplicate of bug 483426 ***
Comment 4 Jan Kupec 2009-05-25 08:19:50 UTC 
JFYI: currently you can downgrade the packages by specifying their version, like this:

$ zypper in libdrm-2.4.1-1.13

HTH
Comment 5 Elmar Stellnberger 2009-05-25 09:49:21 UTC 
  If 'zypper in libdrm-2.4.1-1.13' works anyway it is perhaps better to leave 'zypper in --force' as is and provide an own downgrade command as proposed in Enh 506701.
Comment 6 Elmar Stellnberger 2009-05-25 09:50:01 UTC 
in Bug 506701.