Description of problem: The most recent version of rsnapshot is 1.4.1, but the current Fedora version is 1.3.1, which is now two releases behind. Version-Release number of selected component (if applicable): 1.3.1 How reproducible: Fixed Steps to Reproduce: 1.n/a 2. 3. Actual results: Outdated version Expected results: Updated version Additional info: http://sourceforge.net/p/rsnapshot/mailman/message/34381531/
FYI, myself and a number of package maintainers from other distros were really looking forward to the new snapshot project direction to get releases newer than 1.3.1 available as an official release. Life had gotten in the way, but I will be building a new update based on the new version. It will likely remain in testing for a while to see what sort of backward compatibility issues will come up for it. Given it was about seven years from when 1.3.1 was released to its successor (the 1.4 series) not a package we want to surprise users with an update with until it has had some good testing and vetting. Thank you for getting a bug in on this as it makes sure it stays on my radar. Once I do get a test package available, I would ask that you help get people to test and leave feedback in the fedora packaging system (a link to which should get put into this bug then the build is submitted to testing)
Ping? Meanwhile, rsnapshot-1.4.2 is out (Released Dec 8, 2015) c.f. https://github.com/rsnapshot/rsnapshot/releases https://github.com/rsnapshot/rsnapshot/tags
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
(In reply to Fedora End Of Life from comment #3) > Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is > no longer maintained, which means that it will not receive any further > security or bug fix updates. As a result we are closing this bug. > > If you can reproduce this bug against a currently maintained version of > Fedora please feel free to reopen this bug against that version. If you > are unable to reopen this bug, please file a new report against the > current release. If you experience problems, please add a comment to this > bug. > > Thank you for reporting this bug and we are sorry it could not be fixed. The bug is still present in Fedora 24 and should be reopened. Is it enough to change the Fedora version on this page or is there a specific procedure for reopening?
FYI, see: https://bugzilla.redhat.com/show_bug.cgi?id=1375289 test builds are out for various release