------- Comment on attachment From <email address hidden> 2016-03-04 16:28 EDT-------
Hi @mathieu-tl
Er.. this bug needs another fix.. :) Patch attached.
Problem is.. the NVMe expression needs a 'p' suffix.
Apologies. Should I have I tested this on the real hardware before submitting, I wouldn't have give you 3x the trouble.
To make up for it, I cleaned the regex into something more general, which closely matches the compared string (only a removal of trailing partition numbers -- "${prep_p%[0-9]*}").
The changelog version is "1.128ubuntu4multiprepv31" -- in case bugproxy messes up again (I'm trying a few things to keep it quiet this time.. let's see if it works).
------- Comment on attachment From <email address hidden> 2016-03-04 16:28 EDT-------
Hi @mathieu-tl
Er.. this bug needs another fix.. :) Patch attached.
Problem is.. the NVMe expression needs a 'p' suffix.
Apologies. Should I have I tested this on the real hardware before submitting, I wouldn't have give you 3x the trouble.
To make up for it, I cleaned the regex into something more general, which closely matches the compared string (only a removal of trailing partition numbers -- "${prep_ p%[0-9] *}").
The changelog version is "1.128ubuntu4mu ltiprepv31" -- in case bugproxy messes up again (I'm trying a few things to keep it quiet this time.. let's see if it works).
Sorry. Thanks.