On Tue, 2011-05-24 at 15:46 +1000, Andrew Pollock wrote: > On Sun, May 22, 2011 at 03:40:40PM +0200, Svante Signell wrote: > > Hi, > > > > Is there any specific reason for ignoring the patches adding support for > > GNU/Hurd in isc-dhcp. This package is part of the Debian installer, > > which is working well on GNU/Hurd. Maybe the patches need to be updated > > to conform with isc-dhcp-4.1.1-P1-17, please let me know if this is the > > case. Currently this package is hosted at debian-ports for GNU/Hurd, but > > I don't see any specific reason not to have it in main. > > No specific reason, I just haven't gotten around to that particular bug yet. > I deemed it a higher priority to try and advance IPv6 support a bit more. > > Since you've brought this bug and patch to my attention, I've taken a brief > look at it this evening. I'm going to have to forward it upstream for their > feedback, as it touches a fair bit, and it's not the sort of thing I want to > have to keep carrying indefinitely. I'd like to know that upstream is going > to fix the issue at some point. This is still an issue in 4.2.1-P1, > persumably, given the patch applies cleanly there. > > I guess I should take a look at a build failure on GNU/Hurd, so I can better > understand why what the patch is doing is necessary. > > Given the patch does apply cleanly to 4.2.1-P1, it doesn't look like it will > be an ongoing maintenance burden for me, so I can probably apply it while > upstream figures out what to do about it long-term.
Thank you for your reply. So you mean that there will be no more patches to 4.1.1-P1? Regarding the question if the patches apply cleanly to 4.2.1 I don't know since there are no Debian packages of 4.2.1 yet. In case you are preparing these, please let me know when they are available, so I can try if the patches apply cleanly or have to be modified. To clarify, with upstream you mean: http://www.isc.org/software/dhcp Best regards! -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
