Hi,
Adrian Bunk writes:
> On Fri, Aug 01, 2025 at 07:57:37PM +0200, Carsten Leonhardt wrote:
>> Hi,
>
> Hi Carsten,
>
>>...
>> I'm not a database expert, but my guess is that SQL statements do not
>> result in atomic operations on disk.
>
> a c
Hi,
Adrian Bunk writes:
> On Wed, Jul 30, 2025 at 09:41:59AM +0200, Carsten Leonhardt wrote:
>> Adrian Bunk writes:
>>
>> > On Mon, Jul 28, 2025 at 12:12:55PM +0200, Carsten Leonhardt wrote:
>>...
>> > Is it true that they would "only notic
Hi Otto,
Otto Kekäläinen writes:
> I skimmed through https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109499
> quickly and my initial thought here is that Bacula (or any other program)
> should not rely on dpkg maintainer scripts to upgrade the database as there
> isn't any guarantees about wh
Hi Adrian,
Adrian Bunk writes:
> On Mon, Jul 28, 2025 at 12:12:55PM +0200, Carsten Leonhardt wrote:
>>...
>> should we recommend upgrading to bacula from backports before the
>> dist-upgrade in the release notes? That will perform the database
>> upgrade and se
Hi,
Chris Hofstaedtler writes:
> On Mon, Jul 28, 2025 at 11:27:17AM +0200, Carsten Leonhardt wrote:
>> Hi,
>>
>> my mail from last week didn't receive any feedback.
>>
>> Let's look at this another way: I think this boils down to the question
>>
Hi,
my mail from last week didn't receive any feedback.
Let's look at this another way: I think this boils down to the question
what kind of support we will need to give after the release. My take is
that it will be either:
a) users where the upgrade didn't go through because they didn't affirm
retitle 1109499 bacula-common: preinst intentionally aborts unattended upgrade
of bacula-director
Hi,
first off: let's be clear as to what is happening. We aren't
"intentionally break"ing upgrades.
Paul Gevers writes:
> On Sun, 20 Jul 2025 12:27:53 +0200 Niels Thykier wrote:
>> Perharps deb
Dear texlive-maintainers,
please update texlive-latex-base to include the newest version of xr
(v5.04), the current version (v5.03) causes bacula-doc to FTBFS.
Regards,
Carsten
Hi,
Chris Zubrzycki writes:
> Here is the fix, or you can move zfs-share to zfs-zed for some reason:
I can confirm this patch works.
Aron Xu writes:
> I'm temped to not ship init.d scripts for Buster if there is any
> important issue open when freeze approaches (e.g. bug #915831).
Please l
Control: merge 917654 917735
Hi,
I'm sorry for having used your time by not reporting this myself. As far
as I can say, one of the last TeX updates introduced this FTBFS. I have
yet to find the exact cause.
Regards,
Carsten
Package: libpaper1
Version: 1.1.25
Severity: serious
Dear Maintainer,
the postrm fails because it uses ucf unconditionally. When executing the
postrm, dependencies are not guaranteed to be installed.
Please see /usr/share/doc/ucf/examples/postrm on how to do it corretly.
See also https://piupar
Package: src:bacula
Version: 9.2.2-1
Severity: serious
On 20.11.18 21:59, Sven Hartge wrote:
[...] when "-u root -g root -k" is set, even though the process runs as
root, it doesn't have the proper capabilities anymore.
Package: src:bacula
Version: 9.2.2-1
Severity: serious
postgresql-server-dev-11 depends on clang-7, this depends on
libclang-common-7-dev and this contains 64bit libraries which makes it
in turn depends on other 64bit libraries.
Hence the "if test -d /usr/lib64" in db.m4
https://sources.debian.o
Hi,
I found the source. Upstream commit
ac391519c8e4125db0662dea92e7550d95bd9a16 "Permit catalog to contain
negative FileIndexes", added shortly before the 9.2.1 release.
This makes me wonder about how these schema updates would reach people
that are already on db version 16. For us, we can fix t
Source: bacula
Version: 9.2.1-1
Severity: serious
Hi,
according to piuparts:
applying upgrade sql for 7.4.4+dfsg-6 -> 9.0.0.
Error: near line 84: near "MODIFY": syntax error
Error: near line 85: near "MODIFY": syntax error
Error: near line 86: near "MODIFY": syntax error
https://piupart
On Tue, 25 Jul 2017 14:36:03 +0300 Adrian Bunk wrote:
> Source: approx
> Version: 5.9-1
> Severity: serious
>
> Not sure whether there's a pattern when it fails
> or whether tests fail randomly (and frequently):
>
> https://buildd.debian.org/status/package.php?p=approx&suite=sid
> https://tests.
Source: bacula
Version: 5.2.6+dfsg-9.3
Severity: serious
The main configuration files (bacula-{dir,sd,fd}.conf, bconsole.conf,
bat.conf) in the bacula packages aren't registered as belonging to their
respective packages. This leads to the following problem:
Due to the restructuring of the packagi
Michael Biebl writes:
> I don't remember seeing the test suite to get stuck completely (as it
> apparently did on kfreebsd-* now).
It could well be a general problem of the kfreebsd buildds, as they
regularly get completely stuck during the build of gcc-6 in the last
weeks.
Should I go ahead an
Hi,
> The changes in 0.18.5-3 were supposed to fix #837067, i.e. the test
> suite failing to pass on a single CPU machine.
>
> Did you test that as well?
I did now, on a virtual single CPU kfreebsd-amd64 machine. 6 test runs,
no failures.
Or is this too modern?
$ sysctl hw | head -n 3
hw.machin
Michael Biebl writes:
> If you are sure it fixes the issue, feel free to upload without delay.
I've made a dozen test runs of the collection tests on arm64, all
passed. After double checking the buildd logs, I noticed a different
failing test on mipsel, I've made 5 complete test runs there witho
) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/0004-tests-collection-add-setup-delay.patch:
++ Fix failing test "collection/delete-sync" by correctly placing
+ the delay. Closes: #855951.
+
+ -- Carsten Leonhardt Sat, 18 Mar 2017 15:56:31 +
+
libsecret
> Something weired seems to have happend to hol88-library. On some
> architectures (arm64, hppa, m68k), the package is simply empty. Upon
> closer inspection it turns out that the upstream build system simply
> hides build failures.
>
> https://sources.debian.net/src/hol88/2.02.19940316-32/Makefil
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 "NO_ZERO_D
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
> (Job,Name,Type,Level,JobStatus,SchedTime,JobTDate,ClientId,Comment
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 sta
Control: severity -1 important
bacula 7.4.4+dfsg-3 switched to using libssl1.0-dev, so the release
critical severity no longer applies.
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
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 cases when it was allowed.
> In this case I'm n
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.
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
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
make[1]
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
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}
http://source
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.
Carste
clone 825064 -1
reassign -1 dbconfig-common
thanks
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 upda
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 "dpkg-re
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
38 matches
Mail list logo
