On Tue, 2 Jan 2007 02:16:56 -0500, Theo Van Dinter <[EMAIL PROTECTED]> wrote:
>On Mon, Jan 01, 2007 at 07:11:03PM +0000, Justin Mason wrote: >> Looks like Theo pushed through updates for the wrong version in the 3.1.x >> channel ;) Give it an hour or so and it should be fixed. > >Um. No, I didn't. In fact, I upgraded my machines right after pushing >the upgrade. Doing a little digging, it appears that a 3.2.0 update >got pushed out with the same number and overwrote the 3.1 update. >Speciically: > >$ head -1 /var/lib/spamassassin/3.001007/updates_spamassassin_org.cf ># UPDATE version 491519 > >Looking at the updates dir: > >-r--r--r-- 1 updatesd other 118681 Jan 1 08:50 491519.tar.gz >-r--r--r-- 1 updatesd other 823 Jan 1 08:50 491519.tar.gz.asc >-r--r--r-- 1 updatesd other 84 Jan 1 08:50 491519.tar.gz.sha1 > >Untarring that file does show a 3.2 update tree. Note the time on the >file is 0850 GMT (0350 EST) on 1/1, and I pushed the update around 2030 >EST on 12/31. > >So ... Bug in JM's code, not checking if there's already an update with >that rev number? :P (looks like run_part2, lines 142-144 btw) It went in clean on all servers when I ran it this morning. I guess you fixed whatever the issue was? Kind regards Nigel
