ahkok
ahkok
https://github.com/andelf/go-curl
It doesn't. It's easy to prove that it doesn't, either. Steps to reproduce: 1) open terminal and type `sudo busctl monitor | grep org.pacrunner.client` Note that you'll see messages here...
No, I didn't remove any working autoproxy in my replication case. All I did was replicate a properly new installed clearlinux system where autoproxy is working, and where mixer isn't...
I have no issues with additional ways to manually support proxies. But all our development tools must be able to work with autoproxy, and they don't. We've patched autospec before...
Ideally, docker doesn't go out on the network and has all the data it needs. Making docker go on a public network defies a large part of the reason why...
I think this is a core design problem when docker was implemented. The container shouldn't have to go out over the network. It should purely exist to 'do the root...
That's fine.
It seems unnecessary to duplicate the same source code file 7x. Perhaps we can make a temporary copy for each iteration and use that to validate, instead. Or even symlinks?
Does the new virt-manager perpaps require the split up files? Can we `strace` to see what paths/files it is looking for?
Reported upstream: https://gitlab.gnome.org/GNOME/gnome-disk-utility/issues/155