Paul Wise writes:
> On Sat, May 2, 2009 at 12:23 AM, Matthias Julius wrote:
>
>> As explained in another post this should not affect the user since the
>> database format has not changed.
>
> Please investigate the DB->upgrade thing Clint mentioned and forward
> that upstream, with a patch if yo
On Sat, May 2, 2009 at 12:23 AM, Matthias Julius wrote:
> As explained in another post this should not affect the user since the
> database format has not changed.
Please investigate the DB->upgrade thing Clint mentioned and forward
that upstream, with a patch if you are able.
> I have not done
Here we go ...
Paul Wise writes:
> On Tue, Apr 28, 2009 at 1:04 AM, Matthias Julius wrote:
>
>> I would really be grateful if someone could take a look at this
>> package and possibly upload it for me.
>
> You build-depend on libdb-dev, in sid that depends on libdb4.7-dev but
> the current dnsh
Clint Adams writes:
> Typically the fear which motivates this type of question is unfounded.
> Looking at the dnshistory source code, it appears that the use of BDB
> is trivial. Generally when the feature set you require could just
> as easily have been satisfied by GDBM, there are rarely compa
> > According to
> > http://www.oracle.com/technology/documentation/berkeley-db/db/ref/upgrade/process.html
> > it is not even safe to assume that the API of a new major or minor
> > version is backwards compatible. This means that a binNMU triggered
> > by a libdb transition may cause the applica
On Thu, Apr 30, 2009 at 9:21 PM, Matthias Julius wrote:
> Matthias Julius writes:
>
>> Paul Wise writes:
>>
>>> I don't see anything in the maintainer scripts that would migrate the
>>> db files. Does dnshistory or libdb handle upgrading the on-disk db
>>> format? Or can libdb handle older versi
Matthias Julius writes:
> Paul Wise writes:
>
>> I don't see anything in the maintainer scripts that would migrate the
>> db files. Does dnshistory or libdb handle upgrading the on-disk db
>> format? Or can libdb handle older versions of the on-disk db format?
>
> I was assuming the latter. But
Paul Wise writes:
> I don't see anything in the maintainer scripts that would migrate the
> db files. Does dnshistory or libdb handle upgrading the on-disk db
> format? Or can libdb handle older versions of the on-disk db format?
I was assuming the latter. But, reading
http://www.oracle.com/tec
On Tue, Apr 28, 2009 at 10:25 PM, Matthias Julius wrote:
> I am not quite sure how to deal with that one. Since Luk Claes NMUed
> the package to change the Build-Depends from libdb4.4-dev to libdb-dev
> I don't really have control over which libdb version dnshistory is
> built against. If it ha
Paul Wise writes:
> You build-depend on libdb-dev, in sid that depends on libdb4.7-dev but
> the current dnshistory package is built against libdb4.6. Should you
> add another debian/NEWS entry about this? I'm not sure what to do in
> this situation, could you investigate?
I am not quite sure ho
On 2009-04-28 12:45 +0200, Paul Wise wrote:
> For some reason the mktime test in ./configure takes ages and a lot of
> CPU in pbuilder and then fails.
This means that `configure' needs to be regenerated with a newer version
of autoconf (2.61-7 or better). See
http://lists.debian.org/debian-devel
On Tue, Apr 28, 2009 at 1:04 AM, Matthias Julius wrote:
> I would really be grateful if someone could take a look at this
> package and possibly upload it for me.
You build-depend on libdb-dev, in sid that depends on libdb4.7-dev but
the current dnshistory package is built against libdb4.6. Shou
Matthias Julius writes:
> I am looking for a sponsor for the new version 1.3-2
> of my package "dnshistory".
>
> It builds these binary packages:
> dnshistory - Translating and storing of IP addresses from log files
>
> The package appears to be lintian clean.
>
> The upload would fix these bugs:
13 matches
Mail list logo
