Arch Linux User Repository

If the build fails, that's normally due to a new version available as an rpm, so I just have to update the version and the checksums. This of course is only noticed if someone (re-)builds the package.

There's no need for you to post modified PKGBUILDs. Just flag the package out-of-date or drop me an e-mail and I'll take care of it.

@joe, I needed to manually install 'qt5-webkit' in order to make it work on Gnome. You may want to add this package as a required dependency. Thanks!

@kgizdov, thanks for your feedback. The package does not really provide qtkeychain and ocsync. They are just used by this package in a wrapper script, because older versions are required. That's also why I think the linker configuration should not be updated here. I also don't really like this, but it's the easiest solution that prevents conflicts. The cernbox client (this package) and the CERNBox service are different things, so this is not "a self-referencing way", as the packaging standards put it.

EDIT: The package needs to indicate that it provides qtkeychain=0.4 and ocsync=1.7.2. Running namcap on this gives some problems: kgizdov@arch ~ namcap /var/cache/pacman/pkg/cernbox-1.7.2_3.1-4-x86_64.pkg.tar.xz cernbox W: Description should not contain the package name. cernbox W: Referenced library 'libqtkeychain.so.0' is an uninstalled dependency cernbox W: Referenced library 'libocsync.so.0' is an uninstalled dependency Please adhere to the AUR rules and fix the description of the package. Also, please put a file `cernbox.conf` in /etc/ld.so.conf.d/ to update the linker configuration. It can simply be done by adding the following to the PKGBUILD: # use a file that pacman can track and update environment install -d ${pkgdir}/etc/ld.so.conf.d echo '/usr/lib/cernbox' > ${pkgdir}/etc/ld.so.conf.d/cernbox.conf

@knowak, I cannot confirm your problem, the client is still working for me.

Does anyone have a problem with "Could not authenticate to server: rejected Basic challenge" during syncing? At some point this client stopped working for me - it worked several months ago on a different arch installation (I am still authorized to use cernbox from the browser)

I have included the working qtkeychain version from the cernbox repo into this package now. It's used by a wrapper script to not interfere with other versions and cause conflicts. Hope this works for you.

I too have the libqtchain problem. It would be wonderful if this could be fixed. Thanks and Cheers, Raja.

Thanks, I used "downgrade" on qtkeychain-qt4, to reinstall qtkeychain-qt4-0.5-2-x86_64.pkg.tar.xz (remote). change the dependencies in the cernbox PKGBUILD to qtkeychain-qt4. works fine. thanks

Right, qtkeychain does no longer contain the qt4 version... There is an AUR package 'qtkeychain-qt4' (version 0.6.1), but unfortunately this does not work because this cernbox build is linked against an older version. I know that it worked with version 0.5. The cernbox repository I'm extracting this from contains a verision 0.4 rpm[1], which also works. I'm not sure what is best to do now. I don't know under which circumstances the repositories provided by CERN IT are updated, but I can ask if they can trigger this. I could include qtkeychain into this package, but that might cause conflicts for some people. If you need a solution for now, manually using the libs from [1] works. [1]http://cernbox-resources.web.cern.ch/cernbox-resources/Linux/repo/openSUSE_Factory/x86_64/libqtkeychain0-0.4-8.7.x86_64.rpm

I got a strange error with libqtkeychain. I have removed cernbox and qtkeychain, and reinstalled both, now cernbox cannot load libqtkeychain: cernbox: error while loading shared libraries: libqtkeychain.so.0: cannot open shared object file: No such file or directory is there any obvious solution ? thanks,