Bug 432938

Summary: Restarting aborted "zypper dup" reruns the *whole* transaction
Product: [openSUSE] openSUSE 11.1 Reporter: Klaus Kämpf <kkaempf>
Component: libzyppAssignee: E-mail List <zypp-maintainers>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P3 - Medium CC: adrian.schroeter, behlert, claes.backstrom, dmacvicar, felix, forgotten_qMyteedNxa, friesoft, gp, kukuk, locilka, ma, schubi, vuntz, wm
Version: Beta 2   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: zypper.log (bz2 compressed)
zypper dup solver testcase
zypper dup --debug-solver
zypper dup --debug-solver (Gerald Pfeifer, same problem after successful upgrade)

Description Klaus Kämpf 2008-10-07 09:07:30 UTC
I was running a 'zypper dup' from dir:///mounts/dist/...
For some unknown reason, autofs (or dist.suse.de) failed to provide data via /mounts/dist after upgrading ~1200 of 1541 packages.
So I changed the repo url from dir:/// to ftp://, run "zypper ref" and restarted the upgrade via "zypper dup".

However, zypper insists to reinstall *all* packages, although roughly 1200 of 1541 packages are already up to date.

Most puzzling, "zypper up" does not show any package updates.
Comment 1 Klaus Kämpf 2008-10-07 09:09:11 UTC
Created attachment 243856 [details]
zypper.log (bz2 compressed)
Comment 2 Michael Schröder 2008-10-07 09:38:47 UTC
Solver testcase?
Comment 3 Felix Möller 2008-10-09 09:18:21 UTC
I currently do not have access to my machine. But will try to generate a testcase tonight. This has been hapening for me for weeks. 

I am using the public download.opensuse.org/factory repositories.

I reported this on the #factory mailinglist yesterday.
Comment 4 Dave Plater 2008-10-09 10:04:45 UTC
Created attachment 244548 [details]
zypper dup solver testcase

maybe this will help?
Comment 5 Felix Möller 2008-10-09 17:53:06 UTC
Created attachment 244713 [details]
zypper dup --debug-solver

This attachement should provide Klaus' NEEDINFO.
Comment 6 Forgotten User qMyteedNxa 2008-10-12 09:55:45 UTC
i have the same problem - see 426607 
Comment 7 Felix Möller 2008-10-14 21:19:19 UTC
You are right Sei

Ok looking at my testcase I have in 136187112-package.xml:
<package>
        <name>3ddiag</name>
        <vendor></vendor>
        <buildtime>1222830577</buildtime>

and 
<package>
        <name>3ddiag</name>
        <vendor>openSUSE Build Service</vendor>
        <buildtime>1222830577</buildtime>
        <history>

Even after reinstalling the rpm with zypper in --force this stays the same.

Therfore this bug is not caused by the buildservice giving the same version for different buildtimes. So it is afaik not a dupe of bug #426607

Michael, you probably know better how to look at testcases ... ;)
Comment 8 Michael Schröder 2008-10-15 10:34:03 UTC
The installed packages always have a vendor, so reinstallation can't help. It's about the repository data.
Comment 9 Gerald Pfeifer 2008-10-18 20:10:33 UTC
I am seeing the same after a *successful* upgrade to FACTORY today.
Comment 10 Gerald Pfeifer 2008-10-18 20:12:30 UTC
Created attachment 246412 [details]
zypper dup --debug-solver (Gerald Pfeifer, same problem after successful upgrade)
Comment 11 Klaus Kämpf 2008-10-20 09:31:19 UTC
'susetags' repository data needs vendor information.

We either need 'Vnd:' for every package in suse/setup/descr/packages.gz
or 'VENDOR' in 'content' file.

Reassign to cthiel, CC to SLE release mgrs, CC to OBS prjmgr
Comment 13 Christoph Thiel 2008-10-20 10:26:31 UTC
This should be fixed in the content file now. Adrian?
Comment 14 Gerald Pfeifer 2008-10-20 22:55:59 UTC
On the system from comments #9 and #10:

  # zypper dup
  Loading repository data...
  Reading installed packages...
  Computing distribution upgrade...
  Nothing to do.

So, this seems to be resolved indeed?
Comment 15 Willem Meens 2008-10-24 07:27:45 UTC
Jumping in as I seem to have this same issue... running a fresh install of Beta3.
(I have run the latest updates using zypper up)

Gerald, what solved this for you?

-Wk
Comment 16 Bernhard Friedreich 2008-10-26 09:53:08 UTC
I'm having the same bug with a system installed from netinstall (somewhere between beta 2 and beta 3) updated to the latest available packages (I think they are from 2008-10-20) ... I have asolutely no idea what's wrong here atm..

Other repositories work for updating (in yast) .. 

When using zypper dup it always shows me all packages .. 

When using Yast -- software installation -- packages -- update packages if newer version is available -- no packages are shown.. seems a bit strange to me the whole thing..
Comment 17 Felix Möller 2008-10-27 22:12:11 UTC
OK I think most of this problem has been fixed with todays sync I am now at:
# LANG=CC zypper dup
Loading repository data...
Reading installed packages...
Computing distribution upgrade...

The following product is going to be downgraded:
  openSUSE


The following NEW package is going to be installed:
  openSUSE-release


The following product is going to change architecture:
  openSUSE


The following product is going to change vendor:
  openSUSE


Overall download size: 17.0 K. After the operation, additional 64.0 K will be used.
Continue? [YES/no]:

I can install just these packages again and again.
Comment 18 Adrian Schröter 2008-10-31 09:50:53 UTC
the vendor information are in packages files (not content). This should be correct.
Comment 19 Duncan Mac-Vicar 2008-11-04 09:00:10 UTC
Lowering severity. As it only happens with products now.
Comment 20 Michael Andres 2010-02-11 12:51:10 UTC
Fixed in 11.2