[Bug 779361] New: installer does not recognize Tumbleweed and current repos
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c0 Summary: installer does not recognize Tumbleweed and current repos Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: 64bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bluedzins@wp.pl QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 By definition Tumbleweed and current repos are always valid for given version of openSUSE. This was the goal of those repos, that instead of adding repo targeting (for example) 12.1 I use "current" and when I upgrade to newest version, this will be still the appropriate repo. The installer however does not only recognize it, but also instead of simply disabling it, tries to remove it (never, ever try to remove user's data, unless user explicitly says so). So it is a double bug here. Reproducible: Always Steps to Reproduce: 1. Install 12.1 2. add current or TW repo 3. upgrade to 12.2 4. observe the installer tries to remove those repos Expected Results: TW and current repos should stay intact, all others repos should be DISABLED. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c Maciej Pilichowski <bluedzins@wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Installation |Update Problems -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c1 kk zhang <kkzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkzhang@suse.com AssignedTo|bnc-team-screening@forge.pr |coolo@suse.com |ovo.novell.com | --- Comment #1 from kk zhang <kkzhang@suse.com> 2012-09-10 12:08:14 UTC --- Hi,coolo.could you please help to have a look at this? I am sure who is the maintainer of update. Thanks -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c2 Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Component|Update Problems |YaST2 InfoProvider| |bluedzins@wp.pl AssignedTo|coolo@suse.com |bnc-team-screening@forge.pr | |ovo.novell.com --- Comment #2 from Stephan Kulow <coolo@suse.com> 2013-02-06 11:32:05 CET --- please attach your logs. indeed it shouldn't delete repos. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c3 Maciej Pilichowski <bluedzins@wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|bluedzins@wp.pl | --- Comment #3 from Maciej Pilichowski <bluedzins@wp.pl> 2013-02-06 14:31:12 UTC --- https://bugzilla.novell.com/attachment.cgi?id=507361 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c Du Weihua <whdu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |zypp-maintainers@forge.prov |ovo.novell.com |o.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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c4 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|zypp-maintainers@forge.prov |bnc-team-screening@forge.pr |o.novell.com |ovo.novell.com --- Comment #4 from Michael Andres <ma@suse.com> 2013-02-28 17:49:54 CET --- Reassigning to YaST: There's no code in libzypp which would delete/disable repositories without request. If the repos were deleted this must be part of the yast workflow. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c Du Weihua <whdu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |whdu@suse.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c Thomas Göttlicher <tgoettlicher@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |jsuchome@suse.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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c5 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bluedzins@wp.pl --- Comment #5 from Jiří Suchomel <jsuchome@suse.com> 2013-03-01 12:24:53 UTC --- When did it actually try to remove the repository? Was it done automatically, or were you asked for the review? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c6 --- Comment #6 from Maciej Pilichowski <bluedzins@wp.pl> 2013-03-01 12:41:38 UTC --- During upgrade. My point is TW repo is should not be bound to any version, because it is TW -- it should be treated as all-versions-repos, thus never disabled, never deleted. What review? I am currently testing OS 12.3 RC1, but it is too buggy to test it, so I am keeping NEEDINFO, once we have RC2 I will check this issue as well (OS12.2->12.3). -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c7 --- Comment #7 from Jiří Suchomel <jsuchome@suse.com> 2013-03-01 13:21:47 UTC --- (In reply to comment #6)
During upgrade. My point is TW repo is should not be bound to any version, because it is TW -- it should be treated as all-versions-repos, thus never disabled, never deleted.
What review?
You wrote that YaST removed your repo. I'm asking: Was it done automatically, or were you asked for the review? Like, if you were presented with list of repos that will be deleted. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c8 --- Comment #8 from Maciej Pilichowski <bluedzins@wp.pl> 2013-03-01 13:47:25 UTC --- Jiri, report date "2012-09-07" (half a year ago). When I have RC2 in my hands, I will test it and answer your question. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c9 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|bluedzins@wp.pl |coolo@suse.com --- Comment #9 from Jiří Suchomel <jsuchome@suse.com> 2013-03-01 14:18:45 UTC --- OK, I've just tested upgrade from 12.1 to 12.2 and it is just like I expected: YaST does not delete anything without user knowledge. At start of the upgrade, you are presented with the list of old repositories and you can do whatever you can with them. If they are marked as deleted, you can change the status by one click of the Toggle button. (At this point, I'm close to marking the bug as invalid). So, now we are down to the fact, that we could try to leave Tumbleweed repository enabled by default. Problem is, how do we detect it is the one, other way than looking for substring in repository URL. Stefan, what is our official stand regarding Tumbleweed? And is it recognizable from its metadata somehow? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c10 Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|coolo@suse.com | --- Comment #10 from Stephan Kulow <coolo@suse.com> 2013-03-03 08:42:12 CET --- tumbleweed is just another repo. You can hardcode the key or similiar things, but there is no "this repo will be rebased in the future" flag. The real trick is to switch to services and let the build service answer the question "give me tumbleweed repo for 12.3", but we're not there. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c11 --- Comment #11 from Stephan Kulow <coolo@suse.com> 2013-03-03 08:49:46 CET --- on second thought: if you're using a rolling release like tumbleweed - why would you do an offline update to a non rolling release like 12.3? that sounds like a 100% corner case not worth supporting. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c12 --- Comment #12 from Maciej Pilichowski <bluedzins@wp.pl> 2013-03-03 09:32:00 UTC --- With polished OS, why not? But currently absolutely not: * who will give me a guarantee my connection won't be broken and upgrader will smoothly resume after reconnecting? * what about pulling the data several times, because I am doing this upgrade for several computers * what about the fact TW repo is cleaned when new OS is release -- thus it is impossible to really do rolling release upgrade, because there is no data at all * and add several minor inconsistencies with OS upgrader and TW To sum this up, TW is not mature enough to rely on it, considering especially deleting rolling release data -- it is something completely against RR concept. "non rolling release like 12.3?" According to "commercials" any OS version + TW is rolling release. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=779361 https://bugzilla.novell.com/show_bug.cgi?id=779361#c13 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #13 from Jiří Suchomel <jsuchome@suse.com> 2013-03-06 08:20:19 UTC ---
From the discussion above, it seems best to me to not do anything Tumbleweed during installation.
Of course, user is still able to manage repositories during the upgrade himself (comment 9) -- 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.
participants (1)
-
bugzilla_noreply＠novell.com