Hi Krum, As far as I understand, the "legacy update site" issue may just be the way aggragation failed because of the update, but not the cause of the failure. We can imagine the during the aggregation process, your repo was updated (update of repo during aggregation isn't supported by the aggregation process), so it put aggregation in an inconsistent state and the aggregator wrongly reported that the cause is usage of legacy update site. With last message from Alexander saying everything is working now, I think we can assume everything is back to work and stop worrying about it.
HTH
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
