Created attachment 1235256 [details] SVN history and rev graph in eclipse are inconsistent. Description of problem: Last revision of the project does not appear in the revision graph. Version-Release number of selected component (if applicable): applicationXMI=org.eclipse.ui.workbench/LegacyIDE.e4xmi awt.toolkit=sun.awt.X11.XToolkit eclipse.application=org.eclipse.ui.ide.workbench eclipse.buildId=4.6.1.v20160915-0852 ... org.tigris.subversion.subclipse.graph (1.1.1) "Subversion Revision Graph" [Active] How reproducible: I could see this on the trunk. Steps to Reproduce: 1. Change some files on the trunk, then commit them. 2. Replace trunk by a branch in the working copy. 3. Merge trunk to branch using the default merge options. 4. Replace branch by the trunk in the working copy. 5. Ask eclipse to Show Revision Graph and Show History. Actual results: History and revision graph are inconsistent: history shows the last revision on the trunk while revision graph doesn't. Expected results: Last revision is also visible in the rev graph. Additional info: Sample screenshot attached, the last revision on the trunk is 364.
It is important to note that r364 has directory changes compared to r363: r364 | peter | 2016-12-07 20:46:46 CET Changed paths: A /req_coverage/trunk/etc/CEVT/cfg_gdm.dxl A /req_coverage/trunk/etc/req_lst.txt A /req_coverage/trunk/etc/CEVT/cfg_fnrq.dxl M /req_coverage/trunk/lib/libcov.dxl M /req_coverage/trunk/lib/librep.dxl M /req_coverage/trunk/etc/cfg_urq.dxl A /req_coverage/trunk/etc/CEVT A /req_coverage/trunk/log/ValidationTestReport.html A /req_coverage/trunk/etc/swc_lst.txt 2016-12-07: working state. ---------------------------------------------------------------------------- r363 | peter | 2016-12-03 10:08:08 CET Changed paths: D /req_coverage/trunk/etc/swc_lst.txt M /req_coverage/trunk D /req_coverage/trunk/etc/req_lst.txt M /req_coverage/trunk/lib/libcov.dxl M /req_coverage/trunk/etc/cfg_fnrq.dxl R /req_coverage/trunk/rqc_runner D /req_coverage/trunk/etc/CEVT M /req_coverage/trunk/lib/libinit.dxl M /req_coverage/trunk/etc/cfg_gdm.dxl M /req_coverage/trunk/lib/librep.dxl Local dev merged to trunk. ----------------------------------------------------------------------------
OK, here is what I concluded after some research about the cause of the perceived inconsistency between the history and the revision graph: History lists those revisions which differ from the previous one by the command "svn diff --depth infinity", while the revision graph lists those which differ in the sense of "svn diff --depth empty". But understanding the cause doesn't relieve my feeling of confusion when I try to use these subclipse functions.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.