[Bug 303502] Re: Use regular expressions in kompare causes "could not parse diff output"

2023-03-28 Thread Bug Watch Updater
** Changed in: kdesdk (Debian)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdesdk in Ubuntu.
https://bugs.launchpad.net/bugs/303502

Title:
  Use regular expressions in kompare causes "could not parse diff
  output"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/303502/+subscriptions


-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 303502] Re: Use regular expressions in kompare causes "could not parse diff output"

2023-01-13 Thread Bug Watch Updater
** Changed in: kdesdk (Debian)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdesdk in Ubuntu.
https://bugs.launchpad.net/bugs/303502

Title:
  Use regular expressions in kompare causes "could not parse diff
  output"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/303502/+subscriptions


-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 303502] Re: Use regular expressions in kompare causes "could not parse diff output"

2018-11-11 Thread Bug Watch Updater
** Changed in: kdesdk (Debian)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdesdk in Ubuntu.
https://bugs.launchpad.net/bugs/303502

Title:
  Use regular expressions in kompare causes "could not parse diff
  output"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/303502/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 303502] Re: Use regular expressions in kompare causes could not parse diff output

2013-04-13 Thread hamish
** Also affects: kdesdk (Debian) via
   https://bugs.kde.org/show_bug.cgi?id=253188
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdesdk in Ubuntu.
https://bugs.launchpad.net/bugs/303502

Title:
  Use regular expressions in kompare causes could not parse diff
  output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/303502/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 303502] Re: Use regular expressions in kompare causes could not parse diff output

2013-04-13 Thread Bug Watch Updater
Launchpad has imported 2 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=253188.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2010-10-04T02:10:17+00:00 Alessandro Ghersi wrote:

Version:   unspecified (using KDE 1.2) 
OS:Linux

Bug reported here:
https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/303502

Add in a regular expression, eg Settings, configure Kompare, Diff,
Options tab and click 'Ignore regexp'. I used ^Version as the regular
expression. Close kompare and execute the following

william@caracal:/tmp$ mkdir dir1 dir2
william@caracal:/tmp$ touch dir1/abc.txt dir2/abc.txt
william@caracal:/tmp$
william@caracal:/tmp$ kompare dir1 dir2 

A dialog stating could not parse output appear making the program
unusable. This is a regression from Ubuntu 8.04.

william@caracal:/tmp$ lsb_release -rd
Description:Ubuntu 8.10
Release:8.10

william@caracal:/tmp$ apt-cache policy kompare
kompare:
  Installed: 4:4.1.2-0ubuntu1.1
  Candidate: 4:4.1.2-0ubuntu1.1
  Version table:
 *** 4:4.1.2-0ubuntu1.1 0
500 http://gb.archive.ubuntu.com intrepid-updates/main Packages
100 /var/lib/dpkg/status
 4:4.1.2-0ubuntu1 0
500 http://gb.archive.ubuntu.com intrepid/main Packages
william@caracal:/tmp$

Reproducible: Didn't try

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/303502/comments/4


On 2013-04-13T08:50:53+00:00 hamish wrote:

Hi,

I can reproduce this on debian/stable (squeeze).

kompare .deb package version 4:4.4.5-1.
help - about says kompare 4.0.0, kde 4.4.5.

using the same regex pattern on the command line for 'diff -I' works ok.

thanks,
Hamish

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/303502/comments/7


** Changed in: kdesdk (Debian)
   Status: Unknown = New

** Changed in: kdesdk (Debian)
   Importance: Unknown = Medium

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdesdk in Ubuntu.
https://bugs.launchpad.net/bugs/303502

Title:
  Use regular expressions in kompare causes could not parse diff
  output

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdesdk/+bug/303502/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs


[Bug 303502] Re: Use regular expressions in kompare causes could not parse diff output

2010-10-03 Thread Alessandro Ghersi
Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE 
program itself, and not with our KDE packages. But don't worry! This issue is 
being tracked by the KDE developers at: 
https://bugs.kde.org/show_bug.cgi?id=253188
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix 
is in in reaches Kubuntu. 

Thanks!

** Bug watch added: KDE Bug Tracking System #253188
   http://bugs.kde.org/show_bug.cgi?id=253188

** Changed in: kdesdk (Ubuntu)
   Status: New = Invalid

-- 
Use regular expressions in kompare causes could not parse diff output
https://bugs.launchpad.net/bugs/303502
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdesdk in ubuntu.

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs