.. -*- coding: utf-8 -*-

Version 0.16.2
--------------
:publication date: 2009/10/14
:expected date: n/a

Ticket #6617 behave as good as possible when interrupted with ctrl-c
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 1.000
:state: resolved

I interrupted lgp build with a ctrl-c and it left a projet-x.y.z in the source
tree, which caused it to fail on the following try with messages:

I:logilab.devtools.lgp.build: Use '/home/xxxx/dist/rql-0.20.2.tar.gz' as
original source archive (tarball) C:root: No file matching
/home/xxxx/dist/rql-0.20.2.tar.gz

Try to get lgp to behave better when interrupted (maybe catch ctrl-c and clean
up before exiting).

Comments ::

  On 2008/11/14 15:45 - Unknown author wrote :
  We should add an extra temporary directory for upstream tarball creation.
  
  setuptools build command could be used with option --build-temp (-t) [temporary
  build directory]. But not available in sdist..
  
  On the other hand, setuptools build command doesn't permit to redirect
  destination dir (-d). We need to move the build/ directory afterwards.

Ticket #7992 export raw configuration to a clean ini file
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.500
:state: resolved

A lot of stuff should be moved to the lgp.ini file:

- distribution's names mapping - pbuilder config - check list - constants - ...

Lgp already uses lgc.configuration.

Comments ::

  On 2009/03/03 17:12 - Unknown author wrote :
  Is now mostly done. Maybe we could define the check chain directly in
  /etc/lgp/lgp.ini and drop some raw config especially the distribution mapping.
  > On 2009/04/23 09:15 - Unknown author wrote :
  > We should provide an ini file in the Debian package. Not blocking for 0.14.0.
  > Go without it.

Ticket #10051 lgp build: don't build arch-independant package for each available arch
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 2.000
:state: resolved

Comments ::

  On 2009/10/22 10:24 - Unknown author wrote :
  fix causes 18804 :-(

Ticket #9066 Suspicious message lgp build => Can't exec "locale"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: resolved

While runing `lgp build -d all` (on cubes/book), the following messages appear
::

Can't exec "locale": No such file or directory at
/usr/share/perl5/Debconf/Encoding.pm line 16. Use of uninitialized value in
scalar chomp at /usr/share/perl5/Debconf/Encoding.pm line 17. debconf: delaying
package configuration, since apt-utils is not installed

Comments ::

  On 2009/04/30 06:40 - Unknown author wrote :
  For which version of Debian are you building? This looks very much like a
  temporarily broken unstable repository.
  On 2009/04/30 09:07 - Unknown author wrote :
  I think the two first lines are concerned by LANG environment stuff (try LANG=C
  before command).
  The last one seems to be a warning related to the missing apt-extracttemplates
  normally installed by apt-utils.
  
  I added in 0.16 this extra package in pbuilder configuration. Ping me if you
  have still the same message.

Ticket #9396 lgp check refuse to run if /opt/buildd isn't there
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved

::

syt@scorpius:~/src/apycotbot$ lgp check -s manifest_in C:check: 'unstable' image
not found in '/opt/buildd' C:check: unknown distribution 'unstable'

I should be able to run this even without this directory...

Ticket #8367 on "lgp build" failure some temporary directories are kept
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.500
:state: resolved

then subsequent runs fails for obscure reason, such as :

error: package directory './cubicweb-3/1/1' does not exist

Comments ::

  On 2009/03/10 13:16 - Unknown author wrote :
  I can't reproduce the problem even when mixing symbolic links in the repository.
  
  Please add info about the initial lgp build failure if possible.
  However that's true that lgp has a recurrent problem for cleaning :-\
  
  See http://www.logilab.org/ticket/6617
  On 2009/06/03 19:27 - Unknown author wrote :
  Try python setup.py clean or fakeroot debian/rules clean depending of your
  package. But should be launched automatically by lgp now.