Okay, I tried it again and I still get that one big iso file.  rpmslist
sorts the files out by cd and the script reads rpmslist, and then I see that
the script pushes files according to the rpmslist somewhere, but something
must be going wrong somewhere.


-----Original Message-----
From: Warly <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Friday, June 15, 2001 12:55 AM
Subject: Re: [Cooker] iso file creation


>"pablito" <[EMAIL PROTECTED]> writes:
>
>> I have tried to mirror cooker and make the iso files several times.
Since
>> everyone else makes these with no problems, I figured I must be doing
>> something wrong.
>>
>> There was something wrong with the mkcds install script at first.  Then I
>> found out mkisofs is not installed by default and installed it.  Now, the
>> result is fairly standard:
>>
>>     a.  A message saying I don't have locale configured right, which I
>> checked and found that locale is installed and appears to be configured.
>
>not important
>
>>     b.  At the end of the script, messages that files were not found in
the
>> scripts and were being added to the last iso file.  This happens no
matter
>> how many times I repeat the mirroring process.  (I could not get the DSL
>> connection to work in linux so I am using a windows program called
>> syncromagic that seems to make a copy of the site and delete non-matching
>> files.)
>
>This is not linked to the mirroring process. This only have to do with the
>Mandrake/base/rpmslist file. This files contains the cooker packages
separated
>by CDs. As there are often new packages or new libraries into cooker, these
files,
>that I only check once every one or 2 weeks, are not up to date, and as a
consequence
>there are packages present in the repository but not in the file, these
packages
>are added to the last iso images automatically.
>
>> c.  Result:  I get three iso files, one 1.2 gigs in size and the other 2
of
>> 0 bytes apiece.  I got this same result once by running mkcds.pl by
itself.
>
>This is not normal, however.
>
>--
>Warly
>
>


Reply via email to