-
Notifications
You must be signed in to change notification settings - Fork 78
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
Handle upstream package indices containing packages with the wrong architecture #422
Comments
Analysis revealed that for example the HashiCorp repo package index
This is mainly a bug with the upstream repo (which is structured in a number of strange/specification and good practice defying ways), but we can nevertheless mitigate such cases by skipping the relevant packages during sync. |
Do you know what HCP uses for managing that repo? Might be worth escalating there? (A more resilient pulp-deb ia still a good thing) |
I do not know where I might report the upstream issue, though it would be good to do so. The number of oddities in that repo makes me think it might be something they built themselves... Perhaps just email them? |
Note: I alerted HashiCorp to our findings via the from found at: https://support.hashicorp.com/hc/en-us/requests/new |
Apparently the form I used is for paying enterprise customers only, so I also opened a thread in the HashiCorp community forum: https://discuss.hashicorp.com/t/buggy-weirdly-structured-hashicorp-apt-repo/34814 |
Minimal reproducer:
Error message:
The text was updated successfully, but these errors were encountered: