I haven't followed this thread, and these steps require a bit of git savvy, 
but: you probably need to go into the package METADATA directory, create a 
branch with all your registrations, then check out metadata-v2 again. Do a 
rebase on origin/metadata-v2 and edit it to keep just the registration commits 
you're ready to publish. Then do Pkg.publish(). When you're ready to publish 
more of your registered packages, cherry-pick the commits from the 
"registrations" branch you created in the first step.

Alternatively you might be able to blow away your METADATA directory and clone 
it from scratch and start over. But DON'T do this until someone else who knows 
more about Pkg internals than me tells you that's safe. I bet it is, but just 
sayin'.

--Tim

On Friday, September 05, 2014 06:36:09 AM Samuel S. Watson wrote:
> For the record, I tried Mauro's suggestion, and it worked but it wasn't the
> right thing to do. And the step where I'm stuck is Pkg.publish(), not
> Pkg.register(). That's the one that the documentation says often breaks,
> and it also doesn't take any arguments, which makes me think it's going to
> publish all my registered packages, which I'm not ready to do.

Reply via email to