Bug#755404: libept1.4.12: /usr/lib/libept.so.1.0.5.4.12 is a dangling symlink

[Ansgar Burchardt]

Control: reassign -1 libept1.4.12 1.0.10

On 07/28/2014 12:05, Russell Coker wrote:
>> Also, goplay depends on libept1.4.12 which ships
> 
>> /usr/lib/libept.so.1.0.5.4.12. So how can the linker fail to find

Because that is a dangling symlink since libept installs the actual
shared library into the multi-arch location:

  ./usr/lib/x86_64-linux-gnu/libept.so.1.aptpkg4.12
  ./usr/lib/libept.so.1.0.5.4.12 -> libept.so.1.aptpkg4.12

>> libept.so.1.0.5.4.12 and how does a rebuild help?

Rebuilding results in using a different soname which refers to an
existing file.

> # dpkg -L libept1.4.12 |grep libept.so.1.0.5
> 
> /usr/lib/libept.so.1.0.5.4.12
> 
> # ls -l /usr/lib/libept.so.1.0.5.4.12
> 
> ls: cannot access /usr/lib/libept.so.1.0.5.4.12: No such file or directory
> 
> The above happens on 2 systems that are tracking Unstable, and
> presumably it happens the same way for the person who reported the bug.
> Looks like it might be a libept bug.
> 
> But in any case it doesn't seem to be a problem to rebuild goplay. Maybe
> it would be best to cancel my upload and do a binNMU. What do you think?

I think the upload should be canceled and libept fixed instead.

Ansgar