FS#37687 - [quassel-client] unable to connect to a separate quassel core

Attached to Project: Community Packages
Opened by Damian Nowak (Nowaker) - Friday, 08 November 2013, 01:06 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 29 December 2013, 13:01 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Vesa Kaihlavirta (vegai)
Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

This package is actually quassel-mono, not quassel-client. It can't connect to a separate quassel-core because it already contains one. http://bugs.quassel-irc.org/projects/1/wiki

Please rename this package to quassel-mono, and provide a new package quassel-client which is able to connect to a remote quassel-core.

Additional info:
* package version 0.9.1
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Sunday, 29 December 2013, 13:01 GMT
Reason for closing:  Not a bug
Comment by Damian Nowak (Nowaker) - Saturday, 09 November 2013, 17:27 GMT
Wiki article cache: http://goo.gl/nuYgKD
Comment by Martin Sandsmark (sandsmark) - Sunday, 22 December 2013, 23:35 GMT
No, the "quasselclient" program in the quassel-client package is the right one.

You could argue that the mono version should get its own package, but I think that's bordering on useless splitting.
Comment by Damian Nowak (Nowaker) - Monday, 23 December 2013, 00:00 GMT
I don't know how I came to a conslusion that quassel-client I installed from [community] was quassel mono version. I even found the old file in /var/cache/pacman, installed it - and it's the real quassel client. So forget what I'm saying, everything is okay.

Loading...