Bug 148480 - support for multiple installation sources while installation/upgrade
Summary: support for multiple installation sources while installation/upgrade
Status: VERIFIED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Update Problems (show other bugs)
Version: Beta 3
Hardware: Other Other
: P5 - None : Enhancement with 3 votes (vote)
Target Milestone: ---
Assignee: Jiri Srain
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-06 18:54 UTC by Christian Boltz
Modified: 2006-07-17 20:46 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christian Boltz 2006-02-06 18:54:19 UTC 
Currently, you can have only one installation source when installing or upgrading SUSE Linux.

Therefore my current update workflow is:
- choose to _not_ remove packages that are not on the media (because
  acroread, flash, ... would be removed) - this is really annoying :-(
- after installation, add inst-source-extra as source and start YaST2
  system upgrade to upgrade the non-OSS packages

Even more annoying: While installation, I have to ignore some conflicts (like for kernel-*-nongpl).

SUSE Linux already comes with two installation sources (inst-source, inst-source-extra), so it should be possible to use both _while installation_ already.
Comment 1 Michael Gross 2006-02-07 15:13:22 UTC 
Please don't issue more than one topic in a single bugreport.

> - choose to _not_ remove packages that are not on the media (because
>  acroread, flash, ... would be removed) - this is really annoying :-(

What do you mean here? Be more verbose about this point.
As for the other issues, open seperate reports.
Comment 2 Christian Boltz 2006-02-07 21:34:16 UTC 
This is all about one point - you can only use _one_ installation source when installing or updating.

The other things I mentioned are caused by this. In detail:

The mentioned packages are not in the OSS installation source, so YaST thinks these packages are dropped in 10.1 beta.

The default on upgrade is to uninstall "dropped" packages ("dropped" as in "not on install source") - this is the reason why the packages are proposed for deletion.

If I don't want this, I have to change this to keep "dropped" packages (and, in case of kernel-*-nongpl have to ignore conflicts).


What I would like to see is the possibility to add another installation source (inst-source-extra) where the mentioned packages are available. This way, YaST would know that the mentioned packages are _not_ dropped.

In other words: I ask for   yast2 inst_source   while installation/upgrade.

I hope my request has became clear now ;-)
Comment 3 Michael Gross 2006-02-08 13:10:24 UTC 
Yes, now it's clear. It would be a nice feature...
Comment 4 Jiri Srain 2006-07-17 13:46:10 UTC 
Starting Code10, you can have multiple sources when updating, via the add-on product functionality, thus resolving as WONTFIX.

If it is not sufficient for you, please, reopen.
Comment 5 Christian Boltz 2006-07-17 20:46:52 UTC 
I'd say the add-on functionality FIXED this :-)

-> VERIFIED (unless I find a case where the add-on way doesn't work ;-)