Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better explanation for "deliverer-changed" #1186

Open
marcoscaceres opened this issue Mar 22, 2024 · 1 comment
Open

Better explanation for "deliverer-changed" #1186

marcoscaceres opened this issue Mar 22, 2024 · 1 comment

Comments

@marcoscaceres
Copy link
Member

marcoscaceres commented Mar 22, 2024

We are unclear about what to do when we hit "deliverer-changed" errors.

We have joint deliverables we would like to publish (DAS and WebApps). What do we need to do to get deliverer-changed to accept our two groups? The groups appear to be correct, just Echidna is unhappy.

Found while trying to publish “echidna.tar” (see the publication job)

Cc @himorin

@deniak
Copy link
Member

deniak commented Mar 22, 2024

For historical reasons with the patent policy, there's a current limitation with echidna on specs changing/updating deliverers.
Echidna won't be able to process these docs so they first need to be manually published by sending the request to [email protected] so we can acknowledge the change. Once it's done, the following requests from Echidna should work.

Note that, with the patent policy 2020, we should be able to update echidna to accept these changes. It's been on my todo list for some times now but I didn't find time to work on that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants