Displaying 5 results from an estimated 5 matches for "fc40".
Did you mean:
fc4
2024 Aug 15
2
Certificates are not trusted
...Expired on 2024-08-13T00:46:08Z
De GPG-sleutels bedoeld voor repository "Copr repo for cran owned by
iucar" zijn al ge?nstalleerd maar niet correct voor dit pakket.
Controleer of de juiste sleutel-URLs voor deze repository zijn
opgegeven.. Pakket dat mislukt is:
R-CRAN-kernlab-0.9.33-1.fc40.copr7906033.x86_64
GPG-sleutels zijn geconfigureerd als:
https://download.copr.fedorainfracloud.org/results/iucar/cran/pubkey.gpg
Publieke sleutel voor
R-CRAN-tseries-0.10.57-1.fc40.copr7906036.x86_64.rpm is niet vertrouwd.
Pakket dat mislukt is: R-CRAN-tseries-0.10.57-1.fc40.copr7906036.x86_6...
2024 Jul 27
1
Fedora 40 nut-server not starting at boot
...alled Fedora 40 desktop. Seems once the machine is up, I can
manually start with systemctl start nut-server and everythings fine.
dnf info nut
Last metadata expiration check: 2:08:11 ago on Sat 27 Jul 2024 03:48:13 PM
EDT.
Installed Packages
Name : nut
Version : 2.8.2
Release : 1.fc40
Architecture : x86_64
Size : 12 M
Source : nut-2.8.2-1.fc40.src.rpm
Repository : @System
>From repo : updates
Summary : Network UPS Tools
URL : https://www.networkupstools.org/
License : GPL-2.0-or-later AND GPL-3.0-or-later
Description : These programs are...
2024 Jul 29
2
Fedora 40 nut-server not starting at boot
...ed" in systemctl (IE "systemctl enable ....") is the
> nut.target entry.
>
Tim, can you show output of systemctl list-unit-files| grep nut
Some service has to be enabled to call nut.target I should think.
Also what version of the nut pkg is being used? I'm
using nut-2.8.2-1.fc40.x86_64.
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20240729/58870e5a/attachment.htm>
2024 Nov 10
2
NUT stopped working after an upgrade
Great!
Regarding libusb and nut-scanner, I think the *.so (exact) symlinks are
part of *-devel packages.
This was solved in NUT recently (maybe after 2.8.2 release already) by
detecting and stashing the basename of realpath of the library present
during build, so the exact *.so.X.Y.Z would be also tried.
Also, nut-scanner now (in 2.8.2 IIRC) should not suggest the volatile
bus/busport/device
2024 Jul 29
2
Fedora 40 nut-server not starting at boot
OK, looking at this on my RH8 test image . . .
The first thing that I note, is that the *only* thing that needed to be
set to "enabled" in systemctl (IE "systemctl enable ....") is the
nut.target entry.
All else here are disabled, and "drug along" by nut.target which ensures
that they come up in sequence.
In nut.target I added to the "After" and