The version of exiv2 not keyworded ~amd64 in portage is 3 years old, please unkeyword 0.25. Reproducible: Always
Request to remove "introspection" flag? Is it necessary?
(In reply to Jeff from comment #1) > Request to remove "introspection" flag? Is it necessary? Is it causing problems?
It just keeps getting older.
-r2 was just added with some backported fixes, let's target that instead.
Another reason for stabalisation, I found that exiv2-0.24-r1 kept failing with the same message: iptceasy.cpp:5:27: fatal error: exiv2/exiv2.hpp: No such file or directory whilst building the samples (even though USE had -examples). I don't have the full log handy, but could unmerge exiv2 and try again if that was wanted. Adding an entry to accept the ~amd64 keyword for media-gfx/exiv2-0.25-r2 worked however, that I could build (and without the parallel build issue that Hanno experienced in bug #572394). So rather than filing a bug for the earlier version, I just vote that this package get stabalised.
What can I do to speed this up?
Stable on alpha.
amd64 stable
x86 stable
arm stable
The stabilization of exiv2-25-r2 has caused some dependency issues, seemingly because not all packages that depend on it were properly adapted first (to the new subslot?). See forum post https://forums.gentoo.org/viewtopic.php?p=7881406 and bug #574904 for example. I guess the stabilization cannot be reversed now, even if it feels premature from the perspective of users having to deal with the breakage it causes. I suppose that checking all packages that depend on exiv2 should have been done before stabilization, so that activity's coordination (adding blockers here) is still within the purview of this bug.
(In reply to Erik Quaeghebeur from comment #11) > The stabilization of exiv2-25-r2 has caused some dependency issues, > seemingly because not all packages that depend on it were properly adapted > first (to the new subslot?). > > See forum post https://forums.gentoo.org/viewtopic.php?p=7881406 and bug > #574904 for example. > > I guess the stabilization cannot be reversed now, even if it feels premature > from the perspective of users having to deal with the breakage it causes. I > suppose that checking all packages that depend on exiv2 should have been > done before stabilization, so that activity's coordination (adding blockers > here) is still within the purview of this bug. The subslot conflicts in that forum post appear to be some issue with portage and not specific to exiv2.
ppc stable
ppc64 stable
sparc stable
ia64 stable
@hppa, it looks like the only stable revdep is media-gfx/ufraw so I wonder if there's still interest in having this package stable on your arch?
Stable for HPPA. Closing.