`debupstream` tag in format 0.4 deb-version does not use the epoch
Bug #1934945 reported by
Kain
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| git-build-recipe |
New
|
Undecided
|
Unassigned | ||
Bug Description
If you are using a `{debupstream}` tag in your GBR recipe from a source package that contains a version epoch, the epoch is not copied.
This is likely enough of an edge case that this could be either a design bug OR a documentation bug. I am not sure which it qualifies as.
Specifying an epoch manually works as expected, and the number of often built packages than use versioning epochs is somewhat rare I believe. I ran into it driving a custom version of `golang-defaults` in a PPA to get builds vs a non-default golang revision in a distro.
| summary: |
- `debupstream` tog in format 0.4 deb-version does not use the epoch + `debupstream` tag in format 0.4 deb-version does not use the epoch |
Revision history for this message
| Richard Hansen (rhansen) wrote | #1 |
To post a comment you must log in.
The epoch is not part of the upstream version number, so it is correct to exclude it from `{debupstream}`. If you want the epoch, `{debversion}` is a better choice.