Search Criteria
Package Details: mqtt-explorer 0.3.5-13
Package Actions
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.001045 |
First Submitted: | 2020-02-23 16:05 (UTC) |
Last Updated: | 2023-03-17 14:55 (UTC) |
Dependencies (5)
- nodejs (nodejs-gitAUR, nodejs-lts-fermiumAUR, nodejs-sharedAUR, nodejs-lts-hydrogen, nodejs-lts-iron)
- git (git-gitAUR) (make)
- npm (corepackerAUR) (make)
- sed (busybox-coreutilsAUR, sed-gitAUR) (make)
- yarn (corepackerAUR, yarn-pnpm-corepackAUR, yarn-berryAUR) (make)
Latest Comments
1 2 3 4 5 Next › Last »
sshine commented on 2023-06-06 11:39 (UTC) (edited on 2023-06-06 11:58 (UTC) by sshine)
Upon
makepkg -si
,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:
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 providingnodejs
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.
aarnold commented on 2023-03-26 16:42 (UTC)
@jhf2442 I guess it's possible to adapt the build script to use different arguments/patches for different nodejs versions. But I'm not sure if this is the best solution in the context of a rolling release distribution as well within the yarn/npm/nodejs ecosystem. Maybe somebody can share his/her knowledge.
jhf2442 commented on 2023-03-26 15:59 (UTC) (edited on 2023-03-26 16:01 (UTC) by jhf2442)
Unfortunately, requiring nodejs>=17 now introduces a conflict with bitwarden-cli from community repo !
How can we solve this ?
zhimsel commented on 2023-03-17 14:55 (UTC)
@StefanK2 I updated the PKGBUILD to require v17 or higher. That should hopefully avoid anyone else having issues in the future.
StefanK2 commented on 2023-03-16 20:24 (UTC)
@aarnold yes, that was it. For some reason I had a node v14 lts version installed. I switched the package and now it builds correctly.
Thank you very much :)
1 2 3 4 5 Next › Last »