Re: RFM: transition of flint
Hi Julien,
On 09/04/2015 02:08 PM, Julien Puydt wrote:
> Hi,
>
> I need some mentoring for my first library transition. I have a hard
> time getting exactly what the page on transitions explains
> (https://wiki.debian.org/Teams/ReleaseTeam/Transitions).
>
> The source package is flint, and produced libflint-2.4.5 ; now it
> produces libflint-2.5.2 -- both can coexist.
>
> There is a single reverse dependency, which is singular -- and I checked
> singular is only a recompilation away from using the newer version of
> flint.
>
> Tobias (Hansen) pushed the new version in experimental and it cleared
> off NEW, so the ball is rolling.
>
> The second step is "Ensure it builds on all architectures in testing,
> where it built previously." -- it doesn't say exactly how I'm supposed
> to check that.
>
In the PTA on the right hand side there is a link "buildd: exp":
https://buildd.debian.org/status/package.php?p=flint&suite=experimental
It failed to build on i386 (and also other 32 bit architectures on
ports) so I guess that should be resolved first.
> The third step is about getting a transition tracker. I have it
> (https://release.debian.org/transitions/html/auto-flint.html) ! But the
> page says that if it's not useful I should generate an applicable one. I
> have no clue how one generates an "applicable one" even though the one I
> have looks quite useless:
> - it says there are bad depends -- libflint-2.4.5 isn't bad, as it can
> coexist with libflint-2.5.2 ;
> - it doesn't list singular as needed anything, even though it should ;
> - it says it can't smooth update because libflint-2.4.5 being neither in
> libs nor oldlibs -- what does that even mean ?
>
It looks pretty fine to me.
- libflint-2.4.5 is "bad" because it will be replaced by this
transition. We want to have it gone from unstable. Otherwise you would
have renamed the source package.
- singular is in the list, no problem.
- I'm not sure what smooth-update means (maybe a function of some tool),
but you should set "Section: libs" in debian/control for the lib
package. Since you just forgot to do that, the information that
smooth-update is not possible might be wrong.
Best,
Tobias
Reply to: