* Rafael Laboissiere <[EMAIL PROTECTED]> [2005-03-28 20:33]:
> I am building right now the octave2.1_2.1.68 package, but will upload it to
> unstable only after the arm buildd will have caught up with 2.1.67.
I uploaded 2.1.68-1 to experimental.
In our home page
* Lennart Sorensen <[EMAIL PROTECTED]> [2005-03-08 10:55]:
> On Tue, Mar 08, 2005 at 02:45:55PM +0100, Rafael Laboissiere wrote:
> > Where can you see this?
>
> Go to buildd.debian.org, Click on "examine the build log database",
> select arm, and type octave2.
* Lennart Sorensen <[EMAIL PROTECTED]> [2005-03-07 10:11]:
> Well my arm built 2.1.64 succesfully, but it took a very long time.
It does not surprise me.
> I see in the buildd.debian.org status that arm did build 2.1.65-1,
Where can you see this?
> although I suspect no one has accepted it yet
* Lennart Sorensen <[EMAIL PROTECTED]> [2005-03-04 17:34]:
> I am currently trying a manual build to see if it builds or not on arm.
> So far it has taken about 7 hours, and it's still going (on a 400MHz
> PXA255), so it may simply have timed out on the arm buildd. G++ has a
> tendancy to take a
* Rafael Laboissiere <[EMAIL PROTECTED]> [2005-02-28 23:31]:
> The latest octave2.1 package reached unstable on 25 Feb 2005 08:32:12 -0500.
> All the arches, besides arm, have catched up. Is there a way to know what
> happened with the arm buildd?
We got no answer from the debian
The latest octave2.1 package reached unstable on 25 Feb 2005 08:32:12 -0500.
All the arches, besides arm, have catched up. Is there a way to know what
happened with the arm buildd?
--
Rafael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL
Dear arm and sparc folks,
I sent the message below to debian-admin over one week ago, but it
apparently went into a black hole.
Can someone help me with this?
TIA
Rafael
- Forwarded message from Rafael Laboissiere <[EMAIL PROTECTED]> -
From: Rafael Laboissiere <[EMAIL
7 matches
Mail list logo
