Hey @mcascone, my previous comment was slightly incorrect - my testing showed that ProGet requires the first file in a Debian package to be debian-binary (see this commit I made in a project a while back).

It looks like you're able to verify such is the case on a Debian archive by running the following on a Linux system:

ar tf name-of-package.deb

And the first line in the output should be debian-binary.

I know this is an old issue (no clue if it's still relevant), but I experienced this issue with a program I was working on a while back and I thought I'd post the fix I had here:

If I recall correctly, ProGet thinks a deb is invalid when the first file in a .deb archive isn't control.tar.gz, or something like that. The main thing I remember is that I had to ensure files got added into the .deb archive in the correct order for ProGet to recognize it, and I'm assuming cargo-deb isn't doing that part correctly.

I'm pretty sure it's just due to Microsoft SQL's CLI cutting off the XML output @atripp, as the XML object would just be unfinished when viewing in my terminal.

I'm gonna whip together a quick CLI to try to pull it out programmatically later today, and then I can let you know if it all works. I'm quite confident that's what's been causing my issue though.

I'm not sure how much it'll help, but this is the specific error I get from GPG:

gpg: read_block: read error: Invalid packet
gpg: import from '/dev/stdin' failed: Invalid keyring

After some further looking it appears that the XML entries in FeedConfiguration_Xml just stop without a closing quote/bracket as well, are they supposed to?

I confirmed non of the environment variables were set @atripp, but after getting the GPG key running echo '{gpg_key}' | base64 -d | gpg --show-keys /dev/stdin is complaining about it being an invalid key.

Is the GPG key in that part of the database just in some weird format or something?

@stevedennis: I'm running ProGet through the Docker images, do you know where I could fine the config in that? I haven't been able to find it anywhere inside of my container.

Do you know where I can find the configuration file @atripp?

You mentioned that code to run too, but where should I put it if I want to run it? Is it like an extension I put in ProGet, or is it something I'd run manually on a command line?

It didn't look like there was anything in the UI to get the key out of my instance, so I started looking around in the database to see if I could find anything:

I found the Feeds table which looked like it might contain the key in the SecretKeys field, but GPG isn't recognizing that as valid key if I put it into a file.

Is there something I'm missing? I'm more than glad to do whatever I need to from the database manually if this isn't something that could be added to the UI in the near future.

I've got an APT repository on ProGet that uses a GPG key to sign the repository, but I'm needing to get the private key because I need to do some stuff with it locally.

Where can I find the GPG key at? Looking through ProGet's data directory (on a Docker setup) isn't showing any GPG files.

Hi! I wasn't sure where I could really post about this, but I thought I'd send a message here in case it was of interest to anyone:

I've made a CLI tool for ProGet, which internally is using the ProGet API. The tool can't do much right now - it can currently report status information of a server and upload .deb packages (it was a personal need).

I'm wanting to add more features, but for anyone that would enjoy using the tool, I'm wanting to know if they have any specific things they'd like added.

If there's any feedback that y'all would have, feel free to leave it in the GitHub repo :)