| Summary: | Redundant updated date gets displayed | ||
|---|---|---|---|
| Product: | PackageKit | Reporter: | Mark J Cox <mjc> |
| Component: | backend-yum | Assignee: | Richard Hughes <richard> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: | proposed patch | ||
note adding this patch is consistent with update_md.py which uses this logic in deciding to display the updated field:
if self._md['updated'] and self._md['updated'] != self._md['issued']:
head += " Updated : %s" % self._md['updated']
Looks good to me, thanks. I'll apply when I get back from holiday. Pushed, thanks. New upstream release in a week or so's time. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.
Created attachment 37814 [details] proposed patch Some repos have the 'updated' date on an advisory included in updateinfo.xml set even on the initial release, matching the 'issued' date. In these cases the gpk GUI will display "This notification was issued on 08/05/2010 and updated on 08/05/2010" which could lead to confusion. The following simple patch for the backend just blanks out the updated date if it is identical to the issue date. Note in addition that client/pk-console.c will display field names such as 'cve' 'vendor' 'updated' even if blank. I've not included a patch for this as it might be deliberate.