Re: Debian packages containing large files
Sammy Yu wrote:
Hey Basile,
Ah okay let me clarify. This package is not for public consumption
and would not be part of debian distribution. I'm skimming a subset
(percentage based) of our live production database which goes through
some process which generates a debian package in the end.
I would still copy the data into some new table (this is a mysql
statement) and dump that table. Again, MySQL data files are very brittle
(and there is no guarantee of any compatibility at that level). Don't
redistribute them, even internally. So just make a table (pehaps using
Mysql views) and dump it.
Alternatively, do not redistribute the data, but just set up scripts to
fetch it from its source.
The debian
package is then installed in several different test machines. This
process could happen daily so it doesn't make sense for the test
machines to be filling their local mysql install with the large
mysqldump which takes 6-7 hours. I recently raised the percentage and
noticed that the debian packages will no longer install. I'm mainly
looking for help in explaining why a large file in a debian package
would cause the install process to fail. Thanks!
I have no idea, but this mere fact of failure because of large file
might be an indication that your entire approach is very fragile and
should be rethought. I really think that ditributing a Mysql data file
is asking for trouble.
Perhaps paying a local Debian expert could help. Or just using strace to
understand why exactly the dpkg -i is failing.
But I am not a Debian expert, and never used MySQL for tables that big
(i.e. on a production server).
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
Reply to: