I did a "repo sync", followed by "repo start asmmacros".
I think went and added my changes to "system/core", reviewed and committed them.
If it do "git log" in "system/core" I see my changeset in the log.
I think do a "repo upload" from the top directory and get:
"no branches ready for upload"
Can someone please tell my why I'm an idiot, or point me to an RTFM.
I've read the contribute page, and the repo web page, but I'm
obviously doing something trivially stupid.
Thanks,
Benno
I'm pretty sure this is completely a user error. (I'm an idiot!) But I
can't work out what is going on.
I did a "repo sync", followed by "repo start asmmacros".
I think went and added my changes to "system/core", reviewed and committed them.
If it do "git log" in "system/core" I see my changeset in the log.
I think do a "repo upload" from the top directory and get:
"no branches ready for upload"
Yeah, it was there. I did a fresh checkout and got things working. I
tracked it down a little bit before that though. The 'git refs' (I
think that was the command, maybe something similar), was giving the
wrong info. In particular, if I ran it in the actual checkout
directory, it returned a list with "asmmacros" in it, but with GIT_DIR
environment variable, which pointed to .repo/system/core.git (or
similar? sorry, can't remember).
So I'm not sure why one place got updated, and not the other...
strange. It could be because it did a cp -R <oldtree> <newtree>,
rather than doing a fresh init.
> If the branch "asmmacros" block is missing, that's why it won't upload.
> "repo start asmmacros" was supposed to have created this block; if the
> creation failed, it won't upload. You can edit the config file and insert
> this block yourself, or create a different branch and merge your work into
> it, e.g.:
>
> cd system/core
> repo start asm2 .
> git merge asmmacros
> git branch -d asmmacros
> repo upload
>
> Out of curiosity, what version of Python are you running (python -V).
2.5.1
> I'm starting to suspect that the subprocess module is just plain busted in
> some releases of Python, because I'm seeing users report failures due to
> processes running concurrently when repo is trying to run them sequentially,
> or cases of processes not even executing, and errors never being reported.
Mmm, not the case this time.
Cheers,
Benno
Hi everyone!
I’m having the same issue when doing the command repo upload; i get no branches ready for upload.
If I check the file system/core/.git/config as it was mentioned i get the entire branches blocks that are supposed to be. Also, when I do git branch –vv I see the branch that’s being tracked with my local one, and the commit I did to it.
If someone can give me any advice or hint that could help me I would really appreciate it.
Many thanks in advanced.
Regards,