[Angstrom-devel] bitbake angstrom-console-image failing onprocps

[Paul Sokolovsky]

Hello Michael,

Tuesday, October 2, 2007, 9:16:25 PM, you wrote:

>> 
>> Build completes now, but strangely, it failed several times on different
>> packages.  If I cleaned the package and then expressly rebuilt it, it would
>> build, then I would resume with the 'bitbake angstrom-console-image' - this
>> happened 3-4 times during the build.
>> 
>> Any ideas?  Just sunspots?  more curious than anything else.
>> 

> I don't know about other packages, but with this procps fix, I'd guess
> that's because I didn't bump PR after adding a patch, because in my 
> opinion build fixes do not warrant upgrade of already built binary 
> packages.

  Depends. Such attitude makes builds less deterministic - different
parties may have differently built packages which however has the same
revision. It also may mean that context-dependent bugs may go
unnoticed to bite later - for example, it builds for some people,
doesn't build for you, you apply patch, which makes it build for you,
and regresses for the others, yet this go unnoticed for them until
they bother to rebuild from scratch. Btw, recently we discussed an
issue which was kinda close to this description, right?

  So, it's of course a compromise of pragmatism and formality, but
having other ratio might be helpful. For example, for gcc or glibc, it
would be desirable to avoid semi-spurious bumps, yet for other stuff
which are many it's easier to bump and forget (but let people remind
you soon if something's wrong).

> So, it's normal.

> Love,
> H


-- 
Best regards,
 Paul                            mailto:pmiscml at gmail.com