** Changed in: libproxy (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/547106
Title:
Please upgrade libproxy to 0.4.x
To manage notifications about this
** Changed in: libproxy (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/547106
Title:
Please upgrade libproxy to 0.4.x
To manage notifications about
** Changed in: libproxy (Ubuntu)
Assignee: Ken VanDine (ken-vandine) = (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/547106
Title:
Please upgrade libproxy to 0.4.x
To manage
Ken, could you have a look to that update this cycle? The old version
isn't compatible with GNOME3, see i.e bug #893031, so we will have to do
the update
** Changed in: libproxy (Ubuntu Precise)
Assignee: Canonical Desktop Team (canonical-desktop-team) = Ken VanDine
(ken-vandine)
** No
Brian, the update is not blocked on Debian, it's blocked on having
somebody with time or interest for libproxy wanting to do the update
** Changed in: libproxy (Ubuntu)
Importance: Wishlist = High
** Also affects: libproxy (Ubuntu Precise)
Importance: High
Status: Confirmed
**
I think bug 304889 is actually the main one, CMs need an up-to-date
libproxy backend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/547106
Title:
Please upgrade libproxy to 0.4.x
To manage
~sigh~ My mistake for listening to Nerb_bloke. Sorry for the rant in
that case.
I guess it would have been nice if somebody spoke up and explained it
was not being updated simply due to manpower and not silly policy
stupidity. This bug has been open for almost 2 years now with several
long
OK. So this policy that Canonical (i.e. Ubuntu) won't update libproxy
until Debian does is just stupid.
Waiting for libproxy 0.4.7 in Debian (http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=604934) is just another case of some Debian
idealist who is letting his desire for the *perfect*
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libproxy (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/547106
Title:
Look. libproxy 0.3.1 is broken and obsolete. The developers of it have
completely abandoned it and are not making any fixes to it, and it's
broken!
Current release of libproxy is 0.4.7. Why are you so stubbornly
refusing to update even future releases like Natty+1 with the currently
maintained
Canonical won't update until they can pull from Debian, that is why its
bug is linked here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/547106
Title:
Please upgrade libproxy to 0.4.x
To manage
On 11-09-16 07:46 AM, Nerd_bloke wrote:
Canonical won't update until they can pull from Debian, that is why its
bug is linked here.
But my O/S vendor is Canonical, not Debian. If I wanted to have to deal
with the Debian political quagmire, I'd install a Debian O/S. Why is
Canonical not
** Changed in: libproxy (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/547106
Title:
Please upgrade libproxy to 0.4.x
--
ubuntu-bugs mailing list
13 matches
Mail list logo
