Repositories - 11.2 non-oss sync problem

Having trouble syncing up “

Error: Failed to download /content from…

Was the repository structure modified today? Should I update the 11.2 repos to point to some new url?

Also, contemplating just switching to the factory repos. Do the 11.2 repos just contain factory builds that have been marked/deemed “stable”?

And coming from gentoo - I am used to the rolling release system. Is there a factory-unstable and factory-stable set of repos?


Yes the 11.2 repos are snapshot repos until they are frozen for the final release. The main OSS repo may have been down because Milestone 6 is due on August 20th (tomorrow). The latest snapshot was likely being uploaded.

If you’re looking for a rolling release then Factory is what you want. The catch of course is that Factory is highly variable in its stability (since it’s the perpetually-in-development-version).

There is a middle-road option, use a stable release and then add the Factory repo for the software you care about. This is a popular solution for things like Firefox, KDE, GNOME, Virtualbox, etc… This way you can get the latest software for what you want while keeping the other pieces stable.
An example:

The repo is for openSUSE 11.1 but it has the Factory KDE4 packages. This sort of repo is available for most of the software in the distro.
Welcome to openSUSE & the openSUSE community by the way!

Thanks for your input ReferenceSeete. Do you know if packages can be locked to a certain repo?

For example, I want the core system to be installed from the stable repo, and the kernel (+dependencies) to be installed from the factory repo. And when I complete a system update, the sources do not change.


There are a couple solutions.

A. Repository Priority
B. Package Locks

A. Repository Priority

  1. Open the Software Repositories module in YaST
  2. You’ll see a box named ‘Priority’ likely with the number 99 in it.
  3. If you change this number then the selected repo’s priority will increase or decrease. Priority works by rank-order (1 is the highest, 2 is second-highest etc.).

You can also do this via zypper (the command-line tool for package management)

zypper modifyrepo -p [a number] [repo alias OR number OR URL]


zypper mr -p [a number] [repo name OR number OR URL]

So long as the repositories are organised the way you need - i.e. you want a newer WINE build so the repo offers just WINE & its dependancies - you’ll be fine with the repo priority method. If you mismatch your needs and the repo, this method won’t help you - i.e. if you just want new WINE builds don’t add the Factory OSS master repo because it contains all manner of packages you don’t want to upgrade.

Also be mindful that repo priority trumps package version numbers. If a newer version of a package is available in a lower priority repo it will not be chosen for upgrade automatically.

B. Package Locks

An alternative is to lock the packages you don’t want changed. In YaST if you find the package you want you can lock it by right-clicking and selecting “Protected - Do Not Modify” or “Taboo - Do Not Install”. The same options are also in the ‘Package’ Menu if you’re more of a left-click person.

You can also do the same from the command line using zypper:

zypper addlock [options] [package name]


zypper al [options] [package name]

Zypper will confirm if the lock was successful.

Zypper is actually more powerful than YaST since it allows you to set locks on a per-repository basis. Given your situation, zypper is probably the better route as it allows a more fine grained application of locks. For demonstration purposes, here is my current repo list. [You can see yours using ‘zypper lr’]

#  | Alias                                       | Name                 | Enabled | Refresh
1  | External:VideoLan                           | External:VideoLan    | Yes     | Yes
2  | Factory:Contrib                             | Factory:Contrib      | Yes     | Yes
3  | Factory:Debug                               | Factory:Debug        | Yes     | Yes
4  | Factory:Non-OSS                             | Factory:Non-OSS      | Yes     | Yes
5  | Factory:OSS                                 | Factory:OSS          | Yes     | Yes
6  | home:prusnak:factory                        | home:prusnak:factory | Yes     | Yes
7  | openSUSE 11.2-0                             | oS11.2:DVD           | Yes     | No
8  | openSUSE_BuildService_-_Drivers_for_webcams | Hardware:Webcam      | Yes     | Yes
9  | repo-debug                                  | oS11.2:Debug         | Yes     | Yes
10 | repo-non-oss                                | oS11.2:Non-OSS       | Yes     | Yes
11 | repo-oss                                    | oS11.2:OSS           | Yes     | Yes
12 | repo-source                                 | oS11.2:Source        | No      | Yes
13 | repo-update                                 | oS11.2:Update        | Yes     | Yes

Repos #5, 7, and 11 all have the package “kernel-desktop”. You could lock the package in repos 5 & 7 to make sure that only updates in repo 11 will be delivered.

zypper al -r 5 kernel-desktop
zypper al -r 7 kernel-desktop


zypper al -r 5 -r 7 kernel-desktop

Note a few things:
First, if you plan to lock a package in multiple repos you must use the “-r” option for each repo. If you typed in “zypper al -r 5 7 kernel-desktop” you’d get a lock on a package named “7”(!) and the “kernel-desktop” part would be ignored.
Second, zypper assumes you know what you’re doing. It won’t spit back an error or warning that no package named “7” is available.
Third, you can use wildcards. So typing “kernel*” instead will lock every package that starts with ‘kernel’.

If you want to check for locks on unknown packages…

zypper cleanlocks


zypper cl

If you want to remove a package lock

zypper removelock [package name]


zypper rl [package name]

…In YaST you can right-click a locked package and select “keep”. This will remove the lock.

There’s more you can do with zypper & package locks, but this post is so long its about to turn into a webinar. If you’re comfortable with man pages then check out the zypper’s documentation for more information. If not, just ask for additional help.

As a final note…I wouldn’t mix the repos for Factory and a stable release.

“Factory” is SUSE-speak for “in constant development, comes with no guarantees…but please file bug reports”. There is the Factory distribution which is the most up-to-date build of openSUSE available, and then there are backports of Factory software compiled against the build chains of older stable openSUSE releases. Neither the Factory distribution nor the backports from it come with any guarantees of stability, however if you are going to use a stable release as your base…then add the backport repos for your release version rather than adding the pure Factory repos.

If you want a more up-to-date kernel for openSUSE 11.1, you should use a repo like this one: Index of /repositories/Kernel:/HEAD/openSUSE_11.1

…Rather than adding the Factory OSS repo and trying to manage all of the conflicts through package locks. Coming from Gentoo you likely have a good grip on my concern, but “an ounce of prevention is worth a pound of cure”.

Ok, you’ve been warned. Enjoy openSUSE!