I'll sync soon and see. Thanks.
--
G.Wolfe Woodbury
redwo...@gmail.com
On 08/23/2015 12:48 PM, Gregory Woodbury wrote:
> I am still getting the Manifest files completely reloaded when I sync
> portage. (emerge --sync)
>
If it's truly fixed, you'll still have to sync all the Manifests at
least once before you'll have the new Manifests with stable mtimes [1].
[1] htt
Dnia 2015-08-23, o godz. 15:48:48
Gregory Woodbury napisał(a):
> I am still getting the Manifest files completely reloaded when I sync
> portage. (emerge --sync)
What was the last time you synced? I applied a fix around 8:30 UTC.
Afterwards all Manifests were regenerated, so you should have one
I am still getting the Manifest files completely reloaded when I sync
portage. (emerge --sync)
--
G.Wolfe Woodbury
redwo...@gmail.com
Dnia 2015-08-22, o godz. 22:17:05
Philip Webb napisał(a):
> 150815 Holger Hoffstätte wrote:
> > On Sat, 15 Aug 2015 15:29:21 -0400, Joshua Kinard wrote:
> >> I've been super-busy as of late and just recently ran 'emerge --sync'
> >> on my main dev box for the first time after the git migration.
>
150815 Holger Hoffstätte wrote:
> On Sat, 15 Aug 2015 15:29:21 -0400, Joshua Kinard wrote:
>> I've been super-busy as of late and just recently ran 'emerge --sync'
>> on my main dev box for the first time after the git migration.
>> I just synced my main dev box again, ~10 hours after the last sync
On Sat, 15 Aug 2015 15:29:21 -0400, Joshua Kinard wrote:
> This might already be covered in one of the other e-mail threads, but I've
> been
> super-busy as of late and just recently ran 'emerge --sync' on my main dev box
> for the first time after the git migration. I just synced my main dev bo
