Page History

...

This is instructions on how to make the debian directory in the SpamAssassin source match that from the Debian and Ubuntu packaging. This is used in the daily Ubuntu builds mentioned on DownloadFromSvn.

The Debian and Ubuntu packages of SpamAssassin have been identical lately. Consistency is nice. If the Ubuntu package version does not contain the string "ubuntu", then it's identical to Debian's.

...

• 10_change_config_paths - I would love to see this applied to eliminate the variance between /etc/spamassassin and /etc/mail/spamassassin between Debian based distributions and everything else. Somebody argued against it for backward compatibility, but I think that's a terrible argument because it can easily be handled with symbolic links.
• 20_edit_spamc_pod is was rejected in bug 6602. It's related to stuff in debian/rules that moves the spamd man page to a different section. Again, I think it's probably better to have it applied for consistency, and I think Debian makes these choices well.
• 30_edit_README - I think this is just deleting text that is no-longer relevant, so it should be applied.
  

Manually rebuilding via launchpad

1. You'll need to be a member of http://launchpad.net/~spamassassin - click the "Join the team".
2. Commit changes to SpamAssassin trunk.
3. Go to http://code.launchpad.net/~vcs-imports/spamassassin/trunk
4. Log in.
5. Click the "Import Now" button in the "Import details" section just to the right of "The next import is scheduled to run in N hours." The button is not there if you're not logged in. (Wait for the import to finish.)
6. Go to http://code.launchpad.net/~spamassassin/+recipe/spamassassin-daily
7. Click "Request build(s)" (in green near the bottom). Request a build for a release you can test on. (Wait for the build to finish.)
8. Install the freshly built packages from that PPA and test.
9. Request builds for the rest of the releases, and verify that they built successfully.
   

If a build fails, follow the "buildlog" links. They generally give useful errors. The #launchpad channel on irc.freenode.net is often helpful.

Manually building locally

1. Download trunk:

svn checkout http://svn.apache.org/repos/asf/spamassassin/trunk

cd trunk

1. In the trunk directory, create a pkgrules directory containing the rules from the latest sa-update, something like:

sudo sa-update; mkdir pkgrules; cp /var/lib/spamassassin/3.003002/updates_spamassassin_org/* pkgrules/

1. Create the .orig.tar.gz

tar -zcvf ../spamassassin_3.3.2.orig.tar.gz .

1. In the trunk directory, run the build command:

debuild -us -uc -sa