← Back to issue list

remote parts publishing procedure unclear

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1617968
Type
issue
State
closed
Author
~paelzer
Labels
—
Created
Updated
Closed

Current evaluation

User error, not a bug: the wiki parts entry must use the origin's part name. Maintainer ~joetalbott corrected the entry to waf-project; the reporter confirmed it worked. Missing parser error spun off to LP #1618092.

Resolution: closed not a bug

Reason: ~joetalbott explained that part names in the wiki must match the 'parts' section names of the origin's snapcraft.yaml, and updated the entry from 'wafdemo' to 'waf-project'; ~paelzer confirmed "that did it". The genuine parser gap was tracked separately in LP #1618092, so no code fix landed for this bug.

Evaluated by: mr-cal-bot

No scores available.

Issue body

Hi, this might entirely be on my lack of experience, but I'm trying to progress with PR 716 and fail to do so for now. Due to IRC being not responsive atm I thought I file a bug until one has time to take a look at it. Background: in PR 716 elopio asked if I could move the waf demo bits out of the snapcraft tree into a remote part. While doing so I ran into issues that the remote part is not able to be discovered. I pushed https://github.com/cpaelzer/waf-snapcraft as a simple start (not sure if I want to change it later to actually build the part there, but that is not the issue for now). I listed the part at https://wiki.ubuntu.com/snapcraft/parts as "wafdemo". I get errors when building a snap with "after [wafdemo]" but I also get the same with "snapcraft update && snapcraft search waf" and similar. This blocks me from debugging an finalizing elpios request for PR 716. Is there any particular update cycle associated that I have to wait for? I haven't found any extra doc about this so far. I'm assuming less than a bug than looking for some guidance, but we will see. Kind regards, Christian

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed not a bug User error, not a bug: the wiki parts entry must use the origin's part name. Maintainer ~joetalbott corrected the entry to waf-project; the reporter confirmed it worked. Missing parser error spun off to LP #1618092.
stealth/space-bunny-alpha — closed not a bug Remote part discovery worked after the wiki entry was corrected from “wafdemo” to the origin part name “waf-project”; the absent parser error was spun off to LP #1618092.
stealth/space-bunny-alpha — closed stale Remote-part publishing guidance was never provided; the report was closed without comments or a fix.
qwen/qwen3.6-35b-a3b — — Closed without resolution or comments. Author requested guidance on remote part publishing but received no response. Issue appears abandoned.
qwen/qwen3.6-35b-a3b — — Closed without resolution after one day with zero comments. The request for guidance on the remote parts publishing procedure was abandoned, with no fix, documentation update, or maintainer response provided.
qwen/qwen3.6-35b-a3b — — Closed without resolution. The author reported unclear remote part publishing procedures blocking PR 716, but received no maintainer response. The request was abandoned.
qwen3.6-35b-a3b-mtp-q6 — — Closed without resolution. The report detailed unclear remote parts publishing procedures in snapcraft, blocking a related PR. With zero comments and no maintainer response, the request was abandoned.

Update history

Date Change
created

Related work

  • Caused By: snapcraft (launchpad)#1618092 (confidence 92%)

    Spin-off bug filed by ~joetalbott for the parser not reporting an unknown remote part name; that is where the real defect was tracked.

  • Related To: snapcraft#716 (confidence 80%)

    The snapcraft PR whose remote-part move motivated this report; it was later merged in commit 9cf5b2492 as the Waf plugin.

Related issues

No related issues found above the similarity threshold.