Bug#923295: src:jruby-joni: tests fail with invalid character property name <graphemeclusterbreak=emodifier>

[Andrej Shadura]

Package: src:jruby-joni
Version: 2.1.25-1
Severity: normal
Tags: upstream ftbfs
Forwarded: https://github.com/jruby/joni/issues/40

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dear Maintainer,

As you already know, jruby-joni fails build-time tests in the current
unstable:

    SEVERE ERROR: invalid character property name <graphemeclusterbreak=emodifier>
    Pattern: [/\A\X\z/] Str: [" ??"] Encoding: [UTF-8] Option: [] Syntax: [TEST]
    org.jcodings.exception.CharacterPropertyException: invalid character property name <graphemeclusterbreak=emodifier>
        at org.jruby.jcodings/org.jcodings.unicode.UnicodeEncoding.propertyNameToCType(UnicodeEncoding.java:99)
        at org.jruby.joni/org.joni.Parser$GraphemeNames.nameToCtype(Parser.java:954)
        at org.jruby.joni/org.joni.Parser.parseExtendedGraphemeCluster(Parser.java:1082)
        at org.jruby.joni/org.joni.Parser.parseExp(Parser.java:792)
        at org.jruby.joni/org.joni.Parser.parseBranch(Parser.java:1529)
        at org.jruby.joni/org.joni.Parser.parseSubExp(Parser.java:1546)
        at org.jruby.joni/org.joni.Parser.parseRegexp(Parser.java:1579)
        at org.jruby.joni/org.joni.Analyser.compile(Analyser.java:78)
        at org.jruby.joni/org.joni.Regex.<init>(Regex.java:155)
        at org.jruby.joni/org.joni.Regex.<init>(Regex.java:134)
        at org.jruby.joni/org.joni.test.Test.xx(Test.java:113)
        at org.jruby.joni/org.joni.test.Test.xx(Test.java:99)
        at org.jruby.joni/org.joni.test.Test.x2(Test.java:185)
        at org.jruby.joni/org.joni.test.TestU8.test(TestU8.java:139)
        at org.jruby.joni/org.joni.test.Test.testRegexp(Test.java:256)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
        at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52)
        at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
        at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
        at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
        at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
        at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
        at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
        at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
        at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
        at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:273)
        at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
        at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
        at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
        at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
        at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
        at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)

This bug has already been reported upstream, but I though it would be
good to track it in Debian too.

- -- 
Cheers,
  Andrej

-----BEGIN PGP SIGNATURE-----

iQFIBAEBCAAyFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAlx0buAUHGFuZHJld3No
QGRlYmlhbi5vcmcACgkQXkCM2RzYOdKfRwf9Hvf7jFWyZ112COLnHuLjLoyQtHr2
b8+mcWLYGwzW09xIxQoIzbGIypNYfXpeaArhraN1FsJnAT4AEJ9Aq88Vz0URKFzV
Bd1rD5dGgtUMDAwIyk8cRPJk8PniQLuxK3XfGoyrpO/gTLRJ6J4qbIjDO3UEpcCM
hnPFBS3fT6T5zOTRS1eXhdfCQD37rSIM/YYk0y4FMA78BC1rau1ffkvsXhOJdJwZ
N4Y+lepNQxusE0QX1Uf+ucNNQzP3I9VCbA5FCWoauwQ6r25p4kxONP4Di/m+RWXV
LKn0h0sYyYigRdcqEW2QVoa510WLekCX3uEQUILiuqTvnpZWoNHJtdFOgA==
=/0PO
-----END PGP SIGNATURE-----