Package Details: mqtt-explorer 0.3.5-13

Git Clone URL: https://aur.archlinux.org/mqtt-explorer.git (read-only, click to copy)
Package Base: mqtt-explorer
Description: A comprehensive and easy-to-use MQTT Client
Upstream URL: https://mqtt-explorer.com/
Licenses: CCPL:by-nd
Conflicts: mqtt-explorer-beta
Submitter: dave12311
Maintainer: zhimsel (aarnold)
Last Packager: zhimsel
Votes: 11
Popularity: 0.000005
First Submitted: 2020-02-23 16:05 (UTC)
Last Updated: 2023-03-17 14:55 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

mqs commented on 2025-01-11 22:09 (UTC)

I just now tried to switch from the -appimage package to this one (wanted to build this from source myself) and saw that this increased the size of the installed files from ~70MB (the -appimage package) to 1GB (this package). Is there a reason for this?

Maaike commented on 2024-07-31 09:45 (UTC)

Bit late response but that helped, thank you!

zhimsel commented on 2024-06-08 15:57 (UTC)

@Maaike it looks like this is a bug in the Linux kernel. Supposedly, it should be fixed in 6.9.3:

In the meantime, you can work around this by setting the UV_USE_IO_URING=0 environment variable when building the package (i.e. UV_USE_IO_URING=0 makepkg -s).

Maaike commented on 2024-06-04 16:21 (UTC)

Installing does not work:

[3/4] Linking dependencies...
warning " > electron-telemetry@1.0.0" has incorrect peer dependency "ts-node@^7.0.1".
warning " > tslint-react-recommended@1.0.15" has incorrect peer dependency "tslint-react@^3.0.0".
warning " > tslint-react-recommended@1.0.15" has unmet peer dependency "tslint-eslint-rules@^4.0.0".
[4/4] Building fresh packages...
⠁ 
⠁ 
error /home/maaike/.cache/yay/mqtt-explorer/src/MQTT-Explorer-0.3.5/node_modules/electron-chromedriver: Command failed.
Exit code: 126
Command: node ./download-chromedriver.js
Arguments: 
Directory: /home/maaike/.cache/yay/mqtt-explorer/src/MQTT-Explorer-0.3.5/node_modules/electron-chromedriver
Output:


yarn run v1.22.22
$ tsc && cd app && yarn run build && cd ..
/usr/bin/env: 'node': Text file busy
error Command failed with exit code 126.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: mqtt-explorer-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
mqtt-explorer - exit status 4

sshine commented on 2023-06-06 11:39 (UTC) (edited on 2023-06-06 11:58 (UTC) by sshine)

Upon makepkg -si,

/bin/sh: line 1: tsc: command not found

It seems that we want to add typescript as a dependency.

aarnold commented on 2023-05-22 15:02 (UTC) (edited on 2023-05-22 15:05 (UTC) by aarnold)

@turiok you might try to contact the packager:

pacman -Si bitwarden-cli
Repository      : community
Name            : bitwarden-cli
Version         : 2023.4.0-1
Description     : The command line vault
Architecture    : x86_64
URL             : https://github.com/bitwarden/cli
Licenses        : GPL3
Groups          : None
Provides        : None
Depends On      : nodejs-lts-gallium
Optional Deps   : None
Conflicts With  : None
Replaces        : None
Download Size   : 4.37 MiB
Installed Size  : 29.13 MiB
Packager        : Alexander Epaneshnikov <alex19ep@archlinux.org>
Build Date      : Wed Apr 26 16:21:05 2023
Validated By    : MD5 Sum  SHA-256 Sum  Signature

turiok commented on 2023-05-22 10:18 (UTC)

I have the same problem with bitwarden. I think the best solution is to change bitwarden. Because they use nodejs only for the build. And to solution that, I found this article https://wiki.archlinux.org/title/Node.js_package_guidelines#Using_nvm But I don't know how to ask this because bitwarden is an official package

jhf2442 commented on 2023-04-04 21:46 (UTC)

@zhimsel yes, the problem is that ndejs-lts-gallium provides a version too old for this package, thus the conflict. Else I would have tried modifying the PKGBUILD, but from your comment of 2023-03-15, I deduced that it's not worth it

Nevertheless good hint with the appimage - will go for the mqtt-explorer-appimage package to prevent the version collision. Many thanks !

zhimsel commented on 2023-04-04 13:56 (UTC) (edited on 2023-04-04 13:57 (UTC) by zhimsel)

Actually, this could be solved (potentially) by the nodejs-lts-gallium package providing nodejs via its PKGBUILD. Then it would satisfy the dependency.

EDIT: It does: https://github.com/archlinux/svntogit-community/blob/ec35ab863ae7f597a1225d331fe4767de21a607a/trunk/PKGBUILD#L15. Just not the right version (for us).

zhimsel commented on 2023-04-04 13:56 (UTC)

@jhf2442 sorry for the delayed response. I'm not really sure what the best practice is for this. Within any package management system, there's always the chance for conflicting dependencies; Pacman is not immune to this (especially in the AUR). Given that the build requires nodejs>=17, I'm not sure really how to address this.

Maybe you could create a package out of the AppImage (which are released in the Github repo). Or you could fork this package to work with a lower version of nodejs.

1 2 3 4 5 Next › Last »