> David Paleino <da...@debian.org> (27/04/2012):
>> what's the status of the exiv2 transition? It would really be nice
>> to have exiv2 0.22 in wheezy.
>
We don't know yet (tbh). The transition page indicates that this
transition has packages involved in other ongoing transitions (namely
boost1.49 and tiff4-symbols). The former should be okay, but the latter
needs a few days until tiff{,3} packages migrate (just to be sure that
exiv2 r-deps don't stay stuck behind tiff in sid). Until then, digikam
appears to FTBFS on mips ans has 3 new RC bugs (wrt. testing). It would
be nice to fix it before starting the transition. We can of course get
it out of testing if necessary (it doesn't appear to have any reverse
dependencies in testing, afaics), but let's keep this possibiliy as a last
resort for now.
Besides, Mark mentioned that strigi needed fixing (although the failure
seems not related to exiv2). Do you have news on that?
HTH,
On 04/27/2012 09:25 PM, Cyril Brulebois wrote:
> http://release.debian.org/transitions/html/exiv2.html says not
> started.
>
- or no binNMUs were scheduled
- or everything is broken and still using the old library
- or … :)
… so it doesn't say much.
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f9b0bb1.5000...@debian.org
