Thanks for your response, Jan-Simon-- The sources I'm building from were captured immediately prior to the the M2 Aug release, though now that I think about it they probably are *not* the sources used for that build... Is there a label that corresponds exactly to each (or even just the current) release? That's what I should be building from because I'm attempting to replicate the release, complete with any constituent defects. :-)
I know that gbs uses rpmbuild, shouldn't that give the same answer regardless of whether it's initiated by gbs or obs? The errors I've pointed out should *not* be influenced by how the build is started or even what *compilers* are used-- A syntax error is still an error, and a missing definition is still missing no matter the tool. If gbs is an unreliable tool, then we need to either say that and discourage its use or we need to characterize where it does work well. :-) Personally, I'm still hoping that it's some error in how we are set up here; if we can figure out what it is then it's also in our power to correct it. I want to be viewed as a positive force for good, not the alternative! <g> So here's a question: Was the August M2 release built against a branch and tag (hazy how git refers to such things...) that we can replicate now? TIA, 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 On Sat, Sep 7, 2013 at 1:17 AM, Jan-Simon Möller <[email protected]> wrote: > On Friday 06 September 2013 10:43:52 Hanchett, Paul wrote: > > If OBS and GBS are building the same package, why wouldn't they get the > > same result (assuming no circular references)? > > Well, GBS is just not OBS. > GBS is made to build from a git source tree and make that easy - extended > to > build multiple dependent packages. > > But a full distro with it's cycles and cross-references is more complex. > OBS > was built for exactly that. > > > > > FYI, I'm finding a lot of build errors that are hard to understand-- > Things > > like: > > > > - Configure script gives errors > > - Various compile errors (conflicting definitions/undeclared; > warnings, > > with "treat warnings as errors" turned on..; etc.) > > - use of deprecated api's g_mutex_new, g_mutex_free, g_cond_timed_wait > > - ld errors > > - Multiple missing 1.x patch files on 2.x build > > - Missing libraries > > - "Architecture is excluded" (i686 with -Ai586 on build line) > > - rpmlint exceeds "badness" score > > - rpm error "installed but unpackaged files found" > > - Makefile.am: required directory does not exist (".intl) > > - use of %(x) construct causes lots of commentary from rpm... > > - quite a number and variety of other warnings > > We might hit here differences between what is in the repo/binaries and > what you > build from the source tree through gbs. What does the src.rpm contain vs. > the > tarball you get through gbs. > > > > > > All but the last two would have halted the package build. I expect that > a > > developer touching the package would have tried to rebuild the package > and > > would have noticed and repaired any package defects. > > > > It is as though changes are getting checked in and peer reviewed without > > the package being built to confirm that the package is created... > > There is a peer review, and they're built within the OBS. Maybe someone > eplains to us how the gerrit review-process to package - to OBS - to repo > works right now in Tizen. > > > So, how do we fix this? Then, how do we verify that what is fixed for > gbs > > is also correct for obs? (In these cases, it really should be--but if > it's > > building in obs then something is not reciprocal...) > > Really good points and we need to make this process available for all > participants. > > > For what it's worth, I'm more than willing to help--I just want to be > sure > > that what I'm doing is really the Right Thing To Do. :-) > > > > Thanks for listening, > > Paul > > > > BR, > Jan-Simon >
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
