This bug was fixed in the package postgresql-9.5 -
9.5.16-0ubuntu0.16.04.1
---
postgresql-9.5 (9.5.16-0ubuntu0.16.04.1) xenial; urgency=medium
* New upstream release(s) (LP: #1815665)
- By default, panic instead of retrying after fsync() failure, to avoid
possible data
This bug was fixed in the package postgresql-10 - 10.7-0ubuntu0.18.04.1
---
postgresql-10 (10.7-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1815665)
- By default, panic instead of retrying after fsync() failure, to avoid
possible data corruption.
This bug was fixed in the package postgresql-10 - 10.7-0ubuntu0.18.10.1
---
postgresql-10 (10.7-0ubuntu0.18.10.1) cosmic; urgency=medium
* New upstream release (LP: #1815665)
- By default, panic instead of retrying after fsync() failure, to avoid
possible data corruption.
MP up at https://code.launchpad.net/~paelzer/britney/hints-ubuntu-
xenial-i386-libreoffice/+merge/365333
Since all tests are in I marked all releases verified
** Branch linked: lp:~paelzer/britney/hints-ubuntu-
xenial-i386-libreoffice
--
You received this bug notification because you are a
Oh it is rather trivial in the looong version string the suffix changed due to
another upload.
I'll provide an MP to bump that along this SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815665
Xenial also built and tested fine over the weekend.
There is a single test issue that I need to mention in libreoffice on i386 [1].
That seems to be a known issue [2] and I provided some further debug for it,
but in the SRU context for Xenial this should not be an issue as [3] should
mask the
** No longer affects: postgresql-plproxy (Ubuntu)
** No longer affects: postgresql-plproxy (Ubuntu Bionic)
** No longer affects: postgresql-plproxy (Ubuntu Cosmic)
** No longer affects: postgresql-rum (Ubuntu Cosmic)
** No longer affects: postgresql-rum (Ubuntu Bionic)
** No longer affects:
** No longer affects: postgresql-10 (Ubuntu)
** No longer affects: postgresql-9.5 (Ubuntu)
** No longer affects: skytools3 (Ubuntu Xenial)
** No longer affects: skytools3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
- Xenial ppc64el build complete now, tests will run over the weekend.
- The cosmic diaspora test succeeded on the re-run as expected, thereby all of
Cosmic is good as well
Marking B as verified, X has to wait a bit due to the build issue
causing a delay
** Tags removed:
I was checking the tests, and so far I found:
- Bionic all built and all tests good
- Cosmic all built and just one flake test in diaspora-installer (re-triggered
just now)
- Xenial didn't build on ppc64el (WTH it did in the PPAs two weeks ago)
This seems to be a locking issue in the builders -
Hello Christian, or anyone else affected,
Accepted postgresql-10 into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/postgresql-10/10.7-0ubuntu0.18.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Christian, or anyone else affected,
Accepted postgresql-9.5 into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/postgresql-9.5/9.5.16-0ubuntu0.16.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this
** Changed in: postgresql-11 (Ubuntu Disco)
Status: Confirmed => Fix Released
--
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
This bug was fixed in the package pglogical-ticker - 1.3.1-1ubuntu1
---
pglogical-ticker (1.3.1-1ubuntu1) disco; urgency=medium
* d/p/fix-test-error-11.2.patch: Fix test issue with
postgresql 11.2 (LP: #1815665)
-- Christian Ehrhardt Mon, 11 Mar
2019 13:32:27 +0100
**
Fixes for pglogical-ticker identified and started to be upstreamed at [1]
This was proven to work well at [2] and therefore is now uploaded to Disco at
[3] hopefully unblocking 11.2 in Disco-proposed.
[1]: https://github.com/enova/pglogical_ticker/pull/6
[2]:
$ debdiff postgresql-10_10.*dsc | filterdiff -x '**/doc/**' -x '**/*.po' -x
'**/src/test/**' -x '**/*.m4' | wc -l
31806
$
That's rather substantial, and a bit frightening for an MRE without any
further references to upstream testing. Why is this going via
-proposed, vs the security team's
pglogical-ticker is a test that blocks things in Disco atm, we need to
resolve that before release
--
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,
Due to the reverts this is much less disruptive, plenty of bug tasks got
invalid.
As 11.2 gets the change postgresql-rum in Disco is affected, but that is
already in 1.3.2-4 which is in Disco.
** Changed in: postgresql-rum (Ubuntu)
Status: New => Fix Released
** Changed in:
After adapting the description for the new insights I uploaded the two
10.7 branches (Bionic/Cosmic) to the unapproved queue as well (9.5 for
Xenial was there already).
** Changed in: postgresql-10 (Ubuntu Cosmic)
Status: Triaged => In Progress
** Changed in: postgresql-10 (Ubuntu Bionic)
** 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
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
I have updated the bug description accordingly to cover and explain,
I'll re-add it to the MPs and open them up for a sanity check.
--
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
While 10.7 needs more work for the work with the extensions in regard to
the rb/rbt renaming 9.5 for Xenial is ready - uploaded 9.5.16 to Xenial-
unapproved
** Changed in: postgresql-9.5 (Ubuntu Xenial)
Status: Triaged => In Progress
--
You received this bug notification because you are
** 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
While we will discuss with the SRU Team which way (revert or break) we as
Ubuntu want to go I analyzed the test results with the reverts as they are in
the MPs.
This shall ensure that there are no more lingering errors.
Xenial [1]:
- bareos, orafce, pgfincore, pgpool2, postgresql-multicorn,
The error is due to this change [1]
While we could modify and rebuild postgresql-rum we don't know what else
people might have built against that which is not in the Archive.
This applies only to branches 11 (not yet released, so ok) and 10
(Bionic/Cosmic)
My suggestion would be to carry a
>From the test log:
== dropping database "contrib_regression" ==
DROP DATABASE
== creating database "contrib_regression" ==
NOTICE: database "contrib_regression" does not exist, skipping
CREATE DATABASE
ALTER DATABASE
#3 - pg-partman (i386) - local execution in autopkgtest and reruns on LP
confirmed this was just a flaky test and can be ignored.
#4 - postgresql-rum - local execution in autopkgtest confirmed this is
reproducibly linked to the new version in the PPA
Debugging this now (or after lunch) ...
--
Note: there are references to client_min_messages in bacula and bareos
as well, but those will just (correctly) get more verbose (if failing a
all).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://codesearch.debian.net/search?q=%5BSs%5D%5BEe%5D%5BTt%5D%5Cs*client_min_messages.*fatal
Not sure how I could search that way in a past release, but it gives some
confirming hits.
For our current case I can confirm the following issues being due to this:
- skytools3 (xenial, not in archive
The git tag is public now, make the bug public as well.
** Information type changed from Private to Public
--
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
31 matches
Mail list logo
