[PlanetCCRMA] Apt problems]

Fernando Lopez-Lezcano nando@ccrma.Stanford.EDU
Fri Nov 26 12:35:02 2004


On Thu, 2004-11-25 at 21:23, William M. Quarles wrote:
> William M. Quarles wrote:
> > Fernando Lopez-Lezcano wrote:
> >> Thanks for the report, btw...
> > 
> > No problem for the report.  As for the other errors, I'll need to do 
> > some work to recreate them.  Also, you should know that Up2Date in 
> > graphical mode reports those errors one chooses which packages to 
> > install, but before those packages are installed.  It's getting this 
> > information to determine the conflicts from some header that the Apt 
> > repository provides.
[MUNCH]
> [root@resistance root]# up2date -u
> 
> Fetching package list for channel: PlanetCCRMA_fc1-core...
> 
> Fetching 
> http://ccrma.stanford.edu/planetccrma/apt/fedora/1/i386/base/pkglist.core.bz2...
> ########################################
> 
> Fetching package list for channel: PlanetCCRMA_fc1-updates...
> 
> Fetching 
> http://ccrma.stanford.edu/planetccrma/apt/fedora/1/i386/base/pkglist.updates.bz2...
> ########################################
[MUNCH]

> Testing package set / solving RPM inter-dependencies...
> ########################################
> RPM package conflict error.  The message was:
> Test install failed because of package conflicts:
> file /lib/modules from install of kernel-2.4.26-1.ll.rhfc1.ccrma 
> conflicts with file from package filesystem-2.2.1-5
> file /dev/shm from install of kernel-2.4.26-1.ll.rhfc1.ccrma conflicts 
> with file from package dev-3.3.8-2
> file /dev/shm from install of kernel-2.4.26-1.ll.rhfc1.ccrma conflicts 
> with file from package kernel-2.4.22-1.2115.nptl
> file /lib/modules from install of kernel-2.4.26-1.ll.rhfc1.ccrma 
> conflicts with file from package kernel-2.4.22-1.2115.nptl
> file /dev/shm from install of kernel-2.4.26-1.ll.rhfc1.ccrma conflicts 
> with file from package kernel-2.4.22-1.2199.nptl
> file /lib/modules from install of kernel-2.4.26-1.ll.rhfc1.ccrma 
> conflicts with file from package kernel-2.4.22-1.2199.nptl
> file /dev/shm from install of kernel-2.4.26-1.ll.rhfc1.ccrma conflicts 
> with file from package kernel-2.4.22-1.2188.nptl.caps.rhfc1.ccrma
> file /lib/modules from install of kernel-2.4.26-1.ll.rhfc1.ccrma 
> conflicts with file from package kernel-2.4.22-1.2188.nptl.caps.rhfc1.ccrma

The kernel, dev and filesystem share directories. 

> file /usr/lib/ladspa from install of swh-plugins-0.4.11-1.rhfc1.ccrma 
> conflicts with file from package blop-0.2.8-1.rhfc1.ccrma

Again, apparently up2date does not like that swh-plugins and blop share
a directory (/usr/lib/ladspa)

> file /usr/lib/ladspa from install of swh-plugins-0.4.11-1.rhfc1.ccrma 
> conflicts with file from package caps-0.1.11-1.rhfc1.ccrma
> file /usr/lib/ladspa from install of swh-plugins-0.4.11-1.rhfc1.ccrma 
> conflicts with file from package cmt-1.15-3.rhfc1.ccrma
> file /usr/lib/ladspa from install of swh-plugins-0.4.11-1.rhfc1.ccrma 
> conflicts with file from package fil-plugins-0.0.1-1.rhfc1.ccrma
> file /usr/lib/ladspa from install of swh-plugins-0.4.11-1.rhfc1.ccrma 
> conflicts with file from package mcp-plugins-0.3.0-1.rhfc1.ccrma
> file /usr/lib/ladspa from install of swh-plugins-0.4.11-1.rhfc1.ccrma 
> conflicts with file from package pvoc-0.1.9-1.rhfc1.ccrma
> file /usr/lib/ladspa from install of swh-plugins-0.4.11-1.rhfc1.ccrma 
> conflicts with file from package rev-plugins-0.2.1-2.rhfc1.ccrma
> file /usr/lib/ladspa from install of swh-plugins-0.4.11-1.rhfc1.ccrma 
> conflicts with file from package tap-plugins-0.6.0-1.rhfc1.ccrma
> file /usr/lib/ladspa from install of swh-plugins-0.4.11-1.rhfc1.ccrma 
> conflicts with file from package vco-plugins-0.3.0-2.rhfc1.ccrma

Same with all these, /usr/lib/ladspa is shared by those packages (ie:
each package "owns" the same directory - that is fine and legal). 

I don't think I can solve this, looks to me like a bug in up2date
handling of apt repositories. Have you tried to use yum, which
supposedly has better support in up2date?

Those conflicts should not exist, the proof being that rpm does not
complain at all about them (or apt or yum, AFAIK). The ladspa plugin
spec files and packaging are my doing, but the kernel spec file was
initially a copy of the original redhat spec file used for their kernel,
so what it does is exactly what redhat does (with the exception of the
versions of the kernel and assorted patches, of course). 

Sorry to not have better news, and thanks a lot for taking the time to
make a detailed report of what was happening. Again, looks like the
directory processing in up2date for apt repositories has a bug. 

> On another note, you used to provide direct downloads of the kernel and 
> ALSA packages from the website... Why no longer?

My reasoning for turning that off (I may change that in the future - it
makes less and less sense) was to try to minimize the direct hits of
search engines on the rpms themselves. Otherwise somebody searches for a
given package name, finds it, downloads it in isolation and most
probably can't get it to install or even work, if it by chance installs.
Most packages only work if you install them with the rest of the Planet
CCRMA system... 

-- Fernando