Bug#779667: RFS: node-bluebird/2.9.13+dfsg-1 [ITP]
On 03/04/2015 11:47 PM, Sebastiaan Couwenberg wrote: Thanks for the fixes. I've pushed some more changes for various things I encountered. Thanks for those. Using npm2deb for the first time made me miss some of my normal steps. Did you notice that the upstream build process requires itself? No - I did notice that the upstream build (and tests) did not work, but not that the require was the reason for it. I was looking to see if we could use tools/build.js to build the minified js instead of using uglify. After giving up, my thought was to work with upstream to fix it later - but I am happy to do that now instead. The tools/build.js script also does some modifications to the source when it generates the js/main/ code from the source. If installing the unmodified source is not sufficient, we may need to find a different solution to replace build.js to bootstrap this package. I might raise an issue upstream and see what they say. It would be good to have the upstream build and tests working. I haven't tested this yet. After the doing that, I suppose the final thing is to repack to remove the pre-built minified js. Cheers, Ross signature.asc Description: OpenPGP digital signature
Bug#779377: Fw: Re: Bug#779377: RFS: classified-ads/0.03-1 / ITP
So, does it look any better now? Yes, a lot better! You're almost there, but just two more things: -Add a d/source/format containing the only the string 3.0 (quilt) (without the quotation marks). This ensures that your package will use the new format for any patches you may make in future. -You can add a d/watch file to check for upstream releases. I made one that you can use from the uscan manpage: version=3 https://github.com/operatornormal/classified_ads/tags (?:.*/)?v?(\d[\d \.]*)\.tar\.gz By the way, I just sent you a message using classified-ads! pgpUHj9LMQufE.pgp Description: PGP signature
Bug#779377: Changelog bug closing in classified-ads
Oh, and I forgot to mention: The bug you close in d/changelog should be the ITP, not the RFS. The RFS will be closed automatically once the ITP is closed. pgpTpT7nOdACw.pgp Description: PGP signature
Bug#779486: RFS: pylama/6.2.0-1 [ITP]
On Sun, Mar 01, 2015 at 12:48:21PM +0100, Federico Gimenez wrote:
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package pylama
* Package name: pylama
Version : 6.2.0-1
Upstream Author : Kirill Klenov horn...@gmail.com
* URL : https://github.com/klen/pylama
* License : LGPL-3
Section : python
It builds those binary packages:
python-pylama - Code audit tool for Python and JavaScript - Python 2.x
python3-pylama - Code audit tool for Python and JavaScript - Python 3.x
To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/pylama
Alternatively, one can download the package with dget using this command:
dget -x
http://mentors.debian.net/debian/pool/main/p/pylama/pylama_6.2.0-1.dsc
Consider maintaining this in the DPMT (I've seen pylama added to the topic
of #debian-python but we add only team packages there).
You shouldn't use ${shlibs:Depends} for packages without ELF binaries.
As the packages contain public modules it's a bad idea to have py2 and py3
versions conflict with each other. If the modules are usable only by the
pylama app, you should package only the py3 version in some private path
and call the package pylama. If they are usable as python modules
(importable) then either the binaries should have different names or (if
it doesn't matter for the user which version is used) probably only the
py3 version should be packaged.
See also https://www.debian.org/doc/packaging-manuals/python-policy/
The license of debian/* shouldn't be stricter that the upstream license
(though this is debatable I think).
The package contains tests which aren't run by your debian/rules. On a
first glance they are supposed to be run using py.test and pybuild can be
asked to use that.
--
WBR, wRAR
signature.asc
Description: Digital signature
Bug#774120: marked as done (RFS: libjson-rpc-cpp/0.4.1-2 [ITP])
Your message dated Fri, 06 Mar 2015 09:19:13 +0100 with message-id 54f96301.4000...@autistici.org and subject line closing bug has caused the Debian Bug report #774120, regarding RFS: libjson-rpc-cpp/0.4.1-2 [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.) -- 774120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774120 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: wishlist Dear Mentors! I am still looking for a sponsor for my package libjson-rpc-cpp. Could someone please review it? * Package name: libjson-rpc-cpp Version : 0.4.1-2 Upstream Author : Peter Spiess-Knafl p...@autistici.org (me) * URL : https://github.com/cinemast/libjson-rpc-cpp * License : MIT/X Section : libs It builds those binary packages: libjsonrpccpp-client0 - library implementing json-rpc C++ clients libjsonrpccpp-client0-dbg - debugging symbols for libjsonrpccpp-client0 libjsonrpccpp-common0 - common functionality for server and client library libjsonrpccpp-common0-dbg - debugging symbols for libjsonrpccpp-common0 libjsonrpccpp-dev - Development files for JSON-RPC C++ framework libjsonrpccpp-server0 - library implementing json-rpc C++ servers libjsonrpccpp-server0-dbg - debugging symbols for libjsonrpccpp-server0 libjsonrpccpp-tools - Stubgenerator for libjsonrpccpp based applications To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libjson-rpc-cpp Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libj/libjson-rpc-cpp/libjson-rpc-cpp_0.4.1-2.dsc Changes since the last upload: * Added dbg packages for client, common and server library. * Overrided no-symbols-control-file, because we use shlibs instead. * Changed target from unstable to experimental, due to freeze phase. Thank you and Greetings, Peter ---End Message--- ---BeginMessage--- X-CrossAssassin-Score: 47248---End Message---
