import: dpkg-source emits a fatal error with bad control files

Bug #1721154 reported by Nish Aravamudan on 2017-10-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nish Aravamudan

Bug Description

Rather than printing the source which it can still determine. I think this is an ordering issue in dpkg's source, which we might want to work around.

  dpkg-source: error: binary package stanza libc-bin is using an obsolete Build-Profiles field syntax

Because the profile is not enclosed in <>.

We could either patch dpkg in the snap (in which case I think we should file a bug upstream); or we could patch the source before import (but this could happen with a lot of old packages).

Nish Aravamudan (nacc) wrote :

a patch like
     which results in (IMO) improved
              behavior as:

Nish Aravamudan (nacc) wrote :

Note that after reading the code, we fallback to manual reading of the d/s/format file if it exists, so it's not terrible. But we should make this less noisy.

Nish Aravamudan (nacc) on 2017-10-20
Changed in usd-importer:
assignee: nobody → Nish Aravamudan (nacc)
status: New → Confirmed
importance: Undecided → Low
Robie Basak (racb) on 2017-11-28
tags: added: import
Robie Basak (racb) on 2018-05-24
tags: added: spec
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers