Package: exim4
Version: 4.67-8
User: [EMAIL PROTECTED]
Usertags: oldbdb db4.3
Please switch your package to db4.6 so we can get rid of db4.3.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
tags #442645 confirmed pending
thanks
On Sun, Sep 16, 2007 at 01:43:41PM -0400, Clint Adams wrote:
> Please switch your package to db4.6 so we can get rid of db4.3.
I have changed the Build-Depends. Things would have been faster one
could easily learn which bdb version is the recommended one this
On Sun, Sep 16, 2007 at 09:53:33PM +0200, Marc Haber wrote:
> I have changed the Build-Depends. Things would have been faster one
> could easily learn which bdb version is the recommended one this week.
You can build-depend upon libdb-dev (>= 4.6.19-1), though I'm not sure
that's the recommendatio
* Clint Adams:
> On Sun, Sep 16, 2007 at 09:53:33PM +0200, Marc Haber wrote:
>> I have changed the Build-Depends. Things would have been faster one
>> could easily learn which bdb version is the recommended one this week.
>
> You can build-depend upon libdb-dev (>= 4.6.19-1), though I'm not sure
>
On Thu, Sep 20, 2007 at 08:53:26AM +0200, Florian Weimer wrote:
> * Clint Adams:
> > On Sun, Sep 16, 2007 at 09:53:33PM +0200, Marc Haber wrote:
> >> I have changed the Build-Depends. Things would have been faster one
> >> could easily learn which bdb version is the recommended one this week.
> >
>
* Marc Haber:
>> Berkeley DB upgrades change the API (in addition to the ABI), so
>> explicitly versioned dependencies (libdb4.6-dev et al.) are better.
>
> So, package maintainers need to be aware which Berkeley DB is
> recommended to be used for appropriate dependencies.
Exactly, just like Curl
On 2007-09-20 Marc Haber <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 20, 2007 at 08:53:26AM +0200, Florian Weimer wrote:
>> * Clint Adams:
>>> On Sun, Sep 16, 2007 at 09:53:33PM +0200, Marc Haber wrote:
I have changed the Build-Depends. Things would have been faster one
could easily learn wh
On Thu, Sep 20, 2007 at 11:02:23AM +0200, Florian Weimer wrote:
> If you use on-disk database environments (grep for DB_ENV to get an
> idea if this is the case), you need quite a bit of code to handle
> updates properly (and downgrades, of course). If you use just plain
> DB objects, it's not ver
On Thu, Sep 20, 2007 at 11:02:23AM +0200, Florian Weimer wrote:
> * Marc Haber:
> > I have been informed that it is not always a brilliant idea to use
> > latest Berkeley DB, right?
>
> If you use on-disk database environments (grep for DB_ENV to get an
> idea if this is the case), you need quite
On Thu, Sep 20, 2007 at 07:29:03PM +0200, Marc Haber wrote:
> Exim's default config only uses Berkeley DB files for transient data
> such as retry hints, and the postinst code simply removes all db files
> that exim_dumpdb gives a non-zero reply code for.
>
> If the local admin decides to use db f
On 2007-09-20 Clint Adams <[EMAIL PROTECTED]> wrote:
> On Thu, Sep 20, 2007 at 07:29:03PM +0200, Marc Haber wrote:
>> Exim's default config only uses Berkeley DB files for transient data
>> such as retry hints, and the postinst code simply removes all db files
>> that exim_dumpdb gives a non-zero r
On Fri, Sep 21, 2007 at 09:53:40AM +0200, Andreas Metzler wrote:
> There are a couple of reasons why exim should not always automatically
> use the latest and greatest bdb. exim is in base (Priority: standard).
>
> - The newest and latest bdb has not always been of sufficiently high
> priority i
On Fri, Sep 21, 2007 at 09:53:40AM +0200, Andreas Metzler wrote:
> - The newest and latest bdb has not always been of sufficiently high
> priority itself.[1]
>
> [1] Like currently in sid.
> Package: libpam-modules
> Priority: required
> Depends: libc6 (>= 2.6-1), libcap1, libdb4.6, libpam0g (>=
13 matches
Mail list logo
