Package Details: lbry-desktop-bin 0.53.9-1

Git Clone URL: (read-only, click to copy)
Package Base: lbry-desktop-bin
Description: Desktop app for the lbry-network ( - a decentralized, user-controlled content marketplace and YouTube alternative
Upstream URL:
Licenses: MIT
Conflicts: lbry, lbry-desktop, lbry-desktop-git, lbrynet, lbrynet-bin
Provides: lbry, lbry-desktop, lbrynet
Submitter: RubenKelevra
Maintainer: RubenKelevra
Last Packager: RubenKelevra
Votes: 61
Popularity: 0.181936
First Submitted: 2022-06-23 15:31 (UTC)
Last Updated: 2023-02-14 22:54 (UTC)

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

muflone commented on 2022-12-09 15:20 (UTC)


Please refrain to upload the package lbry-app-bin again. you know that package has no reasons to exist anymore, so please don't create it again. The package lbry-app-bin was created multiple times and it was always deleted as it's duplicate of lbry-desktop-bin

Please don't waste other people time, thank you

Edu4rdSHL commented on 2022-12-09 09:12 (UTC)

TomZander, I suggest you to stop creating duplicated packages with other names, again had to fill another deletion request for lbry-app-bin. If people want to update the package they can do that locally, that is not a reason to create duplicated packages and causing trouble to users.

TomZander commented on 2022-11-16 15:56 (UTC)

As the owner is repeatedly not updating the package (again a week overdue now), I'd like to suggest people use the actually well updated package by git cloning;

RubenKelevra commented on 2022-10-25 06:54 (UTC)

@muflone thanks - my thoughts as well.


muflone commented on 2022-10-24 20:28 (UTC)

I think everything has gone too far already, please stop here

RubenKelevra commented on 2022-10-24 17:41 (UTC)

@skrewball obviously I'm doing this in my free time as well. Just because something is not paid doesn't mean it's not work.

Regarding "forced":

  • I did not force anything, I just made requests to the administrators of the AUR system to have the package renamed.
  • As the requests went through the AUR-system, the package maintainer(s) got an mail as well. There was no response to these mails, neither to me personally nor to the package mailing list until the decision was made, in both cases.
  • To the then followed mails on the mailing list I responded that my intention was, to have the package renamed to be named like the project and the other two packages. I just fixed some packaging issues on the way, while creating the package under the new name. I've also asked if I should disown the package now, so that they could take over again – There was never a response to this.
  • Instead of responding to the question I got insulted via personal mails.
  • Following this I wrote the pinned commend here, and withdrew the offer with it.

skrewball commented on 2022-10-24 17:19 (UTC)

I would hardly call this "work", most of us are doing this in our free time.

Also, I watched it happen from the very beginning so your explanation is not needed, and it was definitely forced.

You have a nice day as well :)

RubenKelevra commented on 2022-10-24 14:53 (UTC) (edited on 2022-10-24 16:51 (UTC) by RubenKelevra)

Hey @skrewball, if you like to work on weekends you're free to do that. I like to not work on weekends.

Anyway, I have already created the update, I just wanted to ship it with pgp signature verification, and noticed in the process that the signature they provide is not supported by makepkg - so I created a bug report for that:

<strike>So this is holding back this update right now.</strike> Edit: Released it without it. Will push a null release as soon as the signature is available.

I also reported that the way the lbry pgp key gets shared is suboptimal and the download link for the signature itself is broken:

And fixed that:

PS: The circumstances were explained by me above and calling this forcefully is a misrepresentation of what happened.

Have a nice day :)

skrewball commented on 2022-10-24 13:14 (UTC)

At least @TomZander was timely and prompt with the updates before this package was forcefully taken from them.

TomZander commented on 2022-09-21 09:41 (UTC)

You seem to be unaware, but it is not possible to import the old commits.

If you ever need this again, I'll explain. Its not very hard as AUR is based on git. Keeping history and changing HEAD is not hard. All it takes is one new commit on that old history.

Either way, you have been shown the damage you have caused, that you chose to debate the points while the outcome is based on facts is showing again the problem here.