I'm getting the following error when performing Team-> Update from eclipse/RAD. Any idea how I can resolve this?
cvs update -l -d -P "/Boss/ejbModule/com/arch/boss/dao/BossDeviceDAO.java" "/Boss/ejbModule/com/arch/boss/dao/BossDeviceDAO.java"
U ejbModule/com/arch/boss/dao/BossDeviceDAO.java
cvs server: nonmergeable file needs merge
cvs server: revision 1.17 from repository is now in ejbModule/com/arch/boss/dao/BossDeviceDAO.java
cvs server: file from working directory is now in .#BossDeviceDAO.java.1.16
C ejbModule/com/arch/boss/dao/BossDeviceDAO.java
ok (took 0:21.461)
Error: The following warnings were reported while performing the "cvs update" command.
Error: Boss: An unmergable conflict has occurred for binary file /Boss/ejbModule/com/arch/boss/dao/BossDeviceDAO.java. Revision 1.17 has been loaded and overwritten local changes have been saved in file /Boss/ejbModule/com/arch/boss/dao/.#BossDeviceDAO.java.1.16
***
I see that in the CVS folder, the Entries file contains the entry for the file that I tried to update with version of 1.6. But in CVS repository, the latest version is 1.7. I did a compare of the source on my local and version 1.7 in the repository and see that I have the latest. So, I use notepad and manually update the entry to version 1.7 and the problem went away.
Related
I want to create a yum repository from my Artifactory URL where I have various rpm packages available.
I created .repo file as below in /etc/yum.repos.d
[customrepo]
name=CustomRepository
baseurl=https://jfrogurl/postgres/13.01.0000
enabled=1
gpgcheck=0
After this when I type yum list I get the following error:
Error: Failed to download metadata for repo 'customrepo': repomd.xml parser error: Parse error at line: 32 (Opening and ending tag mismatch: meta line 0 and head)
Am I missing anything?
You need to make sure that the baseurl in yum.repos.d points to the path which contains the Yum repository metadata files.
From your question it looks like you are pointing to postgres/13.01.0000. You need to make sure that this path contains the metadata files.
By default the metadata is stored relative to the repository's root folder. In this case, Artifactory searches the entire repository for RPMs and saves the repodata directory at $REPO-KEY/repodata. You can control this behavior by configuring the RPM Metadata Folder Depth parameter.
I'm using a batch file to load a workspace repository and accept change sets.
The files in the repository have Eclipse projects.
When I accept a change set, the SCM automatically creates the projects in .metadata:
Windows:
C:\Users\[user_name]\AppData\Local\jazz-scm\scratch\0\.metadata\.plugins\org.eclipse.core.resources
If I accept another change set with changes in Eclipse projects, the SCM tries to create the project in .metadata and throws this error in the log:
com.ibm.team.filesystem.client.FileSystemStatusException: Status ERROR: com.ibm.team.filesystem.client code=0 There were issues encountered during the updating of the sandbox. null children=[Status ERROR: com.ibm.team.filesystem.client code=0 Unable to open project at [path_of_file]/.project, project with name [project_name] already exists null Status ERROR: com.ibm.team.filesystem.client code=0 Unable to open project at [path_of_file]/.project, project with name [project_name] already exists null]
How do I prevent the SCM CLI accept command from generating projects in .metadata?
SCM CLI version:
Build Id: RTC-I20141031-0926
com.ibm.team.filesystem.cli.client, version 3.2.400.v20141016_0123
com.ibm.team.filesystem.cli.tools, version 3.1.800.v20140620_0123
com.ibm.team.filesystem.cli.core, version 3.2.400.v20141011_0139
com.ibm.team.rtc.cli.infrastructure, version 3.1.800.v20140619_0246
I've forked a package from github have made some changes. I'm trying to install the version of the package to which I've made changes with install_github(), but am getting an error message. Any suggestions?
The forked version: https://github.com/embruna/refnet
The edited version on the branch: https://github.com/embruna/refnet/tree/proposed-updates
I can install the forked version with:
install_github("embruna/refnet", subdir="pkg")
I tried to install the version on the branch with the following:
install_github("embruna/refnet#proposed-updates", subdir="pkg")
But then get this error:
** help
*** installing help indices
** building package indices
Error in scan(file = file, what = what, sep = sep, quote = quote, dec = dec, :
line 1 did not have 6 elements
ERROR: installing package indices failed
* removing ‘/Library/Frameworks/R.framework/Versions/3.3/Resources/library/refnet’
Error: Command failed (1)
Thanks for any suggestions.
EDIT: There were two problems: 1) the install_github syntax I used incorrect and 2) there was a folder in "pkg" that was throwing an error even after correcting the syntax. See below for details.
I'm guessing that specifying the branch with # but the subdirectory with the subdir argument is confusing devtools.
This works for me (specifying both subdir and branch in the repo argument):
install_github("embruna/refnet/pkg#proposed-updates",
So does this (specifying both branch and subdir as separate arguments):
devtools::install_github("embruna/refnet",
ref = "proposed-updates", subdir = "pkg")
The output starts this way ...
Using GitHub PAT from envvar GITHUB_PAT
Downloading GitHub repo embruna/refnet#proposed-updates
from URL https://api.github.com/repos/embruna/refnet/zipball/proposed-updates
Installing refnet
This is with devtools 1.12.0
I was able to install your proposed-updates branch with this:
install_github("embruna/refnet", branch = "proposed-updates", subdir = "pkg")
I get a bunch of warnings, but no error messages.
Just getting started with JOlivers event store library and having issues with some of the Nuget commands in the build.cmd. here's the log, perhaps you're already aware of the issue but i thought i'd put it up here.
=== COMPILING ===
Compiling / Target: v4.0 / Config: Release
S:\SourceControl\Test Projects\EventStore\bin\nuget\NuGet.targets(6,9): error : Input string was not in a correct format. [S:\SourceControl\Test Projects\EventStore\src\proj\EventStore.Persistence.RavenPersistence\EventStore.Persistence.RavenPersistence.csproj]
S:\SourceControl\Test Projects\EventStore\bin\nuget\NuGet.targets(6,9): error MSB3073: The command ""S:\SourceControl\Test Projects\EventStore\src\..\bin\nuget\nuget.exe" install "S:\SourceControl\Test Projects\EventStore\src\proj\EventStore.Persistence.RavenPersistence\packages.config" -source "" -o "S:\SourceControl\Test Projects\EventStore\src\..\bin"" exited with code 1. [S:\SourceControl\Test Projects\EventStore\src\proj\EventStore.Persistence.RavenPersistence\EventStore.Persistence.RavenPersistence.csproj]
The master branch of EventStore appears to be broken at the moment. The 3.0 branch is in better shape but is also slightly broken. To fix the 3.0 branch so that it builds, you need to upgrade the 1.5 version of nuget.exe to 1.6. The easiest way to do that is to execute \bin\nuget\NuGet.exe update -self in the repository. I already submitted a pull request to JOliver with that change.
(I also submitted a pull request with a few minor fixes for the example project.)
org.tigris.subversion.javahl.ClientException:
svn: File not found: revision 2276, path '/mobilehollerweb/trunk/admin/mobilehollerweb/trunk/admin'
svn: '/svn/venturedive/!svn/bc/2276/mobilehollerweb/trunk/admin' path not found: 404 Not Found (https://subversion.assembla.com)
org.tigris.subversion.javahl.ClientException:
svn: File not found: revision 2276, path '/mobilehollerweb/trunk/admin/mobilehollerweb/trunk/admin'
svn: '/svn/venturedive/!svn/bc/2276/mobilehollerweb/trunk/admin' path not found: 404 Not Found (https://subversion.assembla.com)
I get this error when creating a tag for my code. We use assembla as our host and I use eclipse with subclipse plugin installed.
Based on the error message, it looks likes you're trying to run a command like:
svn copy https://subversion.assembla.com/svn/mobilehollerweb/trunk/admin /mobilehollerweb/trunk/admin -m "create a tag"
I think what you want is to do something like:
svn copy https://subversion.assembla.com/svn/mobilehollerweb/trunk/admin /mobilehollerweb/tags/admin/1.0 -m "create a tag"
SVN will not recursively create directories that aren't there-- the directory /tags/admin must already exist before the "1.0" tag can be created.