SCIENTIFIC-LINUX-USERS Archives

May 2018

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Winnie Lacesso <[log in to unmask]>
Reply To:
Date:
Fri, 25 May 2018 09:10:40 +0100
Content-Type:
TEXT/PLAIN
Parts/Attachments:
TEXT/PLAIN (40 lines)
Happy Friday!

Happening again:

[root@lcgnetmon02 ~]# yum clean all
Loaded plugins: fastestmirror
Cleaning repos: EGI-trustanchors sl sl-security
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos
Cleaning up list of fastest mirrors

[root@lcgnetmon02 ~]# yum check-update
Loaded plugins: fastestmirror
Determining fastest mirrors
 * sl: ftp2.scientificlinux.org
 * sl-security: ftp2.scientificlinux.org
EGI-trustanchors                                                                     | 2.5 kB  00:00:00     
sl                                                                                   | 3.8 kB  00:00:00     
sl-security                                                                          | 2.9 kB  00:00:00     
(1/6): EGI-trustanchors/primary_db                                                   |  59 kB  00:00:00     
(2/6): sl-security/x86_64/updateinfo                                                 |  20 kB  00:00:00     
(3/6): sl/x86_64/group_gz                                                            | 113 kB  00:00:00     
(4/6): sl/x86_64/updateinfo                                                          | 2.5 MB  00:00:01     
(5/6): sl/x86_64/primary_db                                                          | 5.1 MB  00:00:04     
(6/6): sl-security/x86_64/primary_db                                                 | 1.3 MB  00:00:05     
Update notice SLBA-2018:0764-1 (from sl-security) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the sl-security repository.
If you are the owner, consider re-running the same command with --verbose to see the exact data that caused the conflict.


client info:
[root@lcgnetmon02 ~]# lsb_release -a
LSB Version:    :core-4.1-amd64:core-4.1-noarch
Distributor ID: Scientific
Description:    Scientific Linux release 7.5 (Nitrogen)
Release:        7.5
Codename:       Nitrogen

hopefully fix soon eh?

ATOM RSS1 RSS2