FS#25066 - [js][mongodb] compiled without UTF8 support

Attached to Project: Community Packages
Opened by Salvador de la Puente (lodr) - Friday, 08 July 2011, 07:26 GMT
Last edited by Thomas Dziedzic (tomd123) - Monday, 26 September 2011, 21:22 GMT
Task Type Feature Request
Category Upstream Bugs
Status Closed
Assigned To Ionut Biru (wonder)
Thomas Dziedzic (tomd123)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

Current package is not built with UTF8 support.

Additional info:
* js version: 1.8.5-1
* mongodb version to reproduce: 1.8.2-5

Steps to reproduce:

1.- Try to install mongodb-1.8.2-5 from community-testing repository
2.- Run mongo and you'll see a warning saying that spidermonkey (now js) was not build with UTF8 support.
This task depends upon

Closed by  Thomas Dziedzic (tomd123)
Monday, 26 September 2011, 21:22 GMT
Reason for closing:  Fixed
Additional comments about closing:  mongodb now includes its own internal copy of js
Comment by Ionut Biru (wonder) - Friday, 08 July 2011, 08:07 GMT
i don't see anything relevant to UTF8 in js.
Comment by Thomas Dziedzic (tomd123) - Sunday, 10 July 2011, 18:39 GMT
because I think this has to do with adding official support for mozjs185 in mongodb, I have posted a comment on:

https://jira.mongodb.org/browse/SERVER-2887
SpiderMonkey 1.8.5 support
Comment by Thomas Dziedzic (tomd123) - Tuesday, 12 July 2011, 19:10 GMT
another related bug
https://jira.mongodb.org/browse/SERVER-1104
Comment by Ionut Biru (wonder) - Monday, 18 July 2011, 17:57 GMT
as you guys see, Eliot knew about this issue since more than a year ago and didn't do anything to fix. We cannot do anything
Comment by Konstantin Gribov (gross) - Monday, 18 July 2011, 18:32 GMT
To solve this problem use this patch for PKGBUILD.
It sets -DJS_C_STRINGS_ARE_UTF8 flag for c++ compiler. So utf8 is enabled.
   PKGBUILD.patch (0.3 KiB)
Comment by Konstantin Gribov (gross) - Monday, 18 July 2011, 18:44 GMT
One question: how to tell package mainteiner about this solution?
Comment by Ionut Biru (wonder) - Monday, 18 July 2011, 18:56 GMT
i'm the maintainer
Comment by Konstantin Gribov (gross) - Monday, 18 July 2011, 19:02 GMT
Ok, it's good)
This solution should work both on x86 and x64. Please, add it to official repo.
Comment by Thomas Dziedzic (tomd123) - Monday, 18 July 2011, 19:08 GMT
please link/report the bug upstream to js..
Comment by Ionut Biru (wonder) - Thursday, 21 July 2011, 21:37 GMT
@Kostya i'm going to drop this workaround from js. It breaks gjs/gnome-shell handling.

I also reported to mozilla and they said that is not the right way to do. [1]
If you really want this to be fixed, i suggest to contact mongodb developers.My comments and account were deleted from their bugtracker, true maybe that is my fault.

What you have to do is:
Open a *new bug* explaining that modern JS shared libraries have runtime support to turn UTF8 strings on or off programatically, and request that they do that before they init the runtime.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=628723#c48
Comment by Thomas Dziedzic (tomd123) - Wednesday, 03 August 2011, 15:09 GMT
The only way this will get fixed is if upstream fixes it.

Please comment on their report.

Leaving this open for others wondering why their mongodb app is giving them warnings.

Loading...