Martin v. Löwis wrote: > Thomas Viehmann wrote: >>- If you read Matthew's FAQ, you'll find that the copyright file isn't >> correct. > Can you please point me to my error. I read the FAQ, and I read the > copyright file, and I cannot discover any indescrepancy. Sorry, it's in the Sponsorship Checklist, not the FAQ. There is no copyright notice in the copyright file: http://lists.debian.org/debian-devel-announce/2003/12/msg00007.html
>>- You're #249071 has "127.0.0.1" in the comment but "localhost" in the >> code. Why? > The comment describes what C Xlib does (as it says, in > Xtransutil.c:ConvertAddress); C Xlib, at that point, operates on > network addresses, not host names. OTOH, the caller of get_auth > supplies 'host' as a hostname, hence the code needs to compare > with 'localhost'. See Xtransutil.c. > > This may not cover all possible cases, but it covers the case which > #249071 is about: sshd sets DISPLAY to localhost:10, yet puts > gethostname()/unix:10 into .Xauthority. IMO, this is a bug in > xauth(1), which does not use the same algorithm for matching > as C Xlib does. So in the long run, it might be necessary to > completely rewrite the .Xauthority processing to parse the file > in python-xlib directly. Ah, thanks. Maybe you could make explicit that this is "works with ssh" rather than "properly implements C Xlib's behaviour" in the comment. >>- What's the current best practice of linking doc and library packages? > I don't know; how can I find out? Neither section 7 nor section 12.3 > of the Policy Manual seem to talk about this specific question. Hmm. Based on my own (not very large) sample of current practice, a Suggests seems to be commonly used. (libc6, python, as well as some python-* use Suggests, perl uses Recommends, but that might be a bit much.) >>- IIRC there was some discussion about dropping python 2.1/2.2 for etch. >> Can you check what the deal is? > I checked; for the moment, there is no action to take. Things will be > reconsidered when the migration to python2.4 is started. OK. Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
