Re: Debian's glacial movement--a rant
- To: email@example.com
- Subject: Re: Debian's glacial movement--a rant
- From: Freddy Freeloader <firstname.lastname@example.org>
- Date: Mon, 11 May 2009 21:33:53 -0700
- Message-id: <[🔎] 4A08FC31.email@example.com>
- In-reply-to: <49F9E728.firstname.lastname@example.org>
- References: <49DA3A74.email@example.com> <49DA48E1.firstname.lastname@example.org> <49DA60A8.email@example.com> <20090407130752.GB6679@blitz.hooton> <49F9E728.firstname.lastname@example.org>
Freddy Freeloader wrote:
Just an update on this. I have asked on #gnucash if the patch for this
bug can be backported to 2.2.6 upstream and they say this is a Debian
problem as it is fixed in Gnucash. They will not do anything to help.
Douglas A. Tutty wrote:
On Mon, Apr 06, 2009 at 01:06:00PM -0700, Freddy Freeloader wrote:
Michael Biebl wrote:
Freddy Freeloader wrote:
I'm experiencing a bug in Gnucash that appeared a couple of days
ago on my system that makes Gnucash completely unusable for me. I
turned in a bug report on Friday, checked on it yesterday, and by
today the bug had been blocked from being displayed. It could be
found by searching Debian's bug tracker, but only if you know the
bug id number. If you just search for bugs in Gnucash the bug does
not appear to exist.
The bug was closed, and blocked, because it's been fixed upstream
in version 2.2.9 which was released by Gnucash in February of this
Could you discuss how you're experiencing a new bug ("appeared a couple
of days ago") if you're not using gnucach in a new way? I'm sure there
are bugs in every piece of software I use. There are a couple of which
I am aware (if I care to think on it) but I have work-arounds or I
wouldn't have accepted the software for use and would have chosen a
different solution. I've never run into the "appeared a couple of days
ago" situation where the problem was a new bug; the problem has always
been in a different system (or is upstream of the keyboard :))
Sorry I didn't answer this sooner, but I just now saw your message.
I didn't change anything other than running an apt-get update &&
apt-get upgrade. I was using Gnucash in exactly the same way I had for
last the year. It just started crashing after that when I would close
a tab that was created automatically during creating and posting
vendor invoices or customer bills.
New bug or old bug I don't know. All I know was it was new to me as
I'd been using Gnucash for more than a year to keep track of my
business and suddenly it just didn't work correctly any more.
But, that's all right. Just keep on blaming me. I'm surely at fault.
Hell, I had only been using Gnucash for a year. An imbecile like me
couldn't possibly have developed a stable work flow in that amount of
time. I probably did things differently inside of Gnucash every day
for that entire year....
Starting Gnucash and closing tabs inside it are such technically
challenging tasks that users have a very difficult time doing them
correctly and that most likely explains why Gnucash suddenly began to
fail to open account files at startup too. It's gotta be the stupid
Funny ain't it though how the upstream version, 2.2.9, has a bug fix
for this. I guess they call it the "stupid-user patch", and that's why
they won't backport the patch to 2.2.6.
Here's the short conversation from #gnucash.
* Now talking on #gnucash
* Topic for #gnucash is: Free GPL Personal and Small Business Accounting
|| Please don't ask to ask, just ask and wait! || publically-logged
channel || latest stable: 2.2.9
* Topic for #gnucash set by jsled at Wed May 6 07:46:39 2009
<garyk> Is it possible to have the patch for bug #564928 backported to
2.2.6? I have all my business records in gnucash and this bug crashes
gnucash every time I start it. I run Debian and who knows how long it
will take for Debian to catch up. Right now they are almost a year
behind in version numbers.
* twunder (~email@example.com) has
* warlord-afk is now known as warlord
<warlord> garyk: you need to ask that of Debian. The GnuCash releases
dont have the bug.
* warlord is now known as warlord-afk
<garyk> The Debian devs say it needs to be done upstream as they
won't/can't backport the patch. That's why I asked here.
This looks to be the classic answer given by my stepkids when they were
growing up and didn't want to take responsibility for anything: Who's
responsible? Not me..... Not me was responsible for everything done
wrong in our house for a couple of years. I didn't know one person could
get into that much mischief all their own. ;)
Gnucash version 2.2.6 was released July 31, 2008. The fixed version of
Gnucash, 2.2.9 was released February 4, 2009. It's now May 11, 2009 and
counting. The patch for this critical bug was released 3 months ago and
nothing has been done. It's now 5 weeks since I was told I was being a
jerk for saying Debian was slow in moving on this as they were 3
versions, and 9 months, behind. Well, Debian is now 3 versions and 10
months behind, and the patch has been available for 120+ days while the
bug has been archived in Debian since the day after it was reported.
It couldn't be that this critical bug just isn't on anyone's list of
priorities could it?