http://qa.mandrakesoft.com/show_bug.cgi?id=2829
[EMAIL PROTECTED] changed:
What|Removed |Added
Version|0.1-11mdk |0.1-12mdk
--- Additional
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-19 11:46 ---
Joerg, I am taking this discussion off the list so follow up via email. This
looks more like a networking issue than any type of bug, so dont want to be
flooding the
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-14 14:56 ---
Rob,
i removed the 127.0.0.1 from /etc/resolv.conf. still no resolution (i did not
restart the network). :(
--- You are receiving this mail because: ---
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-12 12:05 ---
Finally got your patch installed. A few minor things as well as some on the
addition files in the SRPM would need to be changed in order for it to work
after an RPM
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-12 14:02 ---
I've tried two installations now, both on VirtualPC but different environments
One worked with no problems at all - the one within the Sun internal network
didn't even
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-12 16:30 ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jsk_priv wrote:
environments
network
Your dhcp server was probably providing a domain name.
Switch Router
resolv.conf
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-12 21:43 ---
You may have the same problem as in Bug #1744. You do have 127.0.0.1 as the primary
nameserver in /etc/resolve.conf. Try removing that entry and see if you can resolve
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
[EMAIL PROTECTED] changed:
What|Removed |Added
AssignedTo|[EMAIL PROTECTED]|[EMAIL PROTECTED]
Component|program
http://qa.mandrakesoft.com/show_bug.cgi?id=2829
--- Additional Comments From [EMAIL PROTECTED] 2003-03-11 22:19 ---
Patch looks like it should fix this. I am unable to test on this machine due to the
Kdevelop
autoconf2 conflict.
I would also like to note that I also run into the
