Possibly an intermittent issue because oneconf-common wasn't upgraded while python3-oneconf and oneconf were trying to upgrade. I've re-run apt-get update and apt-get upgrade now.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: oneconf 0.3
ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic i686
ApportVersion: 2.8-0ubuntu2
Architecture: i386
Date: Tue Jan 22 11:25:05 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/share/oneconf/oneconf-query
InstallationDate: Installed on 2010-10-01 (843 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/oneconf-query --async-update
ProcEnviron:
PATH=(custom, user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/bash
PythonArgs: ['/usr/bin/oneconf-query', '--async-update']
SourcePackage: oneconf
Title: oneconf-query crashed with ImportError in /usr/bin/oneconf-query: No module named oneconf.version
Traceback:
Traceback (most recent call last):
File "/usr/bin/oneconf-query", line 37, in <module>
from oneconf.version import *
ImportError: No module named oneconf.version
UpgradeStatus: Upgraded to raring on 2012-11-16 (67 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
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 #1102715, 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.