This bug was fixed in the package postgresql-8.4 - 8.4.14-0ubuntu12.04.2
---
postgresql-8.4 (8.4.14-0ubuntu12.04.2) precise-proposed; urgency=low
* debian/postgresql-8.4.preinst: Drop check for existing
/etc/init.d/postgresql-common, as this depends on the unpack order.
Looks good. Thanks All!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058218
Title:
do-release-upgrade (lucid-precise)
Hello David, or anyone else affected,
Accepted into precise-proposed. The package will build now and be
available in a few hours in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use
The verification of this Stable Release Update has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression
This bug was fixed in the package postgresql-8.4 - 8.4.14-0ubuntu12.04.1
---
postgresql-8.4 (8.4.14-0ubuntu12.04.1) precise-proposed; urgency=low
* debian/postgresql-8.4.preinst: Do not only clean up the old -8.4 specific
init script when upgrading from 8.4.4-2, as we have
Thanks Scott! I'm reopening this for the remaining issue that 8.4 isn't
running after the upgrade without a reboot, and the old init.d file is
still around. I already uploaded a fix for this last week, but I
reuploaded it now to not include the previous changelog entries any more
as these are in
Oh, I see; the fix in .1 is depending on the unpack order, that's why I
didn't see it. I have prepared a more robust fix, testing now. Answer to
comment 18 still appreciated to verify that we are indeed seeing the
same. Also, if it starts after a reboot, I'd really like to get the
current version
I uploaded postgresql-8.4 8.4.14-0ubuntu12.04.2 to the precise-proposed
queue which fixes this harder. In a test upgrade, I now get a running
8.4 cluster straight after the upgrade.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Martin -- Yes, after a reboot, 8.4 is running.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058218
Title:
do-release-upgrade (lucid-precise) leaves postgres 8.4 in bad state
To manage
root@ubuntu:~# ls -l /etc/init.d/postgres*
-rwxr-xr-x 1 root root 1095 Sep 6 12:53 /etc/init.d/postgresql
-rwxr-xr-x 1 root root 1027 Sep 27 05:46 /etc/init.d/postgresql-8.4
root@ubuntu:~# pg_lsclusters
Version Cluster Port Status OwnerData directory Log
file
David, thanks for testing. Can you please give me the output of
ls -l /etc/init.d/postgres*
pg_lsclusters
Does the 8.4 cluster start after a reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bad news, after the upgrade, postgres-8.4 is still not running:
root@ubuntu:~# /etc/init.d/postgresql-8.4 status
Running clusters:
root@ubuntu:~#
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached files from upgrade attempt with 8.4.14-0ubuntu12.04.1
** Attachment added: dist-upgrade.tar.gz
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1058218/+attachment/3393646/+files/dist-upgrade.tar.gz
--
You received this bug notification because you are a member of
I ran the p-common test suite against 8.4.14-0ubuntu12.04.1 in precise-
proposed, no regressions. I'll let David re-verify the upgrade, as I
don't want to validate my own fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In lucid, postgresql-8.4 still had its own init script
/etc/init.d/postgresql-8.4, but on upgrades to precise this is replaced
with /etc/init.d/postgresql by postgresql-common. Do you still have an
/etc/init.d/postgresql-8.4 after the upgrade? It's presence would
explain why /etc/init.d/postgresql
Ah, I see the problem: postgresql-8.4.preinst only removes the old init
script when upgrading from 8.4.4-2 or earlier, but we have had new
upstream versions in lucid since then. So the migration code needs to be
updated.
--
You received this bug notification because you are a member of Ubuntu
I uploaded a fix for this to the precise-proposed queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058218
Title:
do-release-upgrade (lucid-precise) leaves postgres 8.4 in bad state
To manage
Hi Martin --
I'm still seeing an anomoly in the upgrade. After do-release upgrade,
postgres-8.4 is no longer running. I see at the beginning of the
upgrade, the explicit stop of the service, but I never see it started
again. After I upgrade, I get the following:
root@ubuntu:~# sudo -u
Screen log from the update attempt.
** Attachment added: screenlog.0.gz
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1058218/+attachment/3365652/+files/screenlog.0.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
More debugging: failed attempt by libpam to restart postgresql
(postgresql-8.4 in lucid does not have an init script called
postgresql, it's called postgresql-8.4) :
Setting up libpam0g (1.1.3-7ubuntu2) ...
Checking for services that may need to be restarted...Checking init scripts...
WARNING:
Here is where I would expect to see the start of postgresql-8.4 on
precise after the upgrade, but I don't see it:
Setting up postgresql-8.4 (8.4.14-0ubuntu12.04) ...
Setting up python-central (0.6.17ubuntu2) ...
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Upgrade from lucid - precise using packages in pitti's PPA work great.
Attached apt-term.log from that attempt just for safe keeping.
** Attachment added: apt-term.log
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1058218/+attachment/3366205/+files/apt-term.log
--
You
Upgrade from lucid - precise using 9.1 packages in pitti's PPA work
great. Attached apt-term.log from that attempt just for safe keeping.
** Attachment added: apt-term.log
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/1058218/+attachment/3366251/+files/apt-term.log
--
You
Hello David, or anyone else affected,
Accepted into precise-proposed. The package will build now and be
available in a few hours in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use
** Branch linked: lp:ubuntu/precise-proposed/postgresql-8.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058218
Title:
do-release-upgrade (lucid-precise) leaves postgres 8.4 in bad state
To
I ran the p-common test suite against the -proposed 8.4 package (as well
as current -9.1), and it's all pass. David, can you please double-check
that the upgrade now works for you? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Now uploaded to the precise unapproved queue, for the SRU team to
review.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1058218
Title:
do-release-upgrade (lucid-precise) leaves postgres 8.4 in bad
27 matches
Mail list logo
