[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#627787: ITP or RFP



Hi guys,

I have a few more questions for you:

  Is the "python-django-" mandatory for a django application package ?
  I have a few problems with the package. I still have this last
lintian warning:
W: python-django-gerbi source: format-3.0-but-debian-changes-patch. It
happens because some filenames are added to the list in the
xxx.egg-info/SOURCES.txt file. Those files have two origins:

   * I have the sphinx-generated doc hanging around at the time the
file is updated.
   * The setup.cfg file gets added to the list.

So I have the two following questions:
   * When is the best time to erase the auto-generated doc files. I
tried the override_dh_installdocs rule, added a rm command after the
files are copied to the debian package files. It seems to work for
other packages, but with no luck for me.
   * I am using the tar.gz produce by the "python setup.py sdist"
command as the source package which does include the setup.cfg file
but that file does not appear in the SOURCES.txt file. I'm not sure
why this file is added to the list, it is not modified.
   * I cannot find when is this SOURCES.txt file updated during the
packaging process ?
   * I found some discussion threads where the following line is added
to the clean rule to get rid of the setup.cfg problem:

     override_dh_clean:
         -sed -i -e '/setup\.cfg/d' PyOpenGL.egg-info/SOURCES.txt

    Does not really fill right to me...

Any hints ?
Thanks in advance,
Nicolas

2011/5/25 Nicolas CANIART <nicolas@caniart.net>:
> I'm still reading the Debian Python policy, but thanks for the advice.
>
> The upstream author has plans to rename the package. Maybe I can wait
> he completed the transition / help him with the transition so it
> happens sooner.
>
> 2011/5/25 Jakub Wilk <jwilk@debian.org>:
>> * Piotr Ożarowski <piotr@debian.org>, 2011-05-25, 10:15:
>>>
>>> source package name doesn't matter that much, but please use
>>> "python-pages" rather than "python-django-page-cms" as binary package's name
>>> (as Debian Python Policy suggests)
>>
>> And "pages" is very bad name for a public Python module, especially if it's
>> Django specific.
>>
>> --
>> Jakub Wilk
>>
>


Reply to: