[Starlingx-discuss] Several build failures due to recent code integrations

[Cobbley, David A]

Great idea to verify mirror source lists.  The more involved package availability tests should also be considered as part of a full release cycle validation, though.

--David C

-----Original Message-----
From: Dean Troyer [mailto:dtroyer at gmail.com] 
Sent: Monday, July 2, 2018 8:34 AM
To: Cordoba Malibran, Erich <erich.cordoba.malibran at intel.com>
Cc: starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] Several build failures due to recent code integrations

On Mon, Jul 2, 2018 at 9:48 AM, Cordoba Malibran, Erich <erich.cordoba.malibran at intel.com> wrote:
> The root cause in all failures is the same, not adding the new needed packages into the mirror. Same thing about python src rpm reported last week.

Since this is likely to be a frequent problem can we come up with a test to verify the mirror lists?  I mean just make sure that our mirror source lists contain what we think they need to contain, not actually verify that the referenced packages are still available without downloading them.

These would both be good to have to run locally and possibly by Zuul if we can minimize reliance on reaching external sites.

dt

-- 

Dean Troyer
dtroyer at gmail.com

_______________________________________________
Starlingx-discuss mailing list
Starlingx-discuss at lists.starlingx.io
http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss