Bug#330184: [patch] patched against wrong upstream version

2005-10-06 Thread Mario Lipinski

Hello,

i hat a closer look into it and found out that the patch is against svn 
and not 2.9.18  where it has been applied. The main difference i think 
is in tcpreceiver.cc (a diff is included). After adjusting 
tcpreceiver.cc AXFR works, but i am not familiar with pdns so i cannot 
say whether there are any side-effects by this.


Mario


# diff pdns-2.9.18/pdns/tcpreceiver.cc pdns-2.9.18.new/pdns/tcpreceiver.cc
165c165

---
   packet-d_tcp=true;
303a304
   LLogger::ErrorAXFR of domain 'target' failed: not 
authoritativeendl;

313a315
   LLogger::ErrorAXFR of domain 'target' failed: not 
authoritative in second instanceendl;

512c514
 LLogger::ErrorTCPv6 server bound to 
*laddr:arg()[local-port]endl;

---
 LLogger::ErrorTCPv6 server bound to 
[*laddr]:arg()[local-port]endl;




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#330184: [patch] patched against wrong upstream version

2005-10-06 Thread Matthijs Mohlmann
Hi,

Mario Lipinski wrote:
 Hello,
 
 i hat a closer look into it and found out that the patch is against svn
 and not 2.9.18  where it has been applied. The main difference i think
 is in tcpreceiver.cc (a diff is included). After adjusting
 tcpreceiver.cc AXFR works, but i am not familiar with pdns so i cannot
 say whether there are any side-effects by this.
 
Thanks. I have looked into your patch and added a few other things.

I have created a new pdns package, can you try if the AXFR works with
this release ?

Thanks in advance.

 Mario
 

Regards,

Matthijs Mohlmann


signature.asc
Description: OpenPGP digital signature