dist-gzip target fails
- From: Brian Anderson <bikehead gmail com>
- To: f-spot-list gnome org
- Subject: dist-gzip target fails
- Date: Mon, 18 Jun 2007 09:38:46 -0700
I use the make dist-gzip target to make source archives to build RPMs of
the latest svn image. However when I run dist-gzip or dist-bzip2 I get
the errors below. I didn't used to get these and I checked by tar
defaults and the default storage format is "gnu" which should handle
long names. Anyone else seeing this?
tardir=f-spot-0.4.0 && /bin/sh /home/bikehead/Software/f-spot/missing
--run tar chof - "$tardir" | GZIP=--best gzip -c >f-spot-0.4.0.tar.gz
tar:
f-spot-0.4.0/Mono.Addins/Mono.Addins.Setup/Mono.Addins.Setup.ProgressMonitoring/NullProgressMonitor.cs:
file name is too long (max 99); not dumped
tar:
f-spot-0.4.0/Mono.Addins/Mono.Addins.Setup/Mono.Addins.Setup.ProgressMonitoring/ConsoleProgressMonitor.cs:
file name is too long (max 99); not dumped
tar:
f-spot-0.4.0/Mono.Addins/Mono.Addins.Setup/Mono.Addins.Setup.ProgressMonitoring/ProgressStatusMonitor.cs:
file name is too long (max 99); not dumped
tar: Error exit delayed from previous errors
gtar:
f-spot-0.4.0/Mono.Addins/Mono.Addins.Setup/Mono.Addins.Setup.ProgressMonitoring/NullProgressMonitor.cs:
file name is too long (max 99); not dumped
gtar:
f-spot-0.4.0/Mono.Addins/Mono.Addins.Setup/Mono.Addins.Setup.ProgressMonitoring/ConsoleProgressMonitor.cs:
file name is too long (max 99); not dumped
gtar:
f-spot-0.4.0/Mono.Addins/Mono.Addins.Setup/Mono.Addins.Setup.ProgressMonitoring/ProgressStatusMonitor.cs:
file name is too long (max 99); not dumped
gtar: Error exit delayed from previous errors
{ test ! -d f-spot-0.4.0 || { find f-spot-0.4.0 -type d ! -perm -200
-exec chmod u+w {} ';' && rm -fr f-spot-0.4.0; }; }
--
__o Brian "la lumaca"
_`\<,_
(*)/ (*)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]