On Wed, Jan 17, 2018 at 12:17 PM, Carl George <carl@george.computer> wrote: > To facilitate packages that require a newer version of libsodium, I have coordinated an update of libsodium in EPEL7 from version 1.0.5 (libsodium.so.13) to version 1.0.16 (libsodium.so.23). To avoid any ABI breakage for existing packages, a new libsodium13 compatibility package has been created that will continue to provide the old version. > > The following packages link against libsodium: > - cjdns > - dnscrypt-proxy > - dnsdist > - fastd > - php-pecl-libsodium > - zeromq > > Remi has already rebuilt php-pecl-libsodium against the new version with an override. In my testing, the other packages continue to be installable and just resolve to libsodium13 instead of libsodium, as expected. > > I have read through the update policies [1][2], but I am unsure where this would fall since the old version will continue to be available with the compatibility package. Do I need to take any additional steps other than submitting the bodhi update for libsodium-1.0.16-1.el7 and libsodium13-1.0.5-1.el7? > My understanding is that this should be sufficient. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
