Bug 357371 - In emerge\portage\dev-util\cmake\cmake.py, the regular expression fails to grab the nightly cmake version, resulting in index out of range exception
Summary: In emerge\portage\dev-util\cmake\cmake.py, the regular expression fails to gr...
Status: RESOLVED WORKSFORME
Alias: None
Product: kde-windows
Classification: Miscellaneous
Component: buildsystem (show other bugs)
Version: unspecified
Platform: Microsoft Windows Microsoft Windows
: NOR crash
Target Milestone: ---
Assignee: Alexander Neundorf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-31 16:10 UTC by Jordan Bray
Modified: 2018-12-01 03:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jordan Bray 2015-12-31 16:10:49 UTC
In emerge\portage\dev-util\cmake\cmake.py, the funciton setTargets(self) attempts to grab the latest nightly version of cmake.  I'm not sure when, as I was able to successfully run emerge for a while before it broke on me.  However, at some port, the setTargets will be called, and it will crash on line 15.

The offending line is:

nightlyVer = utils.getNightlyVersionsFromUrl(nightlyUrl + "?C=M;O=D", "\d.\d.\d\d\d\d\d\d\d\d-[0-9A-Za-z]{7}")

Which, as far as I can tell, grabs the list of cmake versions as an HTML document, then extracts the version info with the above regular expression.  However, as you can see from the current latest version (3.4.20151120-g20f70), it does not work because of the {7} at the end.  I switched mine over to a {6-7} and that seems to have resolved the issue.

I'm not sure if they recently changed the format of the versions, or if this function just isn't called that much.  I would commit it myself, but I'm not sure how or where...

Thanks.


Reproducible: Sometimes

Steps to Reproduce:
1. Run emerge (anything) while building on windows.  It does not matter if the package exists or not.


Actual Results:  
List Index Out Of Range Exception

Expected Results:  
Compile a package
Comment 1 Andrew Crouthamel 2018-11-01 13:42:37 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Bug Janitor Service 2018-11-16 11:37:35 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-12-01 03:51:33 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!