The current keybase version in the tree is quiet outdated. Actually I'm no longer able to add new machines with the current version 1.0.21. Can it be bumped to the current release 1.0.33? There are also several missing version bumps between 1.0.21 and 1.0.33: - 1.0.27 - 1.0.28 - 1.0.29 - 1.0.30 - 1.0.31
What would be the purpose of having "all versions between 1.0.21 and 1.0.33"
(In reply to Jeroen Roovers from comment #1) > What would be the purpose of having "all versions between 1.0.21 and 1.0.33" I can imaging the maintainer might want to offer some older versions as well. Maybe there's a policy for it? Looking at it the other way, if the bumps would've happened immediately all these versions would already be there :)
(In reply to Simon from comment #0) > The current keybase version in the tree is quiet outdated. > Actually I'm no longer able to add new machines with the current version > 1.0.21. Can it be bumped to the current release 1.0.33? > I pushed 1.0.33 to tree. Please try it out and let me know if you run into any issues. > There are also several missing version bumps between 1.0.21 and 1.0.33: > - 1.0.27 > - 1.0.28 > - 1.0.29 > - 1.0.30 > - 1.0.31 Sorry about that, I didn't bump the package in a while. If you think you would check out the intermediate versions I can add them to the tree.
(In reply to Simon from comment #2) > (In reply to Jeroen Roovers from comment #1) > > What would be the purpose of having "all versions between 1.0.21 and 1.0.33" > > I can imaging the maintainer might want to offer some older versions as well. > Maybe there's a policy for it? I am not aware of a policy there. But generally I do like to keep older versions around for a while, just so to give users who don't update their system twice daily a chance of some historical continuity :) > Looking at it the other way, if the bumps would've happened immediately all > these versions would already be there :)
(In reply to Nicolas Bock from comment #3) > (In reply to Simon from comment #0) > > The current keybase version in the tree is quiet outdated. > > Actually I'm no longer able to add new machines with the current version > > 1.0.21. Can it be bumped to the current release 1.0.33? > > > > I pushed 1.0.33 to tree. Please try it out and let me know if you run into > any issues. > > > There are also several missing version bumps between 1.0.21 and 1.0.33: > > - 1.0.27 > > - 1.0.28 > > - 1.0.29 > > - 1.0.30 > > - 1.0.31 > > Sorry about that, I didn't bump the package in a while. If you think you > would check out the intermediate versions I can add them to the tree. No problem, thanks for the quick fix! I'm fine with the latest version, so for me personally there's no need to add the intermediate ones.
Thanks!
