| 1 |
On Mon, 1 Mar 2021 10:45:32 -0500, Jack wrote: |
| 2 |
|
| 3 |
> > Alternatively, switch to syncing from github and you'll always be as |
| 4 |
> > up to date as possible - and it's much faster. |
| 5 |
|
| 6 |
> Syncing won't help until the ebuilds are fixed, and the bug does not |
| 7 |
> say that has happened. The problem is not (yet) syncing your portage |
| 8 |
> tree, it is with the mirrors, some of which have the old tarballs and |
| 9 |
> some of which have the new tarballs. |
| 10 |
|
| 11 |
So it's the source mirrors that are out of date rather than the |
| 12 |
rsync mirrors? |
| 13 |
|
| 14 |
> If the ebuild gets updated, and |
| 15 |
> you pull one of the old tarballs, you will have essentially the same |
| 16 |
> errors trying to emerge. You need an ebuild and Manifest that match |
| 17 |
> the tarball you are trying to use. |
| 18 |
|
| 19 |
This sort of issue should only last an hour or so, after which time |
| 20 |
everything should be in sync. if it is still there the next day, |
| 21 |
something is wrong with the mirror you are using. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
Neil Bothwick |
| 26 |
|
| 27 |
Top Oxymorons Number 11: Terribly pleased |
Archives