Package: node-bones Version: 2.0.1+ds1-4 Severity: normal As part of the gargantuan effort to ship tilemill in Debian, I am struggling with this package, which was, I assume, uploaded exactly for tilemill (because it has no other reverse dependencies).
It turns out that tilemill depends explicitely on version 1.3.27, while Debian ships the 2.0 release, which is actually *older* that the 1.3 series: https://github.com/developmentseed/bones/releases I have seen this strangeness before, in fact in tilemill itself: https://github.com/mapbox/tilemill/issues/2258 So I am not sure how to deal with this. Maybe a removal from unstable and a new upload of 1.3 would avoid an epoch change... Thanks for looking into this. A. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages node-bones depends on: ii node-backbone 0.9.2-4 ii node-express 2.5.9-2 ii node-jquery 1.6.3-1 ii node-mirror 0.3.3-3 ii node-optimist 0.3.5-1 ii node-underscore 1.4.4-2 ii nodejs 0.10.26~dfsg1-1 node-bones recommends no packages. node-bones suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org