-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Can't get old versions on Debian package registry with apt #27783
Comments
That's by design at the moment. Usually the debian package index contains only the latest available version and only that version is installable with apt. |
Is it currently necessary to create components for specific versions? |
That would be a workaround. I just used the latest package version then because the "big" repositories do the same. But we can list all package versions. |
Yes, I understand. It would be convenient for the component to select all versions or only the latest one. For example, for the "main" component have only the latest version, and for "dev" have all versions |
I will change it to list all versions. The Docker repository for example does that too https://download.docker.com/linux/debian/dists/bookworm/stable/binary-amd64/Packages . |
Thanks |
Added in #27786 |
Closes go-gitea#27783 This PR lists all and not only the latest package versions in the `Packages` index.
Closes go-gitea#27783 This PR lists all and not only the latest package versions in the `Packages` index.
Description
When I try to get an older version of a package I get an error. After checking all the packages in the repository, I noticed that only the latest packages of each package group are displayed.
Gitea Version
1.20.5 built with GNU Make 4.4.1, go1.20.8 : bindata, timetzdata, sqlite, sqlite_unlock_notify
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Git Version
2.40.1, Wire Protocol Version 2 Enabled
Operating System
Ubuntu 20.04
How are you running Gitea?
Docker version on Docker Hub with latest tag
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: