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

Re: Problems with building new version of pytools



Dnia 2011-11-23, śro o godzinie 17:03 +0100, Jakub Wilk pisze:
> * Tomasz Rybak <bogomips@post.pl>, 2011-11-22, 18:53:
> >I have problem with building pytools though.
> >At the end of build process I got:
> >dpkg-source --after-build pytools-2011.5
> >dpkg-source: info: unapplying replace-setuptools.patch
> >patching file MANIFEST.in
> >patching file pytools.egg-info/SOURCES.txt
> >Hunk #2 FAILED at 8.
> >Hunk #3 FAILED at 24.
> >2 out of 3 hunks FAILED -- saving rejects to file
> >pytools.egg-info/SOURCES.txt.rej
> >patching file setup.py
> >dpkg-source: błąd: LC_ALL=C patch -R -t -N -p1 -u -V never -g0 -E
> >--no-backup-if-mismatch <
> >pytools-2011.5/debian/patches/replace-setuptools.patch zwrócił status
> >błędu 1
> >dpkg-buildpackage: błąd: dpkg-source --after-build pytools-2011.5
> >zwrócił status błędu 1
> 
> There are two common solutions:
> 1) Nuke the whole *.egg-info in the clean target.
> 2) Add it to extend-diff-ignore in debian/source/options.
> 
> >This is caused by setuptools.command.egg_info.manifest_maker. In the 
> >run() method it calls write_manifest(), which overwrites 
> >pytools.egg-info/SOURCES.txt, which was patched by me, to not include 
> >in package decorator (we got own in Debian)
> 
> Well, patching auto-generated files is always a bad idea... But anyway, 
> why do you care? Are there any tools that parse SOURCES.txt?

I cared because I wanted to avoid distributing pytools/log.py
and pytools/decorator.py (which is provided by python-decorator
package anyway). But as I remove those id debian/rules
dh_install I guess I can ignore SOURCES.txt entirely.
After removing it from the patch package builds without a problem.

> 
> And a more general question (to everybody): what's the purpose of 
> installing SOURCES.txt into a binary package?

In my case it is included in *.orig.tar.gz. Should
I nuke it in dh_install, or just leave it as is?

Regards, and thanks for the clues that helped
me solve this.

-- 
Tomasz Rybak <bogomips@post.pl> GPG/PGP key ID: 2AD5 9860
Fingerprint A481 824E 7DD3 9C0E C40A  488E C654 FB33 2AD5 9860
http://member.acm.org/~tomaszrybak

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: