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

[Michael Homer]

On 8/20/07, rubisher <rubisher at scarlet.be> wrote:
> Jonas Karlsson wrote:
> > On Sun, 15 Jul 2007 09:33:19 +0200, Daniele Maccari <gobo.users at gmail.com> wrote:
> >
> >> rubisher ha scritto:
> >>> 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.
> >>> And not enough, each time I accepted this upgrade, it downloaded again and again because at the end each install it removed
> >>>   the package better then waiting the end of Freshen process?
> >>>
> >>> Did I missed important option which would make operation smoother?
> >>>
> >>>
> >> I had the same question in my mind some time ago. The fact that the same
> >> happens with Compile too (afaik) let me believe this could be a Compile
> >> related issue rather than a Freshen related one, also considering that,
> >> again afaik, Freshen uses Compile and other Scripts do get his work done.
> >>
> > As rubisher stated that the file was removed after each install that points
> > to that it was a binary package that was beeing installed. For that
> > InstallPackage is used, however both Compile and InstallPackage should call
> > CheckDependencies, Compile before and InstallPackage before installation,
> > to check if dependencies is fullfilled unless they are called with
> > '--no-dependencies'. That would mean that neither Compile nor
> > InstallPackage would try to install an application if it already was
> > installed _successfully_. Some more output from Freshen/Compile/
> > InstallPackage would help track down this issue.
> >
> Ah here there are some more output during Freshen of GnuPG:
> Freshen: Producing updates list...
> Freshen: Examining only GnuPG
> [IUB] GnuPG 2.0.6                                                                                             2.0.3-r2
> Freshen: Upgrading 1/1...
> [IUB] GnuPG 2.0.6                                                                                             2.0.3-r2
> Freshen: Upgrading GnuPG...
> Freshen: First preference binary, got binary.
> Freshen: Using package, will call InstallPackage
> InstallPackage: Locating a binary package for GnuPG 2.0.6 ...
> InstallPackage: Found package for GnuPG 2.0.6: /Depot/Packages/GnuPG--2.0.6--i686.tar.bz2
> InstallPackage: Installing GnuPG, version 2.0.6.
> InstallPackage: Uncompressing to /Programs...
> InstallPackage: Package Signature Verified
> UpdateSettings: No settings exist
> SymlinkProgram: Symlinking GnuPG 2.0.6.
> SymlinkProgram: Symlinking global settings...
> SymlinkProgram: Symlinking tasks...
> SymlinkProgram: Storing variable files...
> SymlinkProgram: Symlinking libraries...
> SymlinkProgram: Symlinking headers...
> SymlinkProgram: Symlinking info...
> SymlinkProgram: Updating info dir...
> SymlinkProgram: Symlinking manuals...
> SymlinkProgram: Symlinking executables...
> SymlinkProgram: Processed 12 files.
> SymlinkProgram: Processed 2 files.
> SymlinkProgram: Symlinking wrappers...
> SymlinkProgram: Symlinking shared...
> SymlinkProgram: Conflict: /Programs/Tar/1.16.1/Shared/info/dir
> SymlinkProgram: Processed 111 files.
> SymlinkProgram: Removing unused directories...
> SymlinkProgram: Done.
> InstallPackage: Checking dependencies...
>
> CheckDependencies: Curl is not installed.
> CheckDependencies: Install official_package for Curl 7.16.1 or skip this dependency? [I]Install/[S]Skip/[IA]Install A
> ll/[SA]Skip All
That means is that it was unable to find a dependencies list for GnuPG
anywhere. There's no recipe for 2.0.6, but there is a dependencies
file for it in the package repository. Did it fetch that first (during
an earlier run)? Or make an attempt, at least? If it failed fetching
it once, it won't try again.

Run `rm -f /tmp/dependencies-*` and 'rm -f /tmp/Freshen/*` to clear
out the cached data, then run Freshen -c. And make sure that you're
running the most recent release (2.2.6, at time of writing), because
there have been a few bugfixes in how it resolves things lately.
-Michael