blob: b5ed4bb1a9e4edc373dcb15c31d6d6025af60c7b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
|
Tag: epoch-change-without-comment
Severity: warning
Check: debian/changelog
Explanation: The previous version of this package had a different version epoch
(eg. 2:1.0-1) to the current version but there's no reference to this in
the changelog entry.
.
Epochs exist to cope with changes to the upstream version numbering
scheme. Whilst they are a powerful tool, increasing or adding an epoch
has many downsides including causing issues with versioned dependencies,
being misleading to users and being aesthetically unappealing. Whilst
they should be avoided, valid reasons to add or increment the epoch
include:
.
- Upstream changed their versioning scheme in a way that makes the
latest version lower than the previous one.
- You need to permanently revert to a lower upstream version.
.
Temporary revertions (eg. after an NMU) should use not modify or
introduce an epoch - please use the <code>CURRENT+reallyFORMER</code> until
you can upload the latest version again.
.
If you are unsure whether you need to increase the epoch for a package,
please consult the debian-devel mailing list.
.
Lintian looks in this version's changelog entry for the phrase "epoch".
|
