[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

New policy for backports.org

Hi folks, 

from now on we have some small changes in our upload policy. Biggest changes
are the new version numbers and the incluѕion of debian changelogs. Please
read it carefuly and post any questions to the ml. 

*** Start *** 

* Use "etch-backports" or "sarge-backports" as distribution, neither "stable" nor "unstable".
* Append "~bpo${debian_release}+${build_int}" to the version number, e.g. "1.2.3-4" now becomes "1.2.3-4~bpo40+1", 
  or for native packages, "1.2.3" becomes "1.2.3~bpo40+1".
* Please only upload package with a noteable userbase. User request for the 
  package maybe an indicator.
* Reconsider if the package can be installed directly from testing without any
  recompilation and handled via pinning[3].
* Don't backport minor version changes without any user visible changes or 
* The package should be in testing. Of course there are some execptions:
  Security updates. If your package had a security update you can upload a
  new backport even if its not yet in testing. There are also some other
  exeception for packages like the kernel, xorg or oo.org. 
* If you upload security updates please inform formorer@formorer.de about the
  update (Please include which Bugs (CVE!) have been fixed in which versions) 
* Include all changelog entries since the last version on backports.org or 
  since stable if it's the first version. You should to this by passing
  "-v<version>" to dpkg-buildpackage.
  Eg: 'debuild -sa -v0.7.5-2', where '0.7.5-2' is the version in stable.

If you want an exception or are unsure about uploading a package. Talk with 

[1] backports-users@lists.backports.org
[2] http://backports.org/debian/new.html
[3] http://wiki.debian.org/AptPinning

*** END ***


Alexander Wirt, formorer@formorer.de 
CC99 2DDD D39E 75B0 B0AA  B25C D35B BC99 BC7D 020A

Attachment: signature.asc
Description: Digital signature

Reply to: