setup.py yields DistUtilsExtra.auto error

Bug #1263771 reported by John Kim
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pylang
Fix Released
Undecided
Bhavani Shankar

Bug Description

Please see the working directory attached, and try running setup.py in there. Here is what I've seen.

john@kotux:~/pylang/pylang$ sudo python setup.py install --prefix=/usr
running install
running build
running build_py
running build_i18n
intltool-update -p -g pylang
running build_icons
running build_help
running install_lib
running install_data
copying build/mo/es/LC_MESSAGES/pylang.mo -> /usr/share/locale/es/LC_MESSAGES
copying build/mo/ko/LC_MESSAGES/pylang.mo -> /usr/share/locale/ko/LC_MESSAGES
copying build/mo/en_GB/LC_MESSAGES/pylang.mo -> /usr/share/locale/en_GB/LC_MESSAGES
copying build/mo/ast/LC_MESSAGES/pylang.mo -> /usr/share/locale/ast/LC_MESSAGES
copying build/mo/ab/LC_MESSAGES/pylang.mo -> /usr/share/locale/ab/LC_MESSAGES
copying build/share/applications/pylang.desktop -> /usr/share/applications
running install_egg_info
Removing /usr/lib/python2.7/site-packages/pylang-0.0.4-py2.7.egg-info
Writing /usr/lib/python2.7/site-packages/pylang-0.0.4-py2.7.egg-info
WARNING: the following files are not recognized by DistUtilsExtra.auto:
  INSTALL
  bin/pylang
john@kotux:~/pylang/pylang$

Tags: packaging
Revision history for this message
John Kim (kotux) wrote :
Revision history for this message
John Kim (kotux) wrote :

Hi, I added a premature preinst script, and though the installation of pylang succeeded with a "no clean" builddeb, builddeb -S failed. DistUtils didn't recognize 2 files in the "no clean" build, but the building proceeded anyway without a problem. At builddeb -S, DistUtils didn't recognize 4 files.

Please look at the contents of the newly-updated pylang package. I would like some help in making preinst work.

Also see the output from my console:
http://pastebin.com/UcCzh58K

Revision history for this message
John Kim (kotux) wrote :

Something interesting just happened. After customizing my devscripts.conf and running debuild in the root directory [1], I started to have a different sort of errors.

Now, when I run bzr builddeb -S, I get this message:

```bash
john@kotux:~/pylang/pylang$ bzr builddeb -S
Building using working tree
Building package in normal mode
Purging the build dir: /home/john/pylang/build-area/pylang-0.0.4
Looking for a way to retrieve the upstream tarball
Upstream tarball already exists in build directory, using that
bzr: ERROR: An error (1) occurred running quilt:

Applying patch 01_desktop_fix.patch
patching file pylang.desktop.in
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- rejects in file pylang.desktop.in
Patch 01_desktop_fix.patch can be reverse-applied

john@kotux:~/pylang/pylang$
```

[1] http://www.debian.org/doc/manuals/maint-guide/build.en.html#debuild

Changed in pylang:
assignee: nobody → John Kim (kotux)
Revision history for this message
John Kim (kotux) wrote :

Let me also mention that adding a preinst script did not fix the setup.py installation problem. I don't know how the bzr builddeb worked.

Do you think of setup.py installs, then signed builddeb would work too?

```bash
john@kotux:~/pylang/pylang$ sudo python setup.py install
[sudo] password for john:
running install
running build
running build_py
running build_i18n
intltool-update -p -g pylang
running build_icons
running build_help
running install_lib
running install_data
running install_egg_info
Removing /usr/local/lib/python2.7/dist-packages/pylang-0.0.4.egg-info
Writing /usr/local/lib/python2.7/dist-packages/pylang-0.0.4.egg-info
WARNING: the following files are not recognized by DistUtilsExtra.auto:
  INSTALL
  bin/pylang
john@kotux:~/pylang/pylang$
```

Revision history for this message
Bhavani Shankar (bhavi) wrote :

Fixed in the latest upload to the ubuntu repositories.

Sitting in new queue

Regards
Bhavani

Changed in pylang:
status: New → Fix Committed
assignee: John Kim (kotux) → Bhavani Shankar (bhavi)
costales (costales)
Changed in pylang:
status: Fix Committed → Fix Released
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.