nwei
February 22nd, 2018, 11:57 PM
Hi! We have been hosting our own Debian repository for some time now. When `apt` was recently upgraded to `v1.2.25`, `apt update` is no longer able to find the `Release` file in our deb repo. We get the following ignore messages:
Ign:6 http://packages.cloudfoundry.org/debian stable Release
Ign:8 http://packages.cloudfoundry.org/debian stable/main all Packages
we expect to get (which we see on apt v1.2.15, v1.2.24, and v1.5.x):
Get:6 https://cf-cli-debian-repo.s3.amazonaws.com stable Release [1797 B]
Get:7 https://cf-cli-debian-repo.s3.amazonaws.com stable Release.gpg [819 B]
The URLs above are redirects to where these assets actually live.
We verified that:
1. where we host these static assets are working as expected
2. our redirect app is working as expected
When we used other versions of `apt` (v1.2.15ubuntu0.2 (https://launchpad.net/ubuntu/+source/apt/1.2.15ubuntu0.2), , v1.2.24, and v1.5.x), the `apt update` works and is able to get the contents of the Release file.
We have a support ticket open for this which includes reproduction steps: https://github.com/cloudfoundry/cli/issues/1327
Ign:6 http://packages.cloudfoundry.org/debian stable Release
Ign:8 http://packages.cloudfoundry.org/debian stable/main all Packages
we expect to get (which we see on apt v1.2.15, v1.2.24, and v1.5.x):
Get:6 https://cf-cli-debian-repo.s3.amazonaws.com stable Release [1797 B]
Get:7 https://cf-cli-debian-repo.s3.amazonaws.com stable Release.gpg [819 B]
The URLs above are redirects to where these assets actually live.
We verified that:
1. where we host these static assets are working as expected
2. our redirect app is working as expected
When we used other versions of `apt` (v1.2.15ubuntu0.2 (https://launchpad.net/ubuntu/+source/apt/1.2.15ubuntu0.2), , v1.2.24, and v1.5.x), the `apt update` works and is able to get the contents of the Release file.
We have a support ticket open for this which includes reproduction steps: https://github.com/cloudfoundry/cli/issues/1327