Epoch never can go backwards, it should only be incremented if there's an upgrade issue

This commit is contained in:
Peter Robinson 2020-08-05 14:48:13 +01:00
parent 76add4e1b8
commit 947b2f18cf
2 changed files with 6 additions and 21 deletions

20
.gitignore vendored
View File

@ -1,19 +1 @@
irqbalance-0.55.tar.gz
irqbalance-0.56.tbz2
/irqbalance-1.0.tbz2
/irqbalance-1.0.1.tar.gz
/irqbalance-1.0.2.tar.gz
/irqbalance-1.0.3.tar.gz
/irqbalance-1.0.4.tar.bz2
/irqbalance-1.0.5.tar.gz
/irqbalance-1.0.6.tar.gz
/irqbalance-1.0.7.tar.bz2
/v1.0.7.tar.gz
/v1.0.8.tar.gz
/v1.0.9.tar.gz
/irqbalance-1.1.0.tar.gz
/irqbalance-1.2.0.tar.gz
/irqbalance-1.3.0.tar.gz
/irqbalance-1.4.0.tar.gz
/irqbalance-1.6.0.tar.gz
/irqbalance-1.7.0.tar.gz
/irqbalance-*.tar.gz

View File

@ -1,7 +1,7 @@
Name: irqbalance
Version: 1.7.0
Release: 3%{?dist}
Epoch: 1
Release: 4%{?dist}
Epoch: 2
Summary: IRQ balancing daemon
License: GPLv2
@ -69,6 +69,9 @@ fi
/sbin/chkconfig --del irqbalance >/dev/null 2>&1 || :
%changelog
* Wed Aug 05 2020 Peter Robinson <pbrobinson@fedoraproject.org> - 2:1.7.0-4
- Epoch never can go backwards
* Tue Aug 04 2020 Neil Horman <nhorman@redhat.com> - 2:1.7.0-1
- Update to latest upstream (bz 1866002)