Hello Craig, Not ignoring, just two rather long days of work, Traffic Control, an hour or a little less to the yard, then an hour to the work site, and the same returning, with more than 12 hours between arriving at the yard and getting back for two days. Thankfully shorter today. On 2/17/19, Craig Sanders via luv-main <luv-main@luv.asn.au> wrote:
On Sun, Feb 17, 2019 at 05:59:54PM +1100, Mark Trickett wrote:
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?
it's probably easiest to just rebuild these pacakages as "4.0.10-4" without the "~backport"
it probably won't even make any difference anyway - by the time you dist-upgrade to the next debian release, libtiff* will probably have been upgraded a few times. if not, you could always manually force the official debian packages to be installed with "apt-get --reinstall install libtiff5 libtiffxx5 ...".
Aha, another piece of using apt-get. It is brilliant, but also a very steep learning curve. It would be very good to have a good cheat sheet in a printable form. I am now considering two installs on the computer, one stable, the other sid, and dual booting to get the scanning. As there is one normal user, I should be able to set up a shared home partition and the one user in each install sharing the one home directory structure. That way, I still have a usable system for most things, but can get at the stuff in sid at need. Regards, Mark Trickett
craig
-- craig sanders <cas@taz.net.au> _______________________________________________ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main