octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55143] pkg install only succeeds on second at


From: Hartmut
Subject: [Octave-bug-tracker] [bug #55143] pkg install only succeeds on second attempt (Windows only)
Date: Sat, 1 Dec 2018 14:22:34 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0

Follow-up Comment #4, bug #55143 (project octave):

I've tested Philip's suggestion from comment #3 on Win7, and yes, it works
fine just on the first go, then:


>> pkg load image %ver 2.8.1
>> imdilate(eye(3),ones(2))
ans =

   1   1   0
   1   1   1
   0   1   1

>> pkg unload image
>> clear -f
>> pkg uninstall image
>> pkg install image-2.8.1.tar.gz
For information about changes from previous versions of the image package, run
'news image'.
>>


To recap: on Win7 we got unwanted behavior when I tried to upgrade a package
that was already LOADED (I am pretty sure that I did not call any function
from the package, yet.)

I've also tested the behavior under Linux (Ubuntu 18.04, Octave 4.4.1
release)
* upgrade a (image) package that was currently unloaded
* upgrade a (image) packagae that was currently loaded
* upgrade a (image) package that was currently loaded and had already called a
binary function from this package

I couldn't observe ANY unwanted behavior with Linux with all those ways to
upgrade a package. So the Windows version of pkg seems to be much less
tolerant in those circumstances compared to the Linux version.

Here is an example what works fine under Linux:


>> pkg load image
>> pkg list
Package Name  | Version | Installation directory
--------------+---------+-----------------------
       image *|   2.8.0 | /home/hartmut/octave/image-2.8.0
>> imdilate(eye(3),ones(2));
>> pkg install image-2.8.1.tar.gz
For information about changes from previous versions of the image package, run
'news image'.
>>




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?55143>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]