| 1 |
Hi, |
| 2 |
|
| 3 |
> On Mar 15, 2021, at 7:28 AM, Thomas Bracht Laumann Jespersen <t@×××××××.xyz> wrote: |
| 4 |
> |
| 5 |
>>> # Göktürk Yüksek <gokturk@g.o> (2021-03-14) |
| 6 |
>>> # Dead upstream. No revdeps. |
| 7 |
>>> # Removal in 60 days to allow people extra time |
| 8 |
>>> # for transitioning out. Bug #776262. |
| 9 |
>>> app-admin/lastpass-cli |
| 10 |
>>> |
| 11 |
>>> |
| 12 |
>> |
| 13 |
>> |
| 14 |
>> Due to recent changes to Lastpass, I switched to Bitwarden. It may be |
| 15 |
>> worth mentioning somewhere that you can export from Lastpass and import |
| 16 |
>> to Bitwarden and not lose any passwords. My switching took about 5 |
| 17 |
>> minutes, some of which is downloading the sources and add-ons. |
| 18 |
> |
| 19 |
> I actually use lastpass-cli, because my company use LastPass. Is there an |
| 20 |
> alternative, or can we keep this somehow? |
| 21 |
> |
| 22 |
|
| 23 |
Unfortunately we cannot keep it unless the upstream shows a sign of life. You can still use the web interface etc. of LastPass. There is also a community fork of lastpass-cli[0], which I would be opposed to maintaining because it’s not sanctioned by LogMeIn. |
| 24 |
|
| 25 |
Given the fact that upstream is practically dead now, you can just not delete the package. Most likely it’ll eventually break if one of its dependencies’ ABI changes, which would require a rebuild. If you really want to keep the package, you can save it in a local overlay and use it for as long as it lasts. Just remember that if LogMeIn decides to change the web API at some point, lastpass-cli is effectively a program with undefined behavior. |
| 26 |
|
| 27 |
> All the best, |
| 28 |
> — Thomas |
| 29 |
> |
| 30 |
> |
| 31 |
|
| 32 |
[0] https://github.com/lastpass-cli-fork/lastpass-cli <https://github.com/lastpass-cli-fork/lastpass-cli> |
Archives