Arch Linux User Repository

@Crouze, I found the reason for this in your system. There is a package named builtins in your Python 2, though in Python 2 the built-ins module is called __builtin__. Please let me know if this new version now works for you.

@hexd, thanks for this, I indeed got it installed with the added --nocheck flag.

Result of pacman -Q | grep python2: python2 2.7.18-5 python2-apipkg 1.5-7 python2-appdirs 1.4.4-6 python2-atomicwrites 1.4.0-5 python2-attrs 21.4.0-1 python2-backports 1.1-1 python2-backports.functools_lru_cache 1.6.4-3 python2-beautifulsoup4 4.9.3-5 python2-cairo 1.18.2-4 python2-chardet 4.0.0-2 python2-colorlog 4.1.0-1 python2-configobj 5.0.6-6 python2-configparser 4.0.2-2 python2-contextlib2 0.6.0.post1-5 python2-funcsigs 1.0.2-3 python2-future 0.18.2-2 python2-gobject 3.36.1-5 python2-gobject2 2.28.7-7 python2-httplib2 0.18.1-1 python2-idna 2.10-4 python2-importlib-metadata 2.1.1-1 python2-iniconfig 1.1.1-3 python2-linecache2 1.0.0-5 python2-lxml 4.9.0-1 python2-more-itertools 5.0.0-2 python2-numpy 1.16.6-2 python2-olefile 0.46-5 python2-ordered-set 3.1.1-4 python2-packaging 20.9-7 python2-pam 1.8.4-3 python2-pathlib2 2.3.7.post1-1 python2-pbr 5.9.0-2 python2-pexpect 4.8.0-3 python2-pillow 6.2.2-2 python2-pluggy 0.13.1-6 python2-psutil 5.9.1-1 python2-ptyprocess 0.7.0-1 python2-py 1.10.0-3 python2-pybluez 1:0.22-4 python2-pycryptodome 3.14.1-1 python2-pycryptodomex 3.14.1-2 python2-pycurl 1:7.43.0.3-1 python2-pyephem 4.1.3-1 python2-pyinotify 0.9.6-7 python2-pyparsing 2.4.7-6 python2-pyserial 3.5-1 python2-pyside 1.2.4-10 python2-pytest 4.6.11-1 python2-pytest-runner 5.2-4 python2-requests 2.27.1-1 python2-scandir 1.10.0-4 python2-setproctitle 1.1.10-5 python2-setuptools 2:44.1.1-1 python2-setuptools-scm 5.0.2-1 python2-shiboken 1.2.4-8 python2-simplejson 3.17.6-4 python2-six 1.16.0-5 python2-soupsieve 1.9.6-3 python2-traceback2 1.4.0-7 python2-unittest2 1.1.0-7 python2-urllib3 1.26.7-1 python2-wcwidth 0.2.5-6 python2-wxpython3 3.0.2.0-3 python2-zipp 1:1.1.1-1

makepkg -sr is called from /home/foo/Temp/python2-unittest2

Content of src/unittest2-1.1.0: build PKG-INFO README.txt setup.cfg setup.py unittest2 unittest2.egg-info

Hope this helps.

I got the same error as @Crouze when I tried to just do a makepkg normally, but I was able to compile it just fine in a chroot. I don't claim to understand why, but I hope that helps.

@Crouze, this looks like an issue with the checking step, not the build one, so you can still install it by skipping the check() (i.e., calling makepkg --nocheck). But I'll fix it as soon as I discover why this specific test works for me but not for you (i.e., something is different either in our environments or in the building procedure). Can you give me more information about the system, like the result of pacman -Q | grep python2? What's the directory where you called makepkg and the exact command you ran? What's in the src/unittest2-1.1.0 directory?

Here 3 tests are being skipped: testHandlerReplacedButCalled, testSecondInterrupt and test_discovery_from_dotted_namespace_packages; all the other ones are passing. The test that failed for you uses a hackish approach to change (mock) the import mechanism, so a simple empty directory src/unittest2-1.1.0/package/ would make that test fail (though not with that error message, so I guess that's not the case).

Package fails to build:

<h2>ERROR: test_discovery_failed_discovery (unittest2.test.test_discovery.TestDiscovery)</h2>

Traceback (most recent call last): File "unittest2/test/test_discovery.py", line 840, in test_discovery_failed_discovery loader.discover('package') File "unittest2/loader.py", line 364, in discover raise ImportError('Start directory is not importable: %r' % start_dir) ImportError: Start directory is not importable: 'package'