Bug#855476: marked as done (nmu: last rebuilds against openssl1.1)
Your message dated Sat, 18 Feb 2017 21:36:00 +0000
with message-id <a7e37e74-eb2b-02b2-be81-3d29a2e80eb2@thykier.net>
and subject line Re: nmu: last rebuilds against openssl1.1
has caused the Debian Bug report #855476,
regarding nmu: last rebuilds against openssl1.1
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.)
--
855476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855476
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: binnmu
Severity: normal
The following binNMU should move the remaining packages which are still
linked against libssl1.0.2 in the archive to libssl1.1. Each one of them
built successfully against openssl 1.1.0e recently [0] on amd64. I
checked the build logs and each source package had at least one binary
package linked against libssl so I doubt that we will lose ssl support
somewhere.
nmu erlang-p1-tls_1.0.7-2 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu ettercap_1:0.8.2-3 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu eurephia_1.1.0-6 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu fdm_1.7+cvs20140912-1 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu goldencheetah_4.0.0~DEV1607-2 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu httrack_3.48.24-1 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu hyphy_2.2.7+dfsg-1 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu htmldoc_1.8.27-8 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu httping 2.5-1 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu ibm-3270_3.3.14ga11-1 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu identity4c_1.0-1 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu ike-scan_1.9.4-1 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu istgt_0.4~20111008-3 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu lepton_1.2.1-2 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu libtins_3.4-2 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu mokutil 0.2.0-1 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu pam-pkcs11_0.6.9-1 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu bitcoin_0.13.1-0.1 . ANY . unstable . -m "rebuild against openssl 1.1"
nmu efitools_1.4.2-2 . ANY . unstable . -m "rebuild against openssl 1.1"
Only sid-only package should remain after these binNMUs.
[0] https://breakpoint.cc/openssl-rebuild/2017-02-16-rebuild-sid-openssl1.1.0e/successful
Sebastian
--- End Message ---
--- Begin Message ---
On Sat, 18 Feb 2017 22:21:42 +0100 Sebastian Andrzej Siewior
<sebastian@breakpoint.cc> wrote:
> Package: release.debian.org
> User: release.debian.org@packages.debian.org
> Usertags: binnmu
> Severity: normal
>
> The following binNMU should move the remaining packages which are still
> linked against libssl1.0.2 in the archive to libssl1.1. Each one of them
> built successfully against openssl 1.1.0e recently [0] on amd64. I
> checked the build logs and each source package had at least one binary
> package linked against libssl so I doubt that we will lose ssl support
> somewhere.
>
> nmu erlang-p1-tls_1.0.7-2 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu ettercap_1:0.8.2-3 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu eurephia_1.1.0-6 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu fdm_1.7+cvs20140912-1 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu goldencheetah_4.0.0~DEV1607-2 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu httrack_3.48.24-1 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu hyphy_2.2.7+dfsg-1 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu htmldoc_1.8.27-8 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu httping 2.5-1 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu ibm-3270_3.3.14ga11-1 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu identity4c_1.0-1 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu ike-scan_1.9.4-1 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu istgt_0.4~20111008-3 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu lepton_1.2.1-2 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu libtins_3.4-2 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu mokutil 0.2.0-1 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu pam-pkcs11_0.6.9-1 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu bitcoin_0.13.1-0.1 . ANY . unstable . -m "rebuild against openssl 1.1"
> nmu efitools_1.4.2-2 . ANY . unstable . -m "rebuild against openssl 1.1"
>
> Only sid-only package should remain after these binNMUs.
>
> [0] https://breakpoint.cc/openssl-rebuild/2017-02-16-rebuild-sid-openssl1.1.0e/successful
>
> Sebastian
>
>
Scheduled, thanks.
~Niels
--- End Message ---
Reply to: