[Bug 5269] may need to have separate mirror sets for differing versions of same channel
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5269 [EMAIL PROTECTED] changed: What|Removed |Added Severity|major |blocker --- Additional Comments From [EMAIL PROTECTED] 2007-01-03 02:31 --- 'First, we can fix the whole issue through the use of a while statement (or an if statement at a minimum), so I don't think we need to go redesigning the idea of what an update revision is, nor do we need to separate 3.1 and 3.2 updates in different channels, etc.' If we use a while statement, that assumes (a) there will never be a race condition between backend update generation scripts for 3.1.x, 3.2.x (and 3.3.x, 3.4.x et al) (b) all those scripts write their output to the same filesystem, one that is race-immune (like a POSIX fs), and to the same directory path -- ie. not synced into place So we're locking down update generation, basically, to always happen on the same machine. 'This is a relatively simple problem that happens infrequently, so let's keep the solution simple as well.' Well, if you ask me, race conditions are not simple. Things would look less simple when you have to add race-avoidance locking to that while loop. Anyway, go ahead and take a shot at it. The 3.2.x updates won't work until this happens, so marking as a blocker. FWIW, the code worked fine, apart from the warning... ;) --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
[Bug 5269] may need to have separate mirror sets for differing versions of same channel
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5269 [EMAIL PROTECTED] changed: What|Removed |Added Target Milestone|Undefined |3.2.0 --- Additional Comments From [EMAIL PROTECTED] 2007-01-02 09:39 --- : jm 153...; svn commit -m bug 5629: scope v3.2.0 updates with a 'magic' string so they won't collide with 3.1.x updates (or any future 3.3.x, 3.4.x, etc line) sa-update.raw build/mkupdates/run_* Sendingbuild/mkupdates/run_part2 Sendingsa-update.raw Transmitting file data .. Committed revision 491858. It should work, but I'm waiting for various timeouts and TTLs to expire before I can perform a real update to verify it's working in the live setup. --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
[Bug 5269] may need to have separate mirror sets for differing versions of same channel
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5269 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2007-01-02 09:41 --- eh, marking FIXED anyway. feel free to use this as a venue for discussion of the multiple mirrors records question though --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
[Bug 5269] may need to have separate mirror sets for differing versions of same channel
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5269 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Additional Comments From [EMAIL PROTECTED] 2007-01-02 17:10 --- -1 First, we can fix the whole issue through the use of a while statement (or an if statement at a minimum), so I don't think we need to go redesigning the idea of what an update revision is, nor do we need to separate 3.1 and 3.2 updates in different channels, etc. This is a relatively simple problem that happens infrequently, so let's keep the solution simple as well. Second, this change doesn't work anyway. sa-update assumes the revision to be a number, and compares things numerically, so you get warnings when there's a string instead. For example: [26472] dbg: dns: 0.2.3.updates.spamassassin.org = 491858_v32x, parsed as 491858_v32x Argument 491858_v32x isn't numeric in numeric ge (=) at /home/felicity/SA/spamassassin-head/sa-update.raw line 435. I'm going to revert out this change for now: Sendingbuild/mkupdates/run_part2 Sendingsa-update.raw Transmitting file data .. Committed revision 491999. --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
