On Mon, 14 Mar 2016 09:39:04 +0800 Drew Parsons
wrote:
> > Did you read the MOTD? See https://dsa.debian.org/doc/schroot/
>
> I missed that. I'll add it to my bookmarks.
>
>
> > Anyway given the build queue is currently empty on mipsel, I've
given
> > it back.Â
> > Let's see if the problem is
On Sun, 2016-03-13 at 19:59 +0100, Emilio Pozuelo Monfort wrote:
> [Adding debian-wb-team back to Cc]
>
> On 13/03/16 17:56, Drew Parsons wrote:
> >
> > On Sun, 2016-03-13 at 17:35 +0100, Emilio Pozuelo Monfort wrote:
> > >
> > > On 13/03/16 16:34, Drew Parsons wrote:
> > > >
> > What would mak
[Adding debian-wb-team back to Cc]
On 13/03/16 17:56, Drew Parsons wrote:
On Sun, 2016-03-13 at 17:35 +0100, Emilio Pozuelo Monfort wrote:
On 13/03/16 16:34, Drew Parsons wrote:
Source: petsc
Followup-For: Bug #816101
The petsc build failure on mipsel appears to be a transient problem
on
the
On Sun, 2016-03-13 at 17:35 +0100, Emilio Pozuelo Monfort wrote:
> On 13/03/16 16:34, Drew Parsons wrote:
> >
> > Source: petsc
> > Followup-For: Bug #816101
> >
> > The petsc build failure on mipsel appears to be a transient problem
> > on
> > the build machine. Please try the mipsel build again
On 13/03/16 16:34, Drew Parsons wrote:
Source: petsc
Followup-For: Bug #816101
The petsc build failure on mipsel appears to be a transient problem on
the build machine. Please try the mipsel build again.
Why? It has failed twice already. Have you checked if it builds fine on a
porterbox?
Emi
Source: petsc
Followup-For: Bug #816101
The petsc build failure on mipsel appears to be a transient problem on
the build machine. Please try the mipsel build again.
gb petsc_3.6.2.dfsg1-3+b3 . mipsel
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
