Script 'mail_helper' called by obssrc Hello community, here is the log from the commit of package fsarchiver for openSUSE:Factory checked in at 2024-12-16 19:17:44 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/fsarchiver (Old) and /work/SRC/openSUSE:Factory/.fsarchiver.new.29675 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "fsarchiver" Mon Dec 16 19:17:44 2024 rev:30 rq:1231374 version:0.8.8 Changes: -------- --- /work/SRC/openSUSE:Factory/fsarchiver/fsarchiver.changes 2024-02-26 19:47:41.610903384 +0100 +++ /work/SRC/openSUSE:Factory/.fsarchiver.new.29675/fsarchiver.changes 2024-12-16 19:17:55.124409877 +0100 @@ -1,0 +2,7 @@ +Mon Dec 16 10:54:10 UTC 2024 - Michael Vetter <[email protected]> + +- Update to 0.8.8: + * Provide compatibility with e2fsprogs >= 1.47.2 (#154) + * Accept -j arguments greater than FSA_MAX_COMPJOBS (#146) + +------------------------------------------------------------------- Old: ---- fsarchiver-0.8.7.tar.gz New: ---- fsarchiver-0.8.8.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ fsarchiver.spec ++++++ --- /var/tmp/diff_new_pack.MvAbpP/_old 2024-12-16 19:17:55.856440272 +0100 +++ /var/tmp/diff_new_pack.MvAbpP/_new 2024-12-16 19:17:55.860440438 +0100 @@ -1,7 +1,7 @@ # # spec file for package fsarchiver # -# Copyright (c) 2023 SUSE LLC +# Copyright (c) 2024 SUSE LLC # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -17,7 +17,7 @@ Name: fsarchiver -Version: 0.8.7 +Version: 0.8.8 Release: 0 Summary: Filesystem Archiver License: GPL-2.0-only ++++++ fsarchiver-0.8.7.tar.gz -> fsarchiver-0.8.8.tar.gz ++++++ ++++ 7211 lines of diff (skipped) ++++ retrying with extended exclude list diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/fsarchiver-0.8.7/ChangeLog new/fsarchiver-0.8.8/ChangeLog --- old/fsarchiver-0.8.7/ChangeLog 2023-03-19 14:53:17.000000000 +0100 +++ new/fsarchiver-0.8.8/ChangeLog 2024-12-14 10:13:37.000000000 +0100 @@ -1,5 +1,8 @@ fsarchiver: Filesystem Archiver for Linux [http://www.fsarchiver.org] ===================================================================== +* 0.8.8 (2024-12-14): + - Provide compatibility with e2fsprogs >= 1.47.2 (#154) + - Accept -j arguments greater than FSA_MAX_COMPJOBS (#146) * 0.8.7 (2023-03-19): - Implement support for option "uuid=" for vfat (Marcos Mello) - Update list of btrfs supported features (Marcos Mello) diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/fsarchiver-0.8.7/INSTALL new/fsarchiver-0.8.8/INSTALL --- old/fsarchiver-0.8.7/INSTALL 2023-03-19 14:56:47.000000000 +0100 +++ new/fsarchiver-0.8.8/INSTALL 2024-12-14 10:28:34.000000000 +0100 @@ -1,177 +1,177 @@ Installation Instructions ************************* - Copyright (C) 1994-1996, 1999-2002, 2004-2017, 2020-2021 Free -Software Foundation, Inc. - - Copying and distribution of this file, with or without modification, -are permitted in any medium without royalty provided the copyright -notice and this notice are preserved. This file is offered as-is, -without warranty of any kind. - Basic Installation ================== - Briefly, the shell command './configure && make && make install' -should configure, build, and install this package. The following -more-detailed instructions are generic; see the 'README' file for -instructions specific to this package. Some packages provide this -'INSTALL' file but do not implement all of the features documented -below. The lack of an optional feature in a given package is not -necessarily a bug. More recommendations for GNU packages can be found -in *note Makefile Conventions: (standards)Makefile Conventions. + The following shell commands: - The 'configure' shell script attempts to guess correct values for + test -f configure || ./bootstrap + ./configure + make + make install + +should configure, build, and install this package. The first line, +which bootstraps, is intended for developers; when building from +distribution tarballs it does nothing and can be skipped. + + The following more-detailed instructions are generic; see the +âREADMEâ file for instructions specific to this package. Some packages +provide this âINSTALLâ file but do not implement all of the features +documented below. The lack of an optional feature in a given package is +not necessarily a bug. More recommendations for GNU packages can be +found in the GNU Coding Standards. + + Many packages have scripts meant for developers instead of ordinary +builders, as they may use developer tools that are less commonly +installed, or they may access the network, which has privacy +implications. If the âbootstrapâ shell script exists, it attempts to +build the âconfigureâ shell script and related files, possibly using +developer tools or the network. Because the output of âbootstrapâ is +system-independent, it is normally run by a package developer so that +its output can be put into the distribution tarball and ordinary +builders and users need not run âbootstrapâ. Some packages have +commands like â./autopull.shâ and â./autogen.shâ that you can run +instead of â./bootstrapâ, for more fine-grained control over +bootstrapping. + + The âconfigureâ shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses -those values to create a 'Makefile' in each directory of the package. -It may also create one or more '.h' files containing system-dependent -definitions. Finally, it creates a shell script 'config.status' that +those values to create a âMakefileâ in each directory of the package. +It may also create one or more â.hâ files containing system-dependent +definitions. Finally, it creates a shell script âconfig.statusâ that you can run in the future to recreate the current configuration, and a -file 'config.log' containing compiler output (useful mainly for -debugging 'configure'). +file âconfig.logâ containing output useful for debugging âconfigureâ. - It can also use an optional file (typically called 'config.cache' and -enabled with '--cache-file=config.cache' or simply '-C') that saves the + It can also use an optional file (typically called âconfig.cacheâ and +enabled with â--cache-file=config.cacheâ or simply â-Câ) that saves the results of its tests to speed up reconfiguring. Caching is disabled by default to prevent problems with accidental use of stale cache files. If you need to do unusual things to compile the package, please try -to figure out how 'configure' could check whether to do them, and mail -diffs or instructions to the address given in the 'README' so they can +to figure out how âconfigureâ could check whether to do them, and mail +diffs or instructions to the address given in the âREADMEâ so they can be considered for the next release. If you are using the cache, and at -some point 'config.cache' contains results you don't want to keep, you +some point âconfig.cacheâ contains results you donât want to keep, you may remove or edit it. - The file 'configure.ac' (or 'configure.in') is used to create -'configure' by a program called 'autoconf'. You need 'configure.ac' if -you want to change it or regenerate 'configure' using a newer version of -'autoconf'. + The âautoconfâ program generates âconfigureâ from the file +âconfigure.acâ. Normally you should edit âconfigure.acâ instead of +editing âconfigureâ directly. The simplest way to compile this package is: - 1. 'cd' to the directory containing the package's source code and type - './configure' to configure the package for your system. + 1. âcdâ to the directory containing the packageâs source code. + + 2. If this is a developer checkout and file âconfigureâ does not yet + exist, type â./bootstrapâ to create it. You may need special + developer tools and network access to bootstrap, and the network + access may have privacy implications. - Running 'configure' might take a while. While running, it prints - some messages telling which features it is checking for. + 3. Type â./configureâ to configure the package for your system. This + might take a while. While running, âconfigureâ prints messages + telling which features it is checking for. - 2. Type 'make' to compile the package. + 4. Type âmakeâ to compile the package. - 3. Optionally, type 'make check' to run any self-tests that come with + 5. Optionally, type âmake checkâ to run any self-tests that come with the package, generally using the just-built uninstalled binaries. - 4. Type 'make install' to install the programs and any data files and + 6. Type âmake installâ to install the programs and any data files and documentation. When installing into a prefix owned by root, it is recommended that the package be configured and built as a regular - user, and only the 'make install' phase executed with root + user, and only the âmake installâ phase executed with root privileges. - 5. Optionally, type 'make installcheck' to repeat any self-tests, but + 7. Optionally, type âmake installcheckâ to repeat any self-tests, but this time using the binaries in their final installed location. This target does not install anything. Running this target as a - regular user, particularly if the prior 'make install' required + regular user, particularly if the prior âmake installâ required root privileges, verifies that the installation completed correctly. - 6. You can remove the program binaries and object files from the - source code directory by typing 'make clean'. To also remove the - files that 'configure' created (so you can compile the package for - a different kind of computer), type 'make distclean'. There is - also a 'make maintainer-clean' target, but that is intended mainly - for the package's developers. If you use it, you may have to get - all sorts of other programs in order to regenerate files that came - with the distribution. - - 7. Often, you can also type 'make uninstall' to remove the installed - files again. In practice, not all packages have tested that - uninstallation works correctly, even though it is required by the - GNU Coding Standards. - - 8. Some packages, particularly those that use Automake, provide 'make - distcheck', which can by used by developers to test that all other - targets like 'make install' and 'make uninstall' work correctly. - This target is generally not run by end users. + 8. You can remove the program binaries and object files from the + source code directory by typing âmake cleanâ. To also remove the + files that âconfigureâ created (so you can compile the package for + a different kind of computer), type âmake distcleanâ. There is + also a âmake maintainer-cleanâ target, but that is intended mainly + for the packageâs developers. If you use it, you may have to + bootstrap again. + + 9. If the package follows the GNU Coding Standards, you can type âmake + uninstallâ to remove the installed files. Compilers and Options ===================== Some systems require unusual options for compilation or linking that -the 'configure' script does not know about. Run './configure --help' +the âconfigureâ script does not know about. Run â./configure --helpâ for details on some of the pertinent environment variables. - You can give 'configure' initial values for configuration parameters + You can give âconfigureâ initial values for configuration parameters by setting variables in the command line or in the environment. Here is an example: - ./configure CC=c99 CFLAGS=-g LIBS=-lposix + ./configure CC=gcc CFLAGS=-g LIBS=-lposix - *Note Defining Variables::, for more details. + See âDefining Variablesâ for more details. Compiling For Multiple Architectures ==================================== You can compile the package for more than one kind of computer at the -same time, by placing the object files for each architecture in their -own directory. To do this, you can use GNU 'make'. 'cd' to the -directory where you want the object files and executables to go and run -the 'configure' script. 'configure' automatically checks for the source -code in the directory that 'configure' is in and in '..'. This is known -as a "VPATH" build. - - With a non-GNU 'make', it is safer to compile the package for one -architecture at a time in the source code directory. After you have -installed the package for one architecture, use 'make distclean' before -reconfiguring for another architecture. - - On MacOS X 10.5 and later systems, you can create libraries and -executables that work on multiple system types--known as "fat" or -"universal" binaries--by specifying multiple '-arch' options to the -compiler but only a single '-arch' option to the preprocessor. Like -this: - - ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ - CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \ - CPP="gcc -E" CXXCPP="g++ -E" - - This is not guaranteed to produce working output in all cases, you -may have to build one architecture at a time and combine the results -using the 'lipo' tool if you have problems. +same time, by placing the object files for each system in their own +directory. To do this, you can use GNU âmakeâ. âcdâ to the directory +where you want the object files and executables to go and run the +âconfigureâ script. âconfigureâ automatically checks for the source +code in the directory that âconfigureâ is in and in â..â. This is known +as a âVPATHâ build. + + With a non-GNU âmakeâ, it is safer to compile the package for one +system at a time in the source code directory. After you have installed +the package for one system, use âmake distcleanâ before reconfiguring +for another system. + + Some platforms, notably macOS, support âfatâ or âuniversalâ binaries, +where a single binary can execute on different architectures. On these +platforms you can configure and compile just once, with options specific +to that platform. Installation Names ================== - By default, 'make install' installs the package's commands under -'/usr/local/bin', include files under '/usr/local/include', etc. You -can specify an installation prefix other than '/usr/local' by giving -'configure' the option '--prefix=PREFIX', where PREFIX must be an + By default, âmake installâ installs the packageâs commands under +â/usr/local/binâ, include files under â/usr/local/includeâ, etc. You +can specify an installation prefix other than â/usr/localâ by giving +âconfigureâ the option â--prefix=PREFIXâ, where PREFIX must be an absolute file name. You can specify separate installation prefixes for architecture-specific files and architecture-independent files. If you -pass the option '--exec-prefix=PREFIX' to 'configure', the package uses +pass the option â--exec-prefix=PREFIXâ to âconfigureâ, the package uses PREFIX as the prefix for installing programs and libraries. Documentation and other data files still use the regular prefix. In addition, if you use an unusual directory layout you can give -options like '--bindir=DIR' to specify different values for particular -kinds of files. Run 'configure --help' for a list of the directories +options like â--bindir=DIRâ to specify different values for particular +kinds of files. Run âconfigure --helpâ for a list of the directories you can set and what kinds of files go in them. In general, the default -for these options is expressed in terms of '${prefix}', so that -specifying just '--prefix' will affect all of the other directory +for these options is expressed in terms of â${prefix}â, so that +specifying just â--prefixâ will affect all of the other directory specifications that were not explicitly provided. The most portable way to affect installation locations is to pass the -correct locations to 'configure'; however, many packages provide one or +correct locations to âconfigureâ; however, many packages provide one or both of the following shortcuts of passing variable assignments to the -'make install' command line to change installation locations without +âmake installâ command line to change installation locations without having to reconfigure or recompile. The first method involves providing an override variable for each -affected directory. For example, 'make install -prefix=/alternate/directory' will choose an alternate location for all +affected directory. For example, âmake install +prefix=/alternate/directoryâ will choose an alternate location for all directory configuration variables that were expressed in terms of -'${prefix}'. Any directories that were specified during 'configure', -but not in terms of '${prefix}', must each be overridden at install time +â${prefix}â. Any directories that were specified during âconfigureâ, +but not in terms of â${prefix}â, must each be overridden at install time for the entire installation to be relocated. The approach of makefile variable overrides for each directory variable is required by the GNU Coding Standards, and ideally causes no recompilation. However, some @@ -179,190 +179,187 @@ that end up requiring recompilation when using this method, particularly noticeable in packages that use GNU Libtool. - The second method involves providing the 'DESTDIR' variable. For -example, 'make install DESTDIR=/alternate/directory' will prepend -'/alternate/directory' before all installation names. The approach of -'DESTDIR' overrides is not required by the GNU Coding Standards, and + The second method involves providing the âDESTDIRâ variable. For +example, âmake install DESTDIR=/alternate/directoryâ will prepend +â/alternate/directoryâ before all installation names. The approach of +âDESTDIRâ overrides is not required by the GNU Coding Standards, and does not work on platforms that have drive letters. On the other hand, it does better at avoiding recompilation issues, and works well even -when some directory options were not specified in terms of '${prefix}' -at 'configure' time. +when some directory options were not specified in terms of â${prefix}â +at âconfigureâ time. Optional Features ================= If the package supports it, you can cause programs to be installed -with an extra prefix or suffix on their names by giving 'configure' the -option '--program-prefix=PREFIX' or '--program-suffix=SUFFIX'. +with an extra prefix or suffix on their names by giving âconfigureâ the +option â--program-prefix=PREFIXâ or â--program-suffix=SUFFIXâ. - Some packages pay attention to '--enable-FEATURE' options to -'configure', where FEATURE indicates an optional part of the package. -They may also pay attention to '--with-PACKAGE' options, where PACKAGE -is something like 'gnu-as' or 'x' (for the X Window System). The -'README' should mention any '--enable-' and '--with-' options that the -package recognizes. - - For packages that use the X Window System, 'configure' can usually -find the X include and library files automatically, but if it doesn't, -you can use the 'configure' options '--x-includes=DIR' and -'--x-libraries=DIR' to specify their locations. + Some packages pay attention to â--enable-FEATUREâ and +â--disable-FEATUREâ options to âconfigureâ, where FEATURE indicates an +optional part of the package. They may also pay attention to +â--with-PACKAGEâ and â--without-PACKAGEâ options, where PACKAGE is +something like âgnu-ldâ. â./configure --helpâ should mention the +â--enable-...â and â--with-...â options that the package recognizes. Some packages offer the ability to configure how verbose the -execution of 'make' will be. For these packages, running './configure ---enable-silent-rules' sets the default to minimal output, which can be -overridden with 'make V=1'; while running './configure ---disable-silent-rules' sets the default to verbose, which can be -overridden with 'make V=0'. - -Particular systems -================== - - On HP-UX, the default C compiler is not ANSI C compatible. If GNU CC -is not installed, it is recommended to use the following options in -order to use an ANSI C compiler: - - ./configure CC="cc -Ae -D_XOPEN_SOURCE=500" - -and if that doesn't work, install pre-built binaries of GCC for HP-UX. - - HP-UX 'make' updates targets which have the same timestamps as their -prerequisites, which makes it generally unusable when shipped generated -files such as 'configure' are involved. Use GNU 'make' instead. - - On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot -parse its '<wchar.h>' header file. The option '-nodtk' can be used as a -workaround. If GNU CC is not installed, it is therefore recommended to -try - - ./configure CC="cc" - -and if that doesn't work, try - - ./configure CC="cc -nodtk" - - On Solaris, don't put '/usr/ucb' early in your 'PATH'. This -directory contains several dysfunctional programs; working variants of -these programs are available in '/usr/bin'. So, if you need '/usr/ucb' -in your 'PATH', put it _after_ '/usr/bin'. - - On Haiku, software installed for all users goes in '/boot/common', -not '/usr/local'. It is recommended to use the following options: - - ./configure --prefix=/boot/common +execution of âmakeâ will be. For these packages, running â./configure +--enable-silent-rulesâ sets the default to minimal output, which can be +overridden with âmake V=1â; while running â./configure +--disable-silent-rulesâ sets the default to verbose, which can be +overridden with âmake V=0â. + +Specifying a System Type +======================== + + By default âconfigureâ builds for the current system. To create +binaries that can run on a different system type, specify a +â--host=TYPEâ option along with compiler variables that specify how to +generate object code for TYPE. For example, to create binaries intended +to run on a 64-bit ARM processor: + + ./configure --host=aarch64-linux-gnu \ + CC=aarch64-linux-gnu-gcc \ + CXX=aarch64-linux-gnu-g++ + +If done on a machine that can execute these binaries (e.g., via +âqemu-aarch64â, â$QEMU_LD_PREFIXâ, and Linuxâs âbinfmt_miscâ +capability), the build behaves like a native build. Otherwise it is a +cross-build: âconfigureâ will make cross-compilation guesses instead of +running test programs, and âmake checkâ will not work. + + A system type can either be a short name like âmingw64â, or a +canonical name like âx86_64-pc-linux-gnuâ. Canonical names have the +form CPU-COMPANY-SYSTEM where SYSTEM is either OS or KERNEL-OS. To +canonicalize and validate a system type, you can run the command +âconfig.subâ, which is often squirreled away in a subdirectory like +âbuild-auxâ. For example: + + $ build-aux/config.sub arm64-linux + aarch64-unknown-linux-gnu + $ build-aux/config.sub riscv-lnx + Invalid configuration 'riscv-lnx': OS 'lnx' not recognized + +You can look at the âconfig.subâ file to see which types are recognized. +If the file is absent, this package does not need the system type. + + If âconfigureâ fails with the diagnostic âcannot guess build typeâ. +âconfig.subâ did not recognize your systemâs type. In this case, first +fetch the newest versions of these files from the GNU config package +(https://savannah.gnu.org/projects/config). If that fixes things, +please report it to the maintainers of the package containing +âconfigureâ. Otherwise, you can try the configure option â--build=TYPEâ +where TYPE comes close to your system type; also, please report the +problem to <[email protected]>. -Specifying the System Type -========================== - - There may be some features 'configure' cannot figure out -automatically, but needs to determine by the type of machine the package -will run on. Usually, assuming the package is built to be run on the -_same_ architectures, 'configure' can figure that out, but if it prints -a message saying it cannot guess the machine type, give it the -'--build=TYPE' option. TYPE can either be a short name for the system -type, such as 'sun4', or a canonical name which has the form: - - CPU-COMPANY-SYSTEM - -where SYSTEM can have one of these forms: - - OS - KERNEL-OS - - See the file 'config.sub' for the possible values of each field. If -'config.sub' isn't included in this package, then this package doesn't -need to know the machine type. - - If you are _building_ compiler tools for cross-compiling, you should -use the option '--target=TYPE' to select the type of system they will -produce code for. - - If you want to _use_ a cross compiler, that generates code for a -platform different from the build platform, you should specify the -"host" platform (i.e., that on which the generated programs will -eventually be run) with '--host=TYPE'. + For more details about configuring system types, see the Autoconf +documentation. Sharing Defaults ================ - If you want to set default values for 'configure' scripts to share, -you can create a site shell script called 'config.site' that gives -default values for variables like 'CC', 'cache_file', and 'prefix'. -'configure' looks for 'PREFIX/share/config.site' if it exists, then -'PREFIX/etc/config.site' if it exists. Or, you can set the -'CONFIG_SITE' environment variable to the location of the site script. -A warning: not all 'configure' scripts look for a site script. + If you want to set default values for âconfigureâ scripts to share, +you can create a site shell script called âconfig.siteâ that gives +default values for variables like âCCâ, âcache_fileâ, and âprefixâ. +âconfigureâ looks for âPREFIX/share/config.siteâ if it exists, then +âPREFIX/etc/config.siteâ if it exists. Or, you can set the +âCONFIG_SITEâ environment variable to the location of the site script. +A warning: not all âconfigureâ scripts look for a site script. Defining Variables ================== Variables not defined in a site shell script can be set in the -environment passed to 'configure'. However, some packages may run +environment passed to âconfigureâ. However, some packages may run configure again during the build, and the customized values of these variables may be lost. In order to avoid this problem, you should set -them in the 'configure' command line, using 'VAR=value'. For example: +them in the âconfigureâ command line, using âVAR=valueâ. For example: ./configure CC=/usr/local2/bin/gcc -causes the specified 'gcc' to be used as the C compiler (unless it is +causes the specified âgccâ to be used as the C compiler (unless it is overridden in the site shell script). -Unfortunately, this technique does not work for 'CONFIG_SHELL' due to an +Unfortunately, this technique does not work for âCONFIG_SHELLâ due to an Autoconf limitation. Until the limitation is lifted, you can use this workaround: CONFIG_SHELL=/bin/bash ./configure CONFIG_SHELL=/bin/bash -'configure' Invocation +âconfigureâ Invocation ====================== - 'configure' recognizes the following options to control how it + âconfigureâ recognizes the following options to control how it operates. -'--help' -'-h' - Print a summary of all of the options to 'configure', and exit. - -'--help=short' -'--help=recursive' - Print a summary of the options unique to this package's - 'configure', and exit. The 'short' variant lists options used only - in the top level, while the 'recursive' variant lists options also +â--helpâ +â-hâ + Print a summary of all of the options to âconfigureâ, and exit. + +â--help=shortâ +â--help=recursiveâ + Print a summary of the options unique to this packageâs + âconfigureâ, and exit. The âshortâ variant lists options used only + in the top level, while the ârecursiveâ variant lists options also present in any nested packages. -'--version' -'-V' - Print the version of Autoconf used to generate the 'configure' +â--versionâ +â-Vâ + Print the version of Autoconf used to generate the âconfigureâ script, and exit. -'--cache-file=FILE' +â--cache-file=FILEâ Enable the cache: use and save the results of the tests in FILE, - traditionally 'config.cache'. FILE defaults to '/dev/null' to + traditionally âconfig.cacheâ. FILE defaults to â/dev/nullâ to disable caching. -'--config-cache' -'-C' - Alias for '--cache-file=config.cache'. - -'--quiet' -'--silent' -'-q' - Do not print messages saying which checks are being made. To - suppress all normal output, redirect it to '/dev/null' (any error - messages will still be shown). +â--config-cacheâ +â-Câ + Alias for â--cache-file=config.cacheâ. + +â--srcdir=DIRâ + Look for the packageâs source code in directory DIR. Usually + âconfigureâ can determine that directory automatically. -'--srcdir=DIR' - Look for the package's source code in directory DIR. Usually - 'configure' can determine that directory automatically. - -'--prefix=DIR' - Use DIR as the installation prefix. *note Installation Names:: for +â--prefix=DIRâ + Use DIR as the installation prefix. See âInstallation Namesâ for more details, including other options available for fine-tuning the installation locations. -'--no-create' -'-n' +â--host=TYPEâ + Build binaries for system TYPE. See âSpecifying a System Typeâ. + +â--enable-FEATUREâ +â--disable-FEATUREâ + Enable or disable the optional FEATURE. See âOptional Featuresâ. + +â--with-PACKAGEâ +â--without-PACKAGEâ + Use or omit PACKAGE when building. See âOptional Featuresâ. + +â--quietâ +â--silentâ +â-qâ + Do not print messages saying which checks are being made. To + suppress all normal output, redirect it to â/dev/nullâ (any error + messages will still be shown). + +â--no-createâ +â-nâ Run the configure checks, but stop before creating any output files. -'configure' also accepts some other, not widely useful, options. Run -'configure --help' for more details. +âconfigureâ also recognizes several environment variables, and accepts +some other, less widely useful, options. Run âconfigure --helpâ for +more details. + +Copyright notice +================ + + Copyright © 1994â1996, 1999â2002, 2004â2017, 2020â2024 Free Software +Foundation, Inc. + + Copying and distribution of this file, with or without modification, +are permitted in any medium without royalty provided the copyright +notice and this notice are preserved. This file is offered as-is, +without warranty of any kind. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/fsarchiver-0.8.7/compile new/fsarchiver-0.8.8/compile --- old/fsarchiver-0.8.7/compile 2023-03-19 14:56:47.000000000 +0100 +++ new/fsarchiver-0.8.8/compile 2024-12-14 10:28:34.000000000 +0100 @@ -1,9 +1,9 @@ #! /bin/sh # Wrapper for compilers which do not understand '-c -o'. -scriptversion=2018-03-07.03; # UTC +scriptversion=2024-06-19.01; # UTC -# Copyright (C) 1999-2021 Free Software Foundation, Inc. +# Copyright (C) 1999-2024 Free Software Foundation, Inc. # Written by Tom Tromey <[email protected]>. # # This program is free software; you can redistribute it and/or modify @@ -143,7 +143,7 @@ # configure might choose to run compile as 'compile cc -o foo foo.c'. eat=1 case $2 in - *.o | *.[oO][bB][jJ]) + *.o | *.lo | *.[oO][bB][jJ]) func_file_conv "$2" set x "$@" -Fo"$file" shift @@ -248,14 +248,17 @@ right script to run: please start by reading the file 'INSTALL'. Report bugs to <[email protected]>. +GNU Automake home page: <https://www.gnu.org/software/automake/>. +General help using GNU software: <https://www.gnu.org/gethelp/>. EOF exit $? ;; -v | --v*) - echo "compile $scriptversion" + echo "compile (GNU Automake) $scriptversion" exit $? ;; cl | *[/\\]cl | cl.exe | *[/\\]cl.exe | \ + clang-cl | *[/\\]clang-cl | clang-cl.exe | *[/\\]clang-cl.exe | \ icl | *[/\\]icl | icl.exe | *[/\\]icl.exe ) func_cl_wrapper "$@" # Doesn't return... ;; diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/fsarchiver-0.8.7/config.h.in new/fsarchiver-0.8.8/config.h.in --- old/fsarchiver-0.8.7/config.h.in 2023-03-19 14:56:47.000000000 +0100 +++ new/fsarchiver-0.8.8/config.h.in 2024-12-14 10:28:34.000000000 +0100 @@ -15,10 +15,10 @@ /* Define to 1 if you have the <fnmatch.h> header file. */ #undef HAVE_FNMATCH_H -/* Define to 1 if you have the `fstatfs64' function. */ +/* Define to 1 if you have the 'fstatfs64' function. */ #undef HAVE_FSTATFS64 -/* Define to 1 if you have the `fstatvfs64' function. */ +/* Define to 1 if you have the 'fstatvfs64' function. */ #undef HAVE_FSTATVFS64 /* Define to 1 if you have the <gcrypt.h> header file. */ @@ -30,13 +30,13 @@ /* Define to 1 if you have the <inttypes.h> header file. */ #undef HAVE_INTTYPES_H -/* Define to 1 if you have the `pthread' library (-lpthread). */ +/* Define to 1 if you have the 'pthread' library (-lpthread). */ #undef HAVE_LIBPTHREAD -/* Define to 1 if you have the `lstat64' function. */ +/* Define to 1 if you have the 'lstat64' function. */ #undef HAVE_LSTAT64 -/* Define to 1 if you have the `lutimes' function. */ +/* Define to 1 if you have the 'lutimes' function. */ #undef HAVE_LUTIMES /* Define to 1 if you have the <lz4.h> header file. */ @@ -48,16 +48,16 @@ /* Define to 1 if you have the <malloc.h> header file. */ #undef HAVE_MALLOC_H -/* Define to 1 if you have the `mempcpy' function. */ +/* Define to 1 if you have the 'mempcpy' function. */ #undef HAVE_MEMPCPY -/* Define to 1 if you have the `open64' function. */ +/* Define to 1 if you have the 'open64' function. */ #undef HAVE_OPEN64 /* Define to 1 if you have the <pthread.h> header file. */ #undef HAVE_PTHREAD_H -/* Define to 1 if you have the `stat64' function. */ +/* Define to 1 if you have the 'stat64' function. */ #undef HAVE_STAT64 /* Define to 1 if you have the <stdbool.h> header file. */ @@ -72,7 +72,7 @@ /* Define to 1 if you have the <stdlib.h> header file. */ #undef HAVE_STDLIB_H -/* Define to 1 if you have the `strerror' function. */ +/* Define to 1 if you have the 'strerror' function. */ #undef HAVE_STRERROR /* Define to 1 if you have the <strings.h> header file. */ @@ -168,7 +168,7 @@ /* Patch version number */ #undef PACKAGE_VERSION_D -/* Define to 1 if all of the C90 standard headers exist (not just the ones +/* Define to 1 if all of the C89 standard headers exist (not just the ones required in a freestanding environment). This macro is provided for backward compatibility; new code need not use it. */ #undef STDC_HEADERS @@ -179,5 +179,11 @@ /* Number of bits in a file offset, on hosts where this is settable. */ #undef _FILE_OFFSET_BITS -/* Define for large files, on AIX-style hosts. */ +/* Define to 1 on platforms where this makes off_t a 64-bit type. */ #undef _LARGE_FILES + +/* Number of bits in time_t, on hosts where this is settable. */ +#undef _TIME_BITS + +/* Define to 1 on platforms where this makes time_t a 64-bit type. */ +#undef __MINGW_USE_VC2005_COMPAT diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/fsarchiver-0.8.7/configure.ac new/fsarchiver-0.8.8/configure.ac --- old/fsarchiver-0.8.7/configure.ac 2023-03-19 14:53:17.000000000 +0100 +++ new/fsarchiver-0.8.8/configure.ac 2024-12-14 10:19:08.000000000 +0100 @@ -3,12 +3,12 @@ AC_PREREQ(2.59) -AC_INIT([fsarchiver], 0.8.7) -AC_DEFINE([PACKAGE_RELDATE], "2023-03-19", [Define the date of the release]) +AC_INIT([fsarchiver], 0.8.8) +AC_DEFINE([PACKAGE_RELDATE], "2024-12-14", [Define the date of the release]) AC_DEFINE([PACKAGE_FILEFMT], "FsArCh_002", [Define the version of the file format]) AC_DEFINE([PACKAGE_VERSION_A], 0, [Major version number]) AC_DEFINE([PACKAGE_VERSION_B], 8, [Medium version number]) -AC_DEFINE([PACKAGE_VERSION_C], 6, [Minor version number]) +AC_DEFINE([PACKAGE_VERSION_C], 8, [Minor version number]) AC_DEFINE([PACKAGE_VERSION_D], 0, [Patch version number]) AC_CANONICAL_HOST([]) diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/fsarchiver-0.8.7/distrib/rpm/fsarchiver.spec new/fsarchiver-0.8.8/distrib/rpm/fsarchiver.spec --- old/fsarchiver-0.8.7/distrib/rpm/fsarchiver.spec 2023-03-19 14:54:55.000000000 +0100 +++ new/fsarchiver-0.8.8/distrib/rpm/fsarchiver.spec 2023-03-19 15:35:09.000000000 +0100 @@ -1,5 +1,5 @@ Name: fsarchiver -Version: 0.8.7 +Version: 0.8.8 Release: 1%{?dist} Summary: Safe and flexible file-system backup/deployment tool diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/fsarchiver-0.8.7/missing new/fsarchiver-0.8.8/missing --- old/fsarchiver-0.8.7/missing 2023-03-19 14:56:47.000000000 +0100 +++ new/fsarchiver-0.8.8/missing 2024-12-14 10:28:34.000000000 +0100 @@ -1,9 +1,11 @@ #! /bin/sh -# Common wrapper for a few potentially missing GNU programs. +# Common wrapper for a few potentially missing GNU and other programs. -scriptversion=2018-03-07.03; # UTC +scriptversion=2024-06-07.14; # UTC -# Copyright (C) 1996-2021 Free Software Foundation, Inc. +# shellcheck disable=SC2006,SC2268 # we must support pre-POSIX shells + +# Copyright (C) 1996-2024 Free Software Foundation, Inc. # Originally written by Fran,cois Pinard <[email protected]>, 1996. # This program is free software; you can redistribute it and/or modify @@ -54,18 +56,20 @@ -v, --version output version information and exit Supported PROGRAM values: - aclocal autoconf autoheader autom4te automake makeinfo - bison yacc flex lex help2man +aclocal autoconf autogen autoheader autom4te automake autoreconf +bison flex help2man lex makeinfo perl yacc Version suffixes to PROGRAM as well as the prefixes 'gnu-', 'gnu', and 'g' are ignored when checking the name. -Send bug reports to <[email protected]>." +Report bugs to <[email protected]>. +GNU Automake home page: <https://www.gnu.org/software/automake/>. +General help using GNU software: <https://www.gnu.org/gethelp/>." exit $? ;; -v|--v|--ve|--ver|--vers|--versi|--versio|--version) - echo "missing $scriptversion (GNU Automake)" + echo "missing (GNU Automake) $scriptversion" exit $? ;; @@ -108,7 +112,7 @@ program_details () { case $1 in - aclocal|automake) + aclocal|automake|autoreconf) echo "The '$1' program is part of the GNU Automake package:" echo "<$gnu_software_URL/automake>" echo "It also requires GNU Autoconf, GNU m4 and Perl in order to run:" @@ -123,6 +127,9 @@ echo "<$gnu_software_URL/m4/>" echo "<$perl_URL>" ;; + *) + : + ;; esac } @@ -137,48 +144,55 @@ printf '%s\n' "'$1' is $msg." configure_deps="'configure.ac' or m4 files included by 'configure.ac'" + autoheader_deps="'acconfig.h'" + automake_deps="'Makefile.am'" + aclocal_deps="'acinclude.m4'" case $normalized_program in + aclocal*) + echo "You should only need it if you modified $aclocal_deps or" + echo "$configure_deps." + ;; autoconf*) - echo "You should only need it if you modified 'configure.ac'," - echo "or m4 files included by it." - program_details 'autoconf' + echo "You should only need it if you modified $configure_deps." + ;; + autogen*) + echo "You should only need it if you modified a '.def' or '.tpl' file." + echo "You may want to install the GNU AutoGen package:" + echo "<$gnu_software_URL/autogen/>" ;; autoheader*) - echo "You should only need it if you modified 'acconfig.h' or" + echo "You should only need it if you modified $autoheader_deps or" echo "$configure_deps." - program_details 'autoheader' ;; automake*) - echo "You should only need it if you modified 'Makefile.am' or" - echo "$configure_deps." - program_details 'automake' - ;; - aclocal*) - echo "You should only need it if you modified 'acinclude.m4' or" + echo "You should only need it if you modified $automake_deps or" echo "$configure_deps." - program_details 'aclocal' ;; - autom4te*) + autom4te*) echo "You might have modified some maintainer files that require" echo "the 'autom4te' program to be rebuilt." - program_details 'autom4te' + ;; + autoreconf*) + echo "You should only need it if you modified $aclocal_deps or" + echo "$automake_deps or $autoheader_deps or $automake_deps or" + echo "$configure_deps." ;; bison*|yacc*) echo "You should only need it if you modified a '.y' file." echo "You may want to install the GNU Bison package:" echo "<$gnu_software_URL/bison/>" ;; - lex*|flex*) - echo "You should only need it if you modified a '.l' file." - echo "You may want to install the Fast Lexical Analyzer package:" - echo "<$flex_URL>" - ;; help2man*) echo "You should only need it if you modified a dependency" \ "of a man page." echo "You may want to install the GNU Help2man package:" echo "<$gnu_software_URL/help2man/>" ;; + lex*|flex*) + echo "You should only need it if you modified a '.l' file." + echo "You may want to install the Fast Lexical Analyzer package:" + echo "<$flex_URL>" + ;; makeinfo*) echo "You should only need it if you modified a '.texi' file, or" echo "any other file indirectly affecting the aspect of the manual." @@ -189,6 +203,12 @@ echo "want to install GNU make:" echo "<$gnu_software_URL/make/>" ;; + perl*) + echo "You should only need it to run GNU Autoconf, GNU Automake, " + echo " assorted other tools, or if you modified a Perl source file." + echo "You may want to install the Perl 5 language interpreter:" + echo "<$perl_URL>" + ;; *) echo "You might have modified some files without having the proper" echo "tools for further handling them. Check the 'README' file, it" @@ -197,6 +217,7 @@ echo "case some other package contains this missing '$1' program." ;; esac + program_details "$normalized_program" } give_advice "$1" | sed -e '1s/^/WARNING: /' \ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/fsarchiver-0.8.7/src/fs_ext2.c new/fsarchiver-0.8.8/src/fs_ext2.c --- old/fsarchiver-0.8.7/src/fs_ext2.c 2023-03-19 14:12:31.000000000 +0100 +++ new/fsarchiver-0.8.8/src/fs_ext2.c 2024-12-14 10:11:26.000000000 +0100 @@ -59,6 +59,10 @@ // us and therefore is not preserved (i.e. present in FSA_FEATURE_INCOMPAT_SUPP but not listed // below). Users can easily enable it with tune2fs if desired. // +// /etc/mke2fs.conf feature list from [fs_types] section applies to mkfs.extX, mke2fs -t extX +// and mke2fs -j/-J. FSArchiver calls mke2fs without specifying -t/-j/-J, therefore only the +// [defaults] section, containing ext2 baseline features, is used. +// struct s_features mkfeatures[] = // cf e2fsprogs-1.47.0/lib/e2p/feature.c { {"has_journal", FSA_EXT3_FEATURE_COMPAT_HAS_JOURNAL, E2P_FEATURE_COMPAT, EXTFSTYPE_EXT3, PROGVER(1,39,0)}, @@ -349,7 +353,10 @@ strlcatf(options, sizeof(options), " -I %ld ", (long)devisize); // filesystem revision: good-old-rev or dynamic - strlcatf(options, sizeof(options), " -r %d ", (int)fsextrevision); + if (e2fstoolsver<PROGVER(1,47,2)) + strlcatf(options, sizeof(options), " -r %d ", (int)fsextrevision); + else + strlcatf(options, sizeof(options), " -E revision=%d ", (int)fsextrevision); // if extfs revision is dynamic and there are features in the list if (fsextrevision!=EXT2_GOOD_OLD_REV && strlist_count(&strfeatures)>0) diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' --exclude Makefile.in --exclude configure --exclude config.guess --exclude '*.pot' --exclude mkinstalldirs --exclude aclocal.m4 --exclude config.sub --exclude depcomp --exclude install-sh --exclude ltmain.sh old/fsarchiver-0.8.7/src/fsarchiver.c new/fsarchiver-0.8.8/src/fsarchiver.c --- old/fsarchiver-0.8.7/src/fsarchiver.c 2023-03-19 14:12:31.000000000 +0100 +++ new/fsarchiver-0.8.8/src/fsarchiver.c 2024-08-25 16:48:14.000000000 +0200 @@ -231,12 +231,17 @@ break; case 'j': // compression jobs g_options.compressjobs=atoi(optarg); - if (g_options.compressjobs<1 || g_options.compressjobs>FSA_MAX_COMPJOBS) + if (g_options.compressjobs<1) { - errprintf("[%s] is not a valid number of jobs. Must be between 1 and %d\n", optarg, FSA_MAX_COMPJOBS); + errprintf("[%s] is not a valid number of jobs. Must be at least 1\n", optarg); usage(progname, false); return 1; } + if (g_options.compressjobs>FSA_MAX_COMPJOBS) + { + g_options.compressjobs = FSA_MAX_COMPJOBS; + msgprintf(MSG_FORCE, "[%s] is greater than the maximum number of jobs. Limiting to %d.\n", optarg, FSA_MAX_COMPJOBS); + } break; case 'e': // exclude files/directories strlist_add(&g_options.exclude, optarg);
