[gobolinux-users] Freshen couldn't better prepare update?

[Michael Homer]

On 7/15/07, rubisher <rubisher at scarlet.be> wrote:
> Michael Homer wrote:
> > On 7/15/07, rubisher <rubisher at scarlet.be> wrote:
> >> Hello Michael,
> >>
> >> 2 or 3 weeks ago I launch the upgrade of kde with:
> >>
> >> # Freshen -U KDE-Utils KDE-Libs KDE-PIM KDE-Graphics KDE-Multimedia
> >>
> >> (Freshen release 2.2.2-r1)
> >>
> >> Among dependencies there was new Xorg which is also a dependency of other kde's dependencies, I so stopped to count the
> >> number of time Freshen asked me if I want to upgrade Xorg even thought I already accepted at the first time.
> > Freshen never asks you at all. Compile might, but it shouldn't if that
> > version of X has already been installed. Which should have happened at
> > the beginning of the Freshen run if it wasn't already met. If X failed
> > to install at that point, that's the problem, and you should stop and
> > see why.
> mmm, may be did I tell to skip it the first time Freshen put the question (I don't remember)?
It doesn't put the question. Compile might, but only if it isn't
satisfied at that point, which it definitely should be.
> > What does just `Freshen  KDE-Utils KDE-Libs KDE-PIM
> > KDE-Graphics KDE-Multimedia` give you?
> Well as far as kde 3.5.6 seems to be broken to me, I can revert this update and retry the operation.
> I will come back as soon as I can with logs.
You don't need to compile, just give the output of that command.
Freshen --debug might help too.
>
> > `ls -l /Programs/Xorg`?
> No pb:
> # ls -l /Programs/Xorg/
> total 12
> drwxr-xr-x 9 Brother Brother 4096 2007-06-03 11:23 7.1
> drwxrwxr-x 9 Brother Brother 4096 2007-04-07 20:31 7.2
> lrwxrwxrwx 1 Brother Brother    3 2007-06-30 19:10 Current -> 7.2
> drwxr-xr-x 3 Brother Brother 4096 2007-06-03 11:23 Settings
> lrwxrwxrwx 1 Brother Brother   16 2007-06-03 14:51 Variable -> /System/Variable
So Xorg 7.2 is installed and symlinked properly... Freshen definitely
won't try to install it, and Compile/InstallPackage shouldn't be
trying either (plus, they're called with --no-dependencies, they
shouldn't even be looking). That's puzzling. I think we'll need some
more logs of what actually goes on to solve this.
-Michael