Package Details: josm-svn 19018-1

Git Clone URL: https://aur.archlinux.org/josm-svn.git (read-only, click to copy)
Package Base: josm-svn
Description: An editor for OpenStreetMap written in Java
Upstream URL: http://josm.openstreetmap.de/
Keywords: openstreetmap
Licenses: GPL
Conflicts: josm
Provides: josm
Submitter: SammysHP
Maintainer: SammysHP
Last Packager: SammysHP
Votes: 31
Popularity: 0.013360
First Submitted: 2018-06-03 10:03 (UTC)
Last Updated: 2024-03-20 18:33 (UTC)

Dependencies (6)

Required by (1)

Sources (3)

Pinned Comments

Latest Comments

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

s1zed commented on 2022-10-10 18:09 (UTC)

This package is currently out of date for some reason. I am getting version 18557 and latest is 18570 according to the JOSM website.

SammysHP commented on 2022-01-22 17:21 (UTC)

@msnspk The package builds fine for me. Check that your system is up-to-date and try a clean build.

msnspk commented on 2022-01-21 18:40 (UTC) 

==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version:

I guess something changed upstream?

SammysHP commented on 2021-03-29 11:23 (UTC)

@thibaultmol Not necessary. The dependencies in the PKGBUILD list java-environment>=8 which includes 16.

thibaultmol commented on 2021-03-29 09:55 (UTC)

latest josm update also supports java 16 btw (guess it can be changed in the dependencies?) https://josm.openstreetmap.de/wiki/Changelog#stable-release-21.02

SammysHP commented on 2018-06-22 20:48 (UTC)

I disabled the auto update to not disturb the upcoming merge with josm-svn.

SammysHP commented on 2018-06-03 09:02 (UTC)

@Eli

Your argument is absolutely justified. I adopted this package about five years ago when it already skipped the checksum and simply downloaded the pre-compiled josm-latest.jar. I maintain this primarily for legacy reasons and because it is rather convenient to use this in a pre-compiled form:

  • Download might be quicker (unless you keep the svn directory)
  • Official build (non-reproducible because of private build script; but you don't know what you get)
  • Compilation requires additional dependencies and takes a long time (about one minute on my machine, but that is expected from source packages)

All in all there are no clear pros and cons (except for the crude implementation at the moment). I'll provide an SVN version shortly (when it is tested), but keep this package for a while with a legacy warning so that users have time to change to the new version.

eschwartz commented on 2018-06-03 07:18 (UTC)

Umm...

Why don't you just create an svn package which clones the svn sources, then runs "ant dist" to create the latest version?

I'm entirely unsure why you're doing such elaborate magic instead, especially considering "latest" is an inaccurate name.

This also avoids the issue where you've disabled checksums because you want to use nightly binaries but cannot be bothered to do any checking whatsoever, so even if the download is truncated you'll happily consider the package a success. There's a reason why checksums exist...

SammysHP commented on 2018-03-24 18:38 (UTC)

It happened! Automatic updates are now live. If you notice any strange behavior or if you think that this is a really bad idea, please leave a comment (and ideally a suggestion for a better method).

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