Skip to content

Percona packages should conflict with the OS (and PGDG) packages providing the same tool #641

@mohag

Description

@mohag

For Debian packages at least, when trying to install the PGDG versions of pgbouncer, patroni, pgbackrest and pgbadger (those were the ones that I tried to move, others might have similar issues), the install fails due to files that already exists in the Percona packages (this likely happens the other way around as well - moving from OS/PGDG packages to Percona package, I have not tested that yet though)

If the Debian packages are marked as conflicting APT would remove the packages from the other provider before attempting to install the packages.

It seems like marking the packages with Replaces and Breaks might also work. (A test env to build the packages to test in not trivial to get running)

(Background: I'm trying to install pg_cron, which is not packaged in the Percona repo and if I move the other packages to PDGD repo instead, the outbound access requirements for is slightly simpler)

(Keeping the packaged tools / extensions in sync with PGDG / Debian here might be the other option)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions