<br><div class="gmail_quote">2009/6/1 Sergiusz Pawlowicz <span dir="ltr"><<a href="mailto:sergiusz@pawlowicz.name">sergiusz@pawlowicz.name</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, Jun 1, 2009 at 11:54, Martin <<a href="mailto:martin@ml1.co.uk">martin@ml1.co.uk</a>> wrote:<br>
<br>
> So... Worth fixing?<br>
<br>
No. Nothing is broken.<br>
<br></blockquote><div><br>Actually, I'm not the only one to have found this an issue, from the look of it, and I do think it is reasonable to expect, having specified in the Synaptic preferences that there is no proxy, that Synaptic should then ignore (or at least flag) a conflicting directive in apt.conf. However, it does actually respect that conflicting directive, and thus fails without a clear indication of the reason. <br>
<br>Following a configuration which clearly conflicts with a user intention *is* broken. <br><br>So I do agree with Martin that this is a bug, and I do intend to file it - unless there's a really good reason why not!<br>
<br>--<br><br>David<br><br></div></div>