Re: Anaconda illegal address

2015-01-29 Thread Joe Zeff
On 01/29/2015 01:52 PM, CLOSE Dave wrote: Joe Zeff wrote: Closing a bug as a duplicate isn't saying that it's not a bug. It means that the bug's already been reported, and that it's a waste of resources keeping two versions of the report open. But it does mean that when the referenced report

Re: Anaconda illegal address

2015-01-29 Thread CLOSE Dave
Joe Zeff wrote: > Closing a bug as a duplicate isn't saying that it's not a bug. It means > that the bug's already been reported, and that it's a waste of resources > keeping two versions of the report open. But it does mean that when the referenced report has already been closed and marked NOT

Re: Anaconda illegal address

2015-01-29 Thread Chris Murphy
On Thu, Jan 29, 2015 at 1:17 PM, CLOSE Dave wrote: > I wrote: > >> I will now open two BZ reports: >> >> 1. Anaconda should fail with a useful message when a required address >> is missing. > > My report has now been closed, marked as a duplicate of BZ 1178320. That > means at least one developer

Re: Anaconda illegal address

2015-01-29 Thread Joe Zeff
On 01/29/2015 12:17 PM, CLOSE Dave wrote: My report has now been closed, marked as a duplicate of BZ 1178320. That means at least one developer thinks providing a useless error message is not a bug. I strongly disagree. Closing a bug as a duplicate isn't saying that it's not a bug. It means t

Re: Anaconda illegal address

2015-01-29 Thread CLOSE Dave
I wrote: > I will now open two BZ reports: > > 1. Anaconda should fail with a useful message when a required address > is missing. My report has now been closed, marked as a duplicate of BZ 1178320. That means at least one developer thinks providing a useless error message is not a bug. I strongl

Re: Anaconda illegal address

2015-01-29 Thread CLOSE Dave
Chris Murphy wrote: > I mean, when there's a crash libreport should pop up and offer to file > the bug for you. You need to enter bugzilla credentials and then it > automatically files the bug details including uploading all files. > Before it does this, it checks if a bug has already been filed w

Re: Anaconda illegal address

2015-01-29 Thread Chris Murphy
On Thu, Jan 29, 2015 at 10:44 AM, CLOSE Dave wrote: > Chris Murphy wrote: > >>> When anaconda complains about an "illegal IP address string passed >>> to inet_aton", how can I discover what the bad string contains? So >>> far as I can see, all the configured addresses are perfectly valid. >>> Here

Re: Anaconda illegal address

2015-01-29 Thread CLOSE Dave
Chris Murphy wrote: >> When anaconda complains about an "illegal IP address string passed >> to inet_aton", how can I discover what the bad string contains? So >> far as I can see, all the configured addresses are perfectly valid. >> Here's a copy of the traceback: . > If you

Re: Anaconda illegal address

2015-01-28 Thread Chris Murphy
On Wed, Jan 28, 2015 at 7:12 PM, CLOSE Dave wrote: > When anaconda complains about an "illegal IP address string passed to > inet_aton", how can I discover what the bad string contains? So far as I > can see, all the configured addresses are perfectly valid. Here's a copy > of the traceback:

Anaconda illegal address

2015-01-28 Thread CLOSE Dave
When anaconda complains about an "illegal IP address string passed to inet_aton", how can I discover what the bad string contains? So far as I can see, all the configured addresses are perfectly valid. Here's a copy of the traceback: . -- Dave Close, Thales Avionics, Irvine