Yaroslav Halchenko <y...@debian.org> 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. 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. 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. -- Jay Berkenbilt <q...@debian.org> -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
