bugGNU Octave - Bugs: bug #36515, pkg unload does not consider...

 
 

bug #36515: pkg unload does not consider dependencies

Submitter:  Carnë Draug <carandraug>
Submitted:  Mon 21 May 2012 11:39:09 AM UTC
   
 
Category:  Octave Function Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Incorrect Result
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * dev Operating System:  * Any
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Sun 01 Aug 2021 08:48:43 PM UTC, comment #4: 

This has been fixed some time ago with bug #57522.
I'm sorry I didn't find this bug report here.

Closing as fixed.

Philip Nienhuis <philipnienhuis>
Group Member
Thu 24 Nov 2016 12:49:47 AM UTC, comment #3: 

It's actually this that I think this bug is originally about:


pkg load signal
pkg unload control
## signal is still loaded and in the path


This does still affect Octave 4.2 and 4.3-dev.

The reverse would be nice, but would involve keeping track of which packages were explicitly loaded by the user and which were loaded indirectly (as Carnë describes in comment #1).

Mike Miller <mtmiller>
Group Member
Thu 24 Nov 2016 12:39:55 AM UTC, comment #2: 

Problem is still present in 4.3.0+
Testing with singal package that loads control


pkg load signal
pkg list # check control is loaded
pkg unload signal
pkg list # control is still loaded


Juan Pablo Carbajal <juanpi>
Group Member
Tue 12 Apr 2016 12:00:36 PM UTC, comment #1: 

A better solution might be to keep track of why packages were loaded (directly or as dependency), and unload them when there's no reason left to keep them.

Carnë Draug <carandraug>
Group Member
Mon 21 May 2012 11:39:09 AM UTC, original submission:  

Hi

when a package that is a dependency of others is unloaded, no warning is given and the other packages stay loaded which can lead to problems with them.

I'd imagine the following possible behaviors:

1) do not unload the package and issue a warning about the reason why
2) unload the package together with all packages that depend on it and issue a warning about it
3) unload only the selected package (current behaviour) but I think this should be the behaviour if selecting unload with the -nodeps flag

What should be the best way to handle this? I have attached two empty packages that simply depend on each other to test this things.

Carnë

Carnë Draug <carandraug>
Group Member

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #25897:  ori1-1.0.0.tar.gz added by carandraug (370B - application/x-gzip)
file #25898:  ori2-1.0.0.tar.gz added by carandraug (370B - application/x-gzip)

 

Digest:
   bug dependencies.

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mmuetzel (Updated the item)
  • -email is unavailable- added by juanpi (Posted a comment)
  • -email is unavailable- added by mtmiller (Updated the item)
  • -email is unavailable- added by carandraug (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 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2021-08-02 mmuetzel StatusConfirmed Fixed
        Open/ClosedOpen Closed
        Dependencies- Depends on bugs #57522
    2013-10-28 mtmiller CategoryNone Octave Function
        Item GroupNone Incorrect Result
        StatusNone Confirmed
    2012-05-21 carandraug Attached File- Added ori1-1.0.0.tar.gz, #25897
        Attached File- Added ori2-1.0.0.tar.gz, #25898

    Back to the top

    Powered by Savane 3.13-3230.
    Corresponding source code