# Ubuntu xenial and impish have been removed from apt.postgresql.org and \`apt update\`s are failing for xenial based jobs

**URL:** <https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295>\
**Category:** Travis CI Discussions & Feedback\
**Created:** [September 19, 2022, 1:25pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295 "2022-09-19T13:25:47Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![IllicLanthresh](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/illiclanthresh/32/8245_2.png) [@IllicLanthresh](https://travis-ci.community/u/IllicLanthresh)\
**Post date:** [September 19, 2022, 1:25pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295/1 "2022-09-19T13:25:47Z")

</div>

As specified in [Apt - PostgreSQL wiki](https://wiki.postgresql.org/wiki/Apt#News)

Xenial was moved to [apt-archive.postgresql.org](http://apt-archive.postgresql.org) the 6th of July and a warning was issued that it would be removed by the end of August.

Today, 19th of September(way later than what it was warned), Xenial is no longer available in [apt.postgresql.org](http://apt.postgresql.org).

So whenever an `apt update` is executed, it fails not being able to fetch xenial binaries from [apt.postgresql.org](http://apt.postgresql.org).

I suggest changing [apt.postgresql.org](http://apt.postgresql.org) for [apt-archive.postgresql.org](http://apt-archive.postgresql.org) in Xenial to solve the issue.

---

<div class="post-metadata">

**Author:** ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)\
**Post date:** [September 19, 2022, 3:45pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295/2 "2022-09-19T15:45:28Z")

</div>

Thanks @IllicLanthresh,

We are aware of the issue and working on it.

---

<div class="post-metadata">

**Author:** ![denisahearn](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/denisahearn/32/8252_2.png) [@denisahearn](https://travis-ci.community/u/denisahearn)\
**Post date:** [September 19, 2022, 9:16pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295/3 "2022-09-19T21:16:34Z")

</div>

We are seeing an error that looks to be caused by this as well:

```auto
E: Package 'postgresql-server-dev-10' has no installation candidate
E: Unable to locate package postgresql-10-postgis-2.5
E: Couldn't find any package by glob 'postgresql-10-postgis-2.5'
E: Couldn't find any package by regex 'postgresql-10-postgis-2.5'
apt-get.diagnostics
apt-get install failed
The command "sudo -E apt-get -yq --no-install-suggests --no-install-recommends $(travis_apt_get_options) install postgresql-10 postgresql-client-10 postgresql-server-dev-10 postgresql-client-common postgresql-common postgresql-10-postgis-2.5" failed and exited with 100 during .

```

@Montana - Will your fix that you are working on automatically solve this issue for us or do we need to make a change to our `.travis.yml` to work around the issue? We’re trying to get some changes deployed to production but are currently blocked by this CI issue.

---

<div class="post-metadata">

**Author:** ![denisahearn](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/denisahearn/32/8252_2.png) [@denisahearn](https://travis-ci.community/u/denisahearn)\
**Post date:** [September 20, 2022, 4:34pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295/4 "2022-09-20T16:34:42Z")

</div>

@Montana My builds starting working again today (with no changes on my end). Did you make a change on your end that would explain why the builds are working again today?

---

<div class="post-metadata">

**Author:** ![palu3492](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/palu3492/32/8258_2.png) [@palu3492](https://travis-ci.community/u/palu3492)\
**Post date:** [September 20, 2022, 5:51pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295/5 "2022-09-20T17:51:41Z")

</div>

My builds are also working again today. @Montana Should we expect this to happen again in the future?

---

<div class="post-metadata">

**Author:** ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)\
**Post date:** [September 20, 2022, 5:58pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295/6 "2022-09-20T17:58:57Z")

</div>

Hey everybody,

Builds should resume as usual. Please don’t hesitate to post back here if there’s an issue. Keeping a close eye on it.

---

<div class="post-metadata">

**Author:** ![ProBeachBum](https://avatars.discourse-cdn.com/v4/letter/p/5e9695/32.png) [@ProBeachBum](https://travis-ci.community/u/ProBeachBum)\
**Post date:** [September 20, 2022, 6:18pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295/7 "2022-09-20T18:18:36Z")

</div>

Still having build issues. 😑

---

<div class="post-metadata">

**Author:** ![ivanperez-keera](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/ivanperez-keera/32/6843_2.png) [@ivanperez-keera](https://travis-ci.community/u/ivanperez-keera)\
**Post date:** [October 3, 2022, 1:33pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295/8 "2022-10-03T13:33:25Z")

</div>

Still having issues. See: [Travis CI - Test and Deploy with Confidence](https://app.travis-ci.com/github/ivanperez-keera/Yampa/builds/256238425)

For us, this is affecting specifically setups with `language: haskell` since we cannot select a `dist` other than `xenial` (apparently).

---

<div class="post-metadata">

**Author:** ![paulnicholson](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/paulnicholson/32/8294_2.png) [@paulnicholson](https://travis-ci.community/u/paulnicholson)\
**Post date:** [October 6, 2022, 9:17pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295/9 "2022-10-06T21:17:37Z")

</div>

Also having issues on xenial with `language: elixir`

---

<div class="post-metadata">

**Author:** ![Montana](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/montana/32/9566_2.png) [@Montana](https://travis-ci.community/u/Montana)\
**Post date:** [February 3, 2025, 6:08pm UTC](https://travis-ci.community/t/ubuntu-xenial-and-impish-have-been-removed-from-apt-postgresql-org-and-apt-update-s-are-failing-for-xenial-based-jobs/13295/10 "2025-02-03T18:08:11Z")

</div>

Hi all,

For the `elixir` problem, try a similar configuration I coded out:

```yaml
dist: focal  
language: haskell
ghc:
  - "8.0.2"
  - "8.2.2"
  - "8.4.4"
  - "8.6.5"
  - "8.8.3"
  - "8.10.1"

before_install:
  - travis_retry sudo apt-get update
  - travis_retry sudo apt-get install -y libcwiid-dev libsdl1.2-dev

install:
  - travis_retry cabal update
  - travis_retry cabal install --enable-tests -fexamples --only-dependencies yampa/ yampa-test/

script:
  - if [["${TRAVIS_HASKELL_VERSION}" == "8.4.4"]]; then 
        cabal install -ftest-doc-coverage --run-tests -j1 yampa/ yampa-test/; 
    else 
        cabal install --enable-tests -fexamples -j1 yampa/ yampa-test/; 
    fi

branches:
  only:
    - master
    - /^develop.*$/
    - /^hotfix.*$/
    - /^release.*$/

```

See if this is successful.
