https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6647
Bug #: 6647
Summary: Sync Debian packaging from v3.3.2-1 to trunk
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: Packaging: debian
AssignedTo: dev@spamassassin.apache.org
ReportedBy: dar...@chaosreigns.com
Classification: Unclassified
Created attachment 4950
--> https://issues.apache.org/SpamAssassin/attachment.cgi?id=4950
Sync Debian packaging
The process of syncing this Debian packaging information is now documented
here: http://wiki.apache.org/spamassassin/SyncDebianPackaging
All modified files:
--- debian/control (revision 1156706)
+++ debian/control (working copy)
--- debian/patches/10_change_config_paths (revision 1156706)
+++ debian/patches/10_change_config_paths (working copy)
--- debian/README.source (revision 0)
+++ debian/README.source (revision 0)
--- debian/changelog (revision 1156706)
+++ debian/changelog (working copy)
This has not been tested, but it can't break anything other than building
Debian packages from trunk, and by far the easiest method of testing is
committing to trunk and kicking off the existing automated launchpad build (
http://wiki.apache.org/spamassassin/DownloadFromSvn#Ubuntu_daily_builds_PPA ).
The delta for the debian directory from Debian and Ubuntu v3.3.2-1 to trunk is
composed entirely of removing two patches because they have already been
applied to trunk: 85_disable_SSLv2 (bug 6601), and
50_sa-learn_fix_empty_list_handling (bug 6603).
This is the same process I used when syncing the current debian directory in
trunk from Debian / Ubuntu package version 3.3.1-2 for bug 6593.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
