Le mercredi 17 décembre 2014 à 13:55 +0000, Kanevskiy, Alexander a écrit :
> - one of the most important things: no broken builds should be in > profiles. Failed to build package is one of the first priority candidates > to be selected for build if any meta information in repository changes. > so, system can spend times on trying to build something that is broken and > that is not unblocking packages further in the chain. In Common at the > moment there are 5 build failures (at least 2 package changes seems to be > accepted without any testing). Hello, You are right. Please accept my apologies for that state but also accept some explanations. First, croswwalk was broken because of some infrastructure issue. As you know it is a huge piece of code and it reached the 3Gb as .tar. Ronan Le Martret found that replacing .tar by .tar.gz in the spec file solves the issue encountered this morning. Second, last week Stephane changed the default compiling flags. I guess that the new flags are in place since dec. 12th. This has revealed some new warnings that are now breaking packages that have the option -Werror set and that was okay before. I proposed 2 changes for solving this issues [1] and [2]. Third, during the transition between me and Stephane, Crosswalk was broken and some decision about accepting packages or not was hard to take. (And, consequently, the submit queue also grew). If I had maintenance right on prerealease, I would stop selectively their build until recovery of normal load. Best regards José Bollo [1] https://review.tizen.org/gerrit/#/c/32354/ [2] https://review.tizen.org/gerrit/#/c/32362/ _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
