[Bug 777524] Re: “Repair broken packages” option breaks with Python ≥ 2.6
Jean-Baptiste Lallement
jean-baptiste at ubuntu.com
Wed May 25 21:08:47 UTC 2011
Thanks for your report. Confirmed in Oneiric. Setting to triaged/medium
because even if friendly-recovery is a core component it will still work
relying on apt rather than update-manager to recover from a dpkg
failure.
** Changed in: friendly-recovery (Ubuntu)
Importance: Undecided => Medium
** Changed in: friendly-recovery (Ubuntu)
Status: New => Triaged
** Also affects: friendly-recovery (Ubuntu Oneiric)
Importance: Medium
Status: Triaged
** Changed in: friendly-recovery (Ubuntu Oneiric)
Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to friendly-recovery in Ubuntu.
https://bugs.launchpad.net/bugs/777524
Title:
“Repair broken packages” option breaks with Python ≥ 2.6
Status in “friendly-recovery” package in Ubuntu:
Triaged
Status in “friendly-recovery” source package in Oneiric:
Triaged
Bug description:
Binary package hint: friendly-recovery
From /usr/share/recovery-mode/options/dpkg:
for v in 2.5 2.6; do
python="/usr/bin/python$v"
script="/usr/lib/python$v/site-packages/DistUpgrade/dist-upgrade.py"
…
This has two bugs:
• Ubuntu has Python 2.6 and 2.7 now. (Perhaps the version list should be automatically generated from /usr/share/python/debian_defaults?)
• As of Python 2.6, site-packages was renamed to dist-packages.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: friendly-recovery 0.2.11
ProcVersionSignature: Ubuntu 2.6.39-0.5-generic 2.6.39-rc5
Uname: Linux 2.6.39-0-generic x86_64
NonfreeKernelModules: openafs
Architecture: amd64
Date: Wed May 4 21:34:23 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.utf8
SHELL=/bin/bash
SourcePackage: friendly-recovery
UpgradeStatus: No upgrade log present (probably fresh install)
More information about the foundations-bugs
mailing list