On 07/07/2015 09:59 AM, Orion Poplawski wrote: > On 07/07/2015 08:13 AM, Pat Riehecky wrote: >> >> On 07/06/2015 05:15 PM, Orion Poplawski wrote: >>> On 06/29/2015 02:05 PM, Orion Poplawski wrote: >>>> On 06/29/2015 12:13 PM, Connie Sieh wrote: >>>>>> Update notice SLBA-2015:0404-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-2015:0556-1 (from sl-security) is broken, or a bad >>>>>> duplicate, skipping. >>>>>> >>>>>> -- >>>>>> Orion Poplawski >>>>>> Technical Manager 303-415-9701 x222 >>>>>> NWRA, Boulder/CoRA Office FAX: 303-415-9702 >>>>>> 3380 Mitchell Lane [log in to unmask] >>>>>> Boulder, CO 80301 http://www.nwra.com >>>>>> >>>>> Where are you seeing these? >>>>> >>>> yum-cron update output on SL 7.1 >>>> >>> More now: >>> >>> Update notice SLBA-2015:0364-2 (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-2015:0404-1 (from sl-security) is broken, or a bad >>> duplicate, skipping. >>> Update notice SLBA-2015:0556-1 (from sl-security) is broken, or a bad >>> duplicate, skipping. >>> >>> >> Just so I can make sure I'm hunting in all the right places, what is the >> output of lsb_release -r >> >> >> Pat >> > Release: 7.1 > > Seem to be in these files: > > /var/cache/yum/x86_64/7.1/sl/gen/updateinfo.xml > /var/cache/yum/x86_64/7.1/sl-security/gen/updateinfo.xml > hmmmm.... I'm not showing that update in the sl-security updateinfo.xml grep -l SLBA-2015:0364-2 updateinfo.xml grep -l SLBA-2015:0404-1 updateinfo.xml grep -l SLBA-2015:0556-1 updateinfo.xml can I have you run a yum clean all? Pat -- Pat Riehecky Scientific Linux developer Fermi National Accelerator Laboratory www.fnal.gov www.scientificlinux.org