Mailinglist Archive: opensuse-packaging (139 mails)
| < Previous | Next > |
Re: [opensuse-packaging] rpm/lzma upgrade issue
- From: Stephan Kulow <coolo@xxxxxxx>
- Date: Fri, 28 Mar 2008 13:48:15 +0100
- Message-id: <200803281348.15744.coolo@xxxxxxx>
Am Freitag 28 März 2008 schrieb JP Rosevear:
as the payload should be a prereq.
So with some luck a bzip2 payload in rpm fixes the problem already.
are supported. Meaning: you need either do a manual step to fix it or
boot from medium to update.
Greetings, Stephan
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
Trying to upgrade to the latest internal rpm this morning (rev 181) fromThe question I have is if zypper will install rpm first - I guess it should
a factory box that hadn't been updated in a couple weeks I received the
following error:
rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by rpm-4.4.2-181.x86_64
Presumably because the older rpm could not update itself because of the
new payload requirements. Updating to the intermediate rev 179 that was
available in the public channel worked around the problem. There are
two potential issues:
1) People using zypp to upgrade factory may be halted from upgrades
as the payload should be a prereq.
So with some luck a bzip2 payload in rpm fixes the problem already.
For that reason neither zypper dup nor updates from within the system
and the more critical:
2) People on older distros may be unable to upgrade to 11.0 when it
comes out.
are supported. Meaning: you need either do a manual step to fix it or
boot from medium to update.
Greetings, Stephan
--
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
| < Previous | Next > |