On Mon, 2 Oct 2017 23:50:25 +0200
"Patrick Dupre" wrote:
> I do not know what to do.
What's the output of this command?
grep enabled /etc/yum.repos.d/*.repo
If nothing else, you can go here,
https://koji.fedoraproject.org/koji/buildinfo?buildID=970458
download the appropriate binary rpms, an
On Mon, Oct 02, 2017 at 11:50:25PM +0200, Patrick Dupre wrote:
[...]
> Installing:
> nutx86_64 2.7.4-7.fc26 fedora 1.8
> M
> Installing dependencies:
> nut-client x86_64 2.7.4-14.fc26 updates 212
> k
> Transaction Summa
Every time, I get:
dnf install nut
Repository mgeups has no mirror or baseurl set.
Last metadata expiration check: 1:24:29 ago on Mon 02 Oct 2017 10:24:37 PM CEST.
Dependencies resolved.
PackageArch
On Mon, 2 Oct 2017 22:28:26 +0200, Patrick Dupre wrote:
> dnf install --refresh nut
It makes no sense to run that command before you see the latest packages
available in the "updates" repo.
Also, adding --refresh again and again only forces dnf to redownload
the repo metadata again and again, wh
> On Mon, 2 Oct 2017 21:23:44 +0200, Patrick Dupre wrote:
>
> > Sure,
> >
> > dnf list nut\*
> > Repository mgeups has no mirror or baseurl set.
> > Last metadata expiration check: 3 days, 9:44:08 ago on Fri 29 Sep 2017
> > 11:36:48 AM CEST.
> > Installed Packages
> > nut-cgi.x86_64
On Mon, 2 Oct 2017 21:23:44 +0200, Patrick Dupre wrote:
> Sure,
>
> dnf list nut\*
> Repository mgeups has no mirror or baseurl set.
> Last metadata expiration check: 3 days, 9:44:08 ago on Fri 29 Sep 2017
> 11:36:48 AM CEST.
> Installed Packages
> nut-cgi.x86_64 2.7.4-14
Sure,
dnf list nut\*
Repository mgeups has no mirror or baseurl set.
Last metadata expiration check: 3 days, 9:44:08 ago on Fri 29 Sep 2017 11:36:48
AM CEST.
Installed Packages
nut-cgi.x86_64 2.7.4-14.fc26@updates
nut-client.x86_64
On Fri, 29 Sep 2017 21:27:25 +0200, Patrick Dupre wrote:
> Installing:
> nutx86_642.7.4-7.fc26
> fedora1.8 M
>
This is only an old package in the base 'fedora' repo.
Why don't you troubleshoot this a bit more to lis
Il giorno lun, 02/10/2017 alle 23.26 +1030, Tim ha scritto:
> Do I gather that you get two different behaviours:
>
> Auto-restarting if you print directly from the printer server?
The printer it's connect to my workstation/server via USB cable
> Not auto-restarting if you print from a client PC?
Allegedly, on or about 2 October 2017, Dario Lesca sent:
> Into cups printer configuration file, I have set "ErrorPolicy retry-
> job". When I print to a printer power off, I do not want stop
> printer, I want cups still try to print until printer is power on.
>
> And this work great if I print on
Into cups printer configuration file, I have set "ErrorPolicy retry-
job". When I print to a printer power off, I do not want stop printer,
I want cups still try to print until printer is power on.
And this work great if I print on a Fedora server (without GUI).
If I print a document from gnome o
11 matches
Mail list logo