Request for "new upstream version" upgrade.

This doesn't make sense, an upstream project shouldn't have an "ubuntu" release, but rather an upstream release. This new upstream release can then be packaged as a new version in Ubuntu as well. the ubuntuX number should only be incremented if changes are made in Ubuntu to the Ubuntu packaging. If the changes are Ubuntu specific (i.e. packaging, not "upstream code", please file a bug with a debdiff or patch and we can get that updated in Ubuntu.
If this is meant to be a new upstream release, I'd suggest making it so (1.1 or 2.0 depending on how many changes there are) and then request that be packaged. You could prepare the update for Ubuntu as well and request sponsorship (https://wiki.ubuntu.com/SponsorshipProcess). Please join us in #ubuntu-motu on freenode if you'd like to discuss this in an interactive forum.

Sorry, I guess my comments weren't very clear. This is a new package which I created and submitted through REVU. It is in its first release with Ubuntu 11.10. I have some bug fixes that I updated in the package in lp:wakeup, and I would like it if users would be able to get those updates.
Please excuse me if I don't know exactly what I'm talking about. This is my first time having a package included in the Ubuntu repositories. Essentially, I am trying to figure out how to get my updates in launchpad into the package in Ubuntu. Thanks in advance for the help.

I have done some more research into the matter, and believe that this is the proper way to request an upgrade for the package (https://wiki.ubuntu.com/MOTU/Packages/REVUWhatNext). I have updated the Bug info and title accordingly, and subscribed the Ubuntu Universe Sponsors team as detailed in the REVU link.

Adding debdiff attachment.

Fixed debdiff to target precise and close this bug. Attaching.

debdiff applies cleanly and the package build fine in pbuilder.

I went ahead and uploaded it. I do I have one comment though. You should make sure to keep the origin of the items in debian/changelog clear. Usually that only contains changes to the packaging or patches that we carry against the upstream source. Sometimes we highlight upstream changes for new releases. That usually take the format of:

 * New upstream release.
  - First upstream change.
  - Second upstream change.
 * Some change to the packaging in the debian dir.
 * Some patch to the upstream sorce that we in Ubuntu added.

I changed the changelog entry to read:

  * New upstream release (LP: #876649).
   - Fixed lack of time zone in hebcalevents location auto-detect
   - Fixed schedule not outputting "Nothing listed" when no events
   - Fixed reading only first item on schedule.
   - Fixed mix-up of schedule and todo depending on which is called first.
   - Added reading of event location.
   - Removed hard-coding of New Jersey in determing metar ID by IP
   - Fixed inability to set volume when previously muted by user

This way the changes are clearly part of the new upstream release and not things that Ubuntu has added. Hope that makes sense.

Thanks for your work!

This bug was fixed in the package wakeup - 1.1-0ubuntu1

---------------
wakeup (1.1-0ubuntu1) precise; urgency=low

  * New upstream release (LP: #876649).
   - Fixed lack of time zone in hebcalevents location auto-detect
   - Fixed schedule not outputting "Nothing listed" when no events
   - Fixed reading only first item on schedule.
   - Fixed mix-up of schedule and todo depending on which is called first.
   - Added reading of event location.
   - Removed hard-coding of New Jersey in determing metar ID by IP
   - Fixed inability to set volume when previously muted by user
 -- David Glass <email address hidden> Wed, 09 Nov 2011 22:26:14 -0800