[Bug 1511949] Re: Please merge gyp from Debian

[Launchpad Bug Tracker]

This bug was fixed in the package gyp - 0.1+20150913git1f374df9-1ubuntu1

---------------
gyp (0.1+20150913git1f374df9-1ubuntu1) xenial; urgency=medium

  * Merge from Debian unstable. (LP: #1511949) Remaining changes:
      debian/preinst:
        - help dpkg when /usr/lib/python2.7/dist-packages/gyp-0.1.egg-info
        is changed from a symlink to a directory (LP: #1246730)

gyp (0.1+20150913git1f374df9-1) unstable; urgency=medium

  * Upstream update to git 1f374df9 (Closes: #798516)
  * Preprend date to upstream version
  * Update get-orig-source target
  * Update Homepage
  * Update copyright years
  * Update copyright Source
  * Install docs
  * Standards-Version 3.9.6
  * Set Section to devel instead of python

 -- Hans Joachim Desserud <ubuntu at desserud.org>  Sat, 31 Oct 2015
12:42:33 +0100

** Changed in: gyp (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511949

Title:
  Please merge gyp from Debian

Status in gyp package in Ubuntu:
  Fix Released

Bug description:
  A newer version of gyp has been packaged in Debian,
  0.1+20150913git1f374df9-1 (https://tracker.debian.org/pkg/gyp). Of
  course, due to the Ubuntu delta, this has not been synced
  automatically.

  I discovered this when I was browsing ftbfs issues and discovered that
  another packge, node-gyp, depends on this newer version. This prevents
  gyp-node in -proposed from installing which in turn triggers ftbfs for
  among others node-iconv and node-nan which attempt to install it as a
  dependency. This is probably also what keeps it from migrating to
  -release.

  I've prepared a merge locally which was pretty straight-forward for this package, but I started wondering about the fix for bug 1246730. I'm not sure about the details here, but I wonder:
  Should the version number comparison in the preinst file remain unchanged? It currently matches the latest Ubuntu version number,  but I guess changing it might have unintended consequences such as it being run multiple times when a user upgrades through versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gyp/+bug/1511949/+subscriptions