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 make mipsel different to other architectures or from the
> > earlier successful mipsel build?  It's the same petsc.
> petsc may be at the same version, but the environment has changed. 
> It may be a bug in another package (e.g. an rdep) or a bug in petsc
> that was latent until now.
> 
> > > 
> > > Have you checked if it builds fine on a porterbox?
> > I tried but sbuild wouldn't work inside the schroot environment on
> > etler.
> 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 fixed now...

Thanks for that. It's showing a very different build failure now, as if
something is wrong with mpi (openmpi).

I'll follow those schroot instructions and look directly.


Drew

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

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 build machine. Please try the mipsel build again.

Why? It has failed twice already.


What would make mipsel different to other architectures or from the
earlier successful mipsel build?  It's the same petsc.


petsc may be at the same version, but the environment has changed. It may be a 
bug in another package (e.g. an rdep) or a bug in petsc that was latent until now.



Have you checked if it builds fine on a porterbox?


I tried but sbuild wouldn't work inside the schroot environment on
etler.


Did you read the MOTD? See https://dsa.debian.org/doc/schroot/

Anyway given the build queue is currently empty on mipsel, I've given it back. 
Let's see if the problem is fixed now...


Emilio

--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


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 in doubt, don't hesitate to ask me or to the debian-mentors list :)
> 
> $ dcut -k 92978A6E195E4921825F7FF0F34F09744E9F5DD9 ftp-master dm --uid "James 
> Clarke" --allow polyml
> Uploading commands file to ftp.upload.debian.org (incoming: /pub/UploadQueue/)
> Picking DM James Clarke  with fingerprint 
> 8F58342BEABE1EF4379551FBB193770C186A1C7D
> 
> You need a passphrase to unlock the secret key for
> user: "Gianfranco Costamagna "
> 4096-bit RSA key, ID 4E9F5DD9, created 2014-09-14
> 
> Uploading locutus-1457862406.dak-commands to ftp-master
> 
> now you should be able to perform the uploads by yourself :)

Thanks, and thank you once again for all your help! I’m sure you’ll still see 
me around the place, even if you won’t get any more of my emails asking you to 
do things for me :)

James



signature.asc
Description: Message signed with OpenPGP using GPGMail
-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

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.
> Why? It has failed twice already. 

What would make mipsel different to other architectures or from the
earlier successful mipsel build?  It's the same petsc.


> Have you checked if it builds fine on a porterbox?
> 


I tried but sbuild wouldn't work inside the schroot environment on
etler.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

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 times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


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 day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


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 times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


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 britney hint files. Those comments
were not originally meant to be machine readable, so if the
reason for removing your package seems to be nonsense, it is
probably the reporting script that got confused. Please check the
actual hints file before you complain about meaningless removals.

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


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?

Emilio

--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


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
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers


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 a warning not an error.  In any case, I've uploaded
v3.6.3 and invoked plm rather than orte.  Hopefully once the new
version is pushed through, the mipsel build will clear.

Drew

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

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 92978A6E195E4921825F7FF0F34F09744E9F5DD9 ftp-master dm --uid "James 
Clarke" --allow polyml
Uploading commands file to ftp.upload.debian.org (incoming: /pub/UploadQueue/)
Picking DM James Clarke  with fingerprint 
8F58342BEABE1EF4379551FBB193770C186A1C7D

You need a passphrase to unlock the secret key for
user: "Gianfranco Costamagna "
4096-bit RSA key, ID 4E9F5DD9, created 2014-09-14

Uploading locutus-1457862406.dak-commands to ftp-master

now you should be able to perform the uploads by yourself :)

cheers!

Gianfranco

-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers