This bug was fixed in the package pg-repack - 1.3.4-1ubuntu0.1
---
pg-repack (1.3.4-1ubuntu0.1) yakkety; urgency=medium
* Extend testcase to work with latest microrelease (LP: #1664478)
-- Christian Ehrhardt Wed, 15 Feb
2017 11:23:42 +0100
**
postgresql-9.6 has migrated out of zesty-proposed and postgresql-9.5 has
been removed from zesty.
** Changed in: postgresql-9.5 (Ubuntu Zesty)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you Brian,
I checked excuses and can confirm that the fix works getting the Test to work
with the new postgres MRE release.
E.g.
Also zesty has synced latest Debian which has my fix, so setting pg-
repack fixed in devel as well.
** Changed in: pg-repack (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello ChristianEhrhardt, or anyone else affected,
Accepted pg-repack into yakkety-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/pg-
repack/1.3.4-1ubuntu0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** Changed in: pg-repack (Debian)
Status: New => 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/1664478
Title:
New upstream microreleases 9.3.16, 9.5.6
To manage notifications
Also an ack from Debian and a release into Debian unstable.
Could one look into sponsoring fix-1664478-pg-repack-testcase.debdiff into
Yakkety (MOTU).
** Changed in: pg-repack (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of
FYI - Upstream PR for pg-repack got an ack.
https://github.com/reorg/pg_repack/pull/115
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Title:
New upstream microreleases 9.3.16, 9.5.6
To
This bug was fixed in the package postgresql-9.5 - 9.5.6-0ubuntu0.16.04
---
postgresql-9.5 (9.5.6-0ubuntu0.16.04) xenial; urgency=medium
* New upstream release (LP: #1664478)
- Fix a race condition that could cause indexes built with CREATE INDEX
CONCURRENTLY to be
This bug was fixed in the package postgresql-9.3 - 9.3.16-0ubuntu0.14.04
---
postgresql-9.3 (9.3.16-0ubuntu0.14.04) trusty; urgency=medium
* New upstream release (LP: #1664478)
- Fix a race condition that could cause indexes built with CREATE INDEX
CONCURRENTLY to be
This bug was fixed in the package postgresql-9.5 - 9.5.6-0ubuntu0.16.10
---
postgresql-9.5 (9.5.6-0ubuntu0.16.10) yakkety; urgency=medium
* New upstream release (LP: #1664478)
- Fix a race condition that could cause indexes built with CREATE INDEX
CONCURRENTLY to be
So with pg-repack understood and fix on its way (no need to block the
postgres transition on it) the only thing left is mimeo.
Mimeo fails only on armhf for a dependency issue by failing to set up newpid
correctly:
Setting up newpid (7) ...
Failed to set capabilities on file `/usr/bin/newpid'
** Changed in: pg-repack (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Title:
New upstream microreleases 9.3.16, 9.5.6
To manage notifications about
A few of the flaky tests show up as expected, and one that might need an extra
look at "mimeo" fails on arm due to newpid.
Nish and I will (re-)test some and if needed evaluate that and come back here
with a v-done after that.
--
You received this bug notification because you are a member of
** No longer affects: postgresql-9.3 (Ubuntu)
** Project changed: postgresql => ubuntu-translations
** Changed in: ubuntu-translations
Importance: Unknown => Undecided
** Changed in: ubuntu-translations
Remote watch: Debian Bug tracker #854997 => None
** No longer affects:
I published the packages from bileto and accepted them into -proposed.
Now let the distro CI do its spiel and please flip to v-done once the
tests are done.
** Changed in: postgresql-9.3 (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Changed in: postgresql-9.5 (Ubuntu Xenial)
Attaching debdiffs in cae copy from Bileto (or debdiff from there) won't
work
** Patch added: "postgres-MRE-1664478-Trusty.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pg-repack/+bug/1664478/+attachment/4819467/+files/postgres-MRE-1664478-Trusty.debdiff
--
You received this bug
I agree Martin - if ok with the SRU Team - there is no reason to block on the
tests.
Maybe we should also retrigger the Yakkety postfix tests to prove that they
recover and were just flaky as we assumed.
I pinged nacc to do so.
So the next steps will need at least someone with upload rights and
Attaching debdiffs in case copy from Bileto (or debdiff from there)
won't work
** Patch added: "postgres-MRE-1664478-Yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pg-repack/+bug/1664478/+attachment/4819472/+files/postgres-MRE-1664478-Yakkety.debdiff
--
You received this bug
Attaching debdiffs in case copy from Bileto (or debdiff from there)
won't work
** Patch added: "postgres-MRE-1664478-Xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/pg-repack/+bug/1664478/+attachment/4819471/+files/postgres-MRE-1664478-Xenial.debdiff
--
You received this bug
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Title:
New upstream microreleases 9.3.16, 9.5.6
To manage notifications about this bug go to:
FTR, I see no reason to block the update on the pg-repack issue as
that's a test suite bug only. Nice job tracking this down!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Title:
New
Giving things 24 hours to let Debian and/or upstream respond on the suggestion.
Preparing an SRU Teamplate for the pg-repack fix already.
@nacc / @pitti - let me know what you think on this finding and if we
should go this way.
--
You received this bug notification because you are a member of
Added a pg-repack task, this has to be fixed (SRU) for Yakkety before
the MRE for Yakkety will migrate.
It is only a test case failure (no real problem), so if the SRU Team
would consider it as is (and can bypass the failing dep8 test) we could
unblock the MRE and upload that now to proposed.
** Patch added: "pg-regress testcase fix (prereq for the MRE into Yakkety)"
https://bugs.launchpad.net/ubuntu/+source/pg-repack/+bug/1664478/+attachment/4819375/+files/fix-1664478-pg-repack-testcase.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I found the issue in pg-repack and suggested a fix upstream as well as
to Debian.
** Also affects: pg-repack (Ubuntu)
Importance: Undecided
Status: New
** Changed in: pg-repack (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of
Upstream PR https://github.com/reorg/pg_repack/pull/115
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Title:
New upstream microreleases 9.3.16, 9.5.6
To manage notifications about this bug
** Changed in: postgresql
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Title:
New upstream microreleases 9.3.16, 9.5.6
To manage notifications about this bug
Jeremy Bicha spotted that in debici 2 days ago and I chimed in there,
linking the Debian bug for what we see in the Yakkety case.
** Bug watch added: Debian Bug tracker #854997
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854997
** Also affects: postgresql via
No need to excuse, murphy is everywhere :-)
I'll debug as far as I get and call out to the pkg list then.
I already confirmed that Debian is also affected, so we might as well work
together on the solution. Yet I want to spend a bit time debugging myself to
close my skill gap in that regard
Oh, I forgot: This might very well be a bug in pg_repack's tests too of
course.
Weird/sorry that your first update causes such trouble.. :-/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Debdiffs LGTM. For the tests: postfix tests are a bit flaky. But the
pg_repack regression should be investigated more seriously, that doesn't
look like a flake at all (it also happened on all architectures):
2017-02-14 11:07:37 UTC [2371-1] ubuntu@contrib_regression ERROR: could not
create
** Changed in: postgresql-9.3 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Title:
New upstream microreleases 9.3.16, 9.5.6
To manage notifications
** No longer affects: postgresql-9.3 (Ubuntu Zesty)
** No longer affects: postgresql-9.3 (Ubuntu Yakkety)
** No longer affects: postgresql-9.3 (Ubuntu Xenial)
** No longer affects: postgresql-9.5 (Ubuntu Trusty)
** Changed in: postgresql-9.5 (Ubuntu Zesty)
Status: New => Incomplete
**
** Also affects: postgresql-9.3 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: postgresql-9.5 (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: postgresql-9.3 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects:
To easen referencing - the last update was tracked in bug 1637236
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Title:
New upstream microreleases 9.3.16, 9.5.6
To manage notifications
For Trusty I see https://bileto.ubuntu.com/excuses/2468/trusty.html
That is all completing, but postgresql-9.5/armhf.
Quoting Pitti fromt he last stable update "These are fallout from moving from
LXC to LXD. For devel I fixed the latter in
I realized that the diffs are also reachable via bileto as it generated
them, so no need to upload equivalent debdiffs unless requested.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Title:
Working build and autopkgtests can be found in the following Bileto tickets:
https://bileto.ubuntu.com/#/ticket/2468
https://bileto.ubuntu.com/#/ticket/2469
https://bileto.ubuntu.com/#/ticket/2470
I can't sponsor the uploads, maybe one of the SRU Team with the right
powers can just copy from
For Zesty things are more complex as we need to get the 9.6 release out of
proposed first.
But doing SRUs to released versions now in time to get users updated.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
:-/ I can't create ack/nack tasks for this myself, it should be
9.3 - Trusty
9.5 - Xenial
9.5 - Yakkety
9.5 - Zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1664478
Title:
New upstream
41 matches
Mail list logo