Package: apt-build Version: 0.11.10 Severity: important I'm trying to build a few scientific packages myself to optimize, but I see quite a few of them failing. Take, for example grass.
If I go: apt-build build-source grass the following is the last part of the output: Reading Package Lists... Done Building Dependency Tree... Done Need to get 7818kB of source archives. Get:1 ftp://ftp.no.debian.org sarge/main grass 6.0.0-1 (dsc) [1017B] Get:2 ftp://ftp.no.debian.org sarge/main grass 6.0.0-1 (tar) [7791kB] Get:3 ftp://ftp.no.debian.org sarge/main grass 6.0.0-1 (diff) [25.1kB] Fetched 7818kB in 15s (491kB/s) dpkg-source: extracting grass in grass-6.0.0 -----> Building grass <----- E: Unable to find a source package for libgrass Use of uninitialized value in concatenation (.) or string at /usr/bin/apt-build line 301. Can't chdir(libgrass-): No such file or directory at (eval 1) line 3 main::__ANON__('libgrass-') called at /usr/bin/apt-build line 301 main::build('grass', 6.0.0, -1) called at /usr/bin/apt-build line 563 main::build_source called at /usr/bin/apt-build line 81 As we can see, grass is downloaded and found, but is later in the build process not found. The same results if I say apt-build install libgrass and variations of it. I have tried on two different machines now, both running Sarge. The system I submit this report from is the cleanest of the two. This latter system successfully completed apt-build install atlas3-sse2 r-recommended but they are the only self-build packages. I've seen that for some packages it tries to chdir(-), so I've been speculating that the - is the separator between the package name and the version number. In this case it gets the source package name wrong, and once that's failed, the version number is unavailable. Speculations, but something like that... I'm uncertain whether this is an apt-build bug or a package packaging bug. I'm sure the apt-build author is well qualified to figure this out and reassign if appropriate, so I guess my safest bet is to submit it here. BTW, I never saw it using the pentium4 CPU type in any gcc calls either... Cheers, Kjetil -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages apt-build depends on: ii apt 0.5.28.6 Advanced front-end for dpkg ii apt-utils 0.5.28.6 APT utility programs ii debconf 1.4.30.13 Debian configuration management sy ii devscripts 2.8.14 Scripts to make the life of a Debi ii dpkg-dev 1.10.28 Package building tools for Debian ii g++ 4:3.3.5-3 The GNU C++ compiler ii gcc 4:3.3.5-3 The GNU C compiler ii libappconfig-perl 1.56-2 Perl module for configuration file ii libapt-pkg-perl 0.1.13 Perl interface to libapt-pkg ii perl 5.8.4-8 Larry Wall's Practical Extraction -- debconf information: apt-build/arch_amd: k6 apt-build/arch_alpha: ev4 * apt-build/options: * apt-build/arch_intel: pentium4 apt-build/arch_arm: armv2 * apt-build/make_options: * apt-build/olevel: Strong * apt-build/build_dir: /var/cache/apt-build/build * apt-build/repository_dir: /var/cache/apt-build/repository apt-build/arch_sparc: sparc * apt-build/add_to_sourceslist: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
