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

Bug#768161: marked as done (unblock: dogtag-pki/10.2.0-3)



Your message dated Fri, 07 Nov 2014 15:29:50 +0000
with message-id <2d2f2d1c6dc096636adea8191359b9cf@hogwarts.powdarrmonkey.net>
and subject line Re: Bug#768161: unblock: dogtag-pki/10.2.0-3
has caused the Debian Bug report #768161,
regarding unblock: dogtag-pki/10.2.0-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.)


-- 
768161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768161
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 dogtag-pki

It has been on sid for ~19 days, file conflict with strongswan has been
fixed (for now, proper fix should get in strongswan 5.2.1-5),
changelog as follows:

dogtag-pki (10.2.0-3) unstable; urgency=medium

  * control: Add Breaks/Replaces on strongswan-starter to pki-tools.
    (Closes: #767561)

 -- Timo Aaltonen <tjaalton@debian.org>  Wed, 05 Nov 2014 00:40:10 +0200

dogtag-pki (10.2.0-2) unstable; urgency=medium

  * patches: Fix servlet jar name, and paths to jss4.jar and symkey.jar.

 -- Timo Aaltonen <tjaalton@debian.org>  Fri, 24 Oct 2014 20:39:24 +0300

dogtag-pki (10.2.0-1) unstable; urgency=low

  * Initial release (Closes: #653606)

 -- Timo Aaltonen <tjaalton@debian.org>  Fri, 10 Oct 2014 14:40:12 +0300


unblock dogtag-pki/10.2.0-3

--- End Message ---
--- Begin Message ---
Control: tag -1 wontfix

On 2014-11-05 14:28, Timo Aaltonen wrote:
Please unblock package dogtag-pki

It has been on sid for ~19 days, file conflict with strongswan has been
fixed (for now, proper fix should get in strongswan 5.2.1-5),
changelog as follows:

New in Jessie; sorry, but it's too late for that.

--
Jonathan Wiltshire                                      jmw@debian.org
Debian Developer                         http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

<directhex> i have six years of solaris sysadmin experience, from
            8->10. i am well qualified to say it is made from bonghits
			layered on top of bonghits

--- End Message ---

Reply to: