-----BEGIN PGP SIGNED MESSAGE-----
On Thursday 01 April 2004 13:21, Bart Lauwers wrote:
> On Thursday 01 April 2004 11:38, Paul de Vrieze wrote:
> > On Thursday 01 April 2004 11:05, Spider wrote:
> > > please fix the darn Manifest files when you've been touching
> > > things. That includes when you remove files, when you modifiy
> > > patches (!) and others.
> > I completely second this. You must use repoman. Only in very very
> > few special cases is it waranted not to use repoman. If repoman
> > prevents you from committing something, find out why and either have
> > repoman fixed, or fix your package.
> When removing files repoman won't update Manifest, that's bug number
> one, actually I think it will even not let you commit that update
> (rm'ed file).
You also need to remove them from cvs of course. If that doesn't do the
trick, please file a bug.
> And now it also seems when using repoman you still need to verify
> everything by hand because you can't depend on it to do it properly.
> So far I've had nothing but trouble with it and it's never given me
> any helpfull comments, except for complaining about going out of
> So how does one regenerate the Manifest when repoman feels it's not
> needed? touch one of the non-changed builds and repoman commit or is
> there another way?
ebuild some-ebuild.ebuild digest
This will do the trick. That should also fix the deleted file issue.
Paul de Vrieze
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
-----END PGP SIGNATURE-----
firstname.lastname@example.org mailing list