Smart Package Manager

smart update errata severity flag

Bug #244501 reported by Rehan Khan
2
Affects Status Importance Assigned to Milestone
Smart Package Manager
Fix Released
Medium
Unassigned
Smart Package Manager 1.4

Bug Description

Imported: http://tracker.labix.org/issue384

Reason: Patch review

further details: https://blueprints.launchpad.net/smart/+spec/bug-reporting-migration

msg1343 (view) Author: afb Date: 2008-06-27.19:30:58

including parsers for yum "updateinfo.xml" and urpmi "descriptions"

Tags: packagekit

Related branches

lp:~smartpm/smart/errata (Merged)
Revision history for this message
Rehan Khan (rasker) wrote :
Changed in smart:
assignee: nobody → afb
importance: Undecided → Medium
Revision history for this message
Anders F Björklund (afb) wrote :

rewrite based on review feedback

Changed in smart:
status: New → In Progress
Revision history for this message
Anders F Björklund (afb) wrote :

Storing this information in the flags is fundamentally wrong, so it would need to be improved with the update-details specification. The parsers should be OK though, just not the errata type "storage".

Anders F Björklund (afb)
Changed in smart:
milestone: none → 1.4
Anders F Björklund (afb)
Changed in smart:
status: In Progress → Fix Committed
Revision history for this message
Anders F Björklund (afb) wrote :

Decided it would be ok to store security/bugfix/enhancement flags,
similar to the already existing "new" flag being set on each update...

The other errata information however, needs to be stored elsewhere.
So that goes in the other bug, along with the getErrata() and whatnot.

Changed in smart:
assignee: Anders F Björklund (afb) → nobody
Anders F Björklund (afb)
Changed in smart:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.