Processing of woo_1.0-1_amd64.changes

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

woo_1.0-1_amd64.changes is NEW

2015-08-08 Thread Debian FTP Masters
binary:python-woo is NEW. binary:python3-woo is NEW. source:woo 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.

Processed: your mail

2015-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: tags 749921 +wontfix Bug #749921 [src:vtk6] Provide symbol file Added tag(s) wontfix. fixed 773380 6.2.0+dfsg1-2 Bug #773380 [libvtk6.1] Bogus description in d/control There is no source info for the package 'libvtk6.1' at version '6.2.0+dfsg1-2'

Processed: your mail

2015-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: notfixed 750200 6.2.0+dfsg1-2 Bug #750200 [vtk6] Do not hardcode tcl version No longer marked as fixed in versions vtk6/6.2.0+dfsg1-2. thanks Stopping processing here. Please contact me if you need assistance. -- 750200:

Bug#749921: marked as done (Provide symbol file)

2015-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 8 Aug 2015 09:24:04 +0200 with message-id CALF6qJnF=y57xam4yddnc+u_zaswmongjj7gmrpv0uvhhcb...@mail.gmail.com and subject line has caused the Debian Bug report #749921, regarding Provide symbol file to be marked as done. This means that you claim that the problem has been

Bug#750171: marked as done (Get rid of libvtk6)

2015-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 8 Aug 2015 09:24:04 +0200 with message-id CALF6qJnF=y57xam4yddnc+u_zaswmongjj7gmrpv0uvhhcb...@mail.gmail.com and subject line has caused the Debian Bug report #750171, regarding Get rid of libvtk6 to be marked as done. This means that you claim that the problem has been

Bug#750200: marked as done (Do not hardcode tcl version)

2015-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 8 Aug 2015 09:24:04 +0200 with message-id CALF6qJnF=y57xam4yddnc+u_zaswmongjj7gmrpv0uvhhcb...@mail.gmail.com and subject line has caused the Debian Bug report #750200, regarding Do not hardcode tcl version to be marked as done. This means that you claim that the problem

Bug#773380: marked as done (Bogus description in d/control)

2015-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 8 Aug 2015 09:24:04 +0200 with message-id CALF6qJnF=y57xam4yddnc+u_zaswmongjj7gmrpv0uvhhcb...@mail.gmail.com and subject line has caused the Debian Bug report #773380, regarding Bogus description in d/control to be marked as done. This means that you claim that the

apertium-af-nl_0.2.0~r57554-1_amd64.changes REJECTED

2015-08-08 Thread Thorsten Alteholz
Hi Kartik, please add the missing license of apertium-af-nl-0.2.0~r57554/paper/linguho.sty to your debian/copyright. Thanks! Thorsten === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns.

apertium-cy-en_0.1.1~r57554-1_amd64.changes ACCEPTED into experimental, experimental

2015-08-08 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 03 Aug 2015 09:59:34 +0530 Source: apertium-cy-en Binary: apertium-cy-en Architecture: source all Version: 0.1.1~r57554-1 Distribution: experimental Urgency: low Maintainer: Debian Science Team

apertium-br-fr_0.5.0~r61325-1_amd64.changes ACCEPTED into unstable, unstable

2015-08-08 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 01 Aug 2015 20:24:04 +0530 Source: apertium-br-fr Binary: apertium-br-fr Architecture: source all Version: 0.5.0~r61325-1 Distribution: unstable Urgency: low Maintainer: Debian Science Team

octomap_1.6.8+dfsg-2.1_amd64.changes ACCEPTED into unstable, unstable

2015-08-08 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 05 Aug 2015 15:36:45 +0200 Source: octomap Binary: liboctomap1.6v5 octomap-tools liboctomap-dev liboctomap1.6v5-dbg libdynamicedt3d1.6 libdynamicedt3d-dev libdynamicedt3d1.6-dbg liboctovis1.6v5 liboctovis-dev

ipe_7.1.4-2.1_amd64.changes ACCEPTED into unstable, unstable

2015-08-08 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 05 Aug 2015 12:02:06 +0200 Source: ipe Binary: ipe libipe7.1.4v5 libipe-dev Architecture: source amd64 Version: 7.1.4-2.1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Processed: user debian...@lists.debian.org, usertagging 794621, affects 794621, usertagging 793961 ...

2015-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). usertags 794621 piuparts Usertags were: piuparts. Usertags are now: piuparts. affects 794621 + ecatools libecasoundc-dev Bug #794621

Bug#791079: marked as done (ipe: library transition may be needed when GCC 5 is the default)

2015-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2015 10:00:38 + with message-id e1zo0ve-0003t5...@franck.debian.org and subject line Bug#791079: fixed in ipe 7.1.4-2.1 has caused the Debian Bug report #791079, regarding ipe: library transition may be needed when GCC 5 is the default to be marked as done. This

Bug#791221: marked as done (octomap: library transition may be needed when GCC 5 is the default)

2015-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2015 10:00:56 + with message-id e1zo0vw-00041x...@franck.debian.org and subject line Bug#791221: fixed in octomap 1.6.8+dfsg-2.1 has caused the Debian Bug report #791221, regarding octomap: library transition may be needed when GCC 5 is the default to be marked

Re: apertium-af-nl_0.2.0~r57554-1_amd64.changes REJECTED

2015-08-08 Thread Kartik Mistry
On Sat, Aug 8, 2015 at 3:30 PM, Thorsten Alteholz ftpmas...@ftp-master.debian.org wrote: please add the missing license of apertium-af-nl-0.2.0~r57554/paper/linguho.sty to your debian/copyright. Oops! Should I put complete text of http://www.latex-project.org/lppl.txt (LPPL)? -- Kartik

Re: apertium-af-nl_0.2.0~r57554-1_amd64.changes REJECTED

2015-08-08 Thread Thorsten Alteholz
On Sat, 8 Aug 2015, Kartik Mistry wrote: ftpmas...@ftp-master.debian.org wrote: please add the missing license of apertium-af-nl-0.2.0~r57554/paper/linguho.sty to your debian/copyright. Oops! Should I put complete text of http://www.latex-project.org/lppl.txt (LPPL)? Yes, please.

Bug#792625: Fwd: Fwd: Re: multiarch = same and different date-entries in generated man page of i32/i64

2015-08-08 Thread Roelof Berg
Possibly a help2man https://bugs.debian.org/787444 version below 1.47.1 is used on the build server and help2man doesn't support SOURCE_DATE_EPOCH before this date. (See: https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal). I'm not familiar with the debian automated build

How can I examine the Debian build toolchain being used for my package ?

2015-08-08 Thread Roelof Berg
Hi, I'm new to Debian maintain 'Limereg' in DebSci. What would be the best way to examine the Debian build toolchain being used for a released package ? I need to find out the version of help2man being used for fixing the bugs below. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792624