[zypp-devel] syncing zypper lu -t package and up -t package
'zypper lu -t package' currently lists all packages for which there is a newer version available, regardless whether it installable or not. OTOH, 'zypper up -t package' uses solver's doUpdate(). The results are quite different. E.g. on my workstation i currently get 2000+ packages with 'lu' while 'up' wants to upgrade only around 50. I'd like to fix this for 11.0 and there are basically two ways: 1) fix 'lu' to display what doUpdate() proposes 2) fix 'up' to install what 'lu' currently proposes (don't use doUpdate()) I would like to do 2) but i wonder why doUpdate() yields soooo different results than simple checking for newer version (doUpgrade() yields much saner number). It's clear that it is not the same, but it should not be _that_ different, too. If this is caused by some easily fixable bug, i'd go for 2), otherwise i'd do 1). What do you think? cheers, jano https://bugzilla.novell.com/show_bug.cgi?id=392591 -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Jan Kupec wrote:
'zypper lu -t package' currently lists all packages for which there is a newer version available, regardless whether it installable or not.
OTOH, 'zypper up -t package' uses solver's doUpdate().
The results are quite different. E.g. on my workstation i currently get 2000+ packages with 'lu' while 'up' wants to upgrade only around 50.
I'd like to fix this for 11.0 and there are basically two ways:
1) fix 'lu' to display what doUpdate() proposes 2) fix 'up' to install what 'lu' currently proposes (don't use doUpdate())
Swap 2 and 1 from now on (sorry):
I would like to do 2) but i wonder why doUpdate() yields soooo different results than simple checking for newer version (doUpgrade() yields much saner number). It's clear that it is not the same, but it should not be _that_ different, too.
If this is caused by some easily fixable bug, i'd go for 2), otherwise i'd do 1). What do you think?
cheers, jano
-- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
* Jan Kupec <jkupec@suse.cz> [Jun 03. 2008 16:00]:
'zypper lu -t package' currently lists all packages for which there is a newer version available, regardless whether it installable or not.
OTOH, 'zypper up -t package' uses solver's doUpdate().
The results are quite different. E.g. on my workstation i currently get 2000+ packages with 'lu' while 'up' wants to upgrade only around 50.
I'd like to fix this for 11.0 and there are basically two ways:
Please don't.
1) fix 'lu' to display what doUpdate() proposes 2) fix 'up' to install what 'lu' currently proposes (don't use doUpdate())
I would like to do 2) but i wonder why doUpdate() yields soooo different results than simple checking for newer version (doUpgrade() yields much saner number). It's clear that it is not the same, but it should not be _that_ different, too.
If this is caused by some easily fixable bug, i'd go for 2), otherwise i'd do 1). What do you think?
The difference is right and should be shown. I agree, the current output is puzzling and might need some additional explanation. Actually, there are three different views on available updates 1) Any update for installed packages This is (according to my current understanding) the 'lu -t package' output. It just takes the individual package into account. 2) Installable update for installed packages This should limit the list from 1) above to actually installable updates. Each such update is still looked at individually. 3) Complete update This is (according to my current understanding) the 'up -t package' output. This is a further reduction to the list from 2), taking the complete transaction into account. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Klaus Kaempf wrote:
* Jan Kupec <jkupec@suse.cz> [Jun 03. 2008 16:00]:
The results are quite different. E.g. on my workstation i currently get 2000+ packages with 'lu' while 'up' wants to upgrade only around 50.
The difference is right and should be shown. I agree, the current output is puzzling and might need some additional explanation.
Actually, there are three different views on available updates
1) Any update for installed packages This is (according to my current understanding) the 'lu -t package' output. It just takes the individual package into account.
2) Installable update for installed packages This should limit the list from 1) above to actually installable updates. Each such update is still looked at individually.
3) Complete update This is (according to my current understanding) the 'up -t package' output. This is a further reduction to the list from 2), taking the complete transaction into account.
This all sounds great, but how can the difference be so huge? I find it hard to believe that this is OK. It is 2000 vs 50! cheers, jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
* Jan Kupec <jkupec@suse.cz> [Jun 04. 2008 16:12]:
Klaus Kaempf wrote:
* Jan Kupec <jkupec@suse.cz> [Jun 03. 2008 16:00]:
The results are quite different. E.g. on my workstation i currently get 2000+ packages with 'lu' while 'up' wants to upgrade only around 50.
The difference is right and should be shown. I agree, the current output is puzzling and might need some additional explanation.
Actually, there are three different views on available updates
1) Any update for installed packages This is (according to my current understanding) the 'lu -t package' output. It just takes the individual package into account.
2) Installable update for installed packages This should limit the list from 1) above to actually installable updates. Each such update is still looked at individually. 3) Complete update This is (according to my current understanding) the 'up -t package' output. This is a further reduction to the list from 2), taking the complete transaction into account.
This all sounds great, but how can the difference be so huge? I find it hard to believe that this is OK. It is 2000 vs 50!
Yeah, thats a valid question. Maybe Michael can answer this. Klaus -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Wed, Jun 04, 2008 at 04:21:31PM +0200, Klaus Kaempf wrote:
This all sounds great, but how can the difference be so huge? I find it hard to believe that this is OK. It is 2000 vs 50!
Yeah, thats a valid question. Maybe Michael can answer this.
Not really. If I generate a solver testcase and run the solver with updatesystem set to true, it also selects >1000 packages. Seems to be a bug somewhere else... M. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Thu, Jun 05, 2008 at 11:56:27AM +0200, Michael Schroeder wrote:
On Wed, Jun 04, 2008 at 04:21:31PM +0200, Klaus Kaempf wrote:
This all sounds great, but how can the difference be so huge? I find it hard to believe that this is OK. It is 2000 vs 50!
Yeah, thats a valid question. Maybe Michael can answer this.
Not really. If I generate a solver testcase and run the solver with updatesystem set to true, it also selects >1000 packages. Seems to be a bug somewhere else...
Uh oh, not true actually. It is a bug in the solver, it depends on when the system repository is added to the pool. That's why it works in the solver testcase, where system always comes first... Fixing... 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: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
participants (3)
-
Jan Kupec -
Klaus Kaempf -
Michael Schroeder