-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Deb repo inconsistent versions available #8166
Comments
This is a huge blocker right now as our infrastructure is designed to use apt to install Teleport. |
Recommended workaround, until we refactor the apt repositories: Do not use the repo, instead, download and install your prefered $ curl -O https://get.gravitational.com/teleport_7.3.3_amd64.deb
# snip ...
$ apt install ./teleport_7.3.3_amd64.deb
# snip ...
Setting up teleport (7.3.3) ...
$ teleport version
Teleport v7.3.3 git:v7.3.3-0-g47ccf9e5f go1.16.2 |
Got hit by this myself today. |
The debian repo is currently broken, and we shouldn't recommend customers use it until it is fixed. Contributes to #8166
With 8.0 released and a long term fix to #8166 outstanding, we do not want to publish 7.0 debs to deb.releases.teleport.dev until we've moved off reprepo.
With 7.0 released and a long term fix to #8166 outstanding, we do not want to publish 6.X debs to deb.releases.teleport.dev until we've moved off reprepo. (cherry picked from commit 377b1929633ca42e6b54914d3082198cace65bc6)
With 6.0 released and a long term fix to #8166 outstanding, we do not want to publish 5.0 debs to deb.releases.teleport.dev until we've moved off reprepo. (cherry picked from commit 377b1929633ca42e6b54914d3082198cace65bc6)
With 7.0 released and a long term fix to #8166 outstanding, we do not want to publish 6.X debs to deb.releases.teleport.dev until we've moved off reprepo. (cherry picked from commit 377b1929633ca42e6b54914d3082198cace65bc6)
With 8.0 released and a long term fix to #8166 outstanding, we do not want to publish 7.0 debs to deb.releases.teleport.dev until we've moved off reprepo.
With 6.0 released and a long term fix to #8166 outstanding, we do not want to publish 5.0 debs to deb.releases.teleport.dev until we've moved off reprepo. (cherry picked from commit 377b1929633ca42e6b54914d3082198cace65bc6)
This patch makes a couple changes: 1. deb archives are not published to apt if they're not the latest release ever 2. both rpm and deb archives are no longer published to yum / apt if they contain any pre-release indicator or build metadata 3. nothing is published if the commit isn't tagged. Contributes to #8166
This patch makes a couple changes: 1. deb archives are not published to apt if they're not the latest release ever 2. both rpm and deb archives are no longer published to yum / apt if they contain any pre-release indicator or build metadata 3. nothing is published if the commit isn't tagged. Contributes to #8166
This patch makes a couple changes: 1. deb archives are not published to apt if they're not the latest release ever 2. both rpm and deb archives are no longer published to yum / apt if they contain any pre-release indicator or build metadata 3. nothing is published if the commit isn't tagged. Contributes to #8166
This patch makes a couple changes: 1. deb archives are not published to apt if they're not the latest release ever 2. both rpm and deb archives are no longer published to yum / apt if they contain any pre-release indicator or build metadata 3. nothing is published if the commit isn't tagged. Contributes to #8166
This patch makes a couple changes: 1. deb archives are not published to apt if they're not the latest release ever 2. both rpm and deb archives are no longer published to yum / apt if they contain any pre-release indicator or build metadata 3. nothing is published if the commit isn't tagged. Contributes to #8166
This patch makes a couple changes: 1. deb archives are not published to apt if they're not the latest release ever 2. both rpm and deb archives are no longer published to yum / apt if they contain any pre-release indicator or build metadata 3. nothing is published if the commit isn't tagged. Contributes to #8166 (cherry picked from commit 8540533)
This patch makes a couple changes: 1. deb archives are not published to apt if they're not the latest release ever 2. both rpm and deb archives are no longer published to yum / apt if they contain any pre-release indicator or build metadata 3. nothing is published if the commit isn't tagged. Contributes to #8166 (cherry picked from commit 8540533)
This patch makes a couple changes: 1. deb archives are not published to apt if they're not the latest release ever 2. both rpm and deb archives are no longer published to yum / apt if they contain any pre-release indicator or build metadata 3. nothing is published if the commit isn't tagged. Contributes to #8166 (cherry picked from commit 8540533)
Current status: We're no longer seeing any regressions occuring (e.g. a teleport 7 in the repo after teleport 8 was already out) thanks to: However, we don't yet have a way to track a specific major or minor version in apt. The future of this work is being tracked in #9770. |
Description
It seems that with build infrastructure only one version is available at a time, and a build run modifies the version from 7.x to 6.x is back based on what last build has been run.
For example:
teleport 7.x back disappeared from
https://deb.releases.teleport.dev/ stable main
and now there is only 6.x thereThe text was updated successfully, but these errors were encountered: