In some configurations of non-working networking, packman will hang a

very long time or forever retrieving the packages list. It's tricky to
test connectivity automatically, so ask every time.  Reported by
Stanislav Kapustin <kapustin_stanislav@hotmail.com>.

diff --git a/commands/scripts/packman.sh b/commands/scripts/packman.sh
index 71a21ab1236e3c7f16f97f15b6a656afab9c7019..8274da0083cf4c3d9e41e7d0bca5de5df2221fe4 100644 (file)
--- a/commands/scripts/packman.sh
+++ b/commands/scripts/packman.sh
@@ -127,13 +127,9 @@ rm -f $TMPDIR/.*   # Remove any remaining .postinstall script or .list*
 
 netpackages=""
 if ( : </dev/tcp ) 2>/dev/null
-then   if [ -f $LISTFILE ]
-       then    echo -n "Update package list from network? (Y/n) "
-               read y
-       else    echo "No package list found - retrieving initial version."
-               y=y
-       fi
-       if [ "$y" != n -a "$y" != n ]
+then   echo -n "Update package list from network? (Y/n) "
+       read y
+       if [ "$y" != n -a "$y" != N ]
        then    echo "Fetching package list from $LISTURL."
                urlget $LISTURL >$TMPF && mv $TMPF $LISTFILE || echo "Update not successful."
        fi