Bug#709078: libtiff borken - cannot build anymore?
- To: firstname.lastname@example.org, email@example.com
- Subject: Bug#709078: libtiff borken - cannot build anymore?
- From: Russ Allbery <firstname.lastname@example.org>
- Date: Mon, 20 May 2013 09:41:13 -0700
- Message-id: <[🔎] email@example.com>
- Reply-to: Russ Allbery <firstname.lastname@example.org>, email@example.com
- In-reply-to: <firstname.lastname@example.org> (Adam D. Barratt's message of "Mon, 20 May 2013 17:36:37 +0100")
- References: <20130520145326.GM3253@gamma.logic.tuwien.ac.at> <20130520150819.GN3253@gamma.logic.tuwien.ac.at> <email@example.com> <20130520155906.GQ3253@gamma.logic.tuwien.ac.at> <firstname.lastname@example.org> <email@example.com>
"Adam D. Barratt" <firstname.lastname@example.org> writes:
> On 2013-05-20 17:09, Russ Allbery wrote:
>> Norbert Preining <email@example.com> writes:
>>> On Mo, 20 Mai 2013, Jay Berkenbilt wrote:
>>>>>> The build deps that I have are:
>>>>>> libgd2-xpm-dev | libgd2-noxpm-dev => libtiff5-dev
>>>>>> libgs-dev => libtiff4-dev
>>>>>> How should this work out?
>>>> The situation is that you can't have both libtiff4-dev and
>>>> on the build dependency chain of any two packages at the same time.
>>>> For now, what you have to do instead is to have the package that
>>>> requires libtiff5-dev instead build-depend on libtiff5-alt-dev. The
>> It means that ghostscript needs to be updated to do what Jay says.
> Or that gd needs to not tie its own transition to libtiff, and should go
> back to using libtiff4 until we're ready to do the tiff transition.
> Changing gs to use tiff5 just moves the problem to the next reverse
> dependency (of either gs or gd).
Oh, yes, good point -- I was thinking of libgs-dev using libtiff4-alt-dev
and missed that it hasn't yet been introduced. (Copying the ghostscript
bug so that the maintainers are aware that my advice was premature.)
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>