[opensuse-packaging] rpm/lzma upgrade issue
Trying to upgrade to the latest internal rpm this morning (rev 181) from 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 and the more critical: 2) People on older distros may be unable to upgrade to 11.0 when it comes out. Coolo suggested we might need to define some core packages that don't use the new payload system so upgrades work, but it seems like it yast potentially we'd have to upgrade rpm first and then upgrade the packages even if we fix that. -JP -- JP Rosevear <jpr@novell.com> Novell, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Freitag 28 März 2008 schrieb JP Rosevear:
Trying to upgrade to the latest internal rpm this morning (rev 181) from 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 The question I have is if zypper will install rpm first - I guess it should as the payload should be a prereq.
So with some luck a bzip2 payload in rpm fixes the problem already.
and the more critical:
2) People on older distros may be unable to upgrade to 11.0 when it comes out.
For that reason neither zypper dup nor updates from within the system 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@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Freitag 28 März 2008 schrieb Stephan Kulow:
So with some luck a bzip2 payload in rpm fixes the problem already.
... submitted. Let's hope for the best :) Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
JP Rosevear wrote:
rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by rpm-4.4.2-181.x86_64 ...
2) People on older distros may be unable to upgrade to 11.0 when it comes out.
The rpm on the 11.0 media will be lzma-enabled. This would only hit users trying to update a running <11.0 system to 11.0.
Coolo suggested we might need to define some core packages that don't use the new payload system so upgrades work, but it seems like it yast potentially we'd have to upgrade rpm first and then upgrade the packages even if we fix that.
zypp could be "smart" :) and try to update to latest available rpm if it sees a package with unsatisfied rpmlib dependency. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Michal Marek wrote:
JP Rosevear wrote:
Coolo suggested we might need to define some core packages that don't use the new payload system so upgrades work, but it seems like it yast potentially we'd have to upgrade rpm first and then upgrade the packages even if we fix that.
zypp could be "smart" :) and try to update to latest available rpm if it sees a package with unsatisfied rpmlib dependency.
The problem might be that zypp can't know whether the install will succeed before actually updating to new rpm :( Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Freitag 28 März 2008 schrieb Michal Marek:
Michal Marek wrote:
JP Rosevear wrote:
Coolo suggested we might need to define some core packages that don't use the new payload system so upgrades work, but it seems like it yast potentially we'd have to upgrade rpm first and then upgrade the packages even if we fix that.
zypp could be "smart" :) and try to update to latest available rpm if it sees a package with unsatisfied rpmlib dependency.
The problem might be that zypp can't know whether the install will succeed before actually updating to new rpm :(
The rpmlib dependencies need to be provided by the rpm. So it should know pretty well. The problem is if rpm itself requires it. Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Stephan Kulow wrote:
Am Freitag 28 März 2008 schrieb Michal Marek:
The problem might be that zypp can't know whether the install will succeed before actually updating to new rpm :(
The rpmlib dependencies need to be provided by the rpm. So it should know pretty well. The problem is if rpm itself requires it.
The rpm package has never provided these special rpmlib dependencies (because it's the rpm opening the package that matters, not the rpm installed in the system), so does zypp resolve these dependencies at all? Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Fri, Mar 28, 2008 at 03:17:55PM +0100, Michal Marek wrote:
The rpm package has never provided these special rpmlib dependencies (because it's the rpm opening the package that matters, not the rpm installed in the system), so does zypp resolve these dependencies at all?
The rpmlib() dependency are internally provided by rpm, see the output of 'rpm --showrc'. Currently, the solver ignores all rpmlib() dependency as it doesn't know the features of the rpm it uses. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michal Marek wrote: | JP Rosevear wrote: |> rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by rpm-4.4.2-181.x86_64 | ... |> 2) People on older distros may be unable to upgrade to 11.0 when it |> comes out. | The rpm on the 11.0 media will be lzma-enabled. This would only hit | users trying to update a running <11.0 system to 11.0. "only" ? Errm... you're kidding, right ? ;) - -- ~ -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ ~ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> ~ _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFH7PPBr3NMWliFcXcRAluAAJsFxLCzTzJMqmBUEXCUiGfpJ2dnnACgqpTs d35MIbLO6AyFmfD4TzTIc5M= =lNEV -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am Freitag 28 März 2008 schrieb Pascal Bleser:
Michal Marek wrote: | JP Rosevear wrote: |> rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by rpm-4.4.2-181.x86_64 | | ... | |> 2) People on older distros may be unable to upgrade to 11.0 when it |> comes out. | | The rpm on the 11.0 media will be lzma-enabled. This would only hit | users trying to update a running <11.0 system to 11.0.
"only" ? Errm... you're kidding, right ? ;) The point is "running system". You might think of people that boot a 11.0 medium to update a static system.
Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Pascal Bleser wrote:
Michal Marek wrote: | JP Rosevear wrote: |> rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by rpm-4.4.2-181.x86_64 | ... |> 2) People on older distros may be unable to upgrade to 11.0 when it |> comes out. | The rpm on the 11.0 media will be lzma-enabled. This would only hit | users trying to update a running <11.0 system to 11.0.
"only" ? Errm... you're kidding, right ? ;)
You missed the "running" or what makes you worry? Users who update a _running_ system to a newer version should know what they are doing, AFAIK it has always been that way. I didn't say anything about the "normal" update (insert DVD; reboot; wait; reboot; enjoy). Michal --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michal Marek wrote: | Pascal Bleser wrote: |> Michal Marek wrote: |> | JP Rosevear wrote: |> |> rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by rpm-4.4.2-181.x86_64 |> | ... |> |> 2) People on older distros may be unable to upgrade to 11.0 when it |> |> comes out. |> | The rpm on the 11.0 media will be lzma-enabled. This would only hit |> | users trying to update a running <11.0 system to 11.0. |> |> "only" ? Errm... you're kidding, right ? ;) | | You missed the "running" or what makes you worry? Users who update a | _running_ system to a newer version should know what they are doing, | AFAIK it has always been that way. I didn't say anything about the | "normal" update (insert DVD; reboot; wait; reboot; enjoy). Well yes, obviously, a cold upgrade has to work :) I didn't miss the hot upgrade part. But, from what I read above, you're basically saying that it may (will ?) not work for people who shall upgrade a running 10.3 to 11.0 (using yast2's system upgrade, zypper, smart, whatever). Or did I miss something there ? There's a difference between "should know what they are doing" and not possible at all. Unless, of course, there's a documented way of performing that upgrade - -- e.g. upgrading rpm from 10.3's to 11.0's first, then doing the rest. Would that work ? cheers - -- ~ -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ ~ /\\ <pascal.bleser@skynet.be> <guru@unixtech.be> ~ _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFH7XNjr3NMWliFcXcRAuV2AJ0RFv3cXNuCBEDVuKXc/5TCYqEbpACeNBGd Z92ast46cdeA3dakYcGw2Dk= =3wQS -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Friday 28 March 2008 23:38:27 wrote Pascal Bleser:
Michal Marek wrote: | Pascal Bleser wrote: |> Michal Marek wrote: |> | JP Rosevear wrote: |> |> rpmlib(PayloadIsLzma) <= 4.4.2-1 is needed by rpm-4.4.2-181.x86_64 |> | |> | ... |> | |> |> 2) People on older distros may be unable to upgrade to 11.0 when it |> |> comes out. |> | |> | The rpm on the 11.0 media will be lzma-enabled. This would only hit |> | users trying to update a running <11.0 system to 11.0. |> |> "only" ? Errm... you're kidding, right ? ;) | | You missed the "running" or what makes you worry? Users who update a | _running_ system to a newer version should know what they are doing, | AFAIK it has always been that way. I didn't say anything about the | "normal" update (insert DVD; reboot; wait; reboot; enjoy).
Well yes, obviously, a cold upgrade has to work :)
I didn't miss the hot upgrade part. But, from what I read above, you're basically saying that it may (will ?) not work for people who shall upgrade a running 10.3 to 11.0 (using yast2's system upgrade, zypper, smart, whatever).
Or did I miss something there ? There's a difference between "should know what they are doing" and not possible at all.
Unless, of course, there's a documented way of performing that upgrade -- e.g. upgrading rpm from 10.3's to 11.0's first, then doing the rest. Would that work ?
yes, this should work. -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (6)
-
Adrian Schröter -
JP Rosevear -
Michael Schroeder -
Michal Marek -
Pascal Bleser -
Stephan Kulow