[17:36] <ahasenack> for whoever knows perl here, is this "idiomatic" perl regexp? /^processor[\s\d]*:/
[17:36] <ahasenack> or perhaps /^processor\s*\d*\s*:/
[17:36] <ahasenack> I need to match ^processor : 0
[17:37] <ahasenack> and ^processor 0 : stuff
[17:37] <ahasenack> cases
[18:00] <sdeziel> ahasenack: `/^processor\s+:?\s*\d+/` maybe?
[18:01] <ahasenack> looks more complicated
[18:03] <sdeziel> depends on what you want to match on. The first regex won't match the digit on the `processor : 0` variant
[18:04] <sdeziel> here's what I'm testing with: `echo -e 'processor : 0\nprocessor 0: stuff\nprocessor 0 : stuff' | grep -P '^processor\s+:?\s*\d+'`
[18:05] <ahasenack> that first regexp wasn't already matching the digit after the :
[18:05] <ahasenack> I mean, the original one
[18:05] <ahasenack> so I'm not changing that behavior
[18:12] <sdeziel> if you don't want to change the behavior and deal with a `:` between `processor` and the digit, I'd go with: `/^processor[\s\d:]+/`
[18:13] <sdeziel> it basically requires at least one space or one digit or one `:` somewhere after `processor`
[18:22] <JanC> also depends on what other variants also exist but you don't want them...
[18:28] <ahasenack> they should use getconf
[18:30] <sdeziel> `getconf _NPROCESSORS_ONLN` is probably better indeed
[20:36] <ahasenack> kanashiro[m]: new git published in lunar-proposed, retry builds at will
[20:45] <ahasenack> and it failed again, wth
[20:46] <sergiodj> what failed?  git?
[20:46] <ahasenack> no, something that uses git
[20:47] <ahasenack> see #ubuntu-devel
[20:47] <ahasenack> just started a conversation (with myself, so far) there
[20:48]  * sergiodj looks