Bug#783158: marked as done (RFS: mtpolicyd/1.18 [ITP] -- modular policy daemon for postfix)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 16:30:57 +
with message-id 
and subject line closing RFS: mtpolicyd/1.18 [ITP] -- modular policy daemon for 
postfix
has caused the Debian Bug report #783158,
regarding RFS: mtpolicyd/1.18 [ITP] -- modular policy daemon for postfix
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.)


-- 
783158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "mtpolicyd"

 * Package name: mtpolicyd
   Version : 1.18
   Upstream Author : Markus Benning 
 * URL : https://mtpolicyd.org/
 * License : GPLv2
   Section : perl

It builds those binary packages:

  mtpolicyd  - modular policy daemon for postfix

To access further information about this package, please visit the following 
URL:

http://mentors.debian.net/package/mtpolicyd


Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/m/mtpolicyd/mtpolicyd_1.18.dsc

More information about hello can be obtained from http://www.mtpolicyd.org.

Changes since the last upload:

commit 29fd63d02bb0d14acd6f364a512030f86155ff17
Author: Markus Benning 
Date:   Wed Apr 22 23:02:33 2015 +0200

even more lintian fixes

commit 3583c91cbc288e3bb124485f92b8e035884a58d1
Author: Markus Benning 
Date:   Wed Apr 22 22:39:20 2015 +0200

add DEBHELPER comments to maintainer scripts

commit 264f54b2b7a3ccd9de75bfbcebe2c851cffb721c
Author: Markus Benning 
Date:   Wed Apr 22 22:33:59 2015 +0200

fix some spelling errors


Regards,
 Markus Benning


-- 
Markus Benning, https://markusbenning.de/
--- End Message ---
--- Begin Message ---
Package mtpolicyd has been removed from mentors.--- End Message ---

Re: Bug#797794: marked as done (RFS: gnss-sdr/0.0.6-1 [ITP])

[Alex Vong]

Hi Jeffrey,

What sort of bug reports are you receiving? If their titles are in the
form "Bug#: foolishbar (RFS: blablabla)", then they should
belong to the debian-mentors mailing list. I guess the type of bug
reports you are receiving should show what mailing list they are
belonging to.

Cheers,
Alex

2015-09-23 0:41 GMT+08:00, Jeffrey Walton :
> For some reason, I seem to receive a copy of everyone's bug reports.
>
> I tried to unsubscribe by sending an unsubscribe email to
> submit-requ...@bugs.debian.org, but nothing happened. (-REQUEST@
> is supposed to be the address to use).
>
> Why am I receiving everyone's bugs, and how do I stop it?
>
> (There's at least 9 different lists that match a search for "bug" at
> https://www.debian.org/MailingLists/unsubscribe, and I'm not sure
> which one(s) I have been added to).
>
> -- Forwarded message --
> From: Debian Bug Tracking System 
> Date: Tue, Sep 22, 2015 at 12:33 PM
> Subject: Bug#797794: marked as done (RFS: gnss-sdr/0.0.6-1 [ITP])
> To: Bart Martens 
>
> Your message dated Tue, 22 Sep 2015 16:30:57 +
> with message-id 
> and subject line closing RFS: gnss-sdr/0.0.6-1 [ITP]
> has caused the Debian Bug report #797794,
> regarding RFS: gnss-sdr/0.0.6-1 [ITP]
> 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.)
>
> --
> 797794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797794
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
> -- Forwarded message --
> From: Carles Fernandez 
> To: sub...@bugs.debian.org
> Cc:
> Date: Wed, 2 Sep 2015 16:56:48 +0200
> Subject: RFS: gnss-sdr/0.0.6-1 [ITP]
> Package: sponsorship-requests
> Severity: wishlist
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "gnss-sdr"
>
>  * Package name: gnss-sdr
>Version : 0.0.6-1
>Upstream Author : Carles Fernandez, carles.fernan...@cttc.es
>  * URL : https://github.com/gnss-sdr/gnss-sdr
>  * License : GPL v3
>Section : hamradio
>
>   It builds those binary packages:
>
> gnss-sdr   - Global Navigation Satellite Systems Software Defined
> Receiver.
>
>   To access further information about this package, please visit the
> following URL:
>
>   http://mentors.debian.net/package/gnss-sdr
>
>
>   Alternatively, one can download the package with dget using this command:
>
> dget -x
> http://mentors.debian.net/debian/pool/main/g/gnss-sdr/gnss-sdr_0.0.6-1.dsc
>
>   More information about gnss-sdr can be obtained from http://gnss-sdr.org
>
>   Regards,
>Carles Fernandez
>

Bug#799768: RFS: ismrmrd/1.3.1-1

[Gianfranco Costamagna]

I can sponsor the package with that lintian warning.

as said before the package should be lintian clean as long as lintian is 
correct.

But overriding lintian is wrong, because it is still an issue.


If it is ok for you I would prefer a package with a lintian warning.


cheers,


Gianfranco

Sent from Yahoo Mail on Android

From:"Ghislain Vaillant" 
Date:Tue, 22 Sep, 2015 at 19:33
Subject:Bug#799768: RFS: ismrmrd/1.3.1-1


On 22/09/15 17:32, Gianfranco Costamagna wrote:
> I would appreciate a lintian warning instead of a broken documentation
>
>
> e.g. look at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736360
>
>
> G.


>

Should the warning be overridden for the purpose or the review? Apart 
from that, I am ready to push a final version.

I have to say that the lucene++ package you quoted really inspired from 
a packaging standpoint. Now the ismrmrd packaging feels really clean.

Ghis

Bug#799093: marked as done (RFS: chrony/1.31.1-2)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 21:48:35 +0200
with message-id <5601b093.7090...@debian.org>
and subject line Re: Bug#799093: RFS: chrony/1.31.1-2
has caused the Debian Bug report #799093,
regarding RFS: chrony/1.31.1-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.)


-- 
799093: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Hello Paul,

Could you please take a look at chrony 1.31.1-2¹?
In 1.31.1-1, the NEWS.Debian file wasn’t copied by dh_installchangelogs
to /usr/share/doc/chrony because it seems that tool can’t cope with that
filename. So I renamed it to NEWS, and also removed an unnecessary call to
dh_installchangelogs in d/rules. Consequently, apt-listchanges is now
able the read that file at install time.

Cheers,
Vincent

¹ dget -x 
http://mentors.debian.net/debian/pool/main/c/chrony/chrony_1.31.1-2.dsc
I also pushed the changes to the git repository.


Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Hi Vincent,

On 21-09-15 23:27, Vincent Blut wrote:
> I just pushed the necessary stuff to the git tree. I will upload to
> mentors.d.n ASAP.

Build, signed & uploaded.

Paul

PS: may I suggest packaging the latest version of chrony for
experimental shortly?





signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#799205: RFS: eviacam/2.0.1-5 [ITP] -- webcam based mouse emulator

[Gianfranco Costamagna]

nope, but maybe autogenerating one starting from help2man and pushing upstream 
might be worth the effort


about fortify you need to be sure the code doesn't override CPPFLAGS CFLAGS and 
LDFLAGS (or uses them indeed)

IIRC that warning is about CPPFLAGS


cheers,


G.

Sent from Yahoo Mail on Android

From:"Alex Vong" 
Date:Tue, 22 Sep, 2015 at 20:21
Subject:Bug#799205: RFS: eviacam/2.0.1-5 [ITP] -- webcam based mouse emulator

Hi Cesar and Gianfranco,

I have fixed 2 lintian warnings about `debian/copyright', it is in the
attachment. They are `dep5-copyright-license-name-not-unique' and
`old-fsf-address-in-copyright-file'. I think it would be great to
update the address of FSF in the source files as well.

I notice there are some extra warnings when I run:
    $ lintian -EviIL +pedantic ../*.changes

The most important onces are `hardening-no-fortify-functions' and
`binary-without-manpage'. I think `hardening-no-fortify-functions' has
to do with `dpkg-buildflags' in `debian/rules'. About man page, is it
essential?

Cheers,
Alex

2015-09-22 22:07 GMT+08:00, Gianfranco Costamagna
:


> Hi again,
> some lintian stuff
> http://debomatic-amd64.debian.net/distribution#unstable/eviacam/2.0.1-5/lintian
>
> cheers,
>
>
> G.
>
>

Bug#745126: RFS: passwordsafe/0.95.1+dfsg-1

[Eugene Zhukov]

Hi,
I took a peek and didn't find get-orig-source in d/rules. d/watch has link to
github, while pwsafe.org links to sourceforge.

Bug#799655: RFS: arrayfire/3.1.1+dfsg1-1

[PICCA Frederic-Emmanuel]

I will take care of this.

Cheers

Re: Suspicious file changes in -dbg between old and new packages

[Gianfranco Costamagna]

Hi Niels,



>The debug package needs a strictly equal dependency on the original
>package, such as: "foo (= ${binary:Version})".  That is orthogonal to
>the usage of build-ids (that is, you must use the strictly equal with or
>without build-id based debug paths).


sure, I guess lintian even complains otherwise

>As for the build-id and how it is computed.  It is based on the
>internals of the ELF binary including but not limited to:
>
>* The path where the binaries were compiled
>* The options given to gcc when compiled
>* Time and day, if such are included in the code (__DATE__ macros
>   and such).


So how did it work for Thomas with the previous version installed?

/me is confused :)



cheers,

G.

Re: Suspicious file changes in -dbg between old and new packages

[Gianfranco Costamagna]

Hi Niels,

>If the old and the new binary have the same build-id, they can reuse the
>same debug symbols - regardless of the debug symbols are installed by
>name or by build id. :)

>

so the __TIME__ __DATE__ macros are not used, but *might* be used
and not during the build-id computation, but during build, right?
(I mean, it is a side-effect, not a requirement)

>So if Thomas can use the old foo with the new foo-dbg, then I guess:
>
>* foo-dbg is missing the strict mandatory dependency (or Thomas passed
>   force options to dpkg), and
>* Thomas built it in the same path as the previous location with the
>   same options, and
>* upstream does not use any time based macros?
>
>
>On the plus side, this would imply that the ELF binaries are build
>reproducibly. :)


Yes, I fully agree, this was the same conclusion.
I guess it is a good empiric method for knowing if the build is reproducible :)


thanks a lot!

(that is a field where I don't touch if it isn't broken, and usually it worked 
so
well that I never had to touch it :D )

cheers,

G.

Re: Suspicious file changes in -dbg between old and new packages

[Niels Thykier]

On 2015-09-22 08:41, Gianfranco Costamagna wrote:
> Hi Niels,
> 
> [...]
>> As for the build-id and how it is computed.  It is based on the
>> internals of the ELF binary including but not limited to:
>>
>> * The path where the binaries were compiled
>> * The options given to gcc when compiled
>> * Time and day, if such are included in the code (__DATE__ macros
>>   and such).
> 
> 
> So how did it work for Thomas with the previous version installed?
> 
> /me is confused :)
> 
> cheers,
> 
> G.
> 

If the old and the new binary have the same build-id, they can reuse the
same debug symbols - regardless of the debug symbols are installed by
name or by build id. :)

So if Thomas can use the old foo with the new foo-dbg, then I guess:

 * foo-dbg is missing the strict mandatory dependency (or Thomas passed
   force options to dpkg), and
 * Thomas built it in the same path as the previous location with the
   same options, and
 * upstream does not use any time based macros?


On the plus side, this would imply that the ELF binaries are build
reproducibly. :)

Thanks,
~Niels

Re: Suspicious file changes in -dbg between old and new packages

[Gianfranco Costamagna]

Hi Thomas,



>And why does it still work when i install back 1.4.0-2 ?




well, if -2 and -3 didn't change symbols (e.g.  you didn't patch the source 
code),
why shouldn't it work?

(I'm not sure to know how exactly the build.ids are mapped to the binary code, 
but I guess
they work as long as the symbols table don't change)

Re: Suspicious file changes in -dbg between old and new packages

[Niels Thykier]

On 2015-09-22 07:30, Gianfranco Costamagna wrote:
> Hi Thomas,
> 
> 
> 
>> And why does it still work when i install back 1.4.0-2 ?
> 
> 
> 
> 
> well, if -2 and -3 didn't change symbols (e.g.  you didn't patch the source 
> code),
> why shouldn't it work?
> 
> (I'm not sure to know how exactly the build.ids are mapped to the binary 
> code, but I guess
> they work as long as the symbols table don't change)
> 

The debug package needs a strictly equal dependency on the original
package, such as: "foo (= ${binary:Version})".  That is orthogonal to
the usage of build-ids (that is, you must use the strictly equal with or
without build-id based debug paths).

As for the build-id and how it is computed.  It is based on the
internals of the ELF binary including but not limited to:

 * The path where the binaries were compiled
 * The options given to gcc when compiled
 * Time and day, if such are included in the code (__DATE__ macros
   and such).

Thanks,
~Niels





signature.asc
Description: OpenPGP digital signature

Bug#799565: marked as done (RFS: linuxbrew-wrapper/20150804-2 -- missing package manager for linux)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 06:16:25 +
with message-id <1442902585.10030.0.ca...@gmail.com>
and subject line closing bug because RFS complete
has caused the Debian Bug report #799565,
regarding RFS: linuxbrew-wrapper/20150804-2 -- missing package manager for linux
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.)


-- 
799565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

  I am looking for a sponsor for my package "linuxbrew-wrapper"

 * Package name: linuxbrew-wrapper
   Version : 20150804-2 
   Upstream Author : Linuxbrew contributors
 * URL : https://github.com/Homebrew/linuxbrew
 * License : BSD-2-Clause
   Section : utils

  It builds those binary packages:

linuxbrew-wrapper - Missing Package Manager For Linux

  To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/linuxbrew-wrapper


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/l/linuxbrew-wrapper/linuxbrew-wrapper_20150804-2.dsc


  Changes since the last upload:


linuxbrew-wrapper (20150804-2) unstable; urgency=low

  * debian/bin/linuxbrew: 
+ Fix: not ignoring linuxbrew arguments when first time running.
+ Rewrite last part, which makes the wrapper script usable outside
  of this Debian package.
  * d/rules: add get-orig-source target.
  * Fixed lintian warning 
"script-not-executable usr/lib/linuxbrew-wrapper/install".

  Regards,
   Zhou Mo


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
closing bug because RFS complete



signature.asc
Description: This is a digitally signed message part
--- End Message ---

Fwd: Bug#797794: marked as done (RFS: gnss-sdr/0.0.6-1 [ITP])

[Jeffrey Walton]

For some reason, I seem to receive a copy of everyone's bug reports.

I tried to unsubscribe by sending an unsubscribe email to
submit-requ...@bugs.debian.org, but nothing happened. (-REQUEST@
is supposed to be the address to use).

Why am I receiving everyone's bugs, and how do I stop it?

(There's at least 9 different lists that match a search for "bug" at
https://www.debian.org/MailingLists/unsubscribe, and I'm not sure
which one(s) I have been added to).

-- Forwarded message --
From: Debian Bug Tracking System 
Date: Tue, Sep 22, 2015 at 12:33 PM
Subject: Bug#797794: marked as done (RFS: gnss-sdr/0.0.6-1 [ITP])
To: Bart Martens 

Your message dated Tue, 22 Sep 2015 16:30:57 +
with message-id 
and subject line closing RFS: gnss-sdr/0.0.6-1 [ITP]
has caused the Debian Bug report #797794,
regarding RFS: gnss-sdr/0.0.6-1 [ITP]
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.)

--
797794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

-- Forwarded message --
From: Carles Fernandez 
To: sub...@bugs.debian.org
Cc:
Date: Wed, 2 Sep 2015 16:56:48 +0200
Subject: RFS: gnss-sdr/0.0.6-1 [ITP]
Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "gnss-sdr"

 * Package name: gnss-sdr
   Version : 0.0.6-1
   Upstream Author : Carles Fernandez, carles.fernan...@cttc.es
 * URL : https://github.com/gnss-sdr/gnss-sdr
 * License : GPL v3
   Section : hamradio

  It builds those binary packages:

gnss-sdr   - Global Navigation Satellite Systems Software Defined Receiver.

  To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/gnss-sdr


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/g/gnss-sdr/gnss-sdr_0.0.6-1.dsc

  More information about gnss-sdr can be obtained from http://gnss-sdr.org

  Regards,
   Carles Fernandez


signature.asc
Description: PGP signature

Bug#783935: marked as done (RFS: libphpcpp/1.3.2-1 [ITP] -- C++ library for developing PHP extensions)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 16:30:53 +
with message-id 
and subject line closing RFS: libphpcpp/1.3.2-1 [ITP] -- C++ library for 
developing PHP extensions
has caused the Debian Bug report #783935,
regarding RFS: libphpcpp/1.3.2-1 [ITP] -- C++ library for developing PHP 
extensions
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.)


-- 
783935: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist


  Dear mentors,

  I am looking for a sponsor for my package "libphpcpp"

 * Package name: libphpcpp
   Version : 1.3.2-1
   Upstream Author : Emiel Bruijntjes 
 * URL : http://www.php-cpp.com/
 * License : Apache 2.0
   Section : libs

  It builds those binary packages:

libphpcpp-dev - Headers for PHP-CPP a C++ library for developing PHP 
extensions
libphpcpp1 - C++ library for developing PHP extensions
libphpcpp1-dbg - Debugging symbols for libphpcpp1

  To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/libphpcpp


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/libp/libphpcpp/libphpcpp_1.3.2-1.dsc

  More information about PHP-CPP can be obtained from http://www.php-cpp.com.

  Changes since the last upload:

  libphpcpp (1.3.2-1) unstable; urgency=low

   * Initial release. (Closes: #781154)

  -- Rafal Goslawski   Fri, 1 May 2015 11:30:28 
+0200


  Regards,
   Rafal Goslawski
--- End Message ---
--- Begin Message ---
Package libphpcpp has been removed from mentors.--- End Message ---

Bug#784056: marked as done (RFS: libcdio-paranoia/10.2+0.93+1-1 [ITP] -- upstream split of libcdio-paranoia)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 16:30:57 +
with message-id 
and subject line closing RFS: libcdio-paranoia/10.2+0.93+1-1 [ITP] -- upstream 
split of libcdio-paranoia
has caused the Debian Bug report #784056,
regarding RFS: libcdio-paranoia/10.2+0.93+1-1 [ITP] -- upstream split of 
libcdio-paranoia
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.)


-- 
784056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Package: sponsorship-requests
  Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "libcdio-paranoia"

 * Package name: libcdio-paranoia
   Version : 10.2+0.93+1-1
   Upstream Author : Rocky Bernstein 
 * URL : http://www.gnu.org/software/libcdio/
 * License : GPL-3+
   Section : libs

  It builds those binary packages:

libcdio-cdda2 - library to read and control digital audio CDs
 libcdio-paranoia-dev - library to read digital audio CDs with error correction
(developm
 libcdio-paranoia-utils - Compact Disc Input and Control (sample applications)
 libcdio-paranoia2 - library to read digital audio CDs with error correction

  To access further information about this package, please visit the following
URL:

  http://mentors.debian.net/package/libcdio-paranoia


  Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/libc/libcdio-paranoia
/libcdio-paranoia_10.2+0.93+1-1.dsc

  Changes since the last upload:

  * Upstream libcdio >= 0.90 split of libcdio-paranoia. (Closes: #784029)

  Regards,
   Eric Shattow



-- System Information:
Debian Release: 8.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.0.0-trunk-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Package libcdio-paranoia has been removed from mentors.--- End Message ---

Bug#799092: marked as done (RFS: haxe/1:3.2.0+dfsg-1)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 16:30:57 +
with message-id 
and subject line closing RFS: haxe/1:3.2.0+dfsg-1
has caused the Debian Bug report #799092,
regarding RFS: haxe/1:3.2.0+dfsg-1
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.)


-- 
799092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  I am looking for a sponsor for my package "haxe".
  I'm a member of the Haxe Foundation. I would like to maintain the package
in the long term to improve haxe's debian support.


 * Package name: haxe
   Version : 1:3.2.0+dfsg-1
   Upstream Author : Haxe Foundation
 * URL : http://haxe.org/
 * License : GPLv2+, MIT, LGPLv2+
   Section : devel

  It builds those binary packages:

haxe  - A multi-target universal programming language

  To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/haxe


  Alternatively, one can download the package with dget using this command:

dget -x
http://mentors.debian.net/debian/pool/main/h/haxe/haxe_3.2.0+dfsg-1.dsc

  Changes since the last upload:

haxe (1:3.2.0+dfsg-1) unstable; urgency=low

  * Adopt package.
+ Set maintainer to myself.
  * New upstream version.
+ Update neko version dependency.
  * Remove outdated and discontinued emacs haxe mode.
  * Clean up copyright.
+ Remove entries of removed files.
  * Remove d/watch and get-orig-source target because the archive at Github
is missing submodules.

 -- Andy Li   Wed, 26 Aug 2015 15:01:06 +0800


  Regards,
   Andy Li
--- End Message ---
--- Begin Message ---
Package haxe version 1:3.2.0+dfsg-1 is in unstable now.
https://packages.qa.debian.org/haxe--- End Message ---

Bug#745126: marked as done (RFS: passwordsafe/0.95.1+dfsg-1 [ITP] -- Simple & Secure Password Management)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 16:30:57 +
with message-id 
and subject line closing RFS: passwordsafe/0.95.1+dfsg-1 [ITP] -- Simple & 
Secure Password Management
has caused the Debian Bug report #745126,
regarding RFS: passwordsafe/0.95.1+dfsg-1 [ITP] -- Simple & Secure Password 
Management
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.)


-- 
745126: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745126
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "passwordsafe"

 * Package name: passwordsafe
   Version : 0.93+dfsg-1
   Upstream Author : Rony Shapiro 
 * URL : http://passwordsafe.sourceforge.net/
 * License : Artistic 2.0
   Section : utils

  It builds those binary packages:

passwordsafe - Simple & Secure Password Management
passwordsafe-common - architecture independent files for Password Safe

  To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/passwordsafe


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/p/passwordsafe/passwordsafe_0.93+dfsg-1.dsc

  More information about passwordsafe can be obtained from 
http://www.pwsafe.org/


  Regards,
   Bill Blough
--- End Message ---
--- Begin Message ---
Package passwordsafe has been removed from mentors.--- End Message ---

Bug#797794: marked as done (RFS: gnss-sdr/0.0.6-1 [ITP])

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 16:30:57 +
with message-id 
and subject line closing RFS: gnss-sdr/0.0.6-1 [ITP]
has caused the Debian Bug report #797794,
regarding RFS: gnss-sdr/0.0.6-1 [ITP]
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.)


-- 
797794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

  I am looking for a sponsor for my package "gnss-sdr"

 * Package name: gnss-sdr
   Version : 0.0.6-1
   Upstream Author : Carles Fernandez, carles.fernan...@cttc.es
 * URL : https://github .com/gnss-sdr/gnss-sdr
 * License : GPL v3
   Section : hamradio

  It builds those binary packages:

gnss-sdr   - Global Navigation Satellite Systems Software Defined Receiver.

  To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/gnss-sdr


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/g/gnss-sdr/gnss-sdr_0.0.6-1.dsc

  More information about gnss-sdr can be obtained from http://gnss-sdr 
.org



  Regards,
   Carles Fernandez






signature.asc
Description: Message signed with OpenPGP using GPGMail
--- End Message ---
--- Begin Message ---
Package gnss-sdr version 0.0.6-1 is in NEW now,
and the package at mentors is not newer (2015-09-18) than the package in NEW 
(2015-09-18),
so there is currently no package to sponsor.

https://ftp-master.debian.org/new/gnss-sdr_0.0.6-1.html
https://mentors.debian.net/package/gnss-sdr

Please remove the package from mentors or mark it "needs sponsor = no".
If for some reason you need to replace the package in NEW,
then you can upload an updated package to mentors
and feel free to reopen this RFS 797794 or open a new RFS.--- End Message ---

Bug#799768: RFS: ismrmrd/1.3.1-1

[Gianfranco Costamagna]

>

>I still don't get what the recommended solution is. So far, I have been 
>(wrongly?) following what Lintian suggested to do with embedded jquery.


I would appreciate a lintian warning instead of a broken documentation


e.g. look at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736360


G.

Bug#799205: RFS: eviacam/2.0.1-5 [ITP] -- webcam based mouse emulator

[Alex Vong]

Hi Cesar and Gianfranco,

I have fixed 2 lintian warnings about `debian/copyright', it is in the
attachment. They are `dep5-copyright-license-name-not-unique' and
`old-fsf-address-in-copyright-file'. I think it would be great to
update the address of FSF in the source files as well.

I notice there are some extra warnings when I run:
$ lintian -EviIL +pedantic ../*.changes

The most important onces are `hardening-no-fortify-functions' and
`binary-without-manpage'. I think `hardening-no-fortify-functions' has
to do with `dpkg-buildflags' in `debian/rules'. About man page, is it
essential?

Cheers,
Alex

2015-09-22 22:07 GMT+08:00, Gianfranco Costamagna
:
> Hi again,
> some lintian stuff
> http://debomatic-amd64.debian.net/distribution#unstable/eviacam/2.0.1-5/lintian
>
> cheers,
>
>
> G.
>
>


copyright
Description: Binary data

Re: Bug#797794: marked as done (RFS: gnss-sdr/0.0.6-1 [ITP])

[Jeffrey Walton]

On Tue, Sep 22, 2015 at 1:10 PM, Alex Vong  wrote:
> Hi Jeffrey,
>
> What sort of bug reports are you receiving? If their titles are in the
> form "Bug#: foolishbar (RFS: blablabla)", then they should
> belong to the debian-mentors mailing list. I guess the type of bug
> reports you are receiving should show what mailing list they are
> belonging to.
>
Ah, thanks.

I planned on lurking on Debian-Mentors in hopes of learning a thing or
two. These bug reports are just filling up my INBOX with pretty much
useless fodder. the endless stream of bug reports seems to diverge
from the list's purpose
(https://wiki.debian.org/DebianMentorsFaq#What_is_the_debian-mentors_mailing_list_for.3F).
Shouldn't bug reports go to a different list, like a bug related list?
There's about 9 of them to choose from :)

Anyway, I'm going to unsubscribe and forgo all that knowledge. Sorry about that.

Jeff

Bug#799768: RFS: ismrmrd/1.3.1-1

[Ghislain Vaillant]

On 22/09/15 17:32, Gianfranco Costamagna wrote:

I would appreciate a lintian warning instead of a broken documentation


e.g. look at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736360


G.



Should the warning be overridden for the purpose or the review? Apart 
from that, I am ready to push a final version.


I have to say that the lucene++ package you quoted really inspired from 
a packaging standpoint. Now the ismrmrd packaging feels really clean.


Ghis

Re: Bug#797794: marked as done (RFS: gnss-sdr/0.0.6-1 [ITP])

[Alex Vong]

Hi Jeffrey,

RFS actually stands for Request for Sponsorship. So these endless bug
reports are opened by (mostly) non-Debian-developers who want to get
their packages in Debian, or to upload a new version of existing
packages. Perhaps one day you will subscribe to this list again if you
want to upload package to Debian :)

You can obviously ask questions here and someone will answer you
(subscription is not required). Like this email. <--

Cheers,
Alex

2015-09-23 1:17 GMT+08:00, Jeffrey Walton :
> On Tue, Sep 22, 2015 at 1:10 PM, Alex Vong  wrote:
>> Hi Jeffrey,
>>
>> What sort of bug reports are you receiving? If their titles are in the
>> form "Bug#: foolishbar (RFS: blablabla)", then they should
>> belong to the debian-mentors mailing list. I guess the type of bug
>> reports you are receiving should show what mailing list they are
>> belonging to.
>>
> Ah, thanks.
>
> I planned on lurking on Debian-Mentors in hopes of learning a thing or
> two. These bug reports are just filling up my INBOX with pretty much
> useless fodder. the endless stream of bug reports seems to diverge
> from the list's purpose
> (https://wiki.debian.org/DebianMentorsFaq#What_is_the_debian-mentors_mailing_list_for.3F).
> Shouldn't bug reports go to a different list, like a bug related list?
> There's about 9 of them to choose from :)
>
> Anyway, I'm going to unsubscribe and forgo all that knowledge. Sorry about
> that.
>
> Jeff
>

Bug#745126: RFS: passwordsafe/0.95.1+dfsg-1 [ITP] -- Simple & Secure Password Management

[Bill Blough]

Dear mentors,

  I am still looking for a sponsor for my package "passwordsafe"

 * Package name: passwordsafe
   Version : 0.95.1+dfsg-1
   Upstream Author : Rony Shapiro 
 * URL : http://www.pwsafe.org/
 * License : Artistic 2.0
   Section : utils

  It builds these binary packages:

passwordsafe - Simple & Secure Password Management
passwordsafe-common - architecture independent files for Password Safe

  To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/passwordsafe


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/p/passwordsafe/passwordsafe_0.95.1+dfsg-1.dsc

  More information about passwordsafe can be obtained from http://www.pwsafe.org


  Regards,
   Bill Blough

Bug#799813: RFS: snes9x [ITP] -- Cross-platform SNES emulator

[Sérgio Benjamim]

Package: sponsorship-requests
Severity: wishlist

Hey dear mentors,

Looking for a sponsor for this package:

* Package name : snes9x
  Version  : 1.53+git20150819

  Upstream Author  : Gary Henderson 
 and others
 
* URL  : http://www.snes9x.com/

* License  : non-free/non-commercial
  Programming Lang : C++
  Description  : Cross-platform SNES emulator


Snes9x is a portable, freeware SNES emulator. It has a GTK+ and CLI 
frontend,

as well a libretro core.

It's worth to mention that Snes9x is more accurate than ZSNES and use less
hardware resources than bsnes.

The package: https://mentors.debian.net/package/snes9x


--
Sergio Benjamim

Bug#799498: RFS: neko/2.0.0-4

[Andy Li]

Hi Gianfranco,

Thanks for the review!


> 1) please bump debhelper and compat level to 9
> (bonus points for converting the package to multiarch)
>
I've bumped those to 9.
For multiarch, I will address that in the next upstream version since there
are quite some changes needed.


> 2) please drop useless build-dependencies (such as quilt and maybe some
> others, e.g. pkg-config?)
>
I dropped quilt. The others including pkg-config are actually used during
the build.


> 3) rules file, can you please convert in plain dh_ calls?
>
Done.

I've reuploaded the package to mentors.
Please let me know if there is any other problem.

Best regards,
Andy

Bug#799768: RFS: ismrmrd/1.3.1-1

[Ghislain Vaillant]

On 22/09/15 14:57, Gianfranco Costamagna wrote:

Control: merge -1 799767
Control: owner -1 !

Hi Ghislain,


the packaging looks good, however I have some nitpicks/issues:


rules file:

"-DCMAKE_INSTALL_PREFIX=/usr"

is this really needed? AFAIK it should be the default inside a dh build.
(please check)

"--builddirectory=$(BUILDDIR)"

same here

(this will simplify a lot the packaging)
"cd $(BUILDDIR) && $(MAKE) apidoc"

make -C is your friend :)

something like $(MAKE) -C obj-* apidoc should work
(untested)



Indeed, none of CMAKE_INSTALL_PREFIX, CMAKE_BUILD_TYPE and customized 
BUILDDIR are required.


This simplifies d/rules quite a lot. I'll make sure to apply this 
knowledge to other packages I maintain.



now a real issue: please move that to a build-indep target, and add
the required build-dependencies to build-depends-indep target
(you might want to look at lucene++, a similar package I maintain)


Great suggestion.


to check if it is done correctly you can run dpkg-buildpackage -A
and dpkg-buildpackage -B
(this will allow you to do source-only uploads)

control:
move doc stuff to build-depends-indep
Vcs-Git has a space at the end
(not an issue but vim shows it in red colour)

changelog: much stuff is not mentioned:
- a new patch
- a patch dropped

- change of the documentation package installation directory
- drop of a ${shlibs:Depends} (why?)


I will make sure these are more detailed.


last personal note:
"usr/share/javascript/jquery/jquery.js 
usr/share/doc/libismrmrd-doc/html/api/jquery.js"

well I would like to avoid using the embedded jquery, read e.g.
https://lists.debian.org/debian-devel/2014/10/msg00783.html

using the system jquery instead of the doxygen patched one might result in a 
broken documentation.

(the link I gave you should have references to Debian bugs and other 
discussions)


I still don't get what the recommended solution is. So far, I have been 
(wrongly?) following what Lintian suggested to do with embedded jquery.


Ghislain

Re: Suspicious file changes in -dbg between old and new packages

[Gianfranco Costamagna]

Hi,



>So it is explainable that symbol loading works between
>fewly different package versions.
>I would still like to know how i managed to break it.
>Just to be able to avoid this in future.



as said before, the debug package should depend on binary:Version binary
package.

e.g.


Package: foo
Architecture: any
Description: foo package

this is the foo binary package!



Package: foo-dbg
Section: debug
Architecture: any
Depends: foo (= ${binary:Version}),
${misc:Depends},
${shlibs:Depends}
Description: Debug symbols for Foo
This package contains debug symbols for the foo package.


cheers,

G.

Splitting a source package with a new upstream version

[Christian Kastner]

Hi,

libfann 2.1.0~beta+dfsg-1 in Debian currently builds a library as
binary package libfann2, and Python bindings for it as binary package
python-pyfann.

The new upstream version 2.2.0 of libfann no longer provides the Python
bindings; they are now provided by an external contributor instead.
(Apart from this, is otherwise a fairly minor update of the library.)

I'm now wondering how to best handle this split.

The simplest solution, as far as I see it, would be to
  1. upload a 2.2.0 version of the library, with the Python bindings
 dropped. python-pyfann currently has a versioned dependency on a
 specific version of the library, libfann2 (=2.1.0~beta+dfsg-1).
 Therefore, The library itself will not be upgradeable without
 breaking or removing python-pyfann.
  2. Upload the Python bindings from the new upstream source, built
 against the new version of the library
  3. After the bindings have passed NEW, both library and bindings
 should be upgradeable smoothly.

Before getting into the other, more complex, alternatives: am I seeing
this correctly, or am I overlooking some important issue?

Regards,
Christian

Bug#799655: RFS: arrayfire/3.1.1+dfsg1-1

[Andreas Tille]

On Tue, Sep 22, 2015 at 05:59:48AM +, PICCA Frederic-Emmanuel wrote:
> I will take care of this.

Ahh, I missed this.  Frederic, if you could upload this would be great
since I'm behind a slow connection. 

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#799655: RFS: arrayfire/3.1.1+dfsg1-1

[PICCA Frederic-Emmanuel]

It is in the pipe :)

Cheers

Re: Suspicious file changes in -dbg between old and new packages

[Thomas Schmitt]

Hi,

Gianfranco Costamagna wrote:
> So how did it work for Thomas with the previous version installed?

The /usr/bin/cdrskin files of 1.4.0-2 and 1.4.0-3 are identical
(at least their MD5s are).
Curse or blessing of reproducible building.


Niels Thykier wrote:
>  * The path where the binaries were compiled
>  * The options given to gcc when compiled

These were identical.

>  * Time and day, if such are included in the code (__DATE__ macros and such).

If i set such a thing at compile time then i don't get
commended by the ReproducibleBuilds project. :))
(That's why i dropped my plan to add argument "buildstamped"
 to the debuild "make" run. One todo point less.)


So it is explainable that symbol loading works between
fewly different package versions.
I would still like to know how i managed to break it.
Just to be able to avoid this in future.

Will watch this when i make packages of the future
upstream releases.


Have a nice day :)

Thomas

Re: Suspicious file changes in -dbg between old and new packages

[Thomas Schmitt]

Hi,

i wrote:
> > And why does it still work when i install back 1.4.0-2 ?

Gianfranco Costamagna wrote:
> well, if -2 and -3 didn't change symbols (e.g.  you didn't patch the source
> code), why shouldn't it work?

I still wonder why it did not work on the first try.
I had installed cdrskin and libburn-dbg multiple times
since the change from debhelper 8 (.so in -dbg) to
debhelper 9 (.build-id files in -dbg).

Then Andrey reports success, i re-install cdrskin without
a good reason, and suddenly the debugging symbols are found
by gdb.

The web tells me that there is gdb option -symbols=file and
a startup file .gdbinit. But i did not use the option and
the whole Sid disk does not have a file .gdbinit.

The name of the symbol file is in the binary:
  $ strings /usr/bin/cdrskin | grep 66fcd4b56be0f2cc505c54b4ab566e582c8b1e
  66fcd4b56be0f2cc505c54b4ab566e582c8b1e.debug
So the feature seems to be based on a compile time trick.

I was not able to break it by further installations.
The initial riddle stays unsolved.


Have a nice day :)

Thomas

Bug#799205: RFS: eviacam/2.0.1-5 [ITP] -- webcam based mouse emulator

[Gianfranco Costamagna]

Hi Cesar,


>> maybe run "debconf-updatepo" in the clean target, to avoid forgetting of 
>> updating translations.

>
>Done


nack :) you did it correctly, but that way dh_clean is never called :)

override_dh_clean:
debconf-updatepo
dh_clean


this is what I meant.




"#634840 (wishlist): RFP: eviacam -- A cross platform webcam based mouse 
emulator"


can you please change it back to ITP?



eviacam (2.0.1-5) unstable; urgency=medium


well, you should call it 2.0.1-1, since it never has been in Debian before.
(you can upload the same version on mentors)

"check for updates"

well, this is mostly impossible for Debian packages, please patch it :)

the package seems to be working really well! at least with my face :)


cheers,

G.

Bug#799770: RFS: pyfftw/0.9.2+dfsg-3

[Gianfranco Costamagna]

Control: owner -1 !

Hi Ghislain,

the packaging looks good, however:

1) watch file: what about using this one?
http://pypi.debian.net/pyFFTW/watch

2)+  * d/control: bump standards version, no changes required.

I would also mention "3.9.6" somewhere

they are nitpicks, the packaging looks really good!

cheers,

G.

Bug#799768: RFS: ismrmrd/1.3.1-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "ismrmrd"

* Package name: ismrmrd
  Version : 1.3.1-1
  Upstream Author : The ISMRMRD developers
* URL : http://ismrmrd.github.io/
* License : Expat
  Section : science

It builds those binary packages:

 ismrmrd-schema - ISMRM Raw Data format (ISMRMRD) - XML schema
 ismrmrd-tools - ISMRM Raw Data format (ISMRMRD) - binaries
 libismrmrd-dev - ISMRM Raw Data format (ISMRMRD) - development files
 libismrmrd-doc - ISMRM Raw Data format (ISMRMRD) - documentation
 libismrmrd1.3 - ISMRM Raw Data format (ISMRMRD) - shared library

To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/ismrmrd

Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/i/ismrmrd/ismrmrd_1.3.1-1.dsc


Changes since the last upload:

  * New upstream release.
  * Soname bump in d/control and d/*.install.
  * Enable test suite, requires build dependency on libboost-test-dev.
  * Use stricter hardening.

Regards,
Ghislain Vaillant

Bug#799770: RFS: pyfftw/0.9.2+dfsg-3

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pyfftw"

* Package name: pyfftw
  Version : 0.9.2+dfsg-3
  Upstream Author : Henry Gomersall 
* URL : http://hgomersall.github.io/pyFFTW/
* License : BSD-3-clause
  Section : python

It builds those binary packages:

  python-pyfftw - Pythonic wrapper around FFTW - Python 2
  python-pyfftw-dbg - Pythonic wrapper around FFTW - Python 2 (debug)
  python3-pyfftw - Pythonic wrapper around FFTW - Python 3
  python3-pyfftw-dbg - Pythonic wrapper around FFTW - Python 3 (debug)

To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/pyfftw

Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/p/pyfftw/pyfftw_0.9.2+dfsg-3.dsc


Changes since the last upload:

  * d/watch: use pypi.debian.net.
  * d/p/arm-build.diff: fixes build on arm. (Closes: #779724)
- Thanks to Matthias Klose for forwarding the fix.
  * d/control: bump standards version, no changes required.
  * d/copyright:
- update copyright information for pyFFTW and debian,
- remove copyright information for DFSG-stripped files.

 Best regards,
 Ghislain Vaillant

Bug#799767: RFS: ismrmrd/1.3.1-1

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "ismrmrd"

* Package name: ismrmrd
  Version : 1.3.1-1
  Upstream Author : The ISMRMRD developers
* URL : http://ismrmrd.github.io/
* License : Expat
  Section : science

It builds those binary packages:

 ismrmrd-schema - ISMRM Raw Data format (ISMRMRD) - XML schema
 ismrmrd-tools - ISMRM Raw Data format (ISMRMRD) - binaries
 libismrmrd-dev - ISMRM Raw Data format (ISMRMRD) - development files
 libismrmrd-doc - ISMRM Raw Data format (ISMRMRD) - documentation
 libismrmrd1.3 - ISMRM Raw Data format (ISMRMRD) - shared library

To access further information about this package, please visit the
following URL:

  http://mentors.debian.net/package/ismrmrd

Alternatively, one can download the package with dget using this command:

  dget -x
http://mentors.debian.net/debian/pool/main/i/ismrmrd/ismrmrd_1.3.1-1.dsc

Changes since the last upload:

  * New upstream release.
  * Soname bump in d/control and d/*.install.
  * Enable test suite, requires build dependency on libboost-test-dev.
  * Use stricter hardening.

Regards,
Ghislain Vaillant

Bug#799205: RFS: eviacam/2.0.1-5 [ITP] -- webcam based mouse emulator

[Cesar Mauri]

Hi Gianfranco,



the other stuff might be food

maybe run "debconf-updatepo" in the clean target, to avoid forgetting of 
updating translations.


Done



I've uploaded an updated version to mentors. I've also fixed some issues 
(missing .mo files in .deb, remove unneeded files and dependencies). The binary 
package builds and seem to run fine on debian jessie.


Regards, Cesar

Bug#799768: RFS: ismrmrd/1.3.1-1

[Gianfranco Costamagna]

Control: merge -1 799767
Control: owner -1 !

Hi Ghislain,


the packaging looks good, however I have some nitpicks/issues:


rules file:

"-DCMAKE_INSTALL_PREFIX=/usr"

is this really needed? AFAIK it should be the default inside a dh build.
(please check)

"--builddirectory=$(BUILDDIR)"

same here

(this will simplify a lot the packaging)
"cd $(BUILDDIR) && $(MAKE) apidoc"

make -C is your friend :)

something like $(MAKE) -C obj-* apidoc should work
(untested)

now a real issue: please move that to a build-indep target, and add
the required build-dependencies to build-depends-indep target
(you might want to look at lucene++, a similar package I maintain)

to check if it is done correctly you can run dpkg-buildpackage -A
and dpkg-buildpackage -B
(this will allow you to do source-only uploads)

control:
move doc stuff to build-depends-indep
Vcs-Git has a space at the end
(not an issue but vim shows it in red colour)

changelog: much stuff is not mentioned:
- a new patch
- a patch dropped

- change of the documentation package installation directory
- drop of a ${shlibs:Depends} (why?)

last personal note:
"usr/share/javascript/jquery/jquery.js 
usr/share/doc/libismrmrd-doc/html/api/jquery.js"

well I would like to avoid using the embedded jquery, read e.g.
https://lists.debian.org/debian-devel/2014/10/msg00783.html

using the system jquery instead of the doxygen patched one might result in a 
broken documentation.

(the link I gave you should have references to Debian bugs and other 
discussions)

cheers,

G.

Bug#799205: RFS: eviacam/2.0.1-5 [ITP] -- webcam based mouse emulator

[Gianfranco Costamagna]

Hi again,
some lintian stuff
http://debomatic-amd64.debian.net/distribution#unstable/eviacam/2.0.1-5/lintian

cheers,


G.

Bug#799655: marked as done (RFS: arrayfire/3.1.1+dfsg1-1)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 13:46:06 +0100
with message-id <56014d8e.1010...@gmail.com>
and subject line uploaded to unstable
has caused the Debian Bug report #799655,
regarding RFS: arrayfire/3.1.1+dfsg1-1
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.)


-- 
799655: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "arrayfire"

* Package name: arrayfire
  Version : 3.1.1+dfsg1-1
  Upstream Author : ArrayFire Development Group 
* URL : http://arrayfire.com/
* License : BSD-3-Clause
  Programming Lang: C++
  Description : High performance library for parallel computing

It builds those binary packages:

  libarrayfire-cpu-dev - Development files for ArrayFire (CPU backend)
  libarrayfire-cpu3 - High performance library for parallel computing 
(CPU backend)

  libarrayfire-cpu3-dbg - Debugging symbols for ArrayFire (CPU backend)
  libarrayfire-doc - Common documentation for ArrayFire

To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/arrayfire

Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/a/arrayfire/arrayfire_3.1.1+dfsg1-1.dsc


Changes since the last upload:

  * New upstream release.
  * Add d/README.source, explains rationales behind DFSG cleaning.
  * Add d/README.Debian, explains packaging policy.
  * d/control:
- adjust format / content to debmake template,
- modify the existing binary package descriptions, in anticipation 
of the

  future introduction of the OpenCL backend packages.
  * Update d/copyright.
  * d/patches:
- refresh doxygen patch,
- add upstream bugfix patch on assign, fixes memory corruption 
triggered

  whilst running the test suite.
  * d/rules:
- use stricter hardening,
- enable test suite (only for 64-bit architecture due to a bug 
upstream),

- remove extra license file from assets.

Best regards,
Ghislain Vaillant
--- End Message ---
--- Begin Message ---

X-CrossAssassin-Score: 53990--- End Message ---

Bug#799770: RFS: pyfftw/0.9.2+dfsg-3

[Ghislain Vaillant]

On 22/09/15 14:42, Gianfranco Costamagna wrote:

Control: owner -1 !

Hi Ghislain,

the packaging looks good, however:

1) watch file: what about using this one?
http://pypi.debian.net/pyFFTW/watch

2)+  * d/control: bump standards version, no changes required.

I would also mention "3.9.6" somewhere

they are nitpicks, the packaging looks really good!

cheers,

G.



Hi Gianfranco, thanks for reviewing my package.

I have uploaded a new version, which addresses your comments.

Cheers,

Ghis

Bug#799770: marked as done (RFS: pyfftw/0.9.2+dfsg-3)

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 14:45:01 + (UTC)
with message-id <2025357966.2264338.1442933101920.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#799770: RFS: pyfftw/0.9.2+dfsg-3
has caused the Debian Bug report #799770,
regarding RFS: pyfftw/0.9.2+dfsg-3
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.)


-- 
799770: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pyfftw"

* Package name: pyfftw
  Version : 0.9.2+dfsg-3
  Upstream Author : Henry Gomersall 
* URL : http://hgomersall.github.io/pyFFTW/
* License : BSD-3-clause
  Section : python

It builds those binary packages:

  python-pyfftw - Pythonic wrapper around FFTW - Python 2
  python-pyfftw-dbg - Pythonic wrapper around FFTW - Python 2 (debug)
  python3-pyfftw - Pythonic wrapper around FFTW - Python 3
  python3-pyfftw-dbg - Pythonic wrapper around FFTW - Python 3 (debug)

To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/pyfftw

Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/p/pyfftw/pyfftw_0.9.2+dfsg-3.dsc


Changes since the last upload:

  * d/watch: use pypi.debian.net.
  * d/p/arm-build.diff: fixes build on arm. (Closes: #779724)
- Thanks to Matthias Klose for forwarding the fix.
  * d/control: bump standards version, no changes required.
  * d/copyright:
- update copyright information for pyFFTW and debian,
- remove copyright information for DFSG-stripped files.

 Best regards,
 Ghislain Vaillant
--- End Message ---
--- Begin Message ---
Built, thanks for your contribution to Debian!

cheers,

G.





Il Martedì 22 Settembre 2015 16:30, Ghislain Vaillant  ha 
scritto:
On 22/09/15 14:42, Gianfranco Costamagna wrote:
> Control: owner -1 !
>
> Hi Ghislain,
>
> the packaging looks good, however:
>
> 1) watch file: what about using this one?
> http://pypi.debian.net/pyFFTW/watch
>
> 2)+  * d/control: bump standards version, no changes required.
>
> I would also mention "3.9.6" somewhere
>
> they are nitpicks, the packaging looks really good!
>
> cheers,
>
> G.
>

Hi Gianfranco, thanks for reviewing my package.

I have uploaded a new version, which addresses your comments.

Cheers,


Ghis--- End Message ---

Bug#799094: marked as done (RFS: node-kerberos/0.0.14-1 [ITP])

[Debian Bug Tracking System]

Your message dated Tue, 22 Sep 2015 15:33:31 + (UTC)
with message-id <1066647587.2337726.1442936011846.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#799094: RFS: node-kerberos/0.0.14-1 [ITP]
has caused the Debian Bug report #799094,
regarding RFS: node-kerberos/0.0.14-1 [ITP]
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.)


-- 
799094: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: pkg-javascript-de...@lists.alioth.debian.org

  Dear mentors,

  I am looking for a sponsor for my package "node-kerberos"

 * Package name: node-kerberos
   Version : 0.0.14-1
   Upstream Author : Christian Amor Kvalheim 
 * URL : https://github.com/christkv/kerberos
 * License : Apache-2.0
   Section : web

  It builds those binary packages:

node-kerberos - Kerberos library for Node.js

  To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/node-kerberos


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/n/node-kerberos/node-kerberos_0.0.14-1.dsc

  More information about node-kerberos can be obtained from 
https://github.com/christkv/kerberos

  Changes since the last upload:

  * Initial release (Closes: #798183)


  Regards,
   Christopher Hoskin
--- End Message ---
--- Begin Message ---
Hi Christopher,





>I have reviewed all of the other JavaScript packages I am aware of which use 
>GYP (node-contextify, node-groove,  node-leveldown,  node-postgres, 
>node-sqlite3,  node-stringprep,  node-ws, >node-zlib, node-expat, node-iconv, 
>node-mapnik, node-raptor, node-srs and node-zipfile) and they all seem to work 
>in this way, with the exception of node-ws, in which case upstream includes a 


thanks for giving me pointer to similar packages :)

>Makefile which includes similar commands.
>Debhelper doesn't currently have a "--with gyp" option as far as I know, so I 
>can't see how this can be simplified? Please can you make some suggestions?

well, you answered by youself

"Debhelper doesn't currently have a "--with gyp" option"

I would add "yet"

if many packages uses the same gyp facilities, it might be worth implementing 
them on debhelper (note: it should be really trivial to do, because it will 
become a new perl module)

I never touched debhelper, but a file in 
/usr/share/perl5/Debian/Debhelper/Sequence
and a new dh_gyp or whatever should do the trick :)

however, this isn't requested :)

Some questions:--- End Message ---

Bug#799498: RFS: neko/2.0.0-4

[Gianfranco Costamagna]

Control: owner -1 !


Hi, quick review:

1) please bump debhelper and compat level to 9
(bonus points for converting the package to multiarch)


2) please drop useless build-dependencies (such as quilt and maybe some others, 
e.g. pkg-config?)


3) rules file, can you please convert in plain dh_ calls?

the other things looks fine, even if I didn't try to build/run and I didn't 
check the copyright.

cheers,

Gianfranco