Processed: Re: Bug#1068219: chatty, dependencies unsatisfiable on 32-bit non-i386 architectures.

2024-04-07 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 patch
Bug #1068219 [chatty] chatty, dependencies unsatisfiable on 32-bit non-i386 
architectures.
Added tag(s) patch.

-- 
1068219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1068219: chatty, dependencies unsatisfiable on 32-bit non-i386 architectures.

2024-04-07 Thread Andreas Metzler
Control: tags -1 patch

On 2024-04-02 Peter Michael Green  wrote:
> Package: chatty
> Version: 0.8.2-1
> Severity: serious
> User: debian-...@lists.debian.org
> Usertag: time-t

> After being rebuilt for the time64 transition, chatty depends
> on both libpurple0 and libpurple0t64. As a
> result it is uninstallable on architectures that are undergoing
> the time64 transition (armel, armhf and some debian-ports
> archictures).

Hello,

This is caused by
(sid_armhf-dchroot)ametzler@abel:~/TRDY$ head debian/shlibs.local
libjabber 0 libpurple0
and 
(sid_armhf-dchroot)ametzler@abel:~/TRDY$ objdump -p 
chatty-0.8.2/debian/chatty/usr/bin/chatty  | grep NEEDE | grep jab
  NEEDED   libjabber.so.0
(sid_armhf-dchroot)ametzler@abel:~/TRDY$ ldd -r 
chatty-0.8.2/debian/chatty/usr/bin/chatty | grep jabb
libjabber.so.0 => /usr/lib/arm-linux-gnueabihf/purple-2/libjabber.so.0 
(0xb69b6000)
(It uses an rpath to find it.)

So afaiui this could be fixed by pointing to libpurple0t64 in
debian/shlibs.local.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#1068219: chatty, dependencies unsatisfiable on 32-bit non-i386 architectures.

2024-04-01 Thread Peter Michael Green

Package: chatty
Version: 0.8.2-1
Severity: serious
User: debian-...@lists.debian.org
Usertag: time-t

After being rebuilt for the time64 transition, chatty depends
on both libpurple0 and libpurple0t64. As a
result it is uninstallable on architectures that are undergoing
the time64 transition (armel, armhf and some debian-ports
archictures).