Control: reopen 721240
Control: retitle 721240 Please provide a stable branch as a normal git
branch in refs/heads namespace
On 29 August 2013 12:24, Dmitrijs Ledkovs <x...@debian.org> wrote:
> On 29 August 2013 12:17, Dmitrijs Ledkovs <x...@debian.org> wrote:
>> On 29 August 2013 11:51, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote:
>>> Dmitrijs Ledkovs writes ("Bug#721240: Fwd: [recipe build #530064] of ~xnox
>>> dgit-daily in precise: Failed to build"):
>>>> Package: dgit
>>>> Version: 0.14
>>>>
>>>> It looks like the current master has broken top changelog entry, thus
>>>> breaking automatic daily build of the package from git on a derivative
>>>> distribution.
>>>>
>>>> dgit (0.14) unstable; urgency=low
>>>>
>>>> * Include package name in tag message.
>>> ...
>>>> Is that on purpose?
>>> ...
>>>> Please keep master always in a buildable state, for the dgit users =)
>>>
>>> In dgit-repos/reops/dgit.git, "master" is a working branch which may
>>> contain half-finished changes and syntax errors.
>>>
>>
>> From upstream perspective, I would have thought it would be
>> interesting to have continious integration and catch those rather
>> earlier than later.
>>
>>
>>> In general, a "master" branch is not guaranteed even to exist in a
>>> dgit-repos repo. If you're doing some kind of automatic daily build
>>> you should do it from one of the suite branches.
>>>
>>
>> Well, I'm not actually building "master". Git clone points by default
>> at remote HEAD, and the HEAD currently points to master. Maybe it
>> makes more sense for dgit git repositories to have HEAD point at
>> dgit/sid instead?
>>
>> At the moment if I do:
>> $ git clone git://anonscm.debian.org/git/dgit-repos/repos/dgit.git
>>
>> Which results in:
>>
>> $ git branch -a
>> * master
>> remotes/origin/HEAD -> origin/master
>> remotes/origin/master
>>
>> It's typical for git projects to have HEAD in an always (at least)
>> buildable state, and stage experimental changes on a non-default
>> branch. (typicall "master" and "next" respectfully)
>> To follow that logic, it makes sense for dgit git repository for HEAD
>> to point at dgit/sid, while "next" branch is called master.
>> This also suits NMU workflow better, as I'd like to git clone & commit
>> NMU, not on top of any other staged but not ready for upload changes.
>>
>
> Actually ignore me, this is not a bug. And dgit/* are reserved for
> dgit push and nothing else.
No, I'm still stuck. As dgit/* are not normal branches, the default
git clone doesn't clone them and thus I have no stable reference to
build from.
Regards,
Dmitrijs.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
