Hey, On Thu, 16 Jul 2026 at 05:28, Christopher Obbard <[email protected]> wrote: > > Hey Utkarsh, > > On Thu, 16 Jul 2026 at 05:19, Christopher Obbard <[email protected]> wrote: > > > > Hey Utkarsh, > > > > On Wed, 15 Jul 2026 at 01:31, Utkarsh Gupta <[email protected]> > > wrote: > > > > > > 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. > > > > I built the source packages and uploaded them to debusine with: > > > > gbp buildpackage > > --git-builder='dpkg-buildpackage -S -us -uc -d' > > --git-ignore-branch > > > > dput > > -O debusine_workflow=upload-to-bullseye-security > > -O debusine_workflow_data.upload_include_source=true > > debusine.debian.net > > *_source.changes
Just for completeness, seems like debusine_workflow_data.upload_include_source isn't needed. Apologies for the noise again ;-) > > > > The jobs are at: > > https://debusine.debian.net/debian/developers/work-request/924461/ > > https://debusine.debian.net/debian/developers/work-request/924484/ > > > > The artifacts in the "package upload" jobs don't seem to include the > > original tarball, despite having the upload_include_source flag set ? > > :-( > > The artifacts link is > > https://debusine.debian.net/debian/developers/artifact/4150734/ > > Ah, I solved it by adding -sa to the dpkg-buildpackage command. Sorry > for the noise! > > My new jobs are: > https://debusine.debian.net/debian/developers/work-request/925240/ > https://debusine.debian.net/debian/developers/work-request/924953/ > > They seem to include the original tarball in the artifacts to upload now.. > > I'll refrain from uploading until I hear back. > > > > > Can you check my process is OK before I sign and upload, please? > > According to the workflow template both should upload to security-master. > > > > If I can't use debusine for this, I will have another go manually next > > week... > > Cheers! > > Chris
