Apache OpenOffice (AOO) Bugzilla – Issue 68694
Web-based CVS doesn't show changes in branch
Last modified: 2017-05-20 10:27:45 UTC
When trying to view changes to png images within default_images module (using Web CVS), the latest revision is not shown- it always seems to just show the MAIN branch. E.g. Try the following image: http://ui.openoffice.org/source/browse/ui/default_images/res/helpimg/border_ca_1.png?only_with_tag=cws_src680_hcshared04 I assumed this was a time lag (as with anon CVS), but it in fact seems to be a bug. (Using Firefox and MS IE)
have not confirmed this but am routing to support. Support, can you look into this, please? thanks louis
The commit logs are different; the image also is positioned slightly (very slight) different in for the 2 revisions. Can you please attach the 2 different PNG images (the original and the changed) in this issue itself? We would like to make sure that the differences are considerable. BTW, has this been reported by anyone else before?
Hmmm, maybe I didn't chose the best example. Let us consider the new files added to 'Tango' in the ooo_custom_images module. The following should diplay the icon added 6days ago: http://ui.openoffice.org/source/browse/ui/ooo_custom_images/tango/fpicker/res/Attic/fp011.png?rev=1.1.2.1&only_with_tag=cws_src680_jimmactango2&view=markup The tags are correctly updated, however, on WinXP using Firefox no icon (.png) is displayed. It seems the image always shown is that from HEAD. Hope that clarifies things.
Created attachment 38813 [details] Screenshot to clarify problem (annotations in red)
Updating whiteboard .
Was able to reproduce the issue in 3.5.1 of CEE 1) Add a 1.png file and commit into a repo. 2) Create a branch . 3) Checkout the branch. 4) Copy 2.png file and overwrite on the top of the 1.png 5) Commit the changes into the branch. 6) Notice that in the ViewCVS both the revisions show the same image of 1.png file. Please note that in the cvs repo there is no discrepancies. However in trying to reproduce the same in Snake Release of CEE was not able to reproduce this issue . Resolving this issue as Resolved -Later for now . If there is any concern please reopen this issue .
Reopening to modify with the current state of the issue .
This issue has been fixed via the upgrade to 4.5.2 . Closing this issue.