I agree - the postgresql-common should not be touched, nor there is a need to create an SRU for it.
However, resource-agents should be fixed, and only for Xenial and Bionic. But, I felt it was 'cleaner' to do it in a separate bug, LP: #1762492.
For resource-agents part, I'm not sure if it should be completely removed from this bug, or just marked 'Invalid'. That part is actually duplicate of LP: #1762492. Unless you have objections I'll continue resource-agents part there.
P.S. You are correct, the postgresql-common patch was never applied here - I just created a debdiff, waiting for upstream patch to be applied, thinking that the proper way to solve this issue was fixing postsgresql-common.
So, to make it clear - postgresql-common is not to be fixed (there is nothing to be fixed), and this bug should be abandoned (as Debian did). resource-agents needs to be fixed, and that's being worked on in LP: #1762492. Is that good?
I agree - the postgresql-common should not be touched, nor there is a need to create an SRU for it.
However, resource-agents should be fixed, and only for Xenial and Bionic. But, I felt it was 'cleaner' to do it in a separate bug, LP: #1762492.
So, this bug should be marked "Won'f Fix" for postgresql-common (again, based on what Cristoph said in https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 890427# 10).
For resource-agents part, I'm not sure if it should be completely removed from this bug, or just marked 'Invalid'. That part is actually duplicate of LP: #1762492. Unless you have objections I'll continue resource-agents part there.
P.S. You are correct, the postgresql-common patch was never applied here - I just created a debdiff, waiting for upstream patch to be applied, thinking that the proper way to solve this issue was fixing postsgresql-common.
So, to make it clear - postgresql-common is not to be fixed (there is nothing to be fixed), and this bug should be abandoned (as Debian did). resource-agents needs to be fixed, and that's being worked on in LP: #1762492. Is that good?