Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
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
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
|
DetailsThis 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
Sunday, 29 December 2013, 13:01 GMT
Reason for closing: Not a bug
You could argue that the mono version should get its own package, but I think that's bordering on useless splitting.