Because backend system was triggered by SR event from obs , and generally it should only handle these SRs triggered by submit tag, then updated the accepted/** branch. The kernel-x86-ivi package in Tizen:IVI was manually reverted by release engineer, so it didn’t update accepted/tizen/ivi branch to this commit in manifest.
Regards, Lin Yang From: Artem Bityutskiy <[email protected]<mailto:[email protected]>> Subject: Re: [Dev] what are the branch accepted/** for? Date: 2013年11月18日 GMT+8下午7:47:54 To: "Kanevskiy, Alexander" <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Reply-To: <[email protected]<mailto:[email protected]>> On Mon, 2013-11-18 at 11:40 +0000, Kanevskiy, Alexander wrote: Those special branches supposed to point to state of the code that is inside corresponding project. Tizen:Mobile -> accepted/tizen/mobile Developers should not touch those branches, those are created and updated automatically by build system. It looks like there is a bug. The latest IVI snapshots have kernel 3.11.6: http://download.tizen.org/snapshots/tizen/ivi/ivi/latest/repos/ivi/ia32/packages/i686/kernel-x86-ivi-3.11.6-4.4.i686.rpm The manifest file points to the correct commit id: http://download.tizen.org/snapshots/tizen/ivi/ivi/latest/builddata/manifest/tizen_20131115.3_ia32.xml a4b4fd84cb9cdcd8f66485389a1d4b7e8a2df267 However origin/accepted/tizen/ivi points to _incorrect_ commit id bd4424a20a794fc61efbb8f0a61630b1ff41f001 -- Best Regards, Artem Bityutskiy _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
