Snap pocket configuration doesn't override PPA pocket configuration

Bug #1646145 reported by Michael Terry
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Invalid
High
Michael Terry
Launchpad itself
Invalid
Undecided
Unassigned

Bug Description

It appears that snap recipes use the -proposed pockets when building [1]. That probably doesn't make sense?

Or at least, if it does sometimes make sense, could it be possible to allow disabling that in a recipe?

[1] https://launchpadlibrarian.net/295465880/buildlog_snap_ubuntu_xenial_arm64_unity8-session-silo_BUILDING.txt.gz

Michael Terry (mterry)
Changed in canonical-devices-system-image:
milestone: none → p1
Revision history for this message
William Grant (wgrant) wrote :

The pocket is configurable when you create the snap in LP or request a build of it.

Changed in launchpad:
status: New → Invalid
Revision history for this message
Colin Watson (cjwatson) wrote :

I think it might be a bit more complicated than that. In the case at hand, the use of the proposed pocket is being inherited from the PPA that the snap is building against. I haven't yet had a chance to look to see if this is reasonable.

Revision history for this message
Michael Terry (mterry) wrote :

Yeah in our case, the recipe says it is using the Updates pocket:
https://launchpad.net/~unity-team/+snap/unity8-session-silo

But snap builds using the recipe end up with proposed pocket.

Changed in launchpad:
status: Invalid → New
Revision history for this message
William Grant (wgrant) wrote :

Having the snap override the PPA's pocket configuration is error-prone. For example, if the PPA had packages built against a new version of a library that was only in -proposed, but then the snap used only -updates, the snap might fail to install the package from the PPA. It's not at all clear that allowing that override to happen is sensible.

summary: - Consider not using -proposed for snap recipes
+ Snap pocket configuration doesn't override PPA pocket configuration
Changed in launchpad:
status: New → Incomplete
Revision history for this message
Michael Terry (mterry) wrote :

Where do you see a PPA using the -proposed pocket? From what I can see, the recipe is (A) using the -updates pocket and (B) using the stable-phone-overlay PPA. That PPA in turn seems to be set to use only the -updates pocket.

So everyone in the chain is configured to just use -updates. But our snap builds are still looking at -proposed.

Changed in launchpad:
status: Incomplete → New
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

any updates?

Changed in canonical-devices-system-image:
importance: Undecided → High
milestone: p1 → p2
status: New → Confirmed
Changed in canonical-devices-system-image:
assignee: nobody → Michael Terry (mterry)
Revision history for this message
William Grant (wgrant) wrote :

The most recent builds are against silo PPAs, which are configured for -proposed (eg. https://launchpad.net/api/devel/~ci-train-ppa-service/+archive/ubuntu/2129/dependencies).

Changed in launchpad:
status: New → Incomplete
Revision history for this message
Michael Terry (mterry) wrote :

Great point, William. I overlooked the silo PPA config.

That is indeed set to use -proposed. And after I edited it to use -updates only, I notice that building a snap resets the config to -proposed again. Note the "Correcting PPA dependencies!" line in the snap build log:

https://bileto.ubuntu.com/log/2129/snap/40/

I'll talk to robru about what's can change here.

Revision history for this message
Michael Terry (mterry) wrote :

OK, configuring bileto to allow a silo to merely use -updates is bug 1646596 and not ready yet.

So... We could either stop using a silo to build snaps (we're close to that being possible, once the ubuntu-app-launch MPs land). Or source copy those to a separate PPA and build from that, avoiding bileto.

Or wait for the feature to be added.

In the meantime, this does not seem to be a Launchpad issue after all. Thanks for walking me through it, wgrant! I'll close this bug in favor of the bileto one.

Changed in launchpad:
status: Incomplete → Invalid
Changed in canonical-devices-system-image:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.