Le samedi 02 mars 2019 à 17:17 +0100, Sebastian Andrzej Siewior a écrit : > On 2019-03-02 11:54:54 [+0100], Sébastien Villemot wrote: > > Le samedi 02 mars 2019 à 11:26 +0100, Sebastian Andrzej Siewior a écrit : > > > > > > So if the bug is really in libssl1.1 then I don't see why you should do > > > something. I will try to backport that commit then and make a new > > > upload. > > > > Note that the bug has already been fixed in Debian (r-cran-openssl > > 1.2.2+dfsg-1), so no need for a new upload. > > Now I am confused. It is either a bug in openssl and should be fixed or > it is a bug in r-cran-openssl and should be fixed there. > So which one is it?
From Debian's point of view, it is now both, since the bug has been cloned: #923447 for r-cran-openssl (which is now fixed), and #923516 for openssl (still open). There is nothing left to do for r-cran-openssl now, at least for buster. For openssl, it's up to its maintainers to decide what to do now. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
signature.asc
Description: This is a digitally signed message part