Closed GoogleCodeExporter closed 8 years ago
I think you need more steps to reproduce this. Maybe something like:
1) Have internal SUS with Safari 5.0.2 as latest available Safari.
2) Let softwareupdate -d -a run in the background (either via munki or via
normal Apple Software Update scheduled runs)
3) Install Safari 5.0.4 via some non-munki/ ASUS mechanism (manually, for
example)
4) Check for updates with MSU
5) MSU uses results of last `softwareupdate -d -a` run.
If/when you see this issue, and you run `sudo softwareupdate -d -a`, does the
issue go away?
Unless we get some more info, this looks like a duplicate of issue 58...
Original comment by gregnea...@mac.com
on 28 Mar 2011 at 9:17
I don't have the infrastructure immediately available to test that; didn't see
issue 58. Will see what I can discover. Thank you for a quick response.
Original comment by seth.mat...@gmail.com
on 28 Mar 2011 at 9:27
This should be addressed with the new Apple software update mechanism merged to
trunk in r1259.
Original comment by gregnea...@mac.com
on 2 Aug 2011 at 4:16
Original issue reported on code.google.com by
seth.mat...@gmail.com
on 28 Mar 2011 at 9:08