Mailinglist Archive: opensuse-factory (282 mails)
| < Previous | Next > |
Re: [opensuse-factory] Updating Berkely DB
- From: Ralf Haferkamp <rhafer@xxxxxxx>
- Date: Wed, 6 Oct 2010 17:26:57 +0200
- Message-id: <201010061726.57623.rhafer@xxxxxxx>
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.
--
Ralf
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
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.
--
Ralf
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |