← Back to issue list

tests: add jammy packages to stage package apt cache (#494)

View original Github issue

Metadata

Project
craft-parts
Number
#512
Type
pull request
State
merged
Author
lengau
Labels
—
Created
Updated
Closed

Current evaluation

Backport of #494 merged as dcdab592 (also e4f789fc/2d270ec5 on stable branches): added Jammy deps (gcc-13-base, libgcc-s1) to the AptCache stage-package test. With #511 it fixed the CI failure in #513.

Resolution: closed resolved

Reason: The PR was merged and approved, landing as commit dcdab5926caecd1848b6c3c0db9decf8f8ed02cd (cherry-picks e4f789fc, 2d270ec5), adding a 'dependencies in jammy' block to tests/unit/packages/test_apt_cache.py. It resolves the extra-package marking seen in #495, which was closed as expected behaviour from Ubuntu's mutable archive, and combined with #511 restored the CI shown in #513.

Evaluated by: mr-cal-bot

No scores available.

Issue body

New packages are marked for installation on Jammy - see #495 Signed-off-by: Callahan Kovacs <callahan.kovacs@canonical.com> (cherry picked from commit dcdab5926caecd1848b6c3c0db9decf8f8ed02cd) - [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? ----- CI fixed in combination with #511. This is visible in the CI results from #513.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Backport of #494 merged as dcdab592 (also e4f789fc/2d270ec5 on stable branches): added Jammy deps (gcc-13-base, libgcc-s1) to the AptCache stage-package test. With #511 it fixed the CI failure in #513.
stealth/space-bunny-alpha — closed resolved Merged as dcdab5926: added Jammy packages to the stage-package AptCache test, addressing extra dependencies in #495. Combined CI passed with complementary fixes from #511 and #513.
stealth/space-bunny-alpha — closed resolved Merged craft-parts#494 as dcdab592, adding Jammy packages to stage-package apt-cache tests; cherry-picks landed via #512/#520, and #511 fixed linting.
stealth/space-bunny-alpha — closed resolved Merged as dcdab5926caec, updating the stage-package AptCache test for Jammy packages marked for installation and addressing #495; #511 fixed the remaining lint issue.
qwen/qwen3.6-35b-a3b — — PR #494 was merged to add Jammy packages to the stage package apt cache for tests. The change was cherry-picked and required linting fixes from PR #511. Approved and merged with passing CI.
qwen3.6-35b-a3b-mtp-q6 — — Merged PR #494 to add Jammy packages to the stage apt cache. CI failures were resolved by combining changes with PR #511, which fixed linting and CI config. The commit was cherry-picked and integrated.

Update history

No update history recorded yet.

Related work

  • Duplicate Of: canonical/craft-parts#494 (confidence 92%)

    This PR is a cherry-picked backport of original PR #494 (same title), merged as dcdab592.

  • Likely Fixed By: canonical/craft-parts#495 (confidence 90%)

    Issue #495 (AptCache marking extra packages on Jammy) was addressed by this test update and subsequently closed.

  • Related To: canonical/craft-parts#511 (confidence 85%)

    Maintainer noted the linting/CI issue was fixed in #511; the two together resolved the #513 CI failure.

  • Related To: canonical/craft-parts#513 (confidence 80%)

    CI run evidencing the combined fix from #512 and #511.

Related issues

Issue Project State Summary Similarity
#494 tests: add jammy packages to stage package apt cache craft-parts merged Merged #494 as commit dcdab592, updating the AptCache stage-package test for Jammy dependencies; follow-up #495 tracked archive-induced extra packages.
92%
#520 tests: add jammy packages to stage package apt cache (#494) craft-parts merged Merged PR #520 backported the Jammy AptCache test update from #494 via commit dcdab5926, accounting for extra packages marked for installation on Jammy.
92%
#495 AptCache is marking extra packages for installation on Jammy craft-parts closed Test-only Jammy breakage (extra gcc-13-base/libgcc-s1 deps) was already patched by merged PR #494 (commit dcdab592); root-cause issue closed by cmatsuoka as inherent archive dynamism, not a resolver bug.
79%