Tim,
I noticed that for R14 is in build-deps ready "better" version of sudo-trinity. I wanted to put this into v3.5.13.1, but there is a problem with the version number. Previous package sudo-trinity had a version derived from the original package sudo - for example 1.7.2p7-1. New package has version 1.0, but this making it the "older" than previous package.
It would be possible to increase the number of "epoch" in package - for example to package version 1:1.0-1?
Slavek --
Tim,
I noticed that for R14 is in build-deps ready "better" version of sudo-trinity. I wanted to put this into v3.5.13.1, but there is a problem with the version number. Previous package sudo-trinity had a version derived from the original package sudo - for example 1.7.2p7-1. New package has version 1.0, but this making it the "older" than previous package.
It would be possible to increase the number of "epoch" in package - for example to package version 1:1.0-1?
I have been told several times to never increase the epoch; if the version number must be incremented then make it 2.0.
Tim
On Saturday 15 of September 2012 21:06:33 Timothy Pearson wrote:
Tim,
I noticed that for R14 is in build-deps ready "better" version of sudo-trinity. I wanted to put this into v3.5.13.1, but there is a problem with the version number. Previous package sudo-trinity had a version derived from the original package sudo - for example 1.7.2p7-1. New package has version 1.0, but this making it the "older" than previous package.
It would be possible to increase the number of "epoch" in package - for example to package version 1:1.0-1?
I have been told several times to never increase the epoch; if the version number must be incremented then make it 2.0.
Tim
I assume that the increase epoch is precisely for cases where there is a significant change / replacement program, where the new program has a lower version number than the previous one. This is exactly the case, as it is now sudo-trinity. However, an increase in version number to 2.0 also solves the problem.
You prefer an increase in version number to 2.0? I'll wait for the update in build-deps for R14 and then I'll take packages also into v3.5.13.1.
Slavek --
On Sunday 16 of September 2012 02:09:42 Slávek Banko wrote:
I assume that the increase epoch is precisely for cases where there is a significant change / replacement program, where the new program has a
lower
version number than the previous one. This is exactly the case, as it is
now
sudo-trinity. However, an increase in version number to 2.0 also solves
the
problem.
You prefer an increase in version number to 2.0? I'll wait for the
update in
build-deps for R14 and then I'll take packages also into v3.5.13.1.
Slavek
I noticed that sudo-trinity for R14 has the section 'kde' - I suppose it'll probably change the 'tde'. For this reason, I'm not waiting for a updated package for R14 and into v3.5.13-sru I have included sudo-trinity marked as version 1.9.
This should solve the previous complications with replacing sudo on Ubuntu. New installations v3.5.13.1 should be so again a bit easier. Thank you Tim.
Slavek --
-
Slávek Banko -
Timothy Pearson