On Wed, Sep 18, 2013 at 14:33:00 -0500, Steve Langasek wrote:
> On Wed, Sep 18, 2013 at 06:24:13PM +0200, Jakub Wilk wrote:
> > Following the “if it didn't happen on a mailing list, it didn't
> > happen”, I repeat here what I said on IRC:
>
> > 12:26 < kwilk> So I rebuilt src:python-aalib, and I
[Stuart Prescott, 2013-09-19]
> > I don't understand the pip hate. Why don't you guys try and, you know,
> > figure out *why* these tools were invented. It (for sure) is overly
> > simplistic, but it's there for a reason.
>
> It's pretty obvious why these tools were invented -- I think everyone
>
On 2013-09-18 09:36, Paul Tagliamonte wrote:
> 1) pip isn't for global package management, for this is stupid. If we
> disabled root use of pip, I think we'd all be a bit happier.
Very quick and very dirty patch attached.
> 4) Python modules from dpkg are borderline useless for developer
Package: wnpp
I want someone to take over development of lintian4python, as I no
longer use this package.
Description
===
Lintian dissects Debian packages and reports bugs and policy violations.
It contains automated checks for many aspects of Debian policy as well
as some checks fo
[Julien Cristau, 2013-09-19]
> Well, in Jakub's case the module does dlopen("libaa.so.1"), so while it
> doesn't care about the interpreter's architecture, it does need the
> libaa1 and python3 packages to be of the same architecture. AIUI
> "Depends: python3:any, libaa1" doesn't express that?
as
On Thu, Sep 19, 2013 at 14:55:17 +0200, Piotr Ożarowski wrote:
> [Julien Cristau, 2013-09-19]
> > Well, in Jakub's case the module does dlopen("libaa.so.1"), so while it
> > doesn't care about the interpreter's architecture, it does need the
> > libaa1 and python3 packages to be of the same archit
[Julien Cristau, 2013-09-19]
> On Thu, Sep 19, 2013 at 14:55:17 +0200, Piotr Ożarowski wrote:
>
> > [Julien Cristau, 2013-09-19]
> > > Well, in Jakub's case the module does dlopen("libaa.so.1"), so while it
> > > doesn't care about the interpreter's architecture, it does need the
> > > libaa1 and
Paul Tagliamonte wrote:
>On Wed, Sep 18, 2013 at 05:16:22PM +1000, Ben Finney wrote:
>> Howdy all,
>>
>> Over at the ‘python-dev’ forum, PEP 453 is being discussed. This
>affects
>> Debian packaging of Python, and packages written for Python.
>>
>> See the discussion thread and take the opport
On Wed, Sep 18, 2013 at 05:16:22PM +1000, Ben Finney wrote:
> Howdy all,
>
> Over at the ‘python-dev’ forum, PEP 453 is being discussed. This affects
> Debian packaging of Python, and packages written for Python.
>
> See the discussion thread and take the opportunity to represent Debian
> https:/
Hi,
On Wed, Sep 18, 2013 at 06:45:24PM -0400, Scott Kitterman wrote:
> It shows my background, but when I need older versions of things I
> fire up a chroot and work in that. I often do that even for the
> same distro release I'm running to keep things separated. It's quite
> possible to deal wi
* Piotr Ożarowski , 2013-09-19, 15:33:
any proposals on how to detect packages that import ctypes
It's not necessarily only ctypes.
(other than parsing sources, please ;)
Don't detect anything. Add an option (say, --multiarch-me-harder), so that
maintainers can opt-in for :any dependencies
On Thu, Sep 19, 2013 at 05:05:39PM +0200, Jakub Wilk wrote:
> * Piotr Ożarowski , 2013-09-19, 15:33:
> >any proposals on how to detect packages that import ctypes
> It's not necessarily only ctypes.
What are the other cases?
> >(other than parsing sources, please ;)
> Don't detect anything. Add
Paul Tagliamonte writes:
> Donald pung me after, and he's open to working with us.
Thank you! It's important to have calm discussion with upstream, when we
can make a positive difference to this specification.
--
\ “Teach a man to make fire, and he will be warm for a day. Set a |
`\
13 matches
Mail list logo
