Bug#819529: marked as done (transition: libcrypto++)
Your message dated Sun, 17 Apr 2016 10:43:23 +0200
with message-id <57134CAB.7090105@debian.org>
and subject line Re: Bug#819529: transition: libcrypto++
has caused the Debian Bug report #819529,
regarding transition: libcrypto++
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.)
--
819529: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819529
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: transition: libcrypto++
- From: "Laszlo Boszormenyi (GCS)" <gcs@debian.org>
- Date: Wed, 30 Mar 2016 07:38:45 +0200
- Message-id: <1459316325.3465.45.camel@debian.org>
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: transition
I'd like to do the libcrypto++ 5.6.1 to 5.6.3 transition. The latter is
already in experimental. Affected package maintainers are noted,
waiting for feedback. For the time being, I've rebuilt all affected
packages on amd64:
amule
armory
clementine
murasaki
pycryptopp
synergy
tegrarcm (non-free)
All built successfully and as the libcrypto++ libraries are
co-installable, binNMUs can be enough.
Cheers,
Laszlo/GCS
--- End Message ---
--- Begin Message ---
On 03/04/16 13:13, Jonathan Wiltshire wrote:
> Control: tag -1 confirmed
>
> On 2016-03-30 06:38, Laszlo Boszormenyi (GCS) wrote:
>> I'd like to do the libcrypto++ 5.6.1 to 5.6.3 transition. The latter is
>
> Please go ahead.
And it's over.
Cheers,
Emilio
--- End Message ---
Reply to: