[Bug 78455] Re: DEFECT in checkinstall: abort due to missing file or directory

[Marc Deslauriers]

Could someone please open an upstream Debian bug about this issue and
link the bug here? Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/78455

Title:
  DEFECT in checkinstall: abort due to missing file or directory

Status in “checkinstall” package in Ubuntu:
  Triaged
Status in “checkinstall” source package in Maverick:
  Confirmed

Bug description:
  Binary package hint: checkinstall

  I get the following debug information and abort, when I try to create
  a new package with:

  "checkinstall unsermake install"
  #####
  ========================= Installation results ===========================
  Traceback (most recent call last):
    File "<string>", line 1, in ?
    File "/usr/lib/python2.4/site-packages/unsermake/__init__.py", line 1362, in ?
      main()
    File "/usr/lib/python2.4/site-packages/unsermake/__init__.py", line 1047, in main
      files = os.listdir(sourcedir)
  OSError: [Errno 2] No such file or directory: '/usr/lib/python2.4/site-packages/unsermake'

  ****  Installation failed. Aborting package creation.

  Cleaning up...OK

  Bye.

  #####
  This worked with the OLD checkinstall version in Dapper (the newest checkinstall version for Dapper stopped also correct work).
  The strange thing:
  The indicated directory EXISTS. But somehow the program doesn't find it.

  My system is a fresh Edgy install with pure *.deb based system setup.
  Checkinstall is version: 1.6.0-2ubuntu1 from universe/admin

  Is it possible, that I'm missing any python helper package? Or should
  I reconfigure some packages or define suitable alternatives? Maybe it
  works only with some special python versions?

  This happens in all following call scenarios:
  + KDE _user_ session with "sudo checkinstall unsermake install"
  + KDE konsole with calling "su" before --> calling checkinstall in super user mode with "checkinstall unsermake install"
  + console mode (no X11) with direct login as "root" --> calling directly "checkinstall unsermake install"
  I did this to avoid any problems that might be caused by old .dot files from my old $HOME which is containing config files from very old OS versions.
  But the "/root" account is fresh, so that the problem shouldn't be caused by old .dot-files.

  I will have to switch back to the last working checkinstall version
  1.5.3 right now.

  Thanks,
  Achim

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/checkinstall/+bug/78455/+subscriptions