possible apport bug

[Nicholas Skaggs]

Brian is right here -- it just means Jackson is running the same release 
he originally installed -- he's never upgraded it to a newer version. 
For instance, my box has been upgraded each since precise I think (I'm 
on raring now), but if I were to re-install using a raring cd right now, 
I would get the same message. For bug reporting purposes, those upgrades 
could be interacting with something that got changed or removed, or 
reset, etc, during the upgrade, as opposed to a fresh install. You guys 
have seen those types of bugs before :-)

Nicholas

On 02/01/2013 10:35 AM, Brian Murray wrote:
> On Thu, Jan 31, 2013 at 10:44:09PM -0500, Phill Whiteside wrote:
>> Hi Brian,
>>
>> Right, so to be clear this is by design and this are working properly.
>>
>>
>> which is causing people to ask. Maybe an explanation of this is needed
>> instead of "oh, this is working"?
>>
>> The people who actually take the time out to test do deserve a better
>> answer.
> The UpgradeStatus field in your apport report is an attempt to determine
> if the system being reported about has upgraded from one release of
> Ubuntu to another.  This can be helpful in determining factors that may
> affect bugs.
>
> Perhaps somebody would like to take the initiative and document fields
> commonly found in apport reports.  One way to get started doing this
> would be to review a crash report in /var/crash or create a bug report
> using 'apport-cli' with the --save option.  However, any apport package
> hook can add arbitrary keys and values to apport reports so any list
> would not be comprehensive.  Regardless, if someone wants to do this
> I'll be happy to answer any questions regarding keys and their meanings.
>
> --
> Brian Murray
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-quality/attachments/20130201/e630bb5f/attachment.html>