Re: Where did Bacula 1.38.11-7+b1 come from?
On Thu, Feb 22, 2007 at 07:57:07PM +0100, Andreas Metzler <ametzler@downhill.at.eu.org> wrote:
> Mike Hommey <mh@glandium.org> wrote:
> > On Thu, Feb 22, 2007 at 07:31:46PM +0100, Frans Pop <elendil@planet.nl> wrote:
> >> On Thursday 22 February 2007 19:26, Andreas Metzler wrote:
> >> > 1. Add a Build-dependency on dpkg-dev (>=1.13.19)
> >> > 2. For all in bacula-foo packages that are arch:all replace any
> >> > occurence of
> >> > Depends: bacula-foo (= ${Source-Version})
> >> > with Depends: bacula-foo (= ${source:Version})
> >> > 3. (optional, but clarify things) For all in bacula-foo packages that
> >> > are arch:any replace any occurence of
> >> > Depends: bacula-foo (= ${Binary-Version})
>
> >> Something is missing here... I suspect:
> >> | with Depends: bacula-foo (= ${binary:Version})
>
> > That would be
> > bacula-foo (>= ${source:Version}), bacula-foo (<< ${source:Version}.1~)
>
> I do not get that, what is the benefit compared to (= ${binary:Version})
arch: all packages are *not* rebuilt, so their dependency won't ever get
updated, which means the dependency will be stuck to the original
${binary:Version}, which is... ${source:Version}.
Mike
Reply to: