Re: Package involved in transitions
Thank you.
If I'm guessing right that this is part of the time_t 32-to-64-bit
transition, I suppose there's going to be an ABI change but no API
change. If that is correct then I don't expect any breakage.
If there's also an API change I'm not aware of it, please point me to
where I can learn about it.
Gerardo
Il giorno gio 15 feb 2024 alle ore 13:04 Gianfranco Costamagna
<locutusofborg@debian.org> ha scritto:
>
> Hello,
>
> yes RT will trigger the rebuilds.
>
> In case of FTBFS (e.g. if you build using experimental packages), you will need to react and fix it.
> If the FTBFS is fixed with a retro-compatible patch, you can even upload the fix right now, or wait for the transition to start and upload then.
>
> G.
>
>
>
>
>
>
> Il mercoledì 14 febbraio 2024 alle ore 22:41:45 CET, Gerardo Ballabio <gerardo.ballabio@gmail.com> ha scritto:
>
>
>
>
>
> Hello,
> I read from the package tracker that my package galois will soon be
> part of the auto-glibmm2.4, auto-gtkmm3.0 and auto-glib2.0 transitions
> (https://tracker.debian.org/pkg/galois).
> I'm trying to figure out whether I need to take any actions.
> Following the links, I seem to understand that library package names
> will change and get a t64 suffix, for example, libglibmm-2.4-1v5 will
> become libglibmm-2.4-1t64.
> So far as I can see, those library names aren't specified anywhere in
> the source package: debian/control lists libgtkmm-3.0-dev in its
> Build-Depends and the binary packages are pulled in during the package
> build.
> So my understanding is that I don't need to do anything: a simple
> binNMU will suffice and that will be scheduled at the proper time by
> the Release Team.
> Is that correct?
>
> Thank you
> Gerardo
>
Reply to: