[Bug 261642] [NEW] Please sync seccure 0.3-2 (main) from Debian unstable (main)
Launchpad Bug Tracker
261642 at bugs.launchpad.net
Tue Aug 26 23:53:40 BST 2008
You have been subscribed to a public bug by James Westby (james-w):
Binary package hint: seccure
seccure 0.3-2 contains a critical bug-fix for the package, where it is rendered
completely useless without it. We should not ship Intrepid with the current
I am the Debian maintainer, and I made the upload to fix it.
seccure (0.3-2) unstable; urgency=low
* Make failure to mlock all memory only a warning, and re-enable gcrypt's
memory locking. Changes in pam since etch mean that the kernel's defaults
for memory locking are now respected, and seccure tries to lock more
memory than that, which means that the program can't be started. The patch
is from the upstream author, who considers it a stop-gap, but doesn't
anticipate having a proper fix before lenny. (Closes: #489835)
* Don't ignore "$(MAKE) clean" errors. The normal reason for this is the use
of autotools leading to the makefile not necessarily being present when
the clean target is run, be this package doesn't use autotools, so that
* Add a description to debian/patches/10-man-hyphen.dpatch.
* Update the standards version to 3.8.0 (no changes required).
* Release team: this isn't the diff that I sent you, I apologise. My sponsor
suggested that fixing these small things wouldn't be a problem.
-- James Westby <jw+debian at jameswestby.net> Wed, 06 Aug 2008 11:33:27
** Affects: seccure (Ubuntu)
Please sync seccure 0.3-2 (main) from Debian unstable (main)
You received this bug notification because you are a member of Ubuntu Sponsors for universe, which is a direct subscriber.
More information about the Ubuntu-universe-sponsors