Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install

2004-05-11 Thread Eloy A. Paris
Hi Thomas,

On Tue, May 11, 2004 at 03:48:03PM +0200, Thomas Hood wrote:
 I wondered why dhcp-client is still being installed, rather than
 dhcp3-client.
 
 On Tue, 2004-05-11 at 13:48, Anthony Towns wrote:
  That's easy: dhcp3-client didn't used to exist.
 
 So the question is: Why is debootstrap _still_ installing dhcp-client?

Good question. I guess they are using it because that is the official
DHCP client package (official in the sense that dhcp3-client started
out as the unstable and development version of the ISC DHCP client,
IIRC, and when v3 came out as stable we still kept the old v2 client
alive in the dhcp-client package for some reasons.)

  (If dhcp3-client is to replace dhcp-client, why isn't it just being
  called dhcp-client, with dhcp2-client kept around if it's really needed?)
 
 Good question for the dhcp-client maintainers.
 CC'ing [EMAIL PROTECTED]

Migrating the dhcp-* packages to version 3 of the ISC DHCP package was
part of our plan. However, a few months ago we asked the
debian-installer people on debian-boot and someone said the timing
wasn't right for such a migration because of the risk involved.

Cheers!

Eloy.-


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



Re: Is dhcp2 or dhcp3 the default install for Sarge?

2004-03-03 Thread Eloy A. Paris
Hi Luke,

I believe the debian-installer folks are using version 2 of the ISC DHCP
packages for the Sarge installer, but I am not 100% sure so I have Cc'ed
them here for additional input.

The maintainers of the Debian dhcp and dhcp3 packages would like to
replace the dhcp packages (ISC DHCP v2) with version 3 of the ISC DHCP
package, and get rid of the dhcp3 packages. It's been in our to-do list
for some time now but we haven't gotten around it yet. Feedback from the
debian-installer team about this move would be appreciated.

Cheers,

Eloy.-

On Mon, Mar 01, 2004 at 10:31:49AM -0500, Luke Seubert wrote:
 Good day,
 
 In an effort to ensure that the Debian page on DistroWatch.com (1) is as 
 up to date as possible, could you please reply to this email and 
 indicate if dhcp2.0pl5-16.1 or dhcp3.0+3.0.1rc11-5 is the default 
 version of dhcp to be installed for Sarge?
 
 I have forwarded other updates about Debian packages to Mr. Ladislav 
 Bodnar, maintainer of DistroWatch, and he has accepted them. However, a 
 question has arisen about the default install for dhcp in Sarge. 
 
 Many thanks,
 Luke Seubert
 
 (1) http://distrowatch.com/table.php?distribution=debian
 


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



Re: dhcp NMU or dhcp v3?

2002-02-05 Thread Eloy A. Paris

Matthias,

Matt Zimmerman and I decided to leave the v2 dhcp* packages alone and
create instead new dhcp3* packages for DHCP v3. So, both v2 and v3
packages will coexist.

I am almost ready to upload new v2 packages which fix lots of bug
(including the ones you want to fix with the NMU.) I announced our plans
on debian-devel last week (Saturday or Sunday.) In the announcement I
asked people to help us test the new dhcp* packages I plan to upload soon.

You would do me a great favor if, instead of NMU'ing, you could test
out these new packages and confirm that they fix the problems I mark as
fixed in the changelog. The location of the test packages is:

http://people.debian.org/~peloy/dhcp/

Also, take a look at the debian-devel archives to see my announcement
and the current plan.

If you find something wrong you can send me a patch against the source
code of these packages.

Cheers!

Eloy.-

On Tue, Feb 05, 2002 at 10:32:30PM +0100, Matthias Klose wrote:
 Hi,
 
 although v3 is available in experimental ... did you get answer from
 the boot floppies team, if/when v3 can be uploaded to unstable?
 
 If not, I offer to upload a NMU which moves the configuration option
 from /etc/init.d/dhcp to /etc/default/dhcp. Fixing #75365 and #121854.
 
 Thanks, Matthias
 


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