debian/control might not be re-generated, even though debian/control.in is modified
Bug #608210 reported by
Olivier Naudan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gst-plugins-bad0.10 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| gst-plugins-base0.10 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| gst-plugins-good0.10 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
| gstreamer0.10 (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
In case the file modification dates are all equals (as in a GIT tree), debian/control might not be re-generated even if debian/control.in was modified. Same thing for debian/build-deps and debian/
To be on the safe side, I suggest to touch the .in files to force a re-generation, independently of timestamps.
Also I would add a warning notice in debian/control and debian/build-dep, stating that it is generated and shall not be modified.
| description: | updated |
To post a comment you must log in.
