On Mon, May 27, 2013 at 02:00:12PM +0100, Adam D. Barratt wrote:
> However, in this case, that's somewhat complicated by the fact that
> libunwind in unstable doesn't actually build libunwind7 any more, which
> makes updating it somewhat tricky. If the maintainers do agree that
> Peter's solution is feasible then reports of testing on stable systems
> using the p-u package would be appreciated _before_ the point release.
Is someone working on determinging whether we can move libunwind7 in
wheezy? If so, should we move this bug to some other package other
than e2fsprogs? I'm currently not working this bug on the assumption
that someone is looking into the possibility of fixing this outside of
e2fsprogs.
If it turns out that ia64's libc is just busted, worst case I can
disable the use of backtrace just on ia64 on debian, as a special-case
workaround/hack.
Let me know what the Debian Release team would prefer.
- Ted
--
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/20130615235047.gc32...@thunk.org
