Bug archived on Debian showing as fix released
 

Hi all,
From what I understand the Debian BTS closes bug reports when it
fixes a bug. It also does closes the bug when due to inactivity it
doesn't get fixed. Something similar to what launchpad janitor tries
to do. Now this gives wrong impressions for both times it shows as the
fix being released (on launchpad) when it is not so.

For e.g. look at this bug report on debian

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435888

From the couple of last posts it seems it just didn't get worked out
and the bug-report got closed but if you look at the launchpad page of
the same bug it shows that the fix is released.

https://bugs.edge.launchpad.net/ubuntu/+bug/283491

Am I reading something wrong or what?
--
Regards,
Shirish Agarwal
This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/

065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17

--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users

Bug archived on Debian showing as fix released
 

On Sat, 2008-10-25 at 16:16 +0530, shirish wrote:
> Hi all,
> From what I understand the Debian BTS closes bug reports when it
> fixes a bug. It also does closes the bug when due to inactivity it
> doesn't get fixed. Something similar to what launchpad janitor tries
> to do. Now this gives wrong impressions for both times it shows as the
> fix being released (on launchpad) when it is not so.
>
> For e.g. look at this bug report on debian
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435888
>
> From the couple of last posts it seems it just didn't get worked out
> and the bug-report got closed but if you look at the launchpad page of
> the same bug it shows that the fix is released.
>
> https://bugs.edge.launchpad.net/ubuntu/+bug/283491
>
> Am I reading something wrong or what?

Yes, you're reading it wrong. The current status in Ubuntu is
"Confirmed". When a bug is closed due to inactivity in Ubuntu, it is
marked Invalid.

--
Mackenzie Morgan
http://ubuntulinuxtipstricks.blogspot.com
apt-get moo
--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users

Bug archived on Debian showing as fix released
 

Hello all,

On Sat, Oct 25, 2008 at 7:03 PM, Mackenzie Morgan <macoafi@gmail.com> wrote:
> On Sat, 2008-10-25 at 16:16 +0530, shirish wrote:
>> Hi all,
>> From what I understand the Debian BTS closes bug reports when it
>> fixes a bug. It also does closes the bug when due to inactivity it
>> doesn't get fixed. Something similar to what launchpad janitor tries
>> to do. Now this gives wrong impressions for both times it shows as the
>> fix being released (on launchpad) when it is not so.
>>
>> For e.g. look at this bug report on debian
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435888
>>
>> From the couple of last posts it seems it just didn't get worked out
>> and the bug-report got closed but if you look at the launchpad page of
>> the same bug it shows that the fix is released.
>>
>> https://bugs.edge.launchpad.net/ubuntu/+bug/283491
>>
>> Am I reading something wrong or what?
>
> Yes, you're reading it wrong. The current status in Ubuntu is
> "Confirmed". When a bug is closed due to inactivity in Ubuntu, it is
> marked Invalid.
>

The concern of Shirish is about the way launchpad interprets the
status of the debian bug. The point is that the bug in Debian has been
closed due to inactivity - and remains unfixed - but the status for
the Debian bug watch in Launchpad is "Fix Released". As you said,
following launchpad policy, the Debian bug watch should be marked
"Invalid" and not "Fix Released". But I may be wrong.

Sincerely.

--
Jean-Baptiste

--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users

Bug archived on Debian showing as fix released
 

Mackenzie Morgan schrieb:
> On Sat, 2008-10-25 at 16:16 +0530, shirish wrote:
>> Hi all,
>> From what I understand the Debian BTS closes bug reports when it
>> fixes a bug. It also does closes the bug when due to inactivity it
>> doesn't get fixed. Something similar to what launchpad janitor tries
>> to do. Now this gives wrong impressions for both times it shows as the
>> fix being released (on launchpad) when it is not so.
>>
>> For e.g. look at this bug report on debian
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435888
>>
>> From the couple of last posts it seems it just didn't get worked out
>> and the bug-report got closed but if you look at the launchpad page of
>> the same bug it shows that the fix is released.
>>
>> https://bugs.edge.launchpad.net/ubuntu/+bug/283491
>>
>> Am I reading something wrong or what?
>
> Yes, you're reading it wrong. The current status in Ubuntu is
> "Confirmed". When a bug is closed due to inactivity in Ubuntu, it is
> marked Invalid.
>

I think you got shirish wrong. I think his issue is that the debian bug
was closed for being too old (so, similar to Launchpad's invalid
status). However, the launchpad bug watch shows up as "Fix Released",
while it actually isn't.

--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users

Bug archived on Debian showing as fix released
 

On Sat, 2008-10-25 at 19:50 +0200, Kjell Braden wrote:
> Mackenzie Morgan schrieb:
> > Yes, you're reading it wrong. The current status in Ubuntu is
> > "Confirmed". When a bug is closed due to inactivity in Ubuntu, it is
> > marked Invalid.
> >
>
> I think you got shirish wrong. I think his issue is that the debian bug
> was closed for being too old (so, similar to Launchpad's invalid
> status). However, the launchpad bug watch shows up as "Fix Released",
> while it actually isn't.

Oh, ok. Is Debian using one status to mean two different things? I
don't think it's possible for Launchpad to differentiate, if that's the
case.

--
Mackenzie Morgan
http://ubuntulinuxtipstricks.blogspot.com
apt-get moo
--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users

Bug archived on Debian showing as fix released
 

I'm fairly sure there's already a bug on launchpad about this.


--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users

Bug archived on Debian showing as fix released
 

Hi all,

@Kjell Brandon - Thank you for understanding and passing along the message.

@Sarah Hobbs :- If you or anybody comes to know about if a bug has
been filed for the situation described above, a reference here would
be nice. Would like to subscribe to that bug :)
--
Regards,
Shirish Agarwal
This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/

065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17

--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users

Bug archived on Debian showing as fix released
 

Hi all,
Jean, exactly. In fact I would say even 'invalid' would be not right,
it should be 'inactive' but that's another story. But short-term yes,
it would be nice if launchpad would show it 'invalid'.
--
Regards,
Shirish Agarwal
This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/

065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17

--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users

Bug archived on Debian showing as fix released
 

2008/10/27 shirish <shirishag75@gmail.com>

Hi all,

*Jean, exactly. In fact I would say even 'invalid' would be not right,

it should be 'inactive' but that's another story. But short-term yes,

it would be nice if launchpad would show it 'invalid'.

--

* * * * *Regards,

* * * * *Shirish Agarwal

*This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/



065C 6D79 A68C E7EA 52B3 *8D70 950D 53FB 729A 8B17



--

launchpad-users mailing list

launchpad-users@lists.canonical.com

Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users


Whilst I agree that the current status of 'Fix released' for the Debian bug is misleading, I don't think Launchpad has interpreted the status of the Debian bug incorrectly. The Debian bug has been closed as 'Done', which I think is the same status used to close bugs that have been fixed in Debian.


Regards
Chris

--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users

Bug archived on Debian showing as fix released
 

Hi Chris,
Thank you for responding back. Unfortunately, the bug is not done. I
cannot find xmlcopyeditor anywhere in http://packages.debian.org
either as package names or as source package names.

Lemme know if you find the package .
--
Regards,
Shirish Agarwal
This email is licensed under http://creativecommons.org/licenses/by-nc/3.0/

065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17

--
launchpad-users mailing list
launchpad-users@lists.canonical.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/launchpad-users