On 29 April 2012 03:51, Wolodja Wentland <deb...@babilen5.org> wrote:
> Hello,
>
> thank you Daniel for looking into this. I'd like to start by providing a few
> more details as this might help to triage this bug. The bug is related to
> parsing/handling of aptitude-defaults and manifests itself when
> aptitude-defaults.{zh*,..} are used.
>
> I verified this by replacing /usr/local/share/aptitude/aptitude-defaults.zh_TW
> with /usr/local/share/aptitude/aptitude-defaults which fixed the error.
>> I can still reproduce it even with the newest version in git and using "-O0 > -g" > and I am not sure why you don't see the error. Are you running aptitude > directly from the repository with something like ./src/aptitude? I ask because > that doesn't result in the error because aptitude-defaults.zh_TW is not > loaded. > That was why I could not reproduce it. :-) >> Otherwise I will try to reproduce it again on a fresh system, and see >> if my changes fix it. > > I tried to bisect the issue and initially thought that it might have been > de95eb2 or bd3f0ed, but I could reproduce it with e93a341 (i.e. 0.6.5) as > well. I had to cherry-pick 9803921 and fd0f5f3 to get e93a341 to compile > though, but don't expect them to have an effect. Unfortunately I failed to > compile even older versions. > Ubuntu saw this bug when changing to updated apt (>= 0.8.16~exp5) and it appeared here when compiled with 0.9.0 so I believe this is caused by a change in apt -- possibly to do with passing the multibyte characters from aptitude-defaults.?? to the acquire methods (libapt passes all configuration data to each method I believe). Thanks to both of you for narrowing this down, that certainly helps to get this rather serious issue resolved. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
