This bug was fixed in the package postgresql-common - 154ubuntu1
---
postgresql-common (154ubuntu1) trusty-proposed; urgency=medium
* debian/maintscripts-functions: Avoid package installation failure of -9.1
due to the pg_basebackup.1 alternative on systems which have both -9.1
I ran the test case with version 154 from trusty and get the failure. I
re-ran it with 154ubuntu1 from trusty-proposed and both -9.1 and -9.4
now succeed. This is self-verification, but as nobody else verified this
in the past 50 days and the next point release will come at some point,
let's get
** Tags removed: verification-failed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1357682
Title:
package postgresql-client-9.3 9.3.5-0ubuntu0.14.04.1 failed to
upgrade:
I triaged bug 1431253 (it's invalid).
** Tags removed: verification-failed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1357682
Title:
package postgresql-client-9.3
It's bug 1428738 that needed to be tagged.
** Tags removed: bot-stop-nagging
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1357682
Title:
package postgresql-client-9.3
While bug 1428738 is a bug, it's not a regression, this part of the code
hasn't changed in ages. It's mostly the act of restarting postgresql
which exhibits this, which usually happens on package upgrades.
** Tags removed: verification-failed
** Tags added: bot-stop-nagging
--
You received this
** Branch linked: lp:ubuntu/trusty-proposed/postgresql-common
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1357682
Title:
package postgresql-client-9.3
Hello Michael, or anyone else affected,
Accepted postgresql-common into trusty-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/postgresql-
common/154ubuntu1 in a few hours, and then in the -proposed repository.
Please help us by testing this new
** Branch linked: lp:ubuntu/vivid-proposed/postgresql-common
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1357682
Title:
package postgresql-client-9.3
This bug was fixed in the package postgresql-common - 166bzr1
---
postgresql-common (166bzr1) vivid; urgency=medium
[ Christoph Berg ]
* pg_conftool: Fix 'remove' operation. Spotted by François Henry, merci!
(Closes: #778243)
* t/007_pg_conftool.t: Add pg_conftool tests.
** Description changed:
Error while do-release-upgrade from 12.04 to 14.04
+
+
+ SRU TEST CASE:
+ # Run these commands in a precise schroot:
+ apt-get install -y postgresql-9.1
+ echo 'deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main'
/etc/apt/sources.list.d/pgdg.list
+
** Also affects: postgresql-common (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: postgresql-common (Ubuntu Vivid)
Importance: High
Assignee: Martin Pitt (pitti)
Status: In Progress
** Also affects: postgresql-common (Ubuntu Precise)
Importance:
This actually doesn't affect precise's postgresql-common itself. Newer
(i. e. backported) postgresql-X.Y versions also require a backported
postgresql-common, so instead this fix needs to land in vivid,
apt.postgresql.org, and whichever other backport sources people use.
I'll update
Trusty SRU uploaded.
** Changed in: postgresql-common (Ubuntu Trusty)
Status: New = In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to postgresql-common in Ubuntu.
https://bugs.launchpad.net/bugs/1357682
Title:
We just had such a case in our data center on precise. That has a
backported postgresql-common 154 installed, postgresql-9.1 from precise,
and a backported p-9.3. Upgrading 9.3 after 9.1 works ok, as p-common's
_link_manpages() takes care of the transition in that direction. But
upgrading 9.1
This is very similar to bug 1270597, apparently the fix there still was
not sufficient.
** Summary changed:
- package postgresql-client-9.3 9.3.5-0ubuntu0.14.04.1 failed to
install/upgrade: ErrorMessage: Unterprozess installiertes
post-installation-Skript gab den Fehlerwert 2 zurück
+ package
16 matches
Mail list logo
