Let's say that a bug report was filed against your package, #54321, and it describes a problem that you can solve. To create a new Debian revision of the package, you need to:
Tip: how to easily get the date in required format? Use `822-date`, or `date -R`.
Now let's consider a different, a wee bit more complicated situation - a new upstream version was released, and of course you want it packaged. You need to do the following:
uupdate -u gentoo-0.9.13.tar.gz
Of course, replace this file name with the name of your program's new source
archive. uupdate(1)
will properly rename that tarball, try to
apply all the changes from your previous .diff.gz file, and update the new
debian/changelog file.
Note that if you set up `debian/watch' file as described in watch.ex, Section 5.10, you can run
uscan(1)
to automagically look for revised sources, download them,
and run uupdate
.
When you build a new version of the package, you should do the following to verify that the package can be safely upgraded:
Bear in mind that if your package has previously been released in Debian, people will often be upgrading to your package from the version that was in the last Debian release. Remember to test upgrades from that version, too.
Debian New Maintainers' Guide
version 1.2, 6 April 2002.joy-mg@debian.org