Bug#919043: nmu: ckermit_302-5.3 (stretch)
Control: tags -1 + moreinfo
On Sat, 2019-01-12 at 09:29 +0100, Andreas Beckmann wrote:
> since sid already has a +b1 binnmu, but currently FTBFS in sid for
> other reasons, you may need to apply some force to get the newer
> version into stable.
Specifically, if that is still the case at the next point release, then
the binNMU would need prop-upping in to sid, which may break it even
more.
> nmu ckermit_302-5.3 2 . ANY . stretch-proposed-updates . -m "Rebuild
> against openssl1.0 1.0.2q"
The initial arguments are the other way around fwiw - "nmu 2 ckermit" -
and the suite listed is always the base suite, so "stretch".
> Note that this needs to be built against openssl1.0 from
> stretch-proposed-updates, not stretch.
Builds in p-u have p-u in their sources list, so that should be fine.
If one wanted to be really sure (e.g. for cases where the build-
dependency would already be present in the chroot) then --extra-depends
could be used.
> That's the message from starting kermit in stretch:
>
> ?OpenSSL libraries do not match required version:
> . C-Kermit built with OpenSSL 1.0.2j 26 Sep 2016
> . Version found OpenSSL 1.0.2q 20 Nov 2018
> OpenSSL versions prior to 1.0.0 must be the same.
I haven't scheduled the binNMUs yet, as I'm a little confused by that
message - 1.0.2{k,q} are not "OpenSSL versions prior to 1.0.0".
Regards,
Adam
Reply to: