Does any one out there, running ubuntu servers, tries to do it with the "-updates" release (like precise-updates) disabled? If so, how do you deal with ubuntu point releases (that include packages from -updates)?
This is way specific, and I didn't find anything about it in my searches. Please point me out to any previous question or maybe to a more appropriate forum you know for this.
Not so short:
It seems to me that the whole point in having -updates as a separate release is opting to not using it, and having just the security-related updates installed. That's what we try to do in our company.
Of course, you might need some package from -updates, and we do. So we leave the -updates on sources.list, but pin it to -10 ("don't use at all" priority). Specific packages we need from -updates are then pinned with a higher priority so they get selected. We have that setup automated already. It works well ... most of the time.
Problem arises if someone uses an image/CD of an ubuntu's point release (say 12.04.2, for example) to install a new machine. Point releases do include the -updates packages up to that time. When I try to install some new package (after disabling/pinning -updates) and that package depends on one of those -updates packages that came with the point release, I might get a broken package. Like in this case:
# apt-get install vim-nox -s Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-nox : Depends: vim-common (= 2:7.3.429-2ubuntu2) but 2:7.3.429-2ubuntu2.1 is to be installed Depends: vim-runtime (= 2:7.3.429-2ubuntu2) but 2:7.3.429-2ubuntu2.1 is to be installed E: Unable to correct problems, you have held broken packages.
It's trying to install vim-nox from "precise", but vim-common and vim-runtime from precise-updates are already installed (by the base install, before I can change anything), and so it breaks.
Fiddling with the apt_preference priorities didn't help me. AFAICT dependencies don't affect apt's priority/selection algorithm, so it won't do the job.
Of course I can just ban the use of point release images, but that's kind of unfortunate. In a world of increasingly prebuilt images for every kind of virtualization platform, if I want to take advantage of them (even if only for testing), I have to search for old, sometimes deprecated (or non-existant) images made before the first point release.
Does anybody here has been through this?