Python-mode: Running into git submodule issue when updating the plugin via Vundle

Created on 8 Jun 2018  Â·  11Comments  Â·  Source: python-mode/python-mode

I understand this might be an issue with Vundle, but since all the other plugins update just fine and python-mode has a warning about precisely this thing in the README file I thought it might go here. I get the following error when attempting to update the plugin:

[2018-06-08 11:24:11] Plugin python-mode/python-mode
[2018-06-08 11:24:11] $ cd '/home/user/.vim/bundle/python-mode' && git pull && git submodule update --init --recursive
[2018-06-08 11:24:11] > Already up to date.
[2018-06-08 11:24:11] > error: Server does not allow request for unadvertised object 0949a1609dcd59995ae0e30ae2bb644a1aeae744
[2018-06-08 11:24:11] > Fetched in submodule path 'submodules/snowball_py', but it did not contain 0949a1609dcd59995ae0e30ae2bb644a1aeae744. Direct fetching of that commit failed.

Manually running git submodule update --init --recursive in ~/.vim/bundle/python-mode returns the same error.

According to the log, it is updated (and I can see the latest commit in the git log is from 2018-06-01, so it looks okay, but the error message is bugging me.

Thanks!

Most helpful comment

 Plugin python-mode/python-mode                                                                                                                          
 $ cd '/home/neckerskorn/.vim/bundle/python-mode' && git pull && git submodule update --init --recursive                                                 
 > Already up to date.                                                                                                                                   
 > error: Server does not allow request for unadvertised object 837ecd3d7a8597ab5f28bc83072de68e16470f1e                                                 
 > Fetched in submodule path 'submodules/pylama', but it did not contain 837ecd3d7a8597ab5f28bc83072de68e16470f1e. Direct fetching of that commit failed.

This is due to .git/config and .gitmodules referring to different remotes (a fork?) for pylama. Fixed by running git submodule sync.

All 11 comments

Hi @nachogoro.
Can you please send me the content of the ~/.vim/bundle/python-mode/.gitmodules file?

Definitely, thanks for the quick reply!

[submodule "submodules/autopep8"]
    path = submodules/autopep8
    url = https://github.com/hhatto/autopep8
    ignore = dirty
[submodule "submodules/pycodestyle"]
    path = submodules/pycodestyle
    url = https://github.com/PyCQA/pycodestyle
    ignore = dirty
[submodule "submodules/pydocstyle"]
    path = submodules/pydocstyle
    url = https://github.com/PyCQA/pydocstyle
    ignore = dirty
[submodule "submodules/mccabe"]
    path = submodules/mccabe
    url = https://github.com/PyCQA/mccabe
    ignore = dirty
[submodule "submodules/pyflakes"]
    path = submodules/pyflakes
    url = https://github.com/PyCQA/pyflakes
    ignore = dirty
[submodule "submodules/snowball_py"]
    path = submodules/snowball_py
    url = https://github.com/diraol/snowball_py
    ignore = dirty
[submodule "submodules/pylama"]
    path = submodules/pylama
    url = https://github.com/fmv1992/pylama
    ignore = dirty

Hum.....

And what about the result of:

cd ~/.vim/bundle/python-mode/submodules/snowball_py
git config -l

?

[email protected]
user.name=NachoGoro
core.preloadindex=true
core.trustctime=false
includeif.gitdir:~/personal/.path=~/personal/gitconfig
core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
core.worktree=../../../../submodules/snowball_py
remote.origin.url=https://github.com/shibukawa/snowball_py
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
branch.master.remote=origin
branch.master.merge=refs/heads/master

The repo seems to be checked out at f7fb6afc03ee6069b79a3eed861019e12d168596.

@nachogoro, can you try removing the snowball submodule and then reinserting it?

My settings for git config -l under snowball_py dir is:

core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
core.worktree=../../../../submodules/snowball_py
remote.origin.url=https://github.com/diraol/snowball_py
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
branch.develop.remote=origin
branch.develop.merge=refs/heads/develop

We are pointing to different repos, and python-mode .gitmodule file points to my fork of snowball_py, which contains some extra fixes. (Also, it points to snowball_py develop branch, instead of master)

Awesome! Reinstalling the whole python-mode plugin fixed the issue. Not
sure how the misconfiguration happened, though, but all good now :)

On Tue, Jun 12, 2018, 15:31 Diego Rabatone Oliveira <
[email protected]> wrote:

@nachogoro https://github.com/nachogoro, can you try removing the
snowball submodule and then reinserting it?

My settings for git config -l under snowball_py dir is:

core.repositoryformatversion=0
core.filemode=true
core.bare=false
core.logallrefupdates=true
core.worktree=../../../../submodules/snowball_py
remote.origin.url=https://github.com/diraol/snowball_py
remote.origin.fetch=+refs/heads/:refs/remotes/origin/
branch.develop.remote=origin
branch.develop.merge=refs/heads/develop

We are pointing to different repos, and python-mode .gitmodule file
points to my fork of snowball_py, which contains some extra fixes. (Also,
it points to snowball_py develop branch, instead of master)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/python-mode/python-mode/issues/901#issuecomment-396589682,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AO8h41eT7JxLuSQPDxRs3aqH82uATV2cks5t78KcgaJpZM4Ufyz6
.

Great!

Probably something from when we changed from branch master to develop and also changed the submodule reference (to my fork).

hey, sorry for reoppening this issue but, I got exactly the same problem with the submodule "pylama" and when nothing when I try to reinstall :'(
screenshot from 2018-10-03 20-55-47

Hi @tonitch sorry, can you try again? I think I've made a silly mistake.

yep, it work :D I'v another issue but i'll post it asap :+1:
screenshot from 2018-10-03 21-54-01

 Plugin python-mode/python-mode                                                                                                                          
 $ cd '/home/neckerskorn/.vim/bundle/python-mode' && git pull && git submodule update --init --recursive                                                 
 > Already up to date.                                                                                                                                   
 > error: Server does not allow request for unadvertised object 837ecd3d7a8597ab5f28bc83072de68e16470f1e                                                 
 > Fetched in submodule path 'submodules/pylama', but it did not contain 837ecd3d7a8597ab5f28bc83072de68e16470f1e. Direct fetching of that commit failed.

This is due to .git/config and .gitmodules referring to different remotes (a fork?) for pylama. Fixed by running git submodule sync.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

zeraus picture zeraus  Â·  11Comments

randomizedthinking picture randomizedthinking  Â·  7Comments

12kleingordon34 picture 12kleingordon34  Â·  3Comments

lyneca picture lyneca  Â·  4Comments

Notaduck picture Notaduck  Â·  4Comments