Hi Christopher, On Wed, Jul 15, 2026 at 3:22 AM Christopher Obbard <[email protected]> wrote: > > > Once that's in place, we can prepare the security updates for the > > > older releases, complete the paperwork, and release everything > > > together. > > > > Do you mean we need to wait for my flask upload to appear in the > > trixie-updates repo ? > > I got the acceptance email: flask_3.1.1-1+deb13u1_source.changes > ACCEPTED into proposed-updates
Super! > > The changes are here; ready to go: > > - https://salsa.debian.org/python-team/packages/flask/-/tree/debian/bookworm > > - https://salsa.debian.org/python-team/packages/flask/-/tree/debian/bullseye > > > > Let me know what I need to do next. > > PS: I probably won't be able to get around to actioning this until next week. No worries. Whenever you're back, upload your work to security-master; the changelog should be targeting bookworm-security and bullseye-security, respectively. And also, please build your package with -sa. In practice, the workflow should look like: $ dpkg-buildpackage -S -nc -d -sa # review debdiff $ dput security-master <path_to_source>.changes Let me know if you have any questions or concerns. - u
