Hide Forgot
abrt version: 1.1.17 architecture: x86_64 component: R2spec executable: /usr/bin/R2spec kernel: 2.6.35.11-83.fc14.x86_64 package: R2spec-3.0.3-1.fc14 reason: Description.py:150:setDescriptionFile:OSError: [Errno 2] No such file or directory: './tmp/ArrayExpressHTS' release: Fedora release 14 (Laughlin) time: 1302007987 uid: 500 backtrace ----- Description.py:150:setDescriptionFile:OSError: [Errno 2] No such file or directory: './tmp/ArrayExpressHTS' Traceback (most recent call last): File "/usr/bin/R2spec", line 49, in <module> R2spec().main(source, url, package, bioc, cran, rforge, rproject, copyFile, name, email, force) File "/usr/lib/python2.7/site-packages/r2spec/R2spec.py", line 115, in main package.setDescription() File "/usr/lib/python2.7/site-packages/r2spec/RPackage.py", line 152, in setDescription description.setDescriptionFile(self) File "/usr/lib/python2.7/site-packages/r2spec/Description.py", line 150, in setDescriptionFile os.chdir("./tmp/" + package.name) OSError: [Errno 2] No such file or directory: './tmp/ArrayExpressHTS' Local variables in innermost frame: self: <r2spec.Description.Description instance at 0x1e33d88> original_directory: '/home/adam/rpmbuild/SOURCES' package: <r2spec.RPackage.RPackage instance at 0x1df9e60> How to reproduce ----- 1. Tried to build spec file for new R package (in tar.gz) 2. 3.
Created attachment 489974 [details] File: backtrace
It only seems to work for me if I put the .tar.gz in ~/rpmbuild/SOURCES and then run R2spec in that directory. Otherwise, it crashes.
Thanks for the heads-up, I thought I fixed this issue on the git but I cannot find a correspondent entry in the git log... I should document more. I will try to look into it.
I just pushed a fix in the git repo, you may want to test it :) One of these days I will (re)write the version 3 of this tool from scratch...
Yes, it fixes this particular problem, though I still need to put in the explicit path to the downloaded tarball, even if it's in the current directory. Would be nice if I didn't have to do that... Thanks, Adam
Point taken but I will close this bug as for now it is the intended behaviour. Thanks for the report.