unless bugs are pending please mark the following ebuilds stable (latest version) these ebuilds seem stable... (I know they are new) and the postgresql versions with the exception of 8.3.x have been out for years (and 8.3.3 seems stable enough to me). Since they are slotted they shouldn't cause problems with existing installs. virtual/postgresql-base virtual/postgresql-server dev-db/postgresql-base dev-db/postgresql-docs dev-db/postgresql-server (7.3) (~)7.3.21 (7.4) (~)7.4.21 (8.0) (~)8.0.17 (8.1) (~)8.1.13 (8.2) (~)8.2.9 (8.3) (~)8.3.3 Reproducible: Always
Yes, I agree. They're ready to go stable. Thing is: I'll be in holidays for 2 weeks so I'd really like to wait afterwards to be able to coordinate it.
no problem, I'm happy as long as things are going forward, so we can wait a couple more weeks.
bump.
Come on guys, at least postgresql 8.2 has been stable for years. It's a shame to be still "stuck" at 8.0. And I heard only good things about 8.3.
Also, guides and wikis need to be updated with information about "postgresql" vs "postgresql-server" etc.
any progress on this?
I plan to move forward with this unless someone from the pg team objects.
please check out the other bugs and solve them first before going stable with postgresql-{server,docs,base} if you really want to help.
*** Bug 215949 has been marked as a duplicate of this bug. ***
(In reply to comment #8) > please check out the other bugs and solve them first before going stable with > postgresql-{server,docs,base} if you really want to help. > how about using the "depends" and "blocks" features to make it easier ?
which bugs specifically are holding this back?
I've fixed this in funtoo's tree, should I resolve wontfix here?
(In reply to comment #11) > which bugs specifically are holding this back? > _NOTHING_ is blocking this, so just go on and mark 8.1 stable
1 year passed since =dev-db/postgresql-8.3.1 has been hard-masked: # Caleb Tennis <caleb@gentoo.org> (26 Mar 2008) # Masking per dev-zero request for more testing time This is already not the day zero. Please remove at least the hard mask. Thank you.
The same about =dev-db/libpq-8.3.1.
Alexander, AFAIK dev-db/postgresql and dev-db/libpq are being deprecated, and replaced by the ebuilds mentioned in this bug's title (dev-db/postgresql-server & co). Those are still masked (for unexplained reasons!!! Tiziano can you comment?) but not hard-masked.
Adrian, thank you for your input. I am a little confused since I see that virtual/postgresql-server-8.3 pulls dev-db/postgresql-8.3.1 which in turn pulls dev-db/libpq-8.3.1. If these packages are deprecated then the dependencies should be updated. Can anybody comment on this? Thanks.
Again, I'm no expert, but I think virtual/postgresql-server requires either dev-db/postgresql or dev-db/postgresql-server. That's the point of virtual packages, to allow different alternatives to satisfy the same dependency. dev-db/postgresql is probably still kept for not breaking existing installations, but if you want to upgrade to 8.3 I recommend switching to dev-db/postgresql-server
PostgreSQL 8.3.7 is out, please release new ebuild
8.3.7 is in portage. Tiziano, any thoughts on stabilizing some of the newer versions?
Please see my comment 2 on bug #183764. Comment reproduced below for the convenience of CC recipients... ________________________________ Please stabilize postgresql and libpq 8.1, 8.2, and 8.3. PostgreSQL 8.1 was released in 2005. PostgreSQL 8.2 was released in 2006. PostgreSQL 8.3 was released in 2008. All the above are still marked "unstable" on all architectures, though I've been using 8.1 and 8.2 through portage on over a dozen x86 and amd64 boxes in production roles (on Gentoo) for years with zero problems, and I'll be moving to 8.3 in production next month. Additionally, psycopg-2.0.10 (which fixes several threading bugs that affect my organization) depends on >=dev-db/libpq-8.1 (see bug #242336). As we use psycopg on ALL our Gentoo boxes to access our postgresql databases (remotely, on most of them), it currently requires customization of /etc/portage/package.keywords on all our machines, which seems really odd due to the age and stability of PostgreSQL 8.1.
I have used postgresql-server 8.3 for several months on several computers and had zero problems with it. The only complaint I have is that there are no ebuilds or flags for contrib modules (such as intarray). It is ABSOLUTELY RIDICULOUS that the latest stable is still 8.0, and nobody even explained why that is the case.
I agree with this request. I've been using these for ages (on amd64 and x86) and they work great. It's really time to have 8.3 stable, not just 8.0.15. ;)
Didn't notice this bug initially, all the action is happening in the new one *** This bug has been marked as a duplicate of bug 285475 ***
