Package Testing

Registered by David Murphy on 2009-05-05

Packages in Ubuntu should be tested automatically to ensure that they meet basic standards. Packages should at least be installable and uninstallable and files installed should not conflict with those in other packages.

Various tools exist to ensure package quality and should be evaluated for regular package checks.

Blueprint information

Status:
Complete
Approver:
Henrik Nilsen Omma
Priority:
High
Drafter:
Ronald McCollam
Direction:
Approved
Assignee:
Ronald McCollam
Definition:
Approved
Series goal:
Accepted for karmic
Implementation:
Implemented
Milestone target:
milestone icon karmic-alpha-4
Started by
Ronald McCollam on 2009-07-15
Completed by
Henrik Nilsen Omma on 2009-08-07

Related branches

Sprints

Whiteboard

* 2009/06/18 * sbeattie: I've fixed up some of the issues that prevented conflictchecker from running out of the box (as well as merging in some fixups mvo had done) and pushed them to https://code.edge.launchpad.net/~sbeattie/conflictchecker/conflictchecker-fixups . I am able to successfully run this locally against a mirror of hardy+jaunty, though the results require analysis due to the way diversions are handled (or not) by dpkg.

2009-06-19: mvo: I merged the update to macaroni and it is now running on http://conflictchecker.ubuntu.com/
2009-06-22: mvo: its now running on macaroni and is churning through the new packages:
 ...
 Finished dpkg_1.13.11ubuntu6_amd64 in 6.797 seconds [1028/57372]
 ...

2009-07-01: sbeattie: mvo now has conflictchecker running out of cron hourly on http://conflictchecker.ubuntu.com/, results are under http://conflictchecker.ubuntu.com/possible-conflicts.new/ . Needs someone to triage them and file bugs.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.