On Mon, 1 Mar 2021 10:45:32 -0500, Jack wrote: > > Alternatively, switch to syncing from github and you'll always be as > > up to date as possible - and it's much faster.
> Syncing won't help until the ebuilds are fixed, and the bug does not > say that has happened. The problem is not (yet) syncing your portage > tree, it is with the mirrors, some of which have the old tarballs and > some of which have the new tarballs. So it's the source mirrors that are out of date rather than the rsync mirrors? > If the ebuild gets updated, and > you pull one of the old tarballs, you will have essentially the same > errors trying to emerge. You need an ebuild and Manifest that match > the tarball you are trying to use. This sort of issue should only last an hour or so, after which time everything should be in sync. if it is still there the next day, something is wrong with the mirror you are using. -- Neil Bothwick Top Oxymorons Number 11: Terribly pleased
pgpEQT2JVK9fM.pgp
Description: OpenPGP digital signature
