Re: [Ltib] same install problem, different files

[Peter Barada]

On Wed, 2010-07-21 at 18:30 +0200, Jan Wilmans wrote:
>     I'll try, but it takes ~3/4 minutes each time before it stops, this will be a very tideous process, 
>     Why does the MD5 fail?, is the wget not getting the binary right? has de server file changed?
>     
>     
>     I would rather 'fix' the problem that is my next install will just run at once, now I have to keep monitoring and restart it.

I can't see why its failing for each file in the process, unless there's something weird about your setup...

1) Are you running Linux in a vmware type system (where the files may be pulled in with CRLF line endings which messes up the .md5)?

2) How did the files in your local package pool get there, from a .iso, copied into place, or pulled from the global package pool via ltib (and wget)?  Did this step mess up line endings?

3) cd into your local package pool and "file *.patch *.md5 | grep CRLF" - if there's any output then I'd think that somehow line endings got converted from unix (LF only) to dos (CRLF).  If so, then you can fix this by "dos2unix *.patch *.md5" and then try ltib again.  Of course you'll want to back up the originals in case this makes things worse...

Past that, you'll have to tweak bin/Ltibutils.pm (get_ref_md5 function) to dump the md5sum it calculated, and what it read from the .md5 (that differ) - then you might be able to figure out *why* the md5sum doesn't match what's expected:

Index: bin/Ltibutils.pm
===================================================================
--- Ltibutils.pm	(revision 10698)
+++ Ltibutils.pm	(working copy)
@@ -501,11 +501,12 @@
         warn "WARN: skipping md5sum check for $path, md5 file was not found\n";
         return 1;
     }
-    if(md5sum($path) eq $refmd5) {
+    my $md5_sum = md5sum($path);
+    if($md5_sum eq $refmd5) {
         warn "OKAY: md5sum($path)\n" if $verbose;
         return 1;
     }
-    warn "ERROR: md5sum mismatch, re-naming $path to $path.bad, ",
+    warn "ERROR: md5sum mismatch($md5_sum != $refmd5), re-naming $path to $path.bad, ",
          "please re-try\n";
     rename($path, "$path.bad");
     return;

Then you might be able to figure out why the calculated .md5 differs.  For the file that fails, then you can let LTIB grab the new copy and compare the md5 of what LTIB got from the global package pool with what you have in your local copy (that's now renamed to add ".bad" to it).

Another possibility is to move everything in your local package pool elsewhere and let LTIB download everything from the global package pool.  Of course if your environment is coming from a .iso that has packages that aren't in the global package pool then you'll have to repopulate those into your local package pool and figure out why the md5sums don't match.

Hope this helps...

>     
>     Greetings,
>     
>     
>     Jan
>     
>     On 21 July 2010 01:06, <address@hidden> wrote:
> >         "Lather, rinse and and repeat.".
> >         
> >         In other words, remove that bad file(and .md5) and try again.  Eventually you should get all you need from the GPP...
> >         Sent via BlackBerry by AT&T
> >         
> >         -----Original Message-----
> >         From: Jan Wilmans <address@hidden>
> >         Sender: ltib-bounces+peterb=logicpd.com@nongnu.org
> >         Date: Tue, 20 Jul 2010 23:52:07
> >         To: <address@hidden>
> >         Subject: [Ltib] same install problem, different files
> >         
> >         _______________________________________________
> >         LTIB home page: http://ltib.org
> >         
> >         Ltib mailing list
> >         address@hidden
> >         http://lists.nongnu.org/mailman/listinfo/ltib
> >         
> >         
> >     
>     
>     
>     
>     -- 
>     Met vriendelijke groeten,
>