I'm assuming that it is fixed. However, I do not know enough about the
problem (and apt) to know if my test is valid. If my test case is
flawed, please let me know. Here is a transcript:
[EMAIL PROTECTED]:~$ sudo apt-get install gnome-doc-utils
Password:
Reading package lists... Done
Building d
I'm sorry to post this here, but this issue is threatening my use of
Linux as a desktop OS. If I cannot make hosts entries I cannot do my
job and my company will revoke my freedom of OS.
So, being new to this I have ask, "can I install
http://packages.ubuntulinux.org/feisty/gnome/gnome-system-too
I have found that given enough reboots I can always get my system on my
home (wifi) or work (ethernet with lots of search domains and hosts
entries) networks. I simply have to (usually when I get home from work)
delete all the custom entries from /etc/hosts and reboot. Then network-
admin will la
I still get this error as of today.
[EMAIL PROTECTED]:~/svn/f-spot/development/trunk$ sudo apt-get update
Get:1 http://security.ubuntu.com feisty-security Release.gpg [191B]
Ign http://security.ubuntu.com feisty-security/main Translation-en_US
Ign http://security.ubuntu.com feisty-security/restric
I don't know what I did to get this, so I can't very well make a patch.
I also don't know where to get another copy of the original. I realize
that I should have made a backup. Oops!
I'm posting it here so that it may be useful to someone else.
** Attachment added: "a working version"
http:/
nse of the code and my changes compile fine
and work as expected. It was going to be my first code submission,
but this network-admin thing has greater impact/visibility.
So, knowing this, would you be willing to "bring me into the circle"
so to speak?
--
.!# RichardBronosky #!.
--
Okay, I got the specified revision. I compared it to the result of
`apt-get source gnome-system-tool` and have applied only the
"relevant?" changes. But, I'm not sure what to do with it now. I
don't know whether to run the configure script, or use the Makefile
that was in the src, or whether to
*** This bug is a duplicate of bug 67936 ***
@Brian and all,
see my post here
https://launchpad.net/ubuntu/+source/gnome-system-tools/+bug/67936/comments/27
One temporary work around until Feisty goes GA is to find what file is
causing the problem (in my case it was /etc/hosts but Stuart Bishop
