[ some additional clearifying comments ] On Sat, Oct 13, 2012 at 01:54:59PM +0200, Rene Engelhard wrote: > On Sat, Oct 13, 2012 at 12:26:22PM +0100, John Winters wrote: > > On 13/10/12 12:13, Rene Engelhard wrote: > > >On Sat, Oct 13, 2012 at 11:34:33AM +0100, John Winters wrote: > > >>Since the latest version of hunspell etc. arrived in Wheezy, all spell > > > > > >"latest version of hunspell"? Huh? > > > > > >[2011-10-18] hunspell 1.3.2-4 MIGRATED to testing (Britney) > > > > > >That is the "latest version". > > > > > >Sorry, really. I don't believe that this bug was there 1 year > > >and noone noticed. > > > > Did someone get out of bed on the wrong side this morning or are you > > always this scratchy? > > I just said that there was no upgrade of hunspell since a year and that > I simply don't believe that this would not have been noticed before then
I thnk you simply are too picky about this reply just demonstrating a fact. > There's logs. And as libhunspell-1.3-o obviously did NOT get updated... To be precise dpkg has one (/var/log/dpkg.log) and aptitude (/var/log/aptitude) have one. > (Assuming you upgraded before and didn't upgrade from a over a years old > wheezy) Or upgraded squeeze->wheezy. But then you wouldn't have said "arrived in wheezy", which implies you used wheezy before and got a "new" hunspell via upgrade. Regards, Rene -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
