Hi, just a reminder that buster was released and the python2 EOL is approaching end of the year. Thanks for taking care,
Greetings, Varac Quoting Antoine Beaupré (2019-05-09 20:03:31) > On 2019-05-09 19:36:46, Varac wrote: > > Quoting Antoine Beaupré (2019-04-21 23:05:35) > >> I'm not sure I can get away with this one during the freeze, > >> unfortunately. :/ > >> > >> But as soon as buster-backports opens, this will be a distinct > >> possibility. Remind me then if I forget... > > > > Can't it be uploaded already to unstable and later migrated to > > buster-backports > > ? That would allow an installation from unstable until buster-backports is > > there. > > > > I don't want to push on this but possibly unblock it from the buster release > > process, if possible. > > I don't usually upload to unstable during the freeze, as it can block > possible fixes for problems that could be discovered. > > If I say, upload 1.18.12-1 now to unstable and a release critical bug > appears in 1.18.11-1 in buster, there's no easy way to fix it in buster > because that needs an update to unstable. I would need to *revert* the > 1.18.12-1 upload and that would mean messing around with version numbers > in a bad way. > > The proper way to upload a new version now is to send it to > experimental. > > But anyways buster-backports won't be open until after the buster > release, so it won't help you getting it there. > > BTW, the Ubuntu folks sent a patch that fixes this problem in #928177 as > well, you might want to check it out. And I do need help with the > maintenance on this package, as you might have noticed from the bug > report count... any little bit helps! :) > > A. > > -- > I'm sorry if any of you are catholic. I'm not sorry if you're > offended, I'm actually just sorry by the fact that you're catholic > - Bill Hicks
signature.asc
Description: signature
