On 26/01/17 20:42, Maarten wrote:
Great, didn't know that about rpmfusion now doing el7. Anyone know if
nux-desktop repo and rpmfusion can be mixed together? It's not mentioned
on their FAQ.
Quote from the announcement on the rpmfusion list - I forget how to get
a link:
"While bootstrapping
Great, didn't know that about rpmfusion now doing el7. Anyone know if
nux-desktop repo and rpmfusion can be mixed together? It's not mentioned
on their FAQ.
On 2017-01-26 21:32, John Pilkington wrote:
On 26/01/17 20:02, Yasha Karant wrote:
Yesterday afternoon, I did a successful update
On 26/01/17 20:02, Yasha Karant wrote:
Yesterday afternoon, I did a successful update from production 7.2 to
production 7.3 through yumex. In addition to the SL production
repositories, I use the epel, elrepo, and google-chrome repositories for
specific add-ons, including nvidia support. I
You sent the email and it arrived at the mailinglist:
From: Pat Riehecky
Subject: Scientific Linux 7.3 x86_64 is officially released
To:
Message-ID:
Date: Wed, 25 Jan 2017 14:21:28
Yesterday afternoon, I did a successful update from production 7.2 to
production 7.3 through yumex. In addition to the SL production
repositories, I use the epel, elrepo, and google-chrome repositories for
specific add-ons, including nvidia support. I only use kernels from
SL. Although the
Yes, that seemed to fix it... Not sure what the new messages about the
kernel are that I now see on "check-update" but not on "update"...
Gilbert
[root@localhost ~]# yum --enablerepo=* clean expire-cache
Loaded plugins: langpacks
Cleaning repos: epel epel-debuginfo epel-source epel-testing
lsb_release comes out of redhat-lsb-core .
Description : The Linux Standard Base (LSB) Core module support provides the
: fundamental system interfaces, libraries, and runtime
environment
: upon which all conforming applications and libraries depend.
Personally, I put
On Jan 26, 2017, at 17:17 , Pat Riehecky wrote:
> On 01/26/2017 10:15 AM, Stephan Wiesand wrote:
>> On Jan 26, 2017, at 16:32 , Maarten wrote:
>>
>>> And great work for releasing 7.3!! :)
>> Has it actually been released? Can't find an announcement to that effect...
>
> It is out officially,
Can I have you send me the output of the following:
yum --enablerepo=* clean expire-cache
yum repolist
lsb_release -a
cat /etc/yum/vars/slreleasever
yum makecache
find /var/cache/yum/x86_64/ -type f -name repomd.xml -ls -exec sha1sum {} \;
Pat
On 01/26/2017 10:06 AM, Gilbert E. Detillieux
On 01/26/2017 10:15 AM, Stephan Wiesand wrote:
On Jan 26, 2017, at 16:32 , Maarten wrote:
And great work for releasing 7.3!! :)
Has it actually been released? Can't find an announcement to that effect...
It is out officially, I'll see if the email went missing somewhere.
Pat
On Jan 26, 2017, at 16:32 , Maarten wrote:
> And great work for releasing 7.3!! :)
Has it actually been released? Can't find an announcement to that effect...
Pat, I'm seeing these same errors, even after a "yum clean all". This
is just since yesterday's upgrade from SL 7.2 to 7.3, on many boxes.
Gilbert
On 26/01/2017 8:39 AM, Pat Riehecky wrote:
Hello,
Can I have you run a
yum clean all
and see if the problem persists?
Pat
On 01/26/2017
Hello Pat,
Shortly after I sent that mail I thought why not try that first. That
worked, thanks!
And great work for releasing 7.3!! :)
Maarten
On 2017-01-26 15:39, Pat Riehecky wrote:
Hello,
Can I have you run a
yum clean all
and see if the problem persists?
Pat
On 01/26/2017 01:12
Hello,
Can I have you run a
yum clean all
and see if the problem persists?
Pat
On 01/26/2017 01:12 AM, Maarten wrote:
What do these messages mean? It says to contact the repo owner?
etc/cron.daily/0yum-daily.cron:
Not using downloaded repomd.xml because it is older than what we have:
Dear Shane,
Thanks for your suggestion, it makes sense. I maybe need to explore it a bit
further, but so far I’ve not had much success. Trying this in the shell where
these aliases did not work:
$ shopt | grep aliases
expand_aliases on
On top of that, aliases that are defined in ~/.bashrc
Dear Lionel,
I have aliases defined in .sh files in my /etc/profile.d/ folder. When I log in
on my computer directly in either KDE or Gnome, in any terminal (I tried
Konsole, x-term and a few others), these aliases are not working (not set, I
assume). Other commands in the same .sh files
Dear SL users,
I have a strange error and don’t know where to start looking. Google didn’t
help this time. It seems to be distro-specific so I try to get help here.
I’m running sl7.2, patched, updated, etc. with the latest kernel:
$ uname -a
Linux 3.10.0-514.6.1.el7.x86_64 #1 SMP Tue Jan
17 matches
Mail list logo