[ubuntu/plucky-proposed] azure-proxy-agent 1.0.30-0ubuntu4~25.04.2 (Accepted)

Fri Sep 12 12:35:53 UTC 2025

azure-proxy-agent (1.0.30-0ubuntu4~25.04.2) plucky; urgency=medium

  * d/p/fix-systemd-deps-cycle.patch: fix dependency cycle in the unit file.
    Use DefaultDependencies=no to remove the dependency on basic.target
    (LP: #2122345)

azure-proxy-agent (1.0.30-0ubuntu4~25.04.1) plucky; urgency=medium

  * Backport to plucky (LP: #2115197), with the following changes:
    - d/proxy-agent.json, d/t/smoke: re-enable logging to file. The
      modification of the logging behaviour was not preceded by adequate prior
      communication to potential users of the agent regarding the intended
      change and its consequences.

azure-proxy-agent (1.0.30-0ubuntu4) questing; urgency=medium

  * d/t/control: add the isolation-machine restriction to the smoke test, as
    the agent needs a VM.

azure-proxy-agent (1.0.30-0ubuntu3) questing; urgency=medium

  * d/p/cargo-vendor-workspace-ignore.patch: add missing DEP-3 header
  * d/p/systemd-service-description.patch: add missing DEP-3 header

azure-proxy-agent (1.0.30-0ubuntu2) questing; urgency=medium

  * Fix failing autopkgtest.
    Since we stopped logging to a file, the smoke test was failing. We can
    simply read the logs from the journal instead to fix the issue.
    (LP: #2112315)
  * Remove deprecated lintian-overrides.
    The systemd service file was modified upstream and some of the
    lintian-overrides are not needed anymore.
  * Include Cargo.lock in the binary package.
    The MIR doc for rust packages states that the Cargo.lock should be
    included in the package.

azure-proxy-agent (1.0.30-0ubuntu1) questing; urgency=medium

  * New upstream version 1.0.30.
  * d/rules: use the main Cargo.toml to create the vendor directory.
  * debian: create README.source and add script to update crates.
    This is necessary in case a vulnerability is found in one of the
    dependencies and the package needs to be rebuilt.
  * d/p/systemd-service-description.patch: refresh patch.
    The patch was not applying correctly on top of the new upstream version.
  * d/copyright: remove superfuous patterns as some dependencies were removed.
  * Update XS-Vendored-Sources-Rust and verify it during build.
    This also included adding a patch to exclude the rust-vendor directory
    from the workspace.
  * d/control: change Section to admin.
    The Section is not about the programing language used to write the
    software but should reflect what the package is used for.
  * Generate new vendor directory
  * Disable logging to file. The new version of the agent supports disabling
    logging to files by configuring the log directory to an empty string. This
    way, only the logs are only going to the journal and don't fill the disk.

Date: Mon, 08 Sep 2025 10:26:17 +0200
Changed-By: Gauthier Jolly <gauthier.jolly at canonical.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Signed-By: Utkarsh Gupta <utkarsh.gupta at canonical.com>
https://launchpad.net/ubuntu/+source/azure-proxy-agent/1.0.30-0ubuntu4~25.04.2
-------------- next part --------------
Format: 1.8
Date: Mon, 08 Sep 2025 10:26:17 +0200
Source: azure-proxy-agent
Built-For-Profiles: noudeb
Architecture: source
Version: 1.0.30-0ubuntu4~25.04.2
Distribution: plucky
Urgency: medium
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Gauthier Jolly <gauthier.jolly at canonical.com>
Launchpad-Bugs-Fixed: 2112315 2115197 2122345
Changes:
 azure-proxy-agent (1.0.30-0ubuntu4~25.04.2) plucky; urgency=medium
 .
   * d/p/fix-systemd-deps-cycle.patch: fix dependency cycle in the unit file.
     Use DefaultDependencies=no to remove the dependency on basic.target
     (LP: #2122345)
 .
 azure-proxy-agent (1.0.30-0ubuntu4~25.04.1) plucky; urgency=medium
 .
   * Backport to plucky (LP: #2115197), with the following changes:
     - d/proxy-agent.json, d/t/smoke: re-enable logging to file. The
       modification of the logging behaviour was not preceded by adequate prior
       communication to potential users of the agent regarding the intended
       change and its consequences.
 .
 azure-proxy-agent (1.0.30-0ubuntu4) questing; urgency=medium
 .
   * d/t/control: add the isolation-machine restriction to the smoke test, as
     the agent needs a VM.
 .
 azure-proxy-agent (1.0.30-0ubuntu3) questing; urgency=medium
 .
   * d/p/cargo-vendor-workspace-ignore.patch: add missing DEP-3 header
   * d/p/systemd-service-description.patch: add missing DEP-3 header
 .
 azure-proxy-agent (1.0.30-0ubuntu2) questing; urgency=medium
 .
   * Fix failing autopkgtest.
     Since we stopped logging to a file, the smoke test was failing. We can
     simply read the logs from the journal instead to fix the issue.
     (LP: #2112315)
   * Remove deprecated lintian-overrides.
     The systemd service file was modified upstream and some of the
     lintian-overrides are not needed anymore.
   * Include Cargo.lock in the binary package.
     The MIR doc for rust packages states that the Cargo.lock should be
     included in the package.
 .
 azure-proxy-agent (1.0.30-0ubuntu1) questing; urgency=medium
 .
   * New upstream version 1.0.30.
   * d/rules: use the main Cargo.toml to create the vendor directory.
   * debian: create README.source and add script to update crates.
     This is necessary in case a vulnerability is found in one of the
     dependencies and the package needs to be rebuilt.
   * d/p/systemd-service-description.patch: refresh patch.
     The patch was not applying correctly on top of the new upstream version.
   * d/copyright: remove superfuous patterns as some dependencies were removed.
   * Update XS-Vendored-Sources-Rust and verify it during build.
     This also included adding a patch to exclude the rust-vendor directory
     from the workspace.
   * d/control: change Section to admin.
     The Section is not about the programing language used to write the
     software but should reflect what the package is used for.
   * Generate new vendor directory
   * Disable logging to file. The new version of the agent supports disabling
     logging to files by configuring the log directory to an empty string. This
     way, only the logs are only going to the journal and don't fill the disk.
Checksums-Sha1:
 83fa9b764899b018a534d51ba0b321a17b50aa7b 4517 azure-proxy-agent_1.0.30-0ubuntu4~25.04.2.dsc
 64baf30fc039b47bc25412f7771710545a2bf5e0 5284652 azure-proxy-agent_1.0.30.orig-rust-vendor.tar.xz
 e45aa23a913d7f801df4f6cb4528712f5441e419 338285 azure-proxy-agent_1.0.30.orig.tar.gz
 9ee99ed0535f13caf70c82400dd3a88a5c0d8d58 14584 azure-proxy-agent_1.0.30-0ubuntu4~25.04.2.debian.tar.xz
 557c6c1ab3af1c8fe34f374f7656426a5f83eb64 7634 azure-proxy-agent_1.0.30-0ubuntu4~25.04.2_source.buildinfo
Checksums-Sha256:
 5097d12e8dd242d2882f0bca4d1e7672142403f9d69d04b937f39328fc81e016 4517 azure-proxy-agent_1.0.30-0ubuntu4~25.04.2.dsc
 00310de9aa42d89a28878633e0f2eb3c27e122aac9f494a474b710a1468d5fee 5284652 azure-proxy-agent_1.0.30.orig-rust-vendor.tar.xz
 5c376e08ea5e037a5221c22dd9e2ce3d8dd0ef140ac65a30bed2f048380ec887 338285 azure-proxy-agent_1.0.30.orig.tar.gz
 62b8d47de3587981be87f977f1659c1d6f2429f470a283882792ece84a6dd895 14584 azure-proxy-agent_1.0.30-0ubuntu4~25.04.2.debian.tar.xz
 2306d2cf0fa406add15fd4bfac3cf6af549d8ebb1b00feb1fa1b4ed752bc6ac1 7634 azure-proxy-agent_1.0.30-0ubuntu4~25.04.2_source.buildinfo
Files:
 4d009d22b2d338b58aaa0f670851d60b 4517 admin optional azure-proxy-agent_1.0.30-0ubuntu4~25.04.2.dsc
 bd5ef5964986a515a30f32712f4ffd29 5284652 admin optional azure-proxy-agent_1.0.30.orig-rust-vendor.tar.xz
 cfc2a898833130be867eceaebd094bb9 338285 admin optional azure-proxy-agent_1.0.30.orig.tar.gz
 55196fb05cdc2a9fc107f9785b0986a3 14584 admin optional azure-proxy-agent_1.0.30-0ubuntu4~25.04.2.debian.tar.xz
 790e6158d9f3284762f6fa58183578b4 7634 admin optional azure-proxy-agent_1.0.30-0ubuntu4~25.04.2_source.buildinfo
Original-Maintainer: Gauthier Jolly <gauthier.jolly at canonical.com>