On Sat, Nov 12, 2016 at 12:14:37PM +0100, Jonas Smedegaard wrote:
> Quoting Jérémy Lal (2016-11-12 10:51:08)
> > leaflet reverse dependencies need extra careful checks, because i
> > believe there are been many changes between 1.0 and 0.7.
>
> Right. Luckily only few packages depend on leaflet, but indeed they
> need to be checked thoroughly for incompatibilities.
Any news here? I need to package r-cran-leaflet which has a code copy
of leaflet 1.3.1. I guess the recent upstream version 1.3.4 will be
fine as well.
I gave the packaging a naive try imported the new version into leaflet
Git[1] but ended up with:
debian/rules build
test -x debian/rules
mkdir -p "."
jake build
jake aborted.
Error: No Jakefile. Specify a valid path with -f/--jakefile, or place one in
the current directory.
at api.fail (/usr/lib/nodejs/jake/api.js:326:18)
at EventEmitter.utils.mixin.run (/usr/lib/nodejs/jake/jake.js:317:9)
(See full trace by running task with --trace)
make: *** [debian/rules:32: build/libjs-leaflet] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
I: copying local configuration
E: Failed autobuilding of package
Thus I will not push my poor naive changes (which was basically
importing the new version and removing the patch which was trying to fix
a not existing Jakefile). I have no experience with JS and thus will
not be of any help at all.
Kind regards
Andreas.
[1] https://salsa.debian.org/js-team/leaflet
--
http://fam-tille.de
