On Mon, 2005-12-19 at 20:29 +0100, Marius Mauch wrote:
On Mon, 19 Dec 2005 13:45:04 -0500
solar [EMAIL PROTECTED] wrote:
If you do that please set it as a blocker for the .54 release.
Reintroducing ChangeLog/metadata.xml to Manifests would be a undesired
regression. Nothing in the
On Thu, 15 Dec 2005 22:47:21 -0500
Mike Frysinger [EMAIL PROTECTED] wrote:
this months meeting wasnt too eventful, kind of quiet ... on the
agenda:
- Marius: decision on multi-hash for Manifest1
there was a bit of hearsay about why the council was asked to
review/decide on this issue since
Marius Mauch wrote:
On Thu, 15 Dec 2005 22:47:21 -0500
Mike Frysinger [EMAIL PROTECTED] wrote:
this months meeting wasnt too eventful, kind of quiet ... on the
agenda:
- Marius: decision on multi-hash for Manifest1
there was a bit of hearsay about why the council was asked to
review/decide
On Mon, Dec 19, 2005 at 06:37:16PM +0100, Marius Mauch wrote:
On Thu, 15 Dec 2005 22:47:21 -0500
Mike Frysinger [EMAIL PROTECTED] wrote:
there was a bit of hearsay about why the council was asked to
review/decide on this issue since we werent able to locate any
portage devs at the time of
On Mon, 19 Dec 2005 13:45:04 -0500
solar [EMAIL PROTECTED] wrote:
If you do that please set it as a blocker for the .54 release.
Reintroducing ChangeLog/metadata.xml to Manifests would be a undesired
regression. Nothing in the portage as of =.53 make direct use of
those two files and there
On Mon, Dec 19, 2005 at 01:45:04PM -0500, solar wrote:
So right now I'll go ahead and add the pycrypto code to portage, but
will not yet add the dep to any ebuild or change anything metadata.xml
or ChangeLog related (according to Jason 2.0.54 is still away one or
two weeks anyway).
If
this months meeting wasnt too eventful, kind of quiet ... on the agenda:
- Marius: decision on multi-hash for Manifest1
there was a bit of hearsay about why the council was asked to review/decide on
this issue since we werent able to locate any portage devs at the time of the
meeting ... so our
