[Bug 1187507] Re: (open)motif should properly transition from libmotif3

[Dave Gilbert]

I'd add to a testcase install an app dependent on the *3 version, and
then perform the upgrade

** Changed in: openmotif (Ubuntu)
   Importance: Undecided => Low

** Changed in: openmotif (Ubuntu)
       Status: New => Triaged

** Changed in: motif (Ubuntu)
   Importance: Undecided => Low

** Changed in: motif (Ubuntu)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1187507

Title:
  (open)motif should properly transition from libmotif3

Status in “motif” package in Ubuntu:
  Triaged
Status in “openmotif” package in Ubuntu:
  Triaged
Status in “motif” package in Debian:
  Fix Committed

Bug description:
  [SRU] The debdiffs attached to this bug provide a libmotif3 virtual
  package to properly transition from the libmotif3 package still
  present in Lucid to the new libmotif4 packages in Precise, Quantal and
  Raring.  For Precise and Quantal, LP: #1187534 is fixed as well.

  [IMPACT] According to the whole archive statistics in Ubuntu's PopCon
  [1], it appears there are still a significant number of libmotif3
  installations.

  #rank name                            inst  vote   old recent no-files (maintainer)
  8636  libmotif3                      25238    45 18260     4  6929 (Debian Qa Group)
  18967 libmotif4                       3683   115  3264    75   229 (Unknown)

  I believe this may be due to the number of proprietary packages that need libXm.so.3.
  Searching for 'install libmotif3' returns a number of guides on installing some of these packages on Debian and Ubuntu, as well as guides on how to install libmotif3 from previous releases.
  Since openmotif 2.3.3-5ubuntu2 in Quantal and 2.3.3-5ubuntu1.12.04.1 in Precise (LP: #818220), libmotif4 has provided symlinks for libXm.so.3 and the other libmotif3 libraries, but did not provide a libmotif3 transitional package and thus libmotif3 was never properly transitioned to libmotif4.

  [Test Case]
  Install libmotif3 from Lucid then verify that libmotif3 is upgraded and libmotif4 is installed:
  $ wget http://archive.ubuntu.com/ubuntu/pool/multiverse/o/openmotif/libmotif3_2.2.3-4_amd64.deb
  $ sudo dpkg -i libmotif3_2.2.3-4_amd64.deb
  $ sudo apt-get update
  $ sudo apt-get dist-upgrade
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
    libmotif4
  The following packages will be upgraded:
    libmotif3
  1 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.

  As libmotif4 is multi-arch, the test should be repeated for i386, i.e.
  $ wget http://archive.ubuntu.com/ubuntu/pool/multiverse/o/openmotif/libmotif3_2.2.3-4_i386.deb
  $ sudo dpkg -i libmotif3_2.2.3-4_i386.deb
  And so on, as above.

  [Regression Potential]
  Minimal: the fix only affects packaging, however the large number of users with libmotif3 installed are going to be offered an unexpected upgrade.
  New bugs may have been introduced in openmotif 2.3.3, but libmotif3 compatibility has been in Ubuntu for some months now and there have been no bugs reported.
  Should libmotid3 users be affected, they can revert to libmotif3 from Lucid until such time as a fix is released, or until they are upgraded to motif 2.3.4 available in Saucy.

  [1] http://popcon.ubuntu.com/

  ---------------------------------------------------------------------------------------

  The fix has released in motif 2.3.4-4 in Debian and is currently in
  the Binary NEW queue due to the new libmotif3 transitional package.
  It is expected to land in Saucy within a week or so.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/motif/+bug/1187507/+subscriptions