Trying to build the output of "expand-extensions" fails because of the pebble part
Metadata
Current evaluation
Fixed by PR #763 (commit d77ac5ac): expand-extensions output now accepts the injected default Pebble part when it matches Rockcraft's own configuration.
Resolution: closed resolved
Reason: PR #763, commit d77ac5ac, changed validation to allow an explicitly defined Pebble part when it exactly matches Rockcraft's injected default, making expanded rockcraft.yaml files buildable.
Evaluated by: mr-cal-bot
No scores available.
Issue body
### Bug Description
The output of `expand-extensions` should always be buildable on its own; However, in rockcraft it fails because of the implicit pebble part that is injected when creating the project.
### To Reproduce
```
rockcraft init
rockcraft expand-extensions > new-rockcraft.yaml
mv new-rockcraft.yaml rockcraft.yaml
rockcraft pack
```
### Environment
Rockcraft 1.5.3 on Jammy
### rockcraft.yaml
```yaml
n/a
```
### Relevant log output
```shell
2024-11-12 10:23:35.163 Loading project file '/home/tiago/tmp/rockcraft.yaml'
2024-11-12 10:23:35.166 Cannot override the default "pebble" part
```
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha | — | closed resolved | Fixed by PR #763 (commit d77ac5ac): expand-extensions output now accepts the injected default Pebble part when it matches Rockcraft's own configuration. | |
| stealth/space-bunny-alpha | — | closed resolved | Expanded rockcraft.yaml files are now buildable: Rockcraft accepts an explicitly included Pebble part when it matches the injected default. Fixed by PR #763 (commit d77ac5ac). | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by PR #763 (d77ac5ac): expanded project files can now build with the injected Pebble part when it matches Rockcraft's default. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by PR #763 (commit d77ac5ac): expanded rockcraft.yaml files may include the injected default Pebble part. | |
| stealth/space-bunny-alpha | — | closed resolved | Fixed by merged PR canonical/rockcraft#763 (commit d77ac5ac), which accepts an expanded pebble part when it matches Rockcraft’s implicit definition. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. An internal Jira ticket (CRAFT-3667) was created to track the build failure caused by a conflicting implicit pebble part when expanding extensions. No fix or merge was implemented. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The expand-extensions build failure caused by a conflicting implicit pebble part was synced to internal ticket CRAFT-3667. No fix or merge was implemented, leaving the issue effectively abandoned. | |
| qwen/qwen3.6-35b-a3b | — | — | Closed without resolution. The expand-extensions output build failure caused by an implicit pebble part conflict remains unfixed, with no pull requests merged or patches applied. | |
| qwen3.6-35b-a3b-mtp-q6 | — | — | Closed without resolution. A Jira sync comment logged the rockcraft expand-extensions pebble part conflict internally, but no fix, merge, or workaround was provided, indicating the bug was abandoned or deferred. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
canonical/rockcraft#763
(confidence 100%)
The merged fix accepts a matching user-defined Pebble part instead of rejecting it.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #763 fix: accept a 'pebble' part if its the same as ours | rockcraft | merged | Merged in canonical/rockcraft#763 (commit d77ac5ac), accepting an existing Pebble part when identical to Rockcraft’s injected part and fixing expand-extensions builds. |