-
-
Notifications
You must be signed in to change notification settings - Fork 369
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
mirror repository without Release file #237
Comments
There has already been some issue around that... this is for flat Debian repositories without Relese. Probably this should be fixed. |
I believe that this is addressed by #434. |
It's been a long time since initial discussion, but the problem seems to persist aptly -config=/app/aptly.json -keyring=/app/trustedkeys.gpg -architectures="amd64" --with-sources mirror create nvidia-docker-ubuntu18.04-amd64 https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64 ./ |
I'm having the same issue, for example with: Is there any workaround until this gets implemented? |
Hi and thanks for reporting ! Unfortunately no, there is no workaround, the implementation is still broken a bit :( |
A fix was merged to master, could you give it a try ? on a side note, both repos are actually signed, and it is highly recommended to verify signatures, which can be done as follows: opensearch
grafana
|
Hi, it looks like the root cause of my problem was somewhere else. After I created the mirrors with your commands, it worked with aptly 1.5.0 I was using the aptly API to create the mirrors and I think missed the
Thanks for your help though! |
so, did it work now, with signature verification ? if you need to not verify the signatures that will require the latest nightly build... |
I'd like to mirror the debian repository of sonarqube.
With
in sources.list
apt-get update
works fine.creating a mirror with aptly (v0.9.5) using the command
results in an error of receiving the
Release
file which indeed is not available in this repository.Is there a way to work around this issue?
The text was updated successfully, but these errors were encountered: