Hi,
On Sun, Nov 19, 2000 at 11:23:18PM -0800, Tor Slettnes wrote:
> The problem is specifically `non-us' packages. I would if I could,
> but I cannot and so I will not.
> If I were to compile and upload ssh, I would be subject to the same
> legal status as one who has obtain nuclear secrets and s
Based on the name, I assumed you were in Scandinavia or something;
from whois, though, it looks like you're in California. That means
you're just uninformed :-)
First of all, it has been several years since crypto was restricted as
weaponry; it changed to be restricted as crypto.
Second, in Janu
>i was just today confirmed that there were just 2 packages
>uploaden in last weeks/months (don't know for sure but something like
>this was told me this evening).
There were 178 updated ARM packages in 2.2r1. For the stable distribution,
pretty much everything quinn-diff lists as not built is
On Mon, 20 Nov 2000, Philip Blundell wrote:
> >For that matter, is the arm port primarily a netwinder port, or more
> >broad?
>
> It's more broad. All ARM machines should be binary-compatible with the
> Debian
> packages, at least within reason (no big-endian, no ARM2).
Sure seems to work, I
> "Othmar" == Othmar Pasteka <[EMAIL PROTECTED]> writes:
Othmar> i thought there were quite a few careing about the
Othmar> port. anyway, i and one other debian developer think it's
Othmar> time to do something.
The problem is specifically `non-us' packages. I would if I could,
>For that matter, is the arm port primarily a netwinder port, or more
>broad?
It's more broad. All ARM machines should be binary-compatible with the Debian
packages, at least within reason (no big-endian, no ARM2).
p.
Hi,
On Mon, Nov 20, 2000 at 02:21:24AM +, Chris Rutter wrote:
> The ARM port is very much maintained in spirit; I currently correspond
> to <[EMAIL PROTECTED]>, and I very much intend, as soon as time
> permits, to push issues forward. There's a collection of buildds, and
> a prototypic syste
On Sun, 19 Nov 2000, Othmar Pasteka wrote:
> i just had to discover that somehow the arm port isn't
> maintained. i got the impression that someone set up an buildd
> and etc. pp. so, what is the actual status? i am a bit confused
> right now.
The ARM port is very much maintained in spirit; I cur
> # dpkg --install *.deb
Ahh, but that's the tricky part: no /var/lib/dpkg, only about 2.5M of
free space on the device for that matter... much of what is there is a
cramfs, and so readonly. (This is probably better discussed on
[EMAIL PROTECTED], but it didn't get much attention last time I
bro
[[ sorry if people get this mail twice, becausei might have
messed up the Cc: header i resend this post to the list]]
hi,
On Sun, Nov 19, 2000 at 06:14:22PM -0500, Adam C Powell IV wrote:
> As there is no ssh in main/anything. The problem is the non-us packages are
> woefully out-of-date. :-(
y
> "Mark" == Mark W Eichin <[EMAIL PROTECTED]> writes:
Mark> For that matter, is the arm port primarily a netwinder port,
Mark> or more broad? I've been building stuff from debian for the
Mark> iPAQ PDA (200mhz SA1100) mostly to put in the NFS-mounted
Mark> /usr/local, and in f
For that matter, is the arm port primarily a netwinder port, or more
broad? I've been building stuff from debian for the iPAQ PDA (200mhz
SA1100) mostly to put in the NFS-mounted /usr/local, and in fact doing
apt-get source foo
cd foo-version
./configure --prefix=/usr/local
Othmar Pasteka wrote:
> one of the things which also points to a more or less
> unmaintained port is that there is no ssh in main/arm :(.
As there is no ssh in main/anything. The problem is the non-us packages are
woefully out-of-date. :-(
There are a number of problems with the ARM port (e.g.
hi,
i just had to discover that somehow the arm port isn't
maintained. i got the impression that someone set up an buildd
and etc. pp. so, what is the actual status? i am a bit confused
right now.
one of the things which also points to a more or less
unmaintained port is that there is no ssh in ma
14 matches
Mail list logo
