Bug 268800 - Doesn't play well with file symlinks
Summary: Doesn't play well with file symlinks
Status: RESOLVED WORKSFORME
Alias: None
Product: kompare
Classification: Applications
Component: general (show other bugs)
Version: 4.0.0
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kompare developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-18 05:53 UTC by Greg Grothaus
Modified: 2023-01-13 05:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Grothaus 2011-03-18 05:53:25 UTC
Version:           4.0.0 (using KDE 4.4.5) 
OS:                Linux

Diff a file which is a symlink, edit that file (such as applying changes), and then save the file.  Kompare will replace (delete, add) the file rather than modify it, which deletes the symlink and adds a new real file.  It would be preferred if the destination of the symlink was updated and the symlink preserved. 

Reproducible: Always

Steps to Reproduce:
Diff a file which is a symlink, edit that file (such as applying changes), and then save the file.

Actual Results:  
Kompare will replace (delete, add) the file.

Expected Results:  
Kompare will modify the file.

This is a bit of a corner case, but was encountered in the following scenario:  Kompare is used within a script to process a set of files produced by another program (ie: git diff) but the user doesn't want to have kompare process all of the unchanged files in the same subtree.  That script can create a temporary tree with just the changed files as symlinks for kompare to look at.
Comment 1 Andrew Crouthamel 2018-11-05 03:12:13 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-17 04:52:50 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-14 03:09:10 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-29 05:23:47 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2023-01-13 05:14:43 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!