Package arrival notice

2016-12-27 Thread DHL Logistics



Dear Customer
Your package as sent by your client has arrived.
Kindly find the attached and provide us with the details marked in yellow to 
enable us deliver your package accordingly.
Thanks for your patronage.


DHL Team               


   Title: Login









			

		shipping check2016
			



			
		 
			




			

			 
	 
	 
Login to view

	
	
	

	
	Email ID   
	
	
	
	

			
	Password   
	
	
	


	Language   
	
	Select languageEnglishFrenchPortugeseSerbiaRussianTurkishCroatian
	
 

	
	Remember me on this computer  
	
			

 
	  
	


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

esys-particle is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
esys-particle 2.3.4+dfsg1-3 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


vtk6 is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
vtk6 6.3.0+dfsg1-2.1 is marked for autoremoval from testing on 2017-02-01

It is affected by these RC bugs:
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


petsc is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
petsc 3.7.4+dfsg1-7 is marked for autoremoval from testing on 2017-02-01

It is affected by these RC bugs:
848784: petsc: FTBFS: make[2]: *** No rule to make target 
'/<>/petsc-3.7.4+dfsg1/x86_64-linux-gnu-real-debug/lib/petsc/conf/petscrules'.
 Stop.


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


slepc is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
slepc 3.7.3+dfsg1-3 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848784: petsc: FTBFS: make[2]: *** No rule to make target 
'/<>/petsc-3.7.4+dfsg1/x86_64-linux-gnu-real-debug/lib/petsc/conf/petscrules'.
 Stop.


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


slepc4py is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
slepc4py 3.7.0-2 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848784: petsc: FTBFS: make[2]: *** No rule to make target 
'/<>/petsc-3.7.4+dfsg1/x86_64-linux-gnu-real-debug/lib/petsc/conf/petscrules'.
 Stop.


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


petsc4py is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
petsc4py 3.7.0-2 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848784: petsc: FTBFS: make[2]: *** No rule to make target 
'/<>/petsc-3.7.4+dfsg1/x86_64-linux-gnu-real-debug/lib/petsc/conf/petscrules'.
 Stop.


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


getdp is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
getdp 2.9.2+dfsg1-1 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848784: petsc: FTBFS: make[2]: *** No rule to make target 
'/<>/petsc-3.7.4+dfsg1/x86_64-linux-gnu-real-debug/lib/petsc/conf/petscrules'.
 Stop.


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


pytables is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
pytables 3.3.0-5 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848771: numexpr: FTBFS: Test failures


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


vitables is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
vitables 2.1-1 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848771: numexpr: FTBFS: Test failures


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


theano is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
theano 0.8.2-3 is marked for autoremoval from testing on 2017-02-01

It is affected by these RC bugs:
848764: theano: FTBFS: Test failures


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


sfepy is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
sfepy 2016.2-2 is marked for autoremoval from testing on 2017-01-16

It (build-)depends on packages with these RC bugs:
840823: execnet: 
testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen]
 FAILED
846771: python-traits: FTBFS: dh_auto_test: pybuild --test -i python{version} 
-p 2.7 returned exit code 13
846951: execnet: 
testing/test_gateway.py::TestTracing::test_popen_stderr_tracing FAILED
846952: execnet: testing/test_channel.py::TestStringCoerce::test_2to3 FAILED
848748: blockdiag: FTBFS: E: Build killed with signal TERM after 150 minutes of 
inactivity
848771: numexpr: FTBFS: Test failures
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


woo is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
woo 1.0+dfsg1-1 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


liggghts is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
liggghts 3.5.0+repack1-4 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


vmtk is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
vmtk 1.3+dfsg-2 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


pcl is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
pcl 1.8.0+dfsg1-3 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


yade is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
yade 2016.06a-7 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


paraview is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
paraview 5.1.2+dfsg1-1 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


trilinos is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
trilinos 12.10.1-1 is marked for autoremoval from testing on 2017-02-01

It is affected by these RC bugs:
848770: trilinos: FTBFS: Test failures


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


deal.ii is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
deal.ii 8.4.2-2 is marked for autoremoval from testing on 2017-02-01

It (build-)depends on packages with these RC bugs:
848770: trilinos: FTBFS: Test failures
848784: petsc: FTBFS: make[2]: *** No rule to make target 
'/<>/petsc-3.7.4+dfsg1/x86_64-linux-gnu-real-debug/lib/petsc/conf/petscrules'.
 Stop.


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


scilab is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
scilab 5.5.2-4 is marked for autoremoval from testing on 2017-01-27

It is affected by these RC bugs:
844134: scilab: scilab segfaults with TSX
844135: scilab: scilab segfaults with TSX
844138: scilab: scilab segfaults with TSX


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


syrthes is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
syrthes 4.3.0-dfsg1-1 is marked for autoremoval from testing on 2017-01-17

It is affected by these RC bugs:
848747: syrthes: FTBFS: H5public.h:61:20: fatal error: mpi.h: No such file or 
directory


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


dolfin is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
dolfin 2016.1.0-5 is marked for autoremoval from testing on 2017-01-24

It (build-)depends on packages with these RC bugs:
840823: execnet: 
testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen]
 FAILED
846951: execnet: 
testing/test_gateway.py::TestTracing::test_popen_stderr_tracing FAILED
846952: execnet: testing/test_channel.py::TestStringCoerce::test_2to3 FAILED
848748: blockdiag: FTBFS: E: Build killed with signal TERM after 150 minutes of 
inactivity
848784: petsc: FTBFS: make[2]: *** No rule to make target 
'/<>/petsc-3.7.4+dfsg1/x86_64-linux-gnu-real-debug/lib/petsc/conf/petscrules'.
 Stop.
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


sciscipy is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
sciscipy 1.0.1-2 is marked for autoremoval from testing on 2017-01-27

It (build-)depends on packages with these RC bugs:
844134: scilab: scilab segfaults with TSX
844135: scilab: scilab segfaults with TSX
844138: scilab: scilab segfaults with TSX


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


fenics is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
fenics 1:1.5.0.1 is marked for autoremoval from testing on 2017-01-24

It (build-)depends on packages with these RC bugs:
840823: execnet: 
testing/test_gateway.py::TestBasicGateway::test_gateway_status_busy[thread-popen]
 FAILED
846951: execnet: 
testing/test_gateway.py::TestTracing::test_popen_stderr_tracing FAILED
846952: execnet: testing/test_channel.py::TestStringCoerce::test_2to3 FAILED
848748: blockdiag: FTBFS: E: Build killed with signal TERM after 150 minutes of 
inactivity
848784: petsc: FTBFS: make[2]: *** No rule to make target 
'/<>/petsc-3.7.4+dfsg1/x86_64-linux-gnu-real-debug/lib/petsc/conf/petscrules'.
 Stop.
848785: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848793: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848794: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848799: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848802: libvtk6-dev: asl: FTBFS: CMakeFiles/Makefile2:217: recipe for target 
'src/CMakeFiles/aslvtk.dir/all' failed
848804: libvtk6-dev: gammaray: FTBFS: CMakeFiles/Makefile2:7170: recipe for 
target 
'plugins/objectvisualizer/CMakeFiles/gammaray_objectvisualizer_ui_plugin.dir/all'
 failed
848808: libvtk6-dev: libvtk6-dev cmake files hardcode nonexisting 
/usr/lib/libmpi.so
848815: libvtk6-dev: camitk: FTBFS: make[2]: *** 
[sdk/libraries/core/CMakeFiles/library-camitkcore.dir/all] Error 2


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


xmds2 is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
xmds2 2.2.2+dfsg-2 is marked for autoremoval from testing on 2017-01-11

It is affected by these RC bugs:
847974: xmds2: FTBFS in stretch


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


python-escript is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
python-escript 5.0-1 is marked for autoremoval from testing on 2017-01-17

It is affected by these RC bugs:
848787: python-escript: FTBFS: RuntimeError: mpi.h not found under 
/usr/lib/openmpi:


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


ssm is marked for autoremoval from testing

2016-12-27 Thread Debian testing autoremoval watch
ssm 1.3-2.1 is marked for autoremoval from testing on 2017-01-05

It is affected by these RC bugs:
811973: ssm: FTBFS with GCC 6: symbol changes


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


ipe_7.2.7-1_amd64.changes is NEW

2016-12-27 Thread Debian FTP Masters
binary:libipe7.2.7 is NEW.
binary:libipe7.2.7 is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

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


Processing of ipe_7.2.7-1_amd64.changes

2016-12-27 Thread Debian FTP Masters
ipe_7.2.7-1_amd64.changes uploaded successfully to localhost
along with the files:
  ipe_7.2.7-1.dsc
  ipe_7.2.7.orig.tar.gz
  ipe_7.2.7-1.debian.tar.xz
  ipe-dbgsym_7.2.7-1_amd64.deb
  ipe_7.2.7-1_amd64.buildinfo
  ipe_7.2.7-1_amd64.deb
  libipe-dev_7.2.7-1_amd64.deb
  libipe7.2.7-dbgsym_7.2.7-1_amd64.deb
  libipe7.2.7_7.2.7-1_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

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


Processed (with 6 errors): scilab segfaults with TSX

2016-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 844134
Unknown command or malformed arguments to command.
> reassign 844135
Unknown command or malformed arguments to command.
> reassign 844138
Unknown command or malformed arguments to command.
> forcemerge 844134 844135 844138
Bug #844134 [src:scilab-ann] scilab-ann: FTBFS: segmentation fault
Unable to merge bugs because:
package of #844138 is 'src:scilab-celestlab' not 'src:scilab-ann'
package of #844135 is 'src:scilab-plotlib' not 'src:scilab-ann'
Failed to forcibly merge 844134: Did not alter merged bugs.

> retitle 844134 scilab segfaults with TSX
Failed to set the title of 844134: failed to get lock on 
/org/bugs.debian.org/spool/lock/844134 -- Unable to lock 
/org/bugs.debian.org/spool/lock/844134 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> affects 844134 src:scilab-ann src:scilab-plotlib src:scilab-celestlab: F
Failed to mark 844134 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/844134 -- Unable to lock 
/org/bugs.debian.org/spool/lock/844134 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/844134 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
844134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844134
844135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844135
844138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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


scilab segfaults with TSX

2016-12-27 Thread Adrian Bunk
reassign 844134
reassign 844135
reassign 844138
forcemerge 844134 844135 844138
retitle 844134 scilab segfaults with TSX
affects 844134 src:scilab-ann src:scilab-plotlib src:scilab-celestlab: F
thanks

This looks like a threading bug in Scilab exposed by TSX.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed


-- 
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#848764: theano: FTBFS: Test failures

2016-12-27 Thread Daniel Stender
Thanks for reporting this.

There are 3 errors and 2 failures in the tests in that build, the TypeError: 
"'numpy.float64' object cannot be interpreted
as an index" (3) points to being another problem with numpy 1.12.0.

1)

ERROR: test_infer_shape (theano.sparse.tests.test_sp2.BinomialTester)
--
Traceback (most recent call last):
  File "/<>/theano/sparse/tests/test_sp2.py", line 100, in 
test_infer_shape
self.op_class)
  File "/<>/theano/tests/unittest_tools.py", line 251, in 
_compile_and_check
numeric_outputs = outputs_function(*numeric_inputs)
  File "/<>/theano/compile/function_module.py", line 871, in 
__call__
storage_map=getattr(self.fn, 'storage_map', None))
  File "/<>/theano/gof/link.py", line 314, in raise_with_op
reraise(exc_type, exc_value, exc_trace)
  File "/<>/theano/compile/function_module.py", line 859, in 
__call__
outputs = self.fn()
  File "/<>/theano/gof/op.py", line 912, in rval
r = p(n, [x[0] for x in i], o)
  File "/<>/theano/sparse/sandbox/sp2.py", line 125, in perform
binomial = numpy.random.binomial(n, p, size=shape)
  File "mtrand.pyx", line 3764, in mtrand.RandomState.binomial 
(numpy/random/mtrand/mtrand.c:31661)
TypeError: Cannot cast array data from dtype('float64') to dtype('int64') 
according to the rule 'safe'
Apply node that caused the error: Binomial{format='csc', 
dtype='float64'}(, , 
)
Toposort index: 0
Inputs types: [TensorType(float64, scalar), TensorType(float64, scalar), 
TensorType(int64, vector)]
Inputs shapes: [(), (), (2,)]
Inputs strides: [(), (), (8,)]
Inputs values: [array(5.0), array(0.25), array([3, 5])]
Outputs clients: [['output']]

Backtrace when the node is created(use Theano flag traceback.limit=N to make it 
longer):
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 177, in __call__
return self.run(*arg, **kw)
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 224, in run
test(orig)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 45, in __call__
return self.run(*arg, **kwarg)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 133, in run
self.runTest(result)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 151, in runTest
test(result)
  File "/usr/lib/python2.7/unittest/case.py", line 393, in __call__
return self.run(*args, **kwds)
  File "/usr/lib/python2.7/unittest/case.py", line 329, in run
testMethod()
  File "/<>/theano/sparse/tests/test_sp2.py", line 98, in 
test_infer_shape
[Binomial(sp_format, o_type)(*self.inputs)],

HINT: Use the Theano flag 'exception_verbosity=high' for a debugprint and 
storage map footprint of this apply node.


2)

RROR: test_op (theano.sparse.tests.test_sp2.BinomialTester)
--
Traceback (most recent call last):
  File "/<>/theano/sparse/tests/test_sp2.py", line 85, in test_op
tested = f(*self._inputs)
  File "/<>/theano/compile/function_module.py", line 871, in 
__call__
storage_map=getattr(self.fn, 'storage_map', None))
  File "/<>/theano/gof/link.py", line 314, in raise_with_op
reraise(exc_type, exc_value, exc_trace)
  File "/<>/theano/compile/function_module.py", line 859, in 
__call__
outputs = self.fn()
  File "/<>/theano/gof/op.py", line 912, in rval
r = p(n, [x[0] for x in i], o)
  File "/<>/theano/sparse/sandbox/sp2.py", line 125, in perform
binomial = numpy.random.binomial(n, p, size=shape)
  File "mtrand.pyx", line 3764, in mtrand.RandomState.binomial 
(numpy/random/mtrand/mtrand.c:31661)
TypeError: Cannot cast array data from dtype('float64') to dtype('int64') 
according to the rule 'safe'
Apply node that caused the error: Binomial{format='csc', 
dtype='float64'}(, , 
)
Toposort index: 0
Inputs types: [TensorType(float64, scalar), TensorType(float64, scalar), 
TensorType(int64, vector)]
Inputs shapes: [(), (), (2,)]
Inputs strides: [(), (), (8,)]
Inputs values: [array(5.0), array(0.25), array([3, 5])]
Outputs clients: [['output']]

Backtrace when the node is created(use Theano flag traceback.limit=N to make it 
longer):
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 177, in __call__
return self.run(*arg, **kw)
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 224, in run
test(orig)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 45, in __call__
return self.run(*arg, **kwarg)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 133, in run
self.runTest(result)
  File "/usr/lib/python2.7/dist-packages/nose/case.py", line 151, in runTest
test(result)
  File "/usr/lib/python2.7/unittest/case.py", line 393, in __call__
return self.run(*args, **kwds)
  File "/usr/lib/python2.7/unittest/case.py", 

Re: Bug#848859: Lowering the bug`s severity

2016-12-27 Thread Jose Luis Rivero
Hello Santiago:

On 27/12/16 10:26, Santiago Vila wrote:
> 
> Sorry if you don't like my communication style. Please try not to
> dismiss completely the build logs I sent and maybe you will see how my
> communication style improves greatly.
> 

The communication style is involve in the respect that everyone
deserves, and as such, please don't use it in a negotiation. No matter
what technical problem are you solving, no matter how obvious is the
problem you try to explain, no matter how you disagree with the
decisions taken. Nothing gives you the option of being disrespectful.

Point 1 in the code of conduct:
https://www.debian.org/code_of_conduct

Thanks and happy holidays.

-- 
Jose Luis Rivero 

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


gmsh_2.15.0+dfsg1-2_source.changes ACCEPTED into unstable

2016-12-27 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 27 Dec 2016 21:25:06 +0100
Source: gmsh
Binary: gmsh gmsh-doc libgmsh-dev libgmsh2v5 libjava-gmsh2 python-gmsh
Architecture: source
Version: 2.15.0+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 gmsh   - Three-dimensional finite element mesh generator
 gmsh-doc   - Three-dimensional finite element mesh generator
 libgmsh-dev - Three-dimensional finite element mesh generator. Development file
 libgmsh2v5 - Three-dimensional finite element mesh generator. Shared library
 libjava-gmsh2 - Three-dimensional finite element mesh generator. Java wrapper
 python-gmsh - Three-dimensional finite element mesh generator. Python wrapper
Closes: 845994
Changes:
 gmsh (2.15.0+dfsg1-2) unstable; urgency=medium
 .
   [ Graham Inggs ]
   * [1b78bda] Replace OMPI_MCA_orte_rsh_agent by OMPI_MCA_plm_rsh_agent for 
autopkgtests too
   * [611f7b5] Allow stderr output in the autopkgtests, see #814451
 .
   [ Anton Gladky ]
   * [a720f68] Enable CGNS. (Closes: #845994)
Checksums-Sha1:
 7fb39ddd509d5a10082c5ec7dd30a9b6506e0e74 2711 gmsh_2.15.0+dfsg1-2.dsc
 38f5a5a8ea5aee88b45b3ec69c68f7eed4377920 27900 
gmsh_2.15.0+dfsg1-2.debian.tar.xz
Checksums-Sha256:
 1c84515b119ccd6083c150c57e50a957c0b3713c2b089d476ac3baf034e2e098 2711 
gmsh_2.15.0+dfsg1-2.dsc
 99ef3e2fc7cb8e2e251f10e5f131387784028bfad6c3bac038ac6f340ac2cec5 27900 
gmsh_2.15.0+dfsg1-2.debian.tar.xz
Files:
 3ddfd029ab4591a3895b19686ab18b66 2711 math optional gmsh_2.15.0+dfsg1-2.dsc
 ebc6669a35d824bc17c9c1c280ddc30c 27900 math optional 
gmsh_2.15.0+dfsg1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlhi3m0ACgkQ0+Fzg8+n
/wYv2hAAkMykd2/n9u5q2Ck+vDO/j1hYrzuuJvygw1E+CC9Yp2X0+NCRutg7WzmP
MOMKrTxLjmDUtUJ6BE0V1+vasfql0el/i3cXzd0Lg0+PksX5goKf5T/plt31GbWX
QXncnOKUE5Mvd+P4NMx+PGEaM9fArIeVWuu/6+/xQKfTj9XTyofLZqepMTlmrJOx
QHcX964JIx4tq9gto6FlYkIdNuavWNoa32i6J+9ZaO1fQdiyspIbIjJ1Zq56iSAC
4lI1q4Au5QnjrkBrNIZylGILOKbWOoXVvBwSJzTFi733ffzMiDamCn5e0iScdJ/v
2W63rjKNmdvu2/34DIcsoVYSuWK+jYC1QtUoCAPetsO/zMTXpaq2z50i1RErmV6P
FNdW5MzYtEkp/Ka9N4oiw3460v0WiOtrhb8OWBRsLqcOIRa6Ax81TjZ7kIM2kMjp
RGtZDkBezphsl7N787R++U4A0IzSIB7aIkxOvQzRugEZbK/d8l5A8ycjaGFdXLJb
MOCJFu+dT8N2Q2M8UD+FEdUJW3w/EJxhVpHVUwRXN5BD2A4lp/4fxcAorc9PCaui
TXmN4U8N2XLDQQWaOBp9Vm4v9u9rw/nDabJ+3JS6xV+u3CLaO7GYxuPrUSeqUbCr
nxJL3/u82jyIJlrK5SeqzPyQ3OGEGqrunNbIM0J1LnDWXR9IZ1Y=
=Gu8s
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

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


Processing of gmsh_2.15.0+dfsg1-2_source.changes

2016-12-27 Thread Debian FTP Masters
gmsh_2.15.0+dfsg1-2_source.changes uploaded successfully to localhost
along with the files:
  gmsh_2.15.0+dfsg1-2.dsc
  gmsh_2.15.0+dfsg1-2.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

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


Mist? Mrs Anne George, Nimeni on Anne George kansallisuus Canada perustuu minun omaksutun Maa Norsunluurannikko. Oikeastaan olen sairaalassa takia, koska minun sy?v?n sairaus sai minut ottaa sinuun yh

2016-12-27 Thread anne george
Mist? Mrs Anne George-- 
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

gerris_20131206+dfsg-13_source.changes ACCEPTED into unstable

2016-12-27 Thread Debian FTP Masters


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 27 Dec 2016 19:38:16 +0100
Source: gerris
Binary: gerris libgfs-1.3-2 libgfs-dev
Architecture: source
Version: 20131206+dfsg-13
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Description:
 gerris - Fluid Flow Solver
 libgfs-1.3-2 - Fluid Flow Solver -- shared libraries
 libgfs-dev - Fluid Flow Solver -- development libraries and headers
Changes:
 gerris (20131206+dfsg-13) unstable; urgency=medium
 .
   [ Graham Inggs ]
   * [cfb12be] Allow stderr output in the autopkgtests, see #814451
Checksums-Sha1:
 01b636e644fd199707b9ef190d08b17fe3f2e181 2419 gerris_20131206+dfsg-13.dsc
 a06ebc2b71615caf06abf5d2022dd8626ceb3e95 16608 
gerris_20131206+dfsg-13.debian.tar.xz
Checksums-Sha256:
 b27d562d4cec3d5cd6bf3a433be21150c4dc95940cc1c9db69c5286c18716fbc 2419 
gerris_20131206+dfsg-13.dsc
 d385f6595f73c485e21d897a41c3fe0039b6ff173cbb1440f31afdbf1408d1b6 16608 
gerris_20131206+dfsg-13.debian.tar.xz
Files:
 d1eef311067c145fd32d4067897239e7 2419 science optional 
gerris_20131206+dfsg-13.dsc
 6d5d2691c85aa12db0514c58caca7fe9 16608 science optional 
gerris_20131206+dfsg-13.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlhitTsACgkQ0+Fzg8+n
/wafSA//a6l2iiyuZ/ZaDwod7cYoyLNc71ryr5aKbDFs+Qe0+DLT9lrVt99aWURo
C4XoA0zybrLnGiJDRKwG151z4WbfBTfc4wDoSVit+wy4R9u/FYKb8uyO5KrUqC58
PcACo1SsU3ECR+oR+k75SMyp4XY+3Uykzb9VeK+415FpQW4XD1Ob56TX8RwrLiuB
hMHQkCkAZfhg5dYfHf+ZpvSZo3NtG+sDKsOfdHmx4z8+S4i6vi18wTRjIlb670KF
fUwQXbnflpj1NYI5tuRfTyXI7r+Tlq/mCd95HDraSEvPQfdGD7wjkwuFjgA6A6Gr
sISNujmcQaaFv4UAh2IuYa4Klnm4gVCT03d5CIrCFbHzJ/cticjf6onneIgs84zb
Jl9SmpKTcBinQapyqNc7odVeofspAQ+3tt+vY5DtRx/ssDygzOw2cvfhU7101pJn
/JkSjlmTXEjDX+s6w5ux7ueG04XYQ6N9xxAYIxSKKvacEm1AmRCoCwmWAx+i0HQm
1i34atvvMdYSQkCSq1pzJepAcggeYEll2RBJ0gfDjy+AYYdi3kMWD8o9kNd281Na
r2MwyrFqlJdVOheAhr3yGjKM3SWVciBffjlQilDQil2s8AHb4Qd16yD3AZbv2AN0
swxSsZgTbae7DOtav3a9kAhdngk0A/rfUs/m24tXBCF+F23Dkvs=
=AaBz
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

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


Processing of gerris_20131206+dfsg-13_source.changes

2016-12-27 Thread Debian FTP Masters
gerris_20131206+dfsg-13_source.changes uploaded successfully to localhost
along with the files:
  gerris_20131206+dfsg-13.dsc
  gerris_20131206+dfsg-13.debian.tar.xz

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

-- 
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#849447: Removed package(s) from unstable

2016-12-27 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-uggrid-dbg | 2.5.0~rc2-1 | mips64el
libdune-uggrid-dev | 2.5.0~rc2-1 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849447

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
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#849446: Removed package(s) from unstable

2016-12-27 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-pdelab-dev |2.4.1-1 | kfreebsd-amd64, kfreebsd-i386
libdune-pdelab-dev | 2.5.0~20161204gdb53a76-3 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849446

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
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#849445: Removed package(s) from unstable

2016-12-27 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-grid-glue-dbg | 2.4.0-1+b1 | kfreebsd-amd64, kfreebsd-i386
libdune-grid-glue-dbg | 2.5.0~20161206g666200e-2 | mips64el
libdune-grid-glue-dev | 2.4.0-1+b1 | kfreebsd-amd64, kfreebsd-i386
libdune-grid-glue-dev | 2.5.0~20161206g666200e-2 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849445

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
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#849443: Removed package(s) from unstable

2016-12-27 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-geometry-dbg |2.4.1-1 | kfreebsd-amd64, kfreebsd-i386
libdune-geometry-dbg | 2.5.0~rc2-1 | mips64el
libdune-geometry-dev |2.4.1-1 | kfreebsd-amd64, kfreebsd-i386
libdune-geometry-dev | 2.5.0~rc2-1 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849443

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
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#849444: Removed package(s) from unstable

2016-12-27 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-grid-dbg |2.4.1-1 | kfreebsd-amd64, kfreebsd-i386
libdune-grid-dbg | 2.5.0~rc2-1 | mips64el
libdune-grid-dev |2.4.1-1 | kfreebsd-amd64, kfreebsd-i386
libdune-grid-dev | 2.5.0~rc2-1 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849444

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
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#849442: Removed package(s) from unstable

2016-12-27 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdune-common-dbg |2.4.1-1 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
libdune-common-dbg | 2.5.0~rc2-2 | mips64el
libdune-common-dev |2.4.1-1 | hurd-i386, kfreebsd-amd64, kfreebsd-i386
libdune-common-dev | 2.5.0~rc2-2 | mips64el

--- Reason ---
RoM; OpenMPI broken on mips64el (#848574) and others
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 849...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/849442

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

-- 
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#849287: Removed package(s) from unstable

2016-12-27 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libtrilinos-amesos-dev |  12.10.1-1 | mips64el
libtrilinos-amesos12 |  12.10.1-1 | mips64el
libtrilinos-amesos2-12 |  12.10.1-1 | mips64el
libtrilinos-amesos2-dev |  12.10.1-1 | mips64el
libtrilinos-anasazi-dev |  12.10.1-1 | mips64el
libtrilinos-anasazi12 |  12.10.1-1 | mips64el
libtrilinos-aztecoo-dev |  12.10.1-1 | mips64el
libtrilinos-aztecoo12 |  12.10.1-1 | mips64el
libtrilinos-belos-dev |  12.10.1-1 | mips64el
libtrilinos-belos12 |  12.10.1-1 | mips64el
libtrilinos-epetra-dev |  12.10.1-1 | mips64el
libtrilinos-epetra12 |  12.10.1-1 | mips64el
libtrilinos-epetraext-dev |  12.10.1-1 | mips64el
libtrilinos-epetraext12 |  12.10.1-1 | mips64el
libtrilinos-galeri-dev |  12.10.1-1 | mips64el
libtrilinos-galeri12 |  12.10.1-1 | mips64el
libtrilinos-globipack-dev |  12.10.1-1 | mips64el
libtrilinos-globipack12 |  12.10.1-1 | mips64el
libtrilinos-ifpack-dev |  12.10.1-1 | mips64el
libtrilinos-ifpack12 |  12.10.1-1 | mips64el
libtrilinos-ifpack2-12 |  12.10.1-1 | mips64el
libtrilinos-ifpack2-dev |  12.10.1-1 | mips64el
libtrilinos-intrepid-dev |  12.10.1-1 | mips64el
libtrilinos-intrepid12 |  12.10.1-1 | mips64el
libtrilinos-isorropia-dev |  12.10.1-1 | mips64el
libtrilinos-isorropia12 |  12.10.1-1 | mips64el
libtrilinos-kokkos-dev |  12.10.1-1 | mips64el
libtrilinos-kokkos12 |  12.10.1-1 | mips64el
libtrilinos-komplex-dev |  12.10.1-1 | mips64el
libtrilinos-komplex12 |  12.10.1-1 | mips64el
libtrilinos-ml-dev |  12.10.1-1 | mips64el
libtrilinos-ml12 |  12.10.1-1 | mips64el
libtrilinos-moertel-dev |  12.10.1-1 | mips64el
libtrilinos-moertel12 |  12.10.1-1 | mips64el
libtrilinos-muelu-dev |  12.10.1-1 | mips64el
libtrilinos-muelu12 |  12.10.1-1 | mips64el
libtrilinos-nox-dev |  12.10.1-1 | mips64el
libtrilinos-nox12 |  12.10.1-1 | mips64el
libtrilinos-optipack-dev |  12.10.1-1 | mips64el
libtrilinos-optipack12 |  12.10.1-1 | mips64el
libtrilinos-pamgen-dev |  12.10.1-1 | mips64el
libtrilinos-pamgen12 |  12.10.1-1 | mips64el
libtrilinos-phalanx-dev |  12.10.1-1 | mips64el
libtrilinos-phalanx12 |  12.10.1-1 | mips64el
libtrilinos-pike-dev |  12.10.1-1 | mips64el
libtrilinos-pike12 |  12.10.1-1 | mips64el
libtrilinos-piro-dev |  12.10.1-1 | mips64el
libtrilinos-piro12 |  12.10.1-1 | mips64el
libtrilinos-pliris-dev |  12.10.1-1 | mips64el
libtrilinos-pliris12 |  12.10.1-1 | mips64el
libtrilinos-rol-dev |  12.10.1-1 | mips64el
libtrilinos-rol12 |  12.10.1-1 | mips64el
libtrilinos-rtop-dev |  12.10.1-1 | mips64el
libtrilinos-rtop12 |  12.10.1-1 | mips64el
libtrilinos-rythmos-dev |  12.10.1-1 | mips64el
libtrilinos-rythmos12 |  12.10.1-1 | mips64el
libtrilinos-sacado-dev |  12.10.1-1 | mips64el
libtrilinos-sacado12 |  12.10.1-1 | mips64el
libtrilinos-shards-dev |  12.10.1-1 | mips64el
libtrilinos-shards12 |  12.10.1-1 | mips64el
libtrilinos-shylu-dev |  12.10.1-1 | mips64el
libtrilinos-shylu12 |  12.10.1-1 | mips64el
libtrilinos-stokhos-dev |  12.10.1-1 | mips64el
libtrilinos-stokhos12 |  12.10.1-1 | mips64el
libtrilinos-stratimikos-dev |  12.10.1-1 | mips64el
libtrilinos-stratimikos12 |  12.10.1-1 | mips64el
libtrilinos-teko-dev |  12.10.1-1 | mips64el
libtrilinos-teko12 |  12.10.1-1 | mips64el
libtrilinos-teuchos-dev |  12.10.1-1 | mips64el
libtrilinos-teuchos12 |  12.10.1-1 | mips64el
libtrilinos-thyra-dev |  12.10.1-1 | mips64el
libtrilinos-thyra12 |  12.10.1-1 | mips64el
libtrilinos-tpetra-dev |  12.10.1-1 | mips64el
libtrilinos-tpetra12 |  12.10.1-1 | mips64el
libtrilinos-trilinoscouplings-dev |  12.10.1-1 | mips64el
libtrilinos-trilinoscouplings12 |  12.10.1-1 | mips64el
libtrilinos-triutils-dev |  12.10.1-1 | mips64el
libtrilinos-triutils12 |  12.10.1-1 | mips64el
libtrilinos-xpetra-dev |  12.10.1-1 | mips64el
libtrilinos-xpetra12 |  12.10.1-1 | mips64el
libtrilinos-zoltan-dev |  12.10.1-1 | mips64el
libtrilinos-zoltan12 |  12.10.1-1 | mips64el
libtrilinos-zoltan2-12 |  12.10.1-1 | mips64el
libtrilinos-zoltan2-dev |  12.10.1-1 | mips64el
trilinos-all-dev |  12.10.1-1 | mips64el
trilinos-dev |  12.10.1-1 | mips64el

--- Reason ---
RoM; FTBFS
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been 

r-cran-coda 0.19-1-1 MIGRATED to testing

2016-12-27 Thread Debian testing watch
FYI: The status of the r-cran-coda source package
in Debian's testing distribution has changed.

  Previous version: 0.18-1-1
  Current version:  0.19-1-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


tachyon 0.99~b6+dsx-7 MIGRATED to testing

2016-12-27 Thread Debian testing watch
FYI: The status of the tachyon source package
in Debian's testing distribution has changed.

  Previous version: 0.99~b6+dsx-6
  Current version:  0.99~b6+dsx-7

-- 
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


r-cran-gam 1.14-1 MIGRATED to testing

2016-12-27 Thread Debian testing watch
FYI: The status of the r-cran-gam source package
in Debian's testing distribution has changed.

  Previous version: 1.12-2
  Current version:  1.14-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


r-cran-colorspace 1.3-2-1 MIGRATED to testing

2016-12-27 Thread Debian testing watch
FYI: The status of the r-cran-colorspace source package
in Debian's testing distribution has changed.

  Previous version: 1.3-1-1
  Current version:  1.3-2-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


r-cran-geepack 1.2-1-1 MIGRATED to testing

2016-12-27 Thread Debian testing watch
FYI: The status of the r-cran-geepack source package
in Debian's testing distribution has changed.

  Previous version: 1.2-0.2-1
  Current version:  1.2-1-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


Bug#849476: libopencv-dev: fails to install on experimental due to inconsistent version suffix '+b1'

2016-12-27 Thread Simon Frei
Package: libopencv-dev
Version: 3.1.0+dfsg-1~exp2
Severity: serious

Hi,

Trying to install libopencv-dev from experimental fails:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libopencv-dev : Depends: libopencv3.1-java (= 3.1.0+dfsg-1~exp2+b1)
but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

The problem is that all binary packages in experimental are version
3.1.0+dfsg-1~exp2+b1 except libopencv3.1-java which is
3.1.0+dfsg-1~exp2. As libopencv depends on the latter, it fails as its
version number is older.

Cheers,
Simon

-- 
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#848859: FTBFS randomly (failing tests)

2016-12-27 Thread Ole Streicher
Hi Santiago,

> In particular, if something happens 1 every 20 times on average, the
> fact that it did not happen when you try 10 times does not mean in any
> way that it may not happen.


I must however say that I don't see why a package that fails to build
once in 20 builds would have a release critical problem:

There is nothing in our policy that requires a reproducible or even a
always successful build. I totally agree that catching random failures
is a good quality measure, but this is IMO severity "important" at maximum.

And it would be nice to have this QA test not just before the release,
but already early in the release cycle. This would help a lot to avoid
stressful bugfixes just before the freeze.

Best regards

Ole

-- 
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#848859: Lowering the bug`s severity

2016-12-27 Thread Santiago Vila
On Tue, Dec 27, 2016 at 10:11:56AM +0100, Anton Gladky wrote:
> 2016-12-27 9:50 GMT+01:00 Santiago Vila :
> > This means, if you are bad at math, that the error will happen once
> > every 20 tries. If you only built it 5 times, you did not really tried
> > to reproduce it.
> 
> I'm not going to build every package 20 times to catch a "possible" bug,

The build logs I sent prove that there is bug, so it's not a "possible" bug.

> The main source of information for this type of bugs is the
> buildds [1] for me. They are happy at the moment.

The main, maybe, but it should not be the only one.

In particular, if something happens 1 every 20 times on average, the
fact that it did not happen when you try 10 times does not mean in any
way that it may not happen.

This is basic math, and everybody here (debian-science) should be aware of that.

Sorry if you don't like my communication style. Please try not to
dismiss completely the build logs I sent and maybe you will see how my
communication style improves greatly.

Thanks.

-- 
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#848859: Lowering the bug`s severity

2016-12-27 Thread Anton Gladky
2016-12-27 9:50 GMT+01:00 Santiago Vila :
> This means, if you are bad at math, that the error will happen once
> every 20 tries. If you only built it 5 times, you did not really tried
> to reproduce it.

I'm not going to build every package 20 times to catch a "possible" bug,
sorry. The main source of information for this type of bugs is the
buildds [1] for me. They are happy at the moment.

And please change the style of communication with me.

Cheers

[1] https://buildd.debian.org/status/package.php?p=getfem%2B%2B

Anton

-- 
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#847561: marked as done (new homepage and version)

2016-12-27 Thread Debian Bug Tracking System
Your message dated Tue, 27 Dec 2016 09:54:08 +0100
with message-id 
and subject line Re: new homepage and version
has caused the Debian Bug report #847561,
regarding new homepage and version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
847561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcgns
Version: 3.1.4.2-3
Severity: normal
 
Hi,

CGNS is hosted from github now, and a newer version is also available.

http://cgns.github.io/

Thanks
--- End Message ---
--- Begin Message ---
Version: 3.3.0-1

On Fri, 9 Dec 2016 14:53:07 +0100 1...@gmx.us wrote:
> Source: libcgns
> Version: 3.1.4.2-3
> Severity: normal
>  
> Hi,
> 
> CGNS is hosted from github now, and a newer version is also available.
> 
> http://cgns.github.io/

Hi,

Release 3.3.0 entered Debian unstable on 2016-12-15.

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
-- 
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#848859: Lowering the bug`s severity

2016-12-27 Thread Santiago Vila
On Tue, Dec 27, 2016 at 08:20:54AM +0100, Anton Gladky wrote:
> severity 848859 minor
> tags 848859 +unreproducible
> thanks
> 
> Hi  Santiago,
> 
> thanks for your bugreport! I tried to reproduce the failing
> test, building getfem on barriere.d,o 5 times but in all
> cases it did not failed. Also the last upload of getfem was
> successfully built on all supported platforms.
> 
> Nevertheless I am not closing the bug, but lowering its
> severity for the case if the bug will appear again.

The bug is probably still there, just that you didn't really bother to
reproduce it. I clearly said this in my bug report:

"The failure rate is around 5%, so if you try to reproduce this,
please try a *lot* of times."

This means, if you are bad at math, that the error will happen once
every 20 tries. If you only built it 5 times, you did not really tried
to reproduce it.

And then you didn't bother to Cc:me on this message, which I had to
read from debian-bugs-rc@l.d.o.

For this reason, I consider this downgrade of yours unacceptable and a
bad joke.

I'm going to repeat my tests in unstable, just for the case that some
already-fixed build-dependency was to blame for this, but if I still
reproduce this I will restore the original severity, as packages *must*
build from source *without* failure, this is not an invention of mine,
it's Release Policy.

Thanks.

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