| [09:20] <AlanBell> Hi pendulum I am tying this using dasher on maverick and I can't make it crash | |
| [09:24] <AlanBell> I looked at the code there has been a new release and the bit that was crashing has been totally rewriten | |
| [09:24] <AlanBell> back to regular keyboard now | |
| [09:25] <AlanBell> 3 minutes per line is a bit slow | |
| [09:25] <AlanBell> that was with dasher -a into irssi, it works fine, the DeleteCharacters bit it was segfaulting on is now totally not there | |
| [09:26] <AlanBell> it is possible to do /window 20<return> but a little hard still, it thinks it unlikely you want to do a newline without a full stop first | |
| [09:31] <AlanBell> nigelb: how do I mark bug 586558 as fixed in Maverick? | |
| [09:31] <ubot2> Launchpad bug 586558 in dasher (Ubuntu) "dasher crashed with SIGSEGV in Dasher::CDasherModel::DeleteCharacters() (affects: 2) (heat: 121)" [Medium,Confirmed] https://launchpad.net/bugs/586558 | |
| [10:05] <nigelb> AlanBell: nominate for release Maverick and mark it as fix released | |
| [10:06] <AlanBell> done, thanks | |
| [10:07] <vish> nigelb: why nominate thats for older releases? | |
| [10:07] <nigelb> AlanBell: gah, err, nominate for lucid and maverick and once accepted, mark the maverick one as fixed | |
| [10:07] <vish> AlanBell: you can just mark it as fixed and comment "Fixed in Maverick" adding a version number will be a bonus | |
| [10:07] <nigelb> vish: we want to track the same bug for lucid too | |
| [10:08] <AlanBell> ok, nominated for both and set back to confirmed | |
| [10:08] <vish> nigelb: still , it first needs to be marked fixed , the main task is for the devel version ie maverick | |
| [10:09] <nigelb> vish: yes, but when you 2 tasks, having one as fixed relased makes sense doesn't it? | |
| [10:09] <vish> the lucid tasks will be opened later.. | |
| [10:09] <vish> nigelb: no, but that is how it works. first we mark it fixed , the main task is always > devel release | |
| [10:09] <vish> current one.. | |
| [10:10] <nigelb> vish: Ah, correct. /me kicks self | |
| [10:10] <nigelb> today is just not going right | |
| [10:10] <AlanBell> so it should be fix released? | |
| [10:10] <AlanBell> and nominated for Lucid? | |
| [10:10] <vish> AlanBell: yup, the nominate for release we use mainly for SRU | |
| [10:10] <vish> yup | |
| [10:11] <AlanBell> ok, done | |
| [10:11] <AlanBell> don't think I can withdraw the Maverick nomination | |
| [10:11] <vish> no , you've branded the bug ;p | |
| [10:11] <nigelb> AlanBell: don't worry, it will be rejected by the powers that be | |
| [10:12] <vish> AlanBell: if you want to follow through for a SRU , finding the exact patch that fixed it would help.. usually unknown bug fixes dont make it for an SRU | |
| [10:12] <nigelb> Even known bug fixes without someone prodding doesn't make it for SRU | |
| [10:14] <vish> hmm , but reading the AlanBell's comment , it seems it might not be a SRU candidate.. he mentions a rewrite.. | |
| [10:14] <AlanBell> vish: I have a feeling it is a bit of an architectural change rather than a patch | |
| [10:14] <vish> :) | |
| [10:14] <AlanBell> the function that was crashing no longer exists | |
| [10:14] <nigelb> oh, well | |
| [10:43] <nigelb> AlanBell: nominations accepted/rejected :) | |
| [12:03] <AlanBell> great, thanks | |