sbuild gets confused when the dsc version does not match the changelog one
Bug #309645 reported by
m0sia
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| launchpad-buildd |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I'm new to launchpad and uploaded dkms'ed sources of v4l-linux with latest dvb-s2 drivers in my PPA. For now it is still building. Of course i can try again and upload version ~ppa2, but i think it is a bug in lauchpad.
https:/
| Changed in soyuz: | |
| status: | New → Confirmed |
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
| tags: | added: sbuild |
| Changed in launchpad-buildd: | |
| status: | Confirmed → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
Okay, your build bounced across several builders until we could finally remove it from queue manually.
It was caused by a missing feature in `sbuild`, when it's not able to detect that the version listed in DSC is not the same than the one in the latest debian/changelog entry.
Maybe it was dkms's fault, not yours, but the mentioned DSC has version '0.20081210.1~ppa1' while your debian/changelog entry has '0.20081210'. Do you remember of editing it manually ?
Anyway, it was agreed that `sbuild` will be modified to fail those kind of builds pretty quickly instead of getting stuck by not knowing which version it should use.
I hope it clarified the problem.