Bug#656435: pango modules not regenerated after multiarch migration

[Andrew Shadura]

Hello,

On Thu, 19 Jan 2012 12:47:27 +0100
Michael Biebl <biebl at debian.org> wrote:

> 1.14.5-1 was the last version shipping this file, so this is before
> lenny even. We did keep the cleanup code until post-squeeze, i.e. two
> release cycles.

This system was originally lenny, upgraded to unstable then, and I
upgrade it quite regularly.

> Your pango.modules file was most likely created after 1.14.5-1 and I
> can only assume it was created by either another package (which would
> be strange) or manually.

I did not create it manually. However, anything could create it by
calling pango-querymodules, and while that file is supported at all by
pango, pango's scripts should update it or delete it when changing
modules paths, even if I created that file myself, shouldn't it?

One of the releases brought multiarch support which led to breakage
because this particular file is read by pango, and no modules were
found there. It's obvious that if path to modules changes,
pango.modules file can't point to any of them anymore, so it has to be
updated somehow. The exact way of doing this is up to maintainer, but
it must be done.

-- 
WBR, Andrew
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20120119/19e222a3/attachment.pgp>