Bug 970282

NOTE: Compile tested only.  

Here's the obvious spec file diff:

diff --git a/libproxy.spec b/libproxy.spec
index e72a400..74a3561 100644
--- a/libproxy.spec
+++ b/libproxy.spec
@@ -12,7 +12,7 @@
 
 Name:           libproxy
 Version:        0.4.11
-Release:        3%{?svn}%{?dist}
+Release:        4%{?svn}%{?dist}
 Summary:        A library handling all the details of proxy configuration
 
 Group:          System Environment/Libraries
@@ -21,6 +21,7 @@ URL:            http://code.google.com/p/libproxy/
 
 Source0:        http://libproxy.googlecode.com/files/libproxy-%{version}%{?svn}.tar.gz
 Patch0:         libproxy-0.4.10-mozjs.patch
+Patch1:         0001-pacrunner_mozjs-Also-support-mozjs-17.0.patch
 
 BuildRequires:  python-devel
 BuildRequires:  libmodman-devel >= 2.0.1
@@ -32,7 +33,7 @@ BuildRequires:  GConf2-devel
 BuildRequires:  libXmu-devel
 }
 # mozjs
-%{?_with_mozjs:BuildRequires: js-devel}
+%{?_with_mozjs:BuildRequires: mozjs17-devel}
 # NetworkManager
 %{?_with_networkmanager:
 BuildRequires:  NetworkManager-devel
@@ -171,6 +172,7 @@ developing applications that use %{name}.
 %prep
 %setup -q
 %patch0 -p1 -b .orig
+%patch1 -p1 -b .orig
 
 %build
 %{cmake} \

OK, please go ahead with f19/devel

BTW, there is still an issue if the libproxy-mozjs doesn't end in the install media. So it may be required by each Desktop Spin group.

(In reply to Nicolas Chauvet (kwizart) from comment #2)
> OK, please go ahead with f19/devel

Do you have a proxy configuration with PAC?  Can you test this before I upload it?

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

(In reply to Colin Walters from comment #1)

> -%{?_with_mozjs:BuildRequires: js-devel}
> +%{?_with_mozjs:BuildRequires: mozjs17-devel}

That would be better expressed as 
 BuildRequires: pkgconfig(mozjs-17.0)

It's easy enough to generate a PAC file to point to your local proxy. With squid running (a fairly basic install) on a local machine on my home network, I can throw together a PAC file in three lines:

function FindProxyForURL(url, host)
{
       return "PROXY twosheds.infradead.org:3128";
}

(In reply to David Woodhouse from comment #6)
> (In reply to Colin Walters from comment #1)
> 
> > -%{?_with_mozjs:BuildRequires: js-devel}
> > +%{?_with_mozjs:BuildRequires: mozjs17-devel}
> 
> That would be better expressed as 
>  BuildRequires: pkgconfig(mozjs-17.0)

True, but the rest of the BRs are not virtual.  I'd rather do this sort of conversion en-masse later across many spec files.

> It's easy enough to generate a PAC file to point to your local proxy. With
> squid running (a fairly basic install) on a local machine on my home
> network, I can throw together a PAC file in three lines:
> 
> function FindProxyForURL(url, host)
> {
>        return "PROXY twosheds.infradead.org:3128";
> }

Will try, thanks.

This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.