Description of problem: I saw this error on building sazanami-fonts package that uses ttx to patch out. this seems appearing for a while but as deprecation warning. and it seems promoted to the error now on python 2.7. Version-Release number of selected component (if applicable): fonttools-2.2-8.fc14 How reproducible: always Steps to Reproduce: 1.rpmbuild --rebuild sazanami-fonts-0.20040629-14.fc14.src.rpm 2. 3. Actual results: Parsing 'GSUB' table... Traceback (most recent call last): File "/usr/bin/ttx", line 11, in <module> ttx.main(sys.argv[1:]) File "/usr/lib64/python2.7/site-packages/FontTools/fontTools/ttx.py", line 288, in main process(jobs, options) File "/usr/lib64/python2.7/site-packages/FontTools/fontTools/ttx.py", line 273, in process action(input, output, options) File "/usr/lib64/python2.7/site-packages/FontTools/fontTools/ttx.py", line 181, in ttCompile ttf.save(output) File "/usr/lib64/python2.7/site-packages/FontTools/fontTools/ttLib/__init__.py", line 202, in save writer.close() File "/usr/lib64/python2.7/site-packages/FontTools/fontTools/ttLib/sfnt.py", line 137, in close directory = directory + entry.toString() File "/usr/lib64/python2.7/site-packages/FontTools/fontTools/ttLib/sfnt.py", line 196, in toString return sstruct.pack(sfntDirectoryEntryFormat, self) File "/usr/lib64/python2.7/site-packages/FontTools/sstruct.py", line 74, in pack data = apply(struct.pack, (formatstring,) + tuple(elements)) struct.error: 'l' format requires -2147483648 <= number <= 2147483647 error: Bad exit status from /var/tmp/rpm-tmp.PA0I6G (%build) Bad exit status from /var/tmp/rpm-tmp.PA0I6G (%build) Expected results: No errors happens Additional info:
fonttools-2.3-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/fonttools-2.3-1.fc14
fonttools-2.3-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/fonttools-2.3-2.fc14
fonttools-2.3-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.