Problem: cannot install the best update candidate for package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64 - nothing provides atomic-registries >= 1.19.1-6 needed by docker-2:1.13.1-44.git584d391.fc27.x86_64
Problem: cannot install the best update candidate for package docker-2:1.13.1-26.gitb5e3294.fc27.x86_64
- nothing provides atomic-registries >= 1.19.1-6 needed by docker-2:1.13.1-42.git4402c09.fc27.x86_64
LGTM
Works for me.
Old extensions need to be updated to use WebExtensions API versions instead of XUL/NPAPI versions.
I'm using the ones from addons.mozilla.org for now (HTTPSEverywhere, ... etc).
LGTM.
Tested from Koji packages: Arabic text is working again.
Thanks.
This update broke the Arabic language rendering for some fonts (the letters are disconnected from each other).
It affects both GNOME Web (Epiphany) and Geary Mail.
LGTM.
The update is generally functional but I don't know what the "drag space" option does really and I hate that space above tabs (which the "drag space" option doesn't remove apparently) and the space added before tabs when restoring the window to its original size. The close button is still way above the whole row of tabs + buttons which is not consistent (testing with default Adwaita here, BTW).
LGTM.
Also fixes RHBZ Bug #1461407.
LGTM.
need some practice to train memory muscle to accommodate the new acceleration speeds after a long time of the old speeds. :)
LGTM.
local named volumes now work without SELinux alerts.
LGTM.
Same issue with PostgresQL official container and the named volumes.
Update this time contains "container-selinux" package which makes it functional to me.
@dwalsh I've tried to install the package through koji from the linked build which clearly doesn't contain the package container-selinux.
This package never hit the updates-testing repos. I'll test the new version that obsoleted this and see.
This update doesn't contain the container-selinux package:
Error: nothing provides container-selinux = 2:1.12.4-5.git1b5971a.fc25 needed by docker-2:1.12.4-5.git1b5971a.fc25.x86_64.
SELinux is still preventing docker to write to named volumes.
Named volumes still use the same old context container_var_lib_t.
@dustymabe same here.
Ignore the previous comment, I was setting the SELinux to Permissive the whole time to get my work done.
The volume directory still gets the same SELinux context, which leads to the same issue.
Is this update gonna land? or a year isn't enough?