Bug#816101: petsc: FTBFS on mipsel - try rebuild again

2016-03-13 Thread Drew Parsons
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

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

2016-03-13 Thread Emilio Pozuelo Monfort
[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

Re: Poly/ML 5.6-3

2016-03-13 Thread James Clarke
Hi, > On 13 Mar 2016, at 09:48, Gianfranco Costamagna > wrote: >> Added in >> http://anonscm.debian.org/cgit/keyring/keyring.git/commit/?id=bb8f943a3b54332b65cf4a64644e9e8b57bdbdcf. > > ok :) > > please do source-only uploads, or use pbuilder/sbuild to generate the > binaries. > If you are i

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

2016-03-13 Thread Drew Parsons
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

apertium-fra-cat 1.1.0~r64309-1 MIGRATED to testing

2016-03-13 Thread Debian testing watch
FYI: The status of the apertium-fra-cat source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.1.0~r64309-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple tim

apertium-swe 0.5.0~r66062-1 MIGRATED to testing

2016-03-13 Thread Debian testing watch
FYI: The status of the apertium-swe source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.5.0~r66062-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a

apertium-nno-nob 1.1.0~r66076-1 MIGRATED to testing

2016-03-13 Thread Debian testing watch
FYI: The status of the apertium-nno-nob source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 1.1.0~r66076-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple tim

apertium-fr-ca REMOVED from testing

2016-03-13 Thread Debian testing watch
FYI: The status of the apertium-fr-ca source package in Debian's testing distribution has changed. Previous version: 1.0.3~r61322-1 Current version: (not in testing) Hint: (no removal hint found) The script that generates this mail tries to extract removal reasons from comments in the brit

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

2016-03-13 Thread Emilio Pozuelo Monfort
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

Bug#816101: petsc: FTBFS on mipsel - try rebuild again

2016-03-13 Thread Drew Parsons
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

Bug#816101: petsc: FTBFS on mipsel - timeout while running the test suite

2016-03-13 Thread Drew Parsons
As far as I can tell this build failure is just some ephemeral problem on the build machine.  The same code built before, and builds now on mips and other architectures. Trigger a rebuild, maybe it will work now. The orte/plm warning is a red herring.  All architectures have the same problem. It's

Re: Poly/ML 5.6-3

2016-03-13 Thread Gianfranco Costamagna
Hi, >Added in >http://anonscm.debian.org/cgit/keyring/keyring.git/commit/?id=bb8f943a3b54332b65cf4a64644e9e8b57bdbdcf. ok :) please do source-only uploads, or use pbuilder/sbuild to generate the binaries. If you are in doubt, don't hesitate to ask me or to the debian-mentors list :) $ dcut -k