* 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.1 as package name, and see list of bu
On Tue, Mar 08, 2005 at 05:45:23PM +0100, Rafael Laboissiere wrote:
> What do you mean by "no one has accepted it"?
As far as I understand the build system, someone has to sign the build
log before the package is accepted into the archives. Until someone
(not sure if that is a buildd maintainer
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.1 as package name, and see list of build
attemps. Maybe-successful almost always means success. You can c
* 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
On Sat, Mar 05, 2005 at 12:09:51AM +0100, Rafael Laboissiere wrote:
> Thanks a lot. A new upstream version of Octave was released today (2.1.67)
> and I already uploaded the corresponding Debian package. It may be that by
> Monday we will also here news from the arm build daemon...
Well my arm b
* 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
On Thu, Mar 03, 2005 at 10:42:31PM +0100, Rafael Laboissiere wrote:
> * 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
> > h
* 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-arm crew to my
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
9 matches
Mail list logo
