Github messages for voidlinux
 help / color / mirror / Atom feed
From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: rmapi: remove (unmaintained upstream)
Date: Thu, 09 Jan 2025 23:57:39 +0100	[thread overview]
Message-ID: <20250109225739.369392171E@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-53874@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

There's a merged pull request on the void-packages repository

rmapi: remove (unmaintained upstream)
https://github.com/void-linux/void-packages/pull/53874

Description:
This package [is no longer maintained upstream](https://github.com/juruen/rmapi/discussions/313), and I am not aware of any maintained forks (for example, [awesome-reMarkable does not list an active fork](https://github.com/reHackable/awesome-reMarkable)). Unfortunately, since this tool speaks to a proprietary cloud API which changes over time, this package is subject to bitrot, which seems to already be the case: even running `rmapi help` now fails for me, because it tries to phone home to the reMarkable servers which return various 4xx HTTP status codes. Judging from the rmapi issues board, this is just one of many showstopper issues that will now go unresolved. Verdict: IMO it's time to remove this package from our repos.

      reply	other threads:[~2025-01-09 22:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07  6:15 [PR PATCH] " klardotsh
2025-01-09 22:57 ` Johnnynator [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250109225739.369392171E@inbox.vuxu.org \
    --to=johnnynator@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).