[Bug 61030] Re: Mistake in ssed string (dapper)

** Changed in: ssed Status: Fix Committed => Fix Released -- Mistake in ssed string (dapper) https://bugs.launchpad.net/bugs/61030 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@list

[Bug 61030] Re: Mistake in ssed string (dapper)

** Changed in: ssed Status: New => Fix Committed -- Mistake in ssed string (dapper) https://bugs.launchpad.net/bugs/61030 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.

[Bug 61030] Re: Mistake in ssed string (dapper)

ssed (3.62-6.2ubuntu2) hardy; urgency=low * Fixed typo in pcre/pcregrep.c:249 (LP: #61030) * Added patch-system into debian/rules -- Ralph Janke <[EMAIL PROTECTED]> Sat, 10 Nov 2007 13:53:52 + ** Changed in: ssed (Ubuntu) Status: In Progress => Fix Released -- Mistake in ssed

[Bug 61030] Re: Mistake in ssed string (dapper)

I have uploaded the bugfix, since there seem to be no changes upstream. ** Attachment added: "Debdiff with the bugfix" http://launchpadlibrarian.net/10457081/ssed_3.62-6.2ubuntu2.debdiff -- Mistake in ssed string (dapper) https://bugs.launchpad.net/bugs/61030 You received this bug notificatio

[Bug 61030] Re: Mistake in ssed string (dapper)

** Changed in: ssed (Ubuntu) Status: Confirmed => In Progress -- Mistake in ssed string (dapper) https://bugs.launchpad.net/bugs/61030 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@

[Bug 61030] Re: Mistake in ssed string (dapper)

Waiting for upstream response -- Mistake in ssed string (dapper) https://bugs.launchpad.net/bugs/61030 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.c

[Bug 61030] Re: Mistake in ssed string (dapper)

** Changed in: ssed (Ubuntu) Assignee: (unassigned) => txwikinger -- Mistake in ssed string (dapper) https://launchpad.net/bugs/61030 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 61030] Re: Mistake in ssed string (dapper)

** Changed in: ssed (upstream) Status: Unknown => Unconfirmed -- Mistake in ssed string (dapper) https://launchpad.net/bugs/61030 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 61030] Re: Mistake in ssed string (dapper)

Reported bug upstream ** Bug watch added: Debian Bug tracker #416510 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416510 ** Also affects: ssed (upstream) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=416510 Importance: Unknown Status: Unknown -- Mistake in ssed string

[Bug 61030] Re: Mistake in ssed string (dapper)

Checked the source for feisty ssed_3.62-6.2build1. The spelling mistake is still there. However, in the pcregrep pcre3_6.7-1ubuntu2 package it is not. Why does ssed not use the pcre package ? ** Changed in: ssed (Ubuntu) Assignee: txwikinger => (unassigned) Status: Needs Info => Conf

[Bug 61030] Re: Mistake in ssed string (dapper)

All my spelling mistake bugs were found while translating the strings in launchpad, then verified by downloading the source. This spelling mistake is still present in ssed 3.62-6.2build1. -- Mistake in ssed string (dapper) https://launchpad.net/bugs/61030 -- ubuntu-bugs mailing list ubuntu-bug

[Bug 61030] Re: Mistake in ssed string (dapper)

Could you please provide more information for reproducing the problem? Could you please show each step you took, provide an example input file? Which version of the package has this bug? Thanks. ** Changed in: ssed (Ubuntu) Assignee: (unassigned) => txwikinger Status: Unconfirmed =>