[Letsencrypt-devel] Bug#806532: Bug#806532: FTBFS on jessie

Daniel Pocock daniel at pocock.pro
Mon Dec 28 06:44:01 UTC 2015



On 28/12/15 07:40, Francois Marier wrote:
> On 2015-12-06 at 09:00:06, Daniel Pocock wrote:
>>> Are you sure you're trying this on a clean and up-to-date jessie system?
>>
>> Yes
>>
>> I had noticed that the gnulib package was required and was not mentioned
>> in the build-deps.  Could there be any other missing build dependency
>> that you have on your system but I don't have on mine?
> 
> So I took another look at this. Are you running "git pbuilder" directly in
> the package directory by any chance?
> 
> I just noticed this in README.distributors:
> 
> "To make this as easy as possible, setup.py does the following:
>   - create or refresh (overwriting) ChangeLog from ChangeLog.init and the Git
>     log if there is a .git subdirectory in the current directory. This is very
>     quick and done every time setup.py is run. For this to work,
>     gitlog-to-changelog must be in the PATH and executable."
> 
> So basically, it's detecting you're in a git repo and (wrongly) assuming
> that it's the upstream repo so it runs through this unnecessary Changelog
> generation.
> 
> On the other hand, if you create a jessie LXC container and build from there
> using "gbp buildpackage", it never sees a .git directory and works just
> fine.
> 

Yes, I was in a repository with a ".git" directory

I frequently build packages that way when I am tinkering with them so it
would be good to find a way to support that reliably.  Maybe upstream
needs to test for some environment variable or the existence of some
other file that tells it not to do this ChangeLog update.



More information about the Letsencrypt-devel mailing list