Bug 472099 - zypper dup reinstall packages again and again
Summary: zypper dup reinstall packages again and again
Status: RESOLVED DUPLICATE of bug 426607
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: libzypp (show other bugs)
Version: Final
Hardware: 32bit Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-03 19:46 UTC by Daniele Tombolini
Modified: 2009-02-04 16:30 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
zypper log (190.77 KB, text/x-log)
2009-02-03 19:49 UTC, Daniele Tombolini
Details
debug-solver log (1.50 MB, application/x-gzip)
2009-02-03 19:52 UTC, Daniele Tombolini
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Daniele Tombolini 2009-02-03 19:46:18 UTC
User-Agent:       Mozilla/5.0 (compatible; Konqueror/4.2; Linux) KHTML/4.2.0 (like Gecko) SUSE

Hi, since yesterday zypper reinstall few packages from packman again and again..
zypper output:
kailed:/var/log # zypper -v dup
Verbosity: 1                   
Initializing Target            
Checking whether to refresh metadata for KDE42-COMMUNITY
Retrieving: repomd.xml [done]                           
Checking whether to refresh metadata for KDE42-DESKTOP  
Retrieving: repomd.xml [done]                           
Checking whether to refresh metadata for KDE42-EXTRA-APPS
Retrieving: repomd.xml [done]                            
Checking whether to refresh metadata for openSUSE 11.1-0 
Retrieving: content [done]                               
Retrieving: media [done]                                 
Checking whether to refresh metadata for NVIDIA Repository
Retrieving: repomd.xml [done]                             
Checking whether to refresh metadata for openSUSE-11.1-Non-Oss
Retrieving: content [done]                                    
Retrieving: media [done]                                      
Checking whether to refresh metadata for openSUSE-11.1-Update 
Retrieving: repomd.xml [done]
Checking whether to refresh metadata for Packman Repository
Retrieving: repomd.xml [done]
Checking whether to refresh metadata for openSUSE BuildService - Versioni CVS di Wine
Retrieving: repomd.xml [done]
Checking whether to refresh metadata for openSUSE BuildService - Virtualizzazione (VirtualBox)
Retrieving: repomd.xml [done]
Loading repository data...
Reading installed packages...
Computing distribution upgrade...
Force resolution: No
Computing upgrade...

The following packages are going to be reinstalled:
  ffmpeg-0.4.9.16851svn-20090129.pm.1858.i686  (Packman Repository)
  libavcodec52-0.4.9.16851svn-20090129.pm.1858.i686  (Packman Repository)
  libavdevice52-0.4.9.16851svn-20090129.pm.1858.i686  (Packman Repository)
  libavformat52-0.4.9.16851svn-20090129.pm.1858.i686  (Packman Repository)
  libavutil49-0.4.9.16851svn-20090129.pm.1858.i686  (Packman Repository)
  libpostproc51-0.4.9.16851svn-20090129.pm.1858.i686  (Packman Repository)
  libswscale0-0.4.9.16851svn-20090129.pm.1858.i686  (Packman Repository)
  libx264-65-0.0svn20090129-0.pm.0.i686  (Packman Repository)
  libx264-66-0.0svn20090129-0.pm.0.i686  (Packman Repository)


Overall download size: 2.5 M. No additional space will be used or freed after the operation.

log will follow



Reproducible: Always

Steps to Reproduce:
1.zypper dup with packman repo
2.
3.
Actual Results:  
always reinstall

Expected Results:  
don't reinstall already installed packages
Comment 1 Daniele Tombolini 2009-02-03 19:49:27 UTC
Created attachment 269761 [details]
zypper log

this is zypper log after saying no to zypper dup.
Comment 2 Daniele Tombolini 2009-02-03 19:52:36 UTC
Created attachment 269762 [details]
debug-solver log

This is debug-solver log for zypper -v dup --debug-solver
Comment 3 Michael Andres 2009-02-04 16:30:33 UTC
The solver selects them because their buildtime has changed.

*** This bug has been marked as a duplicate of bug 426607 ***