Thanks for the clarification on the correct process for handling bug
status. Apologies for causing trouble. It just seemed like a lot of
time had passed since the fix had been done and there were still
broken packages hanging out there in "stable" releases waiting for
attention. I didn't want them to get missed out. :-(
I guess I shouted too loud. Sorry!
John
On 1/13/07, Freddy Martinez <email address hidden> wrote:
> John, because a bug is Fix Committed does not mean it still doesn't
> exist. It means it has been confirmed, a workaround/patch has been
> created, and it will be released. Some fix commits can't be backported,
> that is why there is an edgy-backport repository. See Richard Johnson's
> comments. While we appreciate you bug work, this is making Richard do
> extra work.
>
> Best,
> Freddy Martinez
>
> --
> Plucker: dead symlinks
> https://launchpad.net/bugs/62069
>
Guys,
Thanks for the clarification on the correct process for handling bug
status. Apologies for causing trouble. It just seemed like a lot of
time had passed since the fix had been done and there were still
broken packages hanging out there in "stable" releases waiting for
attention. I didn't want them to get missed out. :-(
I guess I shouted too loud. Sorry!
John
On 1/13/07, Freddy Martinez <email address hidden> wrote: /launchpad. net/bugs/ 62069
> John, because a bug is Fix Committed does not mean it still doesn't
> exist. It means it has been confirmed, a workaround/patch has been
> created, and it will be released. Some fix commits can't be backported,
> that is why there is an edgy-backport repository. See Richard Johnson's
> comments. While we appreciate you bug work, this is making Richard do
> extra work.
>
> Best,
> Freddy Martinez
>
> --
> Plucker: dead symlinks
> https:/
>