Posts made by Sigve.opedal_6476

Upgraded to version 25.0.15, and it's working. Thanks.

Hi @stevedennis

Today I upgraded proget to v 25.0.14, and unfortunately the problem is the same. I can only find packages that are cached

Edit: This seems to be the case for other feeds as well, for example rpm feed for epel

Hello.

I have multiple rpm feeds set up (postgres, docker-ce, zabbix), and it seems to be working fine. But the rpm feeds for Rocky Linux BaseOS, Appsteam and Extras does not seem to work.

As an example, my feed for BaseOS looks like this:

(I've tried multiple urls as connector and same result)

My repo file looks like this:

I can search- and find for example nano directly in Proget:

However, on a client I cannot find the nano package:

However, if I download the nano package to my PC through the proget web interface so that it is cached on the proget server, I also find it on the clients:

Hello again @atripp
Just wanted to let you know that I figured out why the gpg key didn't work. It was just a case of me not being to familiar with proget, so I used the wrong url.

I right-clicked the file in the asset, and just copied the url instead of cliking on the file and copy the url from the "Usage instructions" portion. After fixing the url's, the gpg verification now works and I can hav gpgcheck = 1 in my repos and pointing the gpg url to the key in an asset.

It is some manual work to be done downloading and uploading gpg keys, but it works

Hi @atripp

I have already tried to make an asset and then download gpg keys to my machine and upload to the asset and then use the url for the gpg key in the asset. I doesn't work, I don't know why.

But I know the same gpkey works in our old solution, which just mirrors the entire remote repository to a local server with rsync.

When I tried Sonatype, I also got it to work, but I don't remember exactly how.

Sorry. Maybe I was a bit unclear. I guess my question is: Is it possible to host gpg keys through proget so that we can have gpgcheck enabled?

For example, the docker ce repo looks like this straight from docker.com:

[docker-ce-stable]
name=Docker CE Stable - $basearch
baseurl=https://download.docker.com/linux/rhel/$releasever/$basearch/stable
enabled=1
gpgcheck=1
gpgkey=https://download.docker.com/linux/rhel/gpg

Is there a way to replace the gpgkey url with

gpgkey=https://myproget.mycompany.com/gpg/docker/gpg

The gpgkeys are not included in a rpm feed through proget, since the feeds have to point to the repodata/ folder in the public repository.

Hello. Is there a way to have gpgcheck enabled in rpm feeds? The servers using the rpm feeds from our proget server does not have access to the internet, so they cannot download the gpg keys from the public repositories. So to have an own "feed" for gpg keys would be nice. I've tried to create an asset for gpg keys, but manually downloading and uploading gpg keys does not work, probably because the timestamp on the keys change.
Keys from our old repo server which has been synced from public repos using rsync to a local server works.