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

Bug#684647: marked as done (unblock: libcap2/1:2.22-1.2)

Your message dated Mon, 24 Sep 2012 20:31:56 +0100
with message-id <1348515116.6724.13.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#684647: unblock: libcap2/1:2.22-1.2
has caused the Debian Bug report #684647,
regarding unblock: libcap2/1:2.22-1.2
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

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

Please unblock package libcap2.

Version 1:2.22-1.1 adds multiarch support and 1:2.22-1.2 fixes a RC bug in 1:2.22-1.1.
libcap2 has a lot of reverse dependencies, so it should better have multiarch support.

Best regards,
Tobias Hansen

unblock libcap2/1:2.22-1.2

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (650, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
On Mon, 2012-09-17 at 01:17 +0200, Tobias Hansen wrote:
> Am 15.09.2012 21:00, schrieb Adam D. Barratt:
> > 
> > The only remaining query I had was regarding the libpam-cap split-off
> > and how to handle the fact that people upgrading with the automatic
> > installation of Recommends disabled will lose the PAM module during the
> > upgrade.  I don't think there's any realistic way to find out how many
> > such users there are in testing or stable without exposing them to the
> > changes; the more interesting and important question is how many of
> > those people are actually using the PAM module.
> I have no idea how to find that out. Can't we just write it into the
> release notes?

That's one possibility, yes; a NEWS.Debian file might also be

In any case, I've unblocked the current package.  Let's hope we're not
about to discover that there are loads of people using the module in
testing with automatic recommends turned off.



--- End Message ---

Reply to: