Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1539 mingw-get (upgrade): failed download does not revoke remove

closed-fixed
2011-05-20
2011-05-04
Keith Marshall
No

See original report by Chris Sutcliffe, at http://thread.gmane.org/gmane.comp.gnu.mingw.devel/4262

I found a bug in mingw-get in that if an upgrade fails to download,
mingw-get will still proceed with removing the package. Running
mingw-get-info I noticed that my w32api was out of date, so I did:

mingw-get update
mingw-get upgrade w32api

for some reason, mingw-get doesn't want to download the file (even
though the direct link works when I copied it to a browser):

mingw-get.exe: *** ERROR *** Get package:
http://prdownloads.sourceforge.net/mingw/w32api-3.17-2-mingw32-dev.tar.lzma?download:
download failed
mingw-get.exe: *** ERROR *** Get package:
http://prdownloads.sourceforge.net/mingw/w32api-3.17-2-mingw32-dev.tar.lzma?download:
download failed

The upgrade process proceed to remove the '-1' release and failed to
install the '-2' release because it failed to download.

Discussion

  • Keith Marshall
    Keith Marshall
    2011-05-08

    Replacement DLL file (compressed) for testing

     
    Attachments
  • Keith Marshall
    Keith Marshall
    2011-05-08

    Please test the attached replacement mingw-get-0.dll; it still doesn't check for possibly broken dependencies, but it should now refuse to remove an existing package during upgrade, if the replacement package failed to download, (and it should complain more appropriately when attempting to install a package which similarly failed to download). It should also correct the issue reported on ticket https://sourceforge.net/tracker/?func=detail&aid=3295526&group_id=2435&atid=102435

    Note that this build also attempts, more aggressively, to retry failing downloads. I've compiled it with fairly verbose tracing of internet requests. I'm undecided whether or not to leave it in this format for release, or to turn that option off and direct users here for the more verbose build, if they are willing to help with debugging. What do you think?

     
  • Keith Marshall
    Keith Marshall
    2011-05-20

    The problem you report has caused modification in some fashion in
    the official CVS for the given package. The w32api and
    mingw-runtime official CVS reside in the winsup CVS directory tree for Cygwin. Those package CVS trees are periodically merged into
    the MinGW CVS tree. If you still find problems then please open a
    new report.

     
  • Keith Marshall
    Keith Marshall
    2011-05-20

    • status: open --> closed-fixed