Active Topics
-
Error after installing Leste on sdcard (13)
to Maemo 7 / Leste by Maemish - 1 hr, 30 mins ago -
TLS 1.2 for N9 is ready (29)
to MeeGo / Harmattan by smatkovi - 10 hrs, 20 mins ago -
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 3 days, 19 hrs ago -
Maemo repository (3)
to Community by torsen - 4 days, 12 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 6 days, 16 hrs ago - more...
|
2008-01-07
, 19:31
|
|
Posts: 2,102 |
Thanked: 1,309 times |
Joined on Sep 2006
|
#2
|
hmm, do you have enough free space to decompress it? The logic to determine whether a file is corrupted may be something along the lines of: try to decompress, if there's a failure (no matter if that's caused by no more disk space) then report that it's corrupt.
How can dpkg -i install it? You're talking about on the tablet I presume? I thought that the whole file had to be decompressed before the bits are moved around or is dpkg more intelligent than that and can decompress individual parts somehow?
How can dpkg -i install it? You're talking about on the tablet I presume? I thought that the whole file had to be decompressed before the bits are moved around or is dpkg more intelligent than that and can decompress individual parts somehow?
 |
|
2008-01-07
, 19:40
|
|
Posts: 3,096 |
Thanked: 1,525 times |
Joined on Jan 2006
@ Michigan, USA
|
#3
|
Originally Posted by lardman
This is what is confusing me, so dpkg can install it without extracting it first and the application manager can't. Is this a bug or a feature?
hmm, do you have enough free space to decompress it? The logic to determine whether a file is corrupted may be something along the lines of: try to decompress, if there's a failure (no matter if that's caused by no more disk space) then report that it's corrupt.
How can dpkg -i install it? You're talking about on the tablet I presume? CORRECT I thought that the whole file had to be decompressed before the bits are moved around or is dpkg more intelligent than that and can decompress individual parts somehow?
It does show an out of space in the log reported from tar in the application manager logs, but WTF. This very annoying
Any ideas
dpkg -i deb works without any issues, but application manager says its a corrupted file?
Its setup like all my other debs (which work great) and I don't think I am doing anything wrong? Does the application manager have a size limitation?
Anyone got any ideas?