do-release-upgrade crashed with AttributeError in run(): 'apt_pkg.PackageManager' object has no attribute 'ResultFailed'

[zakaria daaif]

packag fail

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.4
ProcVersionSignature: Ubuntu 4.4.0-3.17-generic 4.4.1
Uname: Linux 4.4.0-3-generic i686
ApportVersion: 2.19.4-0ubuntu2
Architecture: i386
CrashDB: ubuntu
Date: Sat Feb 6 12:33:10 2016
ExecutablePath: /usr/bin/do-release-upgrade
InstallationDate: Installed on 2016-02-04 (1 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha i386 (20160127)
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/lib/ubuntu-release-upgrader/do-partial-upgrade --frontend=DistUpgradeViewGtk3
PythonArgs: ['/usr/bin/do-release-upgrade', '--frontend=DistUpgradeViewGtk3']
SourcePackage: ubuntu-release-upgrader
Title: do-release-upgrade crashed with AttributeError in run(): 'apt_pkg.PackageManager' object has no attribute 'ResultFailed'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

VarLogDistupgradeAptHistorylog:
 Start-Date: 2016-02-06 12:32:31
 Upgrade: icedtea-netx:i386 (1.6.1-4ubuntu1, 1.6.2-1ubuntu1), libgcc1:i386 (5.3.1-7ubuntu1, 5.3.1-8ubuntu2), libstdc++6:i386 (5.3.1-7ubuntu1, 5.3.1-8ubuntu2), cpp-5:i386 (5.3.1-7ubuntu1, 5.3.1-8ubuntu2), libquadmath0:i386 (5.3.1-7ubuntu1, 5.3.1-8ubuntu2), gcc-5-base:i386 (5.3.1-7ubuntu1, 5.3.1-8ubuntu2), libgomp1:i386 (5.3.1-7ubuntu1, 5.3.1-8ubuntu2), icedtea-netx-common:i386 (1.6.1-4ubuntu1, 1.6.2-1ubuntu1)
 Remove: icedtea-7-plugin:i386 (1.6.1-4ubuntu1)
 Error: Sub-process /usr/bin/dpkg returned an error code (1)
 End-Date: 2016-02-06 12:33:02
VarLogDistupgradeTermlog:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1540017, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.