Bug 1638863 - scala: FTBFS in Fedora rawhide
Summary: scala: FTBFS in Fedora rawhide
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: scala
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mikolaj Izdebski
QA Contact: Fedora Extras Quality Assurance
URL: http://apps.fedoraproject.org/koschei...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-12 16:16 UTC by Mikolaj Izdebski
Modified: 2020-11-24 20:24 UTC (History)
4 users (show)

Fixed In Version: scala-2.10.6-14.fc29 scala-2.10.6-14.fc30
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-24 20:24:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Comment 1 Mikolaj Izdebski 2018-10-12 18:17:30 UTC
Description of problem:
Package scala fails to build from source in Fedora rawhide.
The reason is that scaladoc is not usable at all - whenever invoked it crashes with java.lang.AssertionError

The purpose of scaladoc tool is generating documentation from code written in Scala. Documentation generated with scaladoc is in HTML format and it includes assets such as CSS and JavaScript code, which are copied from resources included in scala package. The crash of scaladoc toos (assertion failure) is caused by a fix for bug #1609878 - resources that scaladoc includes in generated docs were removed. We originally thought that these resources were not used by scala during runtime, but it turned out to be false assumption.

I've re-analyed whether we can re-add or somehow replace removed resources that were removed. Some .js files look like source code and therefore could be re-added: diagrams.js index.js jquery.layout.js scheduler.js template.js. But the following files are more problematic:

jquery.js (jQuery v1.8.2) - it is packaged as 3 packages (js-jquery1, js-jquery2, js-jquery3), but js-jquery1 is orphaned and will probably be retired soon. I don't want to maintain jQuery build.

jquery-ui.js - jQuery UI v1.9.0, compiled/minified code from https://jqueryui.com/. I've been unable to find source code on upstream site - it looks like they are just combining together compiled code from other libraries.

modernizr.custom.js - Modernizr 2.5.3 (Custom Build) containing just inlinesvg module; source code is available, but it can't be used without building it

raphael-min.js - Raphaël 2.1.0 - JavaScript Vector Library, seems to be included in sources, but not used by anything; therefore I believe it could be simply removed

tools.tooltip.js - tools.tooltip 1.1.3, upstream page http://flowplayer.org/tools/tooltip.html is no longer available.

These files can't be re-added as they are in non-source form and we cannot ship prebuilt object code to users. But replacing these files would be a major work, for which we don't have capacity.

Therefore I am going to make scaladoc generate documentation without problematic resources. Documentation generated this way may be less usable compared to docs generated with upstream Scala.

Version-Release number of selected component (if applicable):
2.10.6-11.fc29

Steps to Reproduce:
koji build --scratch f30 scala-2.10.6-11.fc29.src.rpm

Additional info:
This package is tracked by Koschei. See:
http://apps.fedoraproject.org/koschei/package/scala

Comment 2 Mikolaj Izdebski 2018-10-12 18:19:39 UTC
Should be fixed in scala >= 2.10.6-13
https://koji.fedoraproject.org/koji/taskinfo?taskID=30191734

Comment 3 Mikolaj Izdebski 2018-10-12 19:11:54 UTC
Steps to Reproduce:
1. dnf -y install scala
2. echo 'object HelloWorld { def main(args: Array[String]): Unit = { println("Hello, world!") } }' >HelloWorld.scala
3. scaladoc HelloWorld.scala

Actual results:
Exception in thread "main" java.lang.AssertionError: assertion failed: /scala/tools/nsc/doc/html/resource/lib/index.js

Expected results:
No crash. Documentation files are generated in current directory: HelloWorld$.html, index.html, package.html

Comment 4 Fedora Update System 2018-10-12 19:28:04 UTC
scala-2.10.6-14.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2018-425db0f4b6

Comment 5 Fedora Update System 2018-10-13 21:30:58 UTC
scala-2.10.6-14.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-425db0f4b6

Comment 6 Fedora Update System 2018-10-30 17:26:21 UTC
scala-2.10.6-14.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 xg16497 2019-03-01 08:08:46 UTC
(In reply to Fedora Update System from comment #6)
> scala-2.10.6-14.fc29 has been pushed to the Fedora 29 stable repository. If
> problems still persist, please make note of it in this bug report.

There's still the problem that [scaladoc] java.lang.AssertionError: assertion failed: /scala/tools/nsc/doc/html/resource/lib/index.js
Is this the problem of index.js?

Comment 8 xg16497 2019-03-01 08:25:33 UTC
(In reply to xg16497 from comment #7)
> (In reply to Fedora Update System from comment #6)
> > scala-2.10.6-14.fc29 has been pushed to the Fedora 29 stable repository. If
> > problems still persist, please make note of it in this bug report.
> 
> There's still the problem that [scaladoc] java.lang.AssertionError:
> assertion failed: /scala/tools/nsc/doc/html/resource/lib/index.js
> Is this the problem of index.js?

The version is scala-2.10.6-14.fc29

Comment 9 Mikolaj Izdebski 2019-04-09 18:51:24 UTC
(In reply to xg16497 from comment #7)
> There's still the problem that [scaladoc] java.lang.AssertionError:
> assertion failed: /scala/tools/nsc/doc/html/resource/lib/index.js
> Is this the problem of index.js?

I believe this problem should already be fixed. Can you still reproduce it with current latest scala package version?

Comment 10 Ben Cotton 2019-08-13 16:50:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 11 Ben Cotton 2019-08-13 19:28:23 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 12 Ben Cotton 2020-11-03 15:03:16 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 13 Ben Cotton 2020-11-24 20:24:36 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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