Score:0

Package remains upgradable after upgrade

cn flag

Running apt list --upgradable on an Ubuntu 20.04.03 system yields

Listing... Done
timescaledb-2-postgresql-13/focal 2.4.2~ubuntu20.04 amd64 [upgradable from: 2.4.2~ubuntu20.04]
N: There are 4 additional versions. Please use the '-a' switch to see them.

Running apt upgrade installs the package without any problem but afterwards apt list --upgradable still lists the same package as upgradable. I suspect that the problem might be that the installed version has the same version specification:

Unpacking timescaledb-2-postgresql-13 (2.4.2~ubuntu20.04) over (2.4.2~ubuntu20.04) ...
                                       ^^^^^^^^^^^^^^^^^        ^^^^^^^^^^^^^^^^^

Is there a way to make the package manager understand that the package has been properly installed?

Note that unintalling and then reinstalling the package does not fix the problem.

Update: The output of apt policy timescaledb-2-postgresql-13 is

timescaledb-2-postgresql-13:
  Installed: 2.4.2~ubuntu20.04
  Candidate: 2.4.2~ubuntu20.04
  Version table:
     2.4.2~ubuntu20.04 500
        500 https://packagecloud.io/timescale/timescaledb/ubuntu focal/main amd64 Packages
 *** 2.4.2~ubuntu20.04 100
        100 /var/lib/dpkg/status
     2.4.1~ubuntu20.04 500
        500 https://packagecloud.io/timescale/timescaledb/ubuntu focal/main amd64 Packages
     2.4.0~ubuntu20.04 500
        500 https://packagecloud.io/timescale/timescaledb/ubuntu focal/main amd64 Packages
     2.3.1~ubuntu20.04 500
        500 https://packagecloud.io/timescale/timescaledb/ubuntu focal/main amd64 Packages

Update 2: The "problematic package" has the following origin:

deb https://packagecloud.io/timescale/timescaledb/ubuntu/ focal main

Update 3: apt upgrade timescaledb-2-postgresql-13 yields the following output.

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  timescaledb-2-postgresql-13
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1.183 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
(Reading database ... XXX files and directories currently installed.)
Preparing to unpack .../timescaledb-2-postgresql-13_2.4.2~ubuntu20.04_amd64.deb ...
Unpacking timescaledb-2-postgresql-13 (2.4.2~ubuntu20.04) over (2.4.2~ubuntu20.04) ...
Setting up timescaledb-2-postgresql-13 (2.4.2~ubuntu20.04) ...
RECOMMENDED: Run 'timescaledb-tune' (installed as part of the 
timescaledb-tools package, a recommended dependency) to update your 
config settings for TimescaleDB: 

  timescaledb-tune --quiet --yes

IF NOT, you need to update your postgresql.conf file to load TimescaleDB
by adding 'timescaledb' to your shared_preload_libraries.
Find the line below and change the value as shown (uncomment if needed):

shared_preload_libraries = 'timescaledb'
Processing triggers for postgresql-common (231.pgdg20.04+1) ...
Building PostgreSQL dictionaries from installed myspell/hunspell packages...
  en_au
  en_ca
  en_gb
  en_us
  en_za
Removing obsolete dictionary files:
Organic Marble avatar
us flag
can we see the output of `apt policy [packagename]` please?
cn flag
@OrganicMarble: I added the output.
Organic Marble avatar
us flag
Thanks for the edit. That shows the problem for sure, but unfortunately I've never seen an output like that! Usually you'll see the same package listed a few times from the different sources with the '100' version last, and the '****' on the first one. I wonder why it thinks the 2 versions are different??
galexite avatar
pk flag
Have you added any additional repositories? What repositories are displayed in the Software & Updates app?
cn flag
@OrganicMarble: Thanks for your observation. I hope that someone can point to an explanation of how such a state can be reached and how the issue can be resolved. galexite: I updated the post and added the repository.
nobody avatar
gh flag
What gives `sudo apt upgrade package name ` sorry I am on mobile.
cn flag
@nobody: I added the resp. output as well.
nobody avatar
gh flag
Okay did `apt-cache policy package ` change?
cn flag
@nobody: No, the output did not change.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.