Re: Troubles with opkg.org repo
On Thu, Mar 12, 2009 at 7:51 AM, Joel Newkirk freerun...@newkirk.us wrote: On Sun, 8 Mar 2009 15:05:10 +0100 Thomas Zimmermann zimmerm...@vdm-design.de wrote: Additionally there are a lot of Packages that don't contain a control file with depencies and so on: Form the packages in debian format are these: 0_tshark_1.0.99+svnr26030_armv4t.ipk 0_wireshark-common_1.0.99+svnr26030_armv4t.ipk 1_wireshark_1.0.99+svnr26030_armv4t.ipk So if the authors of these packages can update them that would be great. I contributed those three - sorry, I hadn't noticed they were in your list. Strange, I downloaded the files from opkg.org and they are significantly smaller than the originals I uploaded. They contain the beginnings of the correct data, specifically debian-binary and the start of data.tar.gz, but are truncated. The tshark package, eg, is supposed to be 106606 bytes, but the download from opkg.org is only 65536 bytes. In fact, all three are truncated to powers of two as well - multiples of 4096 bytes... I'll try resubmitting them yet again, though not until tomorrow. (I'm off to bed) Clearly the files are getting broken at some point in the process, I'll try to rule out upload. Thanks for uploading them again. I hope uploading again helps but I have the feeling that it's something else, or that the upload fails for some reason and it has really nothing to do with your actions.. Let's see if the scripts get fixed at some point. r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Troubles with opkg.org repo
On Thu, 12 Mar 2009 08:05:03 +0200 Risto H. Kurppa ri...@kurppa.fi wrote: On Thu, Mar 12, 2009 at 7:51 AM, Joel Newkirk freerun...@newkirk.us wrote: On Sun, 8 Mar 2009 15:05:10 +0100 Thomas Zimmermann zimmerm...@vdm-design.de wrote: Additionally there are a lot of Packages that don't contain a control file with depencies and so on: Form the packages in debian format are these: 0_tshark_1.0.99+svnr26030_armv4t.ipk 0_wireshark-common_1.0.99+svnr26030_armv4t.ipk 1_wireshark_1.0.99+svnr26030_armv4t.ipk So if the authors of these packages can update them that would be great. I contributed those three - sorry, I hadn't noticed they were in your list. Strange, I downloaded the files from opkg.org and they are significantly smaller than the originals I uploaded. They contain the beginnings of the correct data, specifically debian-binary and the start of data.tar.gz, but are truncated. The tshark package, eg, is supposed to be 106606 bytes, but the download from opkg.org is only 65536 bytes. In fact, all three are truncated to powers of two as well - multiples of 4096 bytes... I'll try resubmitting them yet again, though not until tomorrow. (I'm off to bed) Clearly the files are getting broken at some point in the process, I'll try to rule out upload. Thanks for uploading them again. I hope uploading again helps but I have the feeling that it's something else, or that the upload fails for some reason and it has really nothing to do with your actions.. Let's see if the scripts get fixed at some point. r I uploaded them again, then re-downloaded to be sure - as of right now, at least, they are correct and intact. Uploaded the same files, from the same desktop machine, with the same browser. :( j ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Troubles with opkg.org repo
On Sun, 8 Mar 2009 15:05:10 +0100 Thomas Zimmermann zimmerm...@vdm-design.de wrote: Additionally there are a lot of Packages that don't contain a control file with depencies and so on: Form the packages in debian format are these: 0_tshark_1.0.99+svnr26030_armv4t.ipk 0_wireshark-common_1.0.99+svnr26030_armv4t.ipk 1_wireshark_1.0.99+svnr26030_armv4t.ipk So if the authors of these packages can update them that would be great. I contributed those three - sorry, I hadn't noticed they were in your list. Strange, I downloaded the files from opkg.org and they are significantly smaller than the originals I uploaded. They contain the beginnings of the correct data, specifically debian-binary and the start of data.tar.gz, but are truncated. The tshark package, eg, is supposed to be 106606 bytes, but the download from opkg.org is only 65536 bytes. In fact, all three are truncated to powers of two as well - multiples of 4096 bytes... I'll try resubmitting them yet again, though not until tomorrow. (I'm off to bed) Clearly the files are getting broken at some point in the process, I'll try to rule out upload. j ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Troubles with opkg.org repo
Hi, Tobias Kündig wrote: This is a little summary of what I do: http://www.opkg.org/repo.html I suggest changing the line (http://www.opkg.org/create_repo.txt) cat control|grep -ve \/^[:space:]*$/\ Packages to cat control | grep -v ^[ ]*$ Packages Greets, Zaptac -- View this message in context: http://n2.nabble.com/Troubles-with-opkg.org-repo-tp2434780p2448399.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Troubles with opkg.org repo
On Sun, 8 Mar 2009 15:30:36 +0200
Risto H. Kurppa ri...@kurppa.fi wrote:
On Sat, Mar 7, 2009 at 10:09 AM, Tobias Kündig
tobias.kuen...@gmail.com wrote:
This is a little summary of what I do: http://www.opkg.org/repo.html
Thanks Tobias!
At #openmoko tried to figure out what's wrong. Someone pointed out
that ftp uses ascii mode by default - I suppose you're uploading at
least the Packages -ascii file. How about packages.gz. Man ftp says
that ascii upload of binary files might corrupt it - this might be
the problem - using binary format shouldn't corrupt the .gz
Another find was that 22 packages out of 93 were other than Debian
Binary when checked with file *ipk. The list file types listed below:
DEBIAN BINARY – CORRECT!!!
{snipped package names}
DATA
EMPTY
GZIP
So things seem to fail because:
- Empty file is an empty file, not much to discuss about that. Only
need to find out the reason for that: did the authors really upload an
empty package or did the upload fail but an empty file was created?
Nothing to add here.
- ar isn't able to extract gzip files so all files recognized as gzip
will not get listed properly in the Packages file. Again the reason
for the wrong file type should be found: did the packages package it
wrong or did the type/mime/something get corrupted along the way,
during the upload or on the server?
It is perfectly acceptable for an ipk to be a tarball (.tar.gz) instead
of an ar archive. 'opkg install' happily works with them. So the
'fix' needs to be in create_repo.
j
{!!untested!!}
#!/bin/sh
cd /root/opkg.org/packages/
echo -n Packages
for file in `ls -1 *.ipk *.opk`; do
echo $file
sum=`md5sum $file | awk '{print $1}'`
pkgtype=`file $file | cut -d' ' -f2`
case $pkgtype in
Debian)
ar x $file control.tar.gz
tar xzf ./control.tar.gz ./control
cat control|grep -e [:alnum:] Packages
echo Filename: $file Packages
echo MD5Sum: $sum Packages
echo Packages
echo Packages
rm
-f /root/opkg.org/packages/control.tar.gz /root/opkg.org/packages/control
;;
gzip)
tar xzf $file ./control.tar.gz
tar xzf ./control.tar.gz ./control
cat control|grep -e [:alnum:] Packages
echo Filename: $file Packages
echo MD5Sum: $sum Packages
echo Packages
echo Packages
rm
-f /root/opkg.org/packages/control.tar.gz /root/opkg.org/packages/control
;;
*)
echo Problem extracting $file
;;
esac
done
gzip -c /root/opkg.org/packages/Packages
/root/opkg.org/packages/Packages.gz
#Upload
ftp -v -n ftp.opkg.org /root/opkg.org/ftp2.input
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Troubles with opkg.org repo
On Sun, 8 Mar 2009 15:30:36 +0200
Risto H. Kurppa ri...@kurppa.fi wrote:
On Sat, Mar 7, 2009 at 10:09 AM, Tobias Kündig
tobias.kuen...@gmail.com wrote:
This is a little summary of what I do: http://www.opkg.org/repo.html
Thanks Tobias!
At #openmoko tried to figure out what's wrong. Someone pointed out
that ftp uses ascii mode by default - I suppose you're uploading at
least the Packages -ascii file. How about packages.gz. Man ftp says
that ascii upload of binary files might corrupt it - this might be
the problem - using binary format shouldn't corrupt the .gz
Another find was that 22 packages out of 93 were other than Debian
Binary when checked with file *ipk. The list file types listed below:
DEBIAN BINARY – CORRECT!!!
{snipped package names}
DATA
EMPTY
GZIP
So things seem to fail because:
- Empty file is an empty file, not much to discuss about that. Only
need to find out the reason for that: did the authors really upload an
empty package or did the upload fail but an empty file was created?
Nothing to add here.
- ar isn't able to extract gzip files so all files recognized as gzip
will not get listed properly in the Packages file. Again the reason
for the wrong file type should be found: did the packages package it
wrong or did the type/mime/something get corrupted along the way,
during the upload or on the server?
It is perfectly acceptable for an ipk to be a tarball (.tar.gz) instead
of an ar archive. 'opkg install' happily works with them. So the
'fix' needs to be in create_repo.
j
{!!untested!!}
#!/bin/sh
cd /root/opkg.org/packages/
echo -n Packages
for file in `ls -1 *.ipk *.opk`; do
echo $file
sum=`md5sum $file | awk '{print $1}'`
pkgtype=`file $file | cut -d' ' -f2`
case $pkgtype in
Debian)
ar x $file control.tar.gz
tar xzf ./control.tar.gz ./control
cat control|grep -e [:alnum:] Packages
echo Filename: $file Packages
echo MD5Sum: $sum Packages
echo Packages
echo Packages
rm
-f /root/opkg.org/packages/control.tar.gz /root/opkg.org/packages/control
;;
gzip)
tar xzf $file ./control.tar.gz
tar xzf ./control.tar.gz ./control
cat control|grep -e [:alnum:] Packages
echo Filename: $file Packages
echo MD5Sum: $sum Packages
echo Packages
echo Packages
rm
-f /root/opkg.org/packages/control.tar.gz /root/opkg.org/packages/control
;;
*)
echo Problem extracting $file
;;
esac
done
gzip -c /root/opkg.org/packages/Packages
/root/opkg.org/packages/Packages.gz
#Upload
ftp -v -n ftp.opkg.org /root/opkg.org/ftp2.input
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: Troubles with opkg.org repo
On Sat, Mar 7, 2009 at 10:09 AM, Tobias Kündig tobias.kuen...@gmail.com wrote: This is a little summary of what I do: http://www.opkg.org/repo.html Thanks Tobias! At #openmoko tried to figure out what's wrong. Someone pointed out that ftp uses ascii mode by default - I suppose you're uploading at least the Packages -ascii file. How about packages.gz. Man ftp says that ascii upload of binary files might corrupt it - this might be the problem - using binary format shouldn't corrupt the .gz Another find was that 22 packages out of 93 were other than Debian Binary when checked with file *ipk. The list file types listed below: DEBIAN BINARY – CORRECT!!! neon_0.9.8-r1_all.ipk openmoocow_0.3_armv4t.ipk nethack_3.4.3-10.1-0.4_armv4t.ipk openmiaocat_0.2.2_armv4t.ipk orrery_2.4_arm_2008.8.ipk pyring_1.1.6-r1_armv4t.ipk python-pyalsaaudio_0.3-ml0_armv4t.ipk perpendicular_0.1_armv4t.ipk pong_0.1_armv4t.ipk liquidwar_5.6.4-2_armv4t.ipk moko-eightball_0.20080721_om-gta02.ipk mokogeocaching_0.2_all.ipk meooem_0.1_armv4t.ipk minimo_0.02+cvs20070626-r1_armv4t.ipk mokomaze_0.2.2-1_armv4t.ipk mokox48_1.0_arm_2008.8.ipk mutagen_svn-4350-2_armv4t.ipk mokopod_0.1.5_armv4t.ipk mokosync_0.1_arm.ipk tangogps_0.9.6-r0_armv4t.ipk wicd_1.5.6_armv4t.ipk wlan_0.3_arm.ipk tor-0.2.0.34_0.1_armv4t.ipk usbmode-button_0.3_armv4t.ipk xmahjongg-3.7_0.2_armv4t.ipk zinnia-tomoe-ja_0.6.0-20080911_armv4t.ipk zinnia-tomoe-zh_0.6.0-20080911_armv4t.ipk zedlock_0.1_armv4t.ipk zinnia_0.02_armv4t.ipk pytomboy_0.1_armv4t.ipk remoko-server_0.2.1_svnr119-r0_armv4t.ipk rotate_0.0.2_armv4t.ipk qwo_0.4_armv4t.ipk remoko_0.3.2_armv4t.ipk rotator_0.1_all.ipk sms-sentry_1.0-r0_armv4t.ipk swedish-illume_0.1_armv4t.ipk satan_0.4_armv4t.ipk scummvm_0.12.0_armv4t.ipk deforaos-browser_0.1.0_armv4t.ipk epiano_0.3.1-r1_armv4t.ipk ethtool_6_armv4t.ipk deforaos-editor_0.1.0_armv4t.ipk enscribi_0.1_armv4t.ipk euphony_0.1.3-r0_armv4t.ipk ffalarms_0.2-r0_all.ipk fido_0.2.2-r0_armv4t.ipk evopedia_0.1_any.ipk fbreader_0.8.2a-r7+elleopatches_om-gta02.ipk 0_pythm_0.5.5-dmr_armv4t.ipk 1_wireshark_1.0.99+svnr26030_armv4t.ipk acceleroids_0.1.0-0_armv4t.ipk 0_tshark_1.0.99+svnr26030_armv4t.ipk 0_wireshark-common_1.0.99+svnr26030_armv4t.ipk bt-gps_1.0-r0_armv4t.ipk cellhunter_0.4.2_armv4t.ipk agps_0.1_armv4t.ipk danish-illume-0.0.1.ipk batalarm_0.2_all.ipk illume-default-alt_0.1_arm.ipk guitartune_0.31_arm.ipk gtick_0.1_armv4t.ipk fourier_1.1_arm.ipk leafpad_0.8.15-r1_armv4t.ipk libsystem_0.1.0_armv4t.ipk gwaterpas_0.2_armv4t.ipk ledclock_0.6_all.ipk flashlight_0.1_armv4t.ipk gridpad_2.0-r0.1_armv4t.ipk gridpad_1.432-r0.1_armv4t.ipk libboost-signals1.33.1_1.33.1-r3_armv4t.ipk DATA gpssight_0.8.4_freerunner.armv4t.ipk EMPTY sortdesk_1.2_armv4t.ipk jdd_0.1_all.ipk usbmode_0.1_armv4t.ipk accel-rotate_0.41_armv4t.ipk 0_multitap-pad_0.1_armv4t.ipk omview_r32_armv4t.ipk deforaos-player_0.1.0_armv4t.ipk illume-keyboards-ru_0.2_om-gta02.ipk GZIP yphonekitd_0.4.3_any.ipk zomg_0.0.6-r2_armv4t.ipk mbac_0.3_all.ipk ylock_0.2_all.ipk mofi_0.02_armv4t.ipk illume-keyboards-norwegian-no_0.1_all.ipk efplayer_0.3_arm.ipk playstankontakarta_0.4_any.ipk osmupdater_0.4_any.ipk voicenote_0.3_arm.ipk mokocard_0.1_all.ipk mokoconv_0.1_all.ipk shortom_0.2_all.ipk So things seem to fail because: - Empty file is an empty file, not much to discuss about that. Only need to find out the reason for that: did the authors really upload an empty package or did the upload fail but an empty file was created? - ar isn't able to extract gzip files so all files recognized as gzip will not get listed properly in the Packages file. Again the reason for the wrong file type should be found: did the packages package it wrong or did the type/mime/something get corrupted along the way, during the upload or on the server? So if YOU reader have packaged some of the packages not recognized as debian binary please make sure that the package you upload is recognized as debian binary with the command 'file packagename.ipk' and then upload it again.. Now we only need to find out a way to contact all packagers... r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Troubles with opkg.org repo
Am Sunday 08 March 2009 14:30:36 schrieb Risto H. Kurppa: On Sat, Mar 7, 2009 at 10:09 AM, Tobias Kündig tobias.kuen...@gmail.com wrote: This is a little summary of what I do: http://www.opkg.org/repo.html Thanks Tobias! At #openmoko tried to figure out what's wrong. Someone pointed out that ftp uses ascii mode by default - I suppose you're uploading at least the Packages -ascii file. How about packages.gz. Man ftp says that ascii upload of binary files might corrupt it - this might be the problem - using binary format shouldn't corrupt the .gz Another find was that 22 packages out of 93 were other than Debian Binary when checked with file *ipk. The list file types listed below: DEBIAN BINARY – CORRECT!!! neon_0.9.8-r1_all.ipk openmoocow_0.3_armv4t.ipk nethack_3.4.3-10.1-0.4_armv4t.ipk openmiaocat_0.2.2_armv4t.ipk orrery_2.4_arm_2008.8.ipk pyring_1.1.6-r1_armv4t.ipk python-pyalsaaudio_0.3-ml0_armv4t.ipk perpendicular_0.1_armv4t.ipk pong_0.1_armv4t.ipk liquidwar_5.6.4-2_armv4t.ipk moko-eightball_0.20080721_om-gta02.ipk mokogeocaching_0.2_all.ipk meooem_0.1_armv4t.ipk minimo_0.02+cvs20070626-r1_armv4t.ipk mokomaze_0.2.2-1_armv4t.ipk mokox48_1.0_arm_2008.8.ipk mutagen_svn-4350-2_armv4t.ipk mokopod_0.1.5_armv4t.ipk mokosync_0.1_arm.ipk tangogps_0.9.6-r0_armv4t.ipk wicd_1.5.6_armv4t.ipk wlan_0.3_arm.ipk tor-0.2.0.34_0.1_armv4t.ipk usbmode-button_0.3_armv4t.ipk xmahjongg-3.7_0.2_armv4t.ipk zinnia-tomoe-ja_0.6.0-20080911_armv4t.ipk zinnia-tomoe-zh_0.6.0-20080911_armv4t.ipk zedlock_0.1_armv4t.ipk zinnia_0.02_armv4t.ipk pytomboy_0.1_armv4t.ipk remoko-server_0.2.1_svnr119-r0_armv4t.ipk rotate_0.0.2_armv4t.ipk qwo_0.4_armv4t.ipk remoko_0.3.2_armv4t.ipk rotator_0.1_all.ipk sms-sentry_1.0-r0_armv4t.ipk swedish-illume_0.1_armv4t.ipk satan_0.4_armv4t.ipk scummvm_0.12.0_armv4t.ipk deforaos-browser_0.1.0_armv4t.ipk epiano_0.3.1-r1_armv4t.ipk ethtool_6_armv4t.ipk deforaos-editor_0.1.0_armv4t.ipk enscribi_0.1_armv4t.ipk euphony_0.1.3-r0_armv4t.ipk ffalarms_0.2-r0_all.ipk fido_0.2.2-r0_armv4t.ipk evopedia_0.1_any.ipk fbreader_0.8.2a-r7+elleopatches_om-gta02.ipk 0_pythm_0.5.5-dmr_armv4t.ipk 1_wireshark_1.0.99+svnr26030_armv4t.ipk acceleroids_0.1.0-0_armv4t.ipk 0_tshark_1.0.99+svnr26030_armv4t.ipk 0_wireshark-common_1.0.99+svnr26030_armv4t.ipk bt-gps_1.0-r0_armv4t.ipk cellhunter_0.4.2_armv4t.ipk agps_0.1_armv4t.ipk danish-illume-0.0.1.ipk batalarm_0.2_all.ipk illume-default-alt_0.1_arm.ipk guitartune_0.31_arm.ipk gtick_0.1_armv4t.ipk fourier_1.1_arm.ipk leafpad_0.8.15-r1_armv4t.ipk libsystem_0.1.0_armv4t.ipk gwaterpas_0.2_armv4t.ipk ledclock_0.6_all.ipk flashlight_0.1_armv4t.ipk gridpad_2.0-r0.1_armv4t.ipk gridpad_1.432-r0.1_armv4t.ipk libboost-signals1.33.1_1.33.1-r3_armv4t.ipk DATA gpssight_0.8.4_freerunner.armv4t.ipk EMPTY sortdesk_1.2_armv4t.ipk jdd_0.1_all.ipk usbmode_0.1_armv4t.ipk accel-rotate_0.41_armv4t.ipk 0_multitap-pad_0.1_armv4t.ipk omview_r32_armv4t.ipk deforaos-player_0.1.0_armv4t.ipk illume-keyboards-ru_0.2_om-gta02.ipk GZIP yphonekitd_0.4.3_any.ipk zomg_0.0.6-r2_armv4t.ipk mbac_0.3_all.ipk ylock_0.2_all.ipk mofi_0.02_armv4t.ipk illume-keyboards-norwegian-no_0.1_all.ipk efplayer_0.3_arm.ipk playstankontakarta_0.4_any.ipk osmupdater_0.4_any.ipk voicenote_0.3_arm.ipk mokocard_0.1_all.ipk mokoconv_0.1_all.ipk shortom_0.2_all.ipk So things seem to fail because: - Empty file is an empty file, not much to discuss about that. Only need to find out the reason for that: did the authors really upload an empty package or did the upload fail but an empty file was created? - ar isn't able to extract gzip files so all files recognized as gzip will not get listed properly in the Packages file. Again the reason for the wrong file type should be found: did the packages package it wrong or did the type/mime/something get corrupted along the way, during the upload or on the server? So if YOU reader have packaged some of the packages not recognized as debian binary please make sure that the package you upload is recognized as debian binary with the command 'file packagename.ipk' and then upload it again.. Now we only need to find out a way to contact all packagers... r Additionally there are a lot of Packages that don't contain a control file with depencies and so on: Form the packages in debian format are these: 0_tshark_1.0.99+svnr26030_armv4t.ipk danish-illume-0.0.1.ipk gtick_0.1_armv4t.ipk numptyphysics_0.3-svn118_armv4t.opk wicd_1.5.6_armv4t.ipk 0_wireshark-common_1.0.99+svnr26030_armv4t.ipk deforaos-browser_0.1.0_armv4t.ipk guitartune_0.31_arm.ipk openttd_0.6-r0.6_armv4t.opk xmahjongg-3.7_0.2_armv4t.ipk 0_xlogical_1.0-8-r0.4_armv4t.opk deforaos-editor_0.1.0_armv4t.ipk illume-keyboards-dutch-nl_0.3_all.opk pong_0.1_armv4t.ipk
Re: Troubles with opkg.org repo
(...cut...) With that huge list of broken packages, wouldn't it be better to just remove them from opkg.org's repository while good versions are uploaded? maybe after that implement some sort of automatic check for both conditions (file type and control file inside) regards Tom ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Troubles with opkg.org repo
On Sat, Mar 07, 2009 at 09:09:15AM +0100, Tobias Kündig wrote: This is a little summary of what I do: http://www.opkg.org/repo.html Debian has this tool called dpkg-scanpackages in the dpkg-dev package. It might simplify your create_repo script. Example usage: $ cat updateindex #!/bin/sh ( dpkg-scanpackages . /dev/null \ ; dpkg-scanpackages -t opk . /dev/null \ ; dpkg-scanpackages -t ipk . /dev/null ) \ | sed -e 's_^Filename: ./_Filename: _' \ | gzip --best Packages.gz -- Rask Ingemann Lambertsen Danish law requires addresses in e-mail to be logged and stored for a year ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Troubles with opkg.org repo
This is a little summary of what I do: http://www.opkg.org/repo.html Am 06.03.2009 22:09, schrieb Risto H. Kurppa: At the moment it looks like that the opkg.org repository is very unstable: packages keep breaking all the time more and more, now I wasn't install sortdesk anymore. AFAIK nothing has changed in the package itself. Tobias: Could you release the scripts that manage the files for public eye to check if we can find something wrong there. OK, I know that some packages are broken but also many that have a fine control fine, they still won't install. http://www.opkg.org/packages/Packages Many packages have only the filename md5.. Not enough for a repository.. How about http://www.opkg.org/packages/ - why some packages are named 0_something or 1_something? See: http://www.opkg.org/package_95.html#comments http://lists.openmoko.org/nabble.html#nabble-td1399612 http://kerneltrap.org/mailarchive/openmoko-community/2009/2/11/4949014/thread#mid-4949014 http://lists.openmoko.org/nabble.html#nabble-td2230730 http://lists.openmoko.org/nabble.html#nabble-td2394770 http://lists.openmoko.org/nabble.html#nabble-td2320442 I'm getting really frustrated with this since there's nothing I can do r ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Troubles with opkg.org repo
Hi all, I have for now disabled the opkg.org repo on my FreeRunner. It kept disturbing opkg update and opkg upgrade. It also offers packages like cellhunter which are not hosted on opkg.org, are identical in files, but result in segmentation fault of opkg. So back to normal and explicit opkg inst http:// until (hopefull soon) opkg.org repo is not causing so much crashes of opkg. Regards, Pander ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Troubles with opkg.org repo
At the moment it looks like that the opkg.org repository is very unstable: packages keep breaking all the time more and more, now I wasn't install sortdesk anymore. AFAIK nothing has changed in the package itself. Tobias: Could you release the scripts that manage the files for public eye to check if we can find something wrong there. OK, I know that some packages are broken but also many that have a fine control fine, they still won't install. http://www.opkg.org/packages/Packages Many packages have only the filename md5.. Not enough for a repository.. How about http://www.opkg.org/packages/ - why some packages are named 0_something or 1_something? See: http://www.opkg.org/package_95.html#comments http://lists.openmoko.org/nabble.html#nabble-td1399612 http://kerneltrap.org/mailarchive/openmoko-community/2009/2/11/4949014/thread#mid-4949014 http://lists.openmoko.org/nabble.html#nabble-td2230730 http://lists.openmoko.org/nabble.html#nabble-td2394770 http://lists.openmoko.org/nabble.html#nabble-td2320442 I'm getting really frustrated with this since there's nothing I can do r -- | risto h. kurppa | risto at kurppa dot fi | http://risto.kurppa.fi ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
