UID ordering and preference is suboptimal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
hockeypuck |
Fix Committed
|
Medium
|
Casey Marshall |
Bug Description
It looks as though Hockeypuck is preferring the latest UID on a key for the name/email address to show, both for the key itself and when referencing it in signature listing displays on other keys.
I suggest the algorithm should be:
* remove any uids which have been revoked
* if any uid has a primary uid bool flag set true on it, restrict the set of uids to those with that flag (should be only one, but in the real world might be N)
* if more than one uid left, prefer the oldest, as being more likely to be "core", with other addresses bolted on.
Case in point: my key 0x403043153903637f has numerous signatures, one has a primary uid flag set on it, but the gazzang instance of Hockeypuck chooses to show the uid specific to a project I work on instead.
Related branches
Changed in hockeypuck: | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → Casey Marshall (cmars) |
milestone: | none → 1.0 |
Changed in hockeypuck: | |
status: | In Progress → Fix Committed |
Should be addressed at bzr199, needs a test case.