On Tue, Jul 11, 2023 at 10:05 PM Salvatore Bonaccorso <car...@debian.org> wrote: > On Tue, Jul 11, 2023 at 06:30:38PM +0300, Martin-Éric Racine wrote: > > Reintroducing the epoch produces the following Lintian ERROR: > > > > E: dhcpcd source: > > epoch-changed-but-upstream-version-did-not-go-backwards 10.0.1-2 -> > > 1:10.0.1-3 [debian/changelog:1] > > The lintian tag in it's intention is clear. But I believe in this case > it reports in error. Because the history of the dhcpcd source package > is as follows, cutting of some irrelevant inbetween steps: > > 0.4-1 -> 1.3.8-0.1 -> 1:0.70-5 (epoch introduced here), then moved > upwards -> 1:3.2.3-11 / 1:3.2.3-11+deb7u1 which was the last version > available for a while. > > But then we dropped to 10.0.1-1 (which already missed the epoch). > > Now the lintian just only checks 10.0.1-2 -> 1:10.0.1-3 and thinks to > report that the epoch addition is an error, but it would not if all > the 10.0.1-1, 10.0.1-2 versions already had the epoch still. > > Does this make sense?
Makes sense to me. Uploaded to Mentors. Please note that Mentors forces me to 'debuild -sa' because it cannot find the 'orig' on its repository even though it's already in unstable. Martin-Éric
