[Bug 256877] security/sequoia and security/py-sequoia update 1.3.0 (patch included)

From: <bugzilla-noreply_at_freebsd.org>
Date: Mon, 28 Jun 2021 21:15:14 +0000
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256877

            Bug ID: 256877
           Summary: security/sequoia and security/py-sequoia update 1.3.0
                    (patch included)
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs_at_FreeBSD.org
          Reporter: phryk-ports_at_wzff.de

Created attachment 226095
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226095&action=edit
updates security/sequoia and security/py-sequoia

Sequoia-OpenPGP recently released version `1.3.0`.

Since both sequoia-openpgp (as well as sequoia-sq and sequoia-sqv) and the
python bindings live in the same git repo, I'm handing in the updates to both
ports in one go. No warnings raised by `portlint` and `make index` runs through
without issue.

Some notes:

I added `SONAME`s for the `ffi` and `openpgp-ffi` libs. This isn't possible for
`ffi-macros` as it doesn't count as "cdylib". The version supplied in `SONAME`
might technically be wrong since they use the `1.3.0` version of the
`sequoia-openpgp` crate and not the `0.22.0` of their own crates because this
led to issues finding the libs that I couldn't resolve.

Both ports now support the `test` target and the test suites run successfully
on the amd64 jail I use for testing purposes – tho for sequoia you first have
to install it; otherwise it will fail to find the libs – I assume this is is
caused by setting `SONAME`, as the error message specifically mentions
`.so.1.3.0` but I haven't been able to properly triage the issue.

`py-sequoia` now has its own version as noted in its `setup.py` (`0.1.0`),
hence the version *decreased*.

Also, for future releases, I'll probably break this up into about half a dozen
different ports and maybe keep `sequoia´ as a metaport with `OPTION`s for the
different crates. `sqop` was already moved into its own repo upstream and isn't
part of the sequoia port anymore. I'll add it back as its own port in the
future.

Would be super nice if we could get this into the next quarterlies, but I
totally understand if the remaining time is a bit short for that. ^_^;

-- 
You are receiving this mail because:
You are the assignee for the bug.
Received on Mon Jun 28 2021 - 21:15:14 UTC

Original text of this message