do-release-upgrade crashes in a freshly installed system

[Fernando Naranjo]

do-release-upgrade command crashes in a fresh install of elementary os freya test 1. This command was auto executed by the system, not by user.

ProblemType: Bug
DistroRelease: elementary OS 0.3
Package: elementary-desktop 1.348+392~ubuntu0.3.1 [origin: unknown]
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CrashDB: elementary_meta
CurrentDesktop: Pantheon
Date: Sat Aug 16 10:06:17 2014
InstallationDate: Installed on 2014-08-16 (0 days ago)
InstallationMedia: elementary OS 0.3 "Freya" - Daily amd64 (20140810)
ProcEnviron:
 LANGUAGE=es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: elementary-meta
SuspiciousXErrors:

ThirdParty: True
UpgradeStatus: No upgrade log present (probably fresh install)

[Derek Pockrandt (derekpock)]

Update your system. I cannot replicate this bug.

[Cody Garver (codygarver)]

This happens, I don't know if it's bad or not. But we do modify this package so it could be my fault somehow.

[Marvin Beckers (embik)]

Maybe we should remove the command do-release-upgrade (which is a Python script)? It's very unlikely an upgrade from Luna 0.2 to Freya 0.3 works anyway. It does not work smooth on Ubuntu as well, so maybe we should simply remove it and advise our users to reinstall for a new release. Better than breaking their system with such an upgrade.

[Cody Garver (codygarver)]

I might have fixed this. We'll have to see if it happens on fully updated system after 25 Feb.

[Cody Garver (codygarver)]

Happen again with a freshly generated iso

Something to do with `/usr/lib/ubuntu-release-upgrade/check-new-release -q`

[Cody Garver (codygarver)]

AFAICT this is harmless, it's just complaining that a file that actually exists does not exist. A file not affected by any of our modifications.