duplicity-team team mailing list archive

[Kenneth Loafman <kenneth@xxxxxxxxxxx>]

Here's the checklist I use.  Launchpad handles the build process to make
.deb's.  What's a *snap* package?

The part you'll need to do is highlighted.  After that, no idea what
happens on LP for package build.

Release Duplicity

   - fix bugs / enhance
   - prep release to bzr
   -
      - merge in po-updates-0.x
      - run tox to check
      - commit all
      - gen release PPA
   -
      - go to
      https://code.launchpad.net/~duplicity-team/+recipe/duplicity-releases
      - edit the "Recipe contents" at the bottom to update the version
      number
      - click "Request build(s)" right above that box and start some
      builds.
      - gen daily PPA
   -
      - go to
      https://code.launchpad.net/~duplicity-team/+recipe/duplicity-daily
      - edit the "Recipe contents" at the bottom to update the version
      number
      - click "Request build(s)" right above that box and start some builds
      - *make and sign the release *
   -
      - *dist/makedist 0.x.yy *
      - *$ gpg --use-agent -b duplicity-0.x.yy.tar.gz *
      - release tar/sig to Savannah
   - release tar/sig to Launchpad
   - move to Releases
   - update web pages
   - release to CVS
   - update Announcements
   - change from fix committed to released
   - send email to talk and announce


On Thu, Oct 4, 2018 at 3:47 AM Aaron <lists@xxxxxxxxxxxxxxxxxx> wrote:

> Hello Kenneth,
>
> I have started trying to build a snap package for duplicity.
>
> Are the steps you follow to package a release written down anywhere? If
> not, would you mind please briefly summarising by reply? It would be
> helpful to use that as a starting point for the snap.
>
> Kind regards,
>
> Aaron
>