Version in base suite: 6.23-1~deb12u1 Base version: rar_6.23-1~deb12u1 Target version: rar_7.01-1~deb12u1 Base file: /srv/ftp-master.debian.org/ftp/pool/non-free/r/rar/rar_6.23-1~deb12u1.dsc Target file: /srv/ftp-master.debian.org/policy/pool/non-free/r/rar/rar_7.01-1~deb12u1.dsc /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/amd64/default.sfx |binary /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/amd64/rar |binary /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/amd64/unrar |binary /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/default.sfx |binary /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/rar |binary /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/unrar |binary rar-7.01/amd64/rar.txt | 417 ++++------ rar-7.01/amd64/rarfiles.lst | 5 rar-7.01/amd64/whatsnew.txt | 105 ++ rar-7.01/debian/changelog | 25 rar-7.01/debian/copyright | 4 rar-7.01/debian/rar.1 | 17 rar-7.01/debian/watch | 4 rar-7.01/rar.txt | 417 ++++------ rar-7.01/rarfiles.lst | 5 rar-7.01/whatsnew.txt | 105 ++ 16 files changed, 606 insertions(+), 498 deletions(-) Binary files /srv/release.debian.org/tmp/LGH83v_Alg/rar-6.23/amd64/default.sfx and /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/amd64/default.sfx differ Binary files /srv/release.debian.org/tmp/LGH83v_Alg/rar-6.23/amd64/rar and /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/amd64/rar differ diff -Nru rar-6.23/amd64/rar.txt rar-7.01/amd64/rar.txt --- rar-6.23/amd64/rar.txt 2023-08-01 09:29:05.000000000 +0000 +++ rar-7.01/amd64/rar.txt 2024-05-12 10:20:16.000000000 +0000 @@ -1,6 +1,6 @@ User's Manual ~~~~~~~~~~~~~ - RAR 6.23 console version + RAR 7.01 console version ~~~~~~~~~~~~~~~~~~~~~~~~ =-=-=-=-=-=-=-=-=-=-=-=-=-=- @@ -455,66 +455,32 @@ a wrong wildcard may corrupt all archived names. - rr[N] Add data recovery record. Optionally, redundant information - (recovery record) may be added to archive. While it increases - the archive size, it helps to recover archived files in case of - disk failure or data loss of other kind, provided that damage - is not too severe. Such damage recovery can be done with - command "r" (repair). - - RAR 4.x and RAR 5.0 archives use different recovery record - structure and algorithms. - - RAR 4.x recovery record is based on XOR algorithm. - You can specify 4.x record size as a number of recovery sectors - or as a percent of archive size. To specify a number of sectors - just add it directly after 'rr', like 'rr1000' for 1000 sectors. - To use a percent append 'p' or '%' modifier after the percent - number, such as 'rr5p' or 'rr5%' for 5%. Note that in Windows - .bat and .cmd files it is necessary to use 'rr5%%' instead of - 'rr5%', because the command processor treats the single '%' - as the start of a batch file parameter, so it might be more - convenient to use 'p' instead of '%' in this case. - - RAR 4.x recovery sectors are 512 bytes long. If damaged area - is continuous, every sector helps to recover 512 bytes of - damaged information. This value may be lower in cases of - multiple damage. Maximum number of recovery sectors is 524288. - - Size of 4.x recovery record may be approximately determined as - /256 + *512 bytes - and cannot exceed the protected data size or 256 MB, - whatever is less. - - RAR 5.0 recovery record uses Reed-Solomon error correction codes. - Its ability to repair continuous damage is about the same - as for RAR 4.x, allowing to restore slightly less data than - recovery record size. But it is more efficient than RAR 4.x - record in case of multiple damaged areas and shifted data - positions. - - RAR 5.0 record does not use 512 byte sectors and you can specify - its size only as a percent of archive size. Even if '%' or 'p' - modifier is not present, RAR treats the value as a percent - in case of RAR 5.0 format, so both 'rr5' and 'rr5p' mean 5%. - Due to service data overhead the actual resulting recovery record + rr[N] Add the data recovery record. + + Recovery record is the data area, optionally added to archive + and containing error correction codes, namely Reed-Solomon codes + for RAR 5.0 archive format. While it increases the archive size, + it helps to recover archived files in case of disk failure + or data loss of other kind, provided that damage is not too + severe. Such recovery can be done with 'R' repair command. + + Optional 'N' parameter defines the recovery record size + as a percent of archive size. If it is omitted, 3% is assumed. + Maximum allowed recovery record size is 1000%. Larger recovery + records are processed slower both when creating and repairing. + Due to service data overhead, the actual resulting recovery record size only approximately matches the user defined percent and difference is larger for smaller archives. - Maximum allowed RAR 5.0 recovery record size is 1000%. - Larger recovery records are processed slower both when creating - and repairing. - - RAR 5.0 recovery record is more resistant to damage of recovery - record itself and can utilize a partially corrupt recovery - record data. Note, though, that 'R' repair command does not fix - broken blocks in recovery record. Only file data are corrected. - After successful archive repair, you may need to create a new - recovery record for saved files. - - If you use the plain 'rr' command without optional parameter, - RAR will set the recovery record size to 3% of archive size - by default. + In case of a single continuous damage, typically it is possible + to restore slightly less data than recovery record size. + Recoverable data size can be lower for multiple damages. + + If a recovery record is partially broken, its remaining valid data + still can be utilized to repair files. Repair command does not + fix broken blocks in recovery record itself, only file data + is corrected. After successful archive repair, you may need to + create a new recovery record for rescued files. While the recovery record improves chances to repair damaged archives, it does not guarantee the successful recovery. @@ -523,7 +489,7 @@ Example: - rar rr5p arcname + rar rr5 arcname add the recovery record of 5% of archive size. @@ -548,7 +514,7 @@ 3 missing volumes. If the number of .rev files is less than the number of missing volumes, reconstructing is impossible. The total number of usual and recovery volumes must not - exceed 255 for RAR 4.x and 65535 for RAR 5.0 archive format. + exceed 65535. Original RAR volumes must not be modified after creating recovery volumes. Recovery algorithm uses data stored both @@ -565,10 +531,9 @@ than media size. The optional parameter specifies a number of recovery - volumes to create. It must be less than the total number of - RAR volumes in the set for RAR 4.x and must not be larger - than tenfold amount of RAR volumes for RAR 5.0 format. - Values exceeding the threshold are adjusted automatically. + volumes to create. It must not be larger than tenfold amount + of RAR volumes. Values exceeding the threshold are adjusted + automatically. You may also append a percent or 'p' character to this parameter, in such case the number of creating .rev files will be equal to @@ -591,9 +556,11 @@ s[name] Convert archive to SFX. The archive is merged with a SFX module (using a module in file default.sfx or specified in the switch). - In the Windows version default.sfx should be placed in the - same directory as the rar.exe, in Unix - in the user's - home directory, in /usr/lib or /usr/local/lib. + In Windows version default.sfx should be placed in the same + directory as the rar.exe, in Unix - in the user's home directory, + in /usr/lib or /usr/local/lib. + + Windows version uses default32.sfx name for 32-bit SFX module. s- Remove SFX module from the already existing SFX archive. RAR creates a new archive without SFX module, the original @@ -1212,8 +1179,7 @@ file contents based on checksums. Do not expect such encrypted file checksums to match usual CRC32 and BLAKE2sp values. - This switch is supported only by RAR 5.0 format, so you - need to use -ma switch with it. + This switch is supported only by RAR 5.0 format. You can see checksums of archived files using 'vt' or 'lt' commands. @@ -1221,7 +1187,7 @@ Example: - rar a -ma -htb lists.rar *.lst + rar a -htb lists.rar *.lst will add *.lst to lists.rar using BLAKE2sp for file checksums. @@ -1410,163 +1376,132 @@ (normal compression). - -ma[4|5] - Specify a version of archiving format. - - By default RAR creates archives in RAR 5.0 format. - Use -ma4 to create RAR 4.x archives. - Use -ma5 or just -ma in case you need to override -ma4 saved - in configuration and force RAR to use RAR 5.0 format. - - This switch is used only when creating a new archive. - It is ignored when updating an existing archive. - - -mc Set advanced compression parameters. - This switch is intended mainly for benchmarking and - experiments. In the real environment it is usually better - to allow RAR to select optimal parameters automatically. - Please note that improper use of this switch may lead - to very serious performance and compression loss, so use - it only if you clearly understand what you do. - - It has the following syntax: + Improper use of this switch may lead to suboptimal performance + and compression. This switch has the following syntax: - -mc[param1][:param2][module][+ or -] + -mc[channels][mode][+ or -] - where is the one character field denoting a part - of the compression algorithm, which has to be configured. + where is the single character field defining + the compression algorithm to be configured. - It may have the following values: + Possible values are: - A - audio compression; - C - true color (RGB) data compression; D - delta compression; E - x86 executable compression; - T - text compression. - - RAR 5.0 archive format supports only 'D' and 'E' values. + L - long range search; + X - exhaustive search. '+' sign at the end of switch applies the selected algorithm - module to all processed data, '-' disables the module at all. - If no sign is specified, RAR will choose modules automatically, - based on data and the current compression method. - - Switch -mc- disables all optional modules and allows only - the general compression algorithm. - - and are module dependent parameters - described below. - + to all processed data, '-' disables it completely. + If no sign is specified, RAR chooses modes automatically, + based on data and current compression method. + Switch -mc- disables all modes. - Audio compression, delta compression: + parameter is used by delta compression and ignored + by other modes. Available modes are described below. - is a number of byte channels (can be 1 - 31). - RAR splits multibyte channels to bytes, for example, - two 16-bit audio channels are considered by RAR as four - channels one byte each. - is ignored. + Delta compression + Splits data to several single byte channels and calculates + the difference between them. Can improve the compression ratio + of table data. is the number of byte channels + from 1 to 31. - x86 Intel executable compression, true color (RGB) data - compression: - and are ignored. + x86 executable compression + Can improve the compression ratio of 32 and 64 bit x86 executables. - Text compression: - Text compression algorithm provides noticeably higher compression - on plain text data. But it cannot utilize several CPU cores - efficiently resulting in slower compression time comparing to - general algorithm in multicore and multiprocessor environment. - Also its decompression speed is much slower than in general - algorithm regardless of CPU cores number. This is why - the text compression is disabled by default. You can specify - -mct switch to allow RAR to select this algorithm automatically - for suitable data. Switch -mct+ will force use of the text - compression for all data. + Long range search - Switch -mct can also include and , so its - full syntax is -mc[param1][:param2]t[+ or -]. - - is the order of PPM algorithm (can be 2 - 63). - Usually a higher value slightly increases the compression ratio - of redundant data, but only if enough memory is available - to PPM. In case of lack of memory the result may be negative. - Higher order values decrease both compression and decompression - speed. + Enables the search algorithm designed to efficiently locate + longer and more distant repeated data blocks. It can helps to + improve the compression ratio and sometimes speed for redundant + data like big text files. This algorithm increases memory + requirements when archiving, but doesn't affect extraction + memory requirements or speed. + + If neither -mcl+ nor -mcl- are specified, RAR applies the long + range search depending on the compression method, dictionary size + and other parameters. This algorithm is required and enabled + automatically for dictionaries exceeding 4 GB, where it can't be + turned off with -mcl- switch. + + Long range search mode is applicable to -m2..-m5 compression + methods and ignored for -m1. - is memory in megabytes allocated for PPM (1-128). - Higher values may increase the compression ratio, but note - that PPM uses the equal memory size both to compress and - decompress, so if you allocate too much memory when creating - an archive, other people may have problems when decompressing - it on a computer with less memory installed. Decompression - will be still possible using virtual memory, but it may - become very slow. + Exhaustive search - Examples: + Enables much slower and more exhaustive repeated data search + and compression algorithm. It might provide the additional + compression gain on some types of redundant data, but at much + lower speed. Long range search is needed to implement this mode + efficiently, so -mcx activates it automatically. - 1) switch -mc1a+ forces use of 8-bit mono audio compression - for all data. - 2) switch -mc10:40t+ forces use of text compression - algorithm for all data, sets the compression order to 10 - and allocates 40 MB memory. + Example: - 3) switch -mc12t sets the text compression order to 12, - when the text compression is used, but leaves to RAR to - decide when to use it. + RAR a -s -md1g -mcx texts *.txt - 4) switches -mct -mcd- allow RAR to apply the text compression - to suitable data and disable the delta compression. + create a solid archive with 1 GB dictionary and exhaustive search. - -md[k,m,g] + -md[x][k,m,g] Select the dictionary size. Sliding dictionary is the memory area used by compression algorithm to find and compress repeated data patterns. - If size of file being compressed (or total files size in case - of solid archive) is larger than dictionary size, increasing + If size of file to compress, or total files size in case + of solid archive, is larger than dictionary size, increasing the dictionary is likely to increase the compression ratio, reduce the archiving speed and increase memory requirements. - For RAR 4.x archive format the dictionary size can be: - 64 KB, 128 KB, 256 KB, 512 KB, 1 MB, 2 MB, 4 MB. - For RAR 5.0 archive format the dictionary size can be: 128 KB, 256 KB, 512 KB, 1 MB, 2 MB, 4 MB, 8 MB, 16 MB, - 32 MB, 64 MB, 128 MB, 256 MB, 512 MB, 1 GB. + 32 MB, 64 MB, 128 MB, 256 MB, 512 MB, 1 GB, 2 GB, 4 GB. - You can use 'k', 'm' and 'g' modifiers to specify the size - in kilo-, mega- and gigabytes, like -md64m for 64 MB dictionary. - If no modifier is specified, megabytes are assumed, - so -md64m and -md64 are equal. - - When archiving, RAR needs about 6x memory of specified - dictionary size, so 512 MB and 1 GB sizes are available - in 64 bit RAR version only. When extracting, slightly more - than a single dictionary size is allocated, so both 32 - and 64 bit versions can unpack archives with all dictionaries - up to and including 1 GB. + RAR 7.0 extends the maximum dictionary size up to 64 GB + and permits not power of 2 sizes for dictionaries exceeding 4 GB. + Such archives can be unpacked by RAR 7.0 and newer. + + By default, RAR refuses to unpack archives with dictionary + exceeding 4 GB. It is done to prevent the unexpected large memory + allocation. Use -md or -mdx to allow unpacking + dictionaries up to and including the specified size. + Unlike -md, -mdx is applied to extraction only + and can be added to RAR environment variable, not affecting + archiving commands. + + 'k', 'm' and 'g' modifiers placed after the size, set kilobyte, + megabyte and gigabyte units, like -md64m for 64 MB dictionary. + If no modifier is present, megabytes are assumed for -md + and gigabytes for -mdx switch, so -md64m and -md64 + or -mdx8 and -mdx8g are equal. + + Compression memory requirements vary depending on the dictionary + size and presence of long range search -mcl switch. + Rough estimate is 7x of dictionary size for 1 GB and 1.5x + for 64 GB dictionary. + + When extracting, slightly more than a single dictionary size + is allocated. If size of all source files for solid archive or size of largest source file for non-solid archive is at least twice less than dictionary size, RAR can reduce the dictionary size. It helps to lower memory usage without decreasing compression. - Default sliding dictionary size is 4 MB for RAR 4.x - and 32 MB for RAR 5.0 archive format. + Default sliding dictionary size is 32 MB. Example: - RAR a -s -ma -md128 lib *.dll + RAR a -s -md128 lib *.dll create a solid archive in RAR 5.0 format with 128 MB dictionary. @@ -1746,7 +1681,7 @@ Examples: - 1) rar a -oi -ma archive + 1) rar a -oi archive Save contents of current directory to archive.rar. Store identical files as references. @@ -1757,15 +1692,15 @@ 1000000 bytes, found in c:\photo and its subdirectories. - -ol[a] Process symbolic links as the link [absolute paths] + -ol[a,-] + Process symbolic links as the link [absolute paths, skip] Save symbolic links as links, so file or directory contents is not archived. In Windows version it also saves reparse points as links. Such archive entries are restored as symbolic links or reparse points when extracting. - Supported both for RAR 4.x and RAR 5.0 archives in RAR for Unix - and only for RAR 5.0 archives in RAR for Windows. + Supported both in Unix and Windows RAR versions. In Windows you may need to run RAR as administrator to create symbolic links when extracting. @@ -1783,7 +1718,9 @@ are sure that archive contents is safe, such as your own backup. Links that are considered safe by RAR are extracted always - regardless of -ol or -ola switch. + regardless of -ol or -ola switch, unless -ol- is specified. + + Switch -ol- skips symbolic links when archiving or extracting. -oni Allow potentially incompatible names. @@ -1834,6 +1771,11 @@ Streams are not saved for NTFS encrypted files. + Unlike GUI WinRAR, the console RAR doesn't propagate the archive + Mark of the Web stream to extracted files. It unpacks archived + Zone.Identifier streams as is, regardless of host archive + Zone.Identifier stream presence. + -ow Use this switch when archiving to save file security information and when extracting to restore it. @@ -1923,6 +1865,10 @@ and do not care about archive open speed in different programs, specify -qo- to exclude the quick open information completely. + Switch -qo- also prohibits access to quick open information + in existing archives, such as when extracting or listing + their contents. + If you wish to measure the performance effect of this switch, be sure that archive contents is not stored in a disk cache. No real disk seeks are performed for cached archive file, @@ -2008,9 +1954,9 @@ rar a -ri0:10 backup *.* - -rr[N] Add data recovery record. This switch is used when creating - or modifying an archive to add a data recovery record to - the archive. See the 'rr[N]' command description for details. + -rr[N] Add the data recovery record. This switch is used when creating + or modifying an archive to add the data recovery record to + archive. See 'rr[N]' command description for details. -rv[N] Create recovery volumes. This switch is used when creating @@ -2034,14 +1980,13 @@ Example: - create solid archive sources.rar with 512 KB dictionary, - recursing all directories, starting with the current directory. - Add only .asm files: + add all *.c and *.h files from the current directory to + the solid archive sources.rar: - rar a -s -md512 sources.rar *.asm -r + rar a -s sources.rar *.c *.h - -s Create solid groups using file count + -s Create solid groups using the file count Similar to -s, but resets solid statistics after compressing files. Usually decreases compression, but also @@ -2110,9 +2055,11 @@ Create SFX archives. If this switch is used when creating a new archive, a Self-Extracting archive (using a module in file default.sfx or specified in the switch) would be created. - In the Windows version default.sfx should be placed in the - same directory as the rar.exe, in Unix - in the user's - home directory, in /usr/lib or /usr/local/lib. + In Windows version default.sfx should be placed in the same + directory as the rar.exe, in Unix - in the user's home directory, + in /usr/lib or /usr/local/lib. + + Windows version uses default32.sfx name for 32-bit SFX module. Example: @@ -2156,16 +2103,26 @@ type docs.rar | rar x -si -o+ -pmypwd dummy docs\ - -sl + -sl[b|B|k|K|m|M|g|G|t|T] Process only those files, which size is less than specified in parameter of this switch. - Parameter must be specified in bytes. + + Unit type character following the size value can be 'b' or 'B' + for bytes, 'k' for kilobytes, 'K' for thousands of bytes, + 'm' for megabytes, 'M' for millions of bytes, 'g' for gigabytes, + 'G' for billions of bytes, 't' for terabytes, 'T' for trillions + of bytes. If this character is not present, bytes are assumed. - -sm + -sm[b|B|k|K|m|M|g|G|t|T] Process only those files, which size is more than specified in parameter of this switch. - Parameter must be specified in bytes. + + Unit type character following the size value can be 'b' or 'B' + for bytes, 'k' for kilobytes, 'K' for thousands of bytes, + 'm' for megabytes, 'M' for millions of bytes, 'g' for gigabytes, + 'G' for billions of bytes, 't' for terabytes, 'T' for trillions + of bytes. If this character is not present, bytes are assumed. -sv Create independent solid volumes @@ -2298,25 +2255,17 @@ are assumed. Append '+' to store a file time with maximum possible precision. - Concrete value depends on a operating system and file system - and can be up 100 nanoseconds in Windows and 1 nanosecond - in Unix. Append '1' to set 1 second precision or '-' to not save - a file time. If '+', '-' or '1' are not present, '+' is assumed, + The exact value depends on the particular operating system + also as the file system and can be up to 100 nanoseconds + in Windows and 1 nanosecond in Unix. Append '1' to set 1 second + precision or '-' to not save a file time, such as -ts- to omit + all 3 times. If '+', '-' or '1' are not present, '+' is assumed, so -ts+ and -ts both save all three high precision times. All stored times for same file always have the same precision. If different precisions are specified, such as -tsm1 -tsc+, common one is selected. - RAR 4.x archives always contain the modification time - and for RAR 4.x archive -tsm- still saves the modification time - with the lowest possible 2 second precision. Two other times - can be disabled. RAR 5.0 archives allow to omit any file time - including modification, so unpacked files will have the current - system time. Switches -tsm- -tsc- -tsa- or just -ts- will store - a low precision modification time for RAR 4.x and no file time - for RAR 5.0 archive. - If -ts switch is not specified, RAR stores the high precision modification time and omits two other times. @@ -2391,13 +2340,15 @@ specified volume. - -v[k|b|m|M|g|G] - Create volumes with size=*1000 [*1024 | *1]. - By default this switch uses as thousands (1000) of bytes - (not 1024 x bytes). You may also enter the size in kilobytes - using the symbol 'k', in bytes using the symbol 'b', - megabytes - 'm', millions of bytes - 'M', gigabytes - 'g', - billions (milliards) of bytes - 'G'. + -v[b|B|k|K|m|M|g|G|t|T] + Create volumes of the specified size. + + Unit type character following the size value can be 'b' or 'B' + for bytes, 'k' for kilobytes, 'K' for thousands of bytes, + 'm' for megabytes, 'M' for millions of bytes, 'g' for gigabytes, + 'G' for billions of bytes, 't' for terabytes, 'T' for trillions + of bytes. If this character is not present, the size value + is treated as thousands of bytes If the size is omitted, autodetection will be used. @@ -2421,13 +2372,14 @@ At this moment in time, you should change the disks. Answering 'A' will cause all volumes to be created without a pause. - By default RAR volumes have names like 'volname.partNNN.rar', - where NNN is the volume number. For RAR 4.x archive format - using -vn switch it is possible to select another, - extension based naming scheme, where the first volume file - in a multi-volume set has the extension .rar, following - volumes are numbered from .r00 to .r99. RAR 5.0 archives - do not support -vn and extension based names. + RAR volumes have names like 'volname.partNNN.rar', where NNN + is the volume number. + + Volumes created by older RAR versions could use the another naming + scheme, where the first volume file in a multi-volume set had + .rar extension, followed by volumes with extensions from .r00 to + .r99. RAR can unpack such volumes, but doesn't use the extension + based names for new archives. When extracting or testing a multi-volume archive you must use only the first volume name. If there is no next volume @@ -2503,17 +2455,6 @@ either is present in archive or will be created later. - -vn Use the old style volume naming scheme - - By default RAR volumes have names like 'volname.partNNN.rar', - where NNN is the volume number. For RAR 4.x archive format - using -vn switch it is possible to select another, - extension based naming scheme, where the first volume file - in a multi-volume set has the extension .rar, following - volumes are numbered from .r00 to .r99. RAR 5.0 archives - do not support -vn and extension based names. - - -vp Pause before each volume By default RAR asks for confirmation before processing @@ -2529,7 +2470,7 @@ RAR creates temporary files in some operations like archive modification. This switch can be used to specify the directory - for such temporary files. This directory must be already exist. + for such temporary files. This directory must already exist. Example: @@ -2680,7 +2621,7 @@ Copyrights - (c) 1993-2023 Alexander Roshal + (c) 1993-2024 Alexander Roshal diff -Nru rar-6.23/amd64/rarfiles.lst rar-7.01/amd64/rarfiles.lst --- rar-6.23/amd64/rarfiles.lst 2023-08-01 09:29:05.000000000 +0000 +++ rar-7.01/amd64/rarfiles.lst 2024-05-12 10:20:16.000000000 +0000 @@ -70,6 +70,7 @@ *.tif *.png *.jpg +*.jxl *.chm *.pdf *.cab @@ -83,9 +84,13 @@ *.gz *.bz2 *.xz +*.zst +*.zstd *.jar +*.avif *.fla *.flac +*.heif *.ape *.bik *.mkv Binary files /srv/release.debian.org/tmp/LGH83v_Alg/rar-6.23/amd64/unrar and /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/amd64/unrar differ diff -Nru rar-6.23/amd64/whatsnew.txt rar-7.01/amd64/whatsnew.txt --- rar-6.23/amd64/whatsnew.txt 2023-08-01 09:29:05.000000000 +0000 +++ rar-7.01/amd64/whatsnew.txt 2024-05-12 10:20:16.000000000 +0000 @@ -1,6 +1,111 @@ RAR - What's new in the latest version + Version 7.01 + + 1. Bugs fixed: + + a) updating an encrypted file in a solid RAR archive produced + a corrupt archive if updated file was the first in archive, + no password was specified when starting updating and file name + encryption in the updated archive wasn't enabled; + + b) fixed a possible crash in Unix RAR and UnRAR when unpacking + a corrupt RAR archive. We are thankful to Matteo Marini + for reporting this bug; + + c) switch -ep4 duplicated the specified path instead of excluding it + when extracting. + + + Version 7.00 + + 1. Compression dictionary sizes larger than 1 GB are supported + for RAR archive format. Depending on the amount of physically + available memory, dictionary up to 64 GB can be selected. + + Not power of 2 dictionary sizes can be specified for dictionaries + exceeding 4 GB. So we are not limited to 4, 8, 16, 32, 64 series + and can use values like 5 GB or 22 GB. + + Archives with dictionaries exceeding 4 GB can be unpacked only + by RAR 7.0 or newer. + + Increasing the dictionary size can improve the compression ratio + for large files with distant repeated blocks, like virtual machine + disk images. It also can be efficient for sets of large similar files + in a solid archive, such as a collection of software ISO images + differing by version or localization. + + 2. By default RAR refuses to unpack archives with dictionary exceeding + 4 GB. It is done to prevent the unexpected excessive memory allocation. + + Use -md or -mdx to allow unpacking dictionaries up to + and including the specified size. Unlike -md, -mdx + is applied to extraction only and can be added to RAR environment + variable, not affecting archiving commands. + + 3. Alternate search algorithm, optimized to locate longer and more distant + repeated data blocks, can be used when creating RAR archives. + It helps to improve the compression ratio and sometimes speed + for redundant data like big text files. + + It increases memory usage and might reduce the compression speed + for some types of data. It can be turned on or off with + with -mcl[+|-] switch. If -mcl is not present, RAR applies the long + range search depending on the compression method, dictionary size + and other parameters. + + This algorithm is required for dictionaries exceeding 4 GB + and turning it off is ignored for such dictionaries. + + 4. Much slower and more exhaustive repeated data search and compression + algorithm can be enabled with -mcx switch. It might provide + the additional compression gain for some types of redundant data, + but at much lower compression speed. + + Long range search is needed to implement this mode efficiently, + so the exhaustive search option activates it automatically. + + Both long range and exhaustive search option do not affect + the compatibility of created archives. So if dictionary size + is in 128 KB - 4 GB range, archives created with these search options + can be unpacked by all RAR versions beginning from 5.0. + + 5. Maximum path length limit is increased from 2047 to 65535 characters. + + 6. Creating archives in RAR 4.x format isn't supported anymore. + Options and switches specific for this format are removed. + It doesn't affect RAR 4.x archives decompression, which is included + into RAR. + + 7. Switch -ol- prohibits archiving and extracting symbolic links. + + 8. Switches -sl[u] and -sm[u] recognize [k|K|m|M|g|G|t|T] + size units for kilobytes, thousands of bytes, megabytes, millions + of bytes, gigabytes, billions of bytes, terabytes, trillions of bytes. + If unit character is 'b', 'B' or not present, bytes are assumed. + + Previously these switches accepted bytes only. + + 9. Switch -v[unit] recognizes 't' and 'T' as terabytes and + trillions of bytes for volume size units. + + 10. Proper progress is displayed when compressing symbolic link targets. + + + Version 6.24 + + 1. Bugs fixed: + + a) extraction command dereferenced a null pointer and crashed + when processing a zero length archive name in the archive metadata + stored with -am switch. + + We are thankful to Radoslaw Madej from Check Point software + for reporting this issue. + + Version 6.23 1. Bugs fixed: diff -Nru rar-6.23/debian/changelog rar-7.01/debian/changelog --- rar-6.23/debian/changelog 2023-08-27 05:38:21.000000000 +0000 +++ rar-7.01/debian/changelog 2025-06-30 20:30:10.000000000 +0000 @@ -1,14 +1,23 @@ -rar (2:6.23-1~deb12u1) bookworm; urgency=high +rar (2:7.01-1~deb12u1) bookworm; urgency=medium * Non-maintainer upload. - * Fix CVE-2023-40477: - A specific flaw within the processing of recovery volumes exists in RAR, - an archive program for rar files. It allows remote attackers to execute - arbitrary code on affected installations. User interaction is required to - exploit this vulnerability. The target must visit a malicious page or open - a malicious rar file. + * Rebuild for bookworm. + - CVE-2024-33899: ANSI Escape Injection - -- Markus Koschany Sun, 27 Aug 2023 07:38:21 +0200 + -- Adrian Bunk Mon, 30 Jun 2025 23:30:10 +0300 + +rar (2:7.01-1) unstable; urgency=medium + + * New upstream version + + -- Bastian Germann Mon, 16 Sep 2024 20:51:09 +0200 + +rar (2:7.00-1) unstable; urgency=medium + + * New upstream version + * d/watch: Insert missing dot in upstream version + + -- Bastian Germann Mon, 04 Mar 2024 22:01:58 +0100 rar (2:6.23-1) unstable; urgency=medium diff -Nru rar-6.23/debian/copyright rar-7.01/debian/copyright --- rar-6.23/debian/copyright 2023-01-27 17:37:39.000000000 +0000 +++ rar-7.01/debian/copyright 2024-03-04 21:01:58.000000000 +0000 @@ -7,13 +7,13 @@ Source: http://www.rarlab.com/download.htm Files: * -Copyright: Copyright (c) 1993-2023 Alexander Roshal +Copyright: Copyright (c) 1993-2024 Alexander Roshal Comment: This software is shareware. License: RAR-EULA Files: *rar Copyright: - Copyright (c) 1993-2023 Alexander Roshal + Copyright (c) 1993-2024 Alexander Roshal Copyright (c) 2004-2006 Intel Corporation. All Rights Reserved License: RAR-EULA and BSD-2-clause diff -Nru rar-6.23/debian/rar.1 rar-7.01/debian/rar.1 --- rar-6.23/debian/rar.1 2022-03-16 18:39:28.000000000 +0000 +++ rar-7.01/debian/rar.1 2024-03-04 21:01:58.000000000 +0000 @@ -14,7 +14,7 @@ .br Commands and options described here are as of .BR rar -6.11. +7.00. .PP .B rar is a program for creating and manipulating .rar archives. @@ -136,6 +136,9 @@ .B \-ai Ignore file attributes. .TP +.B \-am[s,r] +Archive name and time [save, restore] +.TP .B \-ap Set path inside archive. This path is merged to file names when adding files to an archive and removed from file names when extracting. @@ -239,9 +242,6 @@ .BR rar uses \-m3 method (Normal compression). .TP -.B \-ma[4|5] -Specify a version of archiving format. -.TP .B \-mc Set advanced compression parameters. For further details look in @@ -284,8 +284,8 @@ .B \-oi[0-4][:min] Save identical files as references. .TP -.B \-ol[a] -Process symbolic links as the link [absolute paths]. +.B \-ol[a,-] +Process symbolic links as the link [absolute path, skip]. .TP .B \-op Set the output path for extracted files. @@ -391,15 +391,12 @@ .B \-u Update files. .TP -.B \-v[k|b] +.B \-v[b|B|k|K|m|M|g|G|t|T] Create volumes with size=*1000 [*1024, *1] bytes. .TP .B \-ver[n] File version control. .TP -.B \-vn -Use the old style volume naming scheme. -.TP .B \-vp Pause before each volume. .TP diff -Nru rar-6.23/debian/watch rar-7.01/debian/watch --- rar-6.23/debian/watch 2022-10-26 17:06:11.000000000 +0000 +++ rar-7.01/debian/watch 2024-03-04 20:57:13.000000000 +0000 @@ -1,7 +1,7 @@ version=4 -opts="versionmangle=s/b/~b/" \ +opts="versionmangle=s/b/~b/,uversionmangle=s/^(\d)/$1\./" \ https://www.rarlab.com/download.htm /rar/rarlinux-x32-(\d.*)\.tar\.gz debian -opts="versionmangle=s/b/~b/,component=amd64" \ +opts="versionmangle=s/b/~b/,uversionmangle=s/^(\d)/$1\./,component=amd64" \ https://www.rarlab.com/download.htm /rar/rarlinux-x64-(\d.*)\.tar\.gz same uupdate Binary files /srv/release.debian.org/tmp/LGH83v_Alg/rar-6.23/default.sfx and /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/default.sfx differ Binary files /srv/release.debian.org/tmp/LGH83v_Alg/rar-6.23/rar and /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/rar differ diff -Nru rar-6.23/rar.txt rar-7.01/rar.txt --- rar-6.23/rar.txt 2023-08-01 09:28:30.000000000 +0000 +++ rar-7.01/rar.txt 2024-05-12 10:19:40.000000000 +0000 @@ -1,6 +1,6 @@ User's Manual ~~~~~~~~~~~~~ - RAR 6.23 console version + RAR 7.01 console version ~~~~~~~~~~~~~~~~~~~~~~~~ =-=-=-=-=-=-=-=-=-=-=-=-=-=- @@ -455,66 +455,32 @@ a wrong wildcard may corrupt all archived names. - rr[N] Add data recovery record. Optionally, redundant information - (recovery record) may be added to archive. While it increases - the archive size, it helps to recover archived files in case of - disk failure or data loss of other kind, provided that damage - is not too severe. Such damage recovery can be done with - command "r" (repair). - - RAR 4.x and RAR 5.0 archives use different recovery record - structure and algorithms. - - RAR 4.x recovery record is based on XOR algorithm. - You can specify 4.x record size as a number of recovery sectors - or as a percent of archive size. To specify a number of sectors - just add it directly after 'rr', like 'rr1000' for 1000 sectors. - To use a percent append 'p' or '%' modifier after the percent - number, such as 'rr5p' or 'rr5%' for 5%. Note that in Windows - .bat and .cmd files it is necessary to use 'rr5%%' instead of - 'rr5%', because the command processor treats the single '%' - as the start of a batch file parameter, so it might be more - convenient to use 'p' instead of '%' in this case. - - RAR 4.x recovery sectors are 512 bytes long. If damaged area - is continuous, every sector helps to recover 512 bytes of - damaged information. This value may be lower in cases of - multiple damage. Maximum number of recovery sectors is 524288. - - Size of 4.x recovery record may be approximately determined as - /256 + *512 bytes - and cannot exceed the protected data size or 256 MB, - whatever is less. - - RAR 5.0 recovery record uses Reed-Solomon error correction codes. - Its ability to repair continuous damage is about the same - as for RAR 4.x, allowing to restore slightly less data than - recovery record size. But it is more efficient than RAR 4.x - record in case of multiple damaged areas and shifted data - positions. - - RAR 5.0 record does not use 512 byte sectors and you can specify - its size only as a percent of archive size. Even if '%' or 'p' - modifier is not present, RAR treats the value as a percent - in case of RAR 5.0 format, so both 'rr5' and 'rr5p' mean 5%. - Due to service data overhead the actual resulting recovery record + rr[N] Add the data recovery record. + + Recovery record is the data area, optionally added to archive + and containing error correction codes, namely Reed-Solomon codes + for RAR 5.0 archive format. While it increases the archive size, + it helps to recover archived files in case of disk failure + or data loss of other kind, provided that damage is not too + severe. Such recovery can be done with 'R' repair command. + + Optional 'N' parameter defines the recovery record size + as a percent of archive size. If it is omitted, 3% is assumed. + Maximum allowed recovery record size is 1000%. Larger recovery + records are processed slower both when creating and repairing. + Due to service data overhead, the actual resulting recovery record size only approximately matches the user defined percent and difference is larger for smaller archives. - Maximum allowed RAR 5.0 recovery record size is 1000%. - Larger recovery records are processed slower both when creating - and repairing. - - RAR 5.0 recovery record is more resistant to damage of recovery - record itself and can utilize a partially corrupt recovery - record data. Note, though, that 'R' repair command does not fix - broken blocks in recovery record. Only file data are corrected. - After successful archive repair, you may need to create a new - recovery record for saved files. - - If you use the plain 'rr' command without optional parameter, - RAR will set the recovery record size to 3% of archive size - by default. + In case of a single continuous damage, typically it is possible + to restore slightly less data than recovery record size. + Recoverable data size can be lower for multiple damages. + + If a recovery record is partially broken, its remaining valid data + still can be utilized to repair files. Repair command does not + fix broken blocks in recovery record itself, only file data + is corrected. After successful archive repair, you may need to + create a new recovery record for rescued files. While the recovery record improves chances to repair damaged archives, it does not guarantee the successful recovery. @@ -523,7 +489,7 @@ Example: - rar rr5p arcname + rar rr5 arcname add the recovery record of 5% of archive size. @@ -548,7 +514,7 @@ 3 missing volumes. If the number of .rev files is less than the number of missing volumes, reconstructing is impossible. The total number of usual and recovery volumes must not - exceed 255 for RAR 4.x and 65535 for RAR 5.0 archive format. + exceed 65535. Original RAR volumes must not be modified after creating recovery volumes. Recovery algorithm uses data stored both @@ -565,10 +531,9 @@ than media size. The optional parameter specifies a number of recovery - volumes to create. It must be less than the total number of - RAR volumes in the set for RAR 4.x and must not be larger - than tenfold amount of RAR volumes for RAR 5.0 format. - Values exceeding the threshold are adjusted automatically. + volumes to create. It must not be larger than tenfold amount + of RAR volumes. Values exceeding the threshold are adjusted + automatically. You may also append a percent or 'p' character to this parameter, in such case the number of creating .rev files will be equal to @@ -591,9 +556,11 @@ s[name] Convert archive to SFX. The archive is merged with a SFX module (using a module in file default.sfx or specified in the switch). - In the Windows version default.sfx should be placed in the - same directory as the rar.exe, in Unix - in the user's - home directory, in /usr/lib or /usr/local/lib. + In Windows version default.sfx should be placed in the same + directory as the rar.exe, in Unix - in the user's home directory, + in /usr/lib or /usr/local/lib. + + Windows version uses default32.sfx name for 32-bit SFX module. s- Remove SFX module from the already existing SFX archive. RAR creates a new archive without SFX module, the original @@ -1212,8 +1179,7 @@ file contents based on checksums. Do not expect such encrypted file checksums to match usual CRC32 and BLAKE2sp values. - This switch is supported only by RAR 5.0 format, so you - need to use -ma switch with it. + This switch is supported only by RAR 5.0 format. You can see checksums of archived files using 'vt' or 'lt' commands. @@ -1221,7 +1187,7 @@ Example: - rar a -ma -htb lists.rar *.lst + rar a -htb lists.rar *.lst will add *.lst to lists.rar using BLAKE2sp for file checksums. @@ -1410,163 +1376,132 @@ (normal compression). - -ma[4|5] - Specify a version of archiving format. - - By default RAR creates archives in RAR 5.0 format. - Use -ma4 to create RAR 4.x archives. - Use -ma5 or just -ma in case you need to override -ma4 saved - in configuration and force RAR to use RAR 5.0 format. - - This switch is used only when creating a new archive. - It is ignored when updating an existing archive. - - -mc Set advanced compression parameters. - This switch is intended mainly for benchmarking and - experiments. In the real environment it is usually better - to allow RAR to select optimal parameters automatically. - Please note that improper use of this switch may lead - to very serious performance and compression loss, so use - it only if you clearly understand what you do. - - It has the following syntax: + Improper use of this switch may lead to suboptimal performance + and compression. This switch has the following syntax: - -mc[param1][:param2][module][+ or -] + -mc[channels][mode][+ or -] - where is the one character field denoting a part - of the compression algorithm, which has to be configured. + where is the single character field defining + the compression algorithm to be configured. - It may have the following values: + Possible values are: - A - audio compression; - C - true color (RGB) data compression; D - delta compression; E - x86 executable compression; - T - text compression. - - RAR 5.0 archive format supports only 'D' and 'E' values. + L - long range search; + X - exhaustive search. '+' sign at the end of switch applies the selected algorithm - module to all processed data, '-' disables the module at all. - If no sign is specified, RAR will choose modules automatically, - based on data and the current compression method. - - Switch -mc- disables all optional modules and allows only - the general compression algorithm. - - and are module dependent parameters - described below. - + to all processed data, '-' disables it completely. + If no sign is specified, RAR chooses modes automatically, + based on data and current compression method. + Switch -mc- disables all modes. - Audio compression, delta compression: + parameter is used by delta compression and ignored + by other modes. Available modes are described below. - is a number of byte channels (can be 1 - 31). - RAR splits multibyte channels to bytes, for example, - two 16-bit audio channels are considered by RAR as four - channels one byte each. - is ignored. + Delta compression + Splits data to several single byte channels and calculates + the difference between them. Can improve the compression ratio + of table data. is the number of byte channels + from 1 to 31. - x86 Intel executable compression, true color (RGB) data - compression: - and are ignored. + x86 executable compression + Can improve the compression ratio of 32 and 64 bit x86 executables. - Text compression: - Text compression algorithm provides noticeably higher compression - on plain text data. But it cannot utilize several CPU cores - efficiently resulting in slower compression time comparing to - general algorithm in multicore and multiprocessor environment. - Also its decompression speed is much slower than in general - algorithm regardless of CPU cores number. This is why - the text compression is disabled by default. You can specify - -mct switch to allow RAR to select this algorithm automatically - for suitable data. Switch -mct+ will force use of the text - compression for all data. + Long range search - Switch -mct can also include and , so its - full syntax is -mc[param1][:param2]t[+ or -]. - - is the order of PPM algorithm (can be 2 - 63). - Usually a higher value slightly increases the compression ratio - of redundant data, but only if enough memory is available - to PPM. In case of lack of memory the result may be negative. - Higher order values decrease both compression and decompression - speed. + Enables the search algorithm designed to efficiently locate + longer and more distant repeated data blocks. It can helps to + improve the compression ratio and sometimes speed for redundant + data like big text files. This algorithm increases memory + requirements when archiving, but doesn't affect extraction + memory requirements or speed. + + If neither -mcl+ nor -mcl- are specified, RAR applies the long + range search depending on the compression method, dictionary size + and other parameters. This algorithm is required and enabled + automatically for dictionaries exceeding 4 GB, where it can't be + turned off with -mcl- switch. + + Long range search mode is applicable to -m2..-m5 compression + methods and ignored for -m1. - is memory in megabytes allocated for PPM (1-128). - Higher values may increase the compression ratio, but note - that PPM uses the equal memory size both to compress and - decompress, so if you allocate too much memory when creating - an archive, other people may have problems when decompressing - it on a computer with less memory installed. Decompression - will be still possible using virtual memory, but it may - become very slow. + Exhaustive search - Examples: + Enables much slower and more exhaustive repeated data search + and compression algorithm. It might provide the additional + compression gain on some types of redundant data, but at much + lower speed. Long range search is needed to implement this mode + efficiently, so -mcx activates it automatically. - 1) switch -mc1a+ forces use of 8-bit mono audio compression - for all data. - 2) switch -mc10:40t+ forces use of text compression - algorithm for all data, sets the compression order to 10 - and allocates 40 MB memory. + Example: - 3) switch -mc12t sets the text compression order to 12, - when the text compression is used, but leaves to RAR to - decide when to use it. + RAR a -s -md1g -mcx texts *.txt - 4) switches -mct -mcd- allow RAR to apply the text compression - to suitable data and disable the delta compression. + create a solid archive with 1 GB dictionary and exhaustive search. - -md[k,m,g] + -md[x][k,m,g] Select the dictionary size. Sliding dictionary is the memory area used by compression algorithm to find and compress repeated data patterns. - If size of file being compressed (or total files size in case - of solid archive) is larger than dictionary size, increasing + If size of file to compress, or total files size in case + of solid archive, is larger than dictionary size, increasing the dictionary is likely to increase the compression ratio, reduce the archiving speed and increase memory requirements. - For RAR 4.x archive format the dictionary size can be: - 64 KB, 128 KB, 256 KB, 512 KB, 1 MB, 2 MB, 4 MB. - For RAR 5.0 archive format the dictionary size can be: 128 KB, 256 KB, 512 KB, 1 MB, 2 MB, 4 MB, 8 MB, 16 MB, - 32 MB, 64 MB, 128 MB, 256 MB, 512 MB, 1 GB. + 32 MB, 64 MB, 128 MB, 256 MB, 512 MB, 1 GB, 2 GB, 4 GB. - You can use 'k', 'm' and 'g' modifiers to specify the size - in kilo-, mega- and gigabytes, like -md64m for 64 MB dictionary. - If no modifier is specified, megabytes are assumed, - so -md64m and -md64 are equal. - - When archiving, RAR needs about 6x memory of specified - dictionary size, so 512 MB and 1 GB sizes are available - in 64 bit RAR version only. When extracting, slightly more - than a single dictionary size is allocated, so both 32 - and 64 bit versions can unpack archives with all dictionaries - up to and including 1 GB. + RAR 7.0 extends the maximum dictionary size up to 64 GB + and permits not power of 2 sizes for dictionaries exceeding 4 GB. + Such archives can be unpacked by RAR 7.0 and newer. + + By default, RAR refuses to unpack archives with dictionary + exceeding 4 GB. It is done to prevent the unexpected large memory + allocation. Use -md or -mdx to allow unpacking + dictionaries up to and including the specified size. + Unlike -md, -mdx is applied to extraction only + and can be added to RAR environment variable, not affecting + archiving commands. + + 'k', 'm' and 'g' modifiers placed after the size, set kilobyte, + megabyte and gigabyte units, like -md64m for 64 MB dictionary. + If no modifier is present, megabytes are assumed for -md + and gigabytes for -mdx switch, so -md64m and -md64 + or -mdx8 and -mdx8g are equal. + + Compression memory requirements vary depending on the dictionary + size and presence of long range search -mcl switch. + Rough estimate is 7x of dictionary size for 1 GB and 1.5x + for 64 GB dictionary. + + When extracting, slightly more than a single dictionary size + is allocated. If size of all source files for solid archive or size of largest source file for non-solid archive is at least twice less than dictionary size, RAR can reduce the dictionary size. It helps to lower memory usage without decreasing compression. - Default sliding dictionary size is 4 MB for RAR 4.x - and 32 MB for RAR 5.0 archive format. + Default sliding dictionary size is 32 MB. Example: - RAR a -s -ma -md128 lib *.dll + RAR a -s -md128 lib *.dll create a solid archive in RAR 5.0 format with 128 MB dictionary. @@ -1746,7 +1681,7 @@ Examples: - 1) rar a -oi -ma archive + 1) rar a -oi archive Save contents of current directory to archive.rar. Store identical files as references. @@ -1757,15 +1692,15 @@ 1000000 bytes, found in c:\photo and its subdirectories. - -ol[a] Process symbolic links as the link [absolute paths] + -ol[a,-] + Process symbolic links as the link [absolute paths, skip] Save symbolic links as links, so file or directory contents is not archived. In Windows version it also saves reparse points as links. Such archive entries are restored as symbolic links or reparse points when extracting. - Supported both for RAR 4.x and RAR 5.0 archives in RAR for Unix - and only for RAR 5.0 archives in RAR for Windows. + Supported both in Unix and Windows RAR versions. In Windows you may need to run RAR as administrator to create symbolic links when extracting. @@ -1783,7 +1718,9 @@ are sure that archive contents is safe, such as your own backup. Links that are considered safe by RAR are extracted always - regardless of -ol or -ola switch. + regardless of -ol or -ola switch, unless -ol- is specified. + + Switch -ol- skips symbolic links when archiving or extracting. -oni Allow potentially incompatible names. @@ -1834,6 +1771,11 @@ Streams are not saved for NTFS encrypted files. + Unlike GUI WinRAR, the console RAR doesn't propagate the archive + Mark of the Web stream to extracted files. It unpacks archived + Zone.Identifier streams as is, regardless of host archive + Zone.Identifier stream presence. + -ow Use this switch when archiving to save file security information and when extracting to restore it. @@ -1923,6 +1865,10 @@ and do not care about archive open speed in different programs, specify -qo- to exclude the quick open information completely. + Switch -qo- also prohibits access to quick open information + in existing archives, such as when extracting or listing + their contents. + If you wish to measure the performance effect of this switch, be sure that archive contents is not stored in a disk cache. No real disk seeks are performed for cached archive file, @@ -2008,9 +1954,9 @@ rar a -ri0:10 backup *.* - -rr[N] Add data recovery record. This switch is used when creating - or modifying an archive to add a data recovery record to - the archive. See the 'rr[N]' command description for details. + -rr[N] Add the data recovery record. This switch is used when creating + or modifying an archive to add the data recovery record to + archive. See 'rr[N]' command description for details. -rv[N] Create recovery volumes. This switch is used when creating @@ -2034,14 +1980,13 @@ Example: - create solid archive sources.rar with 512 KB dictionary, - recursing all directories, starting with the current directory. - Add only .asm files: + add all *.c and *.h files from the current directory to + the solid archive sources.rar: - rar a -s -md512 sources.rar *.asm -r + rar a -s sources.rar *.c *.h - -s Create solid groups using file count + -s Create solid groups using the file count Similar to -s, but resets solid statistics after compressing files. Usually decreases compression, but also @@ -2110,9 +2055,11 @@ Create SFX archives. If this switch is used when creating a new archive, a Self-Extracting archive (using a module in file default.sfx or specified in the switch) would be created. - In the Windows version default.sfx should be placed in the - same directory as the rar.exe, in Unix - in the user's - home directory, in /usr/lib or /usr/local/lib. + In Windows version default.sfx should be placed in the same + directory as the rar.exe, in Unix - in the user's home directory, + in /usr/lib or /usr/local/lib. + + Windows version uses default32.sfx name for 32-bit SFX module. Example: @@ -2156,16 +2103,26 @@ type docs.rar | rar x -si -o+ -pmypwd dummy docs\ - -sl + -sl[b|B|k|K|m|M|g|G|t|T] Process only those files, which size is less than specified in parameter of this switch. - Parameter must be specified in bytes. + + Unit type character following the size value can be 'b' or 'B' + for bytes, 'k' for kilobytes, 'K' for thousands of bytes, + 'm' for megabytes, 'M' for millions of bytes, 'g' for gigabytes, + 'G' for billions of bytes, 't' for terabytes, 'T' for trillions + of bytes. If this character is not present, bytes are assumed. - -sm + -sm[b|B|k|K|m|M|g|G|t|T] Process only those files, which size is more than specified in parameter of this switch. - Parameter must be specified in bytes. + + Unit type character following the size value can be 'b' or 'B' + for bytes, 'k' for kilobytes, 'K' for thousands of bytes, + 'm' for megabytes, 'M' for millions of bytes, 'g' for gigabytes, + 'G' for billions of bytes, 't' for terabytes, 'T' for trillions + of bytes. If this character is not present, bytes are assumed. -sv Create independent solid volumes @@ -2298,25 +2255,17 @@ are assumed. Append '+' to store a file time with maximum possible precision. - Concrete value depends on a operating system and file system - and can be up 100 nanoseconds in Windows and 1 nanosecond - in Unix. Append '1' to set 1 second precision or '-' to not save - a file time. If '+', '-' or '1' are not present, '+' is assumed, + The exact value depends on the particular operating system + also as the file system and can be up to 100 nanoseconds + in Windows and 1 nanosecond in Unix. Append '1' to set 1 second + precision or '-' to not save a file time, such as -ts- to omit + all 3 times. If '+', '-' or '1' are not present, '+' is assumed, so -ts+ and -ts both save all three high precision times. All stored times for same file always have the same precision. If different precisions are specified, such as -tsm1 -tsc+, common one is selected. - RAR 4.x archives always contain the modification time - and for RAR 4.x archive -tsm- still saves the modification time - with the lowest possible 2 second precision. Two other times - can be disabled. RAR 5.0 archives allow to omit any file time - including modification, so unpacked files will have the current - system time. Switches -tsm- -tsc- -tsa- or just -ts- will store - a low precision modification time for RAR 4.x and no file time - for RAR 5.0 archive. - If -ts switch is not specified, RAR stores the high precision modification time and omits two other times. @@ -2391,13 +2340,15 @@ specified volume. - -v[k|b|m|M|g|G] - Create volumes with size=*1000 [*1024 | *1]. - By default this switch uses as thousands (1000) of bytes - (not 1024 x bytes). You may also enter the size in kilobytes - using the symbol 'k', in bytes using the symbol 'b', - megabytes - 'm', millions of bytes - 'M', gigabytes - 'g', - billions (milliards) of bytes - 'G'. + -v[b|B|k|K|m|M|g|G|t|T] + Create volumes of the specified size. + + Unit type character following the size value can be 'b' or 'B' + for bytes, 'k' for kilobytes, 'K' for thousands of bytes, + 'm' for megabytes, 'M' for millions of bytes, 'g' for gigabytes, + 'G' for billions of bytes, 't' for terabytes, 'T' for trillions + of bytes. If this character is not present, the size value + is treated as thousands of bytes If the size is omitted, autodetection will be used. @@ -2421,13 +2372,14 @@ At this moment in time, you should change the disks. Answering 'A' will cause all volumes to be created without a pause. - By default RAR volumes have names like 'volname.partNNN.rar', - where NNN is the volume number. For RAR 4.x archive format - using -vn switch it is possible to select another, - extension based naming scheme, where the first volume file - in a multi-volume set has the extension .rar, following - volumes are numbered from .r00 to .r99. RAR 5.0 archives - do not support -vn and extension based names. + RAR volumes have names like 'volname.partNNN.rar', where NNN + is the volume number. + + Volumes created by older RAR versions could use the another naming + scheme, where the first volume file in a multi-volume set had + .rar extension, followed by volumes with extensions from .r00 to + .r99. RAR can unpack such volumes, but doesn't use the extension + based names for new archives. When extracting or testing a multi-volume archive you must use only the first volume name. If there is no next volume @@ -2503,17 +2455,6 @@ either is present in archive or will be created later. - -vn Use the old style volume naming scheme - - By default RAR volumes have names like 'volname.partNNN.rar', - where NNN is the volume number. For RAR 4.x archive format - using -vn switch it is possible to select another, - extension based naming scheme, where the first volume file - in a multi-volume set has the extension .rar, following - volumes are numbered from .r00 to .r99. RAR 5.0 archives - do not support -vn and extension based names. - - -vp Pause before each volume By default RAR asks for confirmation before processing @@ -2529,7 +2470,7 @@ RAR creates temporary files in some operations like archive modification. This switch can be used to specify the directory - for such temporary files. This directory must be already exist. + for such temporary files. This directory must already exist. Example: @@ -2680,7 +2621,7 @@ Copyrights - (c) 1993-2023 Alexander Roshal + (c) 1993-2024 Alexander Roshal diff -Nru rar-6.23/rarfiles.lst rar-7.01/rarfiles.lst --- rar-6.23/rarfiles.lst 2023-08-01 09:28:30.000000000 +0000 +++ rar-7.01/rarfiles.lst 2024-05-12 10:19:40.000000000 +0000 @@ -70,6 +70,7 @@ *.tif *.png *.jpg +*.jxl *.chm *.pdf *.cab @@ -83,9 +84,13 @@ *.gz *.bz2 *.xz +*.zst +*.zstd *.jar +*.avif *.fla *.flac +*.heif *.ape *.bik *.mkv Binary files /srv/release.debian.org/tmp/LGH83v_Alg/rar-6.23/unrar and /srv/release.debian.org/tmp/zw1XZgowhC/rar-7.01/unrar differ diff -Nru rar-6.23/whatsnew.txt rar-7.01/whatsnew.txt --- rar-6.23/whatsnew.txt 2023-08-01 09:28:30.000000000 +0000 +++ rar-7.01/whatsnew.txt 2024-05-12 10:19:40.000000000 +0000 @@ -1,6 +1,111 @@ RAR - What's new in the latest version + Version 7.01 + + 1. Bugs fixed: + + a) updating an encrypted file in a solid RAR archive produced + a corrupt archive if updated file was the first in archive, + no password was specified when starting updating and file name + encryption in the updated archive wasn't enabled; + + b) fixed a possible crash in Unix RAR and UnRAR when unpacking + a corrupt RAR archive. We are thankful to Matteo Marini + for reporting this bug; + + c) switch -ep4 duplicated the specified path instead of excluding it + when extracting. + + + Version 7.00 + + 1. Compression dictionary sizes larger than 1 GB are supported + for RAR archive format. Depending on the amount of physically + available memory, dictionary up to 64 GB can be selected. + + Not power of 2 dictionary sizes can be specified for dictionaries + exceeding 4 GB. So we are not limited to 4, 8, 16, 32, 64 series + and can use values like 5 GB or 22 GB. + + Archives with dictionaries exceeding 4 GB can be unpacked only + by RAR 7.0 or newer. + + Increasing the dictionary size can improve the compression ratio + for large files with distant repeated blocks, like virtual machine + disk images. It also can be efficient for sets of large similar files + in a solid archive, such as a collection of software ISO images + differing by version or localization. + + 2. By default RAR refuses to unpack archives with dictionary exceeding + 4 GB. It is done to prevent the unexpected excessive memory allocation. + + Use -md or -mdx to allow unpacking dictionaries up to + and including the specified size. Unlike -md, -mdx + is applied to extraction only and can be added to RAR environment + variable, not affecting archiving commands. + + 3. Alternate search algorithm, optimized to locate longer and more distant + repeated data blocks, can be used when creating RAR archives. + It helps to improve the compression ratio and sometimes speed + for redundant data like big text files. + + It increases memory usage and might reduce the compression speed + for some types of data. It can be turned on or off with + with -mcl[+|-] switch. If -mcl is not present, RAR applies the long + range search depending on the compression method, dictionary size + and other parameters. + + This algorithm is required for dictionaries exceeding 4 GB + and turning it off is ignored for such dictionaries. + + 4. Much slower and more exhaustive repeated data search and compression + algorithm can be enabled with -mcx switch. It might provide + the additional compression gain for some types of redundant data, + but at much lower compression speed. + + Long range search is needed to implement this mode efficiently, + so the exhaustive search option activates it automatically. + + Both long range and exhaustive search option do not affect + the compatibility of created archives. So if dictionary size + is in 128 KB - 4 GB range, archives created with these search options + can be unpacked by all RAR versions beginning from 5.0. + + 5. Maximum path length limit is increased from 2047 to 65535 characters. + + 6. Creating archives in RAR 4.x format isn't supported anymore. + Options and switches specific for this format are removed. + It doesn't affect RAR 4.x archives decompression, which is included + into RAR. + + 7. Switch -ol- prohibits archiving and extracting symbolic links. + + 8. Switches -sl[u] and -sm[u] recognize [k|K|m|M|g|G|t|T] + size units for kilobytes, thousands of bytes, megabytes, millions + of bytes, gigabytes, billions of bytes, terabytes, trillions of bytes. + If unit character is 'b', 'B' or not present, bytes are assumed. + + Previously these switches accepted bytes only. + + 9. Switch -v[unit] recognizes 't' and 'T' as terabytes and + trillions of bytes for volume size units. + + 10. Proper progress is displayed when compressing symbolic link targets. + + + Version 6.24 + + 1. Bugs fixed: + + a) extraction command dereferenced a null pointer and crashed + when processing a zero length archive name in the archive metadata + stored with -am switch. + + We are thankful to Radoslaw Madej from Check Point software + for reporting this issue. + + Version 6.23 1. Bugs fixed: