On Tue, Aug 30, 2022 at 07:33:07PM +0200, Gregor Riepl wrote:
> > I: python3-pyxdameraulevenshtein: hardening-no-bindnow
> > [usr/lib/python3/dist-packages/pyxdameraulevenshtein.cpython-310-x86_64-linux-gnu.so]
> >
> > and there is nothing about CFLAGS or the like in the setup.py file.
> > So if
I: python3-pyxdameraulevenshtein: hardening-no-bindnow
[usr/lib/python3/dist-packages/pyxdameraulevenshtein.cpython-310-x86_64-linux-gnu.so]
and there is nothing about CFLAGS or the like in the setup.py file.
So if having this hardening flag enabled is a good thing, it should
probably be enabled
On Tuesday, September 29, 2015 10:31:23 PM Julien Puydt wrote:
> Le mardi 29 sept. 2015 à 15:51:44 (-0400), Barry Warsaw a écrit :
> > On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote:
> > >(and remember to remove DPMT from debian/control if it's not in SVN ;P)
> >
> > Given that the final git
On Tuesday, September 29, 2015 04:48:09 PM Barry Warsaw wrote:
> On Sep 29, 2015, at 10:31 PM, Julien Puydt wrote:
> >I still have a series of things I plan to package for Debian ; those are
> >Python Modules, and I'll use git. If that's a problem for the Debian
> >Python Modules Team, can you poin
On Sep 29, 2015, at 10:31 PM, Julien Puydt wrote:
>I still have a series of things I plan to package for Debian ; those are
>Python Modules, and I'll use git. If that's a problem for the Debian
>Python Modules Team, can you point me to a more appropriate team?
This illustrates my concern. We'v
Le mardi 29 sept. 2015 à 15:51:44 (-0400), Barry Warsaw a écrit :
> On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote:
>
> >(and remember to remove DPMT from debian/control if it's not in SVN ;P)
>
> Given that the final git migration is imminent (really! otherwise I'm going to
> scream ;), can
On Sep 29, 2015, at 09:46 PM, Piotr Ożarowski wrote:
>(and remember to remove DPMT from debian/control if it's not in SVN ;P)
Given that the final git migration is imminent (really! otherwise I'm going to
scream ;), can we not force people to go through this churn right now?
Yes, let's discourag
Jakub Wilk ha scritto:
>> * E: Don't hard-code {site,dist}-packages
>
> Uhm, what do you mean?
That's what we are trying to fix with
http://bugs.debian.org/cgi-bin/pkgreport.cgi?users=debian-pyt...@lists.debian.org;tag=dist-packages
In case we missed some packages, or some NEW ones were included
Steve Langasek ha scritto:
>> * E: Don't hard-code {site,dist}-packages
>
> hard-coded where, and how will you detect this?
debian/rules and other control files such as debian/install and
debian/links.
>> * W: Build extension for every supported Python version
>
> how will you detect this?
Pa
Scott Kitterman ha scritto:
>> * E: Don't hard-code {site,dist}-packages
>> * E: Python files in incorrect python2.?/{site,dist}-packages directory
>
> Since we currently lack anything like a maintained Python policy, I think
> this is putting the cart before the horse. Particularly any Error le
Ben Finney ha scritto:
>> * I: Place Python applications in private directory
>
> What would be the test for these cases? That is, what would Lintian
> actually check in the package to determine whether these should be
> emitted?
This is quite complex to say, I initially thought of checking for f
On Mon, Nov 02, 2009 at 12:54:04AM +0100, Luca Falavigna wrote:
> Currently, Lintian supports dozen of tags [1], but very few strictly
> related to Python packaging. I think maintainers and sponsors would
> benefit a lot if some common mistakes and suggestions are automatically
> displayed by Linti
* Luca Falavigna , 2009-11-02, 00:54:
I propose a non comprehensive list of tags I'd like to see available:
* E: Don't hard-code {site,dist}-packages
Uhm, what do you mean?
* E: Python files in incorrect python2.?/{site,dist}-packages directory
We need this check as soon as possible.
* I:
Luca Falavigna writes:
> I propose a non comprehensive list of tags I'd like to see available:
Thank you, I think this is a good start.
> * E: Don't hard-code {site,dist}-packages
> * E: Python files in incorrect python2.?/{site,dist}-packages
> directory
> * W: Build extension for every suppor
On Mon, 2 Nov 2009 00:54:04 +0100 Luca Falavigna
wrote:
>Currently, Lintian supports dozen of tags [1], but very few strictly
>related to Python packaging. I think maintainers and sponsors would
>benefit a lot if some common mistakes and suggestions are automatically
>displayed by Lintian.
>
>I p
[Dmitrijs Ledkovs, 2009-09-03]
> I have no clue about the js file bit though. Remove it (via patch) and
> symlink it from the shipped package by debian? That is my wild guess.
> Or maybe contact sphinx maintainer in Debian. I hope there is an
> option to symlink it.
http://lists.debian.org/debian-
(Please reply to list as well thanks)
2009/9/3 Alessandro Dentella :
>> > Last question
>> > -
>> >
>> > When testing creating the package from my newly created sources on a newer
>> > machine (ubuntu 9.04), lintian complained:
>> >
>> > W: python-sqlkit: embedded-javascript-library
>>
2009/9/3 Alessandro Dentella :
>> > bad-distribution-in-changes-file
>> >
>> >
>> > If I run lintian on .changes it complains
>> > "bad-distribution-in-changes-file" but I'm unsure on what I should do.
>> > At present I'm building on an ubuntu-hardy so the nam
thanks to anybody for the answers.
> > I forced
> > it an now lintian complains:
> >
> >san...@bluff:/misc/src/hg/py$ lintian python-sqlkit_0.8.6_all.deb
> >W: python-sqlkit: latest-debian-changelog-entry-without-new-version
> >
> >What should I do?
>
> When you use -v, you have
[Bernd Zeimetz, 2009-09-03]
> Cyril Brulebois wrote:
> > Alessandro Dentella (03/09/2009):
> >> I'm trying to produce the python-sqlkit package. I'm both the upsteam
> >> author and the mantainer. I have /debian folder in original package. I
> >> recently read is not recommended but I found
Cyril Brulebois wrote:
> Alessandro Dentella (03/09/2009):
>> Hi,
>
> Hello,
>
>> I'm trying to produce the python-sqlkit package. I'm both the upsteam
>> author and the mantainer. I have /debian folder in original package. I
>> recently read is not recommended but I found easier to manage
On 03/09/2009 02:04, Alessandro Dentella wrote:
Hi,
I'm trying to produce the python-sqlkit package. I'm both the upsteam
author and the mantainer. I have /debian folder in original package. I
recently read is not recommended but I found easier to manage to have it
in the same merc
Alessandro Dentella (03/09/2009):
> Hi,
Hello,
> I'm trying to produce the python-sqlkit package. I'm both the upsteam
> author and the mantainer. I have /debian folder in original package. I
> recently read is not recommended but I found easier to manage to have it
> in the same mercuri
opers , Debian Policy
, [EMAIL PROTECTED]
Subject: Re: Lintian: image-file-in-usr-lib
On Mon, Mar 17, 2003 at 11:02:01AM -0500, Simon Law wrote:
> I suspect that the most correct thing is to change Zope such
> that it expects it in an FHS-compatible place. For extra points,
On Sat, Oct 19, 2002 at 09:29:24PM +0200, Raphael Bossek wrote:
> $ lintian epydoc_1.0-1_all.deb
> E: epydoc: python-script-but-no-python-dep
> ./usr/lib/python2.1/site-packages/epydoc/cli.py
> E: epydoc: python-script-but-no-python-dep
> ./usr/lib/python2.1/site-packages/epydoc/gui.py
> E: epyd
On Fri, Nov 08, 2002 at 09:32:49PM +1100, Peter Hawkins wrote:
| Are lintian's current python dependency checks on crack or something?
| N: Packages that use python scripts must depend on the package
| N: python-base, probably with a versioned dependency. If the package
| Last time I checke
On Fri, 8 Nov 2002, Peter Hawkins wrote:
> Are lintian's current python dependency checks on crack or something?
Just for the record: Same for me.
Kind regards
Andreas.
On 29-Oct-2001 Tom Cato Amundsen wrote:
> Has anyone started modifying lintian? If I remember correctly,
> packages that generate lintian errors will be rejected...
>
anyone is me, the maint. (-: Although any pythoners among you willing to get
dirty with perl are welcome to send patches.
> At
> "python" is a real package, no virtual one. I.e. at any given time,
> there is only one package "python" on a system (neither python1.5 nor
> python2.1 will provide "python").
Duh, okay. :)
Thanks - Ben.
* Ben Burton <[EMAIL PROTECTED]> [011029 15:46]:
>
> > > Also, someone else reported that lintian complains against
> > > Depends: python (>= 2.1), python (<< 2.2)
> >
> > This is a lintian bug. It's not bothering to notice that one's a less-than
> > and the other's a greater-than.
>
> Btw, isn't
> > Also, someone else reported that lintian complains against
> > Depends: python (>= 2.1), python (<< 2.2)
>
> This is a lintian bug. It's not bothering to notice that one's a less-than
> and the other's a greater-than.
Btw, isn't this Depends line problematic anyway? I could have python 1.5
a
On Mon, Oct 29, 2001 at 12:40:33PM +0100, Tom Cato Amundsen wrote:
> Has anyone started modifying lintian? If I remember correctly,
> packages that generate lintian errors will be rejected...
Lintian is advisory only.
> Also, someone else reported that lintian complains against
> Depends: python
32 matches
Mail list logo
