-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 8/4/06, Josselin Mouette <[EMAIL PROTECTED]> wrote:
Le vendredi 04 août 2006 à 15:03 +0700, Theppitak Karoonboonyanan a
écrit :
> > However, I don't quite understand about the circular
> > dependency problem. Could you give more info?
Currently, there is a circular dependency between libpango1.0-0 and
libpango1.0-common. This is why by chance your package works while not
depending on libpango1.0-common. However this circular dependency will -
hopefully soon - be fixed in pango and your package will stop working.
I see. Thanks for clarifying.
> Umm.. I have also replaced the hard-coded dependencies
> with ${shlibs:Depends}, ${misc:Depends} and , as a result,
> dependency on libpango1.0-0 is now gone. Is this related
> to the problem you mentioned?
No, this is probably because the module doesn't link directly to one of
the libpango*-1.0.so.0 libraries. You can check the output of 'ldd -r
yourmodule.so' for unresolved symbols.
If there are no missing symbols, this is harmless, because
libpango1.0-common will still depend on libpango1.0-0.
It's actually caused by a bug in upstream configure script
(which is also maintained by me).
As upstream maintainer, I would like to fix this by releasing
a new upstream version, which has also gathered some
other fixes to time. And as debian package maintainer, I
would like to wait for that, rather than patching the package
and getting overridden very soon.
That means it may take a couple of days before this bug
is fixed.
- --
Theppitak Karoonboonyanan
http://linux.thai.net/~thep/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFE0zGvqgzR7tCLR/4RAqCDAJ4shzTWbO0Gesaa1P1HrGANhT5xAACfaYM5
gA25yxrGtEskwCmqQcgpw88=
=APEG
-----END PGP SIGNATURE-----
