Re: Attachment spam: do we want to edit history?
Ralf Schlatterbeck <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Sep 05, 2012 at 02:05:33PM -0400, John P. Rouillard wrote: > http://issues.roundup-tracker.org/issue2550731 > > which apparently has been spammed with attachements. Sigh. > > Ralf, any idea on how should I handle the attachment spam? If I just > delete/unlink the file from the ticket the data/link is still > accessible from the history. I've just written a script to completely remove file spam: http://roundup.hg.sourceforge.net/hgweb/roundup/roundup/rev/9f507a042c1b For matching spam, you *have* to give the issues involved (as designators, e.g., issue2550731) and you can specify exact filename, file-start, or username (creator) of files. It will - remove the file from the issue if not already deleted - remove *all* journal (history) entries for the file for the given issue - set the contents of the file to zero-length By default it only prints what it *would* do. It can be silenced with a --quiet option and to make it really do what it advertised you can specify a --no-dry-run option. It's also a good example of the roundup journal API. Before I try this out on our real tracker I'm asking all users: Do we really want to edit history in this way? I'm for it (for spam only). Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting www: http://www.runtux.com Reichergasse 131, A-3411 Weidling email: [email protected] osAlliance member email: [email protected] ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/