[Rock-dev] Autobuild behaviour for fixed packages

[Janosch Machowinski]

The Problem is :
Local repo is checked out at master / any commit that is ahead of the tag.
In this case Autoproj update will not move HEAD back to the tag, but
keep the current commit.
The Bad scenario now is :
1. Package is on master
2. Package is broken, and pinned back by another developer

If you now run an autoproj update you won't notice, that you should
be on the pin, but are still on master.

Also it is annoying in combination with the release.
Greetings
     Janosch


Am 04.06.2015 um 11:17 schrieb Steffen Planthaber:
> Hi,
>
> I'm not sure if i understood the problem.
>
> 1. A dev adds a override to develop a package
> 2. Another dev pins the package to a commit
>
> 3. On update the pinned commit is checked out without warning?
> or
> 3. The first dev doesn't recognize the the override?
>
> In the first scenario, there should be a warning.
>
> In the second, the (first) dev will encounter the same problem and
> either solve it in his (advanced code) and fix it there, or not
> encounter the problem at all. Both is fine for me.
>
> I think in the second case, no warning is required.
>
> Steffen
>
>
>
>
> Am 04.06.2015 um 10:53 schrieb Matthias Goldhoorn:
>> Hi Dev's,
>> we have a non-consens regarding the behaviour of autobuild.
>> The Core question is: Should Autoproj warn if a package is locally newer
>> than the given tag/commit-id
>>
>> Please follow the discussion, comment and help us to find a consens:
>> https://github.com/rock-core/autobuild/pull/23
>>
>> Best,
>> Matthias
>>
>>
>