Bazaar

Bug #230294
Comment #11

Comment 11 for bug 230294

Revision history for this message

Craig A. Eddy (tyche-deactivatedaccount) wrote on 2008-05-27:

#11

I agree with Sarah and Martin. A Stable Release Update for Hardy Heron on something that is used by more than just the Intrepid developers and MOTU's is definitely needed. More, it's expected. I was called out because I was up to date with Hardy, but, "This is a known bug which was fixed in bzr 1.4". In addition, I was told, "Which is, according to your traceback, 1.3.1:
bzr 1.3.1 on python 2.5.2.final.0 (linux2)
Upgrading to 1.5rc1 from PPA will solve this issue: https://launchpad.net/~bzr/+archive". Now, I want you to understand that I appreciate being told where to find the fix. I really do. But I do NOT enjoy being called out for not even knowing where the fix is, especially when that fix is in a PPA where only someone working on it would know.

We who are not developers or MOTU's rely on the repositories for our updates/upgrades. That's where we're told to look for programs, and from where we receive our bug fixes. We have enough trouble trying to figure out what WE did wrong, and correcting it. In addition, security updates and bug fixes are tracked in the UWN for Ubuntu 6.04, 7.04, 7.10 and 8.04 (See https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue92 for evidence of this). These are something with which I am intimately aware. (See https://wiki.ubuntu.com/CraigAEddy). Had a fix for this problem come through there, I'd have been aware of it simply because bzr would have caught my eye.

I am not the only one running Hardy Heron, Ubuntu 8.04, that uses bzr. Others may also have been caught in this problem and be thinking that it is something that they did wrong. Please. I am asking that this fix be released for Hardy. I understand your forward thinking - the release date for Ubuntu 8.10 is coming up like a wall, and you're anxious to get things resolved for it as quickly as possible. But, in the mean time, there are all of us who are still using Ubuntu 8.04 (some of which may be using it for 3 to 5 years, due to the fact that it's and LTS) who also deserve to have the update. Please submit the bug fix to Hardy.

I agree with Sarah and Martin.  A Stable Release Update for Hardy Heron on something that is used by more than just the Intrepid developers and MOTU's is definitely needed.  More, it's expected.  I was called out because I was up to date with Hardy, but, "This is a known bug which was fixed in bzr 1.4".  In addition, I was told, "Which is, according to your traceback, 1.3.1:
bzr 1.3.1 on python 2.5.2.final.0 (linux2)
Upgrading to 1.5rc1 from PPA will solve this issue: https://launchpad.net/~bzr/+archive".  Now, I want you to understand that I appreciate being told where to find the fix.  I really do.  But I do NOT enjoy being called out for not even knowing where the fix is, especially when that fix is in a PPA where only someone working on it would know.

We who are not developers or MOTU's rely on the repositories for our updates/upgrades.  That's where we're told to look for programs, and from where we receive our bug fixes.  We have enough trouble trying to figure out what WE did wrong, and correcting it.  In addition, security  updates and bug fixes are tracked in the UWN for Ubuntu 6.04, 7.04, 7.10 and 8.04 (See https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue92 for evidence of this).  These are something with which I am intimately aware.  (See https://wiki.ubuntu.com/CraigAEddy).  Had a fix for this problem come through there, I'd have been aware of it simply because bzr would have caught my eye.

I am not the only one running Hardy Heron, Ubuntu 8.04, that uses bzr.  Others may also have been caught in this problem and be thinking that it is something that they did wrong.  Please.  I am asking that this fix be released for Hardy.  I understand your forward thinking - the release date for Ubuntu 8.10 is coming up like a wall, and you're anxious to get things resolved for it as quickly as possible.  But, in the mean time, there are all of us who are still using Ubuntu 8.04 (some of which may be using it for 3 to 5 years, due to the fact that it's and LTS) who also deserve to have the update.  Please submit the bug fix to Hardy.