Request VCS import triggers bug mail error

Bug #771575 reported by Matt Giuca on 2011-04-27
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

I just got a very confusing email from Launchpad and I believe it's a bug.

I registered the project 'dosbox' to import the DOSBox repository from Subversion. Then I registered a branch dosbox/trunk and set up an import from That created a branch with import status "Pending Review".

Then, I received an email from <email address hidden> with subject "New code import: dosbox/trunk" and the following contents:

Your message was rejected

---------- Forwarded message ----------
From: Matt Giuca <email address hidden>
To: <email address hidden>
Date: Wed, 27 Apr 2011 01:04:21 -0000
Subject: New code import: dosbox/trunk
A new subversion code import has been requested by Matt Giuca:

You are getting this email because you are a member of the vcs-imports team.

(end of email)

What I believe this means is that my registration triggered an automatic email to <email address hidden> with my own email address in the From field. I'm not sure why that email was sent, but apparently it is because <email address hidden> is in the vcs-imports team (I believe the last line of the email is addressed to launchpad-bugs, not myself).

However, because I am not authorised to post to launchpad-bugs, I got an automated reply from launchpad-bugs-owner telling me not to post there. This is quite confusing for people requesting imports as it implies that the import itself has been rejected.

j.c.sackett (jcsackett) on 2011-04-27
Changed in launchpad:
status: New → Triaged
importance: Undecided → High
Robert Collins (lifeless) wrote :

this was due to the way we (the LP developers) had some of our operational notifications configured. Sorry for the confusion and I believe we have fixed this now (we stopped using that list precisely because of that sort of backscatter).

Changed in launchpad:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions