Backports branch was my original one, I just basically copied it to bpo branch so they were identical. When I fixed the newline issuse that was mentioned, I force pushed it to bpo. So that's why you don't see the commit but it still exists on the other branch.
I can fix whatever, and also go ahead and use the branch scheme Carlos mentioned. I did get some notifications that the package is already moving along so not sure if we'll be able to without a revision.
Hi!
On Mon, Dec 30, 2024 at 10:24:44PM -0500, Boyuan Yang wrote:
> Hi,
>
> 在 12/30/2024 9:05 PM, Blake 写道:
> >
> > Holidays are busy, but I think I have everything done. Branch for the backport
> >
> > I'm not sure which, if any, of the build artifacts y'all need so I've attached
> > a tarball that just has everything.
>
> Your new changelog entry is missing an empty line at
> but alas, that is an easy fix. I am uploading a version with the empty line
> added. Please correct it in your git repo afterwards.
That commit is in backport branch but not on bpo12-0.15.4 one that Blake
sent. Blake, is there a reason for the two of them?
Also, would be nice to include Closes: #1030127 in the changelog if
there is still time. Otherwise you can send a mail to the BTS informing
that it was closed by 0.15.4~bpo12+1.
> Thanks,
> Boyuan Yang
Thanks Boyuan!
Cheers,
Charles