somebody else makes packages with my info in Changed-By that FTBFS and I get emails about it

Bug #375757 reported by Ryan Niebur
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Julian Edwards

Bug Description

16:45 < Ryan52> WTF
16:45 < Ryan52> launchpad is really annoying sometimes...
16:45 < Ryan52> so I have no clue why I'm getting these "build of blah" emails.
16:46 < Ryan52> apparently since I'm the person who packaged something in Debian I now get emails every time somebody builds the package in their PPA? where the first P stands for personal!?!?
16:46 * Ryan52 == confused
16:47 < Ryan52> does somebody understand why this happens? how do I turn it off?
16:48 < beuno> Ryan52, what's your launchpad id?
16:48 < Ryan52> ryan52
16:49 < beuno> Ryan52, and for what PPA are you getting emails?
16:49 -!- abentley [<email address hidden>] has quit [Read error: 113 (No route to host)]
16:49 -!- abentley1 [<email address hidden>] has joined #launchpad
16:50 -!- abentley1 is now known as abentley
16:50 < Ryan52> jeffreyratcliffe
16:51 < beuno> Ryan52, does the email explain on the footer why you are getting it?
16:52 < Ryan52> http://slexy.org/raw/s20FTBW3vY
16:52 < Ryan52> I don't think so..
16:53 < beuno> Ryan52, this does look like a bug
16
:53 < beuno> would you file it against: https://bugs.launchpad.net/soyuz
16:54 < beuno> please include a copy of that email
16:54 < Ryan52> well, presumably it emailed me because the .dsc that he uploaded (I'm guessing) has me in the Changed-By
16:54 < Ryan52> because he probably didn't change the changelog
16:54 < beuno> right
16:54 < beuno> which is the users' error, but it may be worth discussing how to prevent this
16:55 < beuno> at the very minimum, the email should explain why you're getting it
16:55 < beuno> and who to beat up :)
16:58 -!- tsimpson [n=stdin@ubuntu/member/stdin] has quit [Read error: 104 (Connection reset by peer)]
17:00 < Ryan52> meh, so I guess I have to either suck it up or /dev/null mail from launchpad?
17:00 < Ryan52> I hope this guy stops working on packages...
17:00 < beuno> Ryan52, no. File a bug, we can try and improve the situation
17:01 < beuno> we don't want Launchpad to be a spam vector
17:03 < Ryan52> ok

Date: Tue, 12 May 2009 19:54:35 -0000
From: Launchpad Buildd System <email address hidden>
Subject: [Build #1000763] amd64 build of libgoo-canvas-perl 0.06-1 in ubuntu
        hardy RELEASE (jeffreyratcliffe PPA)
To: <email address hidden>
Reply-To: Launchpad Buildd System <email address hidden>

 * Source Package: libgoo-canvas-perl
 * Version: 0.06-1
 * Architecture: amd64
 * Archive: jeffreyratcliffe PPA
 * Component: main
 * State: Failed to build
 * Duration: four minutes
 * Build Log: https://launchpad.net/~jeffreyratcliffe/+archive/ppa/+build/1000763/+files/buildlog_ubuntu-hardy-amd64.libgoo-canvas-perl_0.06-1_FAILEDTOBUILD.txt.gz
 * Builder: https://launchpad.net/builders/aprium
 * Source: not available

If you want further information about this situation, feel free to
contact a member of the Launchpad Buildd Administrators team.

--
amd64 build of libgoo-canvas-perl 0.06-1 in ubuntu hardy RELEASE
https://launchpad.net/~jeffreyratcliffe/+archive/ppa/+build/1000763

Tags: lp-soyuz
Changed in soyuz:
assignee: nobody → Julian Edwards (julian-edwards)
importance: Undecided → High
milestone: none → 2.2.5
status: New → Triaged
Changed in soyuz:
status: Triaged → In Progress
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit

Fixed in devel r8460.

Changed in soyuz:
status: In Progress → Fix Committed
Revision history for this message
Ryan Niebur (ryan52) wrote :

thanks!

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 375757] Re: somebody else makes packages with my info in Changed-By that FTBFS and I get emails about it

To clarify the fix I made, LP will now only send build failure notifications
to the changed-by person provided they are in the PPA's owning team.

Changed in soyuz:
status: Fix Committed → Fix Released
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.