On Thu, Sep 24, 2015 at 6:40 PM, Richard Purdie
wrote:
> On Thu, 2015-09-24 at 08:27 -0300, Otavio Salvador wrote:
>> Thanks for hunting this bug, this was very annoying and hard to
>> figure. It does seem to address the issue in our builder.
>
> Sadly, whilst I merged it and it does fix that prob
On Thu, 2015-09-24 at 08:27 -0300, Otavio Salvador wrote:
> Hello Richard,
>
> Thanks for hunting this bug, this was very annoying and hard to
> figure. It does seem to address the issue in our builder.
Sadly, whilst I merged it and it does fix that problem, I suspect this
causes:
https://autobu
Hello Richard,
Thanks for hunting this bug, this was very annoying and hard to
figure. It does seem to address the issue in our builder.
On Wed, Sep 23, 2015 at 7:32 PM, Richard Purdie
wrote:
> If gdkpixbuf-native rebuilds and there are stale (broken) modules lying
> around,
> it can fail to ru
On Wed, 2015-09-23 at 16:54 -0600, Gary Thomas wrote:
> On 2015-09-23 16:32, Richard Purdie wrote:
> > If gdkpixbuf-native rebuilds and there are stale (broken) modules lying
> > around,
> > it can fail to run the postinst. E.g. svg links to harfbuzz and if harfbuzz
> > is
> > removed from the sy
On 2015-09-23 16:32, Richard Purdie wrote:
If gdkpixbuf-native rebuilds and there are stale (broken) modules lying around,
it can fail to run the postinst. E.g. svg links to harfbuzz and if harfbuzz is
removed from the sysroot but the svg loader isn't, we get a symbol linking
issue.
The reprodu
If gdkpixbuf-native rebuilds and there are stale (broken) modules lying around,
it can fail to run the postinst. E.g. svg links to harfbuzz and if harfbuzz is
removed from the sysroot but the svg loader isn't, we get a symbol linking
issue.
The reproducer is along the lines of build gdk-pixbuf-na
