"Fred L. Drake, Jr." <fdrake@acm.org> writes: > Trent Mick writes: > > It might be nice to move the 'r221' CVS tag further along the > > 'release22-maint' branch. The tree at the current 'r221' location fails > > to build the docs with the following: > > > > make[1]: *** No rule to make target `whatsnew/whatsnew22.tex', needed by `html/whatsnew/whatsnew22.html'. Stop. > > > > 'whatsnew22.tex' was added after the tag. > > > > Thoughts? > > This should be fixed! I don't know who did the tagging, Me, obviously. I think I said when I did it here. > but don't remember any coordination activities. Well, only the 48 hour plan I posted to python-dev. Admittedly that didn't say when I would tag the tree. > This isn't the only file that was changed since whatsnew22.tex was > added. It seems I didn't run "cvs up -d" before tagging the tree or building the tarball, so Doc/whatsnew/ isn't in the tarball or under the tag. Sorry guys. At least nothing else got affected by this. Can some who knows how sort out the CVS mess? I can learn, I guess, but I'd rather not risk cocking it up. The other changes that were made in the process of building the windows installer and the docs I really don't care about (i.e. the changes Trent posted). Is this worth updating the tarball for? Cheers, M. -- Reading Slashdot can [...] often be worse than useless, especially to young and budding programmers: it can give you exactly the wrong idea about the technical issues it raises. -- http://www.cs.washington.edu/homes/klee/misc/slashdot.html#reasons
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4