Dependency relationships in buildsys: was Fedora Extras 4 Package Build Report

[seth vidal]

On Wed, 2005-11-02 at 14:14 -0600, Quentin Spencer wrote:
> seth vidal wrote:
> 
> >On Wed, 2005-11-02 at 13:56 -0600, Quentin Spencer wrote:
> >  
> >
> >>Ville Skyttä wrote:
> >>
> >>    
> >>
> >>>On Wed, 2005-11-02 at 12:57 -0600, Quentin Spencer wrote:
> >>>
> >>> 
> >>>
> >>>      
> >>>
> >>>>When these releases are done, doesn't that mean the build system has the 
> >>>>released packages available for future builds?
> >>>>   
> >>>>
> >>>>        
> >>>>
> >>>Unless I'm mistaken, they should actually be available even earlier,
> >>>right after they've been built.  But see below.
> >>> 
> >>>
> >>>      
> >>>
> >>I thought so, too, but last week I had a case where I submitted two 
> >>builds where the second depended on the first, and the second failed 
> >>because the version of the first package that mock installed was an old 
> >>one rather than the one that had just completed. Anyway, I requested a 
> >>new build of octave-forge and it seems to be working now, so I must have 
> >>by chance hit the window where the current libraries weren't available 
> >>the first time I built it.
> >>    
> >>
> >
> >No, Last week there was another issue. The mock configs on the
> >buildboxes had not been updated to point to the needsign repos for the
> >new targets since the plague 0.4.X update.
> >  
> >
> 
> 
> 
> Wait, I'm still seeing this problem. Build number 514 just failed a few 
> minutes ago on x86_64 because it tried to install
> ginac-devel-1.3.2-1.fc5.x86_64 instead of 
> ginac-devel-1.3.3-1.fc5.x86_64, which completed building earlier today 
> (build number 499) and is awaiting release.

Dan, 
 How often does createrepo get re-run on the needsign repo?

-sv