touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

Public bug reported:

/sbin/ldconfig.real: /usr/lib/arm-linux-gnueabihf/libmirserver.so.33 is
not a symbolic link

Every time I install new packages on a phone I get the above warning.
Seems reasonable that we can and should avoid it. Just use the
convention that the real binary is named according to the full product
version. For example:

   libmirserver.so.33v0.16.0
   libmirserver.so.33 -> libmirserver.so.33v0.16.0
   libmirserver.so -> libmirserver.so.33

** Affects: mir
     Importance: Undecided
         Status: New

** Affects: mir (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: mir (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1490428

Title:
  /sbin/ldconfig.real: /usr/lib/arm-linux-gnueabihf/libmirserver.so.33
  is not a symbolic link

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  /sbin/ldconfig.real: /usr/lib/arm-linux-gnueabihf/libmirserver.so.33
  is not a symbolic link

  Every time I install new packages on a phone I get the above warning.
  Seems reasonable that we can and should avoid it. Just use the
  convention that the real binary is named according to the full product
  version. For example:

     libmirserver.so.33v0.16.0
     libmirserver.so.33 -> libmirserver.so.33v0.16.0
     libmirserver.so -> libmirserver.so.33

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1490428/+subscriptions