versionlock.iist 0 or 1

General support questions
Post Reply
hokie1999
Posts: 39
Joined: 2011/08/10 15:03:16

versionlock.iist 0 or 1

Post by hokie1999 » 2021/06/10 15:53:20

Hello,

Can someone tell me the significance of 0 and the 1 in the following /etc/yum/pluginconf.d/versionlock.list


0:netsniff-ng-0.5.8-ESG_1.el7.centos.*
1:net-snmp-libs-5.5-50_CIRT.el7.centos.x86_64

What is the difference? These numbers are EPOCHs.In this versionlock.list, they are always defined with the leading 0 or 1.

Thanks.

sml
Posts: 305
Joined: 2020/01/17 09:01:44

Re: versionlock.iist 0 or 1

Post by sml » 2021/06/10 17:48:02

No, the epoch is not always 0 or 1. It increments each time package version changes in an incompatible way. E.g. consider a package released in 1999 that was versioned like foo-991122, but the next version released in 2001 was foo-010102, and with the version after that , the upstream changed the versioning scheme to foo-1.0. To ensure smooth upgrades, full versions as recorded in the RPM would be:
foo-0:991122
foo-1:010102
foo-2:1.0
Last edited by sml on 2021/06/10 18:11:33, edited 4 times in total.

User avatar
TrevorH
Site Admin
Posts: 33191
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: versionlock.iist 0 or 1

Post by TrevorH » 2021/06/10 18:02:00

Epoch is a bodge for incompetent packagers :-O And it can be any number from 0 on up.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

hokie1999
Posts: 39
Joined: 2011/08/10 15:03:16

Re: versionlock.iist 0 or 1

Post by hokie1999 » 2021/06/10 18:55:17

Makes sense, thanks. :D

Post Reply