On Tue, Dec 30, 2014 at 06:49:48PM +, Beartooth wrote:
> On Mon, 29 Dec 2014 15:03:07 -0700, Greg Woods wrote:
>
>
> >>
> >>
> >> Downloading failed: Didn't install any keys [root@localhost ~]#
> >>
> >> Clue, please?
> >>
> >>
> > I never could get the GPG part of the Rpmfusion repo
On 12/30/14 14:51, Robin Laing wrote:
On 2014-12-29 15:03, Greg Woods wrote:
Downloading failed: Didn't install any keys
[root@localhost ~]#
Clue, please?
I never could get the GPG part of the Rpmfusion repo to work with
fedup. I
ended up using --nogpgcheck (yes I am aware of th
On 2014-12-29 15:03, Greg Woods wrote:
Downloading failed: Didn't install any keys
[root@localhost ~]#
Clue, please?
I never could get the GPG part of the Rpmfusion repo to work with fedup. I
ended up using --nogpgcheck (yes I am aware of the risks of doing that) so
that I could g
On Mon, 29 Dec 2014 15:03:07 -0700, Greg Woods wrote:
>>
>>
>> Downloading failed: Didn't install any keys [root@localhost ~]#
>>
>> Clue, please?
>>
>>
> I never could get the GPG part of the Rpmfusion repo to work with fedup.
> I ended up using --nogpgcheck (yes I am aware of the risks
>
>
>
> Downloading failed: Didn't install any keys
> [root@localhost ~]#
>
> Clue, please?
>
I never could get the GPG part of the Rpmfusion repo to work with fedup. I
ended up using --nogpgcheck (yes I am aware of the risks of doing that) so
that I could get fedup to complete. Once I had
There must be something obvious here that I don't see :
Complete!
[i.e., machine had just been fully updated.]
[root@localhost ~]# fedup --network 21 --product=nonproduct
setting up repos...
getting boot images...
.treeinfo.signed
