On 3/1/21 3:43 AM, Neil Bothwick wrote:
On Sun, 28 Feb 2021 22:29:49 -0600, Dale wrote:
I'm not sure what is going on with the servers but when I switched to
one of them, recent updates didn't even exist. I just did a KDE and I
think Firefox and neither seemed to be in the tree from those servers.
Thing is, I didn't note which server it was. If someone notices that
their syncing isn't working right, may want to switch and find one that
is up to date.
Alternatively, switch to syncing from github and you'll always be as up
to date as possible - and it's much faster.
% cat /etc/portage/repos.conf/gentoo.conf
[DEFAULT]
main-repo = gentoo
[gentoo]
priority = 20
location = /var/portage
sync-type = git
sync-uri = https://github.com/gentoo-mirror/gentoo
auto-sync = yes
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. 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.
