Failed to upgrade from Oneiric to Precise: E:Could not perform immediate configuration on 'openoffice.org-writer'

[Jean-Baptiste Lallement]

Automated Upgrade Testing: main-all i386

Upgrade from Oneiric to Precise aborts with the following error in main.log

SystemError: E:Could not perform immediate configuration on 'openoffice.org-writer'. Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: openoffice.org (not installed)
ProcVersionSignature: Ubuntu 3.2.0-4.10-generic 3.2.0-rc5
Uname: Linux 3.2.0-4-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
Date: Tue Dec 13 00:24:48 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: openoffice.org
UpgradeStatus: No upgrade log present (probably fresh install)

[Martin Pitt (pitti)]

Some note keeping:

- installed openoffice.org and openoffice.org-writer in a clean and up to date oneiric VM
- apt-get dist-upgrade --simulate works fine (which should pick up pre-dependency loops, a common cause for this error message)
- I tried to inject apt::get::simulate into do-release-upgrade (both in apt.conf.d and inserting it into the code), but that gets ignored
- sudo apt-get dist-upgrade works all the way through (reboot OK)
- do-release-upgrade -d works all the way through

So it seems I don't have enough packages installed yet to reproduce this.

[Martin Pitt (pitti)]

So those are the "interesting" parts of what happens package-wise:

remove/obsolete: openoffice.org (it was demoted from main to universe)
keep: openoffice.org-hyphenation openoffice.org-hyphenation-hr
add: openoffice.org-writer
upgrade: openoffice.org-{base,common}

I recreated that reduced scenario by

  sudo apt-get install openoffice.org-{base,common,hyphenation,hyphenation-hr} hyphen-hr openoffice.org
  sudo dpkg -P openoffice.org-writer

in my oneiric VM, and then switching apt to precise and

  sudo apt-get install openoffice.org-{base,common,writer} openoffice.org-

That removed openoffice.org and added -writer, no problems.

So what happens in above full logs is that it removes openoffice.org because it went to universe. That's really an error, the transitional package should be in main for precise, and in 12.10 we remove the whole openoffice.org transitional source. I re-promoted it to main and seeded it. Due to removing openoffice.org, apt now needs to satisfy

  Package: hyphen-hr
  Depends: openoffice.org (>= 1.0.3-3) | openoffice.org-writer | openoffice.org-impress, dictionaries-common (>= 0.10)

so it installs -writer as the second-best alternative. This really should be updated to depend on libreoffice, too, so I'll add a task.

I'll run a full do-release-upgrade wit the updated start scenario now and see whether I can reproduce now. But perhaps with the above two fixes this bug will already be fixed.

[Martin Pitt (pitti)]

I'm through another do-release-upgrade run, and it succeeded. I noticed that it didn't actually remove openoffice.org and install oo-writer. This is bad because I'm still unable to reproduce, but good because it shows that merely having openoffice.org in main again should already fix this :)

[Launchpad Janitor (janitor)]

This bug was fixed in the package myspell-hr - 20060617-2.3ubuntu1

---------------
myspell-hr (20060617-2.3ubuntu1) precise; urgency=low

  * debian/control: Drop obsolete openoffice.org dependencies and replace with
    a Recommends: libreoffice-writer. (LP: #903475)
 -- Martin Pitt <email address hidden> Wed, 14 Dec 2011 10:53:05 +0100

[Launchpad Janitor (janitor)]

This bug was fixed in the package openoffice.org-en-au - 2.1-5.3ubuntu1

---------------
openoffice.org-en-au (2.1-5.3ubuntu1) precise; urgency=low

  * debian/control: Drop obsolete openoffice.org dependencies, replace with
    Recommends: libreoffice-writer. (LP: #903475)
 -- Martin Pitt <email address hidden> Wed, 14 Dec 2011 11:15:30 +0100

[Martin Pitt (pitti)]

I asked jibel to re-run the upgrade test now, I'm pretty hopeful that it will succeed now (or at least not fail with _this_ bug :) ). If it still fails, can I please have the current logs? I'm still unable to reproduce.

[Martin Pitt (pitti)]

Still waiting on auto dist-upgrade tester to confirm.

[Jean-Baptiste Lallement (jibel)]

I confirm that it is fixed.