Re: PyViennaCL next upload

2014-05-05 Thread Andreas Tille
Hi Anton, On Tue, May 06, 2014 at 08:00:14AM +0200, Anton Gladky wrote: > Hi Toby, > > as far as I know Andreas Tille proposed a nice and really necessary tool > to exclude and repack source tarballs [1], [2] (CC-ing him). But, it seems, > it is not yet in uscan (sorry, I may be wrong). Files-Ex

Re: PyViennaCL next upload

2014-05-05 Thread Anton Gladky
Hi Toby, as far as I know Andreas Tille proposed a nice and really necessary tool to exclude and repack source tarballs [1], [2] (CC-ing him). But, it seems, it is not yet in uscan (sorry, I may be wrong). I would also strongly recommend you to implement autotests using DEP-8 [3]. An example for

Processing of tiemu_3.03-nogdb+dfsg-2.1_amd64.changes

2014-05-05 Thread Debian FTP Masters
tiemu_3.03-nogdb+dfsg-2.1_amd64.changes uploaded successfully to localhost along with the files: tiemu_3.03-nogdb+dfsg-2.1_amd64.deb tiemu_3.03-nogdb+dfsg-2.1.dsc tiemu_3.03-nogdb+dfsg-2.1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org) -- deb

Processed: tiemu: diff for NMU version 3.03-nogdb+dfsg-2.1

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 746086 + patch Bug #746086 [src:tiemu] tiemu: FTBFS: configure: error: Package requirements (ticalcs2 >= 1.0.7) were not met Added tag(s) patch. > tags 746086 + pending Bug #746086 [src:tiemu] tiemu: FTBFS: configure: error: Package requirem

Bug#746086: tiemu: diff for NMU version 3.03-nogdb+dfsg-2.1

2014-05-05 Thread dai
tags 746086 + patch tags 746086 + pending thanks Dear maintainer, I've prepared an NMU for tiemu (versioned as 3.03-nogdb+dfsg-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. -- Regards, dai GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839

armadillo_4.300.0+dfsg-1_amd64.changes ACCEPTED into unstable

2014-05-05 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 05 May 2014 22:52:03 -0400 Source: armadillo Binary: libarmadillo-dev libarmadillo4 Architecture: source amd64 Version: 1:4.300.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

Processing of armadillo_4.300.0+dfsg-1_amd64.changes

2014-05-05 Thread Debian FTP Masters
armadillo_4.300.0+dfsg-1_amd64.changes uploaded successfully to localhost along with the files: libarmadillo-dev_4.300.0+dfsg-1_amd64.deb libarmadillo4_4.300.0+dfsg-1_amd64.deb armadillo_4.300.0+dfsg-1.dsc armadillo_4.300.0+dfsg.orig.tar.gz armadillo_4.300.0+dfsg-1.diff.gz Greetings,

Re: Comments regarding pyviennacl_1.0.1-1_amd64.changes

2014-05-05 Thread Toby St Clere Smithe
Hi Thorsten, Thorsten Alteholz writes: > On Mon, 5 May 2014, Toby St Clere Smithe wrote: >> I know you have the final say here, but the same document[1], under >> seciont 6.7.8.2 point 3 makes the converse point that the orig tarball >> "should, except where impossible for legal reasons, preserve

PyViennaCL next upload

2014-05-05 Thread Toby St Clere Smithe
Hi Anton, further to the discussion earlier, over the next days I'm going to collect together a couple of bug fixes, make a new upstream release, and also do the repackaging. Then would you be happy to sponsor a new upload? Also, I would still like to learn more about this new tool that you and T

[sponsor needed] fcl - Flexible Collision Library

2014-05-05 Thread Jose Luis Rivero
Hi all: I would like to ask for sponsoring on a new package, fcl. Leo started the work and I'm finishing the packaging. Description, in fcl project own words: """ FCL is a collision and proximity library that integrates several techniques for fast and accurate collision checking and proximity com

pyviennacl_1.0.1-1_amd64.changes ACCEPTED into unstable, unstable

2014-05-05 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 10 Mar 2014 18:31:51 + Source: pyviennacl Binary: python-pyviennacl python3-pyviennacl pyviennacl-doc Architecture: source amd64 all Version: 1.0.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Scie

Re: Comments regarding pyviennacl_1.0.1-1_amd64.changes

2014-05-05 Thread Thorsten Alteholz
Hi Toby, On Mon, 5 May 2014, Toby St Clere Smithe wrote: I know you have the final say here, but the same document[1], under seciont 6.7.8.2 point 3 makes the converse point that the orig tarball "should, except where impossible for legal reasons, preserve the entire building and portablility in

Re: Comments regarding pyviennacl_1.0.1-1_amd64.changes

2014-05-05 Thread Toby St Clere Smithe
Hi Anton, Anton Gladky writes: > 2014-05-05 21:18 GMT+02:00 Toby St Clere Smithe : >> But, of course, if you think it is imperative that they are removed, >> then I shall do so! > > Ok, I would agree then with Thorsten. Especially, when we get this new tool > (debian/copyright) this process will

Re: Comments regarding pyviennacl_1.0.1-1_amd64.changes

2014-05-05 Thread Anton Gladky
2014-05-05 21:18 GMT+02:00 Toby St Clere Smithe : > But, of course, if you think it is imperative that they are removed, > then I shall do so! Ok, I would agree then with Thorsten. Especially, when we get this new tool (debian/copyright) this process will be much easier. Thorsten, could you pleas

Re: Comments regarding pyviennacl_1.0.1-1_amd64.changes

2014-05-05 Thread Toby St Clere Smithe
Hi Thorsten, Thorsten Alteholz writes: > On Mon, 5 May 2014, Toby St Clere Smithe wrote: >> Since the source package is built directly from these upstream sources >> (no need to repackage, because the copyright situation is OK), > > but in [1] there are other reasons mentioned to repackage. > Rem

Re: Comments regarding pyviennacl_1.0.1-1_amd64.changes

2014-05-05 Thread Thorsten Alteholz
Hi Toby, On Mon, 5 May 2014, Toby St Clere Smithe wrote: Since the source package is built directly from these upstream sources (no need to repackage, because the copyright situation is OK), but in [1] there are other reasons mentioned to repackage. Removing 4200 files out of 4300 seems to be

Bug#747109: getdp: FTBFS with make 4

2014-05-05 Thread Julien Cristau
Source: getdp Version: 2.4.2-1 Severity: serious Justification: fails to build from source (but built successfully in the past) User: sriva...@debian.org Usertags: transition-make-4.0 Tags: patch Hi, your package no longer builds from source due to a bug in debian/rules that gets triggered with m

Processed: your mail

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 731823 -1 Bug #731823 [libvtk-java] major version 51 is newer than 50, the highest major version supported by this compiler. Bug 731823 cloned as bug 747108 > reassign -1 libvtk6-java Bug #747108 [libvtk-java] major version 51 is newer than

clasp 3.0.4-1 MIGRATED to testing

2014-05-05 Thread Debian testing watch
FYI: The status of the clasp source package in Debian's testing distribution has changed. Previous version: 3.0.3-1 Current version: 3.0.4-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 l

Bug#730869: marked as done (Please upgrade python-pywcs from 1.11 to 1.10.1 or better)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 15:48:27 + with message-id and subject line Bug#730869: fixed in python-pywcs 1.12-1 has caused the Debian Bug report #730869, regarding Please upgrade python-pywcs from 1.11 to 1.10.1 or better to be marked as done. This means that you claim that the probl

python-pywcs_1.12-1_amd64.changes ACCEPTED into unstable

2014-05-05 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 May 2014 15:09:02 +0200 Source: python-pywcs Binary: python-pywcs Architecture: source amd64 Version: 1.12-1 Distribution: unstable Urgency: low Maintainer: Debian Science Maintainers Changed-By: Ole Streicher

Processing of python-pywcs_1.12-1_amd64.changes

2014-05-05 Thread Debian FTP Masters
python-pywcs_1.12-1_amd64.changes uploaded successfully to localhost along with the files: python-pywcs_1.12-1_amd64.deb python-pywcs_1.12-1.dsc python-pywcs_1.12.orig.tar.gz python-pywcs_1.12-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host franck.debian.org)

Processed: Reassign

2014-05-05 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 746493 libjogl2-java Bug #746493 [scilab] scilab: scilab fails to launch on powerpc Bug reassigned from package 'scilab' to 'libjogl2-java'. No longer marked as found in versions scilab/5.5.0-2. Ignoring request to alter fixed versions of

Re: Comments regarding pyviennacl_1.0.1-1_amd64.changes

2014-05-05 Thread Toby St Clere Smithe
Hi Thorsten, (I lost power on my laptop, so lost your e-mail and have to reply like this..) If you have a look at debian/rules, you'll see that in fact I do use the Debian-provided Boost. And there is a good reason why the source package contains a subset of Boost: PyViennaCL is written for a gen

Bug#746772: marked as done (dune-grid: FTBFS on mipsel)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 14:15:18 +0200 with message-id <536780d6.5060...@debian.org> and subject line Re: Bug#746772: dune-grid: FTBFS on mipsel has caused the Debian Bug report #746772, regarding dune-grid: FTBFS on mipsel to be marked as done. This means that you claim that the probl

Bug#746772: dune-grid: FTBFS on mipsel

2014-05-05 Thread Ansgar Burchardt
On 05/03/2014 14:11, Ivo De Decker wrote: > The binnmu of dune-grid on mipsel failed twice: > > https://buildd.debian.org/status/logs.php?pkg=dune-grid&arch=mipsel mayer.debian.org has only 1 GB RAM (+ 0.5 GB swap), but is configured to build in parallel with 2 processes. dune-grid however needs

How to boost your app downloads to maximize installs

2014-05-05 Thread Michael from PressPad
You can boost downloads of your app by joining the exclusive club of the 40%... How To Boost The Number of Installs of Your Digital Magazine Mobile App http://blog.presspadapp.com/boost-number-installs-digital-magazine-mobile-app ===

Comments regarding pyviennacl_1.0.1-1_amd64.changes

2014-05-05 Thread Thorsten Alteholz
Dear Maintainer, is there a reason that most of your package contains of a copy of Boost? Couldn't you use the version already in the archive? Thorsten -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailma

Bug#735807: marked as done (salome-kernel: FTBFS: FATAL ERROR: some mandatory products are missing)

2014-05-05 Thread Debian Bug Tracking System
Your message dated Mon, 05 May 2014 10:35:34 + with message-id and subject line Bug#735807: fixed in salome-kernel 6.5.0-8 has caused the Debian Bug report #735807, regarding salome-kernel: FTBFS: FATAL ERROR: some mandatory products are missing to be marked as done. This means that you claim

salome-kernel_6.5.0-8_amd64.changes ACCEPTED into unstable

2014-05-05 Thread Debian FTP Masters
Mapping sid to unstable. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 05 May 2014 11:18:21 +0200 Source: salome-kernel Binary: salome-kernel salome-kernel-dev salome-kernel-doc salome-kernel-dbg Architecture: source amd64 all Version: 6.5.0-8 Distribution: sid U

Processing of salome-kernel_6.5.0-8_amd64.changes

2014-05-05 Thread Debian FTP Masters
salome-kernel_6.5.0-8_amd64.changes uploaded successfully to localhost along with the files: salome-kernel_6.5.0-8_amd64.deb salome-kernel-dev_6.5.0-8_amd64.deb salome-kernel-dbg_6.5.0-8_amd64.deb salome-kernel-doc_6.5.0-8_all.deb salome-kernel_6.5.0-8.dsc salome-kernel_6.5.0-8.diff.gz

Processing of salome-kernel_6.5.0-8_amd64.changes

2014-05-05 Thread Debian FTP Masters
salome-kernel_6.5.0-8_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: salome-kernel_6.5.0-8_amd64.deb salome-kernel-dev_6.5.0-8_amd64.deb salome-kernel-dbg_6.5.0-8_amd64.deb salome-kernel-doc_6.5.0-8_all.deb salome-kernel_6.5.0-8.dsc salome-kernel_6.5