[01:15] <wigs> hello folk
[01:16] <wigs> sometimes I think that lp "helpers" are more concerned with closing rather than fixing :-/
[01:16] <hggdh> wigs: example?
[01:17] <wigs> hggdh: mass marking of bugs as incomplete because they are reported against EOL releases
[01:17] <TheLordOfTime> that's valid.
[01:17] <wigs> yes
[01:17] <TheLordOfTime> wigs, they're marked as incomplete.
[01:17] <TheLordOfTime> because: they need confirmation in supported releases
[01:18] <wigs> but my particular peeve is for trivial bugs that take all of 5 seconds to confirm
[01:18] <TheLordOfTime> otherwise, the bug could be considered "No Longer Valid"
[01:19] <wigs> I just like to see more people actually attempt the confirmation themselves (for obviously trivial bugs) rather than just push that on to others
[01:19] <hggdh> wigs: once a release goes EOL, a bug on it has to be verified against a non-EOL version. If a bug has already been verified as such, then marking incomplete is wrong
[01:21] <hggdh> wigs: well, I sort of agree with you there. But... we have more bugs than helpers. What, then, should be done?
[01:21] <wigs> imo, for trivial bugs, leave them
[01:22] <wigs> because trivial bugs are often UI quirks that come up in edge cases, etc. and will likely be lost for another more years if the report is just closed
[01:22] <hggdh> wigs: but marking incomplete is not closing the bug
[01:23] <hggdh> I am confused: you complained about mass marking bugs incomplete, and now are talking about closed bugs
[01:23] <wigs> almost equivalent if the original report has long stopped caring
[01:23] <wigs> reporter*
[01:23] <hggdh> then help us
[01:24] <TheLordOfTime> what hggdh said
[01:25] <hggdh> again, we are few, and there are a LOT of bugs. We -- or, to be more correct, at least I -- have other things to do. We try to help, but we *need* help
[01:26] <wigs> indeed
[01:26] <wigs> wigs has focused his efforts on a few packages, but high quality triaging of issues
[01:28] <hggdh> wigs: this is the way to go. We cannot save it all, but we can at least do a good job on what we touch.
[08:18] <xnox> bdmurray: I have a cunning plan on using the file bridge to monitor the '/' inode (that one is real from the upper overlay), notice '/etc' creation and boom launch initctl reload-configuration =)
[11:49] <wagafo> Anybody knowledgeable in apport/python to figure out what is going on in bug 985049 ? I'm the reporter but I'd also like to triage this bug some more.
[11:49] <ubot2`> Launchpad bug 985049 in apport (Ubuntu) "apport-cli crashed with error in _compile(): nothing to repeat" [Medium,Confirmed] https://launchpad.net/bugs/985049
[11:55] <melodie_> hello
[12:07] <jibel> wagafo, this portion of the code crashes because of a specific value of the regex due to the substitution in line replacements.append((re.compile('\\b%s\\b' % s), 'User Name'))
[12:08] <jibel> wagafo, it'd be interesting to know what the value of s is. Looking at the code it contains the gecos field of the current user
[12:08] <wagafo> jibel, thanks, cant you send me python code to include to print the value of "s"? I don't know pythong...
[12:09] <jibel> wagafo, you can get it with getent or in python with python3 -c "import os, pwd; print(pwd.getpwuid(os.getuid())[4])"
[12:10] <jibel> this might be sensitive information though
[12:10] <wagafo> I tried it and i get my full name plus some numbers
[12:13] <jibel> wagafo, is there any special characters like (), |, %, &, ...
 Just "Walter Garcia-Fontes" at the beginning, may the hyphen be the problem? I tried your comand at another system where apport does not crash and I get exactly the same, with the hyphen
[12:17] <wagafo> jibel, Actually I think I can show what I get, I figure out it's just the phone numbers I input in my user profile, here it is "Walter Garcia-Fontes,20.220,+34935422722,+34934221452,"
[12:19] <wagafo> jibel, as I said I get exactly the same in another system with exactly the same version of everything and it works, it's just in this system where apport crashes with "nothing to repeat"
[12:21] <jibel> wagafo, thanks, I can reproduce it. The problem is the phone number starting with a '+' sign, which is pretty common in a phone number
[12:21] <jibel> wagafo, I'll update the bug report
[12:21] <wagafo> jibel , great, I saw that I don't have the plus in the other system! Finally I could figure this out!
[21:12] <Noskcaj> any news on bug 1066223?
[21:12] <ubot2`> Launchpad bug 1066223 in ubiquity (Ubuntu) "kde ubiquity detects Sydney timezone but says Adelaide" [Undecided,Confirmed] https://launchpad.net/bugs/1066223
[22:16] <melodie> good night