Change Details

As per parent task's description (T847), it's possible that the origin computation urls mixed up multiple homonyms dumps. Resulting in the same origin for different dumps (googlecode hosted googlecode and eclispselabs dumps in different arborescence tree but that was not accounted for when creating the actual origin's url). This needs to be investigated and fixed if it's actually true (at least one occurrence is referenced in the parent so that tends to be :). Note: This would also explain an error so far unexplained 'No revision found' on the latest svn loader rescheduling.

As per parent task's description (T847), there exists homonyms dumps coming from different sources. The original urls was not amongst the data transmitted from googlecode when we retrieved information. Thus we had to build them back. The original origin_url computation was too naive. This results in clash in origin urls fields. For the same dumps, we have the same origin (googlecode hosted googlecode and eclispselabs dumps in different arborescence tree). This needs to be fixed. Note: This would also explain an error so far unexplained 'No revision found' on the latest svn loader rescheduling.

As per parent task's description (T847), it's possible that the origin computation urls mixed up multiple homonyms dumpsthere exists homonyms dumps coming from different sources. Resulting in the same origin for different dumps (googlecode hosted googlecode and eclispselabs dumps in different arborescence tree but that was not accounted for when creating the actual origin's urlThe original urls was not amongst the data transmitted from googlecode when we retrieved information. Thus we had to build them back. The original origin_url computation was too naive. This results in clash in origin urls fields. For the same dumps, we have the same origin (googlecode hosted googlecode and eclispselabs dumps in different arborescence tree). This needs to be investigated and fixed if it's actually true (at least one occurrence is referenced in the parent so that tends to be :)fixed. Note: This would also explain an error so far unexplained 'No revision found' on the latest svn loader rescheduling.