package python-ufw 0.34~rc-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1409286 reported by Daniil Vasin
4
Affects Status Importance Assigned to Milestone
ufw (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Long story short, author uses python2.7, and my machine uses python3.3 as python. Module ConfigParser has been changed to configparser in python3. Please accomodate your software for new python versions

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: python-ufw 0.34~rc-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
AptOrdering:
 python-ufw: Install
 ufw-kde: Install
 python-ufw: Configure
 ufw-kde: Configure
Architecture: amd64
Date: Sat Jan 10 10:21:13 2015
DuplicateSignature: package:python-ufw:0.34~rc-0ubuntu2:subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2014-12-15 (25 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: ufw
Title: package python-ufw 0.34~rc-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Daniil Vasin (dvasin) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Thank you for using Ubuntu and filing a bug.

I'm not sure what you mean by "Long story short, author uses python2.7, and my machine uses python3.3 as python." ufw is tested to work with python 2.6-2.7 and python 3.1+ (in fact it defaults to python3 in later Ubuntu releases and python-ufw (the package that failed) is only provided for other python2 apps that use ufw). Specifically, src/applications.py has:

if sys.version_info[0] < 3:
    import ConfigParser
else:
    import configparser

You later say that "my machine uses python3.3 as python". Do you mean that you changed the symlink for /usr/bin/python to point to /usr/bin/python3.3 instead of /usr/bin/python2.7? If so, this is not the recommendation from PEP-0394 and is unsupported in Ubuntu and Debian and I would expect many other python2 applications to fail. This has been discussed in various places:
https://mail.python.org/pipermail/python-dev/2013-July/127529.html
https://wiki.ubuntu.com/Python/3
http://legacy.python.org/dev/peps/pep-0394/

Changed in ufw (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniil Vasin (dvasin) wrote :

My mistake, close this bug. I didn't know that 2.7 is still default python for ubuntu, i symbolic linked python3.3 to python, and was getting bugs

Daniil Vasin (dvasin)
Changed in ufw (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.