I am new to using SVN, and I am trying it out on an android project. I am getting a commit failure based on this error..
svn: E155023: Can't set properties on 'C:\AndroidWorkSpace\myApp\bin\res': invalid status for updating properties.
I have searched for similar problems, but the lingo is all over my head. I just installed SVN on eclipse (it has successfully updated/committed previously), and I opened a repository on cloudforge.com. Other than that, I don't know much about it.
I have tried cleaning project and running team>clean up.
Here is the description of the bug, which might cause this error:
http://subversion.tigris.org/issues/show_bug.cgi?id=4004
Hope that helps!
Related
I've been trying to get On-Demand Resource to work but I keep getting this compile error:
/* com.apple.actool.errors */
: error: The tag combination "tagName" for "xxx.imageset/xxx#3x.png" has no output specification.
I had a look at actool man page and there's an option:
--asset-pack-output-specifications filename
Which says:
Tells actool where to write the information about ODR resources found
in the asset catalog. The emitted file will be a plist.
But I'm not really sure what to put as an argument/where this plist is used or even if this option is in the right track of fixing the error.
My coworkers and I struggled with this error for over a day and were only able to fix it by wiping our existing local repos and installing a fresh clone from our remote repos with the code that contains the on-demand resources.
In our case, I was the one that created the on-demand resources functionality and did the tagging for the assets. I built and ran all of that code, and everything worked fine locally on my machine. I pushed those commits to our remote, and when my coworkers pulled they received the asset catalog compile error that you reported when they tried to build.
I compared my build logs with those of my coworkers and found that I had the --asset-pack-output-specifications flag along with a filename whereas they did not, even though all of our production code was the same. I never set that flag manually myself during development, it was automatically generated at some point in the process but I have no idea where -- I didn't even know it existed until this build failure occurred. After struggling for many hours we noticed that if my coworkers deleted their local projects entirely and basically started fresh by installing a new project and repo again from the remote, they suddenly were able to build. They had already tried to clean and nuke their derived data, but that didn't work. Only totally deleting the repos and the projects entirely did the trick. Not sure why, but something about wiping the project and all associated directories and building themselves totally fresh from their own local machines triggered something that enabled the --asset-pack-output-specifications flag.
I just faced this issue and was totally against deleting my repo and cloning again.
I noticed that alongside this error, I also got a warning stating that I had assets under the same name (thus being duplicated).
Deleting the duplicated asset in order to get rid of the warning, fixed the compilation error.
Hope this helps someone, as deleting the repo and cloning again shouldn't be an option.
I just faced the issue.
I could solve it just by deleting on-demand resource tags and tagging them back again.
I just solve it by rebooting Xcode then run successfully. The error seems to only appear once...I don't know why.
I am using Eclipse Indigo to log into a CVS server. When I try to synchronize with the repository, I am getting this error:
Problems reported while synchronizing CVS Workspace. 0 of 1 resources
were synchronized. The server reported an error: unrecognized request
`dated Template Copy-file Mod-time Set-static-directory
Update-existing Clear-static-directory Set-sticky New-entry MT
Notified Created Remove-entry Checked-in Merged Removed Valid-requests
Clear-sticky Module-expansion'
I am able to commit changes, but I cannot see any updates. Does anyone know what this error message means and how to resolve it? Thanks for your help.
You can try this it might solve your problem
Had the same problem, and solved it when i deleted the content of my workspace/project/WebContent/folder with problem/CVS/Entries, then i refreshed my files in eclipse and it worked.
I guess something there was corrupted.
From here.
I recently started using git with the egit plugin in eclipse, and I thought I had everything working. I cloned a remote repository to my machine, then made a change to a file, and went to commit the change via selecting the file in the project, and going to Team > Commit.... As soon as I do, I get the following error:
Unhandled event loop exception
org.eclipse.swt.SWTError: No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)]
at org.eclipse.swt.SWT.error(SWT.java:4308)
at org.eclipse.swt.browser.Mozilla.initMozilla(Mozilla.java:1826)
at org.eclipse.swt.browser.Mozilla.create(Mozilla.java:687)
at org.eclipse.swt.browser.Browser.<init>(Browser.java:96)
...
(output abbreviated)
I am fully willing to accept that this is a bug of sorts (even though I thought this was working earlier today), but I am hoping someone may have encountered this problem once before.
Any insights? Even if it is only who I should file the bug against? I can provide any additional details. I should also point out that things work fine if I commit through the git repository view.
The problem is that the particular git workflow is creating a SWT Browser component that is having trouble loading on your particular OS + Windowing system + mozilla library version combination. There is a bit of black magic that has to go on to make sure you get the right configuration to allow the SWT browser to work with your embedded mozilla renderer. You can get detailed information on the SWT FAQ page here.
Also there are many other posts on this site that talk about how to resolve the dreaded "NO MORE HANDLES" problem here.
We have a git repository managed by gitosis under Ubuntu, which has worked well all up to the disk ran full. After reading up a bit on the issue, I found that git gc and git gc --aggresive got me quite a bit of diskspace back. Very nice.
Unfortunately this appears to have broken something in egit, as I get this message when trying to clone our repository (during the checkout phase at around 10%)
Packfile corruption detected: Unknown
zlib error.
Interestingly enough the git in msysgit works just fine as before.
I tried upgrading egit to the nightly build of 0.12 as there was some mailing list messages hinting this had been fixed within the last week, but to no avail.
My question now is, what can I do to my repository to get to a state where egit works again? I have full control over the Ubuntu instance running gitosis.
EDIT: I got a stack trace from the Eclipse event log
org.eclipse.jgit.errors.TransportException: Packfile corruption detected: Unknown zlib error.
at org.eclipse.jgit.transport.BasePackFetchConnection.doFetch(BasePackFetchConnection.java:287)
at org.eclipse.jgit.transport.BasePackFetchConnection.fetch(BasePackFetchConnection.java:225)
at org.eclipse.jgit.transport.FetchProcess.fetchObjects(FetchProcess.java:214)
at org.eclipse.jgit.transport.FetchProcess.executeImp(FetchProcess.java:149)
at org.eclipse.jgit.transport.FetchProcess.execute(FetchProcess.java:111)
at org.eclipse.jgit.transport.Transport.fetch(Transport.java:903)
at org.eclipse.egit.core.op.CloneOperation.doFetch(CloneOperation.java:228)
at org.eclipse.egit.core.op.CloneOperation.run(CloneOperation.java:135)
at org.eclipse.egit.ui.internal.clone.GitCloneWizard.executeCloneOperation(GitCloneWizard.java:259)
at org.eclipse.egit.ui.internal.clone.GitCloneWizard.access$3(GitCloneWizard.java:252)
at org.eclipse.egit.ui.internal.clone.GitCloneWizard$4.run(GitCloneWizard.java:233)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: org.eclipse.jgit.errors.CorruptObjectException: Packfile corruption detected: Unknown zlib error.
at org.eclipse.jgit.transport.PackParser$InflaterStream.read(PackParser.java:1530)
at org.eclipse.jgit.transport.PackParser$InflaterStream.skip(PackParser.java:1500)
at org.eclipse.jgit.util.IO.skipFully(IO.java:203)
at org.eclipse.jgit.transport.PackParser.inflateAndSkip(PackParser.java:1352)
at org.eclipse.jgit.transport.PackParser.indexOneObject(PackParser.java:834)
at org.eclipse.jgit.transport.PackParser.parse(PackParser.java:448)
at org.eclipse.jgit.storage.file.ObjectDirectoryPackParser.parse(ObjectDirectoryPackParser.java:178)
at org.eclipse.jgit.transport.PackParser.parse(PackParser.java:410)
at org.eclipse.jgit.transport.BasePackFetchConnection.receivePack(BasePackFetchConnection.java:649)
at org.eclipse.jgit.transport.BasePackFetchConnection.doFetch(BasePackFetchConnection.java:280)
... 11 more
Edit: Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=340305
One way to get a clone without EGit is to:
make a bundle on the server
copy the unique file representing that bundle on the client side
try to clone it in command-line.
Since you mention you can process the bundle with msysgit, that suggests a bug on the Egit or JGit side, as illustrated by bug 330758.
The usual course of action is to update to the nightly latest fo EGit, using this p2 update site, and see if the problem is still there.
If the issue persists, you can then file a bug report or complete the existing one (330758).
Please check the versions of Git you are running and make sure they match.
The latest egit 0.12 does not show this behaviour.
Hopefully the bug has been fixed for real, and not just an accidental side effect.
I get this error :
Share project was failed.
svn: Error writing entries file for
'C:\workspace2\Test'
svn: Entry '' has inconsistent
repository root and url
But we get this error only on a particular PC. Also if we move the workspace in a network drive, everything works fine.
We are using FDT(eclipse based IDE).
We are totaly new to SVN...
I am looking for any advice who will helping us solving the problem
UPDATE:
Without any particular change the problem is gone ?!
Can you reproduced the issue with the latest Eclipse (Galileo 3.5.1)?
And what Subversion Eclipse plugin are you using? (Subversive or Subclipse?)
There was a bug with Subversive with path including a special character (like ~).
In your case, check the 'C:\workspace2\Test' has no special character in it, like a space at the very end. ('C:\workspace2\Test')