Bug 288263

Summary:	Please sync publishing libzypp and yast2* packages
Product:	[openSUSE] openSUSE 10.3	Reporter:	Hans-Peter Holler <holler>
Component:	libzypp	Assignee:	Lars Vogdt <lars.vogdt>
Status:	RESOLVED WONTFIX	QA Contact:	Stanislav Visnovsky <visnov>
Severity:	Enhancement
Priority:	P5 - None	CC:	aj, dmacvicar, ma, markus.kossmann, mmarek
Version:	Alpha 5
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Hans-Peter Holler 2007-06-28 18:54:41 UTC

Update from factory today installs libzypp-3.3.1-2 with libzypp.so.303.0.1.

For example Yast2 package yast2-update (yast2-update-2.15.13-11 not updated/sync'd in factory yet) needs libzypp.so.302.2.2 and fails to start.

ln -s libzypp.so.303.0.1 libzypp.so.302.2.2 resolves this, but this is ugly, of course.

So please sync developing and publishing of libzypp and yast2 modules.

THX.

sh: I know you are not responsible for libzypp, but probably you know the right people.

Comment 1 Hans-Peter Holler 2007-06-28 19:01:54 UTC

Sorry, of course this is an enhancement.

Comment 2 Stefan Hundhammer 2007-06-29 09:28:08 UTC

I didn't change anything, so it's not the UI's fault.

Comment 3 Stefan Hundhammer 2007-06-29 11:36:56 UTC

Oops - wrong reassignment, assigning back to lrupp

Comment 4 Lars Vogdt 2007-06-29 11:42:54 UTC

That's something we try to avoide - but sometimes we run into trouble:
Normally we just sync when nearly everything is finished (exept some "big"
packages like OpenOffice). Sometimes we have failing packages - and that would
avoid a sync because the packages can be "base" packages.

So we have a simple solution which is not everytime as good as it perhaps
should be: if a package failes three times, we ignore it and sync nevertheless.
Thinking "this can't be a base package because someone would have fixed it
otherwise".

This might be happen to libzypp and/or the depending yast2 packages.

If we wait until every package is fixed and the whole tree (factory) is ready,
it can happen that this is just once a month.

So it's a difficult situation - but this is what happens with our factory
branch: sometimes it might be broken... ...and I'm happy that you've already
found a temporary workaround.

I'm closing this as fixed as this should be fixed with the next sync. But we
must expect such problems with the current sync logic. ...and I don't think we
can fix this if we want factory to be synced as often as possible. It's
development - and sometimes developers break some things...

Comment 5 Hans-Peter Holler 2007-06-29 14:29:40 UTC

This was a _System Update_ from factory before the last sync to current.
Because build-numbers of yast-packages didn't increment, YaST didn't update these packages. But the packages _are_ linked against the new libzypp. Installing them with --force resolves the problem.
So maybe a little magic to increase the buildnumber if a needed library changes could be helpful.

Comment 6 Andreas Jaeger 2007-06-30 09:05:31 UTC

Lars, have a look at comment #5.  It seems that we did not increase build numbers!

Comment 7 Hans-Peter Holler 2007-07-02 05:58:57 UTC

*** Bug 288754 has been marked as a duplicate of this bug. ***

Comment 8 Jesse Michael 2007-07-02 18:02:32 UTC

It's not just yast, the latest version of zypper available in factory is linked against the older version of libzypp as well.

Comment 9 Hans-Peter Holler 2007-07-02 20:13:11 UTC

HOLY SHIT! :-(
comment #5 is completely wrong!
I just forget to delete the ugly symlink mentioned in description.
Installing related packages with --force does nothing better.
So please treat this as enhancement that probably never can be resolved.