I'm not seeing the errata version number problem (if you mean the numbers such as SLSA-2013:0983-1 for the recent firefox update) only the date issue. And you're right, if I use repoview on the SL mirror I'm using it has the correct date.
I'll move over to the spacewalk mailing list, thanks for the update
--
Jan-Albert
[cid:image31bc7c.JPG@58585d52.4da814fd][cid:image20c9b3.JPG@ae21a46e.46af7561]
Jan-Albert van Ree
Linux System Administrator
MARIN Support Group
MARIN
2, Haagsteeg
E j.a.v....@marin.nl<mailto:j.a.v....@marin.nl> P.O. Box 28 T +31 317 49 39
11
6700 AA Wageningen F +31 317 49 32 45
T +31 317 49 35 48 The Netherlands I www.marin.nl<http://www.marin.nl>
MARIN news: ‘Applied Hydrodynamics of Floating Offshore Structures’ course, Oct
9 - 11,
Houston<http://www.marin.nl/web/News/News-items/Applied-Hydrodynamics-of-Floating-Offshore-Structures-course-Oct-9-11-Houston.htm>
This e-mail may be confidential, privileged and/or protected by copyright. If
you are not the intended recipient, you should return it to the sender
immediately and delete your copy from your system.
________________________________
From: Paul Robert Marino [prmari...@gmail.com]
Sent: Monday, July 08, 2013 19:43
To: Ree, Jan-Albert van; SCIENTIFIC-LINUX-USERS@FNAL.GOV
Subject: Re: Problem with errata dates?
This is the wrong list for this question it should be on the spacewalk list but
to answer your question its a known issue with the repo-sync process. What you
will also notice is the version numbers on the errata's are incrementing in
spacewalk every time you do a repo sync.
There has been some discussion about fixing this on the developers list but as
far as I know no ones seriously started work on it yet because there doesn't
seem to be quorum yet on the dev list as to how it should be handled yet.
-- Sent from my HP Pre3
________________________________
On Jul 4, 2013 2:53 AM, Ree, Jan-Albert van <j.a.v....@marin.nl> wrote:
This morning our Spacewalk service sent out some emails , among them an errata
mail regarding SLSA-2013:0957-1
What I noticed in Spacewalk is that the Issued date is set at 1/1/70
Same is true for several others,
Bug Fix Advisory SLBA-2013:0835-1 selinux-policy bug fix update 1 1/1/70
Security Advisory SLSA-2013:0911-1 Important: kernel security update 4 1/1/70
Bug Fix Advisory SLBA-2013:0893-1 selinux-policy bug fix update 1 1/1/70
Bug Fix Advisory SLBA-2013:0909-1 selinux-policy bug fix update 4 1/1/70
Bug Fix Advisory SLBA-2013:1000-1 selinux-policy bug fix update 4 1/1/70
Security Advisory SLSA-2013:0983-1 Moderate: curl security update 4 1/1/70
Security Advisory SLSA-2013:0942-1 Moderate: krb5 security update 4 1/1/70
Security Advisory SLSA-2013:0957-1 Critical: java-1.7.0-openjdk security update
4 1/1/70
Security Advisory SLSA-2013:0981-1 Critical: firefox security update 4 1/1/70
Is there a reason these are set at 1/1/70 instead of it's normal issue date?
All these are coming from the sl6 security repository
ftp://ftp.scientificlinux.org/linux/scientific/6rolling/x86_64/updates/security/
Regards,
Jan-Albert van Ree
Linux System Administrator
MARIN Support Group
E mailto:j.a.v....@marin.nl
T +31 317 49 35 48
MARIN
2, Haagsteeg, P.O. Box 28, 6700 AA Wageningen, The Netherlands
T +31 317 49 39 11, F +31 317 49 32 45, I www.marin.nl
<<inline: image31bc7c.JPG>>
<<inline: image20c9b3.JPG>>
