Re: [Fink-beginners] Out of space problem recovery

[Ian K. <ian...@gm...>]

Oh, I saw a whole bunch of /tmp/fink-build(numbers) flicked through
some of the contents, and assumed.

And I moved /sw/var/lib/apt/lists/_sw_fink_dists_unstable_main_binary-darwin-i386_Packages
to the same with _old on the end.

sudo apt-get update
got me a new copy (and, somewhat unsettlingly, deleted the _old file),
then I ran 'fink self-update', which gave me the same error message
(at the bottom of this mail) but also told me that fink scanpackages
might fix the problem, so I ran that and it gave me the same error
again.

Thanks for the tips on freeing more space.

-Ian



On Fri, Oct 30, 2009 at 11:40 PM, Alexander Hansen
<ale...@gm...> wrote:
> (Fink doesn't do partial build stuff in /tmp)
>
> So what _exactly_ did you try?  You removed
>
> /sw/var/lib/apt/lists/_sw_fink_dists_unstable_main_binary-darwin-i386_Packages
>
> but how did you try to get a new copy?  "fink scanpackages"?
>
>
>
> Once you're fixed back up, you might also want to run "fink cleanup" to
> free up some more space; and you can remove any partial builds from
> /sw/src/fink.build with no deleterious effects.
> Removing non-obsolete .deb files and sources is also possible, but you
> may encounter some annoyances later if you do that.
>

> > Reading Package Lists...
> > E: Encountered a section with no Package: header
> > E: Problem with MergeList /sw/var/lib/apt/lists/_sw_fink_dists_unstable_main_binary-darwin-i386_Packages
> > E: The package lists or status file could not be parsed or opened.
> > ### execution of /sw/bin/apt-get-lockwait failed, exit code 100
> > WARNING: Failure while updating indexes.
> > Running 'fink scanpackages' may fix indexing problems.
> > Scanning package description files..........
> > Information about 9469 packages read in 2 seconds.
> > No packages to install.