Bug 643361

Summary: One of the official repos has been migrated, breaking installation process.
Product: [openSUSE] openSUSE 11.2 Reporter: Carlos Robinson <carlos.e.r>
Component: InstallationAssignee: Stephan Kulow <coolo>
Status: RESOLVED FIXED QA Contact: Jiri Srain <jsrain>
Severity: Major    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: openSUSE 11.2   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Carlos Robinson 2010-10-02 18:17:29 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-0.3.1 Firefox/3.6.10

Components affected :

  New installations,
  Upgrade/update/maintenance/usability

The official repo:

<http://download.opensuse.org/source/distribution/11.2/repo/oss/>

has been migrated, un-announced, to:

<http://download.opensuse.org/source/11.2/repo/oss>

This breaks the installation process, and any update process. It has not being announced. It has created distress on many users.

Notice that this repo is activated by default on all installs, disabled but with automatic refresh enabled.

Samples:

http://forums.opensuse.org/showthread.php?t=447447
11.2 oss repo' PackageKit error

View this thread: http://forums.opensuse.org/showthread.php?t=447433
Repository error - oss source

<http://forums.opensuse.org/english/get-help-here/looking-something-other-than-support/447397-source-repo-down.html>
Thread: source repo down?

<http://forums.opensuse.org/english/get-help-here/looking-something-other-than-support/447410-what-happened-oss-non-oss-source-repos-11-2-a.html>
Thread: What Happened to the OSS and Non-OSS Source Repos for 11.2?


The official repository addresses should be frozen for each distro till its end of life. At the very least, changes should be announced in advance.

Or, you should add a feature to yast/zypper that gets messages "from above" and tells the user about changes.





Reproducible: Always

Steps to Reproduce:
Fire up YOU or package management, or zypper ref, up, install; or simply wait for packagekit turn.
Comment 1 Carlos Robinson 2010-10-02 20:41:14 UTC
Somebody has silently repaired this bug - as explained in the project mail list.
Comment 2 Stephan Kulow 2010-10-04 09:37:31 UTC
I repaired it early on friday, but the sync that actually fixed the public area only ran later.