Translation template import emails sent to wrong person

Bug #768095 reported by Greg A
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

A little while ago I gave "maintainership" of the Libre.fm Lauchpad project to ~michael-sheldon. However I (regularlyish) get emails such as the one below, despite not having uploaded any translations.

Hello Greg Auger,

On 2011-04-21 06:50z (1 minutes ago), you uploaded a translation
template for nixtape in Libre.fm trunk in Launchpad.

The template has now been imported successfully.

Thank you,

The Launchpad team

I also got an email recently as below. I didn't personally upload a translation template as the email said, but I did submit a bzr branch to be merged (it was merged and published).

Hello Greg Auger,

On 2011-04-19 16:03z (16 hours 23 minutes ago), you uploaded a
translation template for tomboy in Ubuntu Natty package "tomboy" in
Launchpad.

The template has now been imported successfully.

Thank you,

The Launchpad team

Deryck Hodge (deryck)
Changed in launchpad:
status: New → Invalid
Revision history for this message
Deryck Hodge (deryck) wrote :

Sorry, Greg. I misread your comments. I've converted this back to a bug now.

Changed in launchpad:
status: Invalid → Triaged
importance: Undecided → Low
Revision history for this message
Martin Pool (mbp) wrote :

These specific examples were fixed bug bug 855150 but lp will still send mail about imports:

Possibilities (in rough order of preference):
 1- just stop sending mail about potemplate imports, and make sure any interesting stuff is visible in the web ui
 2- send mail only when people subscribe to translations mail for this project
 3- just don't send mail about it and do nothing (probably will make failures too obscure though)
 4- tweak the destination for failure mail: at the moment it's far too broad; we could make it narrower; the problem is I don't think lp currently has any concept of who would be interested (see #2)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.