On Wed, Nov 22, 2017 at 7:40 AM, Vít Ondruch <[email protected]> wrote:
>
>
> Dne 16.11.2017 v 17:32 Pierre-Yves Chibon napsal(a):
>> On Thu, Nov 16, 2017 at 12:53:44PM +0100, Nikos Mavrogiannopoulos wrote:
>>> On Thu, 2017-11-16 at 09:54 +0100, Pierre-Yves Chibon wrote:
>>>> On Thu, Nov 16, 2017 at 09:14:53AM +0100, Nikos Mavrogiannopoulos
>>>> wrote:
>>>>> Hi,
>>>>>  Has anyone noticed any commits disappearing from packages
>>>>> around/after
>>>>> August 16?
>>>>>
>>>>> Seeing that build for f27:
>>>>> https://koji.fedoraproject.org/koji/buildinfo?buildID=956210
>>>>>
>>>>> it contains the message:
>>>>> * Wed Aug 16 2017 Nikos Mavrogiannopoulos <[email protected]> -
>>>>> 20170816-
>>>>> 1.git2618a6c
>>>>>  - Updated to latest upstream - Restarts openssh server on policy
>>>>> update
>>>> Koji tells you the URL which was used to trigger the build:
>>>> Source: git://pkgs.fedoraproject.org/rpms/crypto-
>>>> policies?#e4abbf8b20f065dab68c28c33b7b55b4b297bf76
>>>> cf: https://koji.fedoraproject.org/koji/taskinfo?taskID=21257571
>>>>
>>>> Which corresponds to this commit in git:
>>>> https://src.fedoraproject.org/rpms/crypto-policies/c/e4abbf8b20f065da
>>>> b68c28c33b7b55b4b297bf76
>>>>
>>>> That commit is indeed in master but not in f27.
>>> Given that, it seems that there was a desync between the branched git
>>> for f27 and the build for it. Was that just an unlucky build that got
>>> from master to 27, while its corresponding code didn't?
>> Koji doesn't check the branch in which a commit is, it just builds from the
>> specified git repo (head, branch or hash).
>> This is also the main reason why releng doesn't remove branches from 
>> dist-git.
>
> If there was tag for each build, would it be possible to drop branches?
>

I think we'd need to have tags regardless, because otherwise there's
no obvious map with the non-dist branch stuff...



-- 
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to