Bug 342394

Summary: boost update conflict with zypper / libzypp
Product: [openSUSE] openSUSE 10.3 Reporter: Rémy Marquis <remy.marquis>
Component: libzyppAssignee: Duncan Mac-Vicar <dmacvicar>
Status: RESOLVED FIXED QA Contact: Duncan Mac-Vicar <dmacvicar>
Severity: Blocker    
Priority: P1 - Urgent CC: bjoernv, coolo, dave, hmuelle, luc, meissner, pth, svgunhouse, tgoettlicher
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: evidence of the mess.

Description Rémy Marquis 2007-11-16 20:30:11 UTC
The last boost update (4704-0, v.1.33.1-108.2, from 16th November) conflict with package management basis system. Both zypper and libzypp are uninstalled.

And thus, no more package management after this "recommanded update" :(
Comment 1 Benjamin Weber 2007-11-16 21:01:37 UTC
*** Bug 342430 has been marked as a duplicate of this bug. ***
Comment 2 Benjamin Weber 2007-11-16 21:01:45 UTC
*** Bug 342401 has been marked as a duplicate of this bug. ***
Comment 3 David Thorp 2007-11-16 21:06:50 UTC
So how can we get package management back now?

If it's not already been done may be idea to remove the update from the repository otherwise we're gonna end up with a lot of people with a critical problem
Comment 4 Marcus Meissner 2007-11-16 21:12:24 UTC
the update has been removed from the repository
Comment 5 David Thorp 2007-11-16 21:55:29 UTC
Ok to solve (for anyone still desperate to get package management back)

Go to http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/ and pick up the following three packages and save them to their own folder (all 3 packages in one folder)

http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/libzypp-3.26.2-2.i586.rpm
http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/boost-1.33.1-108.i586.rpm
http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/zypper-0.8.23-7.i586.rpm

Open a shell and su to root

cd to the folder you put them in

rpm -e boost-1.33.1-108.2 (which erases the wonderfully and thoroughly tested package that caused the mess)
rpm -ivh *.*

Right click on the opensuse updater and click check now and all should be back to normal
Comment 6 Harald Mueller-Ney 2007-11-17 10:51:01 UTC
Rudi, we need to remove latest boost update immediately

I will give you a call.
Comment 7 Harald Mueller-Ney 2007-11-17 11:44:37 UTC
(In reply to comment #5 from David Thorp)
> Ok to solve (for anyone still desperate to get package management back)

Many thanks for your hint!

Do make it maybe a bit easier, use this a root:

export ARCH=$(rpm -q --qf "%{ARCH}\n" aaa_base)
rpm -e boost-doc; rpm -e boost-devel; rpm -e boost;
rpm -Uvh \
        http://download.opensuse.org/distribution/10.3/repo/oss/suse/$ARCH/libzypp-3.26.2-2.$ARCH.rpm \
        http://download.opensuse.org/distribution/10.3/repo/oss/suse/$ARCH/boost-1.33.1-108.$ARCH.rpm \
        http://download.opensuse.org/distribution/10.3/repo/oss/suse/$ARCH/zypper-0.8.23-7.$ARCH.rpm


We need to take care of ARCH to install matching architecture for Power and x86 64bit
Ignore Errors on "rpm -e", your system might not have all subpackages of boost.


Right click on the opensuse updater and click check now and all should be back
to normal
Comment 8 Harald Mueller-Ney 2007-11-17 11:46:49 UTC
Udpate is removed already since yesterday night.

Duncan, you find out what went wrong that libzypp and zypper was uninstalled due boost update?
Comment 10 Cristian Rodriguez 2007-11-17 14:53:34 UTC
Created attachment 183795 [details]
evidence of the mess.
Comment 11 Stephan Kulow 2007-11-17 15:20:43 UTC
boost does no longer provide the libraries needed and zypper was asked to put that update into the system at all costs. 

It would be a feature request for the whole update stack to refuse updates that would remove packages not listed in the patch. But I had another case where the debuginfo needed to be removed, but these are removed without any notice too. 

So the bug is FIXED, the feature worth tracking
Comment 12 Duncan Mac-Vicar 2007-11-27 13:46:34 UTC
Moved to feature #303033