On Thu, 17 Jul 2014, Jay Berkenbilt wrote: > > so when is this transition to use libtiff-dev to happen? cmtk > > just was removed from jessie for no good reason (I have not spotted that > > severity still was "serious"), so I wondered if I should just wait a bit > > and upload updated package or start whining process to bring current > > cmtk back into jessie (since currently technically there is nothing > > wrong with it!)
> I'm sorry this is causing a problem for you. Hopefully my comments below > will help a little. It is definitely not my intention to create a > headache for anyone, but I would point out that this has been in the > works for a long time. > I'm not sure I really see the problem with just uploading a new version > to sid with a build dependency on libtiff-dev. This may work fine for > backported versions since libtiff4-dev provided libtiff-dev for a long > time (years), but if it doesn't, the backporting mechanism supports > having different build dependencies for backporting. IIRC either it is in the policy or just in a "mentality" of buildds that first listed package must be non-virtual. > Yes, it creates a > small headache for the backporter, but it's something that is pretty > routine. I don't know anything about neurodebian, but it seems to me > that it must support the ability to have different build dependencies or > other differences in config for backported packages. yeah -- there we should not have any problem, thanks for "checking" ;) > The tiff transition > has been in the works for something like two years. I believe debian was > the first major distribution to start and the last one to finish making > the switch. I don't want to keep a transitional package around, and > removing it has always been part of the plan. I'm sorry that this is > causing a hassle for you. I tried to organize this to minimize hassle > and to provide loads of time for developers to make the switch. > Let me know if I can be of any assistance in some way other than > reintroducing libtiff4-dev. doh -- blind/silly/busy? me, there is already a libtiff5-dev and what I need is actually to adjust build-depends to bdepend on it -- I took it wrong and assumed that the entire "transition" is about introducing libtiff-dev physical package... ok, so I will just go ahead and adjust build-depends to be libtiff5-dev | libtiff4-dev | libtiff-dev, and that should resolve it ;) Cheers! -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
