Thus spake Goswin von Brederlow:

Jeremy Brand <[EMAIL PROTECTED]> writes:

Package: dpkg-dev
Version: 1.10.28

When I invoke `dpkg-architecture` on Sarge/amd64, the output is
seemingly broken:
                                                                                
 $ uname -a
Linux gamera.domain.mars 2.6.8-11-amd64-k8-smp #1 SMP Wed Jun 1 00:01:27 CEST 2$
$ dpkg-architecture
DEB_BUILD_ARCH=
DEB_BUILD_GNU_CPU=
DEB_BUILD_GNU_SYSTEM=
DEB_BUILD_GNU_TYPE=
DEB_HOST_ARCH=
DEB_HOST_GNU_CPU=                                                               
DEB_HOST_GNU_SYSTEM=
DEB_HOST_GNU_TYPE=

I can't reproduce that and since every second package uses
dpkg-architecture during build the buildd would have had tons of
failures during build with this.

I would suggest looking for the error somewhere else. Did you change
gcc or something?

Nope, not at all. The only thing slightly libc related is our change in nsswitch.conf to use files ldap.

# COLUMNS=150 dpkg -l |grep 'libc6' | awk '{print $1" "$2" "$3}'
ii libc6 2.3.2.ds1-22
ii libc6-dev 2.3.2.ds1-22

This is the same output on all of the 3 extra machines I just ran dpkg-architecture on .

However, I just tested this on some completely different amd64/sarge boxes; some of which were just installed days ago, and the error is still the same. All three systems I tested do not assign values to the output of dpkg-architecture.


[EMAIL PROTECTED]:~% apt-cache policy dpkg-dev
dpkg-dev:
 Installed: 1.10.28

[EMAIL PROTECTED]:~% uname -a
Linux frosties 2.6.8-frosties-1 #2 Sun Oct 3 22:06:03 CEST 2004 x86_64 GNU/Linux

[EMAIL PROTECTED]:~% dpkg-architecture
DEB_BUILD_ARCH=amd64
DEB_BUILD_GNU_CPU=x86_64
DEB_BUILD_GNU_SYSTEM=linux
DEB_BUILD_GNU_TYPE=x86_64-linux
DEB_HOST_ARCH=amd64
DEB_HOST_GNU_CPU=x86_64
DEB_HOST_GNU_SYSTEM=linux
DEB_HOST_GNU_TYPE=x86_64-linux

Well, at least it's good to know the correct output, so that I can force it for building packages.

Is there anything else I can do to help discover why 4 (probably) more of our systems, this doesn't work?

We don't do anything crazy with them at all. We pump them out with an un-attended, debian-installer based (debconf/critical) install.

The mirror we use is:
http://mirrors.jgi-psf.org/debian-amd64/

rsync mirrored from amd64.debian.net/debian-pure64

Jeremy


--
"Prediction is very difficult, especially of the future."
                                   Niels Bohr
http://www.nirvani.net


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to