On Mon, Dec 03, 2012 at 03:46:39PM +1100, Finn Thain wrote:
>
> On Sun, 2 Dec 2012, Wouter Verhelst wrote:
>
> >
> > I have a completely fucked installation on quickstep. The MuckOS won't
> > do TCP/IP anymore, so I can't download from the Internet.
>
> If this MacOS installation has a TCP sta
Le 3 décembre 2012 à 07:19, Michael Tomkins a écrit :
> On 03/12/12 15:46, Finn Thain wrote:
> >
> > On Sun, 2 Dec 2012, Wouter Verhelst wrote:
> >
> >>
> >> I have a completely fucked installation on quickstep. The MuckOS won't
> >> do TCP/IP anymore, so I can't download from the Internet.
> >
>
Hi Thorsten,
Michael Schmitz dixit:
elgar:~# debootstrap --variant=buildd
Add
--keyring=/usr/share/keyrings/wtf-debian-keyring.gpg
here.
--include=apt,wtf-debian-keyring,debian-ports-archive-keyring sid
rg/chroots/buildd/unstable/ http://www.freewrt.org/~tg/dp
Thanks, seems it wo
On 03/12/12 15:46, Finn Thain wrote:
On Sun, 2 Dec 2012, Wouter Verhelst wrote:
I have a completely fucked installation on quickstep. The MuckOS won't
do TCP/IP anymore, so I can't download from the Internet.
If this MacOS installation has a TCP stack, then the problem may be the
network in
On Sun, 2 Dec 2012, Wouter Verhelst wrote:
>
> I have a completely fucked installation on quickstep. The MuckOS won't
> do TCP/IP anymore, so I can't download from the Internet.
If this MacOS installation has a TCP stack, then the problem may be the
network interface. It will disappear in the
Wouter Verhelst dixit:
>I have a completely fucked installation on quickstep. The MuckOS won't
[…]
>What this means is I can't reinstall the Linux system, and I can't fix
>the current Linux system either. And I doubt I have any SCSI-capable
>machines anywhere closeby that I can do a hard disk tran
Michael Schmitz dixit:
>> elgar:~# debootstrap --variant=buildd
Add
--keyring=/usr/share/keyrings/wtf-debian-keyring.gpg
here.
>> --include=apt,wtf-debian-keyring,debian-ports-archive-keyring sid
>> rg/chroots/buildd/unstable/ http://www.freewrt.org/~tg/dp
> I'm seeing the same now - ha
On Sat, Dec 01, 2012 at 02:09:58PM +1300, Michael Schmitz wrote:
> Hello Wouter,
>
> >>>Although it would be nice to have a full archive, I fear that we
> >>>won't be capable to keep up when we try to build the whole archive
> >>>of nearly 1 packages now.
> >>
> >>That was a stretch already la
On 2012-12-02 05:54, Michael Schmitz wrote:
Hi,
There seems to be a problem with your archive key:
E: Release signed by unknown key (key id F7E974E9405422DD)
elgar:~# keyid=F7E974E9405422DD ; gpg --keyserver subkeys.pgp.net
--recv-key $keyid ; gpg --armor --expo
$keyid | apt-key add -
gpg: r
Hi,
There seems to be a problem with your archive key:
elgar:~# apt-get update
Hit http://ftp.de.debian.org unstable InRelease
Get:1 http://www.freewrt.org cross InRelease [13.2 kB]
Hit http://ftp.debian-ports.org unstable InRelease
Hit http://ftp.debian-ports.org unreleased InRelease
Hit http:
On 2012-12-01 12:15, Thorsten Glaser wrote:
Maybe you should first update to etch-m68k and from that to unstable
and
[…]
I think it's doable.
Not officially, really; most of our packages are recent enough to
not support upgrading from anything older than squeeze.
I think, debootstrapping a ch
Ingo Jürgensmann dixit:
> Maybe you should first update to etch-m68k and from that to unstable and
[…]
> I think it's doable.
Not officially, really; most of our packages are recent enough to
not support upgrading from anything older than squeeze.
I think, debootstrapping a chroot, moving stuff
On 2012-12-01 02:09, Michael Schmitz wrote:
Honestly - I did try to follow Thorsten's notes on adding his repo
and bootstrapping a chroot, but it failed mysteriously at step one.
Did I mention my base system is still at version sarge?
Maybe you should first update to etch-m68k and from that to
Thorsten,
Honestly - I did try to follow Thorsten's notes on adding his repo and
bootstrapping a chroot, but it failed mysteriously at step one. Did I
mention
my base system is still at version sarge?
Ouch! The kernel’s current enough though? (At least 2.6.34 if vanilla.)
3.5.0-m68k with
Michael Schmitz dixit:
> Honestly - I did try to follow Thorsten's notes on adding his repo and
> bootstrapping a chroot, but it failed mysteriously at step one. Did I mention
> my base system is still at version sarge?
Ouch! The kernel’s current enough though? (At least 2.6.34 if vanilla.)
> E:
Hello Wouter,
Although it would be nice to have a full archive, I fear that we
won't be capable to keep up when we try to build the whole archive
of nearly 1 packages now.
That was a stretch already last time while we were in the running, so
I
don't think it is worth to try.
The buildd
Am 24.11.2012 um 20:14 schrieb Ingo Jürgensmann:
>> I won't be able to handle more than my own buildd and maybe one more.
> Maybe we should create a list in the Wiki to note this kind of information...
> ;)
> Can please someone add it below the m68k namespace? I'm still on a ship with
> limited
On Sat, Nov 24, 2012 at 08:02:05PM +0100, Ingo Jürgensmann wrote:
> What I've spotted short before my vacation is that sbuild now
> supports LVM snapshots when building. Is it a good idea to try that
> out?
Ah, I forgot about that one.
Yes, it's absolutely a good idea to use that. The snapshot fe
On Sat, Nov 24, 2012 at 09:29:52AM +0100, Michael Schmitz wrote:
> > Although it would be nice to have a full archive, I fear that we
> > won't be capable to keep up when we try to build the whole archive
> > of nearly 1 packages now.
>
> That was a stretch already last time while we were in t
Ingo J�rgensmann dixit:
>Am 24.11.2012 um 13:01 schrieb Thorsten Glaser:
>>--debootstrapopts --keyring=/usr/share/keyrings/wtf-debian-keyring.gpg \
[…]
>> somebox$ sudo debootstrap --variant=buildd \
>>--include=apt,wtf-debian-keyring,debian-ports-archive-keyring \
>>sid /target http:
Am 24.11.2012 um 13:01 schrieb Thorsten Glaser:
> somebox$ sudo sh -c 'echo deb http://www.freewrt.org/~tg/dp cross main
> >>/etc/apt/sources.list'
> # note I choose the "cross" repo because it does not contain
> # any packages that would replace your normal debian packages
> #
Ingo Jürgensmann dixit:
> what needs to get built next.
Another nice thing you can do is:
• install mksh
• go to https://www.mirbsd.org/cvs.cgi/contrib/hosted/tg/assockit.ksh
download the latest version of that library
• go to https://www.mirbsd.org/cvs.cgi/contrib/hosted/tg/deb/quinn-ls.sh
Michael Schmitz dixit:
>With the likely exception of Thorsten, none of us here are. While I've run
>autobuilders in the past, I'm certain the procedures have evolved to a
>point where I do pretty much start from scratch.
Yes well, I can’t get my head wrapped around the buildd thing (yet,
mostly b
Thorsten,
> >> keep up with it and manage it somehow to get the stable version as
> >> well built so that we can offer a stable distri to our users instead
>
> Maybe we can do a jessie-m68k like etch-m68k, basically a stabilised
> snapshot of unstable at that time (hand-picked, with edos-debcheck
Jason,
On Sat, Nov 24, 2012 at 10:20:12PM +1100, Jason Duerstock wrote:
> I'm not sure exactly where I can help, but I'd be willing to supply a
> static endpoint for some tunnel(s), and a mail relay if nothing else. I'm
> no package troubleshooting wizard but I'd be willing to look at anything
>
Ingo,
> On 2012-11-24 09:29, Michael Schmitz wrote:
> >I could offer a 060 Falcon but that will be of limited use only.
> >The network
> >card I got for it in the hope to speed up network operation seems
> >to have
> >died, so it will be quite slow. The whole buildd system will have
> >to be set
>
Ingo Jürgensmann dixit:
> Hmm, I remember that we built just a small set of packages from openoffice.org
> source back then, but well... ;-)
Sure, but only into unreleased with manual patches, or with build
profiles once they get actually usable, and only if the source
package supports this (or w
Ingo Jürgensmann dixit:
> To clarify things: with "re-building toolchain" I meant to really re-build the
> toolchain on real iron, although we already have those packages built. At
> least
> libc6, binutils & gcc. I feel a little bit more safe when I know that we run
> safe on real hardware. :-)
Ingo Jürgensmann dixit:
> UGH! KDE is a real pain when building on m68k. Can we limit that to build
> *-dev
> packages only to fulfill B-D?
No, but I am mostly concerned about kde4libs, libgnomeui-dev and so on,
which are not that hard. Anyway, I’ll take care of them, you concentrate
on getting
Hello, I've been monitoring this mailing list for quite some time.
Unfortunately, my A4000 is at a state where I need to either put a ton of
money in it to replace the pieces i'm missing (a monitor or scan converter
mainly). It's a video toaster, but i'm looking to get rid of this machine
to someon
On 2012-11-23 22:34, Thorsten Glaser wrote:
Maybe just build X11 base
Already done, and I’m working on KDE and GNOME indeed,
because they are B-D of too many other packages to count.
UGH! KDE is a real pain when building on m68k. Can we limit that to
build *-dev packages only to fulfill B-D?
On 2012-11-24 09:29, Michael Schmitz wrote:
I could offer a 060 Falcon but that will be of limited use only. The
network
card I got for it in the hope to speed up network operation seems to
have
died, so it will be quite slow. The whole buildd system will have to
be set
up from scratch.
That
On 2012-11-24 13:01, Thorsten Glaser wrote:
That being said, this is what you should do (after gpg-verifying
this message):
somebox$ sudo sh -c 'echo deb http://www.freewrt.org/~tg/dp cross
main >>/etc/apt/sources.list'
# note I choose the "cross" repo because it does not contain
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Dixi quod…
[…]
>somebox$ sudo cowbuilder --create --mirror http://www.freewrt.org/~tg/dp \
[…]
Actually, use http://frozenfish.freewrt.org/~tg/dp throughout this
for now, because www. is my “live copy”, which means there will be
some timeframe betw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA384
Michael Schmitz dixit:
>On Fri, Nov 23, 2012 at 10:23:36PM +0100, Ingo Jürgensmann wrote:
>> From the current point of view, I think it's too early to think of
>> re-inclusion in Debian. Maybe we can manage to follow unstable and
Right, that was m
I'm not sure exactly where I can help, but I'd be willing to supply a
static endpoint for some tunnel(s), and a mail relay if nothing else. I'm
no package troubleshooting wizard but I'd be willing to look at anything
buildd pukes on.
Jason
On Sat, Nov 24, 2012 at 7:29 PM, Michael Schmitz <
schm.
Ingo,
On Fri, Nov 23, 2012 at 10:23:36PM +0100, Ingo Jürgensmann wrote:
> On 2012-11-23 21:27, Ingo Jürgensmann wrote:
>
> I'm answering to myself to make a start... ;-)
>
> >1) Who will run a buildd? 24/7 operation and a good internet
> >connection are required (DSL or similar is quite common n
Ingo Jürgensmann dixit:
> Maybe just build X11 base
Already done, and I’m working on KDE and GNOME indeed,
because they are B-D of too many other packages to count.
> we won't need number crunching packages (don't know the names, but there were
Except as B-D…
> First we need the toolchain back
Ingo Jürgensmann dixit:
> 1) Who will run a buildd? 24/7 operation and a good internet connection are
> required (DSL or similar is quite common nowadays). Do we split tasks between
> host and buildd maintainers?
I might be able to run an ARAnyM buildd; there used to be a few
of them, but I’d lik
39 matches
Mail list logo
