Your message dated Wed, 6 Dec 2017 12:34:56 +0100
with message-id <1b71db21-1b66-da96-1e29-f6608c5d5...@debian.org>
and subject line Looks like fixed in stable.
has caused the Debian Bug report #853782,
regarding ipmitool: Please migrate to openssl1.1 in buster
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 ow...@bugs.debian.org
immediately.)


-- 
853782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipmitool
Version: 1.8.17-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/ipmitool_1.8.17-1_amd64-20160529-1430

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt

--- End Message ---
--- Begin Message ---
Reading debian/changelog from version 1.8.18-4:

  * Migrate to OpenSSL1.1 (Closes_# 853782):
    - New debian/patches/0120-openssl1.1.patch:
      + Cherry-picked from upstream.
    - debian/control:
      + Switch Build-Depends from libssl1.0-dev to
        libssl-dev to build against OpenSSL 1.1.

So, this has been fixed, but the changelog didn't close the bug properly
due to a syntax typo. I'm therefore hereby closing this bug.

Cheers,

Thomas Goirand (zigo)

--- End Message ---

Reply via email to