Merge lp:~arky/ubuntu/lucid/libdbg/fix-486641 into lp:ubuntu/lucid/libdbg

[arky]

[arky (arky)]

fixes minor typo bug 486641

[Stefano Rivera (stefanor)]

Hi, please forward this patch (and any other relevant changes we have in this package) to Debian. We can give them the first opportunity to fix it, rather than diverging even further away from them.

[Pascal De Vuyst (pascal-devuyst)]

As mentioned in bug 486641 this package doesn't come from Debian but from the unofficial debian packages from http://debian.speedblue.org
I now subscribed the upstream author by it's launchpad account.

[arky (arky)]

Thanks Pascal!

[Stefano Rivera (stefanor)]

Err, so of course this package doesn't come from debian but an unofficial package. Please forward all our current patches there.

This cannot be merged, as it's targeted to lucid. Please re-target this against maverick.

review: Needs Fixing

[Stefano Rivera (stefanor)]

Marking this work-in-progress to get it off the sponsorship queue.

[Stefano Rivera (stefanor)]

err rejected

Unmerged revisions

3. By arky on 2010-02-10

Fixes typos in debian/control (LP: #486641)

=== modified file 'debian/changelog'
--- debian/changelog	2007-09-17 22:53:03 +0000
+++ debian/changelog	2010-02-10 14:36:18 +0000
@@ -1,3 +1,9 @@
+libdbg (1.2-2ubuntu2) lucid; urgency=low
+
+  * Fixes typos in debian/control (LP: #486641)
+
+ -- arky <[e-mail]>  Wed, 10 Feb 2010 18:51:26 +0530
+
 libdbg (1.2-2ubuntu1) gutsy; urgency=low
 
   * Fix depends line for binary packages

=== modified file 'debian/control'
--- debian/control	2007-09-17 22:53:03 +0000
+++ debian/control	2010-02-10 14:36:18 +0000
@@ -16,10 +16,10 @@
  builds, dbg library use can be compiled away to nothing.
  .
  Rich debugging can only be implemented in large code bases from the outset,
- it is hard to retrofit full defensive programming techniques onto existant
+ it is hard to retrofit full defensive programming techniques onto existing
  code. For this reason it is good practice to use a library like dbg when
  you start a new project. By using dbg extensively you will find bugs
- quicker, and prevent more insideous problems rearing their head later in
+ quicker, and prevent more insidious problems rearing their head later in
  the project's life.
 
 Package: happycoders-libdbg-dev
@@ -33,11 +33,11 @@
  builds, dbg library use can be compiled away to nothing.
  .
  Rich debugging can only be implemented in large code bases from the outset,
- it is hard to retrofit full defensive programming techniques onto existant
+ it is hard to retrofit full defensive programming techniques onto existent
  code. For this reason it is good practice to use a library like dbg when
  you start a new project. By using dbg extensively you will find bugs
- quicker, and prevent more insideous problems rearing their head later in
+ quicker, and prevent more insidious problems rearing their head later in
  the project's life.
  .
- This packages Contains the symlinks, headers, and object files needed to 
+ This package contains the symlinks, headers, and object files needed to 
  compile and link programs which use libdbg.