There are some .rej and .orig files in the tarball, which seems odd, because presumably they aren't checked in.
$ find . -name *.orig -o -name \*.rej
./work/allmydata-tahoe-1.9.2/docs/performance.rst.rej
./work/allmydata-tahoe-1.9.2/docs/known_issues.rst.orig
./work/allmydata-tahoe-1.9.2/docs/known_issues.rst.rej
./work/allmydata-tahoe-1.9.2/docs/performance.rst.orig
This is so unusual that I double-checked the tarball itself to make sure
this wasn't a pgksrc artifact.
The .orig files mess up pkgsrc slightly, because we have a mkpatches
script that looks for .orig and generates local patch files (since in
theory those are created by pkgvi that preserves the original when the
packager has to make a change).
FWIW, here's the only patch for tahoe - I haven't tried omitting it
recently.
$NetBSD: patch-aa,v 1.2 2012/01/13 01:14:56 gdt Exp $
Upstream incorrectly installs test code. Patch from David-Sarah
Hopwood (of upstream) in private mail.
--- setup.py.orig 2012-05-31 22:25:33.000000000 +0000
+++ setup.py
@@ -467,8 +467,7 @@ setup(name=APPNAME,
'allmydata.util',
'allmydata.web',
'allmydata.web.static',
- 'allmydata.windows',
- 'buildtest'],
+ 'allmydata.windows'],
classifiers=trove_classifiers,
test_suite="allmydata.test",
install_requires=install_requires,
pgpP9g3cCzW95.pgp
Description: PGP signature
_______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
