Hi,
the latest upstream version of samba rpms for 5.2 is samba-3.0.28-1.el5_2.1. In the Centos 5.2 updates tree there is only samba-3.0.28-0.el5.8 which also is already part of the 5.2 os tree. Could it be that the updates tree just carries the wrong rpms?
Best regards, Bernd
on 6-25-2008 12:25 PM Bernd Bartmann spake the following:
Hi,
the latest upstream version of samba rpms for 5.2 is samba-3.0.28-1.el5_2.1. In the Centos 5.2 updates tree there is only samba-3.0.28-0.el5.8 which also is already part of the 5.2 os tree. Could it be that the updates tree just carries the wrong rpms?
Sometimes updates get a little behind during a new point release, but I'm sure someone will answer that knows better than I.
Scott Silva wrote:
on 6-25-2008 12:25 PM Bernd Bartmann spake the following:
Hi,
the latest upstream version of samba rpms for 5.2 is samba-3.0.28-1.el5_2.1. In the Centos 5.2 updates tree there is only samba-3.0.28-0.el5.8 which also is already part of the 5.2 os tree. Could it be that the updates tree just carries the wrong rpms?
Sometimes updates get a little behind during a new point release, but I'm sure someone will answer that knows better than I.
There are a few updates lagging, samba and sblim amongst them. The wrong packages are in the updates repo, but should cause no harm - its my mistake, an artifact from my testing of the yum-security plugin and how it handles same pkgs across repos got left behind in the updates repo when it was sync'd up. I'll remove the duplicate packages later, but the pending updates along with more recent ones should get announced and all pushed soon ( within the next 24 hrs )
the mirror network is also starting to stabalise after the release-rush, making it possible to actually do updates again :D
On Thu, Jun 26, 2008 at 1:27 AM, Karanbir Singh wrote:
There are a few updates lagging, samba and sblim amongst them. The wrong packages are in the updates repo, but should cause no harm - its my mistake, an artifact from my testing of the yum-security plugin and how it handles same pkgs across repos got left behind in the updates repo when it was sync'd up. I'll remove the duplicate packages later, but the pending updates along with more recent ones should get announced and all pushed soon ( within the next 24 hrs )
the mirror network is also starting to stabalise after the release-rush, making it possible to actually do updates again :D
Thanks for the clarification and another big "Thank you!" for all the hard work that you and all the other Centos developers are doing!
Best regards, Bernd.