On Sat, Jul 22, 2017 at 01:42:11PM -0600, Chris Murphy wrote:
> I don't know what things the unprivileged user can do other than
> search and info. But off hand I'd say an unprivileged user should not
> be able to download metadata. Use one /var/cache/dnf always. And if
> it's stale, just inform the user. Only update the cache if the command
> is issued by root.
I dunno; what harm is there in giving the ability to use a separate
user cache for queries? This allows you to do things like repoquery as
an unprivileged user for repos that aren't enabled by default.
> And then, dnf make cache timer is only keeping the /var/cache/dnf copy
> up to date. So the user copy is always going stale anyway.
Yeah, that's part of the bad experience here, definitely.
Hmmmm. The `dnf -C` (or --cacheonly) flag does not seem to work as
documented. It says:
-C, --cacheonly
Run entirely from system cache, don't update the cache
and use it even in case it is expired.
DNF uses a separate cache for each user under which it
executes. The cache for the root user is called the
system cache. This switch allows a regular user read-only
access to the system cache which usually is more fresh
than the user's and thus he does not have to wait for
metadata sync.
but in practice:
$ dnf clean metadata
Cache was expired
0 files removed
$ dnf -C info
Error: Cache-only enabled but no cache for 'updates-testing'
https://bugzilla.redhat.com/show_bug.cgi?id=1473964
--
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
