bugGNU Octave - Bugs: bug #56775, [octave forge] (symbolic) wrong...

 
 

bug #56775: [octave forge] (symbolic) wrong release version

Submitter:  Philip Nienhuis <philipnienhuis>
Submitted:  Sun 18 Aug 2019 08:59:51 PM UTC
   
 
Category:  Octave Package Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Incorrect Result
Status:  Works For Me Assigned to:  None
Originator Name:  Philip Nienhuis Open/Closed:  * Closed
Release:  * other Operating System:  * Other
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Sat 02 Nov 2019 12:24:36 PM UTC, comment #7: 

The texinfo for "Administrating packages" could use some attention.

E.g., par. 37.3 implies that "only?" on Unix it's possible to have both  global and local installs, but first of all I suppose that should be nix and secondly it *is possible on Windows as well, see this very bug report. I'm unsure about Mac OSX.
So I started trying to improve the text. Do we need a new bug or patch report for this?

I was wondering whether it could be useful to warn if global OF packages are/will be "shadowed", e.g. emitting a warning while installing a local package or when doing a "pkg rebuild" or even "pkg list".

Philip Nienhuis <philipnienhuis>
Group Member
Wed 21 Aug 2019 07:48:57 PM UTC, comment #6: 

A doc fix can help, yes. I'll try to pick it up.

Philip Nienhuis <philipnienhuis>
Group Member
Tue 20 Aug 2019 10:23:48 PM UTC, comment #5: 

Yes, its existence documented in the pkg documentation. It's possible that the precedence between the "global" and "local" package lists is not documented.

If you want to turn this into that, improving the documentation of the internal configuration details of the pkg command, go ahead. Otherwise we can close this as not-a-bug.

Mike Miller <mtmiller>
Group Member
Tue 20 Aug 2019 10:14:12 PM UTC, comment #4: 

Found it.

In my profile there was a old .octave_packages file including a reference to symbolic-2.7.1. Wiping that and doing "pkg rebuild" solved the issue.
No idea how that .octave_packages file got there. It didn't get overwritten by "pkg rebuild".
Am I correct to figure that the authorative octave-packages file would be the one in share/octave ? If I'm wrong, is it documented that an .octave_packages file in a user profile overrules the one in share/octave?

Philip Nienhuis <philipnienhuis>
Group Member
Tue 20 Aug 2019 09:37:51 PM UTC, comment #3: 

To add to the confusion (for me), in octave_packages I see:


# name: dir
# type: sq_string
# elements: 1
# length: 76
C:\Programs\Octave\OCTAVE~1.0_2\mingw64\share\octave\packages\symbolic-2.8.0


# name: archprefix
# type: sq_string
# elements: 1
# length: 74
C:\Programs\Octave\OCTAVE~1.0_2\mingw64\lib\octave\packages\symbolic-2.8.0


yet pkg list stubbornly insists I have 2.7.1. Go figure

Philip Nienhuis <philipnienhuis>
Group Member
Tue 20 Aug 2019 09:34:51 PM UTC, comment #2: 

@Mike:
That's where I got it from.
But I found a clue: "pkg list" shows that I have 2.7.1 installed locally, and apparently that shadows 2.8.0 that is included in my mxe build.
Intriguingly, in the "local" subdir in my profile there's no symbolic-2.7.1 to be found.
"pkg uninstall" mentions:

>> pkg uninstall symbolic
warning: directory C:\Users\philip\octave\symbolic-2.7.1 previously lost
warning: called from
    uninstall at line 130 column 9
    pkg at line 490 column 7
>> pkg rebuild
>> pkg list symbolic
Package Name  | Version | Installation directory
--------------+---------+-----------------------
    symbolic  |   2.7.1 | C:\Users\philip\octave\symbolic-2.7.1
>>


It looks like "pkg" is seriously confused, but I'm at loss where to look further.
Deleting octave-packages in share/octave/ doesn't help.




Philip Nienhuis <philipnienhuis>
Group Member
Tue 20 Aug 2019 07:44:22 PM UTC, comment #1: 

Where did you get "octsympy-win-bundle-2.8.0.tar.gz" from? Is it possible you are looking at an out-of-date local build?

The official release can be found at https://github.com/cbm755/octsympy/releases, is named "symbolic-win-py-bundle-2.8.0.tar.gz", and the version in the DESCRIPTION file is 2.8.0.

Mike Miller <mtmiller>
Group Member
Sun 18 Aug 2019 08:59:51 PM UTC, original submission:  

A cosmetic issue

Don't know if this has already been reported, didn't find it when searching.

After installing octsympy-win-bundle-2.8.0.tar.gz, "pkg list" reports version 2.7.1 rather than 2.8.0.

Philip Nienhuis <philipnienhuis>
Group Member

 

(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 philipnienhuis (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
    2019-09-09 mtmiller Open/ClosedOpen Closed
    2019-08-20 mtmiller StatusNone Works For Me

    Back to the top

    Powered by Savane 3.13-d3ae.
    Corresponding source code