Re: auto-libdap transition
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
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
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.
Given the mix of netcdf / gfortran5 / g++5 transitions it would be best
to get netcdf to complete before gfortran / g++.
regards
Alastair
- --
Alastair McKinstry, <alastair@sceal.ie>, <mckinstry@debian.org>,
https://diaspora.sceal.ie/u/amckinstry
Software is like Poetry - most of it shouldn't have been written.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVtgFqAAoJEMvmu05dmtOl3xoP/3Gt/jdn9qgXTlylz5yeOTdG
/jHgeJx+2rk9UgtVriJpCEQDq7VrI6vU4/Lc5sB6TJpNIKxgwEyqkRDd/gGzztBJ
/Z/afN26vFTP39Sp3b7yzU3PF9o+EKe8PlKJibJdtywWgJII0T78H5591X2fojib
CZ6gFWmLiugNYkMRdWP0u8Go9qyNFoUHIbwxBhFZTIcueygYrKRHDtJgk23MliHN
Jccsbsc2j2L0oLrbmSnRLlFEdNSz4TYcKqMJG/sM6nwKsLx08IB4sFRpcwUEYzBv
zt3siAeQwkDb3euE5oTMkvLA9kwKi1aQS9DYbtgGMwIpIxODOwkt1NFakAl6EESR
BTyraGU9Y00fQD9ZI8n+/YeC+1Y8XdHKkt1jt9DLQmT2NnBaF/mPP3eNbGEnwMB1
u5B7fnOssuG/FUXKLPw202IeLEPVXxFYm8VBHz06b2Uzil3oOYhhMJhx2eJCTRZf
aElKf1Zm+85EX/OMDY/JO+kFmpWqb2zBTQ7Uf8Y5jMgze/rFe/qXlHXA2aEoXiob
y2ekcFrEBhD7svGRfU+obnlrca4+Fx6DJ3V2MwQAm37mPOFiZWWFK/bYVBd4er03
1r32COLFuzNiEDjpCQfThYRlE9RauGHdTrKt6XF2Ry204dDP8zV9MitDQDpFrke0
YFPtgFGObR5DXG71hqRj
=apJd
-----END PGP SIGNATURE-----
Reply to: