Bug#337448: asterisk-web-vmail: Missing dependency

Package: asterisk-web-vmail Version: 1:1.0.9.dfsg-5 Severity: important After installing i get this error displayed when trying to access the cgi on my webserver: Software error: Can't locate DBI.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.7 /usr/local/share/perl/5.8.7

Bug#352044: closed by sean finney [EMAIL PROTECTED]

Would be nice if the fix would make it into the next debian release :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#499619: bacula-sd-mysql: man page for bscan wrong

Package: bacula-director-mysql Version: 2.4.2-1 Severity: normal I was wondering why bscan won't connect to the MySQL-Server, until I found out that the man page is incorrect. The man page for example says: -p password Specify database password (default: none) While bscan

Bug#443563: nagios-plugins-basic: check_http returns warning instead of critical

Package: nagios-plugins-basic Version: 1.4.5-1 Severity: normal When checking the validity of ssl certificates like check_http --ssl -H $HOSTADDRESS$ -C $ARG1$ critical state is only entered 24 hours after expiry. See this excerpt from the log: [2007-08-16 13:32:41] SERVICE ALERT:

Bug#422819: And another trace

A guest (2 vcpus) was to be rebooted, then the host hung itself up: Jul 27 12:46:45 kernel: --- [cut here ] - [please bite here ] - Jul 27 12:46:45 kernel: Kernel BUG at drivers/xen/core/evtchn.c:481 Jul 27 12:46:45 kernel: invalid opcode: [1] SMP Jul 27 12:46:45

Bug#419983: clamav-milter: init.d script fails to stop service correctly

Package: clamav-milter Version: 0.90.2-1~volatile1 Severity: normal The following transcript says it all: # /etc/init.d/clamav-milter stop Stopping Sendmail milter plugin for ClamAV: clamav-milter Waiting . . . . . . . . . . . . . . . . /etc/init.d/clamav-milter: line 101: kill:

Bug#419983: clamav-milter: init.d script fails to stop service correctly

lsb-base3.1-10 Linux Standard Base 3.1 init script functionality # cat /var/run/clamav/clamav-milter.pid -15056 And I checked the other pid-files on these boxes, they only contain positive integers. Regards, Carsten Leonhardt

Bug#319997: nagios-plugins: check_nmap is missing

Package: nagios-plugins Version: 1.4-6 Severity: normal /etc/nagios-plugins/config/nmap.cfg refers to /usr/lib/nagios/plugins/check_nmap which is missing from the package. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500,

Bug#317802: ewiki: links to http when run on https

Package: ewiki Version: 1.02-4 Severity: normal When editing something like here: https://grome.lan/ewiki/?id=edit/FrontPage pressing save sends me to http://grome.lan:443/ewiki/?id=FrontPagethankyou=1 ^^ which won't work of course. -- System Information: Debian Release: testing/unstable

Bug#484646: clamav-daemon: support for external unpackers

Package: clamav-daemon Version: 0.93~dfsg-volatile1 Severity: wishlist Reading the clamd.conf manpage, I can't find an equivalent to clamscan's --unrar, --unzip etc. options. This would be helpful for formats that are not handled internally (eg. rar), especially in combination with clamav-milter

Bug#484642: clamav: Virus not detected in RAR-archive inside email

Package: clamav Version: 0.93~dfsg-volatile1 Severity: normal The first example shows scanning a file which is an email containing a mime/base64 encoded rar-file which in turn contains a trojan. The second example shows scanning the rar-file directly, which works out ok: --- 1 --- $ clamscan

Bug#484642: clamav: Virus not detected in RAR-archive inside email

Could you submit the email to upstream as a failed scan? It sounds like a bug in the base64 parser. Reported as https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1050 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#484646: clamav-daemon: support for external unpackers

Stephen Gran [EMAIL PROTECTED] writes: This one time, at band camp, Carsten Leonhardt said: Reading the clamd.conf manpage, I can't find an equivalent to clamscan's --unrar, --unzip etc. options. This would be helpful for formats that are not handled internally (eg. rar), especially

Bug#485573: simpleproxy: typo in syslog message

Package: simpleproxy Severity: minor There is a typo in the syslog message (inted instead of inetd). Patch attached. --- simpleproxy.c.orig 2005-08-26 06:45:46.0 +0200 +++ simpleproxy.c 2008-06-10 10:07:14.0 +0200 @@ -441,12 +441,12 @@ SrcSockFD = 0; // stdin

Bug#485932: ftp-proxy: missing documentation files

Package: ftp-proxy Version: 1.9.2.4-2 Severity: normal The files /usr/share/doc/ftp-proxy/ftp-proxy-10.html /usr/share/doc/ftp-proxy/ftp-proxy-11.html are referenced from the other ftp-proxy*.html files, but are not included in the package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with

Bug#352044: nagios-images: bernhard/airo350.gd2 is really a tar archive

Package: nagios-images Version: 0.1 Severity: normal The file bernhard/airo350.gd2 is not a gd2 file, but a tar archive containing the rest of bernhard/* again. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable')

Bug#352044: closed by sean finney [EMAIL PROTECTED] (Bug#352044: fixed in nagios-images 0.2)

The bug is back in 0.3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#585037: #585037 still in 5.0.2-2.2+b1

I can confirm it's still there. I tried to use a password that included a slash. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#529419: Man page for pure-ftpd-wrapper wrong

Package: pure-ftpd-common Version: 1.0.21-12 Severity: minor The man page describes FileSystemCharset as a configuration option, but the program actually uses FSCharset instead. # /etc/init.d/pure-ftpd restart Restarting ftp server: /usr/sbin/pure-ftpd-wrapper: Invalid configuration file

Bug#350547: Current version works

Setting the time with ntpdate works here. ntpdate package version: 1:4.2.4p6+dfsg-1 # uname -a GNU/kFreeBSD rackhir.ct.lan 7.1-1-amd64 #0 Tue Apr 14 01:03:37 CEST 2009 x86_64 amd64 Intel(R) Pentium(R) Dual CPU E2160 @ 1.80GHz GNU/kFreeBSD -- To UNSUBSCRIBE, email to

Bug#583850: Bug #583850: inosync: Bug fixed upstream

Fax: +49-241-990012-10 Sitz der Gesellschaft: Aachen Registergericht: Amtsgericht Aachen, HRA 7694 Persönlich haftende Gesellschafterin: carotec Verwaltungs GmbH Sitz der Gesellschaft: Aachen Registergericht: Amtsgericht Aachen, HRB 16151 Geschäftsführer: Carsten Leonhardt, Roger

Bug#748788: paris-traceroute: segmentation fault on kfreebsd-amd64

Package: paris-traceroute Version: 0.92-dev-2 Severity: normal Usertags: kfreebsd The program segfaults on kfreebsd-amd64: (gdb) run 8.8.8.8 Starting program: /usr/sbin/paris-traceroute 8.8.8.8 Program received signal SIGSEGV, Segmentation fault. 0x000801244b9b in _IO_vfscanf () from

Bug#738979: Fixed in upstream v1.0

Hi, this is fixed in upstream version 1.0. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#699149: bacula-fd: should not run as 'root' by default

On Mon, 28 Jan 2013 01:39:52 -0700, Teodor MICU wrote: The other Bacula services are started by 'bacula' user. Only bacula-fd is started as 'root'. However, I've just discovered that it can function properly with limited privileges too. I'm guessing you aren't doing full system backups?

Bug#679479: bacula-fd fails to start because network is not initialized

Dear Tom, is (or was, as your bug report is over 2 years old now) there a specific reason why you had the FDAddress = faerun.epperly.home directive in your bacula-fd.conf? Just omitting the directive should (have) give(n) you a functioning backup. Yours, Carsten -- To UNSUBSCRIBE, email to

Bug#679479: bacula-fd fails to start because network is not initialized

Gesellschaft: Aachen Registergericht: Amtsgericht Aachen, HRA 7694 Persönlich haftende Gesellschafterin: carotec Verwaltungs GmbH Sitz der Gesellschaft: Aachen Registergericht: Amtsgericht Aachen, HRB 16151 Geschäftsführer: Carsten Leonhardt, Roger Koll -- To UNSUBSCRIBE, email to debian-bugs-dist

Bug#486131: Problem still exists in wheezy 5.2.6

Dear Pierre, I've upgraded now to 5.2.6 and can confirm the problem still exists in latest stable packages. The crash ever happens when a job is started and the fd is not available e.b. because the host is switched off. It is reproducible. could you provide a backtrace from the new version,

Bug#742352: bacula-console: shows help links pointing to nowhere

Dear Alberto, This link in bconsole is broken... i looked in archive.org and it didnt show either. Is hard to point to what section of the faq is really trying to point to Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00376 for help.

Bug#680714: [pkg-bacula-devel] Bug#680714: bacula 7.0.5 has been release in july 2014

since bacula 7.0.5 has been released in july last year, i wanted to ask if there are any plans to package it (possibly post the jessie release), as i want to deploy it in an installation and would therefore have to package it myself if there are no plans sofar. yes I'm planning to package it.

Bug#706539: definitely uses urandom to generate keys

I can confirm that versions 0.9.3-1 and 10.0.0-2 use /dev/urandom to generate keys, I checked with strace: $ strace -o /tmp/xca.log xca Opening database: /tmp/test.xdb [generate key] $ grep random /tmp/xca.log open(/dev/urandom, O_RDONLY) = 13 open(/dev/urandom,

Bug#740014: more manpages missing from pf package

Hi, additionally to the reported missing manpage pf.os(5), the two manpages pf(5) pf.conf(5) are also missing in versions 10.1~svn273304-1 (jessie) and 10.1~svn273304-2 (experimental) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe.

Bug#783083: bacula-director-common: Bacula director has problems with kernel linux-image-3.16.0-0.bpo.4-amd64 (v3.16.7-ckt7-1~bpo70+1)

Hi Artur, could you please send the output of ps xuaw | grep bacula-dir - after reboot - after the connect with bat - after /etc/init.d/bacula-dir stop - after /etc/init.d/bacula-dir start Sounds like the director might be hanging, it could be interesting to see if the PID changes and what

Bug#764213: Trying to understand buglog (rsyslog, kfreebsd, /dev/log)

Hi Christoph, Are we sure this is fixed in that BPO version? I have a jessie here which seems to have exactly that problem. I just checked again, I had a wheezy installation where logging didn't work, upgraded to 7.6.3-2~bpo70+1 and now logging works. After that I now downgraded two

Bug#736461: Please enable hardened build flags

There is an Ubuntu bug where the upstream author writes that he recommends not to use Fortify Source. https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/265102

Bug#764314: bacula: PostgreSQL syntax error

Hi, * What led up to the situation? Upgrade from 5.2.6+dfsg-9.2 * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? bacula=# SELECT DISTINCT j.JobId, j.Name AS JobName, j.Level, j.ClientId, j.StartTime,

Bug#793794: bacula-director-pgsql: In the restore command parameter restore_job doesn' work (rejected)

Hi Stefano, thank you for your bug report. issuing a RESTORE command containing a FILESET= and a RESTORE_JOB= parameters, the command is rejected. If you type RESTOREJOB= instead, the command is accepted, but the RESTOREJOB has no effect and a Restore Job is asked for. The problem is due

Bug#645593: Lowering severity to normal

limit source bacula severity 645593 normal thanks This bug does not have a "major effect on the usability" of the package, therefore lowering the severity to normal. If this bug still applies, a workaround can be to use the textmode bconsole and pipe the output to a file.

Bug#764314: Lowering severity to normal

limit source bacula severity 764314 normal thanks >From the information provided it is not clear that this is an important bug. Lowering the severity to normal.

Bug#728582: bacula-sd on kFreeBSD: unable to use tape drive

Hi, > But when using the bacula tools, tape access fails: [...] > 03-Nov 10:30 btape JobId 0: End of Volume "" at 0:0 on device "Drive-1" > (/dev/nsa0). Write of 64512 bytes got 0. > 03-Nov 10:30 btape JobId 0: Error: Error writing final EOF to tape. This > Volume may not be readable. >

Bug#780155: ITP: baculum -- Baculum WebGUI tool for Bacula Community program

Hallo Marcin, > [...] but I understand that the framework has to be packaged as > independent deb package. That would be optimal. I had a quick look, and only tinymce seems to be packaged in Debian already, although it looks very neglected. Maybe it would be a good question to ask on the

Bug#780155: ITP: baculum -- Baculum WebGUI tool for Bacula Community program

Hello Marcin, I'm from the bacula packaging team and have just found your ITP for baculum. It's been 5 months since your last message to the ITP-bug, and I am wondering if you are still working on the packaging. I'm also guessing that there will be a need for coordination between the bacula and

Bug#737821: reopen bug 737821

limit source bacula reopen 737821 found 737821 7.0.5+dfsg-2 tags 737821 + confirmed pending thanks Actually, upstream fixed this after releasing v7.2.0 with commit http://www.bacula.org/git/cgit.cgi/bacula/commit/?h=Branch-7.2=81a823a5d021edf1266599ad86e61d0af713f40b

Bug#807242: ITP: bacula-fd5.2 -- legacy bacula file daemon

Package: wnpp Severity: wishlist Owner: Debian Bacula Team * Package name: bacula-fd5.2 Version : 5.2.13 Upstream Author : Kern Sibbald * URL : http://www.bacula.org * License : Mainly GPL, parts LGPL, BSD and others.

Bug#805306: [pkg-bacula-devel] Bug#805306: Would be nice to have a bacula-fd-legacy...

Hi, > I confess I don't know how much work it'd be, but it'd be nice to keep > around the older version of the file daemon as a separate package. if I were to prepare such a package, I'd want to base it on 5.2.13. And of course I'd want it have all the applicable improvements that the current

Bug#806263: Additional information on otrs connects to cloud.otrs.com

Dear Maintainer, if the system can't reach cloud.otrs.com, the cron job regularly emits the error below, which is rather annoying. Attempts to disable this and the second OTRSBusiness check fail because they are read-only in SysConfig. I would suggest disabling these checks by default.

Bug#806205: bacula-fd

limit source bacula forwarded 806205 http://bugs.bacula.org/view.php?id=2185 thanks Dear Nicholas, > The error message points to an upstream webpage that does NOT state > this restriction. I've reported this upstream, together with my proposed addition to the FAQ: "Please also remember that

Bug#806707: approx cronjob fails on kfreebsd and hurd

Package: approx Version: 5.5-1 Severity: normal Control: tags -1 patch Dear Maintainer, I have an approx installation on a kfreebsd-amd64 machine. The cron job emits the following error: > /etc/cron.weekly/approx: > nice: ionice: No such file or directory > run-parts: /etc/cron.weekly/approx

Bug#826163: [pkg-bacula-devel] Bug#826163: bacula-*.service disabled after upgrade

Hi Sven, > After the upgrade from 7.0.5 to 7.4.0 the systemd services are not > automatically enabled if the SysV init-script was. > > This results in the necessary daemons not being started and also not > starting after a reboot. > > A manual "systemctl enable bacula-XXX.service" is necessary to

Bug#826803: Insecure use of password

Package: fuel-web Version: 9.0+dfsg1-3 Severity: grave Tags: security Dear Maintainer, while investigating the use of PGPASSFILE I found the following code in package fuel-web, file nailgun/tools/env_functions.sh on line 119: echo "*:*:*:${DB_ROOT}:${DB_ROOTPW}" > ${DB_ROOTPGPASS}

Bug#826803: Work in progress, use case limited

Hi Thomas, [good reasons skipped] > For all of these reasons, I'm lowering the severity of this bug to > "important". Sure. > Once all of Fuel is uploaded to Debian *and* fully usable, I will very > much welcome security audit of the whole thing. Until then, I don't > think it's very valuable

Bug#826994: Missing init-script(s)?

Package: zfsutils-linux Version: 0.6.5.7-1 Severity: important Dear Maintainers, I was wondering why my zpools aren't available after a reboot, until I found out that you provide systemd service files that would make them available, but no init file(s). Carsten

Bug#826163: [pkg-bacula-devel] Bug#826163: bacula-*.service disabled after upgrade

Hi Sven, > After the upgrade from 7.0.5 to 7.4.0 the systemd services are not > automatically enabled if the SysV init-script was. > This results in the necessary daemons not being started and also not > starting after a reboot. > > A manual "systemctl enable bacula-XXX.service" is necessary to

Bug#825064: Bacula director does not start silently due to database mismatch

Hi, I've reopened the bug, and as suggested by Paul cloned it to have a copy filed against dbconfig-common. Please use bug #825735 for the issue related to dbconfig-common, and bug #825064 for the issue "bacula silently fails to start" due to database errors, for which I am testing a fix.

Bug#825064: Bacula director does not start silently due to database mismatch

clone 825064 -1 reassign -1 dbconfig-common thanks

Bug#728446: apcupsd: diff for NMU version 3.14.12-1.2

, #810396) + * Build-Depend on libgd-dev instead of the deprecated libgd2-noxpm-dev. + + -- Carsten Leonhardt <l...@debian.org> Mon, 29 Feb 2016 16:13:41 +0100 + apcupsd (3.14.12-1.1) unstable; urgency=medium * Non-maintainer upload. diff -u apcupsd-3.14.12/debian/control apcupsd-3.14.12/

Bug#811089: [pkg-bacula-devel] Bug#811089: bconsole: typo forbids non-interactive restore

Hi Rhonda, > there is a typo in src/dird/ua_restore.c which hinders starting a > non-interactive restore. could you give me an example invocation for such a restore? Which version did you patch - the old 5.2.6 or the 7.0.5 from testing? leo

Bug#822221: ITP: flipcoin -- flip an adjustable coin for random exit status

Hi, > Package: wnpp > Severity: wishlist > Owner: Rudi Cilibrasi > > * Package name: flipcoin > Version : 1.0.0 > Upstream Author : Rudi Cilibrasi > * URL : https://github.com/rudi-cilibrasi/flipcoin > *

Bug#825064: [pkg-bacula-devel] Bug#825064: Bacula director does not start silently due to database mismatch

Hi Klaus, >> I've tested an update from 7.0.5, with dbc_install='false' in >> /etc/dbconfig-common/bacula-director-sqlite3.conf. This time the update >> wasn't applied, apparently dbconfig-common doesn't apply any changes >> when this is set. >> >> Please change it back to 'true' and run

Bug#807242: change package name to bacula-legacy-fd, which is more generic

retitle 807242 ITP: bacula-legacy-fd -- legacy bacula file daemon thanks Update to the ITP: * Package name: bacula-legacy-fd Version : 5.2.13 Upstream Author : Kern Sibbald * URL : http://www.bacula.org * License : Mainly GPL, parts LGPL, BSD and others. See

Bug#825064: [pkg-bacula-devel] Bug#825064: Bacula director does not start silently due to database mismatch

Hi Klaus, did you allow dbconfig common to update the database? Please send the output of: fgrep dbc_upgrade /etc/dbconfig-common/bacula-director-sqlite3.conf If it shows dbc_upgrade='true', could you please check for relevant messages in /var/log/apt/term.log around the line "applying upgrade

Bug#825064: Bacula director does not start silently due to database mismatch

Dear Paul, it would be very helpful if you - as the dbconfig-common maintainer - would be able to spare a few minutes to clear up the following issue, because the discussion is about dbconfig-common by now. Klaus, the bug reporter, updated from bacula 7.0.5 to 7.4.0. This requires a database

Bug#831282: Typo in po/de.po

Package: bash Severity: minor Tags: patch Dear Maintainer, there is a typo in the german help for the builtin "command". Patch attached. Carsten diff --git a/po/de.po b/po/de.po index 0d28040..8cda9a2 100644 --- a/po/de.po +++ b/po/de.po @@ -2828,7 +2828,7 @@ msgstr "" "Führt ein einfaches

Bug#832434: dpkg-shlibdeps.1: typos

Package: src:dpkg Version: 1.18.9 Severity: minor Tags: patch Justification: documentation Dear Maintainer, I noticed two typos / grammatical errors in dpkg-shlibdeps.1 and attached a patch. The phrase "they uses" also occurs in several files in man/po/ but the patch does not touch that

Bug#832357: bacula-director-*: fails to upgrade from 'sid' - trying to overwrite /etc/init.d/bacula-director

tags 832357 + pending thanks Hi Andreas, thank you for your bug report. The problem is already fixed in our git repository, but we want to finish some further packaging changes before the next upload. Carsten

Bug#806205: bacula-fd: authentication errors when bacula-fd is newer than the director

Control: reassign -1 bacula-doc Control: tags + fixed-upstream The FAQ for authentication errors was extended for this case in the documentation for version 7.4.x, possibly earlier. I'm reassigning it to bacula-doc as it was fixed there. Packaging the current documentation is on the Bacula

Bug#830999: [pkg-bacula-devel] Bug#830999: bacula-director-mysql db-config installation fails with reference to ${db_name}

tags 830999 + confirmed patch thanks Dear Nish, > Ubuntu 16.10 is currently in-sync with Debian unstable's packaging and > I am seeing an installation failure with bacula-director-mysql. thank you for your bug report. I can confirm the error and I have commited a - so far untested - fix to our

Bug#831804: Fails to build on arch:all buildd

Package: src:apcupsd Version: 3.14.14-0.1 Severity: serious buildlog excerpt: dh_fixperms chmod 0755 debian/apcupsd/etc/apcupsd/killpower chmod: cannot access 'debian/apcupsd/etc/apcupsd/killpower': No such file or directory debian/rules:46: recipe for target 'override_dh_fixperms' failed

Bug#831396: procps: [ps] fails on kfreebsd

> Ah ha, I think I know the problem. And it is related to the kernel version. > asdfasdf has this: > $ more /proc/sys/kernel/osrelease > 2.6.16 > I bet you have something else, something bigger than 2.6.27 > > The relevant procps code: > if (linux_version_code < LINUX_VERSION(2, 6, 27)) >

Bug#831396: procps: [ps] fails on kfreebsd

Hi, > Could it be they have "improved" the procfs in some way from 9.x to 10.x? > Can you strace the ps command? I'm looking for opens under /proc that fail. this is the end of a ktrace: 3857 ps CALL open(0x80146de1b,0,0) 3857 ps NAMI "/proc/sys/vm/min_free_kbytes" 3857 ps

Bug#830999: [pkg-bacula-devel] Bug#830999: bacula-director-mysql db-config installation fails with reference to ${db_name}

tags 830999 + confirmed patch thanks Dear Nish, > That seems very right to me, I will try and test it here too. > > update_mysql_tables.in > update_mysql_tables_10_to_11.in > update_mysql_tables_11_to_12.in > > may need similar changes (they did in 7.4.1+dfsg-1, and I haven't > rebased yet to

Bug#831396: procps: [ps] fails on kfreebsd

Package: procps Version: 2:3.3.12-2 Severity: normal User: debian-...@lists.debian.org Usertags: kfreebsd Dear Maintainer, ps fails on kfreebsd-amd64: # ps Error: /proc must be mounted To mount /proc at boot you need an /etc/fstab line like: proc /proc procdefaults In the

Bug#825800: graphicsmagick: CVE-2016-5118

Hi László, maybe it would be possible to use 1.3.24 for a stable update? I think the current situation with the unpatched graphicsmagick in stable is quite unacceptable. Carsten

Bug#854042: db insert crashes

Control: severity -1 important Hi Jörg, >> So, did you upgrade your MySQL-Server just before the errors started >> occuring? If yes, from which version to which? > Yes. The update was at 2017-02-01 from version 5.6.35-1 to 5.7.17-1. ok. To make your backups work again, you can remove

Bug#854042: db insert crashes

Control: reassign -1 bacula-director-mysql Hi, > since some days I get this and all job fails: > > [quote] > 03-Feb 12:05 merkur.jff-webhosting.net-dir JobId 0: Fatal error: > sql_create.c:86 Create DB Job record INSERT INTO Job >

Bug#854954: ITA: inosync -- notification-based directory synchronization daemon

Control: retitle -1 ITA: inosync -- notification-based directory synchronization daemon Control: owner -1 ! I intend to adopt this package. - Carsten

Bug#854684: bacula doesn't officially support SQLite3

Dear Serge, > Is it a good option to propose a default SQLite3 database ? > > SQLite3 is no longer supported : > > https://sourceforge.net/p/bacula/mailman/message/35656463/ > https://sourceforge.net/p/bacula/mailman/message/35655925/ > >> The code for SQLite3 remains in Bacula, but it is >> no

Bug#813533: inosync: [PATCH] So someone can -c configfile a dot file

Control: tags -1 - patch + moreinfo Hi Eric, I'm preparing a new Debian package for inosync and was looking at your bug report: > line 134: > add: > > if configfile.startswith("."): > configfile = configfile.strip(".") > > right after the > > if configfile.endswith(".py"): I've

Bug#813533: inosync: [PATCH] So someone can -c configfile a dot file

Control: tags -1 - moreinfo Control: severity -1 wishlist Control: retitle -1 Please allow a dotfile to be used as configfile Hi Eric, thanks for your feedback. I'm setting the bug to severity "wishlist", maybe someone will come up with a solution. - Carsten

Bug#851687: mariadb-server-10.1 uninstallable on kFreeBSD and hurd

Package: mariadb-server-10.1 Version: 10.1.20-3 Severity: important User: debian-...@lists.debian.org Usertags: kfreebsd This package is uninstallable on kfreebsd-any and hurd-i386 due to it's dependencies iproute2 and lsof which are only available on linux.

Bug#851687: [debian-mysql] Bug#851687: mariadb-server-10.1 uninstallable on kFreeBSD and hurd

Otto Kekäläinen writes: > Somebody complained to me about using age old iproute, so I updated it > in > https://anonscm.debian.org/cgit/pkg-mysql/mariadb-10.1.git/commit/?id=4d96f3c7be53afe605b3f5d1b03ba6a28c805e82 > > What is your suggestion on how to solve this? Downgrade

Bug#855645: [pkg-bacula-devel] Bug#855645: btape fill test fails

Control: reassign -1 bacula-sd Control: severity -1 important > Upon installing a new tape drive, I did a "btape fill" test, as advised > in the Bacula manual. This worked when I last installed a tape drive > with version 5.2.6. An example output of the error reported with 7.4.4 is as follows:

Bug#856236: unblock: bacula/7.4.4+dfsg-6 (pre-approval)

+dfsg/debian/changelog 2017-02-26 13:39:25.0 +0100 @@ -1,3 +1,10 @@ +bacula (7.4.4+dfsg-6) unstable; urgency=medium + + [Sven Hartge] + * Backport fix for btape fill test from 7.4.5 (Closes: #855645) + + -- Carsten Leonhardt <l...@debian.org> Sun, 26 Feb 2017 13:39:25 +0100 + bacula

Bug#486131: bacula-sd crashes with unreachable FDs

Hi Pierre, sorry for the long delay before getting back to you. Pierre Bernhardt writes: > I tried to get a backtrace allready, but it was not possible. However I don't > understood why backtrace was not created :-( > > The only content what i got from baculas home

Bug#780155: ITP: baculum -- Baculum WebGUI tool for Bacula Community program

Hi Marcin, it's been a while since we last heard of each other, have you succeeded in making any progress here? - Carsten

Bug#655346: bat: "Run Restore Job" window should mention the volume name

Control: tag -1 + moreinfo Control: tag -1 - upstream Hi, On Tue, 10 Jan 2012 16:36:04 +0200 Teodor wrote: > During the restore operation one step is selecting the volume name that > will be used. However, on the final step when you confirm the job details > the volume name

Bug#780155: ITP: baculum -- Baculum WebGUI tool for Bacula Community program

Control: retitle -1 RFP: baculum -- Baculum WebGUI tool for Bacula Community program Control: submitter -1 pkg-bacula-de...@lists.alioth.debian.org Hi Marcin, thanks for your feedback. > You can close this ITP requires if you want. I am not sure what is the > procedure for this type of cases.

Bug#728582: bacula-sd on kFreeBSD: unable to use tape drive

Control: retitle -1 Add tape support for GNU/kFreeBSD Control: severity -1 wishlist Control: reassign bacula-sd Hi, as GNU/kFreeBSD is not fully supported by upstream, I consider this a wishlist bug. - Carsten

Bug#706362: Bug #706362: bacula-director-pgsql: upgrade scripts may not set permissions

Control: tag -1 moreinfo Hi, I'm looking through old bug reports for the bacula package. You reported wrong/missing access privileges after restoring an old catalog backup and then manually upgrading it by running the upgrade scripts. You noted that some tables have empty access privileges,

Bug#644240: bat: ASSERT failure in QList::operator[]: "index out of range"

Control: tag -1 + moreinfo unreproducible Bună Teodor, I was looking at this old bug report: > Sometimes when I select to restore "All files" from a specific job, > 'bat' will crash with this message: > | ASSERT failure in QList::operator[]: "index out of range", file > |

Bug#825800: graphicsmagick: CVE-2016-5118

László Böszörményi (GCS) writes: > On Tue, Sep 20, 2016 at 9:56 AM, Stephan Großberndt > wrote: >> Do you think 1.3.25-2 might be the used for a stable update? > Upgrade to a newer version in stable is not easy and I can remember > one, maybe two

Bug#699149: bacula-fd: should not run as 'root' by default

Control: tag -1 - wontfix Control: tag -1 + confirmed Control: retitle -1 Make running bacula-fd as non-root easier While the default will not be to run as non-root, it will likely become a debconf question, and so could be preseeded. And to correct my earlier statement - it is possible to

Bug#838080: bacula-director-pgsql: make_catalog_backup fails

Package: bacula-director-pgsql Version: 7.4.3+dfsg-6 Severity: serious XXX_DBUSER_XXX is not replaced by the name of the database user in make_catalog_backup: user=${2:-XXX_DBUSER_XXX} consequently, the catalog backup fails.

Bug#835171: Typo in ucfr(1)

Package: ucf Version: 3.0036 Severity: minor Dear Maintainer, there is a typo in the man page for ucfr(1): "over ridden" should be "overridden". - Carsten

Bug#835120: lintian: false positive: virtual-package-depends-without-real-package-depends in experimental

Package: lintian Version: 2.5.46 Severity: normal Dear Maintainer, lintian reports the following for bacula 7.4.3+dfsg-3, which is currently in experimental: bacula-server W virtual-package-depends-without-real-package-depends depends: bacula-director Probably the confusion comes

Bug#835171: Acknowledgement (Typo in ucfr(1))

Two more findings, hopefully you don't mind following up on the first bug for this: ucfr(1) man page: the examples section points to /usr/share/doc/examples, it probably should point to /usr/share/doc/ucf/examples s/coneected/connected/ in /usr/share/doc/ucf/examples/postinst.gz

Bug#828244: [pkg-bacula-devel] Bug#828244: bacula: FTBFS with openssl 1.1.0

Control: tag -1 + help > There is a libssl-dev package available in experimental that contains a recent > snapshot, I suggest you try building against that to see if everything works. > > If you have problems making things work, feel free to contact us. As adapting openssl-related code is not my

Bug#843838: [pkg-bacula-devel] Bug#843838: Fail to access config file

Hi, thanks for your report. As a quick fix "chgrp bacula /etc/bacula/bacula-dir.conf" should help. To further understand your problem though, could you please also send us the output of: groups bacula cat /etc/defaults/bacula-dir.conf and if you use systemd, any local modifications of the

Bug#828244: bacula: FTBFS with openssl 1.1.0

Hi Kurt, > OpenSSL 1.1.0 is about to released. During a rebuild of all packages using > OpenSSL this package fail to build. A log of that build can be found at: > https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/bacula_7.4.0+dfsg-1_amd64-20160529-1407 [...] > If you have problems

Bug#828244: bacula: FTBFS with openssl 1.1.0

Kurt Roeckx <k...@roeckx.be> writes: > On Fri, Oct 14, 2016 at 10:56:34AM +0200, Carsten Leonhardt wrote: >> Is the plan still to have OpenSSL 1.1 in stretch? There were several >> concerns raised in the thread following your announcement in June. > > Yes it is. I don'

Bug#828244: bacula: FTBFS with openssl 1.1.0

Control: severity -1 important bacula 7.4.4+dfsg-3 switched to using libssl1.0-dev, so the release critical severity no longer applies.

  1   2   3   >