Bug 1430489 - libcurl backend
Summary: libcurl backend
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-08 18:27 UTC by Colin Walters
Modified: 2017-04-01 17:29 UTC (History)
6 users (show)

Fixed In Version: NetworkManager-1.8.0-0.1.fc26
Clone Of:
Environment:
Last Closed: 2017-04-01 17:29:44 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 752642 0 None None None 2017-03-08 19:30:54 UTC

Description Colin Walters 2017-03-08 18:27:14 UTC 
For Fedora Atomic Host today, both ostree and NetworkManager depend on libsoup.  ostree now has a libcurl backend: https://github.com/ostreedev/ostree/pull/641

I'd like to have a NM libcurl-based connectivity check.  Build time option?  I'm potentially willing to do some of the work here if necessary.
Comment 1 Thomas Haller 2017-03-08 19:30:54 UTC 
this is certainly a good idea.

Upstream RFE: https://bugzilla.gnome.org/show_bug.cgi?id=752642
Comment 2 Fedora Update System 2017-03-23 17:48:10 UTC 
NetworkManager-1.8.0-0.1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-a19e0da955
Comment 3 Fedora Update System 2017-03-24 14:52:24 UTC 
NetworkManager-1.8.0-0.1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-a19e0da955
Comment 4 Fedora Update System 2017-04-01 17:29:44 UTC 
NetworkManager-1.8.0-0.1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.