bugGNU Octave - Bugs: bug #59054, [MXE Octave] Can't build current...

 
 

bug #59054: [MXE Octave] Can't build current octave-stable

Submitter:  Markus Mützel <mmuetzel>
Submitted:  Wed 02 Sep 2020 11:36:01 AM UTC
   
 
Category:  Configuration and Build System Severity:  3 - Normal
Priority:  5 - Normal Item Group:  None
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * 6.0.90 Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Wed 02 Sep 2020 03:11:15 PM UTC, comment #3: 

Thanks for the quick fix. That looks good to me.
With that logic, an even number (including 0) at the third position of the version number indicates that it is an "official" release or release candidate. And an odd number indicates that it is an "un-official" build from the stabilization period between "official" versions. That makes sense to me.

Closing as fixed.

Markus Mützel <mmuetzel>
Group administrator
Wed 02 Sep 2020 03:00:08 PM UTC, comment #2: 

I pushed my proposed changes and an update to stable-octave.mk in mxe-octave.  I'm still open to other ideas.  Otherwise, please close this report as fixed if you agree my solution is OK.  Thanks.

John W. Eaton <jwe>
Group administrator
Wed 02 Sep 2020 02:23:07 PM UTC, comment #1: 

Oops.

I propose the following change to the process of handling version numbers during the time when we are making release candidates:


diff --git a/etc/HACKING.md b/etc/HACKING.md
--- a/etc/HACKING.md
+++ b/etc/HACKING.md
@@ -307,6 +307,7 @@ Since version 5, Octave uses the followi
   5.0.0   (experimental)  active development of Octave 5 on default branch
   5.0.1   (pre-release)   stabilization period of Octave 5 on stable branch
   5.0.90  (pre-release)   first release candidate for 5.1.0
+  5.0.91  (pre-release)   continued stabilization of Octave 5 on stable branch
   6.0.0   (experimental)  active development of Octave 6 on default branch
   5.1.0   (release)       first release of Octave 5 from stable branch
   5.1.1   (pre-release)   bug fixing on stable branch after 5.1.0 release
@@ -326,7 +327,9 @@ With this numbering scheme:
   * Any version X.Y.Z with Z > 0 means, "this is a pre-release version
     meant for bug fixing and testing".  In practice, Z will be either 1
     (stabilization period after and before making release candidates) or
-    90, 91, etc. (release candidate snapshots leading up to release).
+    90, 92, etc. (release candidate snapshots leading up to release).
+    91, 93, etc. (stabilization period on stable branch during the
+    process of making release candidates).

   * Any version X.Y.0 with Y != 0 means "this is a released version".


This method requires updating the release-octave.mk and stable-octave.mk files in mxe-octave for each release candidate.

The other alternative I see would be to set the stable branch version back to X.Y.1 (in the current case, 6.0.1).  Then we would only need to update the release-octave.mk file for mxe-octave, but it seems bad to me to have the version number jumping backward after every release candidate snapshot.

John W. Eaton <jwe>
Group administrator
Wed 02 Sep 2020 11:36:01 AM UTC, original submission:  

It's currently not possible to compile Octave from the stable branch with MXE Octave.
If MXE Octave is configured with "--enable-octave=stable" it still downloads the sources of the release candidate from alpha.gnu.org:

[download] octave-6.0.90.tar.lz
[build]    stable-octave


The existing source tarball with the stable source is overwritten by that download because it has the same name.
The corresponding log file is named "release-octave-download".

The buildbots seem to have the same issue (i.e., the release and stable buildbots are building the release candidate).

Markus Mützel <mmuetzel>
Group administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by mmuetzel (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-09-02 mmuetzel StatusNone Fixed
        Open/ClosedOpen Closed

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code