Package Details: pcsxr-git 1.9.94.r1697.6484236c-2

Git Clone URL: https://aur.archlinux.org/pcsxr-git.git (read-only, click to copy)
Package Base: pcsxr-git
Description: A Sony PlayStation emulator based on the PCSX-df Project
Upstream URL: https://github.com/pcsxr/PCSX-Reloaded/tree/master/pcsxr
Licenses: GPL
Conflicts: pcsx-df, pcsxr
Provides: pcsxr
Replaces: pcsxr-svn
Submitter: alucryd
Maintainer: tallero
Last Packager: tallero
Votes: 47
Popularity: 0.000000
First Submitted: 2016-08-16 19:25 (UTC)
Last Updated: 2021-06-03 09:27 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

mikeym commented on 2013-07-11 11:07 (UTC)

It looks like the host CodePlex is broken for the latest version of subversion: https://codeplex.codeplex.com/wikipage?title=Using%20TortoiseSVN%20with%20CodePlex "'downgrading' to a SVN-Client Version 1.7.x is currently the only way to access a codePlex project via SVN :( Your working-copy has to be checked out again, if you've already 'updated' it. So unless CodePlex staff fixes their server-side bridge, I can only recomment to stay on 1.7.x!" So does not work with my subversion-1.8.0-1. I've found a link to the latest version that looks promising as a workaround: https://pcsxr.codeplex.com/SourceControl/latest#

coincoincanard commented on 2013-04-30 22:03 (UTC)

I've been tring for the past 10 days, I still get this error no matter how hard I try.

Enverex commented on 2013-04-21 12:16 (UTC)

Looks like it was just brief downtime or an issue your side, it's working fine for me now.

coincoincanard commented on 2013-04-20 21:41 (UTC)

Impossible to use, the svn url doesn't look to be good anymore. svn: E175002: Unable to connect to a repository at URL 'https://pcsxr.svn.codeplex.com/svn/pcsxr' svn: E175002: OPTIONS de 'https://pcsxr.svn.codeplex.com/svn/pcsxr' : Could not resolve hostname `pcsxr.svn.codeplex.com': Host not found (https://pcsxr.svn.codeplex.com)

BlackLotus89 commented on 2013-04-05 15:12 (UTC)

Alucryd now that the bug tracker is up again I did ;) Just wanted to have it fixed in my favourite PKGBUILD as long as it isn't upstream.Oh and clean code was the issue not clang per se.

alucryd commented on 2013-04-05 09:52 (UTC)

Schala: No hard feelings, just be more careful next time :)

Schala commented on 2013-04-05 09:48 (UTC)

I apologise... I have a habit of doing that without offensive intention.

alucryd commented on 2013-04-05 08:08 (UTC)

BlackLotus89: GCC is still the default in arch, and as long as it is, patches for CLang are to be submitted upstream. Please use your patch locally for now, and submit it upstream when the bugtracker is back up.

BlackLotus89 commented on 2013-04-05 04:36 (UTC)

A little patch for clean code and for clang compability: --- pcsxr/plugins/dfinput/cfg-gtk.c 2013-04-05 05:57:36.193685594 +0200 +++ pcsxr/plugins/dfinput/cfg-gtk.c 2013-04-05 05:58:40.826422140 +0200 @@ -751,7 +751,7 @@ return 0; } -void PADabout() { +long PADabout() { const char *authors[]= {"Wei Mingzhi <weimingzhi@gmail.com>", NULL}; GtkWidget *widget; --- pcsxr/plugins/dfinput/pad.h 2013-04-05 05:57:24.080464107 +0200 +++ pcsxr/plugins/dfinput/pad.h 2013-04-05 05:58:26.306556209 +0200 @@ -231,7 +231,7 @@ long PADreadPort2(PadDataS *pad); long PADkeypressed(void); long PADconfigure(void); -void PADabout(void); +long PADabout(void); long PADtest(void); #ifdef __cplusplus --- pcsxr/plugins/dfinput/pad.c 2013-04-05 05:57:18.437182811 +0200 +++ pcsxr/plugins/dfinput/pad.c 2013-04-05 05:58:17.433304807 +0200 @@ -665,7 +665,7 @@ return PSE_PAD_ERR_SUCCESS; } -void PADabout(void) { +long PADabout(void) { int pid = fork(); if (pid == 0) { EOF I wanted to send it to the bugtracker of pcsxr but it has to wait (it's down right now)

alucryd commented on 2013-04-04 21:08 (UTC)

Well I've found some mushrooms beside my front door, I thought I'd try eating them... Did you really think I'd invent all the stuff in there on a whim... Had you followed the aur-general mailing list, which as an AUR user, you should do, you'd have known that pacman 4.1 is on the way and already in [testing]. While I admit I forgot to post a comment (I did on all the others I've updated so far), even out of pure curiosity and respect, I'd have searched around before spouting so many offensive dots...

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »