[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#785053: marked as done (jessie-pu: package nss-pam-ldapd/0.9.4-3)

Your message dated Sat, 02 Apr 2016 14:20:04 +0100
with message-id <1459603204.2441.216.camel@adam-barratt.org.uk>
and subject line Fix included in stable
has caused the Debian Bug report #785053,
regarding jessie-pu: package nss-pam-ldapd/0.9.4-3
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
785053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785053
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian.org@packages.debian.org
Usertags: pu

I would like to fix #759544 in jessie.

There is a fix already in 0.9.5-2 in testing and unstable
(avoid-signal-race.patch as seen in the package).

I see a couple of ways to solve this:

- prepare 0.9.4-3+deb8u1

  This will require backporting the patch from 0.9.5-2 and a few related
  changes that ended up in 0.9.5 upstream. This would introduce the
  least number of changes but the biggest downside of this is that it
  will be a new, less tested combination of changes compared to the
  other solutions.

- prepare 0.9.5-2~deb8u1

  This will be based on the current version in testing and is probably
  the most stable and well tested version currently available that
  includes the fix. The 0.9.5 release otherwise mostly contains small
  fixes. The only new feature is adjusting the Out-Of-Memory killer.
  Making the module name configurable at build time results in a bit of
  a diff but impact should be limited.

- prepare 0.9.6-1~deb8u1

  The new (to be released) upstream version will include the fix but
  also includes a number of new features.

I think 0.9.5-2~deb8u1 would result in the best overall quality of the
package in stable but 0.9.4-3+deb8u1 would result in a smaller debdiff.

Please let me know what you think.

Thanks,

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
-- arthur - adejong@debian.org - http://people.debian.org/~adejong --

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
--- Begin Message --- 
Version: 8.4

Hi,

The packages referenced by these bugs were included in today's stable
point release.

Regards,

Adam

--- End Message ---
Reply to: