I like P4Win than P4V but it seems P4Win is not available in perforce.com.
Can anybody tell me where can I get P4Win?
Yes Perforce have discontinued P4Win, the replacement being P4V. The last version they released is available from perforce.com here:
ftp://ftp.perforce.com/perforce/r08.1/bin.ntx86/p4winst.exe
Of course it may not function correctly or some of the newer features of the perforce server such as streams will be unavailable.
Related
I have just been allocated a RHEL 6.8 box, I'd like to set up a perforce workspace there. How can I set that up? I don't believe it has p4v installed there(maybe that's step 1). Any help or assistance would be much appreciated.
Yes, installing p4 or p4v would be the logical first step.
You can find the downloads at https://www.perforce.com/downloads/helix.
I recommend starting out with plain old p4, the command-line version,
because it is easy to follow the steps for a command-line interface
when getting started.
Documentation for setting up a workspace is at https://www.perforce.com/perforce/r15.1/manuals/p4guide/chapter.configuration.html#DB5-17566.
Setting up a workspace presumes that someone has already set up a Perforce server that you can use through your workspace. You will want to get the server information from another user or the administrator. Earlier sections of the same documentation web page detail what to do with the server information once you have it.
Hope this helps.
Whenever I get error from perforce server it's printed as question marks.
I want to resolve this by setting client to english language without charset (default locale).
But even if I delete utf8-bom from WorkspaceSettings.xml it gets repopulated after quitting P4V visual client. After opening command line in P4V it shows P4CHARSET=utf8-bom. I don't have environment variables so I don't know where it gets utf8-bom value. It would be ok but this charset does not work for me.
Is this possible to revert behavior to default english locale?
Perforce Server version: P4D/NTX64/2012.1/473528 (2012/05/31)
P4V 2015.1/1233444
It turns out this is a problem with OS messages, not perforce messages. OS produces localized error message, perforce server encodes it incorrectly. I suppose this can be solved by setting perforce server to UTF8.
But we use a workaround:
P4V client version June 2011 somehow works correctly with server in this situation.
So we made a rookie mistake, One of our project team members had forgotten to commit for a couple of weeks, (some of which were vacation) but then when he did commit he did something wrong, most of the code he wrote has been overwritten with what was on the server after trying to resolve all the conflicts automatically.
So is there any way to get the code he used to have on his PC back? because a lot of work has been lost and we can't really afford to make it all again.
So just to clarify, the code which is lost is not on the server, it were his uncommitted changes on his client machine.
We are using the team foundation server and visual studio
Take a look at folder:
C:\Users\%USERNAME%\AppData\Local\Temp\TFSTemp\
In my case, searching by method name, i can recover a mistake merge =)
Nope. Code lost that never made it into source is lost. This is one of the biggest selling points of distributed version control like Git.
If your using Windows 7 or similar check for previous version of the file on his/her computer, right click the file options should be their
If you have not compiled after doing the merge, you can use DotPeek by JetBrains to decompile the assembly and get your code back
On our Trac system, two things suddenly stopped working. The first thing is the update of the "Browse Source". The second thing is the auto-fixing feature. The only solution for the first issue is to manually run the post-commit hook of the SVN repository. But than we still have the problem, that Trac doesn't close ticket anymore depending on the SVN commit message. That was working before without any issues. Ah and a third thing is that PNG images are no longer shown in the HTML preview. The user has to download the file to see it.
Is there any known bug or issue for our described problem. Or how can I update the Trac system without loosing all the information within the Trac projects (I have set up a multi project Trac system).
If all else fails, reboot the server :)
Can you give us some more info about your server and Trac setup? For example, OS and version, Trac version, plugins used, etc.
It's odd for things to suddenly quit working. If you are running a Linux system, it's possible that your server installed some updates that your system isn't fully compatible with (for example, upgrading Trac can cause some plugins to quit working properly). Check your server's logs to see if anything was updated or reconfigured around the time Trac quit working.
Also, try setting Trac's log priority to 'DEBUG' and see if the Trac logfile contains any useful error details.
The solution was the following: file permissions!
To solve the issue we used the sudo in the post-commit hooks of SVN like the following:
sudo /usr/local/bin/trac-admin /var/trac/reponame/ changeset added "reponame" $REV
And we had to allow the SVN user to run the trac-admin command using visudo:
www-data,svn ALL=(ALL) NOPASSWD: /usr/local/bin/trac-admin
I've got a program that I've been working on at home for a while, and I decided finally to throw it up on SourceForge. SourceForge offers Tracker, MantisBT, or Trac for bug tracking.
My app already has a "Sorry, an error occurred" dialog, but I'd like to add a "Complain about it" button that will submit a bug to my bug tracker. Has anyone tried to do this with Tracker? Can you submit anonymous bugs via a query string interface, or something along those lines? Or, if Tracker can't do it, how about MantisBT? Or Trac?
Programmatic access:
Mantis has a SOAP interface;
Trac has an XML-RPC interface.
If your application happens to be built on Eclipse, you can use the existing Mylyn plugins - they're both offered with 1-click install since version 3.2 (reference).
Also, Mantis 1.1.x (and perhaps later 1.2.x) has a php script (core/checkin.php) that can be called from a post-commit hook when the repo and mantis live on the same host. You just need to provide the glue for the hook, e.g. bash, and either commit all notes as a user defined 'vcs' userame or make a small modification to the php to determine the user making the commit.
In the later 1.1.x versions there is a checkincurl.php that will address usage when mantis and the repo are not collocated.