Package Details: mpd-discord-rpc 1.7.2-2

Git Clone URL: https://aur.archlinux.org/mpd-discord-rpc.git (read-only, click to copy)
Package Base: mpd-discord-rpc
Description: Displays metadata of currently playing song from MPD in Discord using Rich Presence
Upstream URL: https://github.com/JakeStanger/mpd-discord-rpc
Keywords: discord mpd rpc rust
Licenses: MIT
Submitter: JakeStanger
Maintainer: JakeStanger (xiota)
Last Packager: xiota
Votes: 3
Popularity: 0.072449
First Submitted: 2020-02-15 14:03 (UTC)
Last Updated: 2024-03-16 00:54 (UTC)

Dependencies (3)

Required by (0)

Sources (1)

Latest Comments

1 2 3 Next › Last »

xiota commented on 2024-03-16 00:48 (UTC)

@JakeStanger pkgbase/pkgname mismatch is now corrected.

JakeStanger commented on 2024-03-15 23:53 (UTC) (edited on 2024-03-15 23:53 (UTC) by JakeStanger)

@xiota That's done, appreciate it :)

xiota commented on 2024-03-14 23:43 (UTC)

@JakeStanger Please add me as comaintainer. I will fix the pkgbase issue, and a few others (eg, missing url).

JakeStanger commented on 2024-02-07 22:03 (UTC)

@kusoneko thanks for the detailed write-up. The issue is that somehow I've ended up in a situation where that -git repo is already taken because the package and pkgbase don't line up:

https://aur.archlinux.org/packages/mpd-discord-rpc-git https://aur.archlinux.org/pkgbase/mpd-discord-rpc

There might be an easy way out of it, but at least your steps & things I've tried in the past lead to a deadlock situation where I can't move the package. If you've any clue, let me know, otherwise I'll eventually try and get hold of the maintainers.

kusoneko commented on 2024-02-04 09:45 (UTC)

@JakeStanger: Hi,

This is a bit of a weird issue, but the package currently doesn't follow the AUR VCS packaging guidelines, which causes the issues Rojikku mentioned previously about their AUR helper not installing the package properly. I've outlined below a few steps to fix it:

  1. git clone ssh://aur@aur.archlinux.org/mpd-discord-rpc-git.git
  2. move PKGBUILD from this repo to the newly cloned repo
  3. regenerate the .SRCINFO file in the new repo
  4. commit and push
  5. come back to https://aur.archlinux.org/packages/mpd-discord-rpc, Submit request, select Merge, type in "mpd-discord-rpc-git" in the small box, and explain roughly that you accidentally put the VCS version of the package in the non-git repository.
  6. wait for the request to be accepted (and thus completed)
  7. pull and make sure you still have the correct PKGBUILD version as well as .SRCINFO file in the new repo, if not, just remodify the PKGBUILD to fix it and regenerate the .SRCINFO before committing that and pushing again, then you shouldn't have to touch the new repo again for a long time, as -git repos tend to be fine without maintenance for a long time.

Then if you wish you can reclaim this aur repo to host stable releases, you can do so with the following steps:

  1. git clone ssh://aur@aur.archlinux.org/mpd-discord-rpc.git
  2. check if there's anything in there, which might still contain the current contents of the repo
  3. make the PKGBUILD with pkgname=mpd-discord-rpc, pkgver=1.7.1, source=('https://github.com/JakeStanger/mpd-discord-rpc/archive/refs/tags/v$pkgver.tar.gz')
  4. remove the pkgver() function (you'll need to manually, each time a new release tag is made, update the pkgver variable, the checksum and regenerate the .SRCINFO)
  5. remove the md5sums line and replace it with a checksum that's more secure such as sha256 or above. You'll also want to put the correct checksum in the array instead of skipping it.
  6. generate the .SRCINFO file
  7. commit and push

then you'll have 2 AUR packages, mpd-discord-rpc pointing to the latest release tarball and mpd-discord-rpc-git pointing to the actual git repo so the latest commits are also built. Both will also successfully work with all AUR helpers too, which is generally a good thing, as despite AUR helpers being officially unsupported, they're generally used by basically everyone instead of manually running makepkg on every AUR package used.

Hopefully this works. I tried just sending a merge request first so you wouldn't have to follow all these steps, and I could put the instructions for what to do when the request got accepted in there, however, it appears making a request to merge into an AUR repo that doesn't exist doesn't work, and I don't wish to 'rob' you of the maintainership by creating the -git repo myself and then creating a merge request, so instead I'm leaving you this comment with short instructions on fixing the situation.

JakeStanger commented on 2024-01-11 22:51 (UTC)

That's fixed, apologies for the delay

Fuxino commented on 2024-01-11 22:49 (UTC)

Building in a clean chroot fails because git is missing in makedepends.

dr460nf1r3 commented on 2023-07-29 12:37 (UTC)

Please add git to makedepends, its needed.

Rojikku commented on 2023-06-16 20:13 (UTC)

Most likely would be under submitting a request.

JakeStanger commented on 2023-06-16 20:07 (UTC)

Hm you might be right. It works with yay alright at least, so there might be an argument to be made that it's a bug (or at least a quirk) of aurto.

Annoyingly there doesn't seem to be any easy way of changing the remote URL. Not sure if that's something worth contacting the mailing list about?