PostgreSQL 8.4.1 backport

Bug #431157 reported by Stuart Bishop
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Hardy Backports
Fix Released
Undecided
Martin Pitt
Intrepid Ibex Backports
Fix Released
Undecided
Unassigned
Jaunty Jackalope Backports
Fix Released
Undecided
Martin Pitt

Bug Description

The Launchpad project wants to switch to PostgreSQL 8.4.1. For this, we need PostgreSQL 8.4.1 packages for Hardy and Jaunty.

Revision history for this message
Martin Pitt (pitti) wrote :

FYI, I maintain a stable backports repository for PostgreSQL: https://launchpad.net/~pitti/+archive/postgresql

I promise that this won't ever get crack or untested stuff.

However, it's probably still worthwhile to have an "official" backport, since other people are going to need this as well. Waiting for -backporters ack before upload, though.

Revision history for this message
Martin Pitt (pitti) wrote :

> I promise that this won't ever get crack or untested stuff.

To clarify that, this means "for stable postgresql versions". I will upload alphas and betas of new major versions, but that won't affect upgrades. You have to explicitly install them, since they have different package names.

Changed in hardy-backports:
status: New → Confirmed
Changed in jaunty-backports:
status: New → Confirmed
Revision history for this message
Stuart Bishop (stub) wrote :

No need to do this on my account - looks like for Launchpad we will need 8.4.2 (we are triggering a bug in 8.4.1, now fixed upstream).

Revision history for this message
Scott Kitterman (kitterman) wrote :

Ack from ubuntu-backporters for whatever Pitti thinks is best.

Revision history for this message
Scott Kitterman (kitterman) wrote :

I would like to see Intrepid covered too so there is a smooth upgrade path for Hardy -> Intrepid -> Jaunty -> Karmic.

Revision history for this message
Martin Pitt (pitti) wrote :

Let's skip intrepid. If you come from Hardy's backoprted packages, you can upgrade through intrepid to jaunty to karmic without a problem due to the way the postgresql packages are organized.

With Karmic being released I also think that the jaunty backport isn't urgent any more. There's still my PPA, too.

Scott, are you fine with delegating me backport ack power for postgresql-*? I deliberately keep the packages backportable (many people ask for them), and I can test them pretty easily (with my chroots and my test suite arsenal).

Changed in intrepid-backports:
status: New → Invalid
Revision history for this message
Martin Pitt (pitti) wrote :

Will do the backports in a couple of days when the karmic release DOS has settled a bit.

Changed in jaunty-backports:
assignee: nobody → Martin Pitt (pitti)
status: Confirmed → In Progress
Changed in hardy-backports:
assignee: nobody → Martin Pitt (pitti)
status: Confirmed → In Progress
Revision history for this message
Martin Pitt (pitti) wrote :

I: Extracting postgresql-common_101.dsc ... done.
I: Building backport of postgresql-common as 101~hardy1 ... done.

Changed in hardy-backports:
status: In Progress → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

I: Extracting postgresql-common_101.dsc ... done.
I: Building backport of postgresql-common as 101~intrepid1 ... done.

Changed in intrepid-backports:
status: Invalid → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

I: Extracting postgresql-common_101.dsc ... done.
I: Building backport of postgresql-common as 101~jaunty1 ... done.

Changed in jaunty-backports:
status: In Progress → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

I: Extracting postgresql-8.4_8.4.1-1.dsc ... done.
I: Building backport of postgresql-8.4 as 8.4.1-1~hardy1 ... done.

Revision history for this message
Martin Pitt (pitti) wrote :

I: Extracting postgresql-8.4_8.4.1-1.dsc ... done.
I: Building backport of postgresql-8.4 as 8.4.1-1~intrepid1 ... done.

I: Extracting postgresql-8.4_8.4.1-1.dsc ... done.
I: Building backport of postgresql-8.4 as 8.4.1-1~jaunty1 ... done.

Revision history for this message
James Andrewartha (trs80) wrote :

Is there any reason the hardy packages haven't been published yet?

Revision history for this message
Martin Pitt (pitti) wrote :

Sorry, they were stuck in the NEW queue. Processed now.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.