summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--debian/README68
1 files changed, 63 insertions, 5 deletions
diff --git a/debian/README b/debian/README
index e989f57..c960806 100644
--- a/debian/README
+++ b/debian/README
@@ -84,12 +84,70 @@ upload some packages with dput!
XXX TODO - document example of git checkout, sig verification, debian git
branch application, build, and generic dput upload.
-XXX TODO - document specifics expected for all package uploads
-XXX TODO - document Debian package upload specifics
-XXX TODO - document Ubuntu package upload specifics
-XXX TODO - document deb.torproject.org package upload specifics
+ Package building QA for $package in Debian/Ubuntu/Tor
+
+It is expected that your package will meet some set of standards for each place
+that you wish to upload. Most the Debian QA process for a package is oral
+folklore and documentation on the Debian website.
+
+XXX TODO: Debian person please link to proper docs on website or add written folk tales here.
+
+Ubuntu's packaging guide can be found here:
+https://wiki.ubuntu.com/PackagingGuide/Complete
+
+Generally your package should build properly with pbuilder, it should have a
+man page, lintian should not complain, and it should be idempotent.
+
+ Uploading $package to Debian
+
+Once you have built Debian packages for the supported suites, you will need to
+be a Debian Developer with upload access or you will need to ask weasel, helix,
+or another Debian Developer to sponsor your packages. If you are a DD and you
+have upload access, you will likely issue the following commands:
+
+ cd /var/cache/pbuilder/result
+ dput *.changes
+
+XXX TODO: Debian person please explain how you expect someone to have their
+package sponsored into the Debian repo
+
+XXX TODO: Tor archive person please
+explain how you expect someone to have their package sponsored into the Tor
+repo
+
+
+ Uploading $package to Ubuntu
+
+Once you have built Ubuntu packages for the supported suites, you will need to
+be a Ubuntu Developer with upload access. In some cases, you can simply open a
+bug in Ubuntu to request a merge from Debian. This should happen automatically
+in most cases unless the specific package is on an Ubuntu automatic importation
+blocklist.
+
+
+ Uploading $package to Ubuntu PPA
+
+On Ubuntu one will use dput to upload into a specific PPA:
+
+ PPA=jacob-appelbaum/tor-project-sandbox
+ cd /var/cache/pbuilder/result
+ dput ppa:$PPA *.changes
+
+
+ Uploading $package to Tor's Debian repository
+
+Once you have built Debian and Ubuntu packages for the supported suites, you
+will need to be a Tor Developer with upload access or you will need to ask
+weasel, helix, or another Tor Developer to sponsor your packages. If you are a
+Tor Developer and you have upload access, you will likely issue the following commands:
+
+ cd /var/cache/pbuilder/result
+ dput byblos *.changes
+
+XXX TODO: Tor archive person please explain how you expect someone to have
+their package sponsored into the Tor repo - do they send a signed email? Do
+they upload a package somewhere?
XXX TODO - automate package building for each maintained software repository -
we should be able to detect the newest stable version, build each package and
automatically test packages.
-