Bug 923941 - Dependency generator can match incorrectly
Summary: Dependency generator can match incorrectly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nodejs
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: T.C. Hollingsworth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-20 18:39 UTC by Tom Hughes
Modified: 2013-04-05 23:02 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-04-05 23:02:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tom Hughes 2013-03-20 18:39:24 UTC
The new native module dependency generator has this path match:

  %__nodejs_native_path ^/usr/lib.*/node_modules/.*\.node$

but it seems that it should actually be \\.node on the end - current it is matching any name (like jasmine-node) that happens to end in "node" and is adding false abi dependencies to those packages.

The original one is also wrong when matching package\.json but is rather less likely to actually mistrigger.

Comment 1 T.C. Hollingsworth 2013-03-20 20:22:58 UTC
jwz was wrong.  Regular expressions usually cause a lot more than *two* problems.  ;-)

I added the extra escape as you suggested and node-jasmine no longer seems to get the ABI provides.  Fixing the non-native one as suggested also doesn't seem to break anything, so we'll go with more correct even though I don't have a test case for breakage there.

nodejs-0.6.10-4 is building for all branches now.

Thanks for the report and the fix!

Comment 2 Fedora Update System 2013-03-20 21:00:35 UTC
v8-3.14.5.7-1.fc18, libuv-0.10.0-2.git5462dab.fc18, nodejs-0.10.0-4.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2012-20578/nodejs-0.10.0-4.fc18,libuv-0.10.0-2.git5462dab.fc18,v8-3.14.5.7-1.fc18

Comment 3 Fedora Update System 2013-03-21 23:55:07 UTC
Package v8-3.14.5.7-1.fc18, libuv-0.10.0-2.git5462dab.fc18, nodejs-0.10.0-4.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing v8-3.14.5.7-1.fc18 libuv-0.10.0-2.git5462dab.fc18 nodejs-0.10.0-4.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-20578/nodejs-0.10.0-4.fc18,libuv-0.10.0-2.git5462dab.fc18,v8-3.14.5.7-1.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2013-03-22 20:59:32 UTC
Package libuv-0.10.0-2.git5462dab.fc18, nodejs-0.10.1-1.fc18, v8-3.14.5.8-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libuv-0.10.0-2.git5462dab.fc18 nodejs-0.10.1-1.fc18 v8-3.14.5.8-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-20578/nodejs-0.10.1-1.fc18,libuv-0.10.0-2.git5462dab.fc18,v8-3.14.5.8-1.fc18
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-04-03 04:54:18 UTC
Package v8-3.14.5.8-1.fc18, nodejs-0.10.2-1.fc18, libuv-0.10.3-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing v8-3.14.5.8-1.fc18 nodejs-0.10.2-1.fc18 libuv-0.10.3-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-20578/nodejs-0.10.2-1.fc18,libuv-0.10.3-1.fc18,v8-3.14.5.8-1.fc18
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-04-05 23:02:22 UTC
v8-3.14.5.8-1.fc18, nodejs-0.10.2-1.fc18, libuv-0.10.3-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.