On Thu, Jun 08, 2006 at 05:37:06PM +0200, Hartmut Meyer wrote:
> Hi,
> 
> Am Donnerstag, 8. Juni 2006 16:34 schrieb Hartmut Meyer:
> > Am Donnerstag, 8. Juni 2006 16:03 schrieb Adrian Schröter:
> > > Please give us any kind of feedback. We know that we are the package
> > > manager is not yet yet perfect, but this update should improve the
> > > situation a lot :)
> >
> > One thing I noticed when I try to install the libzypp update: among the
> > many packages that are listed as part of this patch, one of them is "rug".
> >
> > And it wants to keep it (rug-7.1.1.0-18) even though a newer version is
> > available (rug-7.1.1.0-18.9).
> >
> > See screenshot:
> >
> >   http://hmeyer.dyndns.org/beta/libzypp-update.png
> 
> More oddities (after installing the libzypp update and restarting zmd as 
> described in the readme):
> 
> YaST2 online_update and the ZEN updater do not show consistent results when 
> looking for available updates:
> 
>    http://hmeyer.dyndns.org/beta/libzypp-update-new.png
> 
> BTW: regarding the only update (ifolder3) that is offered through YaST2 
> online_update, YaST2 online_update complained that there is no source 
> available to fetch the suggested ifolder3 update (someting about 
> "atom:ifolder3...").
> 
> I then compared the installation sources in YaST2 with what rug is reporting 
> ("rug sl") and sure enough this isn't in sync. E.g. the 
> 10.1-packagemanagement-update-test catalog is listed as active by rug but as 
> inactive in YaST2.
> 
> And all the available updates that are listed by zen-updater but are not 
> listed by online_update are from that 10.1-packagemanagement-update-test 
> catalog.
> 
> Should we not expect that YaST2 and zen-updater/rug are completely in sync as 
> far as the installation sources are concerned?

rug sl .... it will likely show 2 update sources.

Please use only _one_ update source, either the test repo or the
public repo.

Ciao, marcus

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to