Bug 664759 is the ITP for python-tox. Back in June, Bradley M. Froehle
provided an initial packaging. I finally found some time to take his work,
add a few things (manpage, updated to latest tox version, debian/watch,
lintian clean), and svn-injected it into the PAPT repo.
http://anonscm.debian.
On Friday, November 09, 2012 01:32:53 PM Thomas Kluyver wrote:
> On 9 November 2012 12:44, Maykel Moya wrote:
> > Even in the case of the more restrictive license applying only to
> > debian/* work? Could you/someone elaborate a little the implications of
> > this (link to fine documentation is we
* Joseph Mills , 2012-11-07, 16:51:
Hello there I am not sure that this is going to the correct team but
here it goes. I found this upstream
http://qt.gitorious.org/qt-labs/gimp-qmlexporter so I took it and
packaged it. Now I want to get it into debian so that it will make
its-way to Ubuntu. W
On Fri, 2012-11-09 at 13:19 +, Thomas Kluyver wrote:
> In my opinion, the best way to do that is to build a GUI that holds
> the user's hand through the process of packaging, showing them the
> options available. It should be particularly useful for occasional
> packagers who don't want to rem
* Maykel Moya , 2012-11-09, 13:44:
I'd advise you not to use a more restrictive license than upstream uses.
Even in the case of the more restrictive license applying only to
debian/* work? Could you/someone elaborate a little the implications of
this (link to fine documentation is welcomed)?
On 9 November 2012 12:44, Maykel Moya wrote:
> Even in the case of the more restrictive license applying only to
> debian/* work? Could you/someone elaborate a little the implications of
> this (link to fine documentation is welcomed)?
>
I'm not sure if there's a Debian rule about it, but I'd co
This is an idea I've had knocking around for a while. Packaging is complex
- there are lots of different tools and syntaxes you have to understand to
do a good job of it - quilt, debhelper, watch files, etc. - along with
specialist terminology. I know various CLI tools aim to simplify things,
but n
El 08/11/12 23:08, Jakub Wilk escribió:
Hello
> I'd advise you not to use a more restrictive license than upstream uses.
Even in the case of the more restrictive license applying only to
debian/* work? Could you/someone elaborate a little the implications of
this (link to fine documentation is w
8 matches
Mail list logo