On Fri, 2008-02-15 at 09:43 +1000, Glen Harris wrote: > I've been trying to install the mipsel packages on my machine for a > couple of weeks now, and it been failing because the emdebian repository > is stuck at 4.1.2-15 while the standard debian packages are at 4.1.2-18. > > The 4.1.2-18 packages are in the emdebian repository, (Oops, wrong reg-exp in the previous email.) $ reprepro list unstable gcc-4.1-mipsel-linux-gnu unstable|main|i386: gcc-4.1-mipsel-linux-gnu 4.1.2-18 unstable|main|amd64: gcc-4.1-mipsel-linux-gnu 4.1.2-18 unstable|main|powerpc: gcc-4.1-mipsel-linux-gnu 4.1.2-17 $ reprepro list testing gcc-4.1-mipsel-linux-gnu testing|main|i386: gcc-4.1-mipsel-linux-gnu 4.1.2-15 testing|main|amd64: gcc-4.1-mipsel-linux-gnu 4.1.2-14 > but the Packages > file has not been updated since Dec 4. > No, what has actually happened is that toolchain packages have not been migrated into testing since December 2007. > Can someone please rebuild the Packages files? > It's not about rebuilding the Packages file, it is about migrating packages to testing. This is not automatic in Emdebian. You can always change your emdebian sources list to look at the toolchain from unstable instead of testing. Migration toolchains to testing has proved to be difficult and error-prone when automated. It isn't the same as Britney in Debian, unfortunately. Things will settle in the pre-Lenny release freeze in Debian but right now, Hector has a few internet connection problems so there are a variety of toolchain issues. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
signature.asc
Description: This is a digitally signed message part