Now this is done, I'll look at sponsoring libproxy to unstable and then
hopefully syncing it - I think if the mozjs thing goes to Universe then
it should be ok, but I'll check to be sure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
This bug was fixed in the package libproxy - 0.4.13-0ubuntu1
---
libproxy (0.4.13-0ubuntu1) zesty; urgency=medium
[ FJKong ]
* New upstream release (LP: #1639000)
* Remove 3 Patches because of merging to upsteam:
- dont_segfault_on_exit.patch
- fix-mozjs-detection.patch
It's not hard to set one up, but you don't really need to have one -
libproxy comes with a tool to tell you what it would return ("proxy"?),
and you can just fiddle with the settings to test that.
FJ is working on this and I'll handle sponsoring, we will take it from
here, thanks.
--
You receive
I started on this months ago and pushed my changes to Debian svn, but I
don't have a proxy to test with.
https://anonscm.debian.org/viewvc/pkg-gnome/packages/unstable/libproxy/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags added: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libproxy in Ubuntu.
https://bugs.launchpad.net/bugs/1639000
Title:
New upstream release 0.4.13
Status in libproxy package in Ubuntu:
5 matches
Mail list logo