[Octave-bug-tracker] [bug #47405] pkg update errors out of one package sees dependency error

[Nicholas Jankowski]

URL:
  <http://savannah.gnu.org/bugs/?47405>

                 Summary: pkg update errors out of one package sees dependency
error
                 Project: GNU Octave
            Submitted by: nrjank
            Submitted on: Mon 14 Mar 2016 03:22:21 AM GMT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Installation Failure
                  Status: None
             Assigned to: None
         Originator Name: Nicholas Jankowski
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

When running 'pkg update' it appears to work through the packages in some
particular order (alphabetical order, or install order) When one of the
packages has a dependency on a version of a package that has not been updated
yet, pkg errors out back to the command line and does not continue checking
any other packages for updates.

This can be seen in the windows version of 4.0.0 where the default package set
is a bit out of date. Running the build_packages script followed by pkg update
gives the following error:

error: the following dependencies were unsatisfied:
> >    optim needs struct >= 1.0.12


And pkg update cannot proceed to other packages until struct is done first.
While this is not difficult to do, it may be confusing for a new user.

I would think the simplest solution would be for package to somehow catch the
error and step over that package. Then running the update twice would result
in everything being fully updated. Perhaps if it needed to step over a package
it could tell the user he should probably rerun the update.

Alternatively it would be nice if it would just recognize that it had to step
over one of the packages and to try it again at the end. If it failed again
and could tell the user.

Really nice would be for it to recognize which package is needed, if it is
already installed run that update first, if it's not installed ask the user
whether it should be installed, and then after the dependency has been
satisfied pick up the update process where it left off.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47405>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/