Bug 87520

Summary:	Graphical config tool does not see last package in ecos.db
Product:	[Retired] eCos	Reporter:	Chris Garry <cgarry>
Component:	ConfigTool	Assignee:	John Dallaway <jld>
Status:	CLOSED CURRENTRELEASE	QA Contact:	John Dallaway <jld>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0 beta 1	CC:	jifl-bugzilla
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-03-28 12:06:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Garry 2003-03-28 09:33:48 UTC

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461; .NET 
CLR 1.0.3705)

Description of problem:
The graphical configuration tool (as supplied with 2.0b1) does not see the 
last 'package' entry in the ecos.db file.

In the 2.0b1 repository, the last package (not target) entry is 'Allied Telesyn 
TS1000 ethernet driver'.  But if you select:
build->Packages from the menu and attempt to add the package it is not listed 
under the 'Available packages'.

If you now add a new package using the package administration tool (the lwip 
package for example), then when you  select build->packages the 'Allied Telesyn 
TS1000 ethernet driver' is now listed but the 'lwip' package is not.

This is seen on a Win2K PC running Cygwin.


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Start the graphical config tool and select Build->Packages from the menu.
2. In the available packages window look for the 'Allied Telesyn TS1000 
ethernet driver' (the last package in the 2.0b1 ecos.db file).  It is not there.
3. In the available packages window look for the 'Flash memory support for 
Allied Telesyn TS1000 ...' (the 2nd to last package in the 2.0b1 ecos.db 
file).  It is there.
4. Close the graphical config tool and hand edit the ecos.db file to swap round 
the order of the 2 packages.
5. Repeat steps 1 to 3 to see the ethernet driver package is now seen, but the 
FLASH support package is not.

Additional info:

Comment 1 John Dallaway 2003-03-28 12:06:53 UTC

Problem reproduced, identified and (trivially) fixed. A 'for' loop which 
populates the packages lists in the packages dialog was terminating 
prematurely. I have checked the fix in to anonCVS and it should appear in the 
eCos 2.0 final release. 
 
Thanks for the clear and concise bug report!