.changes files reference .buildinfo files that aren't exposed

Bug #1686242 reported by Steve Langasek
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
In Progress
Simon Quigley

Bug Description

When I download packages from the binary NEW queue in artful, I get a result that lintian chokes on:

$ lintian -Ii caja-*changes
/tmp/caja-extensions_1.18.1-0ubuntu1_amd64.buildinfo does not exist, exiting

I have to manually hack out the .buildinfo lines to get something that lintian can process. This is rather awkward for queue review workflows, would be great to have this fixed.

A link to the .buildinfo file should appear in build pages, but does not.

Related branches

Revision history for this message
Luís Infante da Câmara (luis220413) wrote :
description: updated
Changed in launchpad:
status: New → Confirmed
Revision history for this message
Simon Quigley (tsimonq2) wrote :

The artifacts are created. In fact, if you have the right ID, they're even accessible. That being said, adding both the source.changes file and the .buildinfo file to SourcePackageReleaseFile makes everything work as intended.

Simon Quigley (tsimonq2)
Changed in launchpad:
assignee: nobody → Simon Quigley (tsimonq2)
status: Confirmed → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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