Arch package registry: client error when two versions of a package are present

[balki]

Description

When a new version of a package is added, the database includes both old and new versions. This confuses pacman client.

error: <repo> database is inconsistent: version mismatch on package <package name>

The default core and extra repos include only the latest version of each package.

Gitea Version

1.23.3

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

archlinux

Database

PostgreSQL

[balki]

@KN4CK3R Please take a look.

[wxiaoguang]

Only show the latest version in the Arch index #33262 ?

[ExplodingDragon]

Seems like this is an upstream issue with pacman. If there are two different versions of a package in the database, it might trigger this problem. I guess?

[wxiaoguang]

Seems like this is an upstream issue with pacman. If there are two different versions of a package in the database, it might trigger this problem. I guess?

Or maybe pacman is just designed that way: it expects the package database should only have one version?

[balki]

Seems like this is an upstream issue with pacman.

I think it is by design. In each db, only one version of the packages is supposed to be present. libalpm is the official library to work with databases. The function signature below to get a package does not have version parameter. https://man.archlinux.org/man/libalpm_databases.3.en

alpm_pkg_t * alpm_db_get_pkg (alpm_db_t * db, const char * name)

Different versions can be in different databases. E.g. testing can have newest version and core can have current version. But within one database, only one version is expected.

when there is a need to have both older and newer version at the same time, the package name is changed. E.g. postgresql and postgresql-old-upgrade