Gnuclad claims a child starts after it's parent when it's not true

Bug #1911682 reported by A Eylenburg
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnuclad
New
Undecided
Unassigned

Bug Description

I'm getting "child starts AFTER it's parent stops" when that's not the case and the parent is in fact still alive.

Example error:
"Warning: AFROS starts AFTER it's parent (EmuTOS) stops!"

Corresponding CSV extract:

N,EmuTOS,#000,,2001.10,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
N,AFROS,#FF8585,EmuTOS,2002,2009,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

So as you can see node EmuTOS does not have an end date.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.