Package Details: retroshare 0.6.1-1

Git Clone URL: https://aur.archlinux.org/retroshare.git (read-only)
Package Base: retroshare
Description: Serverless encrypted instant messenger with filesharing, chatgroups, e-mail.
Upstream URL: http://retroshare.sourceforge.net/
Licenses: GPL, LGPL
Conflicts: retroshare
Provides: retroshare
Submitter: None
Maintainer: sehraf
Last Packager: sehraf
Votes: 139
Popularity: 2.802332
First Submitted: 2007-10-03 20:41
Last Updated: 2016-09-05 11:14

Latest Comments

sehraf commented on 2016-09-04 16:16

I've already updated the PKGBUILD and only need to push it but i currently don't have access to the computer.
Expect the update on monday afternoon CET.

sehraf commented on 2016-07-04 14:27

@herzmeister ask upstream or use the -git version. This is not the place to ask for such update...

herzmeister commented on 2016-07-04 11:39

an update would be nice, because apparently a recent commit in the last days might fix a connection issue that i've been having for the last few months

aereaux commented on 2016-06-18 18:57

When building the package with this new patch, I get the following error:

==> Starting prepare()...
../aca88308eae16ab67627593c0df2fce7beb02e89.patch:115: trailing whitespace.
const float Node::MASS_FACTOR = 10 ;
../aca88308eae16ab67627593c0df2fce7beb02e89.patch:116: trailing whitespace.
const float Node::FRICTION_FACTOR = 10.8f ;
../aca88308eae16ab67627593c0df2fce7beb02e89.patch:117: trailing whitespace.
const float Node::REPULSION_FACTOR = 4;
../aca88308eae16ab67627593c0df2fce7beb02e89.patch:118: trailing whitespace.
const float Node::NODE_DISTANCE = 130.0f ;
../aca88308eae16ab67627593c0df2fce7beb02e89.patch:119: trailing whitespace.

error: patch failed: retroshare-gui/src/gui/elastic/node.cpp:87
error: retroshare-gui/src/gui/elastic/node.cpp: patch does not apply
error: patch failed: retroshare-gui/src/gui/elastic/node.h:118
error: retroshare-gui/src/gui/elastic/node.h: patch does not apply
error: patch failed: retroshare-gui/src/gui/gxsforums/GxsForumThreadWidget.cpp:1565
error: retroshare-gui/src/gui/gxsforums/GxsForumThreadWidget.cpp: patch does not apply
==> ERROR: A failure occurred in prepare().
Aborting...

Adding the option --ignore-space-change to the git apply fixes it, but I'm not sure what the best way to fix this error is, or why it's happening to me (if it isn't happening to anyone else).

herzmeister commented on 2016-06-14 11:22

indeed, is working now, thanks

sehraf commented on 2016-06-14 07:26

fixed once and for all

sehraf commented on 2016-06-12 20:02

is this (again) related to C standards?
Does anybody know how to fix this (once and for all)?

This is fix upstream for a long time now - maybe there will be a release soon...

herzmeister commented on 2016-06-12 13:29

Currently getting an error (again):

In file included from dbase/fimonitor.cc:29:0:
./rsserver/p3face.h: At global scope:
./rsserver/p3face.h:197:40: error: ‘constexpr’ needed for in-class initialization of static data member ‘const double RsServer::minTimeDelta’ of non-integral type [-fpermissive]
static const double minTimeDelta = 0.1; // 25;
^~~
./rsserver/p3face.h:198:40: error: ‘constexpr’ needed for in-class initialization of static data member ‘const double RsServer::maxTimeDelta’ of non-integral type [-fpermissive]
static const double maxTimeDelta = 0.5;
^~~
./rsserver/p3face.h:199:37: error: ‘constexpr’ needed for in-class initialization of static data member ‘const double RsServer::kickLimit’ of non-integral type [-fpermissive]
static const double kickLimit = 0.15;
^~~~
Makefile.libretroshare:1740: recipe for target 'temp/linux-g++/obj/fimonitor.o' failed
make[1]: *** [temp/linux-g++/obj/fimonitor.o] Error 1
make[1]: Leaving directory '/tmp/yaourt-tmp-mep/aur-retroshare/src/RetroShare-0.6.0/libretroshare/src'
Makefile:99: recipe for target 'sub-libretroshare-src-libretroshare-pro-make_first' failed
make: *** [sub-libretroshare-src-libretroshare-pro-make_first] Error 2
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build retroshare.

sehraf commented on 2016-04-18 09:25

should be fixed now

sehraf commented on 2016-04-18 06:49

can confirm - i'll have a look

All comments