| 1 |
On 3/1/21 3:43 AM, Neil Bothwick wrote: |
| 2 |
> On Sun, 28 Feb 2021 22:29:49 -0600, Dale wrote: |
| 3 |
>> I'm not sure what is going on with the servers but when I switched to |
| 4 |
>> one of them, recent updates didn't even exist. I just did a KDE and I |
| 5 |
>> think Firefox and neither seemed to be in the tree from those servers. |
| 6 |
>> Thing is, I didn't note which server it was. If someone notices that |
| 7 |
>> their syncing isn't working right, may want to switch and find one that |
| 8 |
>> is up to date. |
| 9 |
> Alternatively, switch to syncing from github and you'll always be as up |
| 10 |
> to date as possible - and it's much faster. |
| 11 |
> |
| 12 |
> % cat /etc/portage/repos.conf/gentoo.conf |
| 13 |
> [DEFAULT] |
| 14 |
> main-repo = gentoo |
| 15 |
> |
| 16 |
> [gentoo] |
| 17 |
> priority = 20 |
| 18 |
> location = /var/portage |
| 19 |
> sync-type = git |
| 20 |
> sync-uri = https://github.com/gentoo-mirror/gentoo |
| 21 |
> auto-sync = yes |
| 22 |
|
| 23 |
Syncing won't help until the ebuilds are fixed, and the bug does not say |
| 24 |
that has happened. The problem is not (yet) syncing your portage tree, |
| 25 |
it is with the mirrors, some of which have the old tarballs and some of |
| 26 |
which have the new tarballs. If the ebuild gets updated, and you pull |
| 27 |
one of the old tarballs, you will have essentially the same errors |
| 28 |
trying to emerge. You need an ebuild and Manifest that match the |
| 29 |
tarball you are trying to use. |
Archives