Package's maintainer don't receive any Accepted mail when a certain package is synced

Bug #408622 reported by Andrea Veri
This bug report is a duplicate of:  Bug #501: Subscribe to packages by email. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Incomplete
Undecided
Unassigned

Bug Description

I found out a small issue while processing some syncs. It seems that package's maintainer don't receive any ACCEPTED mail when a package gets synced into the archive both manually or by an automated import. It would be nice to have this fixed to allow maintainers who work in Ubuntu too to know when a package reached the archive or not preventing them to look at the package LP page.

Tags: lp-soyuz
Revision history for this message
William Grant (wgrant) wrote :

I suspect that this should be a duplicate of bug #501 -- emailing the maintainer by default is probably a bad idea.

Revision history for this message
Celso Providelo (cprov) wrote :

Andrea,

The code responsible for building the recipients for upload notification is at http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/annotate/head%3A/lib/lp/soyuz/model/queue.py#L985 (_getRecipients(changes))

It basically consider the 3 distinct *individuals* that can be involved with an uploader:

 * The uploader (Changed-by:)
 * The maintainer (Maintainer:)
 * The sponsor (owner of the key who signed the .changes)

For uploads to the primary archive, it includes the maintainer *if* the user has ever used LP and set his 'preferredemail'.

PPA uploads do not result in notification to the maintainer, because it's mosly likely that the Maintainer was not involved with the uploaded at all. It doesn't include the signer either, because there is no concept of sponsored uploads in PPAs. OTOH, the PPA upload is announced to any 3rd-part uploaders (user which were explicitly granted permission because they are not part of the team owning the PPA).

Summing up, it does notify maintainer who have opted to be notified. I know the workflow isn't clear enough and I'd be interested to know which circumstances have made you think they are not.

Celso Providelo (cprov)
Changed in soyuz:
status: New → Incomplete
Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 408622] Re: Package's maintainer don't receive any Accepted mail when a certain package is synced

On Tuesday 04 August 2009 01:14:39 William Grant wrote:
> I suspect that this should be a duplicate of bug #501 -- emailing the
> maintainer by default is probably a bad idea.

I agree with this.

In fact, the existing ArchiveSubscriber table will be extended at some point
to support all sorts of different subscriptions to an archive.

Revision history for this message
Andrea Veri (av) wrote :

well, I'm not really sure this is a perfect duplicate of Bug #501, my request was a bit different. Suppose, for istance, that I maintain some packages in Debian, they come to Ubuntu and someone asks for a manual sync or they even get automatically imported (cause no Ubuntu deltas to be merged). When that particular package hit the archive package's mantainer (me) don't get notified with any Accepted mail, so I have to open the package's LP page and check its status everytime I upload a new revision in Debian. Is what I mean a bit more clear?

@Celso
you were talking about 'upload notifications', but it looks like syncs are processed in a different way, if not I would receive the Accepted mail correctly (as the code reports). What I mean is that 'The maintainer (Maintainer:)' field do NOT receive any Accepted mail when the package gets *synced* and not uploaded normally into the archive.

Revision history for this message
Andrea Veri (av) wrote :

The only notification mails I received after a sync being processed is when the archive admin addressed me as Changed-by: but not with the other two fields you told me before.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Andrea

The point is that I suspect very few Debian maintainers will wish to be emailed *automatically* for this, so it should be an opt-in system. That is what bug 501 is talking about and is also something that's in my plans for the medium-term future.

Does this make sense to you now? If not, I am happy to go into it further on IRC.

Revision history for this message
Andrea Veri (av) wrote :

Talked about this with julien on IRC, and I agree this should be an option as Bug 501 suggests. Thanks

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.