[Remove] Please remove postgresql-11 from Focal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cstore-fdw (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
pg-fact-loader (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
pgl-ddl-deploy (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
pglogical (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
pglogical-ticker (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
postgresql-11 (Debian) |
Fix Released
|
Unknown
|
|||
postgresql-11 (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Hi,
together with Debian we want to get rid of Postgresql-11 in future versions.
Currently most importantly in 20.04 before Feature Freeze.
This isn't as clean as we'd have liked it but let me summarize the current case.
Most of the dependencies to postgresql-* are superseded by the new version.
For example `libpq5`, `libpq-dev' and `libecpg6` which make the bulk of the remaining dependencies are provided by src:postgresql-12 now.
What is left is one "context" of packages:
$ reverse-depends -r focal src:postgresql-11 | grep "for postgresql-11"
* postgresql-
* postgresql-
* postgresql-
* postgresql-
* there also is pglogical-ticker which doesn't show up here, but depends on it ?!
They seem mostly neglected by upstream:
- postgresql-
- postgresql-
- postgresql-
Due to that the removal will have to hit not only src:postgresql-11 but also these packages as they don't get updated as needed to move to postgresql-12. Surely if they react in time before 20.04 release we can try to ship them, but not as-is.
This already happened in Debian via: https:/
Due to the above this request here is to remove the following from Ubuntu 20.04 (Focal):
- src:postgresql-11
- src:cstore-fdw
- src:pglogical
- src:pglogical-
- src:pg-fact-loader
- src:pgl-ddl-deploy
=> and all binaries formerly built by them
Changed in postgresql-11 (Debian): | |
status: | Unknown → Fix Released |
Filed to be ready, once wal2json has completed I'll recheck if the other projects responded at all and then we can decide to mark this removal request "active" and subscribe archive admins.