Bob Tanner wrote: > Fri Dec 29 14:02:40 CST 2006 Bob Tanner > <tanner at real-time.com> * * Clean up of control > file to make linda and lintian happy * Upgrade to Standards-Version: 3.7.2 > NOTE, I built this on sid, as the changelog file from pristine darcs states the package is "unstable", which equates to sid. Unless we wanna do debian override files and what not, we should change "unstable" to "testing" in the control file and build on etch (as of 01/2007) or do a naming convention for each release, like: netrek-server-vanilla (2.12.0-2) unstable; urgency=low netrek-server-vanilla (2.12.0-1~etch) testing; urgency=low netrek-server-vanilla (2.12.0-1~sarge) stable; urgency=low The issue would be what is newer? ~etch or ~sarge? If I'm running sarge, dist-upgrade to etch, will apt-get do the right thing? There is a convoluted long document on how apt-get figures it out OR how to override the whole thing in your pool directory. I just found it easier to artificially inflate the release number for sid (unstable) and -1 on etch and -2 on sarge. But I'm open to suggestions. Example: netrek-server-vanilla (2.12.0-2) unstable; urgency=low netrek-server-vanilla (2.12.0-2~etch) testing; urgency=low netrek-server-vanilla (2.12.0-1~sarge) stable; urgency=low -- Bob Tanner <tanner at real-time.com> | Phone : (952)943-8700 http://www.real-time.com, Minnesota, Linux | Fax : (952)943-8500 Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288