do-release-upgrade allows both -d and -p switches although neither takes effect

[Brian Murray]

13:59:33 - flash:[/tmp] do-release-upgrade -h
Usage: do-release-upgrade [options]

Options:
  -h, --help show this help message and exit
  -V, --version Show version and exit
  -d, --devel-release Check if upgrading to the latest devel release is
                        possible
  --data-dir=DATA_DIR Directory that contains the data files
  -p, --proposed Try upgrading to the latest release using the upgrader
                        from $distro-proposed

There is no documentation nor an error message if you use both the -d and -p switches. However, if you look at MetaRelease.py you will see the following:

        # devel and proposed "just" change the postfix
        if useDevelopmentRelease:
            self.METARELEASE_URI += self.METARELEASE_URI_UNSTABLE_POSTFIX
        elif useProposed:
            self.METARELEASE_URI += self.METARELEASE_URI_PROPOSED_POSTFIX

by using both -d and -p you get neither. As there is no meta-release file for meta-release-development-proposed there should be an error message if you use both arguments at the same time.

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-release-upgrader - 1:0.215

---------------
ubuntu-release-upgrader (1:0.215) trusty; urgency=medium

  * do-release-upgrade: indicate that -p and -d switches are mutually
    exclusive (LP: #1071025)
  * debian/control.py: depend on python-apport since DistUpgradeApport.py
    imports it and the release upgrader does not use python3 (LP: #1289604)
  * debian/source_ubuntu-release-upgrader.py: create a DuplicateSignature by
    stripping out the tmpdir from the Traceback (LP: #1289850)
 -- Brian Murray <email address hidden> Fri, 07 Mar 2014 14:29:14 -0800