| slackner | wgrant: was just trying to fix some build/dependency issues, and do some testing builds, but now i get "You have exceeded today's quota for ubuntu trusty, ubuntu precise." - https://code.launchpad.net/~pipelight/+recipe/wine-compholio-daily | 12:48 |
|---|---|---|
| slackner | wgrant: is it possible to reset that quota? we can't really wait 24 hours until we fix that ^^ | 12:48 |
| slackner | wgrant: ah, when one of the other devs pushes it, it still works - so everything fine, we have at least a workaround ;) | 12:53 |
| tgm4883 | Shouldn't the members of the team that is marked as "bug supervisor" of a project be able to see bugs against a project that are set as private? | 22:58 |
| wgrant | tgm4883: No. Those bugs need to be shared with them through the project's +sharing page, or they must be subscribed to the specific bug. | 23:09 |
| wgrant | tgm4883: Tying bug edit permissions to bug view permissions is too inflexible. | 23:09 |
| tgm4883 | hmm | 23:09 |
| tgm4883 | wgrant: how does the initial set of users get view access to it then? | 23:09 |
| wgrant | tgm4883: Which initial set of users? | 23:09 |
| tgm4883 | wgrant: like me, how did I get the initial access to view the private bug? | 23:10 |
| tgm4883 | for instance https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/763872 | 23:10 |
| ubot5 | Error: launchpad bug 763872 not found | 23:10 |
| wgrant | tgm4883: Did you file the private bug? | 23:10 |
| tgm4883 | nope | 23:10 |
| wgrant | ~ubuntu-crashes-universe is subscribed. | 23:10 |
| wgrant | You must be a member of that team. | 23:10 |
| tgm4883 | probably indirectly | 23:11 |
| stuartm | well that would be amusing, private bugs can only be viewed by those who submitted them, not those in a position to actually fix them | 23:11 |
| wgrant | Sure. | 23:11 |
| wgrant | But Ubuntu's bug supervisor team is huge. | 23:11 |
| wgrant | We don't want to trust random bug triagers with access to all the private bugs... | 23:11 |
| tgm4883 | wgrant: out of curiosity, I don't suppose ~ubuntu-crashes-universe also grants access to errors.ubuntu.com | 23:12 |
| wgrant | tgm4883: I don't think so, but that's not a system I have any significant experience with. | 23:12 |
| wgrant | The team was initially created so ~ubuntu-dev could have access to semi-sanitised apport crashes. | 23:12 |
| stuartm | tgm4883: is there actually any sensitive info in the bug report? Apart from SD credentials I can't think of anything which could be considered that sensitive | 23:13 |
| tgm4883 | ok, well at least we know how it works now. | 23:13 |
| stuartm | well not unless the user was browsing their porn collection when it crashed | 23:13 |
| tgm4883 | stuartm: no I don't believe so | 23:13 |
| tgm4883 | wgrant is there anything that automatically marks it as private, or is that the user doing it? | 23:13 |
| wgrant | tgm4883: Crashes are always private by default, as they contain core dumps. | 23:13 |
| wgrant | Apport will then retrace and remove the core dump, then subscribe ~ubuntu-crashes-universe. | 23:14 |
| tgm4883 | ah, so as long as the core dump doesn't contain private data, we should be able to safely change it to public? | 23:14 |
| wgrant | It remains private, as the stacktrace may still contain sensitive information. | 23:14 |
| wgrant | Revealing coredumps publicly is never a good idea, but stack traces can be safe if verified. | 23:14 |
| wgrant | In this case the expanded variables etc. don't appear to contain passwords or anything, so it's probably safe to make it public. | 23:15 |
| tgm4883 | ok (I know almost nothing of what exists in the core dumps) | 23:15 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!