Bug#825373: phantomjs: Please backport phantomjs to jessie-backports

2016-05-26 Thread varacanero
Package: phantomjs Version: 2.1.1+dfsg-1 Severity: wishlist -- no debconf information Please backport phantomjs (2.1.1+dfsg-1 or newer) to jessie-backports. Installing from testing is not an option because it would pull in too many dependencies: root@unstable1:~# apt-get install -t stretch

Bug#805007: pnp4nagios: Package for jessie-backports

2015-11-13 Thread varacanero
Package: pnp4nagios Hallo, i saw that pnp4nagios is missing in jessie, please backport it. Greetings, Varac

Bug#758172: isync: Adds . to Maildir directory names

2015-03-17 Thread varacanero
i have the same problem: on the Mailserver (debian stable, dovecot as debian package): # ls -ald .2.3 drwx-- 5 dovenull mail 4096 Mar 17 20:09 .2.3 where 3 is a subfolder of 2 locally: ls -ald 2/.1 drwx-- 5 varac varac 4096 Mar 17 20:09 2/.1 --- .mbsync/Mail ยป mbsync -V -l

Bug#728791: squid-deb-proxy: After restart, proxy is unavailable until restart of avahi-daemon

2014-03-12 Thread varacanero
On 06.11.2013 07:54, Michael Vogt wrote: On Tue, Nov 05, 2013 at 03:44:57PM +0100, Varac wrote: Package: squid-deb-proxy Version: 0.7.2 Severity: important Thanks for your bugreport. sry for the delay ! After restarting, the service is announced by avahi only on ipv6, not on ipv4

Bug#738987: Release announcement

2014-02-14 Thread varacanero
here's the 1.2.4 announce: http://lists.mathias-kettner.de/pipermail/checkmk-announce/2014-February/80.html the abiltiy for multiple config files in a subdirectory was introduced in 1.2.3i1 (an so called innovation release): logwatch: Agent can now use logwatch.d/ to split config to multipe

Bug#724903: vagrant should not install virtualbox

2013-10-06 Thread varacanero
since v. 1.1, vagrant no longer depends on virtualbox as backend. other provideres are possible via plugins. however, 1.2.2-1 from jessie still pulls virtualbox, even i can't find it in the Depends: for this package: ~# lsb_release -a LSB Version:

Bug#689016: nagios-nrpe-server: /etc/init.d/nagios-nrpe-server, stop, does not stops the daemon

2013-01-25 Thread varacanero
output of bash -x /etc/init.d/nagios-nrpe-server stop is attached i am experiencing this behaviour on all (~6) our wheezy machines. thanks for caring, varac additional infos: root@humpback:~# lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux

Bug#689016: found own local bug

2013-01-25 Thread varacanero
Hi, we are sorry but we found out that we were responsible ourselves for that odd behaviour. We deployed nrpe.cfg with a puppet module that changed the pidfile location, which was different to that in the init script. Changing back to the default location (/var/run/nagios/nrpe.pid) solved our

Bug#697692: installation-reports: Broken Partition if only one partition is used

2013-01-09 Thread varacanero
Hi Ben, thanks for the quick reply ! here it is the partition table dump, attached 00 eb 63 90 10 8e d0 bc 00 b0 b8 00 00 8e d8 8e c0 10 fb be 00 7c bf 00 06 b9 00 02 f3 a4 ea 21 06 00 20 00 be be 07 38 04 75 0b 83 c6 10 81 fe fe 07 75 30 f3 eb 16 b4 02 b0 01 bb 00 7c b2 80 8a 74

Bug#697692: installation-reports: Broken Partition if only one partition is used

2013-01-08 Thread varacanero
Package: installation-reports Severity: important Tags: d-i -- Package-specific info: Boot method: network Image version: http://ftp.us.debian.org/debian/dists/squeeze/main/installer-amd64/ Date: Mon, 07 Jan 2013 19:50:00 -0800 Machine: X9SCL/X9SCM mb, 16GB mem, Intel(R) Xeon(R) CPU E3-1265L

Bug#696332: lsb-release: release/codename depend on a successful apt-get

2012-12-19 Thread varacanero
Subject: lsb-release: release/codename depend on a successful apt-get update Package: lsb-release Version: 4.1+Debian8 Severity: normal If an apt-get update fails (i.e. no internet connection), the lsb codename will change to n/a, which shouldn't happen. Release changes to testing/unstable.

Bug#696335: exit-code 0 when apt-get update fails

2012-12-19 Thread varacanero
Subject: apt: exit-code 0 when apt-get update fails Package: apt Version: 0.9.7.6 Severity: normal Hi, apt-get update still exits with an exit-code 0, even if it fails (i.e. due to network connection error). Is this a regression of an very old bug, #41053 ? from the changelog: apt (0.3.12)

Bug#692295: couchdb: initscript doen't stop/restart service

2012-11-04 Thread varacanero
Package: couchdb Version: 1.2.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, I think i encountered a regression of couchdb: Init script doesn't stop or restart the server (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681549) in current couchdb from unstable. The