I have encountered failing test GRPackageTest>>testPackages. This takes its dependencies from GRPackage class>>grPackages. It now fails for Pharo even thou the the packages is there.

I'm talking about Seaside-Pharo-Canvas which is mentioned in GRPackage class>>magrittePharoSeaside as dependency

I could fix it with:

seasidePharoCanvas
	^ self new
		name: 'Seaside-Pharo-Canvas';
		description: 'Seaside''s Pharo Canvas integration with Magritte metamodel.';
		addDependency: 'Magritte-Seaside';
		url: #seasideUrl;
		yourself

Note: It passes in GemStone as there is no -Pharo- package.

Is this functionality used? If not, wouldn't it be better to mark it obsolete?