apt-cyg fails with /setup.ini: Scheme missing message

[GoogleCodeExporter]

Previously apt-cyg worked without problems, today I get this error:

$ LANG=C apt-cyg update
Working directory is /setup
Mirror is
/setup.bz2: Scheme missing.
/setup.ini: Scheme missing.
Error updating setup.ini, reverting
$

Here some informations:

$ apt-cyg --version
apt-cyg version 0.57
$ uname -a
CYGWIN_NT-6.1-WOW64 PcMorgan-PC 1.7.20(0.266/5/3) 2013-06-07 11:11 i686 Cygwin

Original issue reported on code.google.com by desantis...@gmail.com on 12 Jun 2013 at 8:39

• Merged into: #21

[GoogleCodeExporter]

As of 2013-08-08 support for setup.exe has been dropped.
The location of setup.ini has been changed to reflect x86 and x86_64 
installations.
You must use setup-x86.exe or setup-x86_64.exe instead for installing or 
updating.

As a result, apt-cyg is now broken

In the getsetup() function beginning on line 92 it attempts to wget setup info 
in 2 places.

Line #98 - wget -N $mirror/setup.bz2
Line #105 - wget -N $mirror/setup.ini

These paths need to be changed to reflect the new location of the setup files.

Line #98 - wget -N $mirror/x86/setup.bz2
Line #105 - wget -N $mirror/x86/setup.ini

or (untested)

Line #98 - wget -N $mirror/x86_64/setup.bz2
Line #105 - wget -N $mirror/x86_64/setup.ini

Notes:
0> I too am running apt-cyg version 0.57
1> apt-cyg is a bash script file so you can easily change it with any text 
editor (no need to compile).
2> I replaced setup.exe with setup-x86.exe since the path to cygwin's root 
directory was the same and when I tried setup-x86_64 it showed a different path.
3> This is the reason I selected the /x86/ path (that worked).
4> I have not tried the /x86_64/ path but perhaps if you install using 
setup-x86_64.exe you should use the /x86_64/ path to setup.XXX
5> I got these paths by watching setup-x86.exe as it loaded setup.ini

Original comment by Cyber...@gmail.com on 9 Aug 2013 at 8:41

[GoogleCodeExporter]

I have tested using:
Line #98 - wget -N $mirror/x86_64/setup.bz2
Line #105 - wget -N $mirror/x86_64/setup.ini

and it works.

Original comment by matt...@natalier.com on 21 Aug 2013 at 11:55

[GoogleCodeExporter]

I have verified the fix on my end as well, thanks for figuring this out!

Line #98 - wget -N $mirror/x86_64/setup.bz2
Line #105 - wget -N $mirror/x86_64/setup.ini

Original comment by calvin.d...@gmail.com on 7 Sep 2013 at 5:40

[GoogleCodeExporter]

i had 2 problems with apt-cyg:
1) error updating setup.ini
2) tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors

for problem 1):
see: http://code.google.com/p/apt-cyg/issues/detail?id=23
solution:
  wget http://apt-cyg.googlecode.com/svn/trunk/apt-cyg
  sed -e 's%wget -N \$mirror/%&x86/%' -i apt-cyg #http://code.google.com/p/apt-cyg/issues/detail?id=23

then for problem 2), i wrote a patch.
if you need to install patch.exe, do this first: 
/cygdrive/c/utils/cygwin32/setup-x86.exe -P 
wget,tar,qawk,bzip2,subversion,vim,patch
then apply my patch like this (just copy paste in the terminal):
patch -p0 <<"EOF"
--- apt-cyg     2013-11-03 15:30:45.698629600 +0100
+++ /usr/local/bin/apt-cyg      2013-11-03 14:57:10.822790100 +0100
@@ -350,7 +350,22 @@
     fi

     echo "Unpacking..."
-    cat $file | bunzip2 | tar > "/etc/setup/$pkg.lst" xvf - -C /
+#changed by francois scheurer
+#    cat $file | bunzip2 | tar > "/etc/setup/$pkg.lst" xvf - -C /
+    #case $(echo "$file" | gawk -F. '{print $NF}') in
+    case "${file##*.}" in
+    bz2)
+      tar xjf "$file" -C / >"/etc/setup/$pkg.lst"
+      ;;
+    xz)
+      tar xJf "$file" -C / >"/etc/setup/$pkg.lst"
+      ;;
+    *)
+      echo "error: unknown extension in file $file, cannot extract with tar!"
+      exit 1
+      ;;
+    esac
+#endof
     gzip -f "/etc/setup/$pkg.lst"
     cd ../..

EOF

and finally install the patched apt-cyg:
  chmod +x apt-cyg
  mv -vi apt-cyg /usr/local/bin/

cheers
Francois Scheurer 
^^

Original comment by franc...@synways.com on 3 Nov 2013 at 3:48

[GoogleCodeExporter]

Greeting Francois!
Thanks a lot! :-)

Original comment by itan...@gmail.com on 5 Nov 2013 at 8:17

[GoogleCodeExporter]

thanks, worked!

Original comment by br...@e-guerrillas.nl on 18 Jan 2014 at 3:37

[GoogleCodeExporter]

Original comment by i...@skl.me on 17 Feb 2014 at 8:54

• Changed state: Duplicate