On 27/07/15 12:01, Alastair McKinstry wrote: > > > > On 27/07/2015 10:50, Emilio Pozuelo Monfort wrote: >> On 27/07/15 10:20, Alastair McKinstry wrote: >>> >>> Dear Release managers, >>> >>> Can you please check the autolibdap transition? I believe the transition >>> has completed but the regex in the transition tracker is wrong due to >>> multiple sonames simultaneously changing in different binary packages in >>> the tracker. > >> I don't understand what you're saying. > >> The transition cannot have completed because libdap is still in > experimental. > >> Emilio > > The transition was libdap 3.12 -> libdap 3.14 which changed sonames. > libdapclient3 -> libdapclient6 > libdap11 -> libdap17
That should have completed: libdap | 3.14.0-2 | testing | source libdap | 3.14.0-2 | unstable | source > There is an upcoming _second_ transition due to g++ which changes > package names. > I hope to get the first libdap transition to complete, to test the > second in experimental. > I have not put this into unstable yet as it conflicts with completing > the netcdf transition. Don't put that in unstable until you get the green light from the RT. Emilio > Given the mix of netcdf / gfortran5 / g++5 transitions it would be best > to get netcdf to complete before gfortran / g++. > > regards > Alastair > > > > > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
