On 22 May 2005 at 10:13, Steve Langasek wrote: | Hi Dirk, | | On Sun, May 22, 2005 at 02:09:30PM +0200, Kurt Roeckx wrote: | > Package: rpy | > Version: 0.4.1-2 | > Severity: serious | > Tags: sarge | | > This package is failing to build in sarge but it seems to have | > been fixed in sid. (-3 or -4 version?) | | > It's failing with the following error: | > CFLAGS="-O2 -Wall" python2.2 setup.py build | > Building for R version 2.1.0 ... | > Traceback (most recent call last): | > File "setup.py", line 136, in ? | > RSRC = get_R_SRC() | > File "setup.py", line 57, in get_R_SRC | > raise DistutilsExecError( \ | > distutils.errors.DistutilsExecError: | | > The path | | > /root/build/rpy-0.4.1/R-2.1.0 | | > which should contain header files for R version 2.1.0 | > does not exist! | | > Please see the rpy README file for instructions. | | > make: *** [build-stamp] Error 1 | | It looks like rpy 0.4.1-4 fixes this bug by adding a full set of R-2.1.0
I recalled that we had fixed it; I guess I confused 2.0.1 with 2.1.0 here. | headers inside the tarball. Is this really the appropriate fix? If so, I | can push 0.4.1-4 into sarge; but it looks like these headers are duplicates | of the ones already present in r-base-core, and that this is actually a bug | with the upstream build-scripts? You need to talk to Greg (== upstream) about that. He calls this "batteries ^H generators included". For other less stringently organised upstream systems, shipping the headers is appropriate. For us, it is overkill, but then this ain't a Debian-native package so ... What do I have to do to get 0.4.1-4 into sarge? Looking from the different 'build', 'excuses' and 'more' links off my qa summary page (http://people.debian.org/~igloo/status.php?packages=rpy), it looks like this has been built everywhere. Can you push it into sarge? Dirk -- Statistics: The (futile) attempt to offer certainty about uncertainty. -- Roger Koenker, 'Dictionary of Received Ideas of Statistics' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
