Having now had a more thorough look through the commit history, it
appears to have been this one that I needed to pull in order to get past
the compilation error I was hitting.
https://gitlab.com/sequoia-pgp/sequoia-octopus-librnp/-/commit/b4fcbf558f8f0f07a3b753b802d15a2803a7db5b
On 23/01/2023 17:13, artist wrote:
> Package sequoia-octopus-librnp-1.4.1-4-x86_64.pkg.tar.zst is now in
> universe to be tested; it does not contain newer commits than the
> previous version.
>
> artist
>
> On a bended knee, or systemd, you will never live free
>
> On 1/23/23 14:45, Colin S wrote:
>> I build sequoia-octopus-librnp from the git source rather than using
>> the packaged version in Universe. I'm not sure what exactly in
>> 102.7.0-1 caused this recent breakage, but simply rerunning the
>> Sequoia build now failed to compile, so some crate dependency must
>> also have changed. Pulling in the latest git commits and then
>> rebuilding seems to fix things. I imagine it should be fairly
>> straightforward for the maintainer to correct the Universe package.
>>
>> On 23/01/2023 06:26, Javier wrote:
>>> Hello !
>>>
>>> The new 102.7.0-1 thunderbird in "world" breaks
>>> sequoia-octopus-librnp in "universe". Not sure if a rebuild of
>>> sequoia-octopus-librnp is required, or even worse, a new version for
>>> it is required. BTW, I don't see a new tag on [1], neither a related
>>> reported issue on [2]. For now, this requires preventing pacman to
>>> upgrade thunderbird. At any rate, on boxes trying to authenticate to
>>> enterprise O365, that's currently a must. But this is a different
>>> issue...
>>>
>>> Thanks !
>>>
>>>
>>>
>
More information about the artix-general
mailing list