repoman -vdx --echangelog=n -a -m "test commit" commit RepoMan scours the neighborhood... fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' [INFO] checking package dev-python/packaging >>> Creating Manifest for /local/home/justin/tree/dev-python/packaging fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' RepoMan sez: "Doing nothing is not always good for QA." (Didn't find any changed files...)
As a workaround can initialize the repository, you can initialize the repository HEAD with an empty commit like this: git commit --allow-empty -m "initial empty commit" We can fix repoman to use the empty tree hash when HEAD does not exist. The empty tree hash is 4b825dc642cb6eb9a060e54bf8d69288fbee4904 which can be derived from `git hash-object -t tree /dev/null`.
repoman support has been removed per bug 835013. Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.
