Hi,
I am currently thinking about upgrading our bdb packages to a new release. For that I just submitted libdb-4_8 (containing db-4.8.30) to devel:libraries:c_c++. Would be nice if somebody with sufficient privileges in devel:libraries:c_c++ could accept submit request #48969.
The next step would be integration into Factory by submitting it to Factory and adding "Provides: libdb-devel" to libdb-4_8-devel while removing it from libdb-4_5-devel (I guess we still need to keep libdb-4_5 around for some time) to make depended packages build against the new Version.
But as history has shown libdb version updates can be a source of trouble so I'd like to ask what the best aproach would be to integrate it into Factory. In the pre-Buildservice times we had the "BETA" distribution to test those bigger changes. How is it handled nowadays? Is openSUSE:Factory:Staging comparable to BETA?
BTW, while there are even newer Versions available (db-5.1.19 being the most recent one, released a few days ago) I decided to take the 4.8.X Version for now. The main reason for that is that e.g. OpenLDAP (which relies heavily on bdb) does not yet support any 5.X version. While 4.8.30 has proven to be pretty solid already.
Am Donnerstag, 23. September 2010, 14:12:48 schrieb Ralf Haferkamp:
Hi,
I am currently thinking about upgrading our bdb packages to a new release. For that I just submitted libdb-4_8 (containing db-4.8.30) to devel:libraries:c_c++. Would be nice if somebody with sufficient privileges in devel:libraries:c_c++ could accept submit request #48969.
The next step would be integration into Factory by submitting it to Factory and adding "Provides: libdb-devel" to libdb-4_8-devel while removing it from libdb-4_5-devel (I guess we still need to keep libdb-4_5 around for some time) to make depended packages build against the new Version.
But as history has shown libdb version updates can be a source of trouble so I'd like to ask what the best aproach would be to integrate it into Factory. In the pre-Buildservice times we had the "BETA" distribution to test those bigger changes. How is it handled nowadays? Is openSUSE:Factory:Staging comparable to BETA?
comparable, but better. You can submit your sources there and we can see.
What about the data format? any suprises or "just" API changes?
Greetings, Stephan
On Thursday 23 September 2010 20:36:39 Stephan Kulow wrote:
Am Donnerstag, 23. September 2010, 14:12:48 schrieb Ralf Haferkamp:
Hi,
I am currently thinking about upgrading our bdb packages to a new release. For that I just submitted libdb-4_8 (containing db-4.8.30) to devel:libraries:c_c++. Would be nice if somebody with sufficient privileges in devel:libraries:c_c++ could accept submit request #48969.
The next step would be integration into Factory by submitting it to Factory and adding "Provides: libdb-devel" to libdb-4_8-devel while removing it from libdb-4_5-devel (I guess we still need to keep libdb-4_5 around for some time) to make depended packages build against the new Version.
But as history has shown libdb version updates can be a source of trouble so I'd like to ask what the best aproach would be to integrate it into Factory. In the pre-Buildservice times we had the "BETA" distribution to test those bigger changes. How is it handled nowadays? Is openSUSE:Factory:Staging comparable to BETA?
comparable, but better. You can submit your sources there and we can see.
Should that be going to through the devel-Project first? Or can I submit to Staging directly?
What about the data format? any suprises or "just" API changes?
The transaction log format changed with almost every release since 4.5. Usually that is not a big problem (IIRC) apart from the fact that db_recover might no longer work with the old logs. That's something I need to test in staging with the usual suspects (cyrus-imapd, openldap).
Between 4.5 and 4.6 the format of the Hash database tables was changed but Oracle claims that those changes are backwards compatible (though migrating to the new format might increase performance). Does anybody know a package that uses bdb with hash tables? IIRC the packages I regulary touch only use bdb btree's.
The complete changelogs are here: http://download.oracle.com/otndocs/products/berkeleydb/html/4.6.html http://download.oracle.com/otndocs/products/berkeleydb/html/4.7.html http://download.oracle.com/otndocs/products/berkeleydb/html/changelog_4_8_0....
Am Friday 24 September 2010 schrieb Ralf Haferkamp:
comparable, but better. You can submit your sources there and we can see.
Should that be going to through the devel-Project first? Or can I submit to Staging directly?
As you prefer - my preference would be devel project though.
What about the data format? any suprises or "just" API changes?
The transaction log format changed with almost every release since 4.5. Usually that is not a big problem (IIRC) apart from the fact that db_recover might no longer work with the old logs. That's something I need to test in staging with the usual suspects (cyrus-imapd, openldap).
Great.
Greetings, Stephan
Am Freitag 24 September 2010, 10:02:37 schrieb Stephan Kulow:
Am Friday 24 September 2010 schrieb Ralf Haferkamp:
comparable, but better. You can submit your sources there and we can see.
Should that be going to through the devel-Project first? Or can I submit to Staging directly?
As you prefer - my preference would be devel project though.
Ok, I just created submit requests for libdb-4_8 and libdb_java-4_8 to openSUSE:Factory:Staging. Should I update libdb-4_5 as well to remove the unneeded Provides (db and db-devel) or should that be handled through the Project configuration in Staging?
Am Monday 27 September 2010 schrieb Ralf Haferkamp:
Am Freitag 24 September 2010, 10:02:37 schrieb Stephan Kulow:
Am Friday 24 September 2010 schrieb Ralf Haferkamp:
comparable, but better. You can submit your sources there and we can see.
Should that be going to through the devel-Project first? Or can I submit to Staging directly?
As you prefer - my preference would be devel project though.
Ok, I just created submit requests for libdb-4_8 and libdb_java-4_8 to openSUSE:Factory:Staging. Should I update libdb-4_5 as well to remove the unneeded Provides (db and db-devel) or should that be handled through the Project configuration in Staging?
I would prefer to keep the project config of staging in sync with factory, so please submit the packages.
Greetings, Stephan
Am Montag 27 September 2010, 15:09:09 schrieb Stephan Kulow:
Am Monday 27 September 2010 schrieb Ralf Haferkamp:
Am Freitag 24 September 2010, 10:02:37 schrieb Stephan Kulow:
Am Friday 24 September 2010 schrieb Ralf Haferkamp:
comparable, but better. You can submit your sources there and we can see.
Should that be going to through the devel-Project first? Or can I submit to Staging directly?
As you prefer - my preference would be devel project though.
Ok, I just created submit requests for libdb-4_8 and libdb_java-4_8 to openSUSE:Factory:Staging. Should I update libdb-4_5 as well to remove the unneeded Provides (db and db-devel) or should that be handled through the Project configuration in Staging?
I would prefer to keep the project config of staging in sync with factory, so please submit the packages.
I don't have the permissions to submit libdb-4_5 to Staging could you please either do that yourself or make me a maintainer for libdb-4_5?
regards, Ralf
Am Monday 27 September 2010 schrieb Ralf Haferkamp:
Am Montag 27 September 2010, 15:09:09 schrieb Stephan Kulow:
Am Monday 27 September 2010 schrieb Ralf Haferkamp:
Am Freitag 24 September 2010, 10:02:37 schrieb Stephan Kulow:
Am Friday 24 September 2010 schrieb Ralf Haferkamp:
comparable, but better. You can submit your sources there and we can see.
Should that be going to through the devel-Project first? Or can I submit to Staging directly?
As you prefer - my preference would be devel project though.
Ok, I just created submit requests for libdb-4_8 and libdb_java-4_8 to openSUSE:Factory:Staging. Should I update libdb-4_5 as well to remove the unneeded Provides (db and db-devel) or should that be handled through the Project configuration in Staging?
I would prefer to keep the project config of staging in sync with factory, so please submit the packages.
I don't have the permissions to submit libdb-4_5 to Staging could you please either do that yourself or make me a maintainer for libdb-4_5?
I linked them into dlc and get now:
nothing provides db = 4.5.20 needed by libdb-4_5-devel
Greetings, Stephan
Am Dienstag 28 September 2010, 11:05:15 schrieb Stephan Kulow:
Am Monday 27 September 2010 schrieb Ralf Haferkamp:
Am Montag 27 September 2010, 15:09:09 schrieb Stephan Kulow:
Am Monday 27 September 2010 schrieb Ralf Haferkamp:
Am Freitag 24 September 2010, 10:02:37 schrieb Stephan Kulow:
Am Friday 24 September 2010 schrieb Ralf Haferkamp:
> comparable, but better. You can submit your sources there > and we can see.
Should that be going to through the devel-Project first? Or can I submit to Staging directly?
As you prefer - my preference would be devel project though.
Ok, I just created submit requests for libdb-4_8 and libdb_java-4_8 to openSUSE:Factory:Staging. Should I update libdb-4_5 as well to remove the unneeded Provides (db and db-devel) or should that be handled through the Project configuration in Staging?
I would prefer to keep the project config of staging in sync with factory, so please submit the packages.
I don't have the permissions to submit libdb-4_5 to Staging could you please either do that yourself or make me a maintainer for libdb-4_5?
I linked them into dlc and get now:
Thanks.
nothing provides db = 4.5.20 needed by libdb-4_5-devel
SR#49332 should fix that for now. So it seems some packages have BuildRequires on "libdb-4_5-devel" instead of the generic db-devel. We need to check whether that is really required or if those packages can build with against new libdb.
Ralf
Am Dienstag 28 September 2010, 11:37:37 schrieb Ralf Haferkamp:
Am Dienstag 28 September 2010, 11:05:15 schrieb Stephan Kulow:
I linked them into dlc and get now:
Thanks.
nothing provides db = 4.5.20 needed by libdb-4_5-devel
SR#49332 should fix that for now. So it seems some packages have BuildRequires on "libdb-4_5-devel" instead of the generic db-devel. We need to check whether that is really required or if those packages can build with against new libdb.
I created fixes for some packages that had BuildRequires on libdb-4_5- devel instead of db-devel in home:rhafer:bdb-update. Could you please link them from :Staging? I'll submit them to their according devel projects once we are ready to move libdb-4_8 to Factory.
Update:
I just created submit requests for:
sendmail python-bsddb3 novel-pinyin libgda3 libetpan
These were the packages that still linked against libdb-4.5 in openSUSE:Factory:Staging. I fixed them by either just updating the BuildRequires or patching configure/configure.in to check for newer libdb versions.
Addtionally to the above, php5 and libgda as in Factory still do not contain support for libdb-4.8, but as far as I can see the corresponding devel-projects already have updated Version that have support for libdb-4.8.
What's the best way to coordinate that all above packages will make it into factory before libdb-4.8 enters Factory. Coolo, will you handle that? If yes, I think I can just create submit request for libdb-4.8 and the updated libdb-4.5 now.
Am Wednesday 06 October 2010 schrieb Ralf Haferkamp:
What's the best way to coordinate that all above packages will make it into factory before libdb-4.8 enters Factory. Coolo, will you handle that? If yes, I think I can just create submit request for libdb-4.8 and the updated libdb-4.5 now.
None of them should create a big problem if they are hitting factory slightly later, so just submit your libdbs.
Thanks for handling it so carefully.
Greetings, Stephan
On Thursday 07 October 2010 10:24:11 Stephan Kulow wrote:
Am Wednesday 06 October 2010 schrieb Ralf Haferkamp:
What's the best way to coordinate that all above packages will make it into factory before libdb-4.8 enters Factory. Coolo, will you handle that? If yes, I think I can just create submit request for libdb-4.8 and the updated libdb-4.5 now.
None of them should create a big problem if they are hitting factory slightly later, so just submit your libdbs.
Done. What's still missing is the libdb_java-4_8 link. Seems osc is to smart to create links to non-existing packages :).
-
Ralf Haferkamp -
Stephan Kulow