Re: successful 7.3 update through yumex

[John Pilkington]

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 the EL7 repo, we've tried to look at existing
work, specially from the nux repo. Unfortunately we haven't received
any direct help from this contributor."

I ought to say that the nux packages have worked well for me.

.. and back on topic - if Yasha had his local repo enabled he should 
already have the packages he wants.  I didn't/don't.






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 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 update was slow, it taking a very long time for the
nvidia portion to complete cleanup (I left after a 5 minute wait), when
I came back this morning, everything appears to be working, including
applications that have not been touched since I first installed SL 7
(e.g., UCSF chimera, Weizmann grace).  The machine to which this was
done has a 802.3 wired connection to a USA university research
backbone.  The next thing to update is my laptop that has a 802.11
connection to a production network, significantly lower data rate.  Is
there any way to get a list of the required RPMs, download and burn
these to a DVD, and then have yumex use the DVDs, only going to the
network to get additional RPMs that turn out to be needed?

Yasha Karant


# cat /var/log/yum.log ?

yumex History shows I had 453 packages initially, then 86 more
security packages after a reboot.  I also had 1 auto and one manual
update of the same google-chrome-stable package earlier today.  Seems
strange.

rpmfusion announced support for el7 today.  Switching from nux looks
as if it could be 'interesting'

John P

Re: successful 7.3 update through yumex

[Maarten]

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 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 update was slow, it taking a very long time for the
nvidia portion to complete cleanup (I left after a 5 minute wait), 
when

I came back this morning, everything appears to be working, including
applications that have not been touched since I first installed SL 7
(e.g., UCSF chimera, Weizmann grace).  The machine to which this was
done has a 802.3 wired connection to a USA university research
backbone.  The next thing to update is my laptop that has a 802.11
connection to a production network, significantly lower data rate.  Is
there any way to get a list of the required RPMs, download and burn
these to a DVD, and then have yumex use the DVDs, only going to the
network to get additional RPMs that turn out to be needed?

Yasha Karant


# cat /var/log/yum.log ?

yumex History shows I had 453 packages initially, then 86 more
security packages after a reboot.  I also had 1 auto and one manual
update of the same google-chrome-stable package earlier today.  Seems
strange.

rpmfusion announced support for el7 today.  Switching from nux looks
as if it could be 'interesting'

John P

Re: successful 7.3 update through yumex

[John Pilkington]

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 only use kernels from
SL.  Although the update was slow, it taking a very long time for the
nvidia portion to complete cleanup (I left after a 5 minute wait), when
I came back this morning, everything appears to be working, including
applications that have not been touched since I first installed SL 7
(e.g., UCSF chimera, Weizmann grace).  The machine to which this was
done has a 802.3 wired connection to a USA university research
backbone.  The next thing to update is my laptop that has a 802.11
connection to a production network, significantly lower data rate.  Is
there any way to get a list of the required RPMs, download and burn
these to a DVD, and then have yumex use the DVDs, only going to the
network to get additional RPMs that turn out to be needed?

Yasha Karant


# cat /var/log/yum.log ?

yumex History shows I had 453 packages initially, then 86 more security 
packages after a reboot.  I also had 1 auto and one manual update of the 
same google-chrome-stable package earlier today.  Seems strange.


rpmfusion announced support for el7 today.  Switching from nux looks as 
if it could be 'interesting'


John P

Re: [SCIENTIFIC-LINUX-USERS] update notice?

[Maarten]

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 -0600



On 2017-01-26 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, I'll see if the email went missing somewhere.

Pat

successful 7.3 update through yumex

[Yasha Karant]

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 update was slow, it taking a very long time for the 
nvidia portion to complete cleanup (I left after a 5 minute wait), when 
I came back this morning, everything appears to be working, including 
applications that have not been touched since I first installed SL 7 
(e.g., UCSF chimera, Weizmann grace).  The machine to which this was 
done has a 802.3 wired connection to a USA university research 
backbone.  The next thing to update is my laptop that has a 802.11 
connection to a production network, significantly lower data rate.  Is 
there any way to get a list of the required RPMs, download and burn 
these to a DVD, and then have yumex use the DVDs, only going to the 
network to get additional RPMs that turn out to be needed?


Yasha Karant

<>

Re: [SCIENTIFIC-LINUX-USERS] update notice?

[Gilbert E. Detillieux]

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
  : epel-testing-debuginfo epel-testing-source repos 
repos-source sl

  : sl-debuginfo sl-extras sl-extras-debuginfo sl-extras-source
  : sl-fastbugs sl-rolling sl-rolling-fastbugs 
sl-rolling-security

  : sl-security sl-source sl-testing sl-testing-source
6 metadata files removed
[root@localhost ~]# yum check-update
Loaded plugins: langpacks
epel/x86_64/metalink |  12 kB 
00:00
repos| 3.0 kB 
00:00
sl   | 3.7 kB 
00:00
sl-extras| 3.0 kB 
00:00
sl-fastbugs  | 3.5 kB 
00:00
sl-security  | 2.9 kB 
00:00

Security: kernel-3.10.0-514.6.1.el7.x86_64 is an installed security update
Security: kernel-3.10.0-327.el7.x86_64 is the currently running version
[root@localhost ~]# yum update
Loaded plugins: langpacks
No packages marked for update
[root@localhost ~]# yum check-update
Loaded plugins: langpacks
Security: kernel-3.10.0-514.6.1.el7.x86_64 is an installed security update
Security: kernel-3.10.0-327.el7.x86_64 is the currently running version

On 26/01/2017 11:16 AM, Pat Riehecky wrote:

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 it on every system I manage.  But that is me, YMMV.

Based on what you've sent I think I've got it cleaned up.

Can you run:
yum --enablerepo=* clean expire-cache
yum check-update

and see if the problem is resolved?

Pat

On 01/26/2017 10:58 AM, Gilbert E. Detillieux wrote:

Pat,

I've attached two transcript files...  The first one (script.txt) is
from a newly set-up SL 7.2 system that I upgraded to 7.3 yesterday.
The other (script2.txt) is from an older system, that's gone through
upgrades from 7.1 to 7.2, then to 7.3, and has a more substantial set
of packages and repos installed.

I should add that I see the error messages about the update notices
when I run "yum check-update", but not when I run "yum update".  (I
think I was seeing it on the latter command as well, at least
initially, but it's possible that it stopped doing that on an earlier
run of "yum clean all" I ran yesterday.)  I don't know if that's to be
expected or not.

BTW, I don't seem to have the "lsb_release" command installed. Know
what package I might find that in?

Thanks,
Gilbert

On 26/01/2017 10:22 AM, Pat Riehecky wrote:

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 wrote:

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 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:
  Current   : Wed Jan 25 20:54:42 2017
  Downloaded: Wed Jan 25 20:54:25 2017
Update notice SLBA-2015:2562-1 (from sl-security) is broken, or a bad
duplicate, skipping.
You should report this problem to the owner of the sl-security
repository.
Update notice SLBA-2016:1445-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:1526-1 (from sl-security) is broken, or a bad
duplicate, skipping.

...

Update notice SLSA-2017:0021-1 (from sl-security) is broken, or a bad
duplicate, skipping.


--
Gilbert E. Detillieux   E-mail: 
Dept. of Computer Science   Web:http://www.cs.umanitoba.ca/~gedetil/
University of Manitoba  Phone:  (204)474-8161
Winnipeg MB CANADA  R3T 2N2 Fax:(204)474-7609

Re: [SCIENTIFIC-LINUX-USERS] update notice?

[Pat Riehecky]

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 it on every system I manage.  But that is me, YMMV.

Based on what you've sent I think I've got it cleaned up.

Can you run:
yum --enablerepo=* clean expire-cache
yum check-update

and see if the problem is resolved?

Pat

On 01/26/2017 10:58 AM, Gilbert E. Detillieux wrote:

Pat,

I've attached two transcript files...  The first one (script.txt) is 
from a newly set-up SL 7.2 system that I upgraded to 7.3 yesterday.  
The other (script2.txt) is from an older system, that's gone through 
upgrades from 7.1 to 7.2, then to 7.3, and has a more substantial set 
of packages and repos installed.


I should add that I see the error messages about the update notices 
when I run "yum check-update", but not when I run "yum update".  (I 
think I was seeing it on the latter command as well, at least 
initially, but it's possible that it stopped doing that on an earlier 
run of "yum clean all" I ran yesterday.)  I don't know if that's to be 
expected or not.


BTW, I don't seem to have the "lsb_release" command installed. Know 
what package I might find that in?


Thanks,
Gilbert

On 26/01/2017 10:22 AM, Pat Riehecky wrote:

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 wrote:

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 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:

  Current   : Wed Jan 25 20:54:42 2017
  Downloaded: Wed Jan 25 20:54:25 2017
Update notice SLBA-2015:2562-1 (from sl-security) is broken, or a bad
duplicate, skipping.
You should report this problem to the owner of the sl-security
repository.
Update notice SLBA-2016:1445-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:1526-1 (from sl-security) is broken, or a bad
duplicate, skipping.

...

Update notice SLSA-2017:0021-1 (from sl-security) is broken, or a bad
duplicate, skipping.

Re: [SCIENTIFIC-LINUX-USERS] update notice?

[Stephan Wiesand]

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, I'll see if the email went missing somewhere.


Nevermind, I see it in the listserv archive, so chances are the problem is at 
my end. 

Sorry for the noise, and thanks a lot for SL 7.3 and everything else!

Stephan

-- 
Stephan Wiesand
DESY -DV-
Platanenenallee 6
15738 Zeuthen, Germany

Re: [SCIENTIFIC-LINUX-USERS] update notice?

[Pat Riehecky]

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 wrote:
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 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:
  Current   : Wed Jan 25 20:54:42 2017
  Downloaded: Wed Jan 25 20:54:25 2017
Update notice SLBA-2015:2562-1 (from sl-security) is broken, or a bad
duplicate, skipping.
You should report this problem to the owner of the sl-security
repository.
Update notice SLBA-2016:1445-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:1526-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:1528-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:1540-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2096-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2168-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2171-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2184-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2187-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2211-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2257-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2267-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2276-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2285-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2290-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2331-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2356-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2374-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2396-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2397-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2403-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2404-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2431-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2443-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2446-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2467-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2471-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2526-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2536-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2611-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2612-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2660-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2879-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2015:2281-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:0154-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:0463-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:0517-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:0683-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:1982-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2053-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2154-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2158-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2266-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2275-1 (from sl-security) 

Re: [SCIENTIFIC-LINUX-USERS] update notice?

[Pat Riehecky]

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

Re: [SCIENTIFIC-LINUX-USERS] update notice?

[Stephan Wiesand]

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...

Re: [SCIENTIFIC-LINUX-USERS] update notice?

[Gilbert E. Detillieux]

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 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:
  Current   : Wed Jan 25 20:54:42 2017
  Downloaded: Wed Jan 25 20:54:25 2017
Update notice SLBA-2015:2562-1 (from sl-security) is broken, or a bad
duplicate, skipping.
You should report this problem to the owner of the sl-security
repository.
Update notice SLBA-2016:1445-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:1526-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:1528-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:1540-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2096-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2168-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2171-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2184-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2187-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2211-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2257-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2267-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2276-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2285-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2290-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2331-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2356-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2374-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2396-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2397-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2403-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2404-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2431-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2443-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2446-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2467-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2471-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2526-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2536-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2611-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2612-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2660-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLBA-2016:2879-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2015:2281-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:0154-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:0463-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:0517-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:0683-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:1982-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2053-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2154-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2158-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2266-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2275-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2277-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2278-1 (from sl-security) is broken, or a bad
duplicate, skipping.
Update notice SLEA-2016:2281-1 (from sl-security) is broken, or a bad

Re: [SCIENTIFIC-LINUX-USERS] update notice?

[Maarten]

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 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:
  Current   : Wed Jan 25 20:54:42 2017
  Downloaded: Wed Jan 25 20:54:25 2017
Update notice SLBA-2015:2562-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
You should report this problem to the owner of the sl-security 
repository.
Update notice SLBA-2016:1445-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:1526-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:1528-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:1540-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2096-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2168-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2171-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2184-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2187-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2211-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2257-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2267-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2276-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2285-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2290-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2331-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2356-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2374-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2396-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2397-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2403-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2404-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2431-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2443-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2446-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2467-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2471-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2526-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2536-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2611-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2612-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2660-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2879-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2015:2281-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:0154-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:0463-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:0517-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:0683-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:1982-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2053-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2154-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2158-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2266-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2275-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2277-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2278-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2281-1 

Re: [SCIENTIFIC-LINUX-USERS] update notice?

[Pat Riehecky]

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:
  Current   : Wed Jan 25 20:54:42 2017
  Downloaded: Wed Jan 25 20:54:25 2017
Update notice SLBA-2015:2562-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
You should report this problem to the owner of the sl-security 
repository.
Update notice SLBA-2016:1445-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:1526-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:1528-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:1540-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2096-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2168-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2171-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2184-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2187-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2211-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2257-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2267-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2276-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2285-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2290-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2331-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2356-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2374-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2396-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2397-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2403-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2404-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2431-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2443-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2446-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2467-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2471-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2526-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2536-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2611-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2612-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2660-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLBA-2016:2879-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2015:2281-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:0154-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:0463-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:0517-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:0683-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:1982-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2053-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2154-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2158-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2266-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2275-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2277-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2278-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2281-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2287-1 (from sl-security) is broken, or a bad 
duplicate, skipping.
Update notice SLEA-2016:2288-1 (from 

Re: Aliases in /etc/profile.d not read for one user in graphical mode

[Lionel Guy]

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 are actually working in 
all situations

I tried explicitly stating:

$ shopt -s expand_alisases

either in the shell or in /etc/profile, that didn’t work.

I also tried to move alias definitions in /etc/bashrc, to no avail.

I look at all the different shopt options, and there are two that are 
differently set in the shells where it works/doesn’t work are 

extglob
hostcomplete

But I don’t see how these might make a difference. I anyway tried to set them 
on/off explicitly in ~/etc/profile, but that didn’t work either.

I also tried to find a comprehensive guide of what happens when one logs in 
(which files are read, in what order, etc) but didn’t really got anything 
satisfying. Anyone who has a good suggestion?

Cheers,

Lionel



> On 26 Jan 2017, at 13:16 , Shane Voss  wrote:
> 
> 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 (like additions to $PATH) work 
>> fine.
>> 
>> When I log in with the same user through ssh, or directly on the computer on 
>> a text console (I don’t know how these are called: you access them through 
>> alt+ctrl+2 for example), or with another user in Gnome or KDE, the aliases 
>> work again.
> 
> The  man  page for bash says:
> 
>   Aliases  are not expanded when the shell is not interactive, unless the
>   expand_aliases shell option is set using shopt (see the description  of
>   shopt under SHELL BUILTIN COMMANDS below).
> 
> It looks to me as if some of your shells do not think they are interactive.
> 
>   Shane
> -- 
> Shane Voss, Computing Officer, School of GeoSciences, University of Edinburgh
> 
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
> 

--
Lionel Guy 
Rimbertsvägen 10C SE-75260 Uppsala | email: guy.lio...@gmail.com | mobile: +46 
(0)73 9760618 | phone: +46 (0)18 410 7398

Re: Aliases in /etc/profile.d not read for one user in graphical mode

[Shane Voss]

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 (like additions to $PATH) work 
fine.

When I log in with the same user through ssh, or directly on the computer on a 
text console (I don’t know how these are called: you access them through 
alt+ctrl+2 for example), or with another user in Gnome or KDE, the aliases work 
again.


The  man  page for bash says:

   Aliases  are not expanded when the shell is not interactive, unless the
   expand_aliases shell option is set using shopt (see the description  of
   shopt under SHELL BUILTIN COMMANDS below).

It looks to me as if some of your shells do not think they are interactive.

   Shane
--
Shane Voss, Computing Officer, School of GeoSciences, University of Edinburgh

The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Aliases in /etc/profile.d not read for one user in graphical mode

[Lionel Guy]

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 11:12:41 CST 2017 x86_64 
x86_64 x86_64 GNU/Linux

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 (like additions to $PATH) work 
fine. 

When I log in with the same user through ssh, or directly on the computer on a 
text console (I don’t know how these are called: you access them through 
alt+ctrl+2 for example), or with another user in Gnome or KDE, the aliases work 
again. 

I’m really puzzled. I tried to comment out all of my .bashrc file, log out and 
log in, to no avail.
My .bash_profile has just a standard . ~/.bashrc command:

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi

Any idea? I don’t even know where to start looking.

The error seemed to appear after the recent kernel upgrade (but I can’t really 
be sure that this is the event that triggered the error).

Best regards,

Lionel