From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] PATCH: properly handle metadata transfer on first sync of an empty tree (#96410)
Date: Fri, 5 Aug 2005 20:20:52 +0900 [thread overview]
Message-ID: <200508052020.54209.jstubbs@gentoo.org> (raw)
In-Reply-To: <20050805033118.GM21865@exodus>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
On Friday 05 August 2005 12:31, Brian D. Harring wrote:
> Hola all, patch (incvs now) to fix up a traceback on first sync with
> an empty tree; bug #96410
> http://bugs.gentoo.org/show_bug.cgi?id=96410
>
> The fix isn't exactly what I'd call pretty (creating an intermediate
> portdbapi and config instance to do the updates), but it's a corner
> case; config's categories is a bit of a hack, and tearing it out in
> stable is more work then worth... so this.
>
> Either way, it's attached, poke at it kindly :)
You know the caching fairly well, so I'll ask rather than check. ;)
How does this affect the new version of portage check that follows? Will
that use the old cache, find that it's out of date and then regen it?
--
Jason Stubbs
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-05 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 14:13 [gentoo-portage-dev] PATCH: Use lchown and lchgrp no-op functions when operating on symlinks (#99616) Jason Stubbs
2005-07-21 17:17 ` Brian D. Harring
2005-07-21 23:49 ` Jason Stubbs
2005-08-05 3:31 ` [gentoo-portage-dev] PATCH: properly handle metadata transfer on first sync of an empty tree (#96410) Brian D. Harring
2005-08-05 11:20 ` Jason Stubbs [this message]
2005-08-09 7:19 ` Brian Harring
2005-08-06 23:30 ` Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200508052020.54209.jstubbs@gentoo.org \
--to=jstubbs@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox