On Wed, 2014-11-12 at 09:30 +0800, Ed Greshko wrote:
> On 11/12/14 09:20, Rex Dieter wrote:
> > Ed Greshko wrote:
> >
> >> I'm running an F20/KDE VM with sddm-0.10.0-2.fc20 installed from
> >> updates-testing.
> >>
> >> In trying to do a
> >>
> >> fedup --network 21 --product=nonproduct
> >>
> >> I
On 11/12/14 09:11, Sérgio Basto wrote:
> no, should be reported against sddm , is not fedup fault
OK, that makes sense. Confusing the "process" with the "program". :-)
--
If you can't laugh at yourself, others will gladly oblige.
--
test mailing list
test@lists.fedoraproject.org
To unsubscr
On 11/12/14 09:20, Rex Dieter wrote:
> Ed Greshko wrote:
>
>> I'm running an F20/KDE VM with sddm-0.10.0-2.fc20 installed from
>> updates-testing.
>>
>> In trying to do a
>>
>> fedup --network 21 --product=nonproduct
>>
>> I get
>>
>> WARNING: potential problems with upgrade
>> sddm-0.10.0-2.
Ed Greshko wrote:
> I'm running an F20/KDE VM with sddm-0.10.0-2.fc20 installed from
> updates-testing.
>
> In trying to do a
>
> fedup --network 21 --product=nonproduct
>
> I get
>
> WARNING: potential problems with upgrade
> sddm-0.10.0-2.fc20.x86_64 (no replacement) requires
> libxc
On Qua, 2014-11-12 at 08:59 +0800, Ed Greshko wrote:
> I'm running an F20/KDE VM with sddm-0.10.0-2.fc20 installed from
> updates-testing.
>
> In trying to do a
>
> fedup --network 21 --product=nonproduct
>
> I get
>
> WARNING: potential problems with upgrade
> sddm-0.10.0-2.fc20.x86_64
I'm running an F20/KDE VM with sddm-0.10.0-2.fc20 installed from
updates-testing.
In trying to do a
fedup --network 21 --product=nonproduct
I get
WARNING: potential problems with upgrade
sddm-0.10.0-2.fc20.x86_64 (no replacement) requires
libxcb-1.9.1-3.fc20.x86_64 (replaced by libxcb-1