Sorry, yes – I should have chosen the rc versions differently. The workaraund is pacman -S quassel-core-small
or pacman -U quassel-core-small-0.14.0-1-x86_64.pkg.tar.zst
.
Search Criteria
Package Details: quassel-core-small 0.14.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/quassel-core-small.git (read-only, click to copy) |
---|---|
Package Base: | quassel-core-small |
Description: | Next-generation distributed IRC client - core only, minimal dependencies |
Upstream URL: | https://quassel-irc.org/ |
Licenses: | GPL |
Conflicts: | quassel-core |
Provides: | quassel-core |
Submitter: | buzo |
Maintainer: | buzo |
Last Packager: | buzo |
Votes: | 18 |
Popularity: | 0.000000 |
First Submitted: | 2018-12-20 16:45 (UTC) |
Last Updated: | 2022-01-18 17:57 (UTC) |
Dependencies (9)
- qca (qca-qt5-gitAUR, qca-qt5)
- qt5-base-headlessAUR
- qt5-script (qt5-script-gitAUR)
- boost (boost-gitAUR) (make)
- cmake (cmake-gitAUR) (make)
- extra-cmake-modules (extra-cmake-modules-gitAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
- qt5-tools (make)
- postgresql (postgresql-12AUR, postgresql15-docsAUR, postgresql15AUR, postgresql17-docsAUR, postgresql17AUR, postgresql13AUR, postgresql-gitAUR) (optional) – PostgreSQL database support
Required by (1)
- quassel-core-openrc (requires quassel-core)
Sources (5)
buzo commented on 2022-01-20 08:52 (UTC) (edited on 2022-01-20 08:53 (UTC) by buzo)
xombiemp commented on 2022-01-19 03:03 (UTC)
I'm getting: quassel-core-small: local (0.14.0.rc2-1) is newer than AUR (0.14.0-1)
Looks like an issue with the way the version is being parsed and compared. Can this be fixed somehow, or is there a work around?
buzo commented on 2021-04-10 17:24 (UTC) (edited on 2021-04-10 22:48 (UTC) by buzo)
The update to 0.14-rc1 finally fixes the build.
buzo commented on 2020-04-11 10:36 (UTC)
This package does not build since Arch switched to qt 5.14.0, see upsteam bug #1544. They have fixed this on Github, but won't release a new version soon apparently. As a workaround, I have made the AUR package quassel-core-small-git, which seems to work fine.
xombiemp commented on 2019-09-11 15:45 (UTC)
@buzo Clean building qt5-base-headless and quassel-core-small after full system update fixed the issue. Thanks!
buzo commented on 2019-09-11 08:13 (UTC)
xombiemp: What is the output of pacman -Qs qt5
? New qt5 packages have been moved from testing to extra today, so maybe you need to rebuild qt5-base-headless and quassel-core-small.
xombiemp commented on 2019-09-11 03:04 (UTC) (edited on 2019-09-11 03:05 (UTC) by xombiemp)
After the latest update Quassel won't start for me. I'm seeing:
Sep 10 19:46:49 arch-nas systemd[1]: Started Quassel Core.
Sep 10 19:46:49 arch-nas quasselcore[8898]: 2019-09-10 19:46:49 [Info ] SQLite storage backend is ready. Schema version: 31
Sep 10 19:46:49 arch-nas quasselcore[8898]: 2019-09-10 19:46:49 [Info ] Database authenticator is ready.
Sep 10 19:46:49 arch-nas quasselcore[8898]: 2019-09-10 19:46:49 [Info ] Listening for GUI clients on IPv6 :: port 4242 using protocol version 10
Sep 10 19:46:49 arch-nas quasselcore[8898]: 2019-09-10 19:46:49 [Info ] Listening for GUI clients on IPv4 0.0.0.0 port 4242 using protocol version 10
Sep 10 19:46:49 arch-nas quasselcore[8898]: 2019-09-10 19:46:49 [Info ] Restoring previous core state...
Sep 10 19:46:49 arch-nas systemd[1]: quassel.service: Main process exited, code=killed, status=6/ABRT
Sep 10 19:46:49 arch-nas systemd[1]: quassel.service: Failed with result 'signal'.
It fails after Restoring previous core state... Anyone seen this before?
buzo commented on 2019-04-15 22:03 (UTC) (edited on 2019-04-15 22:04 (UTC) by buzo)
The library /usr/lib/libicudata.so.63 got a version bump to *.64, so any package which needs it won't work any more and needs to be rebuilt against the new version.
The owner of qt5-base-headless could maybe bump pkgrel to force the rebuild, but that's all.
xombiemp commented on 2019-04-15 18:49 (UTC)
@buzo Thanks, that worked. What do you mean icu has been updated in an incompatible way? Should we suggest a change for that package?
Pinned Comments