Re: SPAM: libzypp + rug not updated on one go

[Marcus Meissner]

On Wed, Aug 02, 2006 at 10:12:48AM +0300, Silviu Marin-Caea wrote:

> On a newly installed 10.1, the first update it's libzypp.  That's fine.
>
> After downloading and applying that, there's another libzypp update!  That's
> starting to be confusing.  People start asking, didn't the first go well or
> what?
>
> After that, there's a rug update with the zen-updater.
>
> Only alfter all those are applied we have a working update system.
>
> Can't they be merged into just _one_ megaupdate?

The update system has bugs that do this, so these 3 calls are intentional.

We would have to fix your CD images remotely.

You will note that it downloads and installs the RPMs just _once_
and only does 3 runs with different patches (without downloading, or
just downloading rug).

Ciao, Marcus

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[andreas.hanke]

Hi,

Marcus Meissner schrieb:
> The update system has bugs that do this, so these 3 calls are intentional.

One of the 3 calls is actually caused by a rug packaging bug (the
self-provides bug) and not the update system. But the updated update
system has a workaround, so it works after the 3rd call.

> You will note that it downloads and installs the RPMs just _once_
> and only does 3 runs with different patches (without downloading, or
> just downloading rug).

Would it be possible to avoid the 3rd call (where just rug is installed)
by using a virtual symbol?

The bug is caused by the rug package on the CDs having:

Provides: rug

which causes it to provide all versions.

Something like this could be added:

Provides: rug-fixed = %{version}-%{release}

The patch could then require rug-fixed instead of rug. Would it work?

Andreas Hanke

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]