Set refspecs in clone so that future fetch does not need to be fast-forwarding
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
git-ubuntu |
Fix Released
|
Critical
|
Nish Aravamudan |
Bug Description
I had a cloned samba repository where I decided to run "git fetch pkg", and was surprised to get rejections on branches that I never even checked out:
(ubuntu/
remote: Counting objects: 311, done.
remote: Compressing objects: 100% (26/26), done.
remote: Total 311 (delta 280), reused 310 (delta 279)
Receiving objects: 100% (311/311), 310.20 KiB | 446.00 KiB/s, done.
Resolving deltas: 100% (280/280), completed with 249 local objects.
From https:/
! [rejected] applied/
! [rejected] debian/buster -> pkg/debian/buster (non-fast-forward)
7511daf27.
c80fbe820.
3367af40b.
* [new tag] import/
* [new tag] upstream/
I ended up doing "git fetch pkg --force". Nish said this:
"we need to set the refspecs *in* clone so that future fetch does nnot need to be fast-forwarding"
Related branches
- Server Team CI bot: Approve (continuous-integration)
- git-ubuntu developers: Pending requested
-
Diff: 72 lines (+22/-24)1 file modifiedgitubuntu/git_repository.py (+22/-24)
Changed in usd-importer: | |
status: | New → In Progress |
importance: | Undecided → Critical |
assignee: | nobody → Nish Aravamudan (nacc) |
milestone: | none → lp-beta |
tags: | added: clone remote |
Changed in usd-importer: | |
status: | In Progress → Fix Released |