This upstream project is archived:

https://github.com/henrybear327/Proton-API-Bridge

As such, I don't think we should ship this in forky.  Let's figure out
how to untangle the reverse dependencies.

/Simon

jas@frallan:~/dpkg$ ssh mirror.ftp-master.debian.org dak rm -Rn golang-github-henrybear327-proton-api-bridge
Will remove the following packages from unstable:

golang-github-henrybear327-proton-api-bridge |    1.0.0-3 | source
golang-github-henrybear327-proton-api-bridge-dev |    1.0.0-3 | all

Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
------------------- Reason -------------------

----------------------------------------------

Checking reverse dependencies...
# Broken Depends:
rclone: golang-github-rclone-rclone-dev

# Broken Build-Depends:
rclone: golang-github-henrybear327-proton-api-bridge-dev

Dependency problem found.

jas@frallan:~/dpkg$

Since the consumer of this package is rclone, I noticed that modern
versions of rclone uses this package instead:

https://github.com/rclone/go-proton-api

It seems to be a fork of a fork, but seems more maintained.  Maybe we
should package that instead of the original upstream project
https://github.com/ProtonMail/go-proton-api

/Simon

Sorry, that should have been

github.com/rclone/Proton-API-Bridge

See also this related bug report:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1145074

/Simon

Simon Josefsson <simon@josefsson.org> writes: