Nirbheek Chauhan wrote:
That's because repoman is context-aware. When you use it, it'll look
"around" (../..) the current directory for the dependencies. If it
finds the deps, it'll check if the ebuilds. If can't find the
dependencies, it'll look in ${PORTDIR} for checking them.
Thanks. I really
On Mon, Sep 14, 2009 at 10:26 AM, Andrey Grozin
wrote:
> So, the two directories are identical, but repoman behaves differently.
>
That's because repoman is context-aware. When you use it, it'll look
"around" (../..) the current directory for the dependencies. If it
finds the deps, it'll check if
Jorge Manuel B. S. Vicetto wrote:
I just tried it here and I don't get any errors from repoman. I've run
repoman full -d and it only complains about ebuild.allmasked. Have you
synced the entire repo? In particular the profiles/* tree?
Yes, of course I synced the tree. Now I see even a more stra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andrey Grozin wrote:
> Hello *,
>
> I am fixing a bug (#284080) in a ebuild
> (sci-visualization/mayavi-3.3.0). I have a fix that installs on my
> box fine, all deps are satisfied. I try to commit it, but repoman
> issues a lot of errors like
>
> RDEPE
Hello *,
I am fixing a bug (#284080) in a ebuild (sci-visualization/mayavi-3.3.0).
I have a fix that installs on my box fine, all deps are satisfied. I try
to commit it, but repoman issues a lot of errors like
RDEPEND.bad 25
sci-visualization/mayavi/mayavi-3.3.0.ebuild: