Processed: Re: Bug#813691: make openmpi the default on s390x

2016-02-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 - moreinfo Bug #813691 [src:mpi-defaults] make openmpi the default on s390x Removed tag(s) moreinfo. -- 813691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-science

Processed: Re: Bug#813691: make openmpi the default on s390x

2016-02-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #813691 [src:mpi-defaults] make openmpi the default on s390x Added tag(s) moreinfo. -- 813691: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-science-mai

Processed: Re: Bug#791195: fixed in lttoolbox 3.3.2~r61000-3.1

2016-02-03 Thread Debian Bug Tracking System
Processing control commands: > found -1 3.3.2~r63423-1 Bug #791195 [src:lttoolbox] lttoolbox: library transition may be needed when GCC 5 is the default Marked as found in versions lttoolbox/3.3.2~r63423-1. -- 791195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791195 Debian Bug Tracking S

Re: polyml 5.6-2

2016-02-01 Thread Gianfranco Costamagna
Hi, >That's odd; the only thing I can think of is I changed git-buildpackage from >re-creating the orig.tar.gz from the upstream tag to it using the pristine-tar >>branch... Perhaps they're not identical then? Anyway, thanks! the problem seems to be about compressio

Re: polyml 5.6-2

2016-02-01 Thread James Clarke
(Cc'd Debian Science as I forgot to in my original email) That's odd; the only thing I can think of is I changed git-buildpackage from re-creating the orig.tar.gz from the upstream tag to it using the pristine-tar branch... Perhaps they're not identical then? Anyway, thanks! I

Re: What is up with cddlib in NEW?

2016-01-29 Thread Petter Reinholdtsen
[Tobias Hansen] > Hi, > > yes, I asked ftpmasters twice (on 07/31/15 and 09/01/15) if they could > review it because I wanted to package a new upstream version. I did not > get an answer. It's only in NEW because I renamed the package > libcdd-test to libcdd-tools. It's an easy review. I guess now

Re: What is up with cddlib in NEW?

2016-01-29 Thread Tobias Hansen
Hi, yes, I asked ftpmasters twice (on 07/31/15 and 09/01/15) if they could review it because I wanted to package a new upstream version. I did not get an answer. It's only in NEW because I renamed the package libcdd-test to libcdd-tools. It's an easy review. I guess now nobody reviews it because t

Processed: Re: Bug#805193: aster: FTBFS: Fatal Error: finclude/petscsys.h: No such file or directory

2016-01-29 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #805193 [src:aster] aster: FTBFS: Fatal Error: finclude/petscsys.h: No such file or directory Added tag(s) pending. -- 805193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805193 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: Re: opencv: FTBFS on sparc64

2016-01-27 Thread Debian Bug Tracking System
appropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug reopened No longer marked as fixed in versions opencv/2.4.6.1+dfsg-2. > End of message, stopping processing here. Please contact me if you need assistanc

Re: polyml 5.6-1 (was: polyml 5.5.2-4)

2016-01-26 Thread James Clarke
Great, thanks! And yes, the ABI bump annoyingly slows things down a little... Regards, James > On 26 Jan 2016, at 10:26, Gianfranco Costamagna > wrote: > > Hi, sponsoring in a few moments. > > note: it will go through binNEW queue :) > > cheers, > > G. > > > > > > Il Martedì 26 Gennaio

Re: polyml 5.6-1 (was: polyml 5.5.2-4)

2016-01-26 Thread Gianfranco Costamagna
Hi, sponsoring in a few moments. note: it will go through binNEW queue :) cheers, G. Il Martedì 26 Gennaio 2016 10:12, James Clarke ha scritto: Hi Gianfranco, I have uploaded 5.6-1 to mentors; could you please review it? Thanks, James > On 25 Jan 2016, at 21:08, James Clarke wrote: >

Re: polyml 5.5.2-4

2016-01-25 Thread James Clarke
Ok, hopefully my s390x build will finish soon and I can then upload 5.6-1 to mentors including S/390 support (and thus, barring any regressions, have support for every release architecture!). Thanks, James > On 25 Jan 2016, at 21:07, Gianfranco Costamagna > wrote: > > Again, I think I'll tru

Re: polyml 5.5.2-4

2016-01-25 Thread Gianfranco Costamagna
Again, I think I'll trust your dsc file, but unfortunately I need to prior have one to test and double check/report back in case of issues. So if you have a dsc, please share, I think it will be fine! Cheers,G. Sent from Yahoo Mail on Android On Mon, 25 Jan, 2016 at 22:00, James Clarke wrote:

Re: polyml 5.5.2-4

2016-01-25 Thread James Clarke
Hi Gianfranco, For platforms where fe{g,s}etround (and other equivalent functions for different platforms), the implementation of {g,s}etRoundingMode is to raise an exception saying “Unable to set floating point rounding control” which can be either be caught in the user’s ML code or left to pro

Re: polyml 5.5.2-4

2016-01-25 Thread Gianfranco Costamagna
Hi, you are the maintainer, so it should be only up to you to make the final decision about architectures to support.You need to understand the use case of this particular test, what is the probability to hit this with real code running on an armel machine? In fact since this has almost never wo

Re: polyml 5.5.2-4

2016-01-25 Thread James Clarke
Hi Gianfranco, >> I think it’s implemented in glibc, not gcc; certainly fe{g,s}etround are. >> Should I get in touch with debian-arm? > > probably yes, even if I don't care there are much armel porters there... > > You might end up in asking ftpmaster to remove the armel binary. Ok, I think I’

Re: polyml 5.5.2-4

2016-01-25 Thread Gianfranco Costamagna
Hi, >I think it’s implemented in glibc, not gcc; certainly fe{g,s}etround are. >Should I get in touch with debian-arm? probably yes, even if I don't care there are much armel porters there... You might end up in asking ftpmaster to remove the armel binary. cheers, Gianfranco -- debian-scie

Re: polyml 5.5.2-4

2016-01-25 Thread James Clarke
Hi, >> Besides FE_UPWARD having a different value (given that it’s >> platform-specific), armel calculates 1.0 / 3.0 as 0.15, >> which is wrong for FE_UPWARD (but correct for FE_NEAREST), and I imagine >> there are similar issues for the other rounding modes (other than >> FE_NE

Re: polyml 5.5.2-4

2016-01-25 Thread Gianfranco Costamagna
Hi, > 1/3 can’t be represented exactly, so when rounding to +Inf, you get a little > bit more than 1/3. 3 can be represented exactly, so 3 * 1/3 is a little more > than 1, >and since the rounding mode is set to +Inf it should therefore round > to a little over 1. I’m pretty sure the test is cor

Re: polyml 5.5.2-4

2016-01-25 Thread Gianfranco Costamagna
est suite doesn’t log >anything to a file like that example, so I would have to re-run the failed >tests manually, >or mess with the testing code itself. mmm I was thinking about: dh_auto_test || for i=1 to n do ./poly < Tests/Succeed/Test$$i.ML; done && exit 1 what is prin

Re: polyml 5.5.2-4

2016-01-25 Thread James Clarke
gt; > look e.g. here > https://sources.debian.net/src/insighttoolkit4/4.8.2-3.1/debian/rules/ I’m aware of the sh syntax; the trouble is, the test suite doesn’t log anything to a file like that example, so I would have to re-run the failed tests manually, or mess with the testing code itself

Re: polyml 5.5.2-4

2016-01-25 Thread Gianfranco Costamagna
Hi, >That’s my guess. The test suite wasn’t run before I took over (I feared I had >stopped it running when I changed debian/rules to modern debhelper) either, so >who >knows how long it’s been there. I don't find running testsuites there https://buildd.debian.org/status/logs.php?pkg=polyml&a

Re: polyml 5.5.2-4

2016-01-25 Thread James Clarke
Hi Gianfranco, >> I quickly looked at the test >> setRoundingMode(TO_POSINF); >> check(getRoundingMode() = TO_POSINF); >> val pos = 1.0/3.0; >> check(pos * 3.0 > 1.0); >> val neg = ~1.0/3.0; >> check(neg * 3.0 > ~1.0); >> >> >> well, I'm not sure the test is correct, I mean, you might have the e

Re: polyml 5.5.2-4

2016-01-25 Thread James Clarke
> Hi, > >> Meant to say: I have one, though it’s running raspbian; would that mess with >> things? > not sure, I'm pretty sure the bug has always been there, just hidden because > of a missing > testsuite run… That’s my guess. The test suite wasn’t run before I took over (I feared I had stoppe

Re: polyml 5.5.2-4

2016-01-25 Thread Gianfranco Costamagna
Hi, >Meant to say: I have one, though it’s running raspbian; would that mess with >things? not sure, I'm pretty sure the bug has always been there, just hidden because of a missing testsuite run... and you don't have too much dependencies on your package, so probably you will hit the bug on ras

Re: polyml 5.5.2-4

2016-01-25 Thread James Clarke
> On 25 Jan 2016, at 08:03, James Clarke wrote: > > Hi Gianfranco, > >>> Is there any way in which I could get access to an armel porter box to try >>> and work out what’s causing the failure? >> >> as a normal contributor not, as a DM yes, after you requested the access, as >> a DD yes. > >

Re: polyml 5.5.2-4

2016-01-25 Thread James Clarke
Hi Gianfranco, >> Is there any way in which I could get access to an armel porter box to try >> and work out what’s causing the failure? > > as a normal contributor not, as a DM yes, after you requested the access, as > a DD yes. That was my guess. > that said, I'm happy to test patches if yo

Re: polyml 5.5.2-4

2016-01-24 Thread Gianfranco Costamagna
Hi again, >Is there any way in which I could get access to an armel porter box to try and >work out what’s causing the failure? as a normal contributor not, as a DM yes, after you requested the access, as a DD yes. that said, I'm happy to test patches if you have some, but I can't easily gi

Re: polyml 5.5.2-4

2016-01-24 Thread James Clarke
Hi Gianfranco, >> I am aware s390x is failing. I have been trying to port it, and it no longer >> segfaults (thanks to the pexport-endian.diff patch from upstream), but one >> part of the >build step (the compiler bootstrapping itself) exits with code >> 1, without printing anything. That’s on

Re: polyml 5.5.2-4

2016-01-24 Thread Gianfranco Costamagna
> If you want ti maintain some other packages you might even consider applying > for Debian Contributor or Debian Maintainer, you are doing a good job here, > you might even have direct upload privileges one day for this package :) > > Cheers, > > G. > -

Re: polyml 5.5.2-4

2016-01-24 Thread James Clarke
consider applying >> for Debian Contributor or Debian Maintainer, you are doing a good job here, >> you might even have direct upload privileges one day for this package :) >> >> Cheers, >> >> G. >> >>

Re: polyml 5.5.2-4

2016-01-24 Thread James Clarke
intainer, you are doing a good job here, > you might even have direct upload privileges one day for this package :) > > Cheers, > > G. > > Dom 24/1/16, James Clarke ha scritto: > > Oggetto: Re: polyml 5.5.2-4 > A: "

Re: polyml 5.5.2-4

2016-01-24 Thread Gianfranco Costamagna
Contributor or Debian Maintainer, you are doing a good job here, you might even have direct upload privileges one day for this package :) Cheers, G. Dom 24/1/16, James Clarke ha scritto: Oggetto: Re: polyml 5.5.2-4 A: "Gianfranco Costamagna&

Re: polyml 5.5.2-4

2016-01-24 Thread James Clarke
ce/2016/01/msg00035.html >> >>> 2) a patch against testsuite not mentioned in changelog >>> 3) patches against mips* not mentioned in changelog. >>> >>> basically I would change changelog mentioning the patch name, e.g. >>> new patches: >>> fo

Re: polyml 5.5.2-4

2016-01-24 Thread Gianfranco Costamagna
I would change changelog mentioning the patch name, e.g. >> new patches: >> foo.diff: add support for foo architecture >> >> and so on. >> the patches should be good :) > > I have amended the changelog and re-uploaded to mentors; how is it now? > > Thanks, &

Re: polyml 5.5.2-4

2016-01-24 Thread James Clarke
angelog. >> >> basically I would change changelog mentioning the patch name, e.g. >> new patches: >> foo.diff: add support for foo architecture >> >> and so on. >> the patches should be good :) > > I have amended the changelog and re-uploaded to mentors; how

Re: polyml 5.5.2-4

2016-01-24 Thread Gianfranco Costamagna
ng the patch name, e.g. > new patches: > foo.diff: add support for foo architecture > > and so on. > the patches should be good :) I have amended the changelog and re-uploaded to mentors; how is it now? Thanks, James -- debian-science-maintainers mailing list debian-science-mai

Processed: Re: libvigraimpex: FTBFS in sid: test suite failure due to pynum 1.10

2016-01-24 Thread Debian Bug Tracking System
Processing control commands: > block 650601 by -1  Bug #650601 [release.debian.org] transition: libpng 1.6 650601 was blocked by: 641889 809949 810197 662443 810201 662476 636998 809941 650567 809879 809955 809898 809873 810176 809960 809883 810202 809948 742569 810175 809938 809951 809942 80988

Processed: Re: 3depict: FTBFS with libpng16

2016-01-24 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 811370 Bug #809881 [src:3depict] 3depict: FTBFS with libpng16 809881 was not blocked by any bugs. 809881 was blocking: 650601 Added blocking bug(s) of 809881: 811370 -- 809881: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809881 Debian Bug Tracking

Re: polyml 5.5.2-4

2016-01-24 Thread James Clarke
tioned in changelog > 3) patches against mips* not mentioned in changelog. > > basically I would change changelog mentioning the patch name, e.g. > new patches: > foo.diff: add support for foo architecture > > and so on. > the patches should be good :) I have amended the cha

Re: polyml 5.5.2-4

2016-01-24 Thread Gianfranco Costamagna
Hi James, >I have been working with upstream to port Poly/ML to additional architectures, >and have backported these changes. I have uploaded 5.5.2-4 to mentors; could >you >please check it and then upload it? wonderful, lets review: 1) you took over the package maintenance, can I see a pos

Re: kbibtex_0.6+20160117git.3424e658c4268-1_amd64.changes REJECTED

2016-01-23 Thread roucaries bastien
Fixed under lintian git. Reported upstream will fix On Fri, Jan 22, 2016 at 1:00 AM, Thorsten Alteholz wrote: > > Hi Bastien, > > as testset/isi/ISI_export_format.html is licensed under CC-NC, please > remove this file from a package for main. > > Thanks! > Thorsten > > === > > Please feel free

Bug#740194: closed by Andreas Beckmann (Re: ngspice: request to update to recent upstream release 26)

2016-01-22 Thread Thomas Uhle
Andreas, you are right that version 26 was released in July 2014, but AFAICS without compiling it with FFTW3 support which I also asked for. Best regards, Thomas Uhle -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cg

Re: kbibtex_0.6+20160117git.3424e658c4268-1_amd64.changes REJECTED

2016-01-22 Thread Bastien Roucaries
Le 22 janvier 2016 01:00:20 GMT+01:00, Thorsten Alteholz a écrit : > >Hi Bastien, > >as testset/isi/ISI_export_format.html is licensed under CC-NC, please >remove this file from a package for main Oh shit will do... Lintian does not complain? Bastien > >Thanks! > Thorsten > >=== > >Please

Processed: Re: Bug#812311: scilab: Scilab Crash with Basic functions (det and inv matrix)

2016-01-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 812311 normal Bug #812311 [scilab] scilab: Scilab Crash with Basic functions (det and inv matrix) Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 812311: http://bugs

Processed: Re: Bug#811761: cld2: FTBFS with GCC 6: narrowing conversion

2016-01-20 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/CLD2Owners/cld2/issues/47 Bug #811761 [cld2] cld2: FTBFS with GCC 6: narrowing conversion Ignoring request to change the forwarded-to-address of bug#811761 to the same value -- 811761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Processed: Re: Bug#811761: cld2: FTBFS with GCC 6: narrowing conversion

2016-01-20 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://github.com/CLD2Owners/cld2/issues/47 Bug #811761 [cld2] cld2: FTBFS with GCC 6: narrowing conversion Set Bug forwarded-to-address to 'https://github.com/CLD2Owners/cld2/issues/47'. -- 811761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811

RE

2016-01-19 Thread Margaret.Hoey
I got a donation for you, Email me for details via:: mr.ped...@qq.com Best Regards Mr. Pedro. ** This email is intended for the addressee named and may contain confidential information. If you are not the intended recipient, please delete it and notify the s

Processed: Re: hkl: Update build dependencies for GSL 2.x

2016-01-18 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #807206 [src:hkl] hkl: Update build dependencies for GSL 2.x Added tag(s) pending. -- 807206: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-science-maint

RE: Partnership

2016-01-17 Thread Lucia Arends
Partnership Partnership is needed contact for details email: ian.c...@hotmail.com -- 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: Re: Bug#811191: [regression] lapack 3.6.0 fails the testsuite

2016-01-16 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #811191 [src:lapack] [regression] lapack 3.6.0 fails the testsuite Severity set to 'normal' from 'important' > retitle -1 some test fails in LAPACK testsuite Bug #811191 [src:lapack] [regression] lapack 3.6.0 fails the testsuite Changed Bug tit

Processed: Re: gnuplot5-qt: incorrect font size (regression in gnuplot5 5.0.2+dfsg1-1)

2016-01-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 810943 gnuplot5: font size no longer taken into account in wxt > terminals Bug #810943 [gnuplot5-qt] font size no longer taken into account in wxt terminals Changed Bug title to 'gnuplot5: font size no longer taken into account in wxt t

Processed: Re: gnuplot5-qt: incorrect font size (regression in gnuplot5 5.0.2+dfsg1-1)

2016-01-13 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 font size no longer taken into account in wxt terminals Bug #810943 [gnuplot5-qt] gnuplot5-qt: incorrect font size (regression in gnuplot5 5.0.2+dfsg1-1) Changed Bug title to 'font size no longer taken into account in wxt terminals' from 'gnuplot5-qt: in

Re: vtk6_6.2.0+dfsg1-5_arm64.changes REJECTED

2016-01-13 Thread Anton Gladky
Hi Thorsten, thanks for pointing this out! I have fixed all issues hopefully and uploaded the package again. Best regards Anton 2016-01-13 11:00 GMT+01:00 Thorsten Alteholz : > > Hi Anton, > > please mention all licenses in your debian/copyright. > At least Apache-2, Boost and MIT are missing.

re

2016-01-13 Thread Waif Lastman
SPENCER HINES & ASSOCIATES hereby announce the last Will & Testament of our late client have been read.You are one of the beneficiaries. Please get back to us for the details.Send reply to: firlaste47...@outlook.com -- debian-science-maintainers mailing

Re: Comments regarding ros-geometry-experimental_0.5.12-1_amd64.changes

2016-01-12 Thread Wookey
+++ Thorsten Alteholz [2016-01-12 21:25 +]: > Hi, > > I marked the package for accept, but please check why upstream mentions > LGPL in test_tf2/package.xml and geometry_experimental/package.xml We did. It's just wrong metadata, which should be fixed upstream soon. There may have been an LGP

Notification: IT Support- Have You Re-Activated

2016-01-11 Thread Diane Sinclair
account running. ACTIVATE HERE <http://pageaccesswebteam.webeden.co.uk/> All email will be re-activated. Your account will not function if you do not upgrade. Global IT Support Center -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.or

Re: Comments regarding ros-ros-comm_1.11.16-1_amd64.changes

2016-01-09 Thread Wookey
+++ Thorsten Alteholz [2016-01-09 22:07 +]: > Hi everybody, > > I marked the package for accept, but please take care of the lintian warnings > related to your debian/copyright. Done (and the ros-bond-core lintian errors). Apologies for missing that, sbuild is running the lintian checks and

Processed: Re: libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz

2016-01-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #799340 [libgetdata-doc] libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz Added tag(s) pending. -- 799340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799340 Debian Bug Tracking S

Processed: Re: libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz

2016-01-09 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.9.0-2.1 Bug #799340 {Done: Jonathan Wiltshire } [libgetdata-doc] libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz Marked as found in versions libgetdata/0.9.0-2.1; no longer marked as fixed in

Processed: Re: Bug#784513: qtwebkit removal from python-qt4

2016-01-08 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #784613 [src:spyder] [spyder] Qt4's WebKit removal Severity set to 'serious' from 'important' -- 784613: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784613 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debi

Re: libdxflib changes

2016-01-08 Thread Lisandro Damián Nicanor Pérez Meyer
On Tuesday 05 January 2016 07:33:51 Alastair McKinstry wrote: > Hi, > > dxflib 3.12.2 is now upstream, and I have packaged it in the repo for > review. > git.debian.org/git/debian-science/packages/dxflib.git > > I've made some changes: > * I've changed the package name from libdxflib-2.5.0.0 to l

Processed: Re: Bug#803869: vtk6: FTBFS with FFmpeg 2.9

2016-01-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #803869 [vtk6] vtk6: FTBFS with FFmpeg 2.9 Added tag(s) pending. -- 803869: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- debian-science-maintainers mailing li

Processed: Re: Bug#810140: binwalk: unnecessary(?) deps make binwalk useless on minimal systems

2016-01-06 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python-pyqtgraph Bug #810140 [binwalk] binwalk: unnecessary(?) deps make binwalk useless on minimal systems Bug reassigned from package 'binwalk' to 'python-pyqtgraph'. Ignoring request to alter found versions of bug #810140 to the same values previousl

Processed: Re: Bug#810140: binwalk: unnecessary(?) deps make binwalk useless on minimal systems

2016-01-06 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 binwalk Bug #810140 [python-pyqtgraph] binwalk: unnecessary(?) deps make binwalk useless on minimal systems Bug reassigned from package 'python-pyqtgraph' to 'binwalk'. Ignoring request to alter found versions of bug #810140 to the same values previousl

Re: Status of vmtk

2015-12-22 Thread Johannes Ring
Hi Andreas, On Sat, Dec 19, 2015 at 7:42 AM, Andreas Tille wrote: > when checking reverse dependencies of insighttoolkit3 and vtk5 I > stumbled upon vmtk. I noticed that the project moved to Github and has > a new version. Unfortunately it seems there was no switch to > insighttoolkit4 and vtk6

Re: Bug#808411: RFS: primesieve/5.6.0+ds-1 [new upstream release]

2015-12-19 Thread Anton Gladky
Hi Jerome, I will try to review and upload your package tomorrow. Regards Anton 2015-12-19 22:46 GMT+01:00 Jerome BENOIT : > > > > Forwarded Message > Subject: Bug#808411: RFS: primesieve/5.6.0+ds-1 [new upstream release] > Resent-Date: Sat, 19 Dec 2015 20:57:01 + > Rese

Re: vtk6 and #773424

2015-12-19 Thread Andreas Tille
Hi, I have commited the libvtk6-java enabled packaging to Git. I'd volunteer to upload this to unstable and test with the packaging I have in mind that depends from libvtk6-java. I would consider to unarchive and reopen #773422 and try to sort out the things with the help of the Debian Java team

Processed: Re: Bug#808032: python-genpy: please make the output reproducible

2015-12-19 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:ros-genpy 0.5.7-3 Bug #808032 [src:python-genpy] python-genpy: please make the output reproducible Warning: Unknown package 'src:python-genpy' Bug reassigned from package 'src:python-genpy' to 'src:ros-genpy'. No longer marked as found in versions pyt

Re: Bug#808032: python-genpy: please make the output reproducible

2015-12-19 Thread Andrei POPESCU
Control: reassign -1 src:ros-genpy 0.5.7-3 On Ma, 15 dec 15, 12:20:55, Chris Lamb wrote: > Source: python-genpy > Version: 0.5.7-3 > Severity: wishlist > Tags: patch > User: reproducible-bui...@lists.alioth.debian.org > Usertags: toolchain randomness > X-Debbugs-Cc: reproducible-bui...@lists.aliot

Website Re-Designing

2015-12-18 Thread Riya Sharma
ices *Responsive Website Design *Website Re-Designing *Ecommerce Website Design *Magento Websites *Shopify Websites *Drupal Websites *Payment Gateway Integration *Custom Websites *CMS Theme / Template Design If you are interested in our services the please s

Re: [RFU] xmds2 2.2.2+dfsg-2

2015-12-16 Thread Sébastien Villemot
Le lundi 14 décembre 2015 à 11:47 +0100, Rafael Laboissiere a écrit : > I updated the xmds2 package in Git (commit 479917b) for using libgsl-dev > instead of libgsl0-dev. Please, upload it to unstable. Thanks. Uploaded. -- .''`.Sébastien Villemot : :' :Debian Developer `. `' http:

RE URGENT

2015-12-14 Thread Nasr, Antoinette
I have a very urgent proposal for you,Please contact this email as soon as you can for more details : mrschen80.teob...@gmail.com Best Regards, Mrs Chen -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mail

Processed: re: aster: FTBFS: Fatal Error: finclude/petscsys.h: No such file or directory

2015-12-12 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > Tags 805193 +patch Bug #805193 [src:aster] aster: FTBFS: Fatal Error: finclude/petscsys.h: No such file or directory Added tag(s) patch. > Thanks Stopping processing here. Please contact me if you need assistance. -- 805193: http://bugs.debian.

Processed: Re: Bug#807666: nmu: mpich_3.1-6

2015-12-11 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:mpich Bug #807666 [release.debian.org] nmu: mpich_3.1-6 Bug reassigned from package 'release.debian.org' to 'src:mpich'. Ignoring request to alter found versions of bug #807666 to the same values previously set Ignoring request to alter fixed version

Re: Bug#807666: nmu: mpich_3.1-6

2015-12-11 Thread Emilio Pozuelo Monfort
Control: reassign -1 src:mpich Control: severity -1 serious Control: retitle -1 mpich: overly restrictive GCC check On 11/12/15 14:50, Samuel Thibault wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > Hello, > > Compilin

Processed: Re: Bug#803477: petsc: FTBFS against mpich

2015-12-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 803477 by 807318 Bug #803477 [src:petsc] petsc: FTBFS against mpich 803477 was not blocked by any bugs. 803477 was blocking: 800556 Added blocking bug(s) of 803477: 807318 > thanks Stopping processing here. Please contact me if you need ass

Processed (with 1 error): Re: qtiplot: Fails to build with GSL 2

2015-12-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 805841 Bug #805841 {Done: Anton Gladky } [src:qtiplot] qtiplot: Fails to build with GSL 2 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-

Processed: Re: Bug#756480: fix no longer needed

2015-12-05 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + wontfix Bug #756480 [src:double-conversion] double-conversion: the package should create and install the *.cmake files Added tag(s) wontfix. -- 756480: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756480 Debian Bug Tracking System Contact ow...@bugs.

Re: normaliz_3.0.0+ds-3_amd64.changes REJECTED

2015-12-03 Thread Jerome BENOIT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi: I have just deposited material at mentors.debian.net hth, Jerome On 03/12/15 23:33, Jerome BENOIT wrote: > Hi: > > On 03/12/15 21:06, Graham Inggs wrote: >> On 3 December 2015 at 20:36, Jerome BENOIT wrote: >>> Stricto sensu, it is a Debia

Re: normaliz_3.0.0+ds-3_amd64.changes REJECTED

2015-12-03 Thread Jerome BENOIT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi: On 03/12/15 21:06, Graham Inggs wrote: > On 3 December 2015 at 20:36, Jerome BENOIT wrote: >> Stricto sensu, it is a Debian release: no need to upload the upstream source >> material; >> uploading the Debian source material is what is needed h

Re: normaliz_3.0.0+ds-3_amd64.changes REJECTED

2015-12-03 Thread Graham Inggs
On 3 December 2015 at 20:36, Jerome BENOIT wrote: > Stricto sensu, it is a Debian release: no need to upload the upstream source > material; > uploading the Debian source material is what is needed here. See: https://wiki.debian.org/SourceOnlyUpload dpkg-buildpackage -S -sa source is diff + d

Re: normaliz_3.0.0+ds-3_amd64.changes REJECTED

2015-12-03 Thread Jerome BENOIT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Graham: On 03/12/15 19:28, Graham Inggs wrote: > Hi Jerome > > On 3 December 2015 at 19:53, Jerome BENOIT wrote: >> Please let me know what I may do to solve this issue. >> Thanks in advance, >> Jerome > > I don't think you need to do anyth

Re: normaliz_3.0.0+ds-3_amd64.changes REJECTED

2015-12-03 Thread Graham Inggs
Hi Jerome On 3 December 2015 at 19:53, Jerome BENOIT wrote: > Please let me know what I may do to solve this issue. > Thanks in advance, > Jerome I don't think you need to do anything. Andreas just needs to do regenerate his orig.tar.xz from the pristine-tar branch you fixed recently, or do a

Re: normaliz_3.0.0+ds-3_amd64.changes REJECTED

2015-12-03 Thread Jerome BENOIT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello All: Please let me know what I may do to solve this issue. Thanks in advance, Jerome On 02/12/15 11:21, Debian FTP Masters wrote: > > > normaliz_3.0.0+ds-3.dsc: Invalid size hash for normaliz_3.0.0+ds.orig.tar.xz: > According to the control

Processed: Re: mathgl: Fails to build with GSL 2

2015-12-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch fixed-upstream Bug #805801 [src:mathgl] mathgl: Fails to build with GSL 2 Added tag(s) patch and fixed-upstream. -- 805801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#805829: r-cran-gsl: Fails to build with GSL 2

2015-12-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch fixed-upstream Bug #805829 [src:r-cran-gsl] r-cran-gsl: Fails to build with GSL 2 Added tag(s) fixed-upstream and patch. -- 805829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805829 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

Fwd: Re: J

2015-12-02 Thread 02o3ddj...@q.com
- Original Message - Sent: Wed, 02 Dec 2015 20:41:07 -0500 (EST) Subject: J YOUR TRUST IS NEEDED PLEASE -- 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: normaliz_3.0.0+ds-3_amd64.changes REJECTED

2015-12-02 Thread Jerome BENOIT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello: On 02/12/15 11:21, Debian FTP Masters wrote: > > > normaliz_3.0.0+ds-3.dsc: Invalid size hash for normaliz_3.0.0+ds.orig.tar.xz: > According to the control file the size hash should be 496120, The already uploaded source ball has this size a

Processed: re: mathgl: FTBFS: json/Backend.hpp:6:1: error: expected class-name before '{' token

2015-11-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 803312 +patch Bug #803312 [src:mathgl] mathgl: FTBFS: json/Backend.hpp:6:1: error: expected class-name before '{' token Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 803312: http://bugs

Processed: Re: Bug#806382: opengm: FTBFS on x32: Could NOT find HDF5

2015-11-26 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #806382 [src:opengm] opengm: FTBFS on x32: Could NOT find HDF5 Severity set to 'important' from 'serious' -- 806382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806382 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Processed: Re: libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz

2015-11-24 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.9.0-2 Bug #799340 {Done: Alastair McKinstry } [libgetdata-doc] libgetdata-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/man/man3/gd_frameoffset.3.gz Marked as found in versions libgetdata/0.9.0-2; no longer marked as fixed in ver

Processed: Re: Bug#805893: clblas: add -mxgot option to CFLAGS and CXXFLAGS for mips*64{el}

2015-11-24 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:clblas 2.8+ds1-1 Bug #805893 [src:clblash] clblas: add -mxgot option to CFLAGS and CXXFLAGS for mips*64{el} Warning: Unknown package 'src:clblash' Bug reassigned from package 'src:clblash' to 'src:clblas'. No longer marked as found in versions clblas

Re: Bug#805893: clblas: add -mxgot option to CFLAGS and CXXFLAGS for mips*64{el}

2015-11-24 Thread Andrei POPESCU
Control: reassign -1 src:clblas 2.8+ds1-1 On Ma, 24 nov 15, 01:12:22, YunQiang Su wrote: > Package: src:clblash > Version:2.8+ds1-1 > > diff -Nru clblas-2.8+ds1/debian/rules clblas-2.8+ds1/debian/rules > --- clblas-2.8+ds1/debian/rules 2015-10-28 23:09:33.0 + > +++ clblas-2.8+ds1/debi

Re: normaliz_3.0.0+ds-2_amd64.changes REJECTED

2015-11-22 Thread Andreas Tille
On Sun, Nov 22, 2015 at 06:04:23AM +0100, Jerome BENOIT wrote: > > I've just run your get-orig-source rule and ended up with a 3rd > > version of the orig.tar.xz. > > I guess re-compressing with uscan is not reproducible (yet?). > > It appeared that tar does no

Re: normaliz_3.0.0+ds-2_amd64.changes REJECTED

2015-11-21 Thread Jerome BENOIT
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Graham: On 22/11/15 08:27, Graham Inggs wrote: > On 22 November 2015 at 07:04, Jerome BENOIT wrote: >> I have just done the dirty manoeuvre and some checks: >> it should be ok now. > > It looks OK to me. Shall I go ahead and upload? Yeas, pl

Re: normaliz_3.0.0+ds-2_amd64.changes REJECTED

2015-11-21 Thread Graham Inggs
On 22 November 2015 at 07:04, Jerome BENOIT wrote: > I have just done the dirty manoeuvre and some checks: > it should be ok now. It looks OK to me. Shall I go ahead and upload? -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.de

Re: normaliz_3.0.0+ds-2_amd64.changes REJECTED

2015-11-21 Thread Jerome BENOIT
gt;> 1] ` ./debian/rules get-orig-source ' gives the one in the git; >> 2] the one in the archive is certainly derive from the git itself. >> >> Do I miss something here ? >> What is the best way to fix this ? > > I've just run your get-orig-source rule

Re: normaliz_3.0.0+ds-2_amd64.changes REJECTED

2015-11-21 Thread Jerome BENOIT
gt;> 1] ` ./debian/rules get-orig-source ' gives the one in the git; >> 2] the one in the archive is certainly derive from the git itself. >> >> Do I miss something here ? >> What is the best way to fix this ? > > I've just run your get-orig-source rule

Re: normaliz_3.0.0+ds-2_amd64.changes REJECTED

2015-11-21 Thread Graham Inggs
derive from the git itself. > > Do I miss something here ? > What is the best way to fix this ? I've just run your get-orig-source rule and ended up with a 3rd version of the orig.tar.xz. I guess re-compressing with uscan is not reproducible (yet?). So yes, the faulty one is in

<    5   6   7   8   9   10   11   12   13   14   >