> >Okay. But if they apply this patch right now, package will not build > >aganist unstable. Is it okay? > just mention that in the bug report, this will allow me/you to NMU when the > transition starts
Okay. > > FAIL camldbm_1.0-2.dsc -- patch ready > > FAIL courier_0.73.1-1.6.dsc > > FAIL freeradius_2.2.8+dfsg-0.1.dsc > > FAIL ifmail_2.14tx8.10-22.dsc > > FAIL nis_3.17-34.dsc > > FAIL ntop_5.0.1+dfsg1-2.1.dsc > > FAIL ocsigenserver_2.4.0-1.dsc > > FAIL perdition_2.1-2.dsc > > FAIL python3-stdlib-extensions_3.4.2-1.dsc > > FAIL qsf_1.2.7-1.dsc > > FAIL ruby2.1_2.1.5-2+deb8u2.dsc > > FAIL ruby2.3_2.3.1-5.dsc > > FAIL sortmail_2.4-2.dsc > > > >No. -2 version separated modern and compat interface into different > >binaries packages, so some packages at least need add build-depends: > > >libgdbm-compat-dev. > > if adding an additional build dependency works, I'm ok with a bug filing > (maybe send a mail to -devel, because this sounds like an MBF) > > BTW since there are >10 packages to patch, what about make the new library > depend explictly > on the old one? I would better not. calmdbm patch is not such trivial -- it was more serious. I will do it one-by-one. -- Accept: text/plain, text/x-diff Accept-Language: eo,en,ru X-Keep-In-CC: yes X-Web-Site: sinsekvu.github.io