Re: Where to start hacking unstable on Alpha?
--On Tuesday, July 05, 2011 11:59:43 AM +1200 Michael Cree <mcree@orcon.net.nz> wrote:
On 5/07/2011, at 11:22 AM, Bill MacAllister wrote:
--On Monday, July 04, 2011 08:36:20 AM +1200 Michael Cree <mcree@orcon.net.nz
> wrote:
Life isn't easy in the Unstable chroot, worst of all, it seems that
coreutils are working bad, expecially 'rm'.
This is really bad situation, if coreutils don't work well, nothing
will grow up in health.
I am not seeing this problem. I have an unstable chroot running on a
PWS600au under Lenny and a unstable chroot running on a XP1000 under
Sid. All are updated to my repository which is a few hundred
packages
ahead of debian-ports.
I also have an unhappy chroot. I am running a 2.6.32 kernel with
older,
i.e. not qlogic, SCSI controllers. Here is what is an example of
what is
currently holding me up:
# chroot unstable
# cd tmp
# mkdir foo
# mkdir foo/bar
# chown -R root foo
chown: cannot access `foo/bar': Function not implemented
My guess would be that Michael's chroots pre-date the change that is
causing the problem. I think that we require a newer kernel or an
older
chroot.
Michael,
Thanks for this. A bit slow in getting back to you because both of my
alphas hung with the 2.6.32 kernel.
On the XP1000:
Kernel 2.6.38.8 compiled from sources from kernel.org. Debian
version: Sid updated to my repository which is ahead of
debian-ports. Schroot: 1.4.23-1 with sid installed and upgraded to
my repository. Has libc6.1 version 2.13-8 for example and is
currently building eglibc 2.13-9.
On the PWS600au:
Kernel is Debian Lenny kernel 2.6.26-2-alpha-generic Debian version:
Lenny with sbuild/buildd from Lenny-backports. Schroot:
1.4.19-1~bpo50+3 with sid installed and upgraded to my repository.
Has libc6.1 version 2.13-8 for example.
The buildd on the PWS600au is working very nicely. The one on the
XP1000 does not upload packages properly, i.e, the perl code errors
out when buildd-uploader is called, so I am having to call dupload
manually. Might be because perl is still at 5.10.1-19 on this
machine (whereas it has upgraded to 5.12.whatever in the sid chroot
environment) because I don't have enough built yet for apt-get
dist-upgrade to work.
BTW, eglibc will only build with a newer kernel. It failed with
many test suite failures on the PWS600au running the Lenny kernel,
but builds fine on the XP1000. Even kernel 2.6.32 won't be good
enough as it is missing a number of syscalls.
Maybe I should add one of my Alphas to the debian-ports autobuilder
instead of selfishly building packages for myself? But I would only
want to do this for the short-term, i.e., to help clear some of the
backlog, as I would ultimately like to be able to use the XP1000 for
my own purposes!
The biggest difference that I see if the version of libc6.1. What is
installing on my systems is 2.7-18lenny7. I will build a newer
version and see if that helps me.
I am building a new kernel now, 2.6.39.2. The only change I made to the
configuration that was used with the 2.6.32-bpo.5-alpha-smp was to build
in the qlogic drivers rather than load them as a module.
I am using sudo instead of schroot right now because I thought that
would help. I have just not switched back yet, but it really is not
the problem at this point. I am seeing the failure when I interactively
chroot into the unstable chroot.
I will pound on it intensively this week and see if I can get off the
dime. If I am still stuck we can move your system into the breach. Or,
if you wanted to take command of one of my buildd systems that would be
fine as well. I am only working on one of them at this point.
Bill
--
Bill MacAllister
Infrastructure Delivery Group, Stanford University
Reply to: