Bug#720308: gitweb's manual: please update, amend or remove doc related to FastCGI
Control: reassign -1 git-man 1:1.7.10.4-1+wheezy1 On Ma, 20 aug 13, 12:00:28, Vincent Férotin wrote: Package: git-man Version: 1:1.7.10.4-1+wheezy1 (Sorry for the typo in package's name.) That won't be enough, a reassign is needed (as done with this message). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Bug#720308: gitweb's manual: please update, amend or remove doc related to FastCGI
reassign 720308 gitweb retitle 720308 gitweb: double-utf8-encoding problems in FastCGI mode tags 720308 + upstream forwarded 720308 http://thread.gmane.org/gmane.comp.version-control.git/211888 quit Hi Vincent, Vincent Férotin wrote: gitweb is supposed to be serveable through FastCGI with Apache, as its manual claimed it (section WEBSERVER CONFIGURATION, subsection Apache with FastCGI). I experimented an error using it, as generated XHTML had double/wrong encoding (i.e. non all UTF-8), when gitweb CGI script encounter my (accented) name, e.g. in git's log. This problem is known, as e.g. reported here: http://git.661346.n2.nabble.com/Gitweb-running-as-FCGI-does-not-print-its-output-in-UTF-8-td7573415.html [...] The easiest solution could be to not recommend FastCGI for gitweb, and update documentation so. Heh. I prefer not to do this if possible (it would be better to get the underlying problem fixed). It might be worth adding a description of this issue to the BUGS section to the manpage and pointing to it, though. Also, this section shows a `FastCGIServer` directive, which is specific to libapache2-mod-fastcgi, which belongs to non-free packages' section. For example, a free alternative is package libapache2-mod-fcgid, which has not this directive. So this section content could also be rewritten, according to the recommended Apache's FastCGI module by Debian (I don't know if it is libapache2-mod-fcgid). An other and last remark: could it be possible that gitweb's manual belong to gitweb's package This bug report should IMHO better stand with gitweb's other bugs? The main git package in Debian includes git-instaweb, which is why the gitweb docs are in there. Probably I should move git-instaweb to the gitweb package, which would simplify things. Thanks for a pleasant report, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720308: gitweb's manual: please update, amend or remove doc related to FastCGI
Heh. I prefer not to do this if possible (it would be better to get the underlying problem fixed). Of course, I agree :-) That was an idea due to my own ignorance of FastCGI (first use). Also, mentioning the bug will not refrain happy-with-FastCGI users, such as full-ascii commiters. The main git package in Debian includes git-instaweb, which is why the gitweb docs are in there. Ah, ok. Didn't know about git-instaweb. Thanks you guys, Jonathan and Gerrit, for having taken your time considering this report! -- Vincent 2013/8/21 Jonathan Nieder jrnie...@gmail.com: reassign 720308 gitweb retitle 720308 gitweb: double-utf8-encoding problems in FastCGI mode tags 720308 + upstream forwarded 720308 http://thread.gmane.org/gmane.comp.version-control.git/211888 quit Hi Vincent, Vincent Férotin wrote: gitweb is supposed to be serveable through FastCGI with Apache, as its manual claimed it (section WEBSERVER CONFIGURATION, subsection Apache with FastCGI). I experimented an error using it, as generated XHTML had double/wrong encoding (i.e. non all UTF-8), when gitweb CGI script encounter my (accented) name, e.g. in git's log. This problem is known, as e.g. reported here: http://git.661346.n2.nabble.com/Gitweb-running-as-FCGI-does-not-print-its-output-in-UTF-8-td7573415.html [...] The easiest solution could be to not recommend FastCGI for gitweb, and update documentation so. Heh. I prefer not to do this if possible (it would be better to get the underlying problem fixed). It might be worth adding a description of this issue to the BUGS section to the manpage and pointing to it, though. Also, this section shows a `FastCGIServer` directive, which is specific to libapache2-mod-fastcgi, which belongs to non-free packages' section. For example, a free alternative is package libapache2-mod-fcgid, which has not this directive. So this section content could also be rewritten, according to the recommended Apache's FastCGI module by Debian (I don't know if it is libapache2-mod-fcgid). An other and last remark: could it be possible that gitweb's manual belong to gitweb's package This bug report should IMHO better stand with gitweb's other bugs? The main git package in Debian includes git-instaweb, which is why the gitweb docs are in there. Probably I should move git-instaweb to the gitweb package, which would simplify things. Thanks for a pleasant report, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720308: gitweb's manual: please update, amend or remove doc related to FastCGI
Package: gitman Version: 1:1.7.10.4-1+wheezy1 gitweb is supposed to be serveable through FastCGI with Apache, as its manual claimed it (section WEBSERVER CONFIGURATION, subsection Apache with FastCGI). I experimented an error using it, as generated XHTML had double/wrong encoding (i.e. non all UTF-8), when gitweb CGI script encounter my (accented) name, e.g. in git's log. This problem is known, as e.g. reported here: http://git.661346.n2.nabble.com/Gitweb-running-as-FCGI-does-not-print-its-output-in-UTF-8-td7573415.html I encountered this problem on a personal server of mine, with an up-to-date Debian Wheezy: - uname -a Linux saintux 3.2.0-4-686-pae #1 SMP Debian 3.2.46-1 i686 GNU/Linux - dpkg -s libc6 | grep ^Version Version: 2.13-38 - dpkg -s apache2 | grep ^Version Version: 2.2.22-13 - dpkg -s gitweb | grep ^Version; dpkg -s git-man | grep ^Version; dpkg -s git | grep ^Version Version: 1:1.7.10.4-1+wheezy1 The easiest solution could be to not recommend FastCGI for gitweb, and update documentation so. Or perhaps simply remove dedicated section, as it claims to be UNTESTED? Also, this section shows a `FastCGIServer` directive, which is specific to libapache2-mod-fastcgi, which belongs to non-free packages' section. For example, a free alternative is package libapache2-mod-fcgid, which has not this directive. So this section content could also be rewritten, according to the recommended Apache's FastCGI module by Debian (I don't know if it is libapache2-mod-fcgid). An other and last remark: could it be possible that gitweb's manual belong to gitweb's package This bug report should IMHO better stand with gitweb's other bugs? Thank you! -- Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720308: gitweb's manual: please update, amend or remove doc related to FastCGI
Package: git-man Version: 1:1.7.10.4-1+wheezy1 (Sorry for the typo in package's name.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
