aptly
aptly copied to clipboard
aptly - Debian repository management tool
Hello, trying to make use of a publish API to update the package repository. In the function below, the first part works well: package is posted. But the update won't...
Hello, I'm writing aptly in Python recently. Is there anything I should pay attention to . This passage comes from the translation software, which may not be smooth
aptly version: 0.9.6 Steps to reproduce (all done through the api): 1. Create local repo + add .deb 2. Create snap1 from local repo 3. Publish snap1 to S3 4....
Today, I tried to add "python-cryptography" (from ubuntu bionic) to my aptly mirror filter (configured to pull dependencies). When I try to install this package, apt claims two dependencies as...
## Detailed Description Per the documentation [here](https://www.aptly.info/doc/feature/pgp-providers/), Aptly is only compatible with GPG v1. However, the dependencies for the packages ( [debian](https://packages.debian.org/bullseye/aptly), [ubuntu](https://packages.ubuntu.com/kinetic/aptly)) force installation of [gnupg](https://packages.debian.org/bullseye/gnupg) which is gpg...
## Detailed Description We have a strange issue that couldn't be resolved yet. I uploaded a new version of a package for 3 different plattforms (armhf, arm64, amd64) and wanted...
## Detailed Description When the `Content-Type` header is set to `application/json` on a mirror update via API (no matter if async or not), the API throws HTTP 400 and `{"error":"EOF"}`....
Change-Id: I054c5fc9b02f613601781de8613d684faa0ea7f2 Fixes # ## Requirements All new code should be covered with tests, documentation should be updated. CI should pass. ## Description of the Change ## Checklist - [x]...
Whenever I try to publish snapshot or publish switch, some of my snapshots give the following error message. `ERROR: unable to load package Pall 0ad-data 0.0.25b-1 94979ea1862b17fc: key not found`...
I've just been trying to work out why my package didn't show up even though it added fine and published. This was because my published repository was set to arm64...