On 2 Aug 2015, at 17:25, Reindl Harald <h.reindl(a)thelounge.net>
Am 02.08.2015 um 18:10 schrieb Barry Scott:
> On 30 Jul 2015, at 21:06, Radek Holy <rholy(a)redhat.com> wrote:
>> Can akmods.service simply wait for the RPM lock to be released? Sorry, if the
question is stupid, I am not familiar with akmod system.
why is it locked for no good reason at all
> I am assuming that the normal running of a Fedora system it is odd to have updates
> happening as part of a boot up. The exception to this rule is akmods that handles
> the problem of updating kernel modules after a new kernel is installed.
> If this assumption is reasonable, at least for now, then fixing dnf-makecache
> to use cron and to be off by default will make the world a happy and reliable place
> If my assumptions are wrong and dnf folks manage to keep their dnf-makecache in the
> Then akmods would be forced to work with this in the system
the dnf-cache timer is one of the dumbest things ever
* wasting bandwidth
* introducing other troubles
* completly useless at all
why do i need the cache refresehd until there
is a intention to install / update packages and
then the data my be outdated instead pull it *now*
see also https://bugzilla.redhat.com/show_bug.cgi?id=1187111
The last couple of emails on this thread are a continuation of a line of thought that
Radek Holý started in that bug report.
You are not alone in thinking this is a poorly thought out change to Fedora by the DNF
You might wish to comment on Fedora Devel list.