[Bug 863741] Re: apt doesn't want to replace portmap with rpcbind on upgrade

[Steve Langasek]

Ugh, that's quite bad.  apparently the archive priority was set
correctly in oneiric, but somehow came undone again in precise...
probably because there were no packages depending on rpcbind at
priority: standard so this showed up as an archive inconsistency.

I'm not sure what the right way is to fix this for precise.  We could do
a no-change SRU or pocket-copy to precise-updates, and change the
priority there.  That might be sufficient.

** Also affects: nfs-utils (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Changed in: nfs-utils (Ubuntu Precise)
       Status: New => Triaged

** Changed in: nfs-utils (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: nfs-utils (Ubuntu Precise)
     Assignee: (unassigned) => Steve Langasek (vorlon)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nfs-utils in Ubuntu.
https://bugs.launchpad.net/bugs/863741

Title:
  apt doesn't want to replace portmap with rpcbind on upgrade

Status in “nfs-utils” package in Ubuntu:
  Fix Released
Status in “nfs-utils” source package in Oneiric:
  Fix Released
Status in “nfs-utils” source package in Precise:
  Triaged

Bug description:
  On upgrade from natty to oneiric, the old nfs-common got left behind
  because apt didn't want to replace portmap with rpcbind.

  $ sudo apt-get -oDebug::PkgProblemResolver=1 dist-upgrade
  Reading package lists... Done
  Building dependency tree       
  Reading state information... Done
  Calculating upgrade... Starting
  Starting 2
  Investigating (0) rpcbind [ amd64 ] < none -> 0.2.0-6ubuntu3 > ( net )
  Broken rpcbind:amd64 Conflicts on portmap [ amd64 ] < 6.0.0-2ubuntu5 > ( net )
    Considering portmap:amd64 1 as a solution to rpcbind:amd64 0
    Holding Back rpcbind:amd64 rather than change portmap:amd64
  Investigating (0) nfs-common [ amd64 ] < 1:1.2.2-4ubuntu5 -> 1:1.2.4-1ubuntu2 > ( net )
  Broken nfs-common:amd64 Depends on rpcbind [ amd64 ] < none -> 0.2.0-6ubuntu3 > ( net ) (>= 0.2.0-6ubuntu1)
    Considering rpcbind:amd64 0 as a solution to nfs-common:amd64 0
    Holding Back nfs-common:amd64 rather than change rpcbind:amd64
   Try to Re-Instate (1) nfs-common:amd64
  Done
  Done
  The following packages have been kept back:
    nfs-common
  0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
  $

  I don't know why this is.  Maybe it has to do with the old portmap
  being Priority: standard, and rpcbind being Priority: optional?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/863741/+subscriptions