Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: par2cmdline
------- Additional Comments From laurent.rineau__fc_extra(a)normalesup.org 2006-04-27 12:58
Spec URL: http://www.di.ens.fr/~rineau/Fedora/par2cmdline.spec
SRPM URL: http://www.di.ens.fr/~rineau/Fedora/par2cmdline-0.4-6.src.rpm
(In reply to comment #1)
spectool cannot fetch the upstream source; your Source: URL is wrong.
Fixed, I think. I cannot reach dl.sourceforge.net
at the present time. :-(
you perhaps include a quick description of a PAR2 file in
I modified it:
"par2cmdline is a program for creating and using PAR2 files. PAR2 files are
usually published in binary newsgroups, on Usenet. They apply the
data-recovery capability concepts of RAID-like systems to the posting and
recovery of multi-part archives. On Usenet, PAR2 files are posted together
with multi-part archives. par2cmdline can detect and repair dammaged files
using the corresponding PAR2 files."
Perhaps somebody can help me to correct my english. I declare the hunt of
frenchisms opened! ;)
(I personnaly use it to repair files from binaries of Lost, season 2, which
will not be on french TV until next year. But do not tell to anybody!)
Please use the recommended BuildRoot:
Please remove Distribution: SuSE 9.1.
Sorry! Done. As you can see, I have adapted an existing (and trivial) spec
I'm not sure about your Obsoletes: and Provides:, but I'll
have some previous package history that requires this. I'll ask the list
for a bit of guidance.
I do not understand. parchive-1.1.4 exists in Fedora Extras 4. See
par2cmdline provides the same functionalities as parchive, and has a
symlink /usr/bin/par->par2. That's why I made this couple of
Obsoletes:/Provides: Perhaps I am wrong. I must admit that I am not totally
used with such a trick.
You should remove the executable bits from these files in %build;
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.