Daniel Schepler <dschepler <at> gmail.com> writes: > (Sorry about the lack of threading... for some reason I'm unable to find the > links to download mbox archives for replying to the messages.)
https://www.mirbsd.org/cvs.cgi/contrib/hosted/tg/getarticle?rev=HEAD Just call that with either the Message-ID sans <>, or the GMane group and article number (separated with / like in URIs from GMane also works), and it’ll append to the unix-format mailbox in ~/mail/x which you can just reply to with Pine. > In response to Adam's comments about debootstrap not working because findutils > FTBFS: Yes, I'm aware of that, and for now you have to include "unreleased" as Well, that’s normal for Debian-Ports, nothing to apologise for. > For the reason we still have multilib packages instead of relying on > multiarch, see the thread starting at > http://lists.debian.org/debian-devel/2013/05/msg00692.html . (The one good > argument there IMO is that dropping libc6-i386 in favor of libc6:i386 could > cause difficulties autobuilding gcc-multilib when e.g. libgcc1:i386 and Why is gcc built multi-lib anyway? I see *no* benefit there that wouldn’t also be possible with Multi-Arch on the users’ system or is discriminatory (e.g. why should gdb:amd64 support natively debugging i386 binaries but not e.g. armhf binaries). I never understood multilib and still wonder why it’s around. Maybe there’s a good reason, but other than a desire to keep it, I’ve missed anything about that yet… On the contrary, i386 sid users’ systems now end up with this: -rw------- 1 root root 159744 Jun 6 10:23 core /core: ELF 32-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/libx32/ld-linux-x32.so.2' This file is generated quite often, along with the aforementioned kernel messages. I think this is not acceptable. bye, //mirabilos -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/loom.20130611t160404-...@post.gmane.org