Bug#860267: zabbix-server-mysql: Missing /etc/default/zabbix-server-mysql mentionned in README.Debian
Package: zabbix-server-mysql Version: 1:3.0.7+dfsg-1 Severity: normal Dear Maintainer, Installing Zabbix (3.0.7+dfsg-1) with MySQL(MariaDB) on Debian Stretch (currently "testing") for the first time, I failed to fully install Zabbix server as described in documentation, due to missing /etc/default/zabbix-server-mysql in packaging. This file is mentionned in the document /usr/share/doczabbix-server-mysql/README.Debian, so it seems to me that either the doc is outdated or the fle is missing in package. It seems that the file is also missing for the PostgreSQL version of Zabbix. If you need more infos, do not hesitate to ask. Regards, -- Vincent Férotin -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zabbix-server-mysql depends on: ii adduser 3.115 ii fping 3.15-1 ii libc6 2.24-9 ii libcurl3-gnutls 7.52.1-4 ii libgnutls30 3.5.8-5 ii libiksemel3 1.4-3+b1 ii libldap-2.4-2 2.4.44+dfsg-3 ii libmariadbclient18 10.1.22-3 ii libodbc12.3.4-1 ii libopenipmi02.0.22-1.1 ii libsnmp30 5.7.3+dfsg-1.7 ii libssh2-1 1.7.0-1 ii libxml2 2.9.4+dfsg1-2.2 ii lsb-base9.20161125 ii ucf 3.0036 Versions of packages zabbix-server-mysql recommends: ii default-mysql-server1.0.2 ii mariadb-server-10.1 [virtual-mysql-server] 10.1.22-3 ii nmap7.40-1 ii snmpd 5.7.3+dfsg-1.7 ii traceroute 1:2.1.0-2 Versions of packages zabbix-server-mysql suggests: ii logrotate 3.11.0-0.1 pn snmp-mibs-downloader pn sudo ii zabbix-frontend-php 1:3.0.7+dfsg-1 -- no debconf information
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
Bug#630236: funkload: fl-install-demo aborts: wrong path to demo files
Package: funkload
Version: 1.13.0-1
Severity: normal
Tags: patch
X-Debbugs-CC: Vincent Férotin vincent.fero...@gmail.com
`fl-install-demo` fails to correctly run, due to a wrong path for demo files.
Running ``fl-install-demo``::
$ fl-install-demo
fails with this Python traceback::
Extract FunkLoad examples into ./funkload-demo : ...·
Traceback (most recent call last):
File /usr/bin/fl-install-demo, line 9, in module
load_entry_point('funkload==1.13.0', 'console_scripts',
'fl-install-demo')()
File /usr/lib/pymodules/python2.6/funkload/DemoInstaller.py,
line 13, in main
copytree(cache_path, demo_path)
File /usr/lib/python2.6/shutil.py, line 136, in copytree
names = os.listdir(src)
OSError: [Errno 2] No such file or directory:
'/usr/lib/pymodules/python2.6/funkload/demo'
This program *should* work, and copy demo files and structure
into new local ``funkload-demo`` directory,
instead of aborting before doing anything.
This problem seems occurring because, in :func:`main` in :mod:`DemoInstaller`,
:data:`cache_path` points to local ``demo`` directory
(i.e. ``/usr/share/pyshared/funkload/demo``),
whereas Debian package puts its content to
``/usr/share/doc/funkload/examples/demo``.
A trivial patch could consist on setting :data:`cache_path` to effective path,
set in a global var (e.g. :data`DEMO_DEBIAN_PATH`)::
6a7,9
DEMO_DEBIAN_PATH = os.path.join(/, usr, share, doc, funkload,
examples, demo)
11c14,15
cache_path = resource_filename('funkload', 'demo')
---
# cache_path = resource_filename('funkload', 'demo')
cache_path = DEMO_DEBIAN_PATH
Above patch is, well... ugly, but seems to work locally.
I have no idea how doing a better modification,
although I'm quite sure it is possible :-)
In hope it serves,
Vincent Férotin
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages funkload depends on:
ii python 2.6.6-3+squeeze6 interactive high-level object-orie
ii python-pkg-resources0.6.14-4 Package Discovery and Resource Acc
ii python-support 1.0.10 automated rebuilding support for P
ii python-webunit 1:1.3.10-1 Unit testing for web apps with cod
Versions of packages funkload recommends:
pn gnuplot none (no description available)
ii python-docutils 0.7-2 utilities for the documentation of
ii tcpwatch-httpproxy1.3b-3 TCP monitoring and logging tool wi
funkload suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
