Package: apt-build Version: 0.11.8 Severity: normal
-- System Information: Debian Release: 3.1 APT prefers testing APT policy: (450, 'testing') Architecture: i386 (i586) Kernel: Linux 2.4.22firewall Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) 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.27 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-5 Larry Wall's Practical Extraction -- debconf information: apt-build/arch_amd: k6 apt-build/arch_alpha: ev4 * apt-build/options: -fomit-frame-pointer -pipe * apt-build/arch_intel: pentium apt-build/arch_arm: armv2 * apt-build/make_options: * apt-build/olevel: Medium * 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 I have this problem with apt-build: I installed a minimal system in a chroot jail (using debootstrap) and I want it to compile packages for me. the first thing I do is recompile the base system. I have a /var/cache/apt/archives directory full of i386 binary packages delivered from a Debian mirrors, this is for satisfying build dependencies. The messages apt-build prints out: (remark: adding --reinstall or --rebuild does not make any difference) # apt-build world -----> Rebuilding the world! <----- -----> Building package list <----- Sorry, can't find adduser, is it already installed? (Remove it first, or try running 'apt-get clean') Sorry, can't find apt, is it already installed? (Remove it first, or try running 'apt-get clean') [...] if I start with an empty /var/cache/apt/archives, apt-build starts building stuff like it is supposed to do. I think the logic behind this may be that after building the package, the version in the cache will get instead of the freshly-built version. But I do not care about whether the packages in the chroot jail are optimised or not, it is the fact that I am building the repository that matters. I could work around this by creating a Debian repository of the /var/cache/apt/archives directory, but this has a side effect: that directory contains a truckload of packages from the 3 different Debian branches so I won't be certain about which branch build-deps are installed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
