Hello Craig, On 2/17/19, Craig Sanders via luv-main <luv-main@luv.asn.au> wrote:
On Sun, Feb 17, 2019 at 04:59:46PM +1100, Mark Trickett wrote:
Even with one of the backports, it produced multiple debs, and one of those depends on two others, and adding the "~backport" tag in the
it's not a "tag", it's part of the version string for the package you built.
I regard the "~backport" as a tag on the version string, a component that I call a tag, but I understand it becomes part of the version.
For most Depends: entries, the version isn't important - as long as the package is installed, the dependency will be satisfied. But some dependencies are versioned and require an exactly = or >= match to a specific version of a package.
This is the issue, I will have to remove and rebuild the tiff packages. The relevant lines are :- libtiff5 (=${binary:version}), libtiffxx5 (=$binary:version}) Is there a way to alter these to add the "~backport" item? or should I remove the "~backport" item from the version of the whole in the changelog file?
I built tiff-4.0.10, and libtiff-dev depends on libtiff5 and libtiffxx5 (version = 4.0.10-4 versus 4.0.10-4~backport). Without those all installed, dpkg-buildpackage will not build sane-backends-1.0.27.
If you've built and installed libtiffxx5 version "4.0.10-4~backport" and sane-backends or some other source package depends on "4.0.10-4", then edit the debian/control file for that package to change the dependency to version "4.0.10-4~backport".
If it were just a straight string, not a problem, but then maybe for my backport, that would suffice instead of picking the version from the binary, else look at putting the backport mention in there.
versioned dependencies have to either be an exact match for the version string (when the dep specifies "=") or greater-than-or-equal-to a specific version string (when the dep specifies ">=").
i did not expect this, but it makes sense, just the "right"' way to deal with it. Yes, it is on my system and not propagated, but doing the right way will reduce other problems later. that is why I do stick with the Debian package management.
with some packages, you might also see versioned Conflicts lines that have "=" or "<=".
craig
Again many thanks. These little hiccups are a good learning exercise, although frustrating. Regards, Mark Trickett