Bug#248905: installation report
On Thu, May 13, 2004 at 07:19:31PM -0300, Joey Hess wrote: Can you show what error messages you got exactly and which packages failed to install? Selecting Don't touch keymap should certainly work. I saw this also today during an install. I installed from a slightly old netinst iso, and after tasksel it upgraded several packages, including console-*. During this upgrade, I was asked which keymap to use, even though I had already told it to use the appropriate Brazilian keymap (which of them it is, I forget right now). Then console-something (-data?) failed with exit code 9. Apparently it succeeded on the second pass. I don't understand why console-* is asking about the keymap when d-i has already provided one, or, of course, why it's failing on upgrade. There are some bug reports on this sort of thing for console-common... I think the one with exit code 9 is labelled resolved? Anyway, I also filed a bug there, and I notice another one just now... might take a look there also if you haven't already. I think 0.7.42 was supposed to resolve this... 0.7.41 just dropped down to testing yesterday-ish ? Scott Webster -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
I just installed dhcpcd 1:1.3.22pl4-10 and dpkg -s reports: Conflicts: dhcpcd-sv, dhcp-client so I don't see how you could have both dhcpcd and dhcp-client (or any other DHCP client that Provides dhcp-client) installed. You're right, dhcpcd is not installed. I have dhcp-client 2.0pl5-16.1 When one installs tasks does tasksel knock out uninstallable items from the list and proceed? If so then that would explain how you ended up with resolvconf but not dhcpcd. Dunno, the huge apt-get command flew by with no prompting (probably a good thing). I haven't really investigated how tasksel calls apt-get. Actually, I thought resolvconf only got installed by the unstable version of tasksel (1.51); I just checked and I have 1.50 (testing) installed here. Now I'm not even sure where resolvconf came from. I am 100% sure I did not install resolvconf directly, and 99% sure I did not install anything that depended on it after the initial install (I checked my bash_history for root, and I think it actually contains every command I've used on this install). It's possible that one of the packages installed by one of the tasks I selected depends on it, however, dpkg --no-act -r resolvconf just says it would remove it, no errors based on dependencies. FYI, I think I chose the following tasks: basic-desktop, broadband, c-dev, desktop, java-dev, kernel-compile, office, print-server, python-dev, science, tex, unix-server, lsb. Re: Matt's comment about how this doesn't affect everyone using dhcp, for instance, him: Sorry, my question wasn't really properly phrased... I guess I just want to know who this would affect... you don't use resolvconf, but it got installed on my system through the installer and base-config/tasksel somehow, and I chose only normal options throughout the process. I had thought it came from tasksel (broadband) and that dhcpcd didn't get installed because it conflicted with dhcp-client or something, but that isn't clear to me anymore. I don't suppose d-i/base-config uses tasksel 1.51 somehow but installs 1.50... If it turns out that resolvconf just got on my system randomly then I guess just making it conflict with dhcp-client would be enough here, but I'm almost positive that this is some kind of default currently. The other email from Stefan seems to show at least someone else with the same problem. Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
Perhaps I'm missing something here, but doesn't this mean that the default install with d-i is now broken by using both dhcp-client and resolvconf? Doesn't this affect everyone using dhcp? Clearly if the default install leads to a non-functioning network it won't be getting rave reviews... I must be confused... Scott Webster On Tue, May 11, 2004 at 08:43:44AM -0700, Matt Zimmerman wrote: On Tue, May 11, 2004 at 05:23:06PM +0200, Thomas Hood wrote: On Tue, 2004-05-11 at 17:10, Matt Zimmerman wrote: Because the debian-installer folks asked the dhcp*-client folks to leave things as they are for sarge. So can should debootstrap switch to installing dhcp3-client? I expect not, but ask debian-boot. In order for dhcp-client to be updated to v3, the various upgrade issues (dhcp-* v2 - dhcp-* v3, dhcp3-* - dhcp-* v3) need to be worked out, and I think it's a bit late in the game for that anyway. We asked about it some time ago and were told to leave it alone for d-i's sake. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248256: Problem with DHCP\resolvconf
On Tue, May 11, 2004 at 07:13:12PM +0200, Stefan Salewski wrote: Dear Mr Scott Webster, I just found your Debian-Sarge Installation report: On a clean boot I don't have any DNS servers configured in /etc/resolv.conf. As I can see I did exactly the same installation method last sunday and get the same problem. (Solved it by hand by replacing the link /etc/resolv.conf with a handmade file). I am absolutely new to Debian (converted from SuSE 8.2) so I have not good chances to find the reason for this problem. I have read the README of resolvconf and searched more than two hours at lists.debian.org for this problem. Your report is the best description of this problem I found. I think you have much more knowledge of Debian as me, so I would be grateful if You can send me a mail when you find the reason or solution of this problem. Is it useful when I send a bug-report concerning this problem to Debian too? Beside this little bug, Debian-Sarge works great! Best regards Stefan Salewski Stefan is refererring to bug # 248256. Stefan, you could follow the discussion on bug # 248399 (bugs.debian.org/248399). You likely shouldn't send a bug report on this issue, maybe one for the rest of your installation report. These two bugs should probably be merged, I probably shouldn't have submitted both in fact, given that the resolvconf one ended back here (sorry!) Scott Webster -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#248399: dhcp-found dns servers not placed in resolv.conf after default install
On Tue, May 11, 2004 at 08:07:00PM +0200, Thomas Hood wrote: Is resolvconf installed by default? If so then it's news to me. (I knew that resolvconf was installed as part of the Broadband and Dialup tasks; however Broadband includes dhcpcd and that does work with resolvconf.) I likely selected the Broadband task in tasksel. I may have dhcpcd installed. I can't check now unfortunately, as the box is at home, and apparently the dynamic IP has changed. If I remember correctly, it is installed, and presumably it would be if it's in the same task as resolvconf. Nevertheless, dhclient is being run, presumably by ifup? How does ifup choose which dhcp program to run? Or am I offtrack here? Scott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
