|
Bugzilla – Full Text Bug Listing |
| Summary: | zypper ar obs://something should default to current distro | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Christian Boltz <suse-beta> |
| Component: | libzypp | Assignee: | Jan Kupec <jkupec> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P4 - Low | CC: | dimstar |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | openSUSE 11.3 | ||
| Whiteboard: | patches-welcome | ||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Christian Boltz
2010-10-24 21:56:14 UTC
You can specify it, or configure the default to use on your system. [man zypper]: ... These URIs have the form of obs://<project>/[platform], where project is the name of the OBS project and platform is the target platform (OS) for which the repository is intended. For example: obs://server:http/openSUSE_11.3. If platform is omitted, zypper.conf's obs.platform value is used. See also other options in the [obs] section of zypper.conf. Good to know there's a config option for it, but this doesn't solve the problem.
Zypper should use a _sane default value_, which is the _currently installed distribution_ (as found in /etc/SuSE-release). Defaulting to Factory (or is it $random?) is just crazy and a good way to break users' systems out there.
Please change the default to the current distribution.
BTW: My zypper.conf has the default of
[obs]
...
# platform = openSUSE_11.3
The easiest solution would be to ship zypper.conf without this comment sign in front of "platform". That would possibly break on upgrades (reading /etc/SuSE-release is safer), but it's still better than Factory as default value.
I agree Christian, but i won't have time to do it -> WONTFIX Patches are welcome, though. See also http://en.opensuse.org/openSUSE:Zypper_bugs_for_adoption *** Bug 687440 has been marked as a duplicate of this bug. *** |