I think that probably the most productive thing would be to get a
reproducible test case in the hands of the libcurl Fedora maintainer
and ostree developers- e..g, figure out what parts of your network
configuration are relevant.
I wouldn't mind seeing a WG ticket tracking this.
On Thu, Jul 11, 2019 at 9:26 PM Chris Murphy <lists(a)colorremedies.com> wrote:
> I haven't been able to install flatpaks on a clean installation of
> Fedora 30 for a month now. This bug has the most complete and recent
> The biggest issue is no one really knows exactly what the problem is
> so there's a lot of finger pointing, most of it centered on libcurl
> version. Supposedly the fix was backported to 7.64.0-8.fc30 but that
> hasn't actually fixed the problem; today a user reports that upstream
> master/7.65.2 did fix the problem. But what's the policy for rebasing
> to that? Is the Fedora libcurl maintainer expected to figure out what
> fixes it and backport it? The verbose output is not that helpful, and
> libcurl folks are like, this is too complicated with too many layers,
> try to reproduce it with libcurl directly - and I'm like, that's
> pretty unlikely.
> Perhaps more likely is maybe asking this user to bisect and find out
> the good commit that fixes the problem, and ask the Fedora libcurl
> maintainer to backport that?
> Anyway, if it's better for me to file a WG issue and we can discuss it
> at Monday's meeting, I'll do that.
> Chris Murphy
> desktop mailing list -- desktop(a)lists.fedoraproject.org
> To unsubscribe send an email to desktop-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: