[PR PATCH] rmapi: remove (unmaintained upstream)

[PR PATCH] rmapi: remove (unmaintained upstream)

[klardotsh]

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

There is a new pull request by klardotsh against master on the void-packages repository

https://github.com/klardotsh/void-packages klardotsh/remove-unmaintained-rmapi
https://github.com/void-linux/void-packages/pull/53874

rmapi: remove (unmaintained upstream)
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.

A patch file from https://github.com/void-linux/void-packages/pull/53874.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-klardotsh/remove-unmaintained-rmapi-53874.patch --]
[-- Type: text/x-diff, Size: 1875 bytes --]

From 6bbbd763cd42f2e4c260fdd6a52e5ae36336c2ad Mon Sep 17 00:00:00 2001
From: Josh Klar <josh@klar.sh>
Date: Mon, 6 Jan 2025 22:09:28 -0800
Subject: [PATCH 1/2] rmapi: remove.

---
 srcpkgs/rmapi/template | 12 ------------
 1 file changed, 12 deletions(-)
 delete mode 100644 srcpkgs/rmapi/template

diff --git a/srcpkgs/rmapi/template b/srcpkgs/rmapi/template
deleted file mode 100644
index e9726d22e14cfe..00000000000000
--- a/srcpkgs/rmapi/template
+++ /dev/null
@@ -1,12 +0,0 @@
-# Template file for 'rmapi'
-pkgname=rmapi
-version=0.0.25
-revision=4
-build_style=go
-go_import_path=github.com/juruen/rmapi
-short_desc="CLI for accessing reMarkable table files through the cloud api"
-maintainer="Patrick Pichler <mail@patrickpichler.dev>"
-license="GPL-3.0-or-later"
-homepage="https://github.com/juruen/rmapi"
-distfiles="https://github.com/juruen/rmapi/archive/v${version}.tar.gz"
-checksum=f8ae984941e6e4755ee8b156f9876fa7f1cde084bca02bd83ced6afcc886bc33

From bfd202bb382603fc583de7fdf4d3b14bf311a833 Mon Sep 17 00:00:00 2001
From: Josh Klar <josh@klar.sh>
Date: Mon, 6 Jan 2025 22:11:04 -0800
Subject: [PATCH 2/2] removed-packages: add rmapi.

---
 srcpkgs/removed-packages/template | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/srcpkgs/removed-packages/template b/srcpkgs/removed-packages/template
index 78a6dabaafb4ed..3610564c907b74 100644
--- a/srcpkgs/removed-packages/template
+++ b/srcpkgs/removed-packages/template
@@ -1,6 +1,6 @@
 # Template file for 'removed-packages'
 pkgname=removed-packages
-version=0.1.20250103
+version=0.1.20250106
 revision=1
 build_style=meta
 short_desc="Uninstalls packages removed from repository"
@@ -796,6 +796,7 @@ replaces="
  rkt-stage1-coreos<=1.30.0_3
  rkt-stage1-fly<=1.30.0_3
  rkt<=1.30.0_3
+ rmapi<=0.0.25_4
  Rocket.Chat-Desktop<=3.8.7_3
  rpi-userland-devel<=20230920_1
  rundird<=0.2.0_1

Re: [PR PATCH] [Merged]: rmapi: remove (unmaintained upstream)

[Johnnynator]

[-- 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.