@ahasenack, As you know, I am temporarily covering for @gjolly. In keeping with our conversation in the Ubuntu SRU room on Matrix, I created merge proposals for Questing and Plucky.
* Questing: https://code.launchpad.net/~danpdraper/ubuntu/+source/azure-proxy-agent/+git/azure-proxy-agent/+merge/489911 * Plucky: https://code.launchpad.net/~danpdraper/ubuntu/+source/azure-proxy-agent/+git/azure-proxy-agent/+merge/489921 The Questing merge proposal supersedes https://code.launchpad.net/~gjolly/ubuntu/+source/azure-proxy- agent/+git/azure-proxy-agent/+merge/489505 . The Plucky merge proposal supersedes https://code.launchpad.net/~gjolly/ubuntu/+source/azure- proxy-agent/+git/azure-proxy-agent/+merge/488282 . The Questing merge proposal addresses your request for the addition of DEP-3 headers to the patches. The Plucky merge proposal addresses the DEP-3 header request and reverts the change to the agent's logging behaviour. Note that the reversion of the logging behaviour change _only_ applies to Plucky; I decided to leave the logging behaviour change intact for Questing, Noble, and Jammy, as it mirrors an upstream change. As the package has yet to be uploaded to the Noble and Jammy branches of the archive, I stopped after uploading my local Noble and Jammy branches to Launchpad. * Noble: https://code.launchpad.net/~danpdraper/ubuntu/+source/azure-proxy-agent/+git/azure-proxy-agent/+ref/noble-1.0.30-0ubuntu3 * https://code.launchpad.net/~danpdraper/ubuntu/+source/azure-proxy-agent/+git/azure-proxy-agent/+ref/jammy-1.0.30-0ubuntu3 I also want to call attention to the versions in the changelogs. You will note that the changes by version are identical across Questing, Plucky, Noble, and Jammy for versions 1.0.30-0ubuntu1, 1.0.30-0ubuntu2, and 1.0.30-0ubuntu3. For Plucky, instead of bundling the logging behaviour change reversion into version 1.0.30-0ubuntu3, I moved the reversion into a new version (1.0.30-0ubuntu4). Should we wish, at some point, to create a new Ubuntu-specific version of 1.0.30 on any of the Questing, Noble, and Jammy branches, we will likely want to skip version 1.0.30-0ubuntu4, given that we will not want to revert the logging behaviour change. Does that make sense to you? Is there a different approach that you would rather I take? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2115197 Title: [SRU] azure-proxy-agent 1.0.30-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/azure-proxy-agent/+bug/2115197/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
