Hi there,
the command that actually was installed was "dnf install steam". I
resolve the issue meanwhile however. It seems really like my database
was damaged in some strange way as I had certain packages (these listed
here) in two different version for x86_64 installed on the system at the
same t
On 09/02/2017 04:32 AM, Florian Sievert wrote:
> Hi there,
>
> since last week, I got some issues when attempting to update the system.
> Multiple packages i686/x86_64 are conflicting with each other. I
> attempted to deinstall most of the i686 packages on that system, however
> when I try to reins
On 09/01/2017 01:32 PM, Florian Sievert wrote:
since last week, I got some issues when attempting to update the system.
Multiple packages i686/x86_64 are conflicting with each other. I
attempted to deinstall most of the i686 packages on that system, however
when I try to reinstall steam again, it
On 09/01/2017 01:49 PM, Florian Sievert wrote:
Hi,
It looks like these packages expect that others are also being
upgraded, but the upgrades are still in testing. Most of the time,
when this happens, it corrects itself within a day or two.
Hm, this issue exist for nearly a week now for me. But
Hi,
> It looks like these packages expect that others are also being
> upgraded, but the upgrades are still in testing. Most of the time,
> when this happens, it corrects itself within a day or two.
Hm, this issue exist for nearly a week now for me. But okay, I might
give it a bit more time, even
On 09/01/2017 01:32 PM, Florian Sievert wrote:
Any ideas what might be broken here or how to fix this issue?
[Massive snippage of valuable error messages for brevity]
It looks like these packages expect that others are also being upgraded,
but the upgrades are still in testing. Most of the t
Hi there,
since last week, I got some issues when attempting to update the system.
Multiple packages i686/x86_64 are conflicting with each other. I
attempted to deinstall most of the i686 packages on that system, however
when I try to reinstall steam again, it tries to pull them in. I am
wondering
> When I run 'git commit', I have no more syntax highlighting. If I do
> set filetype=gitcommit, it still does not work.
I just checked that those files are NOT missing and are user readable:
/usr/share/vim/vim80/ftplugin/gitcommit.vim
/usr/share/vim/vim80/syntax/gitcommit.vim
Hi,
When I run 'git commit', I have no more syntax highlighting. If I do
set filetype=gitcommit, it still does not work.
The file name is .../.git/COMMIT_EDITMSG.
However 'git log | vim -' works with filetype=git.
Frédéric
___
users mailing list -- use
On Thu, Aug 31, 2017 at 9:44 PM, Christopher wrote:
> On Tue, Aug 29, 2017 at 8:26 AM Ed Greshko wrote:
>>
>> On 08/28/2017 05:16 PM, Ed Greshko wrote:
>> > On 08/28/2017 03:27 PM, Christopher wrote:
>> >> One interesting thing I noticed with this: if I hit "Backspace" a few
>> >> times before
>>
10 matches
Mail list logo