]>
Commit | Line | Data |
---|---|---|
4f160de4 | 1 | Summary: Data copying in presence of I/O errors |
5528d04f | 2 | Summary(pl.UTF-8): Kopiowanie danych z błędami wejścia/wyjścia |
4f160de4 | 3 | Name: ddrescue |
b7f41199 | 4 | Version: 1.8 |
5 | Release: 0.1 | |
5675f9c7 | 6 | License: GPL v3+ |
4f160de4 | 7 | Group: Applications/System |
4b5ee2c2 | 8 | Source0: http://savannah.nongnu.org/download/ddrescue/%{name}-%{version}.tar.bz2 |
b7f41199 | 9 | # Source0-md5: 51451893ea96a5f9943523743a6a35ae |
2b04df20 | 10 | Patch0: %{name}-info.patch |
312de3fb JB |
11 | # updated from http://guru.multimedia.cx/wp-content/uploads/2006/08/ddrescue-patch.txt |
12 | Patch1: ddrescue-patch.txt | |
4f160de4 | 13 | URL: http://www.nongnu.org/ddrescue/ddrescue.html |
752885db | 14 | BuildRequires: libstdc++-devel |
469ad9ec | 15 | BuildRequires: rpmbuild(macros) >= 1.167 |
4f160de4 | 16 | BuildRoot: %{tmpdir}/%{name}-%{version}-root-%(id -u -n) |
17 | ||
18 | %description | |
19 | ddrescue copies data from one file or block device (hard disk, cdrom, | |
20 | etc) to another, trying hard to rescue data in case of read errors. | |
21 | ||
22 | ddrescue does not truncate the output file if not asked to. So, | |
23 | everytime you run it on the same output file, it tries to fill in the | |
24 | gaps. | |
25 | ||
26 | If you have two or more copies of a damaged file, cdrom, etc, and run | |
27 | ddrescue on all of them, one at a time, with the same output file, you | |
28 | will probably obtain a complete and error-free file. This is so | |
29 | because the probability of having damaged areas at the same places on | |
30 | different input files is very low. | |
31 | ||
4b5ee2c2 JB |
32 | If you also use the bad blocks file feature of ddrescue, the data will |
33 | be rescued very efficiently. Also you can interrupt the rescue at any | |
34 | time and resume it later. | |
35 | ||
9d25d2c8 JR |
36 | %description -l pl.UTF-8 |
37 | ddrescue kopiuje dane z jednego pliku lub urządzenia blokowego (dysku | |
38 | twardego, płyty CD-ROM itp.) do innego, próbując usilnie uratować dane | |
39 | w przypadku błędów odczytu. | |
4b5ee2c2 | 40 | |
9d25d2c8 JR |
41 | ddrescue nie skraca pliku wyjściowego, jeśli nie zostanie o to |
42 | poproszony. Za każdym uruchomieniem na tym samym pliku wyjściowym | |
43 | próbuje wypełnić luki. | |
4b5ee2c2 | 44 | |
9d25d2c8 | 45 | Jeśli mamy dwie lub więcej kopii uszkodzonego pliku, płyty itp. i |
4b5ee2c2 | 46 | uruchomimy ddrescue na wszystkich z nich z tym samym plikiem |
9d25d2c8 JR |
47 | wyjściowym, prawdopodobnie dostaniemy cały plik bez błędów. Stanie się |
48 | tak dlatego, że prawdopodobieństwo uszkodzenia pliku w tych samych | |
49 | miejscach na różnych kopiach jest bardzo małe. | |
4b5ee2c2 | 50 | |
9d25d2c8 JR |
51 | Jeśli użyjemy opcji obsługi pliku z listą złych bloków w ddrescue dane |
52 | będą odzyskiwane bardzo wydajnie. | |
4f160de4 | 53 | |
54 | %prep | |
55 | %setup -q | |
0487855c | 56 | %patch0 -p1 |
b7f41199 | 57 | #%patch1 -p1 |
4f160de4 | 58 | |
59 | %build | |
0487855c PS |
60 | ./configure \ |
61 | --prefix=%{_prefix} \ | |
62 | --infodir=%{_infodir} \ | |
63 | --mandir=%{_mandir} | |
64 | ||
4f160de4 | 65 | %{__make} \ |
66 | CXX="%{__cxx}" \ | |
0487855c | 67 | CXXFLAGS="%{rpmcxxflags}" |
4f160de4 | 68 | |
69 | %install | |
70 | rm -rf $RPM_BUILD_ROOT | |
0487855c PS |
71 | |
72 | %{__make} install install-man \ | |
73 | DESTDIR=$RPM_BUILD_ROOT | |
4f160de4 | 74 | |
75 | %clean | |
76 | rm -rf $RPM_BUILD_ROOT | |
77 | ||
0c6984fd ER |
78 | %post -p /sbin/postshell |
79 | -/usr/sbin/fix-info-dir -c %{_infodir} | |
0487855c | 80 | |
0c6984fd ER |
81 | %postun -p /sbin/postshell |
82 | -/usr/sbin/fix-info-dir -c %{_infodir} | |
0487855c | 83 | |
4f160de4 | 84 | %files |
85 | %defattr(644,root,root,755) | |
b58fc7e6 | 86 | %doc AUTHORS ChangeLog NEWS README |
4f160de4 | 87 | %attr(755,root,root) %{_bindir}/ddrescue |
73590886 | 88 | %{_infodir}/*.info* |
4b5ee2c2 | 89 | %{_mandir}/man1/* |