Re: [gentoo-user] Problems with 'emerge sync'

2003-11-13 Thread Jernej Zidar
I reeived this error when I did a Stage3 install and I had a bunch of
packages in /usr/portage/poackages/

I "solved" this problem bz emptying the packages directory.

Jernej Zidar

- Original Message - 
From: "David Gethings" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 13, 2003 12:07 PM
Subject: [gentoo-user] Problems with 'emerge sync'


> Every time I do an 'emerge sync' I get the following error message:
>
>  ** Skipping packages. Run 'fixpackages' or set it in FEATURES to fix
> the
> tbz2's in the packages directory. Note: This can take a very long
> time.
>
> So I run 'fixpackages' and sure enough it fixes stuff. And sure enough
> it takes a *long* time!
>
> This has happened a few times now. On every occasion the I get the
> following error messages:
>
> !!! Cannot update binary: Destination exists.
> !!! sys-apps/raidtools-1.00.3-r1 -> sys-fs/raidtools-1.00.3-r1
> ..!!! Cannot update binary: Destination exists.
> !!! app-admin/dosfstools-2.8-r3 -> sys-fs/dosfstools-2.8-r3
>
> I plan to unmerge then emerge both these ebuilds in an attempt to stop
> this problem in the future. Is this the right course of action, or is
> there a better way to solve this problem.
>
> Cheers
>
> Dg
>
>
> --
> [EMAIL PROTECTED] mailing list
>
>


--
[EMAIL PROTECTED] mailing list



[gentoo-user] Problems with 'emerge sync'

2003-11-13 Thread David Gethings
Every time I do an 'emerge sync' I get the following error message:

 ** Skipping packages. Run 'fixpackages' or set it in FEATURES to fix
the
tbz2's in the packages directory. Note: This can take a very long
time.

So I run 'fixpackages' and sure enough it fixes stuff. And sure enough
it takes a *long* time!

This has happened a few times now. On every occasion the I get the
following error messages:

!!! Cannot update binary: Destination exists.
!!! sys-apps/raidtools-1.00.3-r1 -> sys-fs/raidtools-1.00.3-r1
..!!! Cannot update binary: Destination exists.
!!! app-admin/dosfstools-2.8-r3 -> sys-fs/dosfstools-2.8-r3

I plan to unmerge then emerge both these ebuilds in an attempt to stop
this problem in the future. Is this the right course of action, or is
there a better way to solve this problem.

Cheers

Dg


--
[EMAIL PROTECTED] mailing list