bucketmetadata has a key for source package but daisy inserts binary package
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Daisy |
New
|
High
|
Unassigned |
Bug Description
Looking at update_
def update_
...
if metadata:
So it appears that bucketmetadata is intended to contain information about source packages, however looking at the data we find 'compiz-core', 'jockey-gtk', 'chromium-browser', and many other binary packages.
Looking into utils.py from daisy we see the following:
def bucket(oops_config, oops_id, crash_signature, report_dict):
....
package = report_
In apport reports 'Package' is the binary package and 'SourcePackage' is the SourcePackage. For the work I'm doing now, phased updates, I'd like the source package to be in bucketmetadata and it appears that was the intent. However, we should check to see if there are other cases where bucketmetadata is queried for the binary package and not the source package.
Changed in daisy: | |
importance: | Undecided → High |
most_common_ problems in errors/ api/resources. py says that it is getting Source but it is really getting binary since that is what was inserted and in this case we do want binaries.
bucket in errors/view.py could use either binary or source package as it is just displaying the name and then links a Launchpad page for that package, which contains information about published versions of that package (which would be the same for the binary or source package).