Re: [arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread bardo
2009/7/15 Thomas Bächler : > What readelf said is what is written in the binary. If the binary says > libjpeg.so.62, then it's an old binary! You're right. I reverted back to the puzzle.ch mirror and I saw it didn't sync properly, it still has the old mldonkey. Thanks for clarifications =) Corrad

Re: [arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread Thomas Bächler
bardo schrieb: 2009/7/15 bardo : Yes, i686, but just to be sure I checked on both arches, and I get the new version. The problem has been solved by switching repos. Could it be that mldonkey just linked to libjpeg.so, and readelf recurred to libjpeg.so.62, while the program said it didn't find

Re: [arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread bardo
2009/7/15 bardo : > Yes, i686, but just to be sure I checked on both arches, and I get the > new version. The problem has been solved by switching repos. Could it be that mldonkey just linked to libjpeg.so, and readelf recurred to libjpeg.so.62, while the program said it didn't find the library be

Re: [arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread bardo
2009/7/15 Allan McRae : > Strange - both using the same architecture? Yes, i686, but just to be sure I checked on both arches, and I get the new version.

Re: [arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread Allan McRae
bardo wrote: 2009/7/15 bardo : It worked for me, but it seems it did not for the user, so I'm waiting to know which mirror he uses and readelf's output. He uses archlinux.puzzle.ch... I had problems in the last few days with it too, so I switched to another one, maybe this caused the i

Re: [arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread bardo
2009/7/15 bardo : > It worked for me, but it seems it did not for the user, so I'm waiting > to know which mirror he uses and readelf's output. He uses archlinux.puzzle.ch... I had problems in the last few days with it too, so I switched to another one, maybe this caused the issue. Anyway, here's

Re: [arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread bardo
2009/7/15 Allan McRae : > If a full update does not help, you might want to try lddd from devtools to > try and find what is still using libjpeg6. It worked for me, but it seems it did not for the user, so I'm waiting to know which mirror he uses and readelf's output. Corrado

Re: [arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread Allan McRae
Thomas Bächler wrote: bardo schrieb: Hi guys. Yesterday I rebuild mldonkey since it depended on libjpeg. On x86_64 there are no problems, and everything works as expected; this is not the case for i686, where there's a strange problem: [r...@plafone ~]# ldd /usr/bin/mldonkey | grep libjpeg

Re: [arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread Thomas Bächler
bardo schrieb: Hi guys. Yesterday I rebuild mldonkey since it depended on libjpeg. On x86_64 there are no problems, and everything works as expected; this is not the case for i686, where there's a strange problem: [r...@plafone ~]# ldd /usr/bin/mldonkey | grep libjpeg libjpeg.so.7 => /us

Re: [arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread bardo
2009/7/15 bardo : > The package was created with makechrootpkg in a clean chroot. How is > it even possible to link with two different versions of the same > library? And where did it get the old version, since it didn't exist > in the chroot? I may start to understand... The command I posted was

[arch-general] Perplexing libjpeg-related packaging issue

2009-07-15 Thread bardo
Hi guys. Yesterday I rebuild mldonkey since it depended on libjpeg. On x86_64 there are no problems, and everything works as expected; this is not the case for i686, where there's a strange problem: [r...@plafone ~]# ldd /usr/bin/mldonkey | grep libjpeg libjpeg.so.7 => /usr/lib/libjpeg.so.