On Sep 21, 2011, at 02:40 AM, Thomas Goirand wrote:
>Thanks for the pointer. However, I don't understand this:
>
>"All packages that use the same namespace have to be
>converted at the same time. Be sure to use Breaks or
>Depends relationships to ensure you cannot mix
>installation of python-suppo
On Oct 18, 2011, at 12:00 PM, Boris Pek wrote:
>> I don't want to learn GIT right now. Is there someplace I could stay with
>> svn?
>
>Maybe it was the sign to learn something new? =)
>
>Git and Mercurial are really great DVCS. They are very suitable for small
>projects with small developers grou
On Oct 20, 2011, at 12:26 PM, Thomas Goirand wrote:
>Not getting into any war, but it seems 90% of everyone thinks Git is a way
>better than BZR, and that the 10% that remains are BZR extremists. Since
>VCS is all about sharing your sources (unless you don't care about others
>and sees it as only
On Oct 20, 2011, at 11:04 PM, Paul Wise wrote:
>I think people tend not to contribute at all to projects using a VCS
>they don't like.
I still contribute to Python .
>For example I might stop putting off the Mailman stuff I promised to
>work on (porting the Indymedia patchset to mailman 3) if it
On Oct 20, 2011, at 08:48 AM, Alex Chiang wrote:
>The lowest common denominator is patch(1).
>
>So all you really need to know how to do is use the upstream's
>tool to obtain the source:
>
> git clone
> bzr branch
> svn co
> etc.
>
>Then, you can import the source into your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Nov 20, 2013, at 09:44 PM, Ross Gammon wrote:
>This has been frustrating me for a few days now and I am hoping
>someone can help with some inspiration :-)
>
>My upstream are maintaining two parallel versions at the moment, and I
>am trying to pre
On Feb 28, 2014, at 10:52 AM, Mikhail Morfikov wrote:
>I'm new to building packages by using pbuilder tool, and I have to build
>a package multiple times before it builds successfully, or in the way
>I prefer.
This is one of the reasons why I prefer to use sbuild for most of my local
builds. You
On Jun 11, 2014, at 10:03 PM, Ross Gammon wrote:
>A supplementary question - do I need to name the package "python3-foo"
>if a python 2 version is not being provided any more? Or will python-foo
>do? Previous versions were just "foo" and being dealt with by
>Conflicts/Replaces.
This could be your
On Jun 28, 2014, at 09:13 PM, Daniel Lintott wrote:
>The only thing I was able to find was this-
>http://www.wefearchange.org/2011/09/sbuild-with-local-newer-dependencies.html
I still use that setup extensively, most recently while adding Python 3
support to a stack of zope.* and other packages.
On Jul 24, 2014, at 10:29 AM, Daniel Stender wrote:
>I'm working on packaging a Python package with a Sphinx based documentation,
>Nltk 3.0.0b1, and there are encoding related build errors.
>...
>Strangely, this only occurs when trying to build against Sid (via
>Cowbuilder), building with debuild
On Nov 04, 2014, at 10:21 PM, Etienne Millon wrote:
>The best practice is indeed to discard the binary in one of the
>packages, like your solution 1. However, it is better to use the
>python3 version (this is the recommended way now, can't find the
>debian-python thread from earlier this year).
C
On Feb 28, 2015, at 04:37 PM, Daniel Stender wrote:
>1) what would be the proper license for that file in deb/copyright?
IANAL but the PSF's policy on use of its trademarks is clearly stated here:
https://www.python.org/psf/trademarks/
They are also fairly permissive in granting approval for it
On Jun 09, 2015, at 10:05 PM, Andrey Rahmatullin wrote:
>I don't think the language of the software itself matters here at all.
Except of course it should be Python 3, not Python 2. ;)
Cheers,
-Barry
pgp72_qCDJkRv.pgp
Description: OpenPGP digital signature
On Feb 04, 2016, at 09:08 PM, Sean Whitton wrote:
>I'm packaging a Python application, ocrmypdf [1], that has a test suite
>run by py.test. Most of the tests fail because they try to call the
>/usr/bin/ocrmypdf script. This script doesn't exist until after
>debhelper has run setup.py, which gene
14 matches
Mail list logo
