On Tue, 2010-10-19 at 21:56 +0200, Josselin Mouette wrote:
> Le mardi 19 octobre 2010 à 20:13 +0100, Adam D. Barratt a écrit :
> > On Wed, 2010-10-06 at 09:29 +0200, Josselin Mouette wrote:
> > > Le mercredi 06 octobre 2010 à 08:12 +0200, Mike Hommey a écrit :
> > > > Does that mean libproxy will
Le mardi 19 octobre 2010 à 20:13 +0100, Adam D. Barratt a écrit :
> On Wed, 2010-10-06 at 09:29 +0200, Josselin Mouette wrote:
> > Le mercredi 06 octobre 2010 à 08:12 +0200, Mike Hommey a écrit :
> > > Does that mean libproxy will depend (as in Depends control field) on
> > > webkit ? That's going
On Wed, 2010-10-06 at 09:29 +0200, Josselin Mouette wrote:
> Le mercredi 06 octobre 2010 à 08:12 +0200, Mike Hommey a écrit :
> > Does that mean libproxy will depend (as in Depends control field) on
> > webkit ? That's going to be a problem later, because iceweasel 4.0 may use
> > libproxy (I enabl
Josselin Mouette writes:
> Le mercredi 06 octobre 2010 à 08:12 +0200, Mike Hommey a écrit :
> > Does that mean libproxy will depend (as in Depends control field) on
> > webkit ? That's going to be a problem later, because iceweasel 4.0 may use
> > libproxy (I enabled it, but I'm not entirely sure
Le mercredi 06 octobre 2010 à 08:12 +0200, Mike Hommey a écrit :
> Does that mean libproxy will depend (as in Depends control field) on
> webkit ? That's going to be a problem later, because iceweasel 4.0 may use
> libproxy (I enabled it, but I'm not entirely sure I'll keep it that way).
No. It do
On Wed, Oct 06, 2010 at 06:30:41AM +0200, Emilio Pozuelo Monfort wrote:
> On 23/09/10 23:45, Josselin Mouette wrote:
> > Le jeudi 23 septembre 2010 à 19:55 +0200, Emilio Pozuelo Monfort a
> > écrit :
> >> That's not true. libproxy can autodetect the proxy configuration from
> >> several
> >> plac
On 23/09/10 23:45, Josselin Mouette wrote:
> Le jeudi 23 septembre 2010 à 19:55 +0200, Emilio Pozuelo Monfort a
> écrit :
>> That's not true. libproxy can autodetect the proxy configuration from several
>> places, libmozjs being one of them. But if you don't have it, it can still
>> autodetect it
Le jeudi 23 septembre 2010 à 19:55 +0200, Emilio Pozuelo Monfort a
écrit :
> That's not true. libproxy can autodetect the proxy configuration from several
> places, libmozjs being one of them. But if you don't have it, it can still
> autodetect it from GConf (for GNOME), some KDE mechanism (I'm no
I'm running GNOME, and I'm configuring my proxy settings through
the GNOME Network Proxy preferences that is in the menu. I think
the following steps would get you where I ended up:
1. Install Debian testing with a Desktop Environment (GNOME).
2. Set the automatic proxy configuration URL through
Hi,
Please, CC the bug report in your replies.
On 23/09/10 20:52, Anye Li wrote:
> Thanks for the speedy response.
>
>> (I'm not a KDE guy!), your environment, a configuration file... so we
>> don't force anything to be installed, because you most likely have
>> installed something so that libpr
On 23/09/10 19:34, Anye Li wrote:
> The libproxy0 package does not depend on libmozjs2d but cannot
> process automatic proxy configurations without it. If you
> remove iceweasel and dependencies down to libmozjs2d, you
> will lose support for automatic proxy configuration and it
> is not obvious w
Package: libproxy0
Version: 0.3.1-1
Severity: important
The libproxy0 package does not depend on libmozjs2d but cannot
process automatic proxy configurations without it. If you
remove iceweasel and dependencies down to libmozjs2d, you
will lose support for automatic proxy configuration and it
is
12 matches
Mail list logo
