Gadget snap Recipe Creation Error

Bug #2011747 reported by Talha Can Havadar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Repo has snap/snapcraft.yml and gadget.yml in root folder. I tried to create a snap recipe with default options.

Here is the Error ID: OOPS-33b62023b1749175e9e0c54dfaa90e34

Tags: oops ui
Revision history for this message
Jürgen Gmach (jugmac00) wrote :

The error is about:

```
lp.snappy.interfaces.snap.SnapPrivacyMismatch: Snap recipe contains private information and cannot be public.
```

Does that make sense to you?

And when I have a look at the source code, one of the two conditions which return `False` will apply to your situation:

```
    def isValidInformationType(
        self, information_type, owner, branch=None, git_ref=None
    ):
        private = information_type not in PUBLIC_INFORMATION_TYPES
        if private:
            # If appropriately enabled via feature flag.
            if not getFeatureFlag(SNAP_PRIVATE_FEATURE_FLAG):
                raise SnapPrivateFeatureDisabled
            return True

        # Public snaps with private sources are not allowed.
        source = branch or git_ref
        if source is not None and source.private:
            return False

        # Public snaps owned by private teams are not allowed.
        if owner is not None and owner.private:
            return False

        return True
```

Revision history for this message
Jürgen Gmach (jugmac00) wrote :

It would be probably a good idea to present a user friendly error message.

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Indeed, setting a consistent project & information-type, resulting in creating a snap recipe.

Revision history for this message
Jürgen Gmach (jugmac00) wrote :

The op has a working solution.

Let's keep this issue open for presenting a user friendly message.

Changed in launchpad:
status: New → Triaged
importance: Undecided → Low
tags: added: oops ui
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.