Launchpad itself

Changelog-Close feature tries to close already-closed bugs (when syncing changes back from debian

Bug #118671 reported by Emilio Pozuelo Monfort
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

I put a LP: # bug for future reference in an upload, and Soyuz tried to close it (it was already closed some time ago).

Maybe Soyuz should check whether a bug report is already closed, and if it is, don't put the changelog entry.

https://launchpad.net/ubuntu/gutsy/+source/listen/0.5-3ubuntu1
Bug #118030 (the good one).
Bug #87959 (the reference).

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Indeed, this is moderately annoying.

Changed in soyuz:
status: Unconfirmed → Confirmed
Revision history for this message
Celso Providelo (cprov) wrote :

If bug #87959 was not supposed to be marked as fixed-released why it was mentioned in the changes 'Launchpad-Bugs-Fixed' [1] ?

I don't think it's a good strategy to ignore legitimate attempts to close a bug from a changes files w/o a comment.

Is there any good rationale for doing that, despite of the fact that it might result in a noisy comment ?

[1] http://launchpadlibrarian.net/7935668/listen_0.5-3ubuntu1_source.changes

Changed in soyuz:
status: Confirmed → Incomplete
Revision history for this message
Adrien Cunin (adri2000) wrote :

What has happened to me already is: I fix a bug in Ubuntu with an upload and close the report using LP: #nnnnnn in the changelog, and later the Debian version is either merged or synced and the Debian changelog contains also LP: #nnnnnn. In this case the bug report is first closed with the Ubuntu upload, ie. when the bug is actually fixed in Ubuntu, but it is closed again when the Debian version hits Ubuntu.

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

Thanks, Adrien. I see your point now. Sometimes it's hard for the client tools to get it right and they take the safest path, which is always ' request server-side to close the bug'.

The easiest solution is to avoid closing/comment bug-tasks that are already fix-released. The worst thing it would cause is to have a bug that was manually fixed and will miss some information, bug you can trace the who mistakenly did it.

Changed in soyuz:
importance: Undecided → Medium
status: Incomplete → Triaged
tags: added: soyuz-upload
Robert Collins (lifeless)
summary: - Changelog-Close feature tries to close already-closed bugs.
+ Changelog-Close feature tries to close already-closed bugs (when syncing
+ changes back from debian
Changed in launchpad:
importance: Medium → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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