Your message dated Sun, 24 Jul 2016 16:21:43 +0000
with message-id <[email protected]>
and subject line Bug#828295: fixed in epic5 2.0-1
has caused the Debian Bug report #828295,
regarding epic5: 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 [email protected]
immediately.)


-- 
828295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828295
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: epic5
Version: 1.1.11-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/epic5_1.1.11-1_amd64-20160529-1417

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: epic5
Source-Version: 2.0-1

We believe that the bug you reported is fixed in the latest version of
epic5, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kurt Roeckx <[email protected]> (supplier of updated epic5 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 [email protected])


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

Format: 1.8
Date: Sun, 24 Jul 2016 17:34:28 +0200
Source: epic5
Binary: epic5
Architecture: source
Version: 2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Kurt Roeckx <[email protected]>
Changed-By: Kurt Roeckx <[email protected]>
Description:
 epic5      - epic irc client, version 5
Closes: 828295 829761
Changes:
 epic5 (2.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Add CPPFLAGS to the CFLAGS, remove -Wall
   * Make it build reproducible.  Patch from Reiner Herrmann
     <[email protected]> (Closes: #829761)
   * Update config.patch to apply and only have irc.debian.org as
     default.
   * Make it build using openssl 1.1 (Closes: #828295)
   * Use dh_prep instead of dh_clean -k
   * Add sh -e in the prerm
   * Use sh instead of bash in the preinst
Checksums-Sha1:
 c3962cab16fbe7c4aeefe00333ac516060ab7713 1704 epic5_2.0-1.dsc
 5aea2e85b7361429175212f349af5c1db58399dc 802756 epic5_2.0.orig.tar.xz
 25d28931e17ae4dc7ad12b8ccfbeae2a51370a65 17208 epic5_2.0-1.debian.tar.xz
Checksums-Sha256:
 17e77d7ac0f1c6e7018474eaf0588acd2574a1269bc478599103d90a4593981d 1704 
epic5_2.0-1.dsc
 c7f8aacfa9a81c76dc24c2cad355850327be428681415a2491a7bc8639feecdf 802756 
epic5_2.0.orig.tar.xz
 3e0ab2b3c4b5432eddc477e8d91f5b75a37e5eddd9df36dcb22f591b03feb836 17208 
epic5_2.0-1.debian.tar.xz
Files:
 9b2de32af311f941837f8509ccc6abf0 1704 net optional epic5_2.0-1.dsc
 15dc7a1103d162e841ac494c5d5017cb 802756 net optional epic5_2.0.orig.tar.xz
 e337662c4e23b328f58e3506554c417c 17208 net optional epic5_2.0-1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJXlOHTAAoJEOPE3c0eTBJE2iQP/2zrngLN/j4eNSiE14egU9Gz
DUIsWXDd+C5slXekLuWTIGRfPW2S7JJma3bk4nfWuc3kigI+2peZuVPmytRFi6Qb
RM/KAtE3ak05+AOQkimMcIB2yDMclpjiWrdVkDdPAsqHlRS5H8ldneZMIfBYzyC5
0px2AXS/RcU3+xP3jUFkwOAajpEAd6Tx1/JSFO2iCNF16Gk9Vrdi1WTXq/O2MBry
3z5p+wBL0y454e/j6PUJG+WW+VNTi+MuOxMQ5aDcfnEwbAuWipHj0t3rXAWEboWe
a8KY+WVPtY3XGwtnnz0xTbXDKhVDCx4jzgGQ7E8cIA8xLh6zPgFlkYnRHUSD75if
NC3ZKpXKGQIuKQrbGwd+ey5K4WneXjYl8ax3pMZBY8L3vNJiYmlJPDohq+1iyGV0
t9148TI7zwA7qgWLmoCXKFIGB+QlTwrgH0PcGgnA5nLuqOA5FXys2WR/Euch0Kxn
WuE9ZsTmYZEoPC/Jcm43W4SDmdWSx8zzqeSzX5gHhGTYcMjZ8/gZmzfREzH8RWR9
ouoSyy/ObNZyg7kKICKVsM9hYGvhnL5VO1NmY4HHwRsCPqkTrz2U3EVTiPdOPFJH
M8pqcH2E4wCX9yoPt2uiNRmwyFgobRlt9mPHgRaE32bJ5/58hsiDZE0cYenzko5w
nGgWivEAvatyO7NA7rWt
=Me4N
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to