Package: git-lfs
Version: 3.0.2-1
Severity: important
Tags: lfs upstream
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Maintainer,
* What led up to the situation ?
using git lfs to put large files on a github repository.
* What exactly did you do (or not do) that was effective (or
ineffective) ?
"git push" was stuck asking forever the passphrase of my ssh key (even if
I wrote it correcty).
A workaround is to remove the passphrase (using "ssh-keygen -p"), but it is not
an acceptable solution.
It seems like a problem of closed or badly redirected stdin file descriptor.
- -- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages git-lfs depends on:
ii git 1:2.34.1-1
ii libc6 2.33-1
git-lfs recommends no packages.
git-lfs suggests no packages.
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQHRBAEBCgA7FiEE0cUD1MSUGdbeqKS5SKyGZH3qIPEFAmHUUH4dHGplYW5qYWNx
dWVzYnJ1Y2tlckBnbWFpbC5jb20ACgkQSKyGZH3qIPFeEwv/W3gSsuHlJkef5H9X
n3BSx6c6UOSaTOiByPOIBiFkO08drZknUzsJhv9rTQ7k2MAJDAlMJ9dh+0kycZPn
JyblMVhSVTA1yg0qQZmLoVVjYI/a0OoacYIXy0d+PiShlrHzUS25lvTIWCnDvWsD
q3509qBl93yR4Cgnpy8iIccOXkuOp8s6jMbFdm13Jtg2CPDZHwiAjsLOq1baqGfS
+nOUxkru82KewQv90ssAqOrcfDYYxYFZdImkou3UAFcAJ67nMPe+IbXWrtle6Gpl
eMhx48QNkO7kDSNZx4IGWCgA+9ntK1YgTDrTuQkpYxxZY6Wqr2AZ8lD8j7qYvrow
52pRYsA10nkUfMTSsWoA65TBYvfrLIddcfVFNVOoJ7JIQJfYTCZQqBRBUkBkCJpn
cCNJ5bq+1wZvVrsdhnVUpleN+hz0KoNYJAhIEFQ5cuOKYJUMlrDESTNUv4HCIvI1
7KPmJkx5l5sTU9lhAd2GOuo+TNUzkJf6AaK0Kf7K53w36lTE
=msS8
-----END PGP SIGNATURE-----
