Hi Jonas, On Thu, Aug 23, 2018 at 10:49:52AM +0200, Jonas Smedegaard wrote: > Quoting Andreas Tille (2018-08-23 09:45:17) > > Any news here? > > Leaflet 1.0.3 is in experimental since a while. That means > incomatibilities should be easier to test. > > Pending is for someone to test which reverse dependencies break with the > newer Leaflet.
My poor (rather non-existing) JS knowledge might explain my possibly naive question: Does it make sense to spent time to test a version which is obviously outdated at the time of testing? I'd consider it a sensible strategy to upload 1.3.x to experimental and do the testing on this version since the motivation of testers might be higher. > Bonus points for providing patches to automate such testing ;-) Sorry, I do not even know how to test manually and I have zero resources to dive into this. > > 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. > > This bug#844075 is about updating to release 1.0.1 (impractical to > eternally be about "latest"). I have adjusted the title accordingly. Remembering my naivity - but I'd consider this a diversion from the bug reporters intention (Ross in CC). If the report said "latest" than changing the bug title to "current at time of bug report" might or might not intended by the reporter. So I'd rather ask back what's really needed. > Please file a separate bug if r-cran-leaflet cannot be patched to use > Leaflet 1.0.3 now in experimental (and please have that new bugreport > track a specific lowest-possible version to not repeat this confusion). I admit I will not dive into patching some code to support older versions of some code copies before I do not see any other chance. I for myself consider living with a code copy until the Debian package catches up the more promising strategy here. Kind regards Andreas. -- http://fam-tille.de
