[gentoo-user] Re: How long does "Verifying /usr/portage" take?
On 2018-07-06, Grant Edwards wrote: > On 2018-07-06, Grant Edwards wrote: > >> Now that the public key stuff is working again (knock on wood), I'm >> curious if it's usual for an emerge --sync to take 10-15 minutes >> longer than it used due to the "Verifying /usr/portage" step. >> >> On some systems (with fewer packages installed) it only takes a minute >> or less. But, on my "main" desktop system it takes 10-15 minutes every >> time. > > I cleared out /usr/portage/distfiles, and the verify time dropped to > about 10 seconds. I should probably do that more often... FWIW, I think that change was due to a warm buffer cache. The next few times I did a sync the verify was back to the usual 10+ minutes (with /usr/portage/distfiles still empty). -- Grant Edwards grant.b.edwardsYow! With YOU, I can be at MYSELF ... We don't NEED gmail.comDan Rather ...
Re: [gentoo-user] Re: How long does "Verifying /usr/portage" take?
Rich Freeman wrote: > On Fri, Jul 6, 2018 at 4:43 PM Grant Edwards > wrote: >> On 2018-07-06, Grant Edwards wrote: >> >>> Now that the public key stuff is working again (knock on wood), I'm >>> curious if it's usual for an emerge --sync to take 10-15 minutes >>> longer than it used due to the "Verifying /usr/portage" step. >>> >>> On some systems (with fewer packages installed) it only takes a minute >>> or less. But, on my "main" desktop system it takes 10-15 minutes every >>> time. >> I cleared out /usr/portage/distfiles, and the verify time dropped to >> about 10 seconds. I should probably do that more often... >> > Assuming it is reproducible it is probably a bug. > > That said, I always move distfiles to someplace like /var/cache. I > guess /usr/portage should probably be in there as well, though I would > not mix my distfiles with my repository for a number of reasons. I > think it is just inertia preserving the current situation as I can't > imagine anybody involved in portage/council/etc really would design it > this way today. > > You can tweak this in make.conf with DISTDIR=... > I set mine up this way and it seems to work OK. It's sort of along the lines of yours. root@fireball / # ls /var/cache/portage/ -al total 160 drwxr-xr-x 5 root root 4096 Dec 20 2012 . drwxr-xr-x 13 root root 4096 Jul 4 03:26 .. drwxrwxr-x 3 portage portage 143360 Jul 2 20:42 distfiles drwxr-xr-x 103 portage portage 4096 Jul 3 00:01 packages drwxr-xr-x 171 portage portage 4096 Jul 2 18:22 tree root@fireball / # If anyone wants to duplicate this, this is the relevant parts of make.conf: DISTDIR="/var/cache/portage/distfiles/" PKGDIR="/var/cache/portage/packages" PORTDIR="/var/cache/portage/tree" After I did the move, I think someone came up with a better place but to be blunt, I just didn't feel like moving it all again. It's not like portage really cares where it is anyway. Dale :-) :-)
Re: [gentoo-user] Re: How long does "Verifying /usr/portage" take?
On Fri, Jul 6, 2018 at 4:43 PM Grant Edwards wrote: > > On 2018-07-06, Grant Edwards wrote: > > > Now that the public key stuff is working again (knock on wood), I'm > > curious if it's usual for an emerge --sync to take 10-15 minutes > > longer than it used due to the "Verifying /usr/portage" step. > > > > On some systems (with fewer packages installed) it only takes a minute > > or less. But, on my "main" desktop system it takes 10-15 minutes every > > time. > > I cleared out /usr/portage/distfiles, and the verify time dropped to > about 10 seconds. I should probably do that more often... > Assuming it is reproducible it is probably a bug. That said, I always move distfiles to someplace like /var/cache. I guess /usr/portage should probably be in there as well, though I would not mix my distfiles with my repository for a number of reasons. I think it is just inertia preserving the current situation as I can't imagine anybody involved in portage/council/etc really would design it this way today. You can tweak this in make.conf with DISTDIR=... -- Rich
Re: [gentoo-user] Re: How long does "Verifying /usr/portage" take?
On Friday, 6 July 2018 21:43:35 BST Grant Edwards wrote: > On 2018-07-06, Grant Edwards wrote: > > Now that the public key stuff is working again (knock on wood), I'm > > curious if it's usual for an emerge --sync to take 10-15 minutes > > longer than it used due to the "Verifying /usr/portage" step. > > > > On some systems (with fewer packages installed) it only takes a minute > > or less. But, on my "main" desktop system it takes 10-15 minutes every > > time. > > I cleared out /usr/portage/distfiles, and the verify time dropped to > about 10 seconds. I should probably do that more often... This is odd. Why would a verification of portage include the distfiles, when the latter are checked before they are unpacked as a package is being emerged. It doesn't make sense to me. :-/ -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] Re: How long does "Verifying /usr/portage" take?
On 2018-07-06, Grant Edwards wrote: > Now that the public key stuff is working again (knock on wood), I'm > curious if it's usual for an emerge --sync to take 10-15 minutes > longer than it used due to the "Verifying /usr/portage" step. > > On some systems (with fewer packages installed) it only takes a minute > or less. But, on my "main" desktop system it takes 10-15 minutes every > time. I cleared out /usr/portage/distfiles, and the verify time dropped to about 10 seconds. I should probably do that more often... -- Grant Edwards grant.b.edwardsYow! Hello, GORRY-O!! at I'm a GENIUS from HARVARD!! gmail.com
[gentoo-user] Re: How long does "Verifying /usr/portage" take?
On 2018-07-06, Dale wrote: > I haven't timed mine yet but that sounds about like mine here. I'm not > sure what the bottleneck is but I have a four core AMD CPU running at > 3.2GHz with 16GBs of ram and SATA spinning rust drives. While I'm glad > to have the added security measures, it does add a significant amount of > time to the update process, the tree not the compile part. We all know > the compile part can get big. lol Yea, it sounds a bit stupid to whine about an extra 15 minutes doing a "sync" now that the build time for chromium is measured in days on a not-that-old machine. :) -- Grant Edwards grant.b.edwardsYow! One FISHWICH coming at up!! gmail.com
