A couple of thoughts:
1)
In addition to future supported platforms, what about weird third party
hacked up things? Are we going to end up with reports from users who
have grabbed a custom image for some esoteric platform from someone who
is hacking something together for that platform by basing their work on
one of our official Raspberry Pi images? To be clear, they're welcome to
do that; we just don't want images mislabelled as Raspberry Pi causing
confusion in that case. Of course people can do that regardless of what
apport does, but labelling them as Raspberry Pi would exacerbate the
issue.
2)
+ if 'ImageMediaBuild' in report:
+ if report['Architecture'] in ('arm64', 'armhf'):
+ add_tag(report, 'raspi-image')
Why not simply add tags arm64-image and armhf-image? Then you'll get the
same effect you want but without a potentially misleading tag. This may
be kicking the can down the road, but maybe that's exactly what we want
to do here?
This should presumably be settled in the development release before the SRU
proceeds, so I'm deferring SRU review for now.
--
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/1920837
Title:
apport bugs from official raspi or riscv images are not identified
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Focal:
In Progress
Status in apport source package in Groovy:
In Progress
Bug description:
It would be helpful if bugs reported from images for Raspberry Pi's or
RISCV systems were tagged so that one could search for bugs from
systems running those images e.g. 'raspi-image'.
[Test Case]
After installing a preinstalled image of Ubuntu for Raspberry Pi do the
following:
1) run 'ubuntu-bug apport'
2) view the bug report and check the Tags field
With the current version of apport you will not see the tag 'raspi-image'.
With the version of apport in -proposed you will see the tag 'raspi-image'.
[Where problems could occur]
If the code being added is syntactically incorrect then we'd see a Traceback
which would be bad as it could affect all bug / crash reports.
[Other Info]
Since there aren't any Groovy images for RISC-V there will be nothing to test
there.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1920837/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
