5:44 a.m.
Just updated about 40 packages.
Kernel to 4.0.8-300.fc22.x86_64
akmods now at 0.5.2 release 1.fc2
Updated via the GUI, rather than dnf on cmd line.
Same problem, the sad face.
Same fix, root, non-gui
# akmods --force
HTH
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
6:22 a.m.
On 07/19/15 13:44, Dave Pawson wrote:
Just updated about 40 packages.
Kernel to 4.0.8-300.fc22.x86_64
akmods now at 0.5.2 release 1.fc2
Updated via the GUI, rather than dnf on cmd line.
Same problem, the sad face.
Same fix, root, non-gui
# akmods --force
FWIW, the KDE/gui updated worked on one system here....but not on a second system.
Also, akmods.service akmods-shutdown.service being enabled didn't result in the
rpm's being installed on reboot.
Reverting to manually doing things before reboot.
Oh, well....
2:17 p.m.
On Sun, Jul 19, 2015 at 12:44 AM, Dave Pawson <dave.pawson(a)gmail.com> wrote:
Just updated about 40 packages.
Kernel to 4.0.8-300.fc22.x86_64
akmods now at 0.5.2 release 1.fc2
Updated via the GUI, rather than dnf on cmd line.
Same problem, the sad face.
Same fix, root, non-gui
# akmods --force
Yeah, I haven't addressed the failure problem yet. Got a highly
experimental package if you want to test? :)
Basically I added a conditional that if the RPM build, but doesn't install,
it still logs it as a failure but doesn't mark it as failed so it shouldn't
skip it during the boot service.
Thanks,
Richard
2:24 p.m.
On Sun, 19 Jul 2015 09:17:34 -0500
Richard Shaw wrote:
Basically I added a conditional that if the RPM build, but
doesn't install,
it still logs it as a failure but doesn't mark it as failed so it shouldn't
skip it during the boot service.
I'm about to try and build a dnf plugin that will wait for
dnf to finish, then run some random stuff.
I wonder if that would work for akmods as well - background itself
and monitor the dnf PID that started everything to wait for it
to exit, then run the build while no one has the rpm lock.
2:30 p.m.
On Sun, Jul 19, 2015 at 9:24 AM, Tom Horsley <horsley1953(a)gmail.com> wrote:
I'm about to try and build a dnf plugin that will wait for
dnf to finish, then run some random stuff.
I wonder if that would work for akmods as well - background itself
and monitor the dnf PID that started everything to wait for it
to exit, then run the build while no one has the rpm lock.
That would be ideal, but not something I know how to do.
Thanks,
Richard
2:56 p.m.
On Sun, 19 Jul 2015 09:30:34 -0500
Richard Shaw wrote:
> I wonder if that would work for akmods as well - background
itself
> and monitor the dnf PID that started everything to wait for it
> to exit, then run the build while no one has the rpm lock.
>
That would be ideal, but not something I know how to do.
Well, if I was going to do it, I'd start by reading /proc/self/status
to find the PPid: line and get the parent pid off the end of
the line then check /proc/pid/cmdline for "python" and "dnf"
in which case that pid is the dnf process you want to wait
for, otherwise, look for the next PPid in /proc/pid/status
and keep backing up through parents till you find a dnf,
or hit PPid 1 in which case you aren't being run from dnf :-).
Once you find the pid, waiting for it is easier. Just
check and see if there is a directory /proc/pid every
so often and once it goes away dnf has finished running.
4:43 p.m.
Sorry Richard (told you I wasn't up on these things), more explicit
instructions please.
I'm guessing you want me to install akmod from ???
and then report back next time I update (using gui or dnf on cmd line?)
Bit further information...
When it did come back up, along with 'notifications' (your system has been
updated) there was a simple (not very informative) message saying
something was wrong (error -1 iirc?).
regards
On 19 July 2015 at 15:17, Richard Shaw <hobbes1069(a)gmail.com> wrote:
On Sun, Jul 19, 2015 at 12:44 AM, Dave Pawson
<dave.pawson(a)gmail.com> wrote:
>
> Just updated about 40 packages.
> Kernel to 4.0.8-300.fc22.x86_64
> akmods now at 0.5.2 release 1.fc2
>
> Updated via the GUI, rather than dnf on cmd line.
>
> Same problem, the sad face.
> Same fix, root, non-gui
> # akmods --force
Yeah, I haven't addressed the failure problem yet. Got a highly experimental
package if you want to test? :)
Basically I added a conditional that if the RPM build, but doesn't install,
it still logs it as a failure but doesn't mark it as failed so it shouldn't
skip it during the boot service.
Thanks,
Richard
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
3443
days inactive
3443
days old
rpmfusion-users@lists.rpmfusion.org
6 comments
4 participants
participants (4)
-
Dave Pawson -
Ed Greshko -
Richard Shaw -
Tom Horsley