[Debichem-devel] cclib-data new debian version

[Michael Banck]

Hi,

On Sat, Sep 10, 2011 at 01:46:39PM +0200, Michael Banck wrote:
> On Fri, Sep 09, 2011 at 06:40:03PM +0200, Karol M. Langner wrote:
> > On Fri, Sep 09, 2011 at 05:51:15PM +0200, Michael Banck wrote:
> > > On Fri, Sep 09, 2011 at 05:48:56PM +0200, Karol M. Langner wrote:
> > > > On Fri, Sep 09, 2011 at 05:34:02PM +0200, Michael Banck wrote:
> > > > > Hi,
> > > > > 
> > > > > On Fri, Sep 09, 2011 at 04:22:02PM +0200, Karol M. Langner wrote:
> > > > > > On Fri, Sep 09, 2011 at 04:02:40PM +0200, Michael Banck wrote:
> > > > > > > Do you know why that is?  I currently do not have much time to look at
> > > > > > > it in detail.
> > > > > > 
> > > > > > I had that before I fixed setup.py again, but can't reproduce it now.
> > > > > > Are you sure you checked out the last revision (2891)?
> > > > > 
> > > > > Yes, that is the one I have, weird. 
> > > > 
> > > > Maybe there's something different in the way we build? I simply
> > > > run 'dpkg-buildpackage' from dpkg-dev 1.16.0.3.
> > > 
> > > I am building with sbuild, which keeps an up-to-date unstable chroot.
> > 
> > OK, I repeated the build using sbuild and a new unstable chroot. Attached is
> > the log file, with what seems to be the same effect -- no errors.
> 
> Thanks for checking, so it must be something on my end.  I tried on two
> different computers (i386 and amd64), but I will have another look.

I checked again and it was indeed some local or obsolete change I had in
the tree and which dpkg helpfully stored as an additional patch. Mea
culpa.

I purged that, it rebuilt fine and I uploaded it now.


Michael