[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#587969: mock: doesn't work on kfreebsd-*: /usr/bin/python: undefined symbol: personality

Package: mock
Version: 1.0.8-1
Severity: wishlist
User: debian-bsd@lists.debian.org
Usertags: kfreebsd

On kfreebsd-*, mock crashes with a not very friendly error message:

# mock init
Traceback (most recent call last):
  File "/usr/sbin/mock", line 64, in <module>
    import mock.backend
  File "/usr/lib/pymodules/python2.6/mock/backend.py", line 25, in <module>
    import mock.util
  File "/usr/lib/pymodules/python2.6/mock/util.py", line 29, in <module>
    _libc.personality.argtypes = [ctypes.c_ulong]
  File "/usr/lib/python2.6/ctypes/__init__.py", line 366, in __getattr__
    func = self.__getitem__(name)
  File "/usr/lib/python2.6/ctypes/__init__.py", line 371, in __getitem__
    func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /usr/bin/python: undefined symbol: personality

While it is understandable that mock doesn't work on non-Linux systems, it would be nice if an error message explained what is the culprit (i.e., that you need Linux to run this program).

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: kfreebsd-i386 (i686)

Kernel: kFreeBSD 7.3-1-686
Locale: LANG=C, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages mock depends on:
ii  adduser                       3.112      add and remove users and groups
ii  python                        2.6.5-5    An interactive high-level object-o
ii  python-decoratortools         1.7-3      version-agnostic decorators suppor
ii  python-support                1.0.9      automated rebuilding support for P
ii  rpm                           4.8.1-5    package manager for RPM
ii  usermode                      1.105-0.1  Graphical tools for certain user a
ii  yum                           3.2.25-1   Advanced front-end for rpm

Jakub Wilk

Attachment: signature.asc
Description: Digital signature

Reply to: