Hi Christian, On Wed, 2006-07-26 at 23:08 +0200, Christian Perrier wrote: > Quoting Andree Leidenfrost ([EMAIL PROTECTED]): > > Package: libnewt0.52 > > Version: 0.52.2-5.1 > > Severity: important > > > > Dear Alistair, > > > > In version 0.52.2-5.1, the crashes in case libfribidi0 is not installed > > have returned. I am attaching a full backtrace of a non-stripped program > > (mondoarchive) using a non-stripped libnewt0.52 (0.52.2-5.1). > > > > I believe this is really the same as #351367 and #290722. > > > > 0.52.2-5 is fine, the problem only starts with 0.52.2-5.1. Also as > > before, if libfribidi0 is installed, the problem goes away. > > > > I presume the underlying reason is (from the changelog): > > > > [...] > > * Apply patch from Eugeniy Meshcheryako to regenerate configure during build > > so that bidi support is enabled again. Closes: #379566 > > [...] > > > > Please let me know if you need any other information. > > > Please note that this latter change was needed by D-I, so any solution > reverting that change is not acceptable.
Fair enough. > I guess that a short-term solution would be making libnewt0.52 depend > on libfribidi0....but that'd virtually make the latter part of the > base system. I presume there is a reason why libnewt0.52 is linked opportunistically against libfribidi0. I would have thought that it was to save space space. However, I take it that D-I not only needs the change in libnewt0.52 but also makes use of libfribidi0 itself (at least there is a udeb)? If this is the case, we wouldn't really be saving any space, so maybe the easiest would indeed be to make libnewt0.52 depend on libfribidi0 for the time being, especially since libfribidi0 does not have any other dependencies, so the impact would be limited to having libfribidi0 in base but nothing on top of that. Cheers, Andree -- Andree Leidenfrost @ Debian Developer Sydney - Australia
signature.asc
Description: This is a digitally signed message part
