Package: wnpp Severity: normal The current maintainer of gddrescue, Ayman Negm <n...@debian.org>, is apparently not active anymore. Therefore, I orphan this package now.
Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: gddrescue Binary: gddrescue Version: 1.2-1.3 Priority: optional Section: utils Maintainer: Ayman Negm <n...@debian.org> Build-Depends: debhelper (>= 4.0.0), autotools-dev Architecture: any Standards-Version: 3.6.2 Format: 1.0 Directory: pool/main/g/gddrescue Files: 18e8741442eda3eceef15d9d6b8ada28 954 gddrescue_1.2-1.3.dsc 39146c48f7d40ed0a98dde692f8466f7 53782 gddrescue_1.2.orig.tar.gz 49011bcff7f3c71429783f2836c8ff5e 6225 gddrescue_1.2-1.3.diff.gz Checksums-Sha1: 882daab6c7559a8a8903d1db28aa86dd63938572 53782 gddrescue_1.2.orig.tar.gz 2f197784248372674f627b4c8411818c9f67f358 6225 gddrescue_1.2-1.3.diff.gz Checksums-Sha256: dc941d993fad5a12ec911edba86fed55e488f6998ef311a89bee6c955264948a 53782 gddrescue_1.2.orig.tar.gz de6edbc6cb5ef21e92b717a28cdc01d7e51e2312177121bf912a83ca3ce1b750 6225 gddrescue_1.2-1.3.diff.gz Package: gddrescue Binary: gddrescue Version: 1.2-1.3 Priority: optional Section: utils Maintainer: Ayman Negm <n...@debian.org> Build-Depends: debhelper (>= 4.0.0), autotools-dev Architecture: any Standards-Version: 3.6.2 Format: 1.0 Directory: pool/main/g/gddrescue Files: 18e8741442eda3eceef15d9d6b8ada28 954 gddrescue_1.2-1.3.dsc 39146c48f7d40ed0a98dde692f8466f7 53782 gddrescue_1.2.orig.tar.gz 49011bcff7f3c71429783f2836c8ff5e 6225 gddrescue_1.2-1.3.diff.gz Checksums-Sha1: 882daab6c7559a8a8903d1db28aa86dd63938572 53782 gddrescue_1.2.orig.tar.gz 2f197784248372674f627b4c8411818c9f67f358 6225 gddrescue_1.2-1.3.diff.gz Checksums-Sha256: dc941d993fad5a12ec911edba86fed55e488f6998ef311a89bee6c955264948a 53782 gddrescue_1.2.orig.tar.gz de6edbc6cb5ef21e92b717a28cdc01d7e51e2312177121bf912a83ca3ce1b750 6225 gddrescue_1.2-1.3.diff.gz Package: gddrescue Priority: optional Section: utils Installed-Size: 128 Maintainer: Ayman Negm <n...@debian.org> Architecture: amd64 Version: 1.2-1.3 Depends: libc6 (>= 2.7-1), libgcc1 (>= 1:4.1.1-21), libstdc++6 (>= 4.1.1-21) Filename: pool/main/g/gddrescue/gddrescue_1.2-1.3_amd64.deb Size: 31640 MD5sum: c23765edd18a9569bfa0fb739fe59912 SHA1: 3f7c118ed0eba61d472ffbc1d2ca2ac92f292028 SHA256: 400670472475fc7bb60d3602ecdf677250d8bc6fb597f8cdbdf468fa1c8228ed Description: the GNU data recovery tool it copies data from one file or block device (hard disc, cdrom, etc) to another, trying hard to rescue data in case of read errors. . gddrescue does not truncate the output file if not asked to. So, every time you run it on the same output file, it tries to fill in the gaps. . The basic operation of ddrescue is fully automatic. That is, you don't have to wait for an error, stop the program, read the log, run it in reverse mode, etc. If you use the logfile feature of ddrescue, the data is rescued very efficiently (only the needed blocks are read). Also you can interrupt the rescue at any time and resume it later at the same point. . Automatic merging of backups: If you have two or more damaged copies of a file, cdrom, etc, and run ddrescue on all of them, one at a time, with the same output file, you will probably obtain a complete and error-free file. This is so because the probability of having damaged areas at the same places on different input files is very low. Using the logfile, only the needed blocks are read from the second and successive copies. . The logfile is periodically saved to disc. So in case of a crash you can resume the rescue with little recopying. Also, the same logfile can be used for multiple commands that copy different areas of the file, and for multiple recovery attempts over different subsets. . gddrescue aligns its I/O buffer to the sector size so that it can be used to read from raw devices. For efficiency reasons, also aligns it to the memory page size if page size is a multiple of sector size. Tag: admin::recovery, hardware::storage, interface::commandline, role::program, scope::utility, suite::gnu, use::storing Package: gddrescue Priority: optional Section: utils Installed-Size: 128 Maintainer: Ayman Negm <n...@debian.org> Architecture: amd64 Version: 1.2-1.3 Depends: libc6 (>= 2.7-1), libgcc1 (>= 1:4.1.1-21), libstdc++6 (>= 4.1.1-21) Filename: pool/main/g/gddrescue/gddrescue_1.2-1.3_amd64.deb Size: 31640 MD5sum: c23765edd18a9569bfa0fb739fe59912 SHA1: 3f7c118ed0eba61d472ffbc1d2ca2ac92f292028 SHA256: 400670472475fc7bb60d3602ecdf677250d8bc6fb597f8cdbdf468fa1c8228ed Description: the GNU data recovery tool it copies data from one file or block device (hard disc, cdrom, etc) to another, trying hard to rescue data in case of read errors. . gddrescue does not truncate the output file if not asked to. So, every time you run it on the same output file, it tries to fill in the gaps. . The basic operation of ddrescue is fully automatic. That is, you don't have to wait for an error, stop the program, read the log, run it in reverse mode, etc. If you use the logfile feature of ddrescue, the data is rescued very efficiently (only the needed blocks are read). Also you can interrupt the rescue at any time and resume it later at the same point. . Automatic merging of backups: If you have two or more damaged copies of a file, cdrom, etc, and run ddrescue on all of them, one at a time, with the same output file, you will probably obtain a complete and error-free file. This is so because the probability of having damaged areas at the same places on different input files is very low. Using the logfile, only the needed blocks are read from the second and successive copies. . The logfile is periodically saved to disc. So in case of a crash you can resume the rescue with little recopying. Also, the same logfile can be used for multiple commands that copy different areas of the file, and for multiple recovery attempts over different subsets. . gddrescue aligns its I/O buffer to the sector size so that it can be used to read from raw devices. For efficiency reasons, also aligns it to the memory page size if page size is a multiple of sector size. Tag: admin::recovery, hardware::storage, interface::commandline, role::program, scope::utility, suite::gnu, use::storing -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org