Re: libdatetime-timezone-perl need to wait?
On 20/06/2020 22:39, Ola Lundqvist wrote:
> Thanks for the clarification. Would that really be an issue if they
> got it? They will get the newer version later.
> But I get the point. In any case it is not an urgent thing so we can
> wait. I'll add notes about this too.
Yes, it can be a problem, for example if the package has dependencies on
libraries that have bumped the SONAME on the newer Debian release. That can
cause apt to not be able to do a dist-upgrade.
In this particular case, that's unlikely to be a problem, but we follow the more
general rule of not having a higher version in an older release. Besides, this
update is not urgent (the changes are scheduled to happen in October or so) so
there's no rush and we can wait for the point release. If the changes were
urgent, the stretch update would have happened quickly through a SUA rather than
waiting for a point release.
> // Ola
> On Sat, 20 Jun 2020 at 00:53, Sylvain Beucler <firstname.lastname@example.org> wrote:
>> On 19/06/2020 23:29, Ola Lundqvist wrote:
>>> In the DLA needed entry for libdatetime-timezone-perl you have
>>> mentioned that we need to wait for oldstable update via point release
>>> before the LTS update is made. When looking at the version numbers for
>>> the different releases I fail to see the necessity of that.
>>> Have I missed something? Or is this note false?
>> From what I understand, we want to provide 2020a-0+deb8u1 but if we do
>> before 2019c-0+deb9u1 -> 2020a-0+deb9u1 is done on stretch, people who
>> upgrade jessie -> stretch will retain the jessie package (while they
>> should use the stretch package).
>> See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958995