Bug 247385

Summary:	Support for 3rd party repos in opensuseupdater
Product:	[openSUSE] openSUSE 10.2	Reporter:	Grozdan Nikolov <mutex1>
Component:	Update Problems	Assignee:	E-mail List <bnc-team-screening>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Enhancement
Priority:	P5 - None	CC:	forgotten_Xh41Ao4q6j, francis, marcio.ferreira
Version:	Final
Target Milestone:	---
Hardware:	x86
OS:	Other
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Grozdan Nikolov 2007-02-21 15:39:49 UTC

Hi,

I would like to submit a feature request for the opensuseupdater. I think that the updater *should* support all repo channels and not just the patch/security repo channels. A lot of people (me including) both on the SUSE IRC chat rooms and SUSE forums like updating their favorite applications when a newer version arrives. I think the opensuseupdater *must* allow the user to choose whether he likes to get only patches/security updates or also newer application versions from 3rd party repositories like Packman and/or Guru.

I am very annoyed because the updater doesn't support this feature so at the moment I am forced to use zen-updater/zmd or SMART. Many people have moved over to use 3rd party package managers like SMART because of this mess with the native SUSE update/package manager.

Thanks

Comment 1 Andreas Jaeger 2007-02-21 17:27:02 UTC

I'm adding the following to our feature tracking database as new feature #302008:

From https://bugzilla.novell.com/show_bug.cgi?id=247385 "I think that the updater *should* support all repo channels and not just the patch/security repo channels. A lot of people (me including) both on the SUSE IRC chat rooms and SUSE forums like updating their favorite applications when a newer version arrives. I think the opensuseupdater *must* allow the user to choose whether he likes to get only patches/security updates or also newer application versions from 3rd party repositories like Packman and/or Guru." 
 I received a comment that we should not do this automatically - and should even differentiate between repositories so that the users see updates from the official openSUSE update channel in a different form than from other repositories. I suggest to make switches "Show only patches" and "Show patches and packages". We might also consider to make this a switch for each repository so that the user has a more fine granular role. Please discuss what is usefull.

Comment 2 marcio ferreira 2007-02-21 17:34:01 UTC

I would prefer if it wasnt the default. The updater is a tool to deliver apthces, not to let the user go in crazy upgraditis. It should not be default, and the user should explicitely enable that if thats exactly what he wants, as he understands that this will greatly affect the genera stability of the installation.

Packman has lots of packages one may or may not want to upgrade (and lots of alpha buildings, cvs, nightly version etc). A guy goes in ther to get codecs,a nd end with whole multimedia stack upgraded beucase of the applet

Comment 3 Forgotten User Xh41Ao4q6j 2007-04-14 20:33:57 UTC

  Is there any need to change opensuseupdater? 

Who wants to have all possible updates can use zen-updater, it is doing just what is asked in description. 

BTW, that feature is one of the reasons that I removed zen-updater from my computer. The updates from third party repositories comming often and it is time consuming to review all of them, add to that zen-updater inability to remember what updates were refused, it equals annoyance. 

  This kind of feature can have unwanted side effects.

First joy to have so fast updates, new users will tell "Linux rocks". Overhelmed with new stuff they can easily ignore fact that distribution has released versions for one reason, to ensure that all packages play nicely togheather. When third party packages introduce incompatibilities, and produce strange results, they have no idea what happened and blame openSUSE.

Comment 4 Francis Giannaros 2007-05-29 12:24:47 UTC

This is actually a duplicate of bug 216097, not really resolved fixed (yet?).

Comment 5 Rafał Miłecki 2007-05-29 12:46:19 UTC

Yes, it seems to be duplicate of bug 216097

Comment 6 Rafał Miłecki 2007-05-29 12:46:52 UTC

Marking as duplicate

*** This bug has been marked as a duplicate of bug 216097 ***