[Bug 264447] New: update channel
https://bugzilla.novell.com/show_bug.cgi?id=264447 Summary: update channel Product: openSUSE 10.3 Version: Alpha 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jt@newmarket.k12.nh.us QAContact: jsrain@novell.com i'm on Opensuse 10.2 but opensuse as a whole should have the domain, update.opensuse.org which points to the update mirror services around the world, I have recently had the update channel that got registered during installation become inaccessible which stalled the process of opening yast software management until I answered a question. This is not acceptable. Because the question was whether to delete the channel or not, I deleted it and had to go search for another which isn't exactly an end user friendly process. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=264447 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |aj@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=264447 aj@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aj@novell.com |cthiel@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=264447 cthiel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Status|NEW |NEEDINFO Info Provider| |adrian@novell.com ------- Comment #1 from cthiel@novell.com 2007-04-17 17:40 MST ------- With the upcoming 10.3, we will improve dramatically on this. CCing Adrian: How about adding updates.opensuse.org as a CNAME to download.openSUSE.org, like discussed earlier today. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=264447 adrian@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Info Provider|adrian@novell.com |cthiel@novell.com ------- Comment #2 from adrian@novell.com 2007-04-18 04:52 MST ------- I would not create update.o.o before we have defined what kind of path URLs should be supported by it. I am looking for a proposal from you (Christoph) covering released distributions + optional extra maintained repositories. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=264447 cthiel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|cthiel@novell.com | ------- Comment #3 from cthiel@novell.com 2007-04-20 02:45 MST ------- So, here is what I think we could to in this regard: Proposal 1) update.openSUSE.org only for distribution Updates: update.openSUSE.org /10.1/ /10.1/repodata/ /10.1/i386/ /10.1/x86_64/ /10.2/ ... /10.3/ ... or, in case we want to have different update channels for our different trees inside distribution/, we could do: update.openSUSE.org /10.3/non-oss/repodata/ /10.3/non-oss/i386/ /10.3/non-oss/x86_64/ Proposal 2) including proposal 1, but keeping the option to (later) have update channels for build service repositories: /distribution/10.3/repodata/ /distribution/10.3/i386/ ... /repositories/home:/cthiel1/openSUSE_10.2/repodata/ ... However, I'm not sure, if we really want to do this, as there is no way to create a "stable branch" in the build service (yet?). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=264447 ------- Comment #5 from jt@newmarket.k12.nh.us 2007-04-20 08:16 MST ------- Hello, Is there no way to have update.opensuse.org decipher what operating system is attaching and feed it the correct update channels dynamically. what I mean is when we first opened Firefox after NLD9\suse 9.3\SLED installation, we got a connection to a page at novell.com that seemed to know what version we where on. if so, make the system's update engine of choice(you, opensuseupdater,etc) go to update.opensuse.org by default and get an update "cookie" (registered user key)get redirected to a mirror dynamically every time updates are needed (i.e. mirrors.kernel.org/opensuse/updates/10.2 or updates.xxx.com/opensuse/10.2 or linuxguru.org/updates/opensuse/10.2) which ever is available and feed us our OSS\security updates? (and of course the obligatory advertisements if commercial entity). Lets face it End Users are used to having a mindless update service with MS and will complain that anything else is to complicated to deal with. so using Mr Thiel's option 1, but limit it to patches and security enhancements. Leave the non-oss stuff on software.opensuse.org ,make a default desktop link that presents a EULA that covers the Adobe\Nvidia\etc requirements then makes a yast installation source link to software.opensuse.org\xx.x then those non-oss packages get updated in the build service with there security and enhancement patches, instead of patching them in the running distro, pushing the work back on the package supplier. YOU or opensuseupdater could simply announce "there is a newer version of xxxx, would you like to install it" or "for security reasons xxx.x has been updated to xxx.x.x, please install it". I'm sure Adobe can afford a guy who keeps their RPM based packages up to date. James -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=264447 cthiel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|cthiel@novell.com |adrian@novell.com Status|NEEDINFO |NEW Info Provider|adrian@novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=264447#c8
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=264447#c9
Christoph Thiel
participants (1)
-
bugzilla_noreply@novell.com