Dňa Friday 18 April 2008 10:43:27 Dr. Peter Poeml ste napísal:

On Fri, Apr 18, 2008 at 10:39:03AM +0200, Michael Schroeder wrote:

...

On Fri, Apr 18, 2008 at 10:37:36AM +0200, Dr. Peter Poeml wrote:

...

stupid question, how do I avoid that zypper removes the installed kernel packages (when updating)?

The following packages are going to be REMOVED: kernel-default kernel-default kernel-default kernel-default kernel-default kernel-default

I need to keep those.

Is that 11.0? Currently you can't, support for keeping multiple packages is not implemented yet in the solver. (It will be there for the final 11.0, of course.)

Sorry, Michael.

Yes, that's 11.0. Great to hear that it'll be implemented, it is a long-standing critical feature for me (one of the reasons I need to use yum so far).

Short of that, can I update selected packages? It doesn't seem to be possible, but I'm probably missing something. For example, I'd like to update the zypper package:

# zypper update -t package zypper Too many arguments. Usage: [...]

zypper install -t package zypper Stano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Stanislav Visnovsky wrote:

Dňa Friday 18 April 2008 10:43:27 Dr. Peter Poeml ste napísal:

...

On Fri, Apr 18, 2008 at 10:39:03AM +0200, Michael Schroeder wrote:

...

...

stupid question, how do I avoid that zypper removes the installed kernel packages (when updating)?

The following packages are going to be REMOVED: kernel-default kernel-default kernel-default kernel-default kernel-default kernel-default

I need to keep those. Is that 11.0? Currently you can't, support for keeping multiple

On Fri, Apr 18, 2008 at 10:37:36AM +0200, Dr. Peter Poeml wrote: packages is not implemented yet in the solver. (It will be there for the final 11.0, of course.)

Sorry, Michael. Yes, that's 11.0. Great to hear that it'll be implemented, it is a long-standing critical feature for me (one of the reasons I need to use yum so far).

Short of that, can I update selected packages? It doesn't seem to be possible, but I'm probably missing something. For example, I'd like to update the zypper package:

# zypper update -t package zypper Too many arguments. Usage: [...]

zypper install -t package zypper

-t package is not needed here, it is the default. Actually zypper update -t package foo*? has been implemented recetly, too :O) check zypper 0.11.0 BTW: can we resolve the question of -t patch being the default for update? (start new thread please). Cheers, jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Dr. Peter Poeml wrote:

On Fri, Apr 18, 2008 at 03:22:13PM +0200, Jan Kupec wrote:

...

...

...

Short of that, can I update selected packages? It doesn't seem to be possible, but I'm probably missing something. For example, I'd like to update the zypper package:

# zypper update -t package zypper Too many arguments. Usage: [...] zypper install -t package zypper

-t package is not needed here, it is the default.

Actually zypper update -t package foo*? has been implemented recetly, too :O) check zypper 0.11.0

Indeed, update foo* is accepted now -- I'm at 0.11.0 now, after updating zypper.

But it doesn't look quite right:

# zypper update zypper Reading installed packages... Patch 'zypper' not found.

remember the -t package -t package is the default for 'install' -t patch is the default for 'update'

The following NEW packages are going to be installed: obex-data-server openobex mozilla-xulrunner190-gnomevfs libarchive2 gvfs-fuse fuse libsoup gvfs-backends libsoup-2_4-1 libfuse2

Overall download size: 752.0 K. After the operation, additional 3.5 M will be used. Continue? [YES/no]:

It intends to update packages that I didn't specify. Known bug?

Yes, see the other thread "zypper odds" here on zypp-devel. jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Dr. Peter Poeml wrote:

On Fri, Apr 18, 2008 at 03:30:43PM +0200, Jan Kupec wrote:

...

...

But it doesn't look quite right:

# zypper update zypper Reading installed packages... Patch 'zypper' not found. remember the -t package

-t package is the default for 'install' -t patch is the default for 'update'

Ah, confusing.

I tried with -t package also BTW, but it behaves exactly the same:

# zypper update -t package zypper Reading installed packages... No update candindate for 'zypper'

At least it did confirm it knows zypper :O) This message means you have the best version already installed - there's no update available.

The following NEW packages are going to be installed: obex-data-server openobex mozilla-xulrunner190-gnomevfs libarchive2 gvfs-fuse fuse libsoup gvfs-backends libsoup-2_4-1 libfuse2

and this is the buggy stuff...

Overall download size: 752.0 K. After the operation, additional 3.5 M will be used. Continue? [YES/no]: n

...

...

It intends to update packages that I didn't specify. Known bug? Yes, see the other thread "zypper odds" here on zypp-devel.

Okay. I admit I don't understand that thread and whether the existence of the bug is acknowledged. But the report is about the same problem, definitely. Sorry for reporting it again. I didn't look closely enough when I skimmed that thread, and didn't recognize it when it happened to me now.

of course, no problem. jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

* Michael Andres [Apr 18. 2008 11:12]:

On Fri, Apr 18, Dr. Peter Poeml wrote:

...

...

Is that 11.0? Currently you can't, support for keeping multiple packages is not implemented yet in the solver. (It will be there for the final 11.0, of course.)

Sorry, Michael.

Yes, that's 11.0. Great to hear that it'll be implemented, it is a long-standing critical feature for me (one of the reasons I need to use yum so far).

'implemented in the solver'

We nedd zypper and UI support for this otherwise no one can use it.

Is it on the feature lists?

#301979: Install multiple versions of a package Klaus -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

* Michael Andres [Apr 18. 2008 16:35]:

On Fri, Apr 18, Klaus Kaempf wrote:

...

...

'implemented in the solver'

We nedd zypper and UI support for this otherwise no one can use it.

Is it on the feature lists?

#301979: Install multiple versions of a package

I actually wanted to know if we have a plan how to do it ;)

1st: Who decides which packages are to be installed with -i?

The user!?

Yes. At least, this is what I remember from previous discussions on this topic. A patch, as it contains additional information about an update, should also be able to request "-i" vs. "-U" for a package. This helps kernel installs, where "-i" should be the default without requiring user interaction. (We still need a way to limit the number of parallel installed kernels)

Persistent via some file in /etc/zypp? Similar to locks?

I do not see any need to make this persistent.

- I.e. a collection of query expressions describing installed packages. (or a flat list of package names).

- Matching packages get the 'keep on update' bit set in their status.

- This is then promoted to the solver to indicate the package will be installed with -i (not -U).

2nd: Is it required that also available packages in some repo indicate the desire to be installed with -i?

No, I do not think so.

If yes, we have to decide what to do if some package in a repo says '-i', but the user did not define 'keep on update' in /etc/...?

- zypp.conf option?: Follow 'keep on update' requests: (never/always/ask)

- Or per .repo?

- Both.

Klaus -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

On Mon, Apr 21, 2008 at 02:50:11PM +0200, Jan Kupec wrote:

Klaus Kaempf wrote:

...

* Michael Andres [Apr 18. 2008 16:35]:

...

1st: Who decides which packages are to be installed with -i?

The user!?

Yes.

At least, this is what I remember from previous discussions on this topic.

A patch, as it contains additional information about an update, should also be able to request "-i" vs. "-U" for a package. This helps kernel installs, where "-i" should be the default without requiring user interaction.

(We still need a way to limit the number of parallel installed kernels)

Would that do more good than harm? Why not leave this to the user?

yum has a "keepkernels" Feature which lets the user determine the number in case it is a kernel, but I find that I don't actually use that feature. I prefer that I do that housekeeping on my own (deinstalling old kernels). I think, anyone who desires to keep old kernels installed is absolutely capable (and willing) to do that. And anyone who isn't is probably not aware of old installed kernels anyway and doesn't make use of them. Also in the light of our bootloader scripts not being able to deal with it properly either. Also, in real life I may want to keep a particular kernel package which may be a little older, but I may want to remove the last two kernels before the current one anyway. In the end the number of kernels installed in parallel is self-limited anyway, because rpm/the installer will complain if / fills up with kernel modules, or /boot fills up with kernels. So it's easy to see for the admin that some old kernels should be removed to free space. Just my two cents, Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development