On 2017-11-04 11:55:24, Sebastian Ramacher wrote: > On 2017-10-31 14:06:06, Emilio Pozuelo Monfort wrote: > > Control: tags -1 confirmed > > > > On 30/10/17 15:21, Sebastian Ramacher wrote: > > > Package: release.debian.org > > > Severity: normal > > > User: release.debian.org@packages.debian.org > > > Usertags: transition > > > Control: forwarded -1 https://release.debian.org/transitions/html/auto-libva.html > > > Control: block -1 by 879064 > > > > > > libva 2.0 was released and it bumped its SONAME, so it needs a transition. Note > > > that somme reverse dependencies need sourceful uploads coordinated with the > > > start of the transition: libva-utils and intel-vaapi-driver. > > > > > > mesa (#879064) needs to be fixed. A rebuild will correctly rebuild against libva > > > 2.0, but it has an hard-coded dependency on libva1 which could be avoided by > > > using dh_libva from libva-dev. > > > > > > libyami currently fails to build (no bug, since I maintain that), but has a fix > > > available upstream. I'll upload a fixed version together with libva. > > > > > > All other reverse dependencies build fine. > > > > mesa is fixed now. Please go ahead. > > Thanks. libva, libva-utils and intel-vaapi-driver uploaded. I'll handle libyami > on Monday. I've also uploaded libyami and filed for the failed binNMUs of nageru and ring. Please also binNMU mesa and vdpau-video so that their libva-driver-abi-X.Y dependencies get updated to libva-driver-abi-1.0. Since the start of the transition, qtav also entered the archive and uses hardcoded library dependencies (#880884). Cheers -- Sebastian Ramacher
Attachment:
signature.asc
Description: PGP signature