[pkg-bacula-devel] Making bacula-director-{pgsql, mysql, sqlite3} Arch: all

[Sven Hartge]

Um 23:57 Uhr am 14.12.18 schrieb Sven Hartge:

> I'll meditate a bit over debian/rules and try to figure out, which
> packages to use as link-doc target for
> bacula-director-{pgsql,mysql,sqlite3}.

Well, there is no other package, so linking the docs for those packages is
out of the question now. Investigating.

But, and this is a big but:

,----
| E: bacula source: not-binnmuable-any-depends-all bacula-director -> bacula-director-pgsql
| N:
| N:    The package is not safely binNMUable because an arch:any package depends
| N:    on an arch:all package with a (= ${binary:Version}) relationship. Please
| N:    use (= ${source:Version}) instead.
`----

,----
| E: bacula source: not-binnmuable-all-depends-any bacula-director-sqlite3 -> bacula-common-sqlite3
| N:
| N:    The package is not safely binNMUable because an arch:all package depends
| N:    on an arch:any package with a strict (= ${source:Version}), or similar,
| N:    relationship.
| N:
| N:    It is not possible for arch:all packages to depend so strictly on
| N:    arch:any packages while having the package binNMUable, so please use one
| N:    of these, whichever is more appropriate:
| N:
| N:      Depends: arch_any (>= ${source:Version})
| N:      Depends: arch_any (>= ${source:Version}),
| N:       arch_any (<< ${source:Version}.1~)
`----

Changing the dependency releationship between those packages makes me feel
uneasy, because it can introduce problems during an upgrade, for example
where the new database schema is not installed and configured at the same
time as the rest of the packages.

I see the need for the dependency chagnes, because a BinNMU does not touch
the Arch:all packages, thus the Arch:any packages could have higher
version, but I am yet unsure what the best way forward is here.

Right now I am experimenting with using

Depends: arch_any (>= ${source:Version}), arch_any (<< ${source:Version}.1~)

so that a new upstream version forces an upgrade of the Arch:all packages,
which would otherwise not happen or happen in the wrong order or too late
in the process. (At least I understand it that way, please correct me if I
am wrong here.)

You can see the whole process over at
https://salsa.debian.org/hartge-guest/bacula

Grüße,
Sven.