On Wed, Nov 13, 2013 at 6:17 AM, Ronan Le Martret <[email protected]> wrote:
> In Tizen OBS the problem is not visible, because the previous packages are > not built from the git source, but from a archive tarball. > Hence, the date bug does not show. > This pretty clearly points out the danger of falling back to an older version when the current version fails to build. I understand that it's a tactical choice, but it may be a strategic error (at least from a quality process point of view.) Maybe there need to be two OBS builds, one that substitutes pre-built for package build failures and another that does not? BTW, one of our people here told me that in the past couple of days he got the current tizen sources and was able to build with GBS resulting in only 15 errors and 900+ successful packages-- That's a great improvement! Great work, it is very encouraging! Paul Paul Hanchett ------------------- Infotainment Engineer MSX on behalf of Jaguar Land Rover One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, Oregon, 97204 Email: [email protected] ------------------- Business Details: Jaguar Land Rover Limited Registered Office: Abbey Road, Whitley, Coventry CV3 4LF Registered in England No: 1672070
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
