Hi Guilhem,

According to #805715, this package was introduced as a php-crypt-gpg
dependency, but I noticed the latest version does not use it anymore
(nor any other package in Debian). If I’m not mistaken, we shouldn’t
release Forky with this package, hence this bug report to get it removed
from testing ASAP (and not block, e.g., the upcoming php8.6 transition).

If there are no objections otherwise, I assume this package should also
be removed from Debian (unstable), but there is no hurry AFAICT, so
maybe we can wait a few months in order to let time for people to raise
their objections.

Regards,

taffit

Hi!

Yup, php-crypt-gpg upstream finally got rid of that stale dependency
https://github.com/pear/Crypt_GPG/issues/41

Totally fine by me, and sorry for forgetting to file this bug in the
first place!

I wonder why php-crypt-gpg is currently marked for autoremoval from
testing on Sep 19 though, since the versions found in testing and
unstable do not depend on php-console-commandline hence shouldn't be
affected by #1143834 (and 1.9.0-1 even migrated to testing before you
filed this bug).  But either way there is plenty of time before the
release to find out the reason why and try to keep php-crypt-gpg in
forky :-)

Hi Guilhem,

On 8/15/26 03:01, Guilhem Moulin wrote:
[…]

When I looked this morning, I assumed it was because the dependency was
dropped in 2.0.0, expected to migrate tomorrow. Then I just looked
closer, and noticed that php-console-commandline is still part of the
build-dependencies. Feel free to lower the priority of this bug report
until a php-crypt-gpg version without php-console-commandline as a
build-dependency is uploaded ;).

Cheers,

taffit

Oh!  Indeed, sorry for the noise and stupid question.  I blame the lack
of morning coffee ;-)

No need to wait, I just uploaded php-crypt-gpg=2.0.0-2 without the
obsolete B-D.  It should migrate into testing long before the autoremove
kicks in.  Thanks again!