Bug 267151

Summary:	Kompare does not understand a diff with skipped originals
Product:	[Applications] kompare	Reporter:	Christopher Yeleighton <giecrilj>
Component:	parser	Assignee:	Kompare developers <kompare-devel>
Status:	REPORTED ---
Severity:	minor
Priority:	NOR
Version:	4.1.22120
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	test case: 2/2.txt intentionally missing

Description Christopher Yeleighton 2011-02-25 14:13:08 UTC

Version:           4.0.0 (using KDE 4.6.0) 
OS:                Linux

I often create an override directory structure containing only modified files.  When I create a diff of that, I do not want to have the unmodified original files deleted, so I ask Kompare not to treat missing files as empty.  When Kompare is done with the diff, it reports the result as "malformed".

Reproducible: Always

Steps to Reproduce:
Tell Kompare to compare 1 to 2 ignoring missing files.

Actual Results:  
Warning: malformed diff.

Expected Results:  
Some less scary way to express the observation, possibly without an intervening dialogue box.



OS: Linux (x86_64) release 2.6.34.7-0.7-desktop
Compiler: gcc

(Note that the actual diff contains localized messages from diff that cannot be turned off AFAIK; in order to recognize the format, Kompare would have to get text from diff or else run a micro diff experiment somewhere aside)

Comment 1 Christopher Yeleighton 2011-02-25 14:15:06 UTC

Created attachment 57525 [details]
test case: 2/2.txt intentionally missing

Comment 2 Andrew Crouthamel 2018-11-05 03:12:24 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 3 Andrew Crouthamel 2018-11-17 05:03:13 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 4 Justin Zobel 2022-12-18 08:18:31 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 5 Bug Janitor Service 2023-01-02 05:27:03 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!