Re: Future of m68k - Etch and beyond
On Thu, 1 Mar 2007, Wouter Verhelst wrote:
> On Thu, Mar 01, 2007 at 10:05:55AM +1100, Finn Thain wrote:
> > On Wed, 28 Feb 2007, Ingo Juergensmann wrote:
> > > I think most of the Debian m68k porters would prefer to stay with Debian
> > > instead of another distro. Just an assumption... ;)
> >
> > Yes, but I'll say it anyway: Gentoo gives you sufficient flexibility
> >
> >
> > Just the fact that they don't really have a "release cycle" makes it
> > attractive. And (apparently) it has already been ported to m68k. And it
>
> Only partially so. I once tried it, it wasn't even remotely useful.
I guess the Debian build daemons have more RAM/disk than the average machine
running Linux/m68k? I don't want to compile everything myself.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Future of m68k - Etch and beyond
On Fri, 2 Mar 2007, Geert Uytterhoeven wrote:
> On Thu, 1 Mar 2007, Wouter Verhelst wrote:
> > On Thu, Mar 01, 2007 at 10:05:55AM +1100, Finn Thain wrote:
> > > On Wed, 28 Feb 2007, Ingo Juergensmann wrote:
> > > > I think most of the Debian m68k porters would prefer to stay with
> > > > Debian instead of another distro. Just an assumption... ;)
> > >
> > > Yes, but I'll say it anyway: Gentoo gives you sufficient flexibility
> > >
> > >
> > > Just the fact that they don't really have a "release cycle" makes it
> > > attractive. And (apparently) it has already been ported to m68k. And
> > > it
> >
> > Only partially so. I once tried it, it wasn't even remotely useful.
>
> I guess the Debian build daemons have more RAM/disk than the average
> machine running Linux/m68k? I don't want to compile everything myself.
Gentoo supports binary packages, but there are very few available for m68k
at present.
I'm not going to attempt it without distcc and some fast cross-compilers
(even though that still requires a fair chunk of RAM for linking).
-f
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like
> that.
> -- Linus Torvalds
>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Future of m68k - Etch and beyond
On Fri, Mar 02, 2007 at 10:24:55AM +0100, Geert Uytterhoeven wrote: > On Thu, 1 Mar 2007, Wouter Verhelst wrote: [gentoo] > > Only partially so. I once tried it, it wasn't even remotely useful. > > I guess the Debian build daemons have more RAM/disk than the average machine > running Linux/m68k? Absolutely. Most of our build daemons are maxed out on RAM. > I don't want to compile everything myself. Me neither :) -- Fun will now commence -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Please build tpu vlc 0.8.6-svn20061012.debian-4
> > I fixed the testing chroot on kullervo, and updated buildd.conf to place > > testing before unstable there. > > The caveat to having testing before unstable is that when the same version is > pending both places, as happens to us on occasion, you end up getting a > reject on the testing one. The problem with having unstable first is that we never get to testing except when there is no crunch. Seems to work now, but I'd rather get cracking on testing... > > q650 has severe disk space problems so I'd rather not add testing there. > > I could probably send you a disk if that would help. I'm sure I've got a > 4 or 9GB lying around somewhere. A 4 GB would already help a lot, thanks. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Newbie installing Sarge on Amiga from CD
Hello, I am about to try installing Debian Sarge (3.1 rev 5) on my Amiga 2000 (Blizzard 2060, 96 MB Fast RAM, Buddha IDE, X-Surf). After a few unsuccessful tries using CD:s burnt from downloaded ISO images (it turned out the CD-R media were of bad quality. After a change of brand it went well), I today began an installation. My (well, the miggy's) hardware was recognized, the base-installer loaded from CD, and the network configured using DHCP. At the point where partitions are prepared for Linux, I tried to get the installer to use 3 partitions I used a few years ago when doing a partial install of Woody (two ext2 and one swap partition). However, the installer found the old files and refused to continue, probably to prevent me from destroying an old installation. Is there an easy way to erase the data on these partitions? I know that the preferred way is to let the Linux tool partition hard drives, but I did that with (OS3.9BB2) HDToolBox (worked for Woody) because I have AMIGA partitions on the same disk, and thought it would be safest to use a native tool which I know very well. The AMIGA partition tools I have experience with do not erase existing data on partitions when repartitioning a hard drive, but perhaps the Linux tool launched during the installation does? What would you guys recommend? The part of the HD intended for Debian is at the high cylinder end of the drive, so that I can play around with the partitions without risking the AMIGA data on the other partitions. Regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
testing_outdate, build clustalw, buildd information request...
Hi, http://ftp-master.debian.org/testing/testing_outdate.txt has bothered me since I discovered it a few times. It shows m68k has 22 out of date with mipsel and hppa at 6. Most are at 0 or 1. Please consider building/uploading clustalw 1.83-1.2 What's going on with etch-secure? See http://etch-secure.buildd.net/index-m68k.html that things are claimed but seemingly nothing's been built for a long time. What is this? An unembargoed pre-release version of the security buildd setup? Where's tpu, spu buildd information? I'm guessing security uploads are embargoed, but proposed updates shouldn't be security updates right? Some ftbfs problems (add to reasons: http://buildd.debian.org/fetch.cgi?&pkg=ctn&ver=3.0.6-10&arch=m68k&stamp=1171341799&file=log [...] ln -s ../facilities/dicom/intsizes.h /build/buildd/ctn-3.0.6/libsrc ln: creating symbolic link `/build/buildd/ctn-3.0.6/libsrc/intsizes.h' to `../facilities/dicom/intsizes.h': File exists make[3]: *** [links] Error 1 [...] http://buildd.debian.org/fetch.cgi?&pkg=fcitx&ver=1%3A3.4.3-1&arch=m68k&stamp=1171495231&file=log [...] m68k-linux-gnu-gcc -Wall -g -O2 -INONE -INONE -I/usr/include/freetype2 -D_USE_XFT -Wall -o mb2org mb2org.o ../src/pyParser.o ../src/pyMapTable.o ../src/PYFA.o ../src/sp.o pyTools.o -LNONE -lXft -lfontconfig -lX11 ./txt2mb ./../data/cj.txt ../data/cj.mb Reading 6726 records. ./txt2mb ./../data/erbi.txt ../data/erbi.mb Reading 82911 records. ./txt2mb ./../data/wbx.txt ../data/wbx.mb Reading 68782 records. ./createPYMB ./../data/gbkpy.org ./../data/pyPhrase.org make[3]: *** [all] Segmentation fault [...] I'm occasionally looking through the testing script output then: 1 checking to see if that version failed to build or was never built 1a if it was never built, request it be built 1b if it was built, bug someone to upload and install? 1c if it failed to build, check if it ftbfs on other architectures 1ci if it didn't ftbfs on other archs, request consider requesting rebuild 1cii if it did ftbfs on other archs, almost automatically file a bug So some of this might be able to be automated and save some future porter time. Also adding links between some of these pages would save time. I guess later I'll: - bug smarenka to find out if his pages are automatically generated - bug d-release (probably aj) about links from the testing output to buildd.d.o. - 1b sounds like it could generate an email for the porters list or possibly ftpmaster if it has been uploaded? Who works on this software? I'll look for someone to discuss this with. - find buildd.d.o person to help mark ftbfs that's only on one arch? I guess igloo does this? - Discuss 1ci with 1b people. Certainly this kind of failure should be flagged somehow. - Discuss 1cii on debian-devel. Perhaps a script to check buildd failures and automatically file bugs when a package files on multiple archs? The script may also be able to close such bugs when they do get fixed. Maybe buildd maybe-failed should always trigger filing a bug and maybe-success could be tied to it and automatically close such a bug (with appropriate version tags). Fwiw, I'd like it if all of buildd.net's targets were being built. If that means more buildd's, then why not? backports shows no buildds. non-free may need another buildd. sarge-volatile is built, but may be problematic later (where's ekg's libreadline4 though? dep-wait since 2005?). I've heard some people talk about not building testing, or not releasing with etch. Isn't the port just about ready for etch? Most of the remaining ftbfs could be made not-for-us (nfu) on m68k right? E.g. mozart, r-base... vorlon or aj seemed to suggest once that porters should mark more packages as nfu (although I'm sure they want to avoid dependency problems). I supposed I've rambled on a bit, but then I'm hoping if my comments don't help the port much directly, it'll help it indirectly by helping me learn the buildd process better. Thanks, Drew Daniels Resume: http://www.boxheap.net/ddaniels/resume.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Newbie installing Sarge on Amiga from CD
Zitat von Christer Oldhoff <[EMAIL PROTECTED]>: > At the point where partitions are prepared for Linux, I tried to get > the installer to use 3 partitions I used a few years ago when doing a > partial install of Woody (two ext2 and one swap partition). > However, the installer found the old files and refused to continue, > probably to prevent me from destroying an old installation. > > Is there an easy way to erase the data on these partitions? Two ways: either you will leave the Partitioning information intact, then you can use "dd if=/dev/null/ of=/dev/"name of partition here"" to overwrite every single byte on the partition. or you can easily delete the partitions with afdisk Of course you have to pay attention when you use low-level tools like dd and afdisk. You need a shell to enter theese commands. You should be able to switch to a second console by pushing Alt-F2 or you choose the option from the install-menue. Kind Regards Andreas Obländer
