Bug#1061079: RFS pidgin-skype
Hello,
>It is really random, for upstream modification.
>
>But it looks I could have to do something for auto-glib2.0
><https://release.debian.org/transitions/html/auto-glib2.0.html> transition.
>Which I don't really understand yet.
Just don't do any action should be fine.
There is a time_t -> time64_t transition ongoing (not yet, but will start soon TM)
this should happen for armel/armhf only,
https://lists.debian.org/debian-release/2024/01/msg00033.html
>I plan to make a backport for Bookworm. Do you think I should:
>- Backport this version even if VCS fields are not up to date?
>- Make a new version with update VCS fields and backport it as soon as
>it is in testing?
up to you!
>- Wait again for the auto-glib2.0
><https://release.debian.org/transitions/html/auto-glib2.0.html>
>transition. to make all needed modifications, create a version with also
>updated VCS fields and see what will happen for the backport?
This won't affect the package, it should be a no change rebuild done semi automatically
by Release Team, and only for 32 bit architectures excluded i386.
So, it is really up to you.
G.
Reply to: