Package Details: znc-clientbuffer-git r37.7ae14f8-1

Git Clone URL: https://aur.archlinux.org/znc-clientbuffer-git.git (read-only, click to copy)
Package Base: znc-clientbuffer-git
Description: ZNC module for client specific buffers
Upstream URL: https://github.com/CyberShadow/znc-clientbuffer
Licenses: Apache
Submitter: arcnmx
Maintainer: arcnmx
Last Packager: arcnmx
Votes: 4
Popularity: 0.000000
First Submitted: 2016-08-11 18:08 (UTC)
Last Updated: 2018-05-18 22:39 (UTC)

Latest Comments

aphirst commented on 2018-05-22 21:14 (UTC)

Build issue is fixed upstream in znc.

https://github.com/znc/znc/commit/d71331259a981ba51e324206c68ee246b1aa26d9

aphirst commented on 2018-05-22 10:28 (UTC)

I can confirm that the issue IS upstream:

[alarm@alarm ~]$ cat /usr/bin/znc-buildmod | grep distcc '-DCMAKE_C_COMPILER=/usr/lib/distcc/bin/cc', '-DCMAKE_CXX_COMPILER=/usr/lib/distcc/bin/c++',

Editing these lines in znc-buildmod to simply point to /usr/bin/cc and /usr/bin/c++ fixes the issue. It seems that the Archlinux ARM "znc" package is being build using distcc, and that the znc developers figured it was a good idea to hardcode the build machine's compiler into the output znc-buildmod, even though there's no reason to assume that the settings will be valid.

aphirst commented on 2018-05-21 13:39 (UTC) (edited on 2018-05-21 13:39 (UTC) by aphirst)

I think the issue is upstream, as such I've reported it there.

https://github.com/CyberShadow/znc-clientbuffer/issues/3

https://github.com/znc/znc/issues/1536

aphirst commented on 2018-05-20 23:34 (UTC)

I've just started getting build problems:

https://ptpb.pw/xqcz

Cmake seems to be very confused, trying distcc, even though distcc isn't even installed, and is !'ed out in makepkg.conf. I get this when building with aurutils or via makepkg manually.

arcnmx commented on 2018-05-18 22:27 (UTC)

Is there a standard set of dependencies that should be used for znc-buildmod? A casual glance looks like it'd be python, znc, and cmake?

prg commented on 2018-05-18 14:57 (UTC)

cmake should be added as build dep

S13ntist commented on 2018-04-23 20:28 (UTC)

Git needs to be added as a make dep. Else this fails to build in a clean chroot

arcnmx commented on 2017-10-10 15:38 (UTC)

Updated to use the newer fork. If CyberShadow wants to comment here requesting that I transfer ownership I can do that (is that even a thing or do I just disown it?)

aphirst commented on 2017-10-10 06:58 (UTC)

It seems that CyberShadow's repo is now actually considered the "official" one. https://github.com/CyberShadow/znc-clientbuffer https://github.com/jpnurmi/znc-clientbuffer/issues/6#issuecomment-334988936

S13ntist commented on 2017-10-08 09:45 (UTC)

Apparently jpnurmi abandoned the project (or at least has been inactive for a long while now regarding this repo, on github and on irc) CyberShadow did a fork, which is now also the repo mentioned on the znc-wiki (https://wiki.znc.in/Clientbuffer), in which they implemented lots of new functionality and improvements. Would you mind updating the source origin? The new repo would be https://github.com/CyberShadow/znc-clientbuffer CyberShadow would also be interested to accept ownership of this package if you are so inclined, as he is also on Arch

arcnmx commented on 2017-09-06 22:11 (UTC)

Hm the wiki indicates in https://wiki.archlinux.org/index.php/PKGBUILD#arch that "any" would be incorrect. It's always been annoying how arch=() isn't scalable or really even useful... Eventually x86_64 was just added to everything and maybe many years from now arm will be too.

aphirst commented on 2017-09-06 21:51 (UTC)

Since it's possible to install this package on platforms other than just i686 and x86_64, indeed on any for which znc is available, could this possibly be reflected in the PKGBUILD? I have to keep adding armv7h to mine, or keep changing to 'any', which is starting to get frustrating, and I struggle to think I'm the only one.