Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Jun 2021 21:15:14 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 256877] security/sequoia and security/py-sequoia update 1.3.0 (patch included)
Message-ID:  <bug-256877-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256877

            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@FreeBSD.org
          Reporter: phryk-ports@wzff.de

Created attachment 226095
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D226095&action=
=3Dedit
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 bo=
th
ports in one go. No warnings raised by `portlint` and `make index` runs thr=
ough
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 `SONA=
ME`
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 th=
is
led to issues finding the libs that I couldn't resolve.

Both ports now support the `test` target and the test suites run successful=
ly
on the amd64 jail I use for testing purposes =E2=80=93 tho for sequoia you =
first have
to install it; otherwise it will fail to find the libs =E2=80=93 I assume t=
his 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 do=
zen
different ports and maybe keep `sequoia=C2=B4 as a metaport with `OPTION`s =
for the
different crates. `sqop` was already moved into its own repo upstream and i=
sn'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. ^_^;

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-256877-7788>