Your message dated Sat, 05 Nov 2016 16:21:08 +0000
with message-id <e1c33io-000fjn...@fasolo.debian.org>
and subject line Bug#828483: fixed in osslsigncode 1.7.1-2
has caused the Debian Bug report #828483,
regarding osslsigncode: FTBFS with openssl 1.1.0
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.)


-- 
828483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828483
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osslsigncode
Version: 1.7.1-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/osslsigncode_1.7.1-1_amd64-20160529-1503

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 ---
Source: osslsigncode
Source-Version: 1.7.1-2

We believe that the bug you reported is fixed in the latest version of
osslsigncode, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 828...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Stephen Kitt <sk...@debian.org> (supplier of updated osslsigncode package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 05 Nov 2016 17:02:20 +0100
Source: osslsigncode
Binary: osslsigncode
Architecture: source
Version: 1.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt <sk...@debian.org>
Changed-By: Stephen Kitt <sk...@debian.org>
Description:
 osslsigncode - Authenticode signing tool
Closes: 828483
Changes:
 osslsigncode (1.7.1-2) unstable; urgency=medium
 .
   * Switch to https: VCS URIs (see #810378).
   * Build-depend on libssl1.0-dev, converting to OpenSSL 1.1 is going to
     involve a lot of work... Closes: #828483.
   * Switch to debhelper compatibility level 10.
   * Clean up debian/control using cme.
   * Standards-Version 3.9.8, no change required.
   * Clean up debian/rules and debian/copyright.
   * Fix debian/watch.
   * Enable all hardening options.
Checksums-Sha1:
 7335f85b8e346ff4256377a0e0f5169db0666f87 1922 osslsigncode_1.7.1-2.dsc
 c7efcc194ce76982a1bb229278d86e3c16374811 2292 
osslsigncode_1.7.1-2.debian.tar.xz
Checksums-Sha256:
 1467f7107907cb949eb1fae8c33242420937952c5911e53463dd7338a88fa0ef 1922 
osslsigncode_1.7.1-2.dsc
 00300bfe4c541e27ce5f9e81857341f08d57c0c12c0993e4b9bf6553ab16c047 2292 
osslsigncode_1.7.1-2.debian.tar.xz
Files:
 bb11337b5c14e263f20d8aec48fb8c1e 1922 otherosfs optional 
osslsigncode_1.7.1-2.dsc
 93e23fd83a47a36f29cb76886b10d519 2292 otherosfs optional 
osslsigncode_1.7.1-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJYHgKrAAoJEIDTAvWIbYOc3cAP/Ris1s3f5aef1NC1bUmYdTWN
R5W1Mr8Gq4C/3MWHa9qpCG4YVXwW0/0KDSntiROGvtnmB7O7F3UdYpOCvy/91kF0
dZp/HBO1Uqx1a0EdNpSRcTQNbZ946Ga+NwqT96GBKvMXGPFJczBQzrdK9ZtJZbkq
xOk/tPXj4ZBzawJyYsjxzvs7GGknajpmPOshZsMZwgxkQHJLW5m1xsZzE7kCgHmF
+0ge/CrlkuHeb4BMU0FYlQm8JSCJvfhPxIU7tQiT78chrs4yMeQL0neeifD9v/jh
q8KWWzrG1/nekK41icvq4bkkzL0h6ZJ/vVSSbSvLN1g5ZAv88oyOL8cwjQKhkQ4e
GSMQZUPkOf0V4lAoNLnjnpSiux/Htbk4xMWca24T7o1kQUxBQ/wnzhuoEdTlVZR5
wymNTvN+iw93WIdkA+OdxNhb46BXVJXF1Y83DT6+jVab+sJ8lGB/bUZp8LVvOr96
cTkBVeoWn/8LDi2iPmMFWoduQkl8NGRaEtKe0Gn0mIs3eN/iFL7XCQqSw7Hv7xy6
n7Ua2++6tzjLJAff62+0h8+DDGbrbw1FF2w3072hv3NrjVdKMQWmKnl9YtTg0gZV
yUV/7OGUxEnFuetx+kgqKjPsN6eWYtX1v2FDfB31CSK8qXVNhiA971sfDY0qyUy2
ybLnMPg7ayrs8EQH5KlF
=iAgl
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to