fetch fails with "fatal: couldn't find remote ref refs/notes/commits"

Bug #1877486 reported by Bryce Harrington
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
git-ubuntu
Fix Released
Undecided
Robie Basak

Bug Description

git ubuntu version: 0.10

Steps to reproduce:
$ git ubuntu clone exim4 exim4-gu
$ cd exim4-gu/
$ git status
On branch ubuntu/devel
nothing to commit, working tree clean

$ git ubuntu remote add sergiodj
fatal: Couldn't find remote ref refs/notes/commits

I'm able to clone his branch into a separate directory though:
$ git clone -b groovy-exim4-93-15-merge git+ssh://<email address hidden>/~sergiodj/ubuntu/+source/exim4
Cloning into 'exim4'...
remote: Counting objects: 1642, done.
remote: Compressing objects: 100% (880/880), done.
remote: Total 1642 (delta 918), reused 1163 (delta 724)
Receiving objects: 100% (1642/1642), 3.72 MiB | 2.45 MiB/s, done.
Resolving deltas: 100% (918/918), done.

Here is the .git/config from the first git ubuntu clone:
###

[core]
        bare = false
        repositoryformatversion = 0
        filemode = true
        logallrefupdates = true
[remote "pkg"]
        url = https://git.launchpad.net/ubuntu/+source/exim4
        fetch = +refs/heads/*:refs/remotes/pkg/*
        fetch = +refs/tags/*:refs/tags/pkg/*
        fetch = +refs/notes/commits:refs/notes/changelog
        pushurl = ssh://<email address hidden>/ubuntu/+source/exim4
        tagOpt = --no-tags
[remote "bryce"]
        url = https://git.launchpad.net/~bryce/ubuntu/+source/exim4
        fetch = +refs/heads/*:refs/remotes/bryce/*
        fetch = +refs/tags/*:refs/tags/bryce/*
        fetch = +refs/notes/commits:refs/notes/changelog
        pushurl = ssh://<email address hidden>/~bryce/ubuntu/+source/exim4
        tagOpt = --no-tags
[notes]
        displayRef = refs/notes/changelog
[remote "sergiodj"]
        url = https://git.launchpad.net/~sergiodj/ubuntu/+source/exim4
        fetch = +refs/heads/*:refs/remotes/sergiodj/*
        fetch = +refs/tags/*:refs/tags/sergiodj/*
        fetch = +refs/notes/commits:refs/notes/changelog
        pushurl = ssh://<email address hidden>/~sergiodj/ubuntu/+source/exim4
        tagOpt = --no-tags
###

Here's the .git/config from directly checking out sergio's branch:

[core]
        repositoryformatversion = 0
        filemode = true
        bare = false
        logallrefupdates = true
[remote "origin"]
        url = git+ssh://<email address hidden>/~sergiodj/ubuntu/+source/exim4
        fetch = +refs/heads/*:refs/remotes/origin/*
[branch "groovy-exim4-93-15-merge"]
        remote = origin
        merge = refs/heads/groovy-exim4-93-15-merge
        rebase = true

Related branches

Revision history for this message
Bryce Harrington (bryce) wrote :

Workaround appears to be to comment out the notes fetch in the sergiodj remote:

[remote "sergiodj"]
        url = https://git.launchpad.net/~sergiodj/ubuntu/+source/exim4
        fetch = +refs/heads/*:refs/remotes/sergiodj/*
        fetch = +refs/tags/*:refs/tags/sergiodj/*
# fetch = +refs/notes/commits:refs/notes/changelog
        pushurl = ssh://<email address hidden>/~sergiodj/ubuntu/+source/exim4
        tagOpt = --no-tags

$ git fetch sergiodj -a -t
remote: Counting objects: 19, done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 19 (delta 14), reused 2 (delta 1)
Unpacking objects: 100% (19/19), 8.17 KiB | 177.00 KiB/s, done.
From https://git.launchpad.net/~sergiodj/ubuntu/+source/exim4
 * [new branch] groovy-exim4-93-15-merge -> sergiodj/groovy-exim4-93-15-merge

description: updated
Revision history for this message
Robie Basak (racb) wrote :

Yes the fix for this is pending review.

Changed in usd-importer:
status: New → In Progress
assignee: nobody → Robie Basak (racb)
Revision history for this message
Robie Basak (racb) wrote :

Fixed in 9804f96.

Changed in usd-importer:
status: In Progress → Fix Committed
Revision history for this message
Robie Basak (racb) wrote : Fix released in git-ubuntu

Fix released in git-ubuntu version 1.0

Changed in usd-importer:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.