package flightgear-data-base 2.10.0-2 failed to install/upgrade: trying to overwrite '/usr/share/games/flightgear/Scenery/Terrain/w130n30/w123n37/59CA.btg.gz', which is also in package fgfs-scenery-base 2.6.0-1.1

[geonel]

[Impact]

 * Users who have the flightgear/simgear/fgfs-base packages installed on Raring and
   earlier will be unable to successfully update flightgear (et al.) to the version in
   Saucy.

 * This is partially because due to the renaming of the fgfs-base package to
   flightgear-data, Breaks and Replaces had to be added to allow the transition. However,
   the Breaks in the flightgear-data-base package didn't include all packages.

 * This bug was fixed in 2.10.0-3, which is currently in Trusty. This fix needs to be
   applied to Saucy.

[Test Case]

 * On Raring, install flightgear. This will automatically install simgear and fgfs-base.

 * Upgrade to Saucy.

 * An error message will come up saying that flightgear couldn't be upgraded because
   the new flightgear-data-base package couldn't be cleanly installed.

[Regression Potential]

 * None; the worst case scenario is that users will still be unable to upgrade.

[Original Description]

Happened when upgrading from 13.04 to 13.10(final beta)

ProblemType: Package
DistroRelease: Ubuntu 13.10
Package: flightgear-data-base 2.10.0-2
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
Date: Sun Oct 13 23:39:48 2013
DuplicateSignature: package:flightgear-data-base:2.10.0-2:trying to overwrite '/usr/share/games/flightgear/Scenery/Terrain/w130n30/w123n37/59CA.btg.gz', which is also in package fgfs-scenery-base 2.6.0-1.1
ErrorMessage: trying to overwrite '/usr/share/games/flightgear/Scenery/Terrain/w130n30/w123n37/59CA.btg.gz', which is also in package fgfs-scenery-base 2.6.0-1.1
InstallationDate: Installed on 2010-12-23 (1027 days ago)
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: flightgear-data
Title: package flightgear-data-base 2.10.0-2 failed to install/upgrade: trying to overwrite '/usr/share/games/flightgear/Scenery/Terrain/w130n30/w123n37/59CA.btg.gz', which is also in package fgfs-scenery-base 2.6.0-1.1
UpgradeStatus: Upgraded to saucy on 2013-10-13 (3 days ago)

[Rebecca Palmer (rebecca-palmer)]

This is Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722513, which is fixed in 2.10.0-3 (in Trusty).

In the meantime, it can be worked around by manually removing fgfs-scenery-base before installing 2.10.

[Saikrishna Arcot (saiarcot895)]

Debdiff attached. The fix is in debian/control, so the patch is a little meta.

[Brian Murray (brian-murray)]

It looks like you missed part of the fix as there is also a breaks on fgfs-scenery-base.

Package: flightgear-data-base
Architecture: all
Depends: tzdata, fonts-liberation, ${misc:Depends}
Replaces: fgfs-base (<< 2.10.0), fgfs-scenery-base (<< 2.10.0)
Breaks: flightgear (<< 2.10.0~),
 fgfs-base (<< 2.10.0~), fgfs-scenery-base (<< 2.10.0~),
 fgfs-aircraft-base (<< 2.10.0~)

[Brian Murray (brian-murray)]

Anyway, I'll sort it out and upload it.

[Saikrishna Arcot (saiarcot895)]

That's...strange.

[Stéphane Graber (stgraber)]

Hello geonel, or anyone else affected,

Accepted flightgear-data into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/flightgear-data/2.10.0-2ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

[Rebecca Palmer (rebecca-palmer)]

This works for an upgrade of flightgear at the command line (log attached), but in the case of a previously failed upgrade the user needs to run sudo apt-get -f install as instructed, and I haven't tested whether the graphical update manager displays this message ("E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution)."); is it possible to test that without triggering an upgrade of everything to -proposed?

I also haven't tested upgrading the entire system.

[Saikrishna Arcot (saiarcot895)]

I can test a full upgrade in a Raring VM later today.

[Saikrishna Arcot (saiarcot895)]

I tested a semi-upgrade, where, on Raring, I change sources.list to use saucy instead of raring, and the upgrade from 2.6 to 2.10 works correctly. Is there a way to have the GUI upgrade to -proposed packages?

[Brian Murray (brian-murray)]

If you enable proposed in raring, but don't install anything from the -proposed should still be enable during the upgrade process from raring to saucy. You can confirm this by viewing /var/log/dist-upgrade/main.log and look for lines regarding -proposed and it being upgraded to the next release. You'll probably also want to call the distribution upgrade via 'update-manager -c --no-update' so that update-manager doesn't force you to upgrade packages first.

[Rebecca Palmer (rebecca-palmer)]

More tests, again within Saucy, but this time with the graphical update-manager:
-Update installs cleanly over 2.6.0 or non-broken 2.10.0 and works.
-Over broken 2.10.0 (i.e. after a failed upgrade), update-manager tells the user to run apt-get install -f; this fixes the problem whether or not -proposed is enabled.
i.e. this update doesn't actually make recovering an already broken upgrade any easier, but (as that message probably appears before any new packages are installed) it is likely that no update could, and as it doesn't do any harm it should still go ahead for the benefit of those who haven't yet tried to upgrade.

I haven't tested a full system upgrade.

[Saikrishna Arcot (saiarcot895)]

A full system upgrade works. This is with enabling the -proposed repository and running "update-manager -c --no-update". Obsolete packages were removed, including simgear2.6.0, fgfs-base, fgfs-aircraft-base, fgfs-models-base, and fgfs-scenery-base (the older package names).

[Saikrishna Arcot (saiarcot895)]

I think verification-done can be declared?

[Launchpad Janitor (janitor)]

This bug was fixed in the package flightgear-data - 2.10.0-2ubuntu1

---------------
flightgear-data (2.10.0-2ubuntu1) saucy; urgency=low

  * Fix the breaks on fgfs-scenery-base and fgfs-aircraft-base, thanks to
    Saikrishna Arcot for the initial patch. (LP: #1240600)
 -- Brian Murray <email address hidden> Fri, 15 Nov 2013 16:21:53 -0800

[Brian Murray (brian-murray)]

The verification of the Stable Release Update for flightgear-data has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.