Cannot install Citus in Ubuntu 24.04

[iopanda]

Hi team,

I got problem when I going to install Citus in Ubuntu 24.04. Here's the error:

$ curl https://install.citusdata.com/community/deb.sh | sudo bash
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  9887  100  9887    0     0  14487      0 --:--:-- --:--:-- --:--:-- 14497
Detected operating system as Ubuntu/noble.
Running apt-get update... done.
Checking for curl...
Detected curl...
Checking for gpg...
Detected gpg...
Checking for postgresql-16...
Detected postgresql-16...
Installing apt-transport-https... done.
Installing /etc/apt/sources.list.d/citusdata_community.list... done.
Importing Citus Data Community gpg key... done.
Running apt-get update... done.

The repository is set up! You can now install packages.

$ sudo apt update
Hit:1 http://jp.archive.ubuntu.com/ubuntu noble InRelease
Hit:2 http://security.ubuntu.com/ubuntu noble-security InRelease
Ign:3 https://repos.citusdata.com/community/ubuntu noble InRelease
Hit:4 http://jp.archive.ubuntu.com/ubuntu noble-updates InRelease
Err:5 https://repos.citusdata.com/community/ubuntu noble Release
  404  Not Found [IP: 3.166.228.122 443]
Hit:6 http://jp.archive.ubuntu.com/ubuntu noble-backports InRelease
Reading package lists... Done
E: The repository 'https://repos.citusdata.com/community/ubuntu noble Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

$ sudo apt-get -y install postgresql-16-citus-12.1
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package postgresql-16-citus-12.1
E: Couldn't find any package by glob 'postgresql-16-citus-12.1'
E: Couldn't find any package by regex 'postgresql-16-citus-12.1'

Does Ubuntu 24.04 not be supported yet?

[wissam-khair]

it is the same issue here citusdata/citus#4263

I couldn't open it again ... please we need support and help regarding this

[wissam-khair]

NOTE: not related only for ubuntu 24

[aggroot]

Please take care of this

[FellGleaming]

I too have this same issue ... looking at your package list, it appears you have Postgre16 packages for jammy and bionic, but not yet noble. Is this correct.?

[iopanda]

@FellGleaming

I think what you said is the root cause. They didn't upload packages for noble.
So as the solution, I edited the source file in /etc/apt/sources.list.d/citusdata_community.list, replace the noble with jammy. Then do execute apt update then install, then everything looks fine.

# this file was generated by packagecloud.io for
# the repository at https://repos.citusdata.com/community

#deb [signed-by=/etc/apt/keyrings/citusdata_community-archive-keyring.gpg] https://repos.citusdata.com/community/ubuntu/ noble main
deb [signed-by=/etc/apt/keyrings/citusdata_community-archive-keyring.gpg] https://repos.citusdata.com/community/ubuntu/ jammy main
#deb-src [signed-by=/etc/apt/keyrings/citusdata_community-archive-keyring.gpg] https://repos.citusdata.com/community/ubuntu/ noble main
deb-src [signed-by=/etc/apt/keyrings/citusdata_community-archive-keyring.gpg] https://repos.citusdata.com/community/ubuntu/ jammy main

I'm not sure whether this is recommended by official or not.

[simonramosb]

@FellGleaming @iopanda In my case it was that too!

So far, this is an active issue.

[iopanda]

@FellGleaming @iopanda In my case it was that too!

So far, this is an active issue.

Let me reopen it.

[hanefi]

I too have this same issue ... looking at your package list, it appears you have Postgre16 packages for jammy and bionic, but not yet noble. Is this correct.?

Yes, that is correct.

[matthewpull]

@hanefi thanks for the confirmation - do you know if there is any ballpark eta of when this might be added?

[FellGleaming]

@matthewpull, I used the suggested workaround by @iopanda successfully.

[matthewpull]

@FellGleaming it's an okay patch, but (as I understand it, happy to be corrected!) not great for production as it's based on the 22.04 image of Postgres, so would not contain any 24.04-specific content.

Now that's fine now, and will probably be fine in the future as well, but there is a chance that a bug or security issue occurs that only affects 24.04 (or some other combination of releases that doesn't include 22.04). Postgres could release a patch only for the 24.04 image, which users of @iopanda's helpful workaround would not see and so would be vulnerable.

That may seem like a remote possibility - and it probably is fairly unlikely - but for me at least I need to wait for something with stronger security guarantees.

Thank you for your comment though, and to @iopanda for sharing the workaround :)