Re: Proposing patch for packages, affected by transition
> >Recently, I took over gdbm package and got new version into
> >experimental. Now I work on fixing reverse dependencies FTBFS.
> >
> >Given I have patch for one of rdependency (camldbm, namely). What now?
> >Should I ask maintainer to apply it and make upload into experimental?
> >Or something else?
>
> open bugs against the affected packages, severity important, tags patch
> and mention that it will become RC when the transition starts.
Okay. But if they apply this patch right now, package will not build
aganist unstable. Is it okay?
> Do you have a wider view about how many packages are affected by
> rebuild issues?
Yes.
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
> the -2 version should make probably all of them build correctly if
> I'm not wrong.
No. -2 version separated modern and compat interface into different
binaries packages, so some packages at least need add build-depends:
libgdbm-compat-dev.
--
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Keep-In-CC: yes
X-Web-Site: sinsekvu.github.io
Reply to: