On 01/08/2017 01:19 AM, Allan McRae wrote:
> The key probably expired... Just do "pacman-key --refresh-keys" on the
> install media.
>
> A
Roger WILCO,
Thanks A :)
--
David C. Rankin, J.D.,P.E.
On 08/01/17 17:11, David C. Rankin wrote:
> All,
>
> Attempting an arch install tonight, and I get the following at pacstrap /mnt
> What was this caused by? I had to boot from the 10/2016 iso. Is it a change
> in signatures since then? I'll download a new iso and try, but I'd be
>
All,
Attempting an arch install tonight, and I get the following at pacstrap /mnt
:: Proceed with installation? [Y/n]
:: Retrieving packages...
krb5-1.13.7-1-x86_64 1100.1 KiB 1405K/s 00:01
[##] 100%
libpsl-0.16.1-1-x86_64
I did:
sudo cp /usr/bin/gufw-pkexec /usr/bin/gufw-pkexec.old
Then sudo nano /usr/bin/gufw-pkexec
and edited it from:
. . .
"/usr/lib/python3.5/site-packages/gufw/gufw.py"
"/usr/lib/python3.5/dist-packages/gufw/gufw.py"
. . .
to:
. . .
"/usr/lib/python3.6/site-packages/gufw/gufw.py"
On Sat, 2017-01-07 at 12:03 +0100, Jelle van der Waa wrote:
> On 01/07/17 at 02:36am, Phil Wyett via arch-general wrote:
> > Workaround...
> >
> > In terminal:
> >
> > sudo python /usr/lib/python3.6/site-packages/gufw/gufw.py
>
> This generates a new pyc file, so beware of conflicts when
On 01/07/17 at 02:36am, Phil Wyett via arch-general wrote:
> Workaround...
>
> In terminal:
>
> sudo python /usr/lib/python3.6/site-packages/gufw/gufw.py
This generates a new pyc file, so beware of conflicts when updating to a
new gufw package. You will have to use the --force :)
--
Jelle van
6 matches
Mail list logo