When preparing the changes I happened to realize that we got mislead by too
many open tabs and mails in our discussion. The change with a potential to
break data is [1] but not [2].
Therefore our discussion was misleading - for [1] there can be no comparable
solution for the "check for the symbol in the extensions" as the setting of
client_min_messages could be anywhere.
That said I'll switch back to my suggestion to revert of both:
- [1]: client_min_messages: users of Bionic/Cosmic are either
a) not affected at all and therefore are fine as-is (majority)
b) not affected by the problem but have tests/scripts/CI/... that relies on
the behavior (we
don't want to SRU break them)
b) have a case that is affected, in that case the "user" of
client_min_messages that is
considered broken should be changed.
Furthermore with that decision we are also in sync with Debian handling the
same
- [2]: rb/rbt: fine doing forward (Disco), but not Bionic/Cosmic not breaking
ABI of the past in
an SRU
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910
[2]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b2e754c14
** Description changed:
Current versions in supported releases:
postgresql-9.3 | 9.3.23-0ubuntu0.14.04 trusty <- no upstream updates anymore
postgresql-9.5 | 9.5.14-0ubuntu0.16.04 xenial
postgresql-10 | 10.6-0ubuntu0.18.04.1 bionic
postgresql-10 | 10.6-0ubuntu0.18.10.1 cosmic
Special cases:
- Disco will be synced from Debian soon (we are on 11.1-2)
- This is again a security update, so we prep and security will eval and
publish through -security
Last relevant related stable updates: 9.5.16, 10.7
So the todo is to pick:
MRE: Xenial 9.5.14 from
https://ftp.postgresql.org/pub/source/v9.5.16/postgresql-9.5.16.tar.gz
MRE: Bionic/Cosmic 10.7 from
https://ftp.postgresql.org/pub/source/v10.7/postgresql-10.7.tar.gz
Standing MRE - Consider last updates as template:
- pad.lv/1637236
- pad.lv/1664478
- pad.lv/1690730
- pad.lv/1713979
- pad.lv/1730661
- pad.lv/1747676
- pad.lv/1752271
- pad.lv/1786938
New - this bug
- pad.lv/1815665
As usual we test and prep from the PPA and then push through
SRU/Security as applicable.
Regression potential:
- - usually this works smoothly except a few test hickups that need to be
- clarified to be sure. But this time there are changes worth to
+ - usually this works smoothly except a few test hickups that need to be
+ clarified to be sure. But this time there are changes worth to
mention for the SRU team.
- - change [1] is in all branches and after coordinating with Debian and
- Upstream and some members of the SRU Team (Malta) we decided to revert
- this change in all releases that get SRUs (So 11.x in Disco is the
- only who will get it).
- - Furthermore [2] is only in the 10.x branch (Bionic/Cosmic) and will
- change the ABI. After discussion with upstream and the SRU Team we
- want to avoid that the ABI (for extensions) differes between diffrent
- 10.7 out in the wild. Therefore we will rework the affected extensions
- in the archive and try to scan for out of archive extensions before
- upgrading bailing out in preinst (That has to be proven to work
- reliably)
+ - change [1] is in all branches Xenil/Bionic/Cosmic and after
+ coordinating with Debian and Upstream and some members of the SRU Team
+ (Malta) and Debian we decided to revert this change in all releases
+ that get SRUs (So 11.x in Disco is the only who will get it).
+ Users are either:
+ a) not affected at all and therefore are fine as-is (majority)
+ b) not affected by the problem but have tests/scripts/CI/... that
+ rely on the behavior (we don't want to SRU break them)
+ c) have a case that is affected, in that case the "code using
+ client_min_messages" is the one to be considered broken (in favor
+ of the majority of users) and that code should be changed in stead
+ of postgres.
+ Furthermore with that decision we are also in sync with Debian
+ handling the same
+ - Change [2] renaming of symbols rb/rbt is fine doing forward (Disco),
+ but not in Bionic/Cosmic as we'd break en external ABI of the past in
+ an SRU
Note: opening private as it is not yet announced
Public announce will on thursday.
[1]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=c09daa910
[2]: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b2e754c14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815665
Title:
New upstream microreleases 9.5.16, 10.7 and 11.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pg-partman/+bug/1815665/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
