flint is marked for autoremoval from testing
flint 2.5.2-3 is marked for autoremoval from testing on 2016-05-05 It is affected by these RC bugs: 818990: flint: FTBFS: recipe for target '../build/fmpz_poly/test/t-taylor_shift_multi_mod_threaded_RUN' failed -- 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#819515: python-sympy: please package new upstream version
Package: python-sympy Version: 0.7.6.1-2 Severity: wishlist Hello and thanks (again) for maintaining the sympy Debian package! There's a new upstream version (1.0) available with new interesting features: could you please package it? Thanks for your time. P.S.: As an aside, I noticed that the tracker [1] claims that src:sympy is marked for autoremoval from testing on 23 April due to bug #817789 [2]; frankly speaking, I do not understand the relation between the bug and sympy, since python-blockdiag does not seem to be a (direct or indirect) dependency of any of src:sympy binary packages, nor a (direct) build-dependency... maybe it's an indirect build-dependency? Anyway, please investigate and, possibly, help to fix bug #817789 ! Once more, thanks for your time and dedication. [1] https://tracker.debian.org/pkg/sympy [2] https://bugs.debian.org/817789 -- 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#802961: marked as done (vtk6: FTBFS on hppa: error: couldn't find library libvtkRenderingQtPython27D-6.2.so.6.2)
Your message dated Tue, 29 Mar 2016 22:40:40 +0200 with message-id <1459284040.6250.2.ca...@gmail.com> and subject line Builds now has caused the Debian Bug report #802961, regarding vtk6: FTBFS on hppa: error: couldn't find library libvtkRenderingQtPython27D-6.2.so.6.2 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.) -- 802961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vtk6 Version: 6.2.0+dfsg1-4 Severity: normal Dear Maintainer, Build fails with error here: dpkg-shlibdeps: warning: can't extract name and version from library name 'libvtkRenderingCoreJava.so' dpkg-shlibdeps: warning: can't extract name and version from library name 'libvtkRenderingCoreJava.so' dpkg-shlibdeps: warning: can't extract name and version from library name 'libvtkRenderingCoreJava.so' dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/libvtk6.2/usr/lib/hppa-linux-gnu/libvtkverdict-6.2.so.6.2.0 debian/libvtk6.2/usr/lib/hppa-linux-gnu/libvtkalglib-6.2.so.6.2.0 debian/libvtk6.2/usr/lib/hppa-linux-gnu/libvtksys-6.2.so.6.2.0 debian/libvtk6.2/usr/lib/hppa-linux-gnu/libvtkDICOMParser-6.2.so.6.2.0 debian/libvtk6.2/usr/lib/hppa-linux-gnu/libvtkmetaio-6.2.so.6.2.0 were not linked against libmpichcxx.so.12 (they use none of the library's symbols) dpkg-shlibdeps: error: couldn't find library libvtkRenderingQtPython27D-6.2.so.6.2 needed by debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkRenderingQtPython.hppa-linux-gnu.so (ELF format: 'elf32-hppa-linux'; RPATH: '') dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/python-vtk6/usr/bin/pvtkpython debian/python-vtk6/usr/bin/vtk6python were not linked against libvtkWrappingPython27Core-6.2.so.6.2 (they use none of the library's symbols) dpkg-shlibdeps: error: cannot continue due to the error above Note: libraries are not searched in other binary packages that do not have any shlibs or symbols file. To help dpkg-shlibdeps find private libraries, you might need to use -l. dh_shlibdeps: dpkg-shlibdeps -Tdebian/python-vtk6.substvars debian/python-vtk6/usr/bin/pvtk debian/python-vtk6/usr/bin/pvtkpython debian/python-vtk6/usr/bin/vtkWrapPython-6.2 debian/python-vtk6/usr/bin/vtk6python debian/python-vtk6/usr/bin/vtkWrapPythonInit-6.2 debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkIOLegacyPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkParallelCorePython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkGeovisCorePython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkInfovisLayoutPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkCommonDataModelPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkFiltersExtractionPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkIOExodusPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkRenderingConte xt2DPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkRenderingImagePython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkIOMySQLPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkIOSQLPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkFiltersTexturePython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkRenderingFreeTypePython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkImagingMorphologicalPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkIOParallelExodusPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkRenderingCorePython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkViewsInfovisPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkImagingHybridPython.hppa-linux-gnu.so debian/ python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkFiltersSourcesPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkIOXMLPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkFiltersSMPPython.hppa-linux-gnu.so debian/python-vtk6/usr/lib/python2.7/dist-packages/vtk/vtkIOInfovisPython.hppa-linux-gnu.so
calculix-ccx-test 2.10-1 MIGRATED to testing
FYI: The status of the calculix-ccx-test source package in Debian's testing distribution has changed. Previous version: 2.9-1 Current version: 2.10-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
Otkriće najveće kamene kugle u Europi
Bosanske piramide NEWSLETTER OTKRIĆE NAJVEĆE KAMENE KUGLE U EUROPI … Početkom marta 2016. započelo je iskopavanje kamene kugle u selu Podubravlje, na periferiji zavidovićke općine. Nakon desetak dana kopanja, postalo je jasno da je riječ o megalitnim dimenzijama kugle. Tog 19. marta smo izmjerili otkopani dio, koji je bio nešto manji nego polovina obima kamene kugle. Rezultat: 3,80 m. Obim je najvjerovatnije između osam i devet metara. Piše: dr. Semir Osmanagić Fenomen prahistorijskih kamenih kugli istražujem već petnaestak godina. Nekoliko puta sam posjetio nalazišta na jugu Kostarike, u zapadnom Meksiku, na Uskršnjem Otoku, Turskoj, otoku Isla del Cano u Pacifiku, Tunisu, Kanarskim otocima. Prisutne su i na Antarktiku, Novom Zelandu, Rusiji, Egiptu, SAD, Argentini … Na Balkanu sam pisao o kamenim kuglama iz sjeverne Albanije, Dalmatinske Zagore, zapadne Srbije i Sandžaka. Osnivanjem Fondacije “Arheološki park: Bosanska piramida Sunca” počeli smo sistematska istraživanja ovog fenomena u Bosni i Hercegovini. U početku su u timu bili Ahmed Bosnić, Jovo Jovanović i Bojan Zečević. Do sada smo ih pronašli na dvadeset lokacija: osam oblikovanih granitnih kugli u Teočaku kod Tuzle, vulkanska kamena kugla kod Konjica, te one građene od pješčara u selima Trn i Slatina kod Banja Luke, zatim Vareš, Zenica, Bihać, Žepče, i drugdje. Najveće nalazište je kod Zavidovića, u Dubokom potoku, gdje ih je svojevremeno bilo 80. Neke su završile niže u rijeci Bosni, veći dio su lokalni stanovnici razbili u potrazi za blagom kojeg nikada nisu našli, dio ukrašava privatna imanja, a još uvijek osam očuvanih kamenih kugli leži u potoku. U septembru 2006., na inicijativu Fondacije, osnovan je “Arheološki park: Bosanske kamene kugle”, koji smo pretvorili u turističku atrakciju promovirajući je širom svijeta i šaljući naše goste u posjet ovoj lokaciji. O njoj sa danas brine Nedžad Ikanović s nekolicinom mještana. Tokom 2007. četiri uzorka oštećenih kamenih kugli iz Zavidovića te uzorak prirodnog stjenskog materijala uzeo je profesor Muhamed Pašić i analizirao na Institutu za materijale u Zenici. Fizičko-kemijska analiza je pokazala prisutnost istih devet elemenata u istom omjeru u kuglama i prirodnim stijenama. Međutim, razlika je bila u tome što su kugle sadržavale i mangan, koji se koristi za poboljšanje čvrstoće, te kalcijum oksid, osnovu za vezivni materijal. Zaključak: drevna civilizacija je topila prirodni kamen i dodavala aditive da poboljša kvalitet, izljevala u kalupe i dobijala izuzetno čvrste kamene kugle. Početkom marta 2016. započelo je iskopavanje kamene kugle u selu Podubravlje, na periferiji zavidovićke općine. Lokaciju sam posjetio 19. marta 2016. s nekoliko medija i grupom turista iz 13 zemalja. Ova kamena kugla je površinom manjom od jednog kvadratnog metra virila iz zemlje decenijama. O njenom postojanju su znali stariji stanovnici ovog kraja. Međutim, skorašnja iskopavanja su započela dva entuzijasta (Kristijan i “Ciklon”). Otkopavanje ide sporo zbog nataložene zemlje, ručnih alata i želje da se kugla ne ošteti. Nakon desetak dana kopanja, postalo je jasno da je riječ o megalitnim dimenzijama kugle. Tog 19. marta smo izmjerili otkopani dio, koji je bio nešto manji nego polovina obima kamene kugle. Rezultat: 3,80 m. Obim je najvjerovatnije između osam i devet metara. Odatle možemo dobiti i radijus, koji je između 1,20 – 1,50 m. Za određivanje mase potrebno je odrediti i gustoću, a za to nam treba analiza materijala koji su prisutni u kugli. Ono što je bilo očigledno je smeđe-crvena boja kugle, odnosno visoka koncentracija željeza. Ako pretpostavimo da je gustoća između gustoće krečnjaka (2,2 kg/k.cm.) i željeza (7,8), ona bi mogla iznositi oko 5 kg/k.cm. U tom slučaju imamo dvije preliminarne vrijednosti za radijus i gustoću i možemo izračunati masu. Ona iznosi više od 30 tona! U Europi, u ovom momentu, nema masivnije (“teže”) kamene kugle od upravo iskopane kugle u Podubravlju. Iznad kamene kugle se nalazi sloj ploča pješčara, zatim sloj gline, zemlje i vegetacije. To svjedoči o enormnoj starosti kugle iznad koje su se sedimentirali prirodni materijali desetinama, a možda i stotinama hiljada godina. Najveća kamena kugla u Kostarici je 35 tona, a najmasivnija u zapadnom Meksiku iznosi 40 tona. Tek kada u potpunosti očistimo kamenu kuglu u Podubravlju, saznamo tačan radijus, te kada analiziramo strukturu materijala, znaćemo da li je ovo najmasivnija kamena kugla na svijetu. Ukoliko je napravljena od lijevanog željeza, odgovor bi bio definitivno potvrdan. Šta bi to značilo? Prvo, da je tlo južne Europe, Balkana i Bosne i Hercegovine, bilo lokacija izuzetno starih naprednih civilizacija o kojima ne postoje pisani tragovi. Drugo, da su poznavali tehnologiju sasvim drugačiju od nase. I, treće, da su koristili moćan geometrijski oblik (“sfera”), energetski potentan materijal (elektromagnetizam željeza) na energetski važnim tačkama (kretanje vode, oslobađanje
Processing of python-arrayfire_3.3.20160328-1_amd64.changes
python-arrayfire_3.3.20160328-1_amd64.changes uploaded successfully to localhost along with the files: python-arrayfire_3.3.20160328-1.dsc python-arrayfire_3.3.20160328.orig.tar.gz python-arrayfire_3.3.20160328-1.debian.tar.xz python-arrayfire-doc_3.3.20160328-1_all.deb python-arrayfire_3.3.20160328-1_all.deb python3-arrayfire_3.3.20160328-1_all.deb Greetings, Your Debian queue daemon (running on host franck.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
Processing of python-arrayfire_3.3.20160328-1_amd64.changes
python-arrayfire_3.3.20160328-1_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: python-arrayfire_3.3.20160328-1.dsc python-arrayfire_3.3.20160328.orig.tar.gz python-arrayfire_3.3.20160328-1.debian.tar.xz python-arrayfire-doc_3.3.20160328-1_all.deb python-arrayfire_3.3.20160328-1_all.deb python3-arrayfire_3.3.20160328-1_all.deb Greetings, Your Debian queue daemon (running on host coccia.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
Processing of gle-graphics_4.2.5-4_amd64.changes
gle-graphics_4.2.5-4_amd64.changes uploaded successfully to localhost along with the files: gle-graphics_4.2.5-4.dsc gle-graphics_4.2.5-4.debian.tar.xz gle-graphics-dbgsym_4.2.5-4_amd64.deb gle-graphics_4.2.5-4_amd64.deb Greetings, Your Debian queue daemon (running on host franck.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#750197: Please enable VTK6 test suite
On Tue, 2016-03-29 at 11:19 +0200, Mathieu Malaterre wrote: > There is a vtkdata package. Do you need a vtk6data package ? vtkdata is used for the examples, and not for the tests. The test data set consists of files that have their md5sums as file names - just like with ITK, only that VTK-upstream doesn't provide an according tarball. With that in mind I wouldn't want to create an extra package for just the test data since it is useless after the package has been build. Another problem is that VTK will need an OpenGL enabled test environment. xvfb doesn't cut it, and with Xdummy I don't have any experience yet (i.e. it doesn't provide such a nice script like xvfb-run. Best, Gert -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
