#9501 closed defect (fixed)
JOSM build failed with SVN
Reported by: | Andre68 | Owned by: | team |
---|---|---|---|
Priority: | major | Milestone: | 14.01 |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
I'm fetching JOSM by SVN and currently cannot compile the latest JOSM on a Ubuntu system.
Besides a long list of warnings I believe the relevant part is the following:
init-svn-revision-xml: init-git-revision-xml: [exec] Result: 128 create-revision: [xmlproperty] [Fatal Error] REVISION.XML:1:1: Content is not allowed in prolog. BUILD FAILED /home/andi/Projekte/osm/josm/build.xml:74: Failed to load /home/andi/Projekte/osm/josm/REVISION.XML
The file REVISION.XML contains the following:
fatal: Not a git repository (or any parent up to mount point /home) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
I'm not an ant expert. I believe that ant tries to execute 'LANG="C" svn info --xml .' which gives the following output on my system:
<?xml version="1.0" encoding="UTF-8"?> <info> <entry kind="dir" path="." revision="6581"> <url>http://josm.openstreetmap.de/svn/trunk</url> <repository> <root>http://josm.openstreetmap.de/svn</root> <uuid>0c6e7542-c601-0410-84e7-c038aed88b3b</uuid> </repository> <wc-info> <wcroot-abspath>/home/andi/Projekte/osm/josm</wcroot-abspath> <schedule>normal</schedule> <depth>infinity</depth> </wc-info> <commit revision="6581"> <author>simon04</author> <date>2013-12-31T14:10:06.679140Z</date> </commit> </entry> </info>
This looks fine to me and the error code is 0.
File state of REVISION.XML is -rw-r--r-- which should also be fine.
So why does ant afterwards try to run git?
Attachments (0)
Change History (4)
comment:1 Changed 10 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 Changed 10 years ago by
Milestone: | → 14.01 |
---|
comment:3 Changed 9 years ago by
On Ubuntu 14.04 I also had to do this:
svn upgrade
before building.
comment:4 Changed 9 years ago by
This is unrelated to this ticket. Reading the texts you were presented properly you should have noticed that this happens when you update your local subversion to a new version!
In 6585/josm: