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

mirror repository without Release file #237

Open
HerrBerg opened this issue Apr 10, 2015 · 8 comments · Fixed by #1308
Open

mirror repository without Release file #237

HerrBerg opened this issue Apr 10, 2015 · 8 comments · Fixed by #1308
Assignees

Comments

@HerrBerg
Copy link

I'd like to mirror the debian repository of sonarqube.
With

deb http://downloads.sourceforge.net/project/sonar-pkg/deb binary/

in sources.list apt-get update works fine.

creating a mirror with aptly (v0.9.5) using the command

aptly mirror create -ignore-signatures=true mirror-sonarqube http://downloads.sourceforge.net/project/sonar-pkg/deb binary/

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?

@smira
Copy link
Contributor

smira commented Apr 10, 2015

There has already been some issue around that... this is for flat Debian repositories without Relese. Probably this should be fixed.

@smira smira added the feature label Apr 10, 2015
@smira smira added this to the v0.9.6 milestone Apr 10, 2015
@smira smira modified the milestones: v0.9.6, v0.9.7 Jan 24, 2016
@smira smira modified the milestones: v0.9.7, v0.9.8 Apr 18, 2016
@ffrank
Copy link

ffrank commented Aug 11, 2016

I believe that this is addressed by #434.

@smira smira removed this from the v0.9.8 milestone Mar 27, 2017
@lbolla lbolla closed this as completed Jan 28, 2022
@lbolla lbolla reopened this Jan 28, 2022
@Kepler-Br
Copy link

It's been a long time since initial discussion, but the problem seems to persist
In my case I'm trying to mirror https://nvidia.github.io/nvidia-docker/ubuntu18.04/amd64
My command is

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 ./

@tplueer
Copy link

tplueer commented Jun 27, 2024

I'm having the same issue, for example with:
https://artifacts.opensearch.org/releases/bundle/opensearch/2.x
or
https://apt.grafana.com/

Is there any workaround until this gets implemented?

@neolynx
Copy link
Member

neolynx commented Jul 2, 2024

Hi and thanks for reporting !

Unfortunately no, there is no workaround, the implementation is still broken a bit :(
But I started working on a fix: #1308 :)

@neolynx
Copy link
Member

neolynx commented Jul 3, 2024

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

curl -fsSL https://artifacts.opensearch.org/publickeys/opensearch.pgp | gpg --import --no-default-keyring --keyring=trustedkeys.gpg
aptly mirror create opensearch https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/apt stable

grafana

curl -fsSL https://apt.grafana.com/gpg.key | gpg --import --no-default-keyring --keyring=trustedkeys.gpg
aptly mirror create grafana https://apt.grafana.com stable

@neolynx neolynx reopened this Jul 3, 2024
@tplueer
Copy link

tplueer commented Jul 5, 2024

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 Distribution which needed to be set to stable, that resulted in the following errors, so I thought that just the Release file was missing ...

Error #01: unable to fetch mirror: HTTP code 404 while fetching https://apt.grafana.com/Release
Error #01: unable to fetch mirror: HTTP code 403 while fetching https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/apt/Release

Thanks for your help though!

@neolynx
Copy link
Member

neolynx commented Jul 5, 2024

so, did it work now, with signature verification ?

if you need to not verify the signatures that will require the latest nightly build...

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

Successfully merging a pull request may close this issue.

8 participants
@lbolla @smira @ffrank @neolynx @HerrBerg @tplueer @Kepler-Br and others