Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=676544 --- Comment #10 from Xavier Bachelot <xavier@xxxxxxxxxxxx> 2011-02-15 17:00:32 EST --- That's still not right : $ svn export http://pidgin-logviewer.googlecode.com/svn/trunk/ pidgin-logviewer-read-only ...snip... Exported revision 13. $ tar -cvzf pidgin-logviewer-0.2.tar.gz pidgin-logviewer-0.2 tar: pidgin-logviewer-0.2: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors The commands in the comments are expected to recreate the exact same tarball as you used for building. That is, if you made a snapshot at trunk revision 13, then the commands needs to do exactly that. I would suggest something like that : svn export -r13 http://pidgin-logviewer.googlecode.com/svn/trunk/ pidgin-logviewer tar -cvzf pidgin-logviewer-0.2.tar.gz pidgin-logviewer See https://fedoraproject.org/wiki/Packaging:SourceURL#Using_Revision_Control Going further, you might want to have the snapshot revision and date defined in macros so you can reuse them in the spec. So make it something like : %global snapshot_date 20110215 %global snapshot_revision 13 Name: pidgin-logviewer Version: 0.2 Release: 5.%{snapshot_date}svn%{snapshot_revision}%{?dist} # svn export -r %{snapshot_revision} http://pidgin-logviewer.googlecode.com/svn/trunk/ pidgin-logviewer-%{version} # tar -cvzf pidgin-logviewer-%{version}svn%{snapshot_revision}.tar.gz pidgin-logviewer-%{version} Source0: %{name}-%{version}svn%{snapshot_revision}.tar.gz -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review