Launchpad itself

Can technical-ezekiel33 please be banned from *-backports trackers and his bugs deleted?

Asked by Michael Casadevall

technical-ezekiel33 has been spamming the fiesty and gutsy backport trackers, with non-sensical bugs marked needs-packaging. He was mailed multiple times to stop it, and that none of his subscriptions made valid backporting requests. I ask that be please be banned from the backport trackers, and all bugs opened by him please be deleted. There is so much spam on both trackers now to the point of unusability.

https://bugs.edge.launchpad.net/~technical-ezekiel33 - profile

The trackers currently spammed to hell; every bug that starts [needs-packaging] is spam on our trackers.
https://bugs.edge.launchpad.net/gutsy-backports
https://bugs.edge.launchpad.net/feisty-backports

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
[LEGACY] Canonical WebOps Edit question
Last query:
Last reply:
Revision history for this message
Steve McInerney (spm) said : 		#1

The account in question has been disabled.

Cheers!
- Steve

Revision history for this message
Michael Casadevall (mcasadevall) said : 		#2

If its possible, can his bugs be deleted from the database? If I ever search backports for a closed (invalid/wontfix bug), a lot of this spam can clog up the search results, mostly because he's filed more spam than there were of bug reports total. If not, then can every bug please be mass changed to invalid?

Revision history for this message
Björn Tillenius (bjornt) said : 		#3

It's not trivial to delete the bugs. Is it really a problem that it's marked Invalid? I guess my main quiestion is, why do want to search Invalid bugs?

Revision history for this message
Michael Casadevall (mcasadevall) said : 		#4

(I didn't see the response, probably got deleted in the spam tidewave my inbox had)

Being able to search invalid bugs in backports allows us to find old reports. I'll settle for having everything marked invalid, but removal is perferred.

Revision history for this message
Gary Poster (gary) said : 		#5

Because you indicated that the "invalid" option is acceptable, I am marking this bug as "solved".