** Tags removed: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master bugs are confusing and lead to more duplicate filings
Status i
** Tags added: rls-hh-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master bugs are confusing and lead to more duplicate filings
Status in
Hey, @ubuntu-johnwash. I agree @tafthorne's comment was long, but it
also went into more detail than mine (mine left some steps as "exercises
for the reader"). I'm glad I was able to summarize the key part for you
:-).
Yes, would be nice if a maintainer wanted to pick this up. I don't have
any
@kfogel: really? Is that what tafthorne's suggestion was? Well, in
that case, I agree, that's brilliant.
@tafthorne: why did I not realise how brilliant your suggestion was?
Simple. Because its length made me mutter 'tl;dr' and skip on to the
next. Please, if you're going to make further brill
+1 on @tafthorne's suggestion in comment#21 that there be a widget that
a maintainer can use to easily swap a private master bug with some
chosen public duplicate bug. (Actually, nothing about this widget is
specifically about private vs public, but I'll talk about it in those
terms here, since th
This bug happened to me today. I found an easily reproducible bug in a
package, so because I am a helpful person, I did a fresh install just to
repro it in +1, and submitted a core dump through apport. Because I knew
for a fact that there was no private information in the clean install I
set my bug
reverting to Triaged.
** Changed in: apport (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master bugs
Would 'Confirmed' be a more appropriate status than 'In progress'?
Indeed, given that this bug was reported over 5 years ago, even
mentioning the word 'progress' carries a touch of irony. :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
changed to "in progress" as im not able to set it back to "triaged"
** Changed in: apport (Ubuntu)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.lau
** Changed in: apport (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/764414
Title:
private master bugs are confusing and le
I would like to +1 the idea of a
> A. Public master bug
However I do not think is a job that apport could be expected to do safely. It
cannot interpret what data is safe to make public, what summary would be
helpful to future reports trying to determine duplicates or what should go in
the
11 matches
Mail list logo