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 <nmav@xxxxxxxxxx> - > > > 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. Pierre _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
