Please merge rampart (1.3.0-1) from Debian unstable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rampart (Ubuntu) |
Fix Released
|
Wishlist
|
Thierry Carrez |
Bug Description
Changelogs:
Debian changelog:
rampart (1.3.0-1) unstable; urgency=low
* Build for debian package based largely on Ubuntu package (#561268)
-- Kyo Lee <email address hidden> Wed, 16 Dec 2009 20:50:33 -0800
rampart (1.3.0-0ubuntu5) karmic; urgency=low
* Depend on newer libaxis2c0 so that /usr/lib/axis2/lib is no longer a
symlink and upgrade from 1.2 is handled in the right order (LP: #426752)
-- Thierry Carrez <email address hidden> Mon, 12 Oct 2009 11:17:02 +0200
Ubuntu Changelog:
rampart (1.3.0-0ubuntu7) lucid; urgency=low
* debian/
for every connection receiver_cert is not freed (LP: #460085)
-- Thierry Carrez <email address hidden> Mon, 14 Dec 2009 09:09:58 +0100
The debian unstable package builds fine in chroot:
dpkg-genchanges >../rampart_
dpkg-genchanges: not including original source code in upload
dpkg-buildpackage: binary and diff upload (original source NOT included)
I: Copying back the cached apt archive contents
I: unmounting dev/pts filesystem
I: unmounting proc filesystem
I: cleaning the build env
I: removing directory /var/cache/
I: Current time: Sat Jun 5 19:52:18 EDT 2010
I: pbuilder-
A patch is attached with the merged changes and it applies fine on -p0:
$ patch -p0 < diff.debdiff
patching file debian/changelog
patching file debian/
patching file debian/
patching file debian/rules
Related branches
tags: | added: patch |
Changed in rampart (Ubuntu): | |
assignee: | nobody → Thierry Carrez (ttx) |
importance: | Undecided → Wishlist |
status: | New → In Progress |
Three problems in this merge proposal: /wiki.ubuntu. com/DebianMaint ainerField, since this is a merge
* debian/changelog entry should mention this merge bug as fixed:
"Merging with debian unstable (LP: #590268)"
* debian/changelog should *not* mention an old bug as fixed: "(LP: #460085)"
* In debian/control, the "Maintainer:" should be set according to https:/
I sponsored a package with these three fixes applied.